1 This document summarizes new features and bugfixes in each stable
2 release of Tor. If you want to see more detailed descriptions of the
3 changes in each development snapshot, see the ChangeLog file.
5 Changes in version 0.4.5.7 - 2021-03-16
6 Tor 0.4.5.7 fixes two important denial-of-service bugs in earlier
9 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
10 who can send directory data to a Tor instance to force that Tor
11 instance to consume huge amounts of CPU. This is easiest to exploit
12 against authorities, since anybody can upload to them, but directory
13 caches could also exploit this vulnerability against relays or clients
14 when they download. The other vulnerability (TROVE-2021-002) only
15 affects directory authorities, and would allow an attacker to remotely
16 crash the authority with an assertion failure. Patches have already
17 been provided to the authority operators, to help ensure
20 We recommend that everybody upgrade to one of the releases that fixes
21 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
24 This release also updates our GeoIP data source, and fixes a few
25 smaller bugs in earlier releases.
27 o Major bugfixes (security, denial of service):
28 - Disable the dump_desc() function that we used to dump unparseable
29 information to disk. It was called incorrectly in several places,
30 in a way that could lead to excessive CPU usage. Fixes bug 40286;
31 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
32 001 and CVE-2021-28089.
33 - Fix a bug in appending detached signatures to a pending consensus
34 document that could be used to crash a directory authority. Fixes
35 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
38 o Minor features (geoip data):
39 - We have switched geoip data sources. Previously we shipped IP-to-
40 country mappings from Maxmind's GeoLite2, but in 2019 they changed
41 their licensing terms, so we were unable to update them after that
42 point. We now ship geoip files based on the IPFire Location
43 Database instead. (See https://location.ipfire.org/ for more
44 information). This release updates our geoip files to match the
45 IPFire Location Database as retrieved on 2021/03/12. Closes
48 o Minor bugfixes (directory authority):
49 - Now that exit relays don't allow exit connections to directory
50 authority DirPorts (to prevent network reentry), disable
51 authorities' reachability self test on the DirPort. Fixes bug
52 40287; bugfix on 0.4.5.5-rc.
54 o Minor bugfixes (documentation):
55 - Fix a formatting error in the documentation for
56 VirtualAddrNetworkIPv6. Fixes bug 40256; bugfix on 0.2.9.4-alpha.
58 o Minor bugfixes (Linux, relay):
59 - Fix a bug in determining total available system memory that would
60 have been triggered if the format of Linux's /proc/meminfo file
61 had ever changed to include "MemTotal:" in the middle of a line.
62 Fixes bug 40315; bugfix on 0.2.5.4-alpha.
64 o Minor bugfixes (metrics port):
65 - Fix a BUG() warning on the MetricsPort for an internal missing
66 handler. Fixes bug 40295; bugfix on 0.4.5.1-alpha.
68 o Minor bugfixes (onion service):
69 - Remove a harmless BUG() warning when reloading tor configured with
70 onion services. Fixes bug 40334; bugfix on 0.4.5.1-alpha.
72 o Minor bugfixes (portability):
73 - Fix a non-portable usage of "==" with "test" in the configure
74 script. Fixes bug 40298; bugfix on 0.4.5.1-alpha.
76 o Minor bugfixes (relay):
77 - Remove a spammy log notice falsely claiming that the IPv4/v6
78 address was missing. Fixes bug 40300; bugfix on 0.4.5.1-alpha.
79 - Do not query the address cache early in the boot process when
80 deciding if a relay needs to fetch early directory information
81 from an authority. This bug resulted in a relay falsely believing
82 it didn't have an address and thus triggering an authority fetch
83 at each boot. Related to our fix for 40300.
85 o Removed features (mallinfo deprecated):
86 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
90 Changes in version 0.4.5.6 - 2021-02-15
91 The Tor 0.4.5.x release series is dedicated to the memory of Karsten
92 Loesing (1979-2020), Tor developer, cypherpunk, husband, and father.
93 Karsten is best known for creating the Tor metrics portal and leading
94 the metrics team, but he was involved in Tor from the early days. For
95 example, while he was still a student he invented and implemented the
96 v2 onion service directory design, and he also served as an ambassador
97 to the many German researchers working in the anonymity field. We
98 loved him and respected him for his patience, his consistency, and his
99 welcoming approach to growing our community.
101 This release series introduces significant improvements in relay IPv6
102 address discovery, a new "MetricsPort" mechanism for relay operators
103 to measure performance, LTTng support, build system improvements to
104 help when using Tor as a static library, and significant bugfixes
105 related to Windows relay performance. It also includes numerous
106 smaller features and bugfixes.
108 Below are the changes since 0.4.4.7. For a list of changes since
109 0.4.5.5-rc, see the ChangeLog file.
111 o Major features (build):
112 - When building Tor, first link all object files into a single
113 static library. This may help with embedding Tor in other
114 programs. Note that most Tor functions do not constitute a part of
115 a stable or supported API: only those functions in tor_api.h
116 should be used if embedding Tor. Closes ticket 40127.
118 o Major features (metrics):
119 - Introduce a new MetricsPort which exposes, through an HTTP
120 interface, a series of metrics that tor collects at runtime. At
121 the moment, the only supported output format is Prometheus data
122 model. Closes ticket 40063. See the manual page for more
123 information and security considerations.
125 o Major features (relay, IPv6):
126 - The torrc option Address now supports IPv6. This unifies our
127 address discovery interface to support IPv4, IPv6, and hostnames.
129 - Launch IPv4 and IPv6 ORPort self-test circuits on relays and
130 bridges. Closes ticket 33222.
131 - Relays now automatically bind on IPv6 for their ORPort, unless
132 specified otherwise with the IPv4Only flag. Closes ticket 33246.
133 - When a relay with IPv6 support is told to open a connection to
134 another relay, and the extend cell lists both IPv4 and IPv6
135 addresses, the first relay now picks randomly which address to
136 use. Closes ticket 33220.
137 - Relays now track their IPv6 ORPort reachability separately from
138 the reachability of their IPv4 ORPort. They will not publish a
139 descriptor unless _both_ ports appear to be externally reachable.
142 o Major features (tracing):
143 - Add event-tracing library support for USDT and LTTng-UST, and a
144 few tracepoints in the circuit subsystem. More will come
145 incrementally. This feature is compiled out by default: it needs
146 to be enabled at configure time. See documentation in
147 doc/HACKING/Tracing.md. Closes ticket 32910.
149 o Major bugfixes (directory cache, performance, windows):
150 - Limit the number of items in the consensus diff cache to 64 on
151 Windows. We hope this will mitigate an issue where Windows relay
152 operators reported Tor using 100% CPU, while we investigate better
153 solutions. Fixes bug 24857; bugfix on 0.3.1.1-alpha.
155 o Major bugfixes (relay, windows):
156 - Fix a bug in our implementation of condition variables on Windows.
157 Previously, a relay on Windows would use 100% CPU after running
158 for some time. Because of this change, Tor now require Windows
159 Vista or later to build and run. Fixes bug 30187; bugfix on
160 0.2.6.3-alpha. (This bug became more serious in 0.3.1.1-alpha with
161 the introduction of consensus diffs.) Patch by Daniel Pinto.
163 o Major bugfixes (TLS, buffer):
164 - When attempting to read N bytes on a TLS connection, really try to
165 read all N bytes. Previously, Tor would stop reading after the
166 first TLS record, which can be smaller than the N bytes requested,
167 and not check for more data until the next mainloop event. Fixes
168 bug 40006; bugfix on 0.1.0.5-rc.
170 o Minor features (address discovery):
171 - If no Address statements are found, relays now prioritize guessing
172 their address by looking at the local interface instead of the
173 local hostname. If the interface address can't be found, the local
174 hostname is used. Closes ticket 33238.
176 o Minor features (admin tools):
177 - Add a new --format argument to -key-expiration option to allow
178 specifying the time format of the expiration date. Adds Unix
179 timestamp format support. Patch by Daniel Pinto. Closes
182 o Minor features (authority, logging):
183 - Log more information for directory authority operators during the
184 consensus voting process, and while processing relay descriptors.
187 o Minor features (bootstrap reporting):
188 - When reporting bootstrapping status on a relay, do not consider
189 connections that have never been the target of an origin circuit.
190 Previously, all connection failures were treated as potential
191 bootstrapping failures, including connections that had been opened
192 because of client requests. Closes ticket 25061.
194 o Minor features (build):
195 - When running the configure script, try to detect version
196 mismatches between the OpenSSL headers and libraries, and suggest
197 that the user should try "--with-openssl-dir". Closes 40138.
198 - If the configure script has given any warnings, remind the user
199 about them at the end of the script. Related to 40138.
201 o Minor features (configuration):
202 - Allow using wildcards (* and ?) with the %include option on
203 configuration files. Closes ticket 25140. Patch by Daniel Pinto.
204 - Allow the configuration options EntryNodes, ExcludeNodes,
205 ExcludeExitNodes, ExitNodes, MiddleNodes, HSLayer2Nodes and
206 HSLayer3Nodes to be specified multiple times. Closes ticket 28361.
207 Patch by Daniel Pinto.
209 o Minor features (control port):
210 - Add a DROPTIMEOUTS command to drop circuit build timeout history
211 and reset the current timeout. Closes ticket 40002.
212 - When a stream enters the AP_CONN_STATE_CONTROLLER_WAIT status,
213 send a control port event. Closes ticket 32190. Patch by
215 - Introduce GETINFO "stats/ntor/{assigned/requested}" and
216 "stats/tap/{assigned/requested}" to get the NTor and TAP circuit
217 onion handshake counts respectively. Closes ticket 28279. Patch by
220 o Minor features (control port, IPv6):
221 - Tor relays now try to report to the controller when they are
222 launching an IPv6 self-test. Closes ticket 34068.
223 - Introduce "GETINFO address/v4" and "GETINFO address/v6" in the
224 control port to fetch the Tor host's respective IPv4 or IPv6
225 address. We keep "GETINFO address" for backwards-compatibility.
226 Closes ticket 40039. Patch by Neel Chauhan.
228 o Minor features (directory authorities):
229 - Add a new consensus method 30 that removes the unnecessary "="
230 padding from ntor-onion-key. Closes ticket 7869. Patch by
232 - Directory authorities now reject descriptors from relays running
233 Tor versions from the obsolete 0.4.1 series. Resolves ticket
234 34357. Patch by Neel Chauhan.
235 - The AssumeReachable option no longer stops directory authorities
236 from checking whether other relays are running. A new
237 AuthDirTestReachability option can be used to disable these
238 checks. Closes ticket 34445.
239 - When looking for possible Sybil attacks, also consider IPv6
240 addresses. Two routers are considered to have "the same" address
241 by this metric if they are in the same /64 network. Patch from
242 Maurice Pibouin. Closes ticket 7193.
244 o Minor features (directory authorities, IPv6):
245 - Make authorities add their IPv6 ORPort (if any) to the trusted
246 servers list. Authorities previously added only their IPv4
247 addresses. Closes ticket 32822.
249 o Minor features (documentation):
250 - Mention the "!badexit" directive that can appear in an authority's
251 approved-routers file, and update the description of the
252 "!invalid" directive. Closes ticket 40188.
254 o Minor features (ed25519, relay):
255 - Save a relay's base64-encoded ed25519 identity key to the data
256 directory in a file named fingerprint-ed25519. Closes ticket
257 30642. Patch by Neel Chauhan.
259 o Minor features (heartbeat):
260 - Include the total number of inbound and outbound IPv4 and IPv6
261 connections in the heartbeat message. Closes ticket 29113.
263 o Minor features (IPv6, ExcludeNodes):
264 - Handle IPv6 addresses in ExcludeNodes; previously they were
265 ignored. Closes ticket 34065. Patch by Neel Chauhan.
267 o Minor features (logging):
268 - Add the running glibc version to the log, and the compiled glibc
269 version to the library list returned when using --library-versions.
270 Patch from Daniel Pinto. Closes ticket 40047.
271 - Consider an HTTP 301 response to be an error (like a 404) when
272 processing a directory response. Closes ticket 40053.
273 - Log directory fetch statistics as a single line. Closes
275 - Provide more complete descriptions of our connections when logging
276 about them. Closes ticket 40041.
277 - When describing a relay in the logs, we now include its ed25519
278 identity. Closes ticket 22668.
280 o Minor features (onion services):
281 - Only overwrite an onion service's existing hostname file if its
282 contents are wrong. This enables read-only onion-service
283 directories. Resolves ticket 40062. Patch by Neel Chauhan.
285 o Minor features (pluggable transports):
286 - Add an OutboundBindAddressPT option to allow users to specify
287 which IPv4 and IPv6 address pluggable transports should use for
288 outgoing IP packets. Tor does not have a way to enforce that the
289 pluggable transport honors this option, so each pluggable transport
290 needs to implement support on its own. Closes ticket 5304.
292 o Minor features (protocol, proxy support, defense in depth):
293 - Respond more deliberately to misbehaving proxies that leave
294 leftover data on their connections, so as to make Tor even less
295 likely to allow the proxies to pass their data off as having come
296 from a relay. Closes ticket 40017.
298 o Minor features (relay address tracking):
299 - We now store relay addresses for OR connections in a more logical
300 way. Previously we would sometimes overwrite the actual address of
301 a connection with a "canonical address", and then store the "real
302 address" elsewhere to remember it. We now track the "canonical
303 address" elsewhere for the cases where we need it, and leave the
304 connection's address alone. Closes ticket 33898.
306 o Minor features (relay):
307 - If a relay is unable to discover its address, attempt to learn it
308 from the NETINFO cell. Closes ticket 40022.
309 - Log immediately when launching a relay self-check. Previously we
310 would try to log before launching checks, or approximately when we
311 intended to launch checks, but this tended to be error-prone.
314 o Minor features (relay, address discovery):
315 - If Address option is not found in torrc, attempt to learn our
316 address with the configured ORPort address if any. Closes
319 o Minor features (relay, IPv6):
320 - Add an AssumeReachableIPv6 option to disable self-checking IPv6
321 reachability. Closes part of ticket 33224.
322 - Add new "assume-reachable" and "assume-reachable-ipv6" consensus
323 parameters to be used in an emergency to tell relays that they
324 should publish even if they cannot complete their ORPort self-
325 checks. Closes ticket 34064 and part of 33224.
326 - Allow relays to send IPv6-only extend cells. Closes ticket 33222.
327 - Declare support for the Relay=3 subprotocol version. Closes
329 - When launching IPv6 ORPort self-test circuits, make sure that the
330 second-last hop can initiate an IPv6 extend. Closes ticket 33222.
332 o Minor features (safety):
333 - Log a warning at startup if Tor is built with compile-time options
334 that are likely to make it less stable or reliable. Closes
337 o Minor features (specification update):
338 - Several fields in microdescriptors, router descriptors, and
339 consensus documents that were formerly optional are now required.
340 Implements proposal 315; closes ticket 40132.
342 o Minor features (state management):
343 - When loading the state file, remove entries from the statefile
344 that have been obsolete for a long time. Ordinarily Tor preserves
345 unrecognized entries in order to keep forward-compatibility, but
346 these entries have not actually been used in any release since
347 before 0.3.5.x. Closes ticket 40137.
349 o Minor features (statistics, ipv6):
350 - Relays now publish IPv6-specific counts of single-direction versus
351 bidirectional relay connections. Closes ticket 33264.
352 - Relays now publish their IPv6 read and write statistics over time,
353 if statistics are enabled. Closes ticket 33263.
355 o Minor features (subprotocol versions):
356 - Use the new limitations on subprotocol versions due to proposal
357 318 to simplify our implementation. Part of ticket 40133.
359 o Minor features (testing configuration):
360 - The TestingTorNetwork option no longer implicitly sets
361 AssumeReachable to 1. This change allows us to test relays' self-
362 testing mechanisms, and to test authorities' relay-testing
363 functionality. Closes ticket 34446.
365 o Minor features (testing):
366 - Added unit tests for channel_matches_target_addr_for_extend().
367 Closes Ticket 33919. Patch by MrSquanchee.
369 o Minor bugfixes (circuit padding):
370 - When circpad_send_padding_cell_for_callback is called,
371 `is_padding_timer_scheduled` flag was not reset. Now it is set to
372 0 at the top of that function. Fixes bug 32671; bugfix
374 - Add a per-circuit padding machine instance counter, so we can
375 differentiate between shutdown requests for old machines on a
376 circuit. Fixes bug 30992; bugfix on 0.4.1.1-alpha.
377 - Add the ability to keep circuit padding machines if they match a
378 set of circuit states or purposes. This allows us to have machines
379 that start up under some conditions but don't shut down under
380 others. We now use this mask to avoid starting up introduction
381 circuit padding again after the machines have already completed.
382 Fixes bug 32040; bugfix on 0.4.1.1-alpha.
384 o Minor bugfixes (circuit, handshake):
385 - In the v3 handshaking code, use connection_or_change_state() to
386 change the state. Previously, we changed the state directly, but
387 this did not pass the state change to the pubsub or channel
388 objects, potentially leading to bugs. Fixes bug 32880; bugfix on
389 0.2.3.6-alpha. Patch by Neel Chauhan.
391 o Minor bugfixes (compilation):
392 - Change the linker flag ordering in our library search code so that
393 it works for compilers that need the libraries to be listed in the
394 right order. Fixes bug 33624; bugfix on 0.1.1.0-alpha.
395 - Fix the "--enable-static-tor" switch to properly set the "-static"
396 compile option onto the tor binary only. Fixes bug 40111; bugfix
399 o Minor bugfixes (configuration):
400 - Exit Tor on a misconfiguration when the Bridge line is configured
401 to use a transport but no corresponding ClientTransportPlugin can
402 be found. Prior to this fix, Tor would attempt to connect to the
403 bridge directly without using the transport, making it easier for
404 adversaries to notice the bridge. Fixes bug 25528; bugfix
407 o Minor bugfixes (control port):
408 - Make sure we send the SOCKS request address in relay begin cells
409 when a stream is attached with the purpose
410 CIRCUIT_PURPOSE_CONTROLLER. Fixes bug 33124; bugfix on 0.0.5.
411 Patch by Neel Chauhan.
413 o Minor bugfixes (crash, relay, signing key):
414 - Avoid assertion failures when we run Tor from the command line
415 with `--key-expiration sign`, but an ORPort is not set. Fixes bug
416 40015; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
418 o Minor bugfixes (logging):
419 - Avoid a spurious log message about missing subprotocol versions,
420 when the consensus that we're reading from is older than the
421 current release. Previously we had made this message nonfatal, but
422 in practice, it is never relevant when the consensus is older than
423 the current release. Fixes bug 40281; bugfix on 0.4.0.1-alpha.
424 - Remove trailing whitespace from control event log messages. Fixes
425 bug 32178; bugfix on 0.1.1.1-alpha. Based on a patch by
427 - Turn warning-level log message about SENDME failure into a debug-
428 level message. (This event can happen naturally, and is no reason
429 for concern). Fixes bug 40142; bugfix on 0.4.1.1-alpha.
430 - When logging a rate-limited message about how many messages have
431 been suppressed in the last N seconds, give an accurate value for
432 N, rounded up to the nearest minute. Previously we would report
433 the size of the rate-limiting interval, regardless of when the
434 messages started to occur. Fixes bug 19431; bugfix
437 o Minor bugfixes (onion services):
438 - Avoid a non-fatal assertion in certain edge-cases when
439 establishing a circuit to an onion service. Fixes bug 32666;
440 bugfix on 0.3.0.3-alpha.
442 o Minor bugfixes (rust, protocol versions):
443 - Declare support for the onion service introduction point denial of
444 service extensions when building with Rust. Fixes bug 34248;
445 bugfix on 0.4.2.1-alpha.
446 - Make Rust protocol version support checks consistent with the
447 undocumented error behavior of the corresponding C code. Fixes bug
448 34251; bugfix on 0.3.3.5-rc.
450 o Minor bugfixes (self-testing):
451 - When receiving an incoming circuit, only accept it as evidence
452 that we are reachable if the declared address of its channel is
453 the same address we think that we have. Otherwise, it could be
454 evidence that we're reachable on some other address. Fixes bug
455 20165; bugfix on 0.1.0.1-rc.
457 o Minor bugfixes (spec conformance):
458 - Use the correct key type when generating signing->link
459 certificates. Fixes bug 40124; bugfix on 0.2.7.2-alpha.
461 o Minor bugfixes (subprotocol versions):
462 - Consistently reject extra commas, instead of only rejecting
463 leading commas. Fixes bug 27194; bugfix on 0.2.9.4-alpha.
464 - In summarize_protover_flags(), treat empty strings the same as
465 NULL. This prevents protocols_known from being set. Previously, we
466 treated empty strings as normal strings, which led to
467 protocols_known being set. Fixes bug 34232; bugfix on
468 0.3.3.2-alpha. Patch by Neel Chauhan.
470 o Code simplification and refactoring:
471 - Add and use a set of functions to perform down-casts on constant
472 connection and channel pointers. Closes ticket 40046.
473 - Refactor our code that logs descriptions of connections, channels,
474 and the peers on them, to use a single call path. This change
475 enables us to refactor the data types that they use, and eliminates
476 many confusing usages of those types. Closes ticket 40041.
477 - Refactor some common node selection code into a single function.
479 - Remove the now-redundant 'outbuf_flushlen' field from our
480 connection type. It was previously used for an older version of
481 our rate-limiting logic. Closes ticket 33097.
482 - Rename "fascist_firewall_*" identifiers to "reachable_addr_*"
483 instead, for consistency with other code. Closes ticket 18106.
484 - Rename functions about "advertised" ports which are not in fact
485 guaranteed to return the ports that have been advertised. Closes
487 - Split implementation of several command line options from
488 options_init_from_torrc into smaller isolated functions. Patch by
489 Daniel Pinto. Closes ticket 40102.
490 - When an extend cell is missing an IPv4 or IPv6 address, fill in
491 the address from the extend info. This is similar to what was done
492 in ticket 33633 for ed25519 keys. Closes ticket 33816. Patch by
495 o Deprecated features:
496 - The "non-builtin" argument to the "--dump-config" command is now
497 deprecated. When it works, it behaves the same as "short", which
498 you should use instead. Closes ticket 33398.
501 - Replace URLs from our old bugtracker so that they refer to the new
502 bugtracker and wiki. Closes ticket 40101.
505 - We no longer ship or build a "tor.service" file for use with
506 systemd. No distribution included this script unmodified, and we
507 don't have the expertise ourselves to maintain this in a way that
508 all the various systemd-based distributions can use. Closes
510 - We no longer ship support for the Android logging API. Modern
511 versions of Android can use the syslog API instead. Closes
513 - The "optimistic data" feature is now always on; there is no longer
514 an option to disable it from the torrc file or from the consensus
515 directory. Closes part of 40139.
516 - The "usecreatefast" network parameter is now removed; there is no
517 longer an option for authorities to turn it off. Closes part
521 - Add unit tests for bandwidth statistics manipulation functions.
522 Closes ticket 33812. Patch by MrSquanchee.
524 o Code simplification and refactoring (autoconf):
525 - Remove autoconf checks for unused funcs and headers. Closes ticket
526 31699; Patch by @bduszel
528 o Code simplification and refactoring (maintainer scripts):
529 - Disable by default the pre-commit hook. Use the environment
530 variable TOR_EXTRA_PRE_COMMIT_CHECKS in order to run it.
531 Furthermore, stop running practracker in the pre-commit hook and
532 make check-local. Closes ticket 40019.
534 o Code simplification and refactoring (relay address):
535 - Most of IPv4 representation was using "uint32_t". It has now been
536 moved to use the internal "tor_addr_t" interface instead. This is
537 so we can properly integrate IPv6 along IPv4 with common
538 interfaces. Closes ticket 40043.
540 o Documentation (manual page):
541 - Move them from doc/ to doc/man/. Closes ticket 40044.
542 - Describe the status of the "Sandbox" option more accurately. It is
543 no longer "experimental", but it _is_ dependent on kernel and libc
544 versions. Closes ticket 23378.
546 o Documentation (tracing):
547 - Document in depth the circuit subsystem trace events in the new
548 doc/tracing/EventsCircuit.md. Closes ticket 40036.
550 o Removed features (controller):
551 - Remove the "GETINFO network-status" controller command. It has
552 been deprecated since 0.3.1.1-alpha. Closes ticket 22473.
555 Changes in version 0.4.4.6 - 2020-11-12
556 Tor 0.4.4.6 is the second stable release in the 0.4.4.x series. It
557 backports fixes from later releases, including a fix for TROVE-2020-
558 005, a security issue that could be used, under certain cases, by an
559 adversary to observe traffic patterns on a limited number of circuits
560 intended for a different relay.
562 o Major bugfixes (security, backport from 0.4.5.1-alpha):
563 - When completing a channel, relays now check more thoroughly to
564 make sure that it matches any pending circuits before attaching
565 those circuits. Previously, address correctness and Ed25519
566 identities were not checked in this case, but only when extending
567 circuits on an existing channel. Fixes bug 40080; bugfix on
568 0.2.7.2-alpha. Resolves TROVE-2020-005.
570 o Minor features (directory authorities, backport from 0.4.5.1-alpha):
571 - Authorities now list a different set of protocols as required and
572 recommended. These lists have been chosen so that only truly
573 recommended and/or required protocols are included, and so that
574 clients using 0.2.9 or later will continue to work (even though
575 they are not supported), whereas only relays running 0.3.5 or
576 later will meet the requirements. Closes ticket 40162.
577 - Make it possible to specify multiple ConsensusParams torrc lines.
578 Now directory authority operators can for example put the main
579 ConsensusParams config in one torrc file and then add to it from a
580 different torrc file. Closes ticket 40164.
582 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
583 - Tor no longer allows subprotocol versions larger than 63.
584 Previously version numbers up to UINT32_MAX were allowed, which
585 significantly complicated our code. Implements proposal 318;
588 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
589 - Fix a rendezvous cache unit test that was triggering an underflow
590 on the global rend cache allocation. Fixes bug 40125; bugfix
592 - Fix another rendezvous cache unit test that was triggering an
593 underflow on the global rend cache allocation. Fixes bug 40126;
594 bugfix on 0.2.8.1-alpha.
596 o Minor bugfixes (compilation, backport from 0.4.5.1-alpha):
597 - Fix compiler warnings that would occur when building with
598 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
599 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
600 - Resolve a compilation warning that could occur in
601 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
603 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
604 - Remove a debug logging statement that uselessly spammed the logs.
605 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
607 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
608 - Avoid a fatal assert() when failing to create a listener
609 connection for an address that was in use. Fixes bug 40073; bugfix
612 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
613 - For HSFETCH commands on v2 onion services addresses, check the
614 length of bytes decoded, not the base32 length. Fixes bug 34400;
615 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
618 Changes in version 0.4.3.7 - 2020-11-12
619 Tor 0.4.3.7 backports several bugfixes from later releases. It
620 includes a fix for TROVE-2020-005, a security issue that could be
621 used, under certain cases, by an adversary to observe traffic patterns
622 on a limited number of circuits intended for a different relay.
624 Please be aware that support for the 0.4.3.x series will end on 15
625 February 2021. Please upgrade to 0.4.4.x or 0.4.5.x before then, or
626 downgrade to 0.3.5.x, which will be supported until at least 1
629 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
630 - Replace the 148 fallback directories originally included in Tor
631 0.4.1.4-rc (of which around 105 are still functional) with a list
632 of 144 fallbacks generated in July 2020. Closes ticket 40061.
634 o Major bugfixes (security, backport from 0.4.5.1-alpha):
635 - When completing a channel, relays now check more thoroughly to
636 make sure that it matches any pending circuits before attaching
637 those circuits. Previously, address correctness and Ed25519
638 identities were not checked in this case, but only when extending
639 circuits on an existing channel. Fixes bug 40080; bugfix on
640 0.2.7.2-alpha. Resolves TROVE-2020-005.
642 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
643 - When running with NSS enabled, make sure that NSS knows to expect
644 nonblocking sockets. Previously, we set our TCP sockets as
645 nonblocking, but did not tell NSS, which in turn could lead to
646 unexpected blocking behavior. Fixes bug 40035; bugfix
649 o Minor features (security, backport from 0.4.4.4-rc):
650 - Channels using obsolete versions of the Tor link protocol are no
651 longer allowed to circumvent address-canonicity checks. (This is
652 only a minor issue, since such channels have no way to set ed25519
653 keys, and therefore should always be rejected for circuits that
654 specify ed25519 identities.) Closes ticket 40081.
656 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
657 - Tor no longer allows subprotocol versions larger than 63.
658 Previously version numbers up to UINT32_MAX were allowed, which
659 significantly complicated our code. Implements proposal 318;
662 o Minor features (tests, backport from 0.4.4.5):
663 - Our "make check" target now runs the unit tests in 8 parallel
664 chunks. Doing this speeds up hardened CI builds by more than a
665 factor of two. Closes ticket 40098.
667 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
668 - Fix a rendezvous cache unit test that was triggering an underflow
669 on the global rend cache allocation. Fixes bug 40125; bugfix
671 - Fix another rendezvous cache unit test that was triggering an
672 underflow on the global rend cache allocation. Fixes bug 40126;
673 bugfix on 0.2.8.1-alpha.
675 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
676 - Fix a correctness bug that could cause an assertion failure if we
677 ever tried using the buf_move_all() function with an empty input
678 buffer. As far as we know, no released versions of Tor do this.
679 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
681 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
682 - Remove a debug logging statement that uselessly spammed the logs.
683 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
685 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
686 - On a bridge, treat all connections from an ExtORPort as remote by
687 default for the purposes of rate-limiting. Previously, bridges
688 would treat the connection as local unless they explicitly
689 received a "USERADDR" command. ExtORPort connections still count
690 as local if there is a USERADDR command with an explicit local
691 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
693 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
694 - Avoid a fatal assert() when failing to create a listener
695 connection for an address that was in use. Fixes bug 40073; bugfix
698 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
699 - Adjust the rules for when to warn about having too many
700 connections to other relays. Previously we'd tolerate up to 1.5
701 connections per relay on average. Now we tolerate more connections
702 for directory authorities, and raise the number of total
703 connections we need to see before we warn. Fixes bug 33880; bugfix
706 o Minor bugfixes (tests, 0.4.4.5):
707 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
708 on its own. Previously, it would exit with an error. Fixes bug
709 40099; bugfix on 0.2.8.1-alpha.
711 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
712 - For HSFETCH commands on v2 onion services addresses, check the
713 length of bytes decoded, not the base32 length. Fixes bug 34400;
714 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
716 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
717 - Fix a bug that prevented Tor from starting if its log file grew
718 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
720 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
721 - Add a deprecation warning for version 2 onion services. Closes
724 o Removed features (backport from 0.4.4.3-alpha):
725 - Our "check-local" test target no longer tries to use the
726 Coccinelle semantic patching tool parse all the C files. While it
727 is a good idea to try to make sure Coccinelle works on our C
728 before we run a Coccinelle patch, doing so on every test run has
729 proven to be disruptive. You can still run this tool manually with
730 "make check-cocci". Closes ticket 40030. ticket 40030.
733 Changes in version 0.3.5.12 - 2020-11-12
734 Tor 0.4.3.7 backports several bugfixes from later releases. It
735 includes a fix for TROVE-2020-005, a security issue that could be
736 used, under certain cases, by an adversary to observe traffic patterns
737 on a limited number of circuits intended for a different relay.
739 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
740 - Replace the 148 fallback directories originally included in Tor
741 0.4.1.4-rc (of which around 105 are still functional) with a list
742 of 144 fallbacks generated in July 2020. Closes ticket 40061.
744 o Major bugfixes (security, backport from 0.4.5.1-alpha):
745 - When completing a channel, relays now check more thoroughly to
746 make sure that it matches any pending circuits before attaching
747 those circuits. Previously, address correctness and Ed25519
748 identities were not checked in this case, but only when extending
749 circuits on an existing channel. Fixes bug 40080; bugfix on
750 0.2.7.2-alpha. Resolves TROVE-2020-005.
752 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
753 - When running with NSS enabled, make sure that NSS knows to expect
754 nonblocking sockets. Previously, we set our TCP sockets as
755 nonblocking, but did not tell NSS, which in turn could lead to
756 unexpected blocking behavior. Fixes bug 40035; bugfix
759 o Minor features (security, backport from 0.4.4.4-rc):
760 - Channels using obsolete versions of the Tor link protocol are no
761 longer allowed to circumvent address-canonicity checks. (This is
762 only a minor issue, since such channels have no way to set ed25519
763 keys, and therefore should always be rejected for circuits that
764 specify ed25519 identities.) Closes ticket 40081.
766 o Minor features (debugging, directory system):
767 - Don't crash when we find a non-guard with a guard-fraction value
768 set. Instead, log a bug warning, in an attempt to figure out how
769 this happened. Diagnostic for ticket 32868.
771 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
772 - Tor no longer allows subprotocol versions larger than 63.
773 Previously version numbers up to UINT32_MAX were allowed, which
774 significantly complicated our code. Implements proposal 318;
777 o Minor features (tests, backport from 0.4.4.5):
778 - Our "make check" target now runs the unit tests in 8 parallel
779 chunks. Doing this speeds up hardened CI builds by more than a
780 factor of two. Closes ticket 40098.
782 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
783 - Fix a rendezvous cache unit test that was triggering an underflow
784 on the global rend cache allocation. Fixes bug 40125; bugfix
786 - Fix another rendezvous cache unit test that was triggering an
787 underflow on the global rend cache allocation. Fixes bug 40126;
788 bugfix on 0.2.8.1-alpha.
790 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
791 - Fix a correctness bug that could cause an assertion failure if we
792 ever tried using the buf_move_all() function with an empty input
793 buffer. As far as we know, no released versions of Tor do this.
794 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
796 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
797 - Remove a debug logging statement that uselessly spammed the logs.
798 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
800 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
801 - On a bridge, treat all connections from an ExtORPort as remote by
802 default for the purposes of rate-limiting. Previously, bridges
803 would treat the connection as local unless they explicitly
804 received a "USERADDR" command. ExtORPort connections still count
805 as local if there is a USERADDR command with an explicit local
806 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
808 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
809 - Avoid a fatal assert() when failing to create a listener
810 connection for an address that was in use. Fixes bug 40073; bugfix
813 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
814 - Adjust the rules for when to warn about having too many
815 connections to other relays. Previously we'd tolerate up to 1.5
816 connections per relay on average. Now we tolerate more connections
817 for directory authorities, and raise the number of total
818 connections we need to see before we warn. Fixes bug 33880; bugfix
821 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
822 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
823 descriptors, when the IPv6 port was configured as "auto". Fixes
824 bug 32588; bugfix on 0.2.3.9-alpha.
826 o Minor bugfixes (tests, 0.4.4.5):
827 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
828 on its own. Previously, it would exit with an error. Fixes bug
829 40099; bugfix on 0.2.8.1-alpha.
831 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
832 - Fix a bug that prevented Tor from starting if its log file grew
833 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
835 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
836 - Add a deprecation warning for version 2 onion services. Closes
839 Changes in version 0.4.4.5 - 2020-09-15
840 Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This
841 series improves our guard selection algorithms, adds v3 onion balance
842 support, improves the amount of code that can be disabled when running
843 without relay support, and includes numerous small bugfixes and
844 enhancements. It also lays the ground for some IPv6 features that
845 we'll be developing more in the next (0.4.5) series.
847 Per our support policy, we support each stable release series for nine
848 months after its first stable release, or three months after the first
849 stable release of the next series: whichever is longer. This means
850 that 0.4.4.x will be supported until around June 2021--or later, if
851 0.4.5.x is later than anticipated.
853 Note also that support for 0.4.2.x has just ended; support for 0.4.3
854 will continue until Feb 15, 2021. We still plan to continue supporting
855 0.3.5.x, our long-term stable series, until Feb 2022.
857 Below are the changes since 0.4.3.6-rc. For a complete list of changes
858 since 0.4.4.4-rc, see the ChangeLog file.
860 o Major features (Proposal 310, performance + security):
861 - Implements Proposal 310, "Bandaid on guard selection". Proposal
862 310 solves load-balancing issues with older versions of the guard
863 selection algorithm, and improves its security. Under this new
864 algorithm, a newly selected guard never becomes Primary unless all
865 previously sampled guards are unreachable. Implements
866 recommendation from 32088. (Proposal 310 is linked to the CLAPS
867 project researching optimal client location-aware path selections.
868 This project is a collaboration between the UCLouvain Crypto Group,
869 the U.S. Naval Research Laboratory, and Princeton University.)
871 o Major features (fallback directory list):
872 - Replace the 148 fallback directories originally included in Tor
873 0.4.1.4-rc (of which around 105 are still functional) with a list
874 of 144 fallbacks generated in July 2020. Closes ticket 40061.
876 o Major features (IPv6, relay):
877 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
878 warning if the IPv4 or IPv6 address is an internal address, and
879 internal addresses are not allowed. But continue to use the other
880 address, if it is valid. Closes ticket 33817.
881 - If a relay can extend over IPv4 and IPv6, and both addresses are
882 provided, it chooses between them uniformly at random. Closes
884 - Re-use existing IPv6 connections for circuit extends. Closes
886 - Relays may extend circuits over IPv6, if the relay has an IPv6
887 ORPort, and the client supplies the other relay's IPv6 ORPort in
888 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
889 ORPort self-tests in 33222. Closes ticket 33817.
891 o Major features (v3 onion services):
892 - Allow v3 onion services to act as OnionBalance backend instances,
893 by using the HiddenServiceOnionBalanceInstance torrc option.
896 o Major bugfixes (NSS):
897 - When running with NSS enabled, make sure that NSS knows to expect
898 nonblocking sockets. Previously, we set our TCP sockets as
899 nonblocking, but did not tell NSS, which in turn could lead to
900 unexpected blocking behavior. Fixes bug 40035; bugfix
903 o Major bugfixes (onion services, DoS):
904 - Correct handling of parameters for the onion service DoS defense.
905 Previously, the consensus parameters for the onion service DoS
906 defenses were overwriting the parameters set by the service
907 operator using HiddenServiceEnableIntroDoSDefense. Fixes bug
908 40109; bugfix on 0.4.2.1-alpha.
910 o Major bugfixes (stats, onion services):
911 - Fix a bug where we were undercounting the Tor network's total
912 onion service traffic, by ignoring any traffic originating from
913 clients. Now we count traffic from both clients and services.
914 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
916 o Minor features (security):
917 - Channels using obsolete versions of the Tor link protocol are no
918 longer allowed to circumvent address-canonicity checks. (This is
919 only a minor issue, since such channels have no way to set ed25519
920 keys, and therefore should always be rejected for circuits that
921 specify ed25519 identities.) Closes ticket 40081.
923 o Minor features (bootstrap reporting):
924 - Report more detailed reasons for bootstrap failure when the
925 failure happens due to a TLS error. Previously we would just call
926 these errors "MISC" when they happened during read, and "DONE"
927 when they happened during any other TLS operation. Closes
930 o Minor features (client-only compilation):
931 - Disable more code related to the ext_orport protocol when
932 compiling without support for relay mode. Closes ticket 33368.
933 - Disable more of our self-testing code when support for relay mode
934 is disabled. Closes ticket 33370.
935 - Most server-side DNS code is now disabled when building without
936 support for relay mode. Closes ticket 33366.
938 o Minor features (code safety):
939 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
940 functions in DNS and IP address processing code, and adjust
941 codepaths to make them less likely to crash entire Tor instances.
942 Resolves issue 33788.
944 o Minor features (continuous integration):
945 - Run unit-test and integration test (Stem, Chutney) jobs with
946 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
947 Resolves ticket 32143.
949 o Minor features (control port):
950 - If a ClientName was specified in ONION_CLIENT_AUTH_ADD for an
951 onion service, display it when we use ONION_CLIENT_AUTH_VIEW.
952 Closes ticket 40089. Patch by Neel Chauhan.
953 - Return a descriptive error message from the 'GETINFO status/fresh-
954 relay-descs' command on the control port. Previously, we returned
955 a generic error of "Error generating descriptor". Closes ticket
956 32873. Patch by Neel Chauhan.
958 o Minor features (defense in depth):
959 - Wipe more data from connection address fields before returning
960 them to the memory heap. Closes ticket 6198.
962 o Minor features (denial-of-service memory limiter):
963 - Allow the user to configure even lower values for the
964 MaxMemInQueues parameter. Relays now enforce a minimum of 64 MB,
965 when previously the minimum was 256 MB. On clients, there is no
966 minimum. Relays and clients will both warn if the value is set so
967 low that Tor is likely to stop working. Closes ticket 24308.
969 o Minor features (developer tooling):
970 - Add a script to help check the alphabetical ordering of option
971 names in the manual page. Closes ticket 33339.
972 - Refrain from listing all .a files that are generated by the Tor
973 build in .gitignore. Add a single wildcard *.a entry that covers
974 all of them for present and future. Closes ticket 33642.
975 - Add a script ("git-install-tools.sh") to install git hooks and
976 helper scripts. Closes ticket 33451.
978 o Minor features (directory authority):
979 - Authorities now recommend the protocol versions that are supported
980 by Tor 0.3.5 and later. (Earlier versions of Tor have been
981 deprecated since January of this year.) This recommendation will
982 cause older clients and relays to give a warning on startup, or
983 when they download a consensus directory. Closes ticket 32696.
985 o Minor features (directory authority, shared random):
986 - Refactor more authority-only parts of the shared-random scheduling
987 code to reside in the dirauth module, and to be disabled when
988 compiling with --disable-module-dirauth. Closes ticket 33436.
990 o Minor features (directory):
991 - Remember the number of bytes we have downloaded for each directory
992 purpose while bootstrapping, and while fully bootstrapped. Log
993 this information as part of the heartbeat message. Closes
996 o Minor features (entry guards):
997 - Reinstate support for GUARD NEW/UP/DOWN control port events.
1000 o Minor features (IPv6 support):
1001 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
1002 changes and tor_addr_is_null(). Closes ticket 33679. Patch
1004 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
1005 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
1006 Closes ticket 33901.
1008 o Minor features (linux seccomp2 sandbox, portability):
1009 - Allow Tor to build on platforms where it doesn't know how to
1010 report which syscall caused the linux seccomp2 sandbox to fail.
1011 This change should make the sandbox code more portable to less
1012 common Linux architectures. Closes ticket 34382.
1013 - Permit the unlinkat() syscall, which some Libc implementations use
1014 to implement unlink(). Closes ticket 33346.
1016 o Minor features (logging):
1017 - When trying to find our own address, add debug-level logging to
1018 report the sources of candidate addresses. Closes ticket 32888.
1020 o Minor features (onion service client, SOCKS5):
1021 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
1022 new type of onion service connection failures. The semantics of
1023 these error codes are documented in proposal 309. Closes
1026 o Minor features (onion service v3):
1027 - If a service cannot upload its descriptor(s), log why at INFO
1028 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
1030 o Minor features (python scripts):
1031 - Stop assuming that /usr/bin/python exists. Instead of using a
1032 hardcoded path in scripts that still use Python 2, use
1033 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
1034 bug 33192; bugfix on 0.4.2.
1036 o Minor features (testing, architecture):
1037 - Our test scripts now double-check that subsystem initialization
1038 order is consistent with the inter-module dependencies established
1039 by our .may_include files. Implements ticket 31634.
1040 - Initialize all subsystems at the beginning of our unit test
1041 harness, to avoid crashes due to uninitialized subsystems. Follow-
1042 up from ticket 33316.
1043 - Our "make check" target now runs the unit tests in 8 parallel
1044 chunks. Doing this speeds up hardened CI builds by more than a
1045 factor of two. Closes ticket 40098.
1047 o Minor features (v3 onion services):
1048 - Add v3 onion service status to the dumpstats() call which is
1049 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
1050 services. Closes ticket 24844. Patch by Neel Chauhan.
1052 o Minor features (windows):
1053 - Add support for console control signals like Ctrl+C in Windows.
1054 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
1056 o Minor bugfixes (control port, onion service):
1057 - Consistently use 'address' in "Invalid v3 address" response to
1058 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
1059 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
1061 o Minor bugfixes (correctness, buffers):
1062 - Fix a correctness bug that could cause an assertion failure if we
1063 ever tried using the buf_move_all() function with an empty input
1064 buffer. As far as we know, no released versions of Tor do this.
1065 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
1067 o Minor bugfixes (directory authorities):
1068 - Directory authorities now reject votes that arrive too late. In
1069 particular, once an authority has started fetching missing votes,
1070 it no longer accepts new votes posted by other authorities. This
1071 change helps prevent a consensus split, where only some authorities
1072 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
1074 o Minor bugfixes (git scripts):
1075 - Stop executing the checked-out pre-commit hook from the pre-push
1076 hook. Instead, execute the copy in the user's git directory. Fixes
1077 bug 33284; bugfix on 0.4.1.1-alpha.
1079 o Minor bugfixes (initialization):
1080 - Initialize the subsystems in our code in an order more closely
1081 corresponding to their dependencies, so that every system is
1082 initialized before the ones that (theoretically) depend on it.
1083 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
1085 o Minor bugfixes (IPv4, relay):
1086 - Check for invalid zero IPv4 addresses and ports when sending and
1087 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
1089 o Minor bugfixes (IPv6, relay):
1090 - Consider IPv6 addresses when checking if a connection is
1091 canonical. In 17604, relays assumed that a remote relay could
1092 consider an IPv6 connection canonical, but did not set the
1093 canonical flag on their side of the connection. Fixes bug 33899;
1094 bugfix on 0.3.1.1-alpha.
1095 - Log IPv6 addresses on connections where this relay is the
1096 responder. Previously, responding relays would replace the remote
1097 IPv6 address with the IPv4 address from the consensus. Fixes bug
1098 33899; bugfix on 0.3.1.1-alpha.
1100 o Minor bugfixes (linux seccomp2 sandbox):
1101 - Fix a regression on sandboxing rules for the openat() syscall. The
1102 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
1103 but broke with versions of glibc. We now choose a rule based on
1104 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
1106 - Makes the seccomp sandbox allow the correct syscall for opendir
1107 according to the running glibc version. This fixes crashes when
1108 reloading torrc with sandbox enabled when running on glibc 2.15 to
1109 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
1112 o Minor bugfixes (logging, testing):
1113 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
1114 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
1115 used to log a non-fatal warning, regardless of the debugging
1116 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
1117 - Remove surprising empty line in the INFO-level log about circuit
1118 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
1120 o Minor bugfixes (mainloop):
1121 - Better guard against growing a buffer past its maximum 2GB in
1122 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
1124 o Minor bugfixes (onion service v3 client):
1125 - Remove a BUG() warning that could occur naturally. Fixes bug
1126 34087; bugfix on 0.3.2.1-alpha.
1128 o Minor bugfixes (onion service, logging):
1129 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
1130 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
1132 o Minor bugfixes (onion services v3):
1133 - Avoid a non-fatal assertion failure in certain edge-cases when
1134 opening an intro circuit as a client. Fixes bug 34084; bugfix
1137 o Minor bugfixes (protocol versions):
1138 - Sort tor's supported protocol version lists, as recommended by the
1139 tor directory specification. Fixes bug 33285; bugfix
1142 o Minor bugfixes (rate limiting, bridges, pluggable transports):
1143 - On a bridge, treat all connections from an ExtORPort as remote by
1144 default for the purposes of rate-limiting. Previously, bridges
1145 would treat the connection as local unless they explicitly
1146 received a "USERADDR" command. ExtORPort connections still count
1147 as local if there is a USERADDR command with an explicit local
1148 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
1150 o Minor bugfixes (refactoring):
1151 - Lift circuit_build_times_disabled() out of the
1152 circuit_expire_building() loop, to save CPU time when there are
1153 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
1155 o Minor bugfixes (relay, self-testing):
1156 - When starting up as a relay, if we haven't been able to verify
1157 that we're reachable, only launch reachability tests at most once
1158 a minute. Previously, we had been launching tests up to once a
1159 second, which was needlessly noisy. Fixes bug 40083; bugfix
1162 o Minor bugfixes (relay, usability):
1163 - Adjust the rules for when to warn about having too many
1164 connections to other relays. Previously we'd tolerate up to 1.5
1165 connections per relay on average. Now we tolerate more connections
1166 for directory authorities, and raise the number of total
1167 connections we need to see before we warn. Fixes bug 33880; bugfix
1170 o Minor bugfixes (SOCKS, onion service client):
1171 - Detect v3 onion service addresses of the wrong length when
1172 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
1175 o Minor bugfixes (tests):
1176 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
1177 on its own. Previously, it would exit with an error. Fixes bug
1178 40099; bugfix on 0.2.8.1-alpha.
1180 o Minor bugfixes (v3 onion services):
1181 - Remove a BUG() warning that could trigger in certain unlikely
1182 edge-cases. Fixes bug 34086; bugfix on 0.3.2.1-alpha.
1183 - Remove a BUG() that was causing a stacktrace when a descriptor
1184 changed at an unexpected time. Fixes bug 28992; bugfix
1187 o Minor bugfixes (windows):
1188 - Fix a bug that prevented Tor from starting if its log file grew
1189 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
1191 o Code simplification and refactoring:
1192 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
1193 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
1194 brackets, separating colon, and port number. Closes ticket 33956.
1195 Patch by Neel Chauhan.
1196 - Merge the orconn and ocirc events into the "core" subsystem, which
1197 manages or connections and origin circuits. Previously they were
1198 isolated in subsystems of their own.
1199 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
1200 inversion. Closes ticket 33633.
1201 - Move the circuit extend code to the relay module. Split the
1202 circuit extend function into smaller functions. Closes
1204 - Rewrite port_parse_config() to use the default port flags from
1205 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
1206 - Updated comments in 'scheduler.c' to reflect old code changes, and
1207 simplified the scheduler channel state change code. Closes
1209 - Refactor configuration parsing to use the new config subsystem
1210 code. Closes ticket 33014.
1211 - Move a series of functions related to address resolving into their
1212 own files. Closes ticket 33789.
1215 - Replace most http:// URLs in our code and documentation with
1216 https:// URLs. (We have left unchanged the code in src/ext/, and
1217 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
1218 - Document the limitations of using %include on config files with
1219 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
1220 0.3.1.1-alpha. Patch by Daniel Pinto.
1223 - Our "check-local" test target no longer tries to use the
1224 Coccinelle semantic patching tool parse all the C files. While it
1225 is a good idea to try to make sure Coccinelle works on our C
1226 before we run a Coccinelle patch, doing so on every test run has
1227 proven to be disruptive. You can still run this tool manually with
1228 "make check-cocci". Closes ticket 40030.
1229 - Remove the ClientAutoIPv6ORPort option. This option attempted to
1230 randomly choose between IPv4 and IPv6 for client connections, and
1231 wasn't a true implementation of Happy Eyeballs. Often, this option
1232 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
1233 Patch by Neel Chauhan.
1234 - Stop shipping contrib/dist/rc.subr file, as it is not being used
1235 on FreeBSD anymore. Closes issue 31576.
1238 - Add a basic IPv6 test to "make test-network". This test only runs
1239 when the local machine has an IPv6 stack. Closes ticket 33300.
1240 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
1241 These jobs run the IPv4-only and dual-stack chutney flavours from
1242 test-network-all. Closes ticket 33280.
1243 - Remove a redundant distcheck job. Closes ticket 33194.
1244 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
1245 chutney job. This job runs on macOS, so it's a bit slow. Closes
1247 - Sort the Travis jobs in order of speed. Putting the slowest jobs
1248 first takes full advantage of Travis job concurrency. Closes
1250 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1251 previously configured to fast_finish (which requires
1252 allow_failure), to speed up the build. Closes ticket 33195.
1253 - Test v3 onion services to tor's mixed IPv4 chutney network. And
1254 add a mixed IPv6 chutney network. These networks are used in the
1255 test-network-all, test-network-ipv4, and test-network-ipv6 make
1256 targets. Closes ticket 33334.
1257 - Use the "bridges+hs-v23" chutney network flavour in "make test-
1258 network". This test requires a recent version of chutney (mid-
1259 February 2020). Closes ticket 28208.
1260 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1261 tool to produce detailed diagnostic output. Closes ticket 32792.
1263 o Deprecated features (onion service v2):
1264 - Add a deprecation warning for version 2 onion services. Closes
1267 o Documentation (manual page):
1268 - Add cross reference links and a table of contents to the HTML tor
1269 manual page. Closes ticket 33369. Work by Swati Thacker as part of
1270 Google Season of Docs.
1271 - Alphabetize the Denial of Service Mitigation Options, Directory
1272 Authority Server Options, Hidden Service Options, and Testing
1273 Network Options sections of the tor(1) manual page. Closes ticket
1274 33275. Work by Swati Thacker as part of Google Season of Docs.
1275 - Refrain from mentioning nicknames in manpage section for MyFamily
1276 torrc option. Resolves issue 33417.
1277 - Updated the options set by TestingTorNetwork in the manual page.
1278 Closes ticket 33778.
1281 Changes in version 0.3.5.11 - 2020-07-09
1282 Tor 0.3.5.11 backports fixes from later tor releases, including several
1283 usability, portability, and reliability fixes.
1285 This release also fixes TROVE-2020-001, a medium-severity denial of
1286 service vulnerability affecting all versions of Tor when compiled with
1287 the NSS encryption library. (This is not the default configuration.)
1288 Using this vulnerability, an attacker could cause an affected Tor
1289 instance to crash remotely. This issue is also tracked as CVE-2020-
1290 15572. Anybody running a version of Tor built with the NSS library
1291 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1294 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1295 - Fix a crash due to an out-of-bound memory access when Tor is
1296 compiled with NSS support. Fixes bug 33119; bugfix on
1297 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1300 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1301 - Fix a bug that was preventing DoS defenses from running on bridges
1302 with a pluggable transport. Previously, the DoS subsystem was not
1303 given the transport name of the client connection, thus failed to
1304 find the GeoIP cache entry for that client address. Fixes bug
1305 33491; bugfix on 0.3.3.2-alpha.
1307 o Minor features (testing, backport from 0.4.3.4-rc):
1308 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1309 variable to specify a list of space-separated test cases that
1310 should not be executed. We will use this to disable certain tests
1311 that are failing on Appveyor because of mismatched OpenSSL
1312 libraries. Part of ticket 33643.
1314 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1315 - Use the correct 64-bit printf format when compiling with MINGW on
1316 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1318 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1319 - Warn if the ContactInfo field is not set, and tell the relay
1320 operator that not having a ContactInfo field set might cause their
1321 relay to get rejected in the future. Fixes bug 33361; bugfix
1324 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1325 - Resume use of preemptively-built circuits when UseEntryGuards is set
1326 to 0. We accidentally disabled this feature with that config
1327 setting, leading to slower load times. Fixes bug 34303; bugfix
1330 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1331 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1332 style "/* falls through */" comments. Both Clang and GCC allow
1333 __attribute__((fallthrough)) instead, so that's what we're using
1334 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1336 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1337 - Fix a compiler warning on platforms with 32-bit time_t values.
1338 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1340 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1341 - When starting Tor any time after the first time in a process,
1342 register the thread in which it is running as the main thread.
1343 Previously, we only did this on Windows, which could lead to bugs
1344 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1347 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1348 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1349 if we are not running on Windows. Previously, non-Windows hosts
1350 would reject these line-endings in certain positions, making
1351 certain key files hard to move from one host to another. Fixes bug
1352 33032; bugfix on 0.3.5.1-alpha.
1354 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1355 - Downgrade a noisy log message that could occur naturally when
1356 receiving an extrainfo document that we no longer want. Fixes bug
1357 16016; bugfix on 0.2.6.3-alpha.
1359 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1360 - Remove a BUG() warning that would cause a stack trace if an onion
1361 service descriptor was freed while we were waiting for a
1362 rendezvous circuit to complete. Fixes bug 28992; bugfix
1365 o Testing (CI, backport from 0.4.3.4-rc):
1366 - In our Appveyor Windows CI, copy required DLLs to test and app
1367 directories, before running tor's tests. This ensures that tor.exe
1368 and test*.exe use the correct version of each DLL. This fix is not
1369 required, but we hope it will avoid DLL search issues in future.
1370 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1371 - On Appveyor, skip the crypto/openssl_version test, which is
1372 failing because of a mismatched library installation. Fix
1376 Changes in version 0.4.2.8 - 2020-07-09
1377 Tor 0.4.2.8 backports various fixes from later releases, including
1378 several that affect usability and portability.
1380 This release also fixes TROVE-2020-001, a medium-severity denial of
1381 service vulnerability affecting all versions of Tor when compiled with
1382 the NSS encryption library. (This is not the default configuration.)
1383 Using this vulnerability, an attacker could cause an affected Tor
1384 instance to crash remotely. This issue is also tracked as CVE-2020-
1385 15572. Anybody running a version of Tor built with the NSS library
1386 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1389 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1390 - Fix a crash due to an out-of-bound memory access when Tor is
1391 compiled with NSS support. Fixes bug 33119; bugfix on
1392 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1395 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1396 - Fix a bug that was preventing DoS defenses from running on bridges
1397 with a pluggable transport. Previously, the DoS subsystem was not
1398 given the transport name of the client connection, thus failed to
1399 find the GeoIP cache entry for that client address. Fixes bug
1400 33491; bugfix on 0.3.3.2-alpha.
1402 o Minor feature (sendme, flow control, backport form 0.4.3.4-rc):
1403 - Default to sending SENDME version 1 cells. (Clients are already
1404 sending these, because of a consensus parameter telling them to do
1405 so: this change only affects what clients would do if the
1406 consensus didn't contain a recommendation.) Closes ticket 33623.
1408 o Minor features (diagnostic, backport from 0.4.3.3-alpha):
1409 - Improve assertions and add some memory-poisoning code to try to
1410 track down possible causes of a rare crash (32564) in the EWMA
1411 code. Closes ticket 33290.
1413 o Minor features (testing, backport from 0.4.3.4-rc):
1414 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1415 variable to specify a list of space-separated test cases that
1416 should not be executed. We will use this to disable certain tests
1417 that are failing on Appveyor because of mismatched OpenSSL
1418 libraries. Part of ticket 33643.
1420 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1421 - Use the correct 64-bit printf format when compiling with MINGW on
1422 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1424 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1425 - Warn if the ContactInfo field is not set, and tell the relay
1426 operator that not having a ContactInfo field set might cause their
1427 relay to get rejected in the future. Fixes bug 33361; bugfix
1430 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1431 - Resume use of preemptively-built circuits when UseEntryGuards is set
1432 to 0. We accidentally disabled this feature with that config
1433 setting, leading to slower load times. Fixes bug 34303; bugfix
1436 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1437 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1438 style "/* falls through */" comments. Both Clang and GCC allow
1439 __attribute__((fallthrough)) instead, so that's what we're using
1440 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1441 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
1444 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1445 - Fix a compiler warning on platforms with 32-bit time_t values.
1446 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1448 o Minor bugfixes (controller protocol, backport from 0.4.3.2-alpha):
1449 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
1450 report them as SIGNAL events. Previously we would log a bug
1451 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
1453 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1454 - When starting Tor any time after the first time in a process,
1455 register the thread in which it is running as the main thread.
1456 Previously, we only did this on Windows, which could lead to bugs
1457 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1460 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1461 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1462 if we are not running on Windows. Previously, non-Windows hosts
1463 would reject these line-endings in certain positions, making
1464 certain key files hard to move from one host to another. Fixes bug
1465 33032; bugfix on 0.3.5.1-alpha.
1467 o Minor bugfixes (logging, backport from 0.4.3.2-rc):
1468 - When logging a bug, do not say "Future instances of this warning
1469 will be silenced" unless we are actually going to silence them.
1470 Previously we would say this whenever a BUG() check failed in the
1471 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
1473 o Minor bugfixes (logging, backport from 0.4.3.4-rc):
1474 - Flush stderr, stdout, and file logs during shutdown, if supported
1475 by the OS. This change helps make sure that any final logs are
1476 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1478 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1479 - Downgrade a noisy log message that could occur naturally when
1480 receiving an extrainfo document that we no longer want. Fixes bug
1481 16016; bugfix on 0.2.6.3-alpha.
1483 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1484 - Remove a BUG() warning that would cause a stack trace if an onion
1485 service descriptor was freed while we were waiting for a
1486 rendezvous circuit to complete. Fixes bug 28992; bugfix
1489 o Testing (CI, backport from 0.4.3.4-rc):
1490 - In our Appveyor Windows CI, copy required DLLs to test and app
1491 directories, before running tor's tests. This ensures that tor.exe
1492 and test*.exe use the correct version of each DLL. This fix is not
1493 required, but we hope it will avoid DLL search issues in future.
1494 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1495 - On Appveyor, skip the crypto/openssl_version test, which is
1496 failing because of a mismatched library installation. Fix
1500 Changes in version 0.4.3.6 - 2020-07-09
1501 Tor 0.4.3.6 backports several bugfixes from later releases, including
1502 some affecting usability.
1504 This release also fixes TROVE-2020-001, a medium-severity denial of
1505 service vulnerability affecting all versions of Tor when compiled with
1506 the NSS encryption library. (This is not the default configuration.)
1507 Using this vulnerability, an attacker could cause an affected Tor
1508 instance to crash remotely. This issue is also tracked as CVE-2020-
1509 15572. Anybody running a version of Tor built with the NSS library
1510 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1513 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1514 - Fix a crash due to an out-of-bound memory access when Tor is
1515 compiled with NSS support. Fixes bug 33119; bugfix on
1516 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1519 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1520 - Use the correct 64-bit printf format when compiling with MINGW on
1521 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1523 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1524 - Resume use of preemptively-built circuits when UseEntryGuards is set
1525 to 0. We accidentally disabled this feature with that config
1526 setting, leading to slower load times. Fixes bug 34303; bugfix
1529 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1530 - Fix a compiler warning on platforms with 32-bit time_t values.
1531 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1533 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
1534 - Fix a startup crash when tor is compiled with --enable-nss and
1535 sandbox support is enabled. Fixes bug 34130; bugfix on
1536 0.3.5.1-alpha. Patch by Daniel Pinto.
1538 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1539 - Downgrade a noisy log message that could occur naturally when
1540 receiving an extrainfo document that we no longer want. Fixes bug
1541 16016; bugfix on 0.2.6.3-alpha.
1543 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
1544 - Update the man page to reflect that MinUptimeHidServDirectoryV2
1545 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
1547 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
1548 - Prevent an assert() that would occur when cleaning the client
1549 descriptor cache, and attempting to close circuits for a non-
1550 decrypted descriptor (lacking client authorization). Fixes bug
1551 33458; bugfix on 0.4.2.1-alpha.
1553 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
1554 - Fix a portability error in the configure script, where we were
1555 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
1557 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
1558 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
1559 descriptors, when the IPv6 port was configured as "auto". Fixes
1560 bug 32588; bugfix on 0.2.3.9-alpha.
1562 o Documentation (backport from 0.4.4.1-alpha):
1563 - Fix several doxygen warnings related to imbalanced groups. Closes
1567 Changes in version 0.4.3.5 - 2020-05-15
1568 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
1569 series adds support for building without relay code enabled, and
1570 implements functionality needed for OnionBalance with v3 onion
1571 services. It includes significant refactoring of our configuration and
1572 controller functionality, and fixes numerous smaller bugs and
1575 Per our support policy, we support each stable release series for nine
1576 months after its first stable release, or three months after the first
1577 stable release of the next series: whichever is longer. This means
1578 that 0.4.3.x will be supported until around February 2021--later, if
1579 0.4.4.x is later than anticipated.
1581 Note also that support for 0.4.1.x is about to end on May 20 of this
1582 year; 0.4.2.x will be supported until September 15. We still plan to
1583 continue supporting 0.3.5.x, our long-term stable series, until
1586 Below are the changes since 0.4.2.6. For a list of only the changes
1587 since 0.4.3.4-rc, see the ChangeLog file.
1589 o New system requirements:
1590 - When building Tor, you now need to have Python 3 in order to run
1591 the integration tests. (Python 2 is officially unsupported
1592 upstream, as of 1 Jan 2020.) Closes ticket 32608.
1594 o Major features (build system):
1595 - The relay code can now be disabled using the --disable-module-relay
1596 configure option. When this option is set, we also disable the
1597 dirauth module. Closes ticket 32123.
1598 - When Tor is compiled --disable-module-relay, we also omit the code
1599 used to act as a directory cache. Closes ticket 32487.
1601 o Major features (directory authority, ed25519):
1602 - Add support for banning a relay's ed25519 keys in the approved-
1603 routers file. This will help us migrate away from RSA keys in the
1604 future. Previously, only RSA keys could be banned in approved-
1605 routers. Resolves ticket 22029. Patch by Neel Chauhan.
1607 o Major features (onion services):
1608 - New control port commands to manage client-side onion service
1609 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
1610 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
1611 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
1612 - Introduce a new SocksPort flag, ExtendedErrors, to support more
1613 detailed error codes in information for applications that support
1614 them. Closes ticket 30382; implements proposal 304.
1616 o Major features (proxy):
1617 - In addition to its current supported proxy types (HTTP CONNECT,
1618 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
1619 HAProxy server. A new torrc option was added to specify the
1620 address/port of the server: TCPProxy <protocol> <host>:<port>.
1621 Currently the only supported protocol for the option is haproxy.
1622 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
1624 o Major bugfixes (security, denial-of-service):
1625 - Fix a denial-of-service bug that could be used by anyone to
1626 consume a bunch of CPU on any Tor relay or authority, or by
1627 directories to consume a bunch of CPU on clients or hidden
1628 services. Because of the potential for CPU consumption to
1629 introduce observable timing patterns, we are treating this as a
1630 high-severity security issue. Fixes bug 33119; bugfix on
1631 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1632 as TROVE-2020-002 and CVE-2020-10592.
1634 o Major bugfixes (circuit padding, memory leak):
1635 - Avoid a remotely triggered memory leak in the case that a circuit
1636 padding machine is somehow negotiated twice on the same circuit.
1637 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1638 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1640 o Major bugfixes (directory authority):
1641 - Directory authorities will now send a 503 (not enough bandwidth)
1642 code to clients when under bandwidth pressure. Known relays and
1643 other authorities will always be answered regardless of the
1644 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
1646 o Major bugfixes (DoS defenses, bridges, pluggable transport):
1647 - Fix a bug that was preventing DoS defenses from running on bridges
1648 with a pluggable transport. Previously, the DoS subsystem was not
1649 given the transport name of the client connection, thus failed to
1650 find the GeoIP cache entry for that client address. Fixes bug
1651 33491; bugfix on 0.3.3.2-alpha.
1653 o Major bugfixes (networking):
1654 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
1655 and accept strings as well as binary addresses. Fixes bug 32315;
1656 bugfix on 0.3.5.1-alpha.
1658 o Major bugfixes (onion service):
1659 - Report HS circuit failure back into the HS subsystem so we take
1660 appropriate action with regards to the client introduction point
1661 failure cache. This improves reachability of onion services, since
1662 now clients notice failing introduction circuits properly. Fixes
1663 bug 32020; bugfix on 0.3.2.1-alpha.
1665 o Minor feature (heartbeat, onion service):
1666 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
1667 message. Closes ticket 31371.
1669 o Minor feature (sendme, flow control):
1670 - Default to sending SENDME version 1 cells. (Clients are already
1671 sending these, because of a consensus parameter telling them to do
1672 so: this change only affects what clients would do if the
1673 consensus didn't contain a recommendation.) Closes ticket 33623.
1675 o Minor features (best practices tracker):
1676 - Practracker now supports a --regen-overbroad option to regenerate
1677 the exceptions file, but only to revise exceptions to be _less_
1678 tolerant of best-practices violations. Closes ticket 32372.
1680 o Minor features (configuration validation):
1681 - Configuration validation can now be done by per-module callbacks,
1682 rather than a global validation function. This will let us reduce
1683 the size of config.c and some of its more cumbersome functions.
1684 Closes ticket 31241.
1686 o Minor features (configuration):
1687 - If a configured hardware crypto accelerator in AccelName is
1688 prefixed with "!", Tor now exits when it cannot be found. Closes
1690 - We now use flag-driven logic to warn about obsolete configuration
1691 fields, so that we can include their names. In 0.4.2, we used a
1692 special type, which prevented us from generating good warnings.
1693 Implements ticket 32404.
1695 o Minor features (configure, build system):
1696 - Output a list of enabled/disabled features at the end of the
1697 configure process in a pleasing way. Closes ticket 31373.
1699 o Minor features (continuous integration):
1700 - Run Doxygen Makefile target on Travis, so we can learn about
1701 regressions in our internal documentation. Closes ticket 32455.
1702 - Stop allowing failures on the Travis CI stem tests job. It looks
1703 like all the stem hangs we were seeing before are now fixed.
1704 Closes ticket 33075.
1706 o Minor features (controller):
1707 - Add stream isolation data to STREAM event. Closes ticket 19859.
1708 - Implement a new GETINFO command to fetch microdescriptor
1709 consensus. Closes ticket 31684.
1711 o Minor features (debugging, directory system):
1712 - Don't crash when we find a non-guard with a guard-fraction value
1713 set. Instead, log a bug warning, in an attempt to figure out how
1714 this happened. Diagnostic for ticket 32868.
1716 o Minor features (defense in depth):
1717 - Add additional checks around tor_vasprintf() usage, in case the
1718 function returns an error. Patch by Tobias Stoeckmann. Fixes
1721 o Minor features (developer tools):
1722 - Remove the 0.2.9.x series branches from git scripts (git-merge-
1723 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
1724 Closes ticket 32772.
1725 - Add a check_cocci_parse.sh script that checks that new code is
1726 parseable by Coccinelle. Add an exceptions file for unparseable
1727 files, and run the script from travis CI. Closes ticket 31919.
1728 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
1729 target. Closes ticket 31919.
1730 - Add a rename_c_identifiers.py tool to rename a bunch of C
1731 identifiers at once, and generate a well-formed commit message
1732 describing the change. This should help with refactoring. Closes
1734 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
1735 semantic patching tool with the correct flags. These flags are
1736 fairly easy to forget, and these scripts should help us use
1737 Coccinelle more effectively in the future. Closes ticket 31705.
1739 o Minor features (diagnostic):
1740 - Improve assertions and add some memory-poisoning code to try to
1741 track down possible causes of a rare crash (32564) in the EWMA
1742 code. Closes ticket 33290.
1744 o Minor features (directory authorities):
1745 - Directory authorities now reject descriptors from relays running
1746 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
1747 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
1749 o Minor features (Doxygen):
1750 - Update Doxygen configuration file to a more recent template (from
1751 1.8.15). Closes ticket 32110.
1752 - "make doxygen" now works with out-of-tree builds. Closes
1754 - Make sure that doxygen outputs documentation for all of our C
1755 files. Previously, some were missing @file declarations, causing
1756 them to be ignored. Closes ticket 32307.
1757 - Our "make doxygen" target now respects --enable-fatal-warnings by
1758 default, and does not warn about items that are missing
1759 documentation. To warn about missing documentation, run configure
1760 with the "--enable-missing-doc-warnings" flag: doing so suspends
1761 fatal warnings for doxygen. Closes ticket 32385.
1763 o Minor features (git scripts):
1764 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
1765 customisation. Closes ticket 32347.
1766 - Add git-setup-dirs.sh, which sets up an upstream git repository
1767 and worktrees for tor maintainers. Closes ticket 29603.
1768 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
1769 remote. Closes ticket 32347.
1770 - Call the check_cocci_parse.sh script from the git commit and push
1771 hooks. Closes ticket 31919.
1772 - Make git-push-all.sh skip unchanged branches when pushing to
1773 upstream. The script already skipped unchanged test branches.
1774 Closes ticket 32216.
1775 - Make git-setup-dirs.sh create a master symlink in the worktree
1776 directory. Closes ticket 32347.
1777 - Skip unmodified source files when doing some existing git hook
1778 checks. Related to ticket 31919.
1780 o Minor features (IPv6, client):
1781 - Make Tor clients tell dual-stack exits that they prefer IPv6
1782 connections. This change is equivalent to setting the PreferIPv6
1783 flag on SOCKSPorts (and most other listener ports). Tor Browser
1784 has been setting this flag for some time, and we want to remove a
1785 client distinguisher at exits. Closes ticket 32637.
1787 o Minor features (portability, android):
1788 - When building for Android, disable some tests that depend on $HOME
1789 and/or pwdb, which Android doesn't have. Closes ticket 32825.
1790 Patch from Hans-Christoph Steiner.
1792 o Minor features (relay modularity):
1793 - Split the relay and server pluggable transport config code into
1794 separate files in the relay module. Disable this code when the
1795 relay module is disabled. Closes part of ticket 32213.
1796 - When the relay module is disabled, reject attempts to set the
1797 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
1798 ServerTransport* options, rather than ignoring the values of these
1799 options. Closes part of ticket 32213.
1800 - When the relay module is disabled, change the default config so
1801 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
1803 o Minor features (release tools):
1804 - Port our ChangeLog formatting and sorting tools to Python 3.
1805 Closes ticket 32704.
1807 o Minor features (testing):
1808 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1809 variable to specify a list of space-separated test cases that
1810 should not be executed. We will use this to disable certain tests
1811 that are failing on Appveyor because of mismatched OpenSSL
1812 libraries. Part of ticket 33643.
1813 - Detect some common failure cases for test_parseconf.sh in
1814 src/test/conf_failures. Closes ticket 32451.
1815 - Allow test_parseconf.sh to test expected log outputs for successful
1816 configs, as well as failed configs. Closes ticket 32451.
1817 - The test_parseconf.sh script now supports result variants for any
1818 combination of the optional libraries lzma, nss, and zstd. Closes
1820 - When running the unit tests on Android, create temporary files in
1821 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
1822 patch from Hans-Christoph Steiner.
1824 o Minor features (usability):
1825 - Include more information when failing to parse a configuration
1826 value. This should make it easier to tell what's going wrong when
1827 a configuration file doesn't parse. Closes ticket 33460.
1829 o Minor bugfix (relay, configuration):
1830 - Warn if the ContactInfo field is not set, and tell the relay
1831 operator that not having a ContactInfo field set might cause their
1832 relay to get rejected in the future. Fixes bug 33361; bugfix
1835 o Minor bugfixes (bridges):
1836 - Lowercase the configured value of BridgeDistribution before adding
1837 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1839 o Minor bugfixes (build system):
1840 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
1841 bugfix on 0.4.1.2-alpha.
1843 o Minor bugfixes (compiler compatibility):
1844 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1845 style "/* falls through */" comments. Both Clang and GCC allow
1846 __attribute__((fallthrough)) instead, so that's what we're using
1847 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1848 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
1851 o Minor bugfixes (configuration handling):
1852 - Make control_event_conf_changed() take in a config_line_t instead
1853 of a smartlist of alternating key/value entries. Fixes bug 31531;
1854 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
1855 - Check for multiplication overflow when parsing memory units inside
1856 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
1857 - When dumping the configuration, stop adding a trailing space after
1858 the option name when there is no option value. This issue only
1859 affects options that accept an empty value or list. (Most options
1860 reject empty values, or delete the entire line from the dumped
1861 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
1862 - Avoid changing the user's value of HardwareAccel as stored by
1863 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
1864 bug 32382; bugfix on 0.2.2.1-alpha.
1865 - When creating a KeyDirectory with the same location as the
1866 DataDirectory (not recommended), respect the DataDirectory's
1867 group-readable setting if one has not been set for the
1868 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
1870 o Minor bugfixes (continuous integration):
1871 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
1874 o Minor bugfixes (controller protocol):
1875 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
1876 report them as SIGNAL events. Previously we would log a bug
1877 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
1879 o Minor bugfixes (controller):
1880 - In routerstatus_has_changed(), check all the fields that are
1881 output over the control port. Fixes bug 20218; bugfix
1884 o Minor bugfixes (developer tools):
1885 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
1886 31336; bugfix on 0.4.1.2-alpha.
1888 o Minor bugfixes (dirauth module):
1889 - Split the dirauth config code into a separate file in the dirauth
1890 module. Disable this code when the dirauth module is disabled.
1891 Closes ticket 32213.
1892 - When the dirauth module is disabled, reject attempts to set the
1893 AuthoritativeDir option, rather than ignoring the value of the
1894 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
1896 o Minor bugfixes (embedded Tor):
1897 - When starting Tor any time after the first time in a process,
1898 register the thread in which it is running as the main thread.
1899 Previously, we only did this on Windows, which could lead to bugs
1900 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1903 o Minor bugfixes (git scripts):
1904 - Avoid sleeping before the last push in git-push-all.sh. Closes
1906 - Forward all unrecognised arguments in git-push-all.sh to git push.
1907 Closes ticket 32216.
1909 o Minor bugfixes (key portability):
1910 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1911 if we are not running on Windows. Previously, non-Windows hosts
1912 would reject these line-endings in certain positions, making
1913 certain key files hard to move from one host to another. Fixes bug
1914 33032; bugfix on 0.3.5.1-alpha.
1916 o Minor bugfixes (logging):
1917 - Stop truncating IPv6 addresses and ports in channel and connection
1918 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
1919 - Flush stderr, stdout, and file logs during shutdown, if supported
1920 by the OS. This change helps make sure that any final logs are
1921 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1922 - Stop closing stderr and stdout during shutdown. Closing these file
1923 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
1925 - If we encounter a bug when flushing a buffer to a TLS connection,
1926 only log the bug once per invocation of the Tor process.
1927 Previously we would log with every occurrence, which could cause
1928 us to run out of disk space. Fixes bug 33093; bugfix
1930 - When logging a bug, do not say "Future instances of this warning
1931 will be silenced" unless we are actually going to silence them.
1932 Previously we would say this whenever a BUG() check failed in the
1933 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
1935 o Minor bugfixes (onion services v2):
1936 - Move a series of v2 onion service warnings to protocol-warning
1937 level because they can all be triggered remotely by a malformed
1938 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
1939 - When sending the INTRO cell for a v2 Onion Service, look at the
1940 failure cache alongside timeout values to check if the intro point
1941 is marked as failed. Previously, we only looked at the relay
1942 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
1945 o Minor bugfixes (onion services v3):
1946 - Remove a BUG() warning that would cause a stack trace if an onion
1947 service descriptor was freed while we were waiting for a
1948 rendezvous circuit to complete. Fixes bug 28992; bugfix
1950 - Relax severity of a log message that can appear naturally when
1951 decoding onion service descriptors as a relay. Also add some
1952 diagnostics to debug any future bugs in that area. Fixes bug
1953 31669; bugfix on 0.3.0.1-alpha.
1954 - Fix an assertion failure that could result from a corrupted
1955 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1956 bugfix on 0.3.3.1-alpha. This issue is also tracked
1958 - Properly handle the client rendezvous circuit timeout. Previously
1959 Tor would sometimes timeout a rendezvous circuit awaiting the
1960 introduction ACK, and find itself unable to re-establish all
1961 circuits because the rendezvous circuit timed out too early. Fixes
1962 bug 32021; bugfix on 0.3.2.1-alpha.
1964 o Minor bugfixes (onion services):
1965 - Do not rely on a "circuit established" flag for intro circuits but
1966 instead always query the HS circuit map. This is to avoid sync
1967 issue with that flag and the map. Fixes bug 32094; bugfix
1970 o Minor bugfixes (onion services, all):
1971 - In cancel_descriptor_fetches(), use
1972 connection_list_by_type_purpose() instead of
1973 connection_list_by_type_state(). Fixes bug 32639; bugfix on
1974 0.3.2.1-alpha. Patch by Neel Chauhan.
1976 o Minor bugfixes (pluggable transports):
1977 - When receiving a message on standard error from a pluggable
1978 transport, log it at info level, rather than as a warning. Fixes
1979 bug 33005; bugfix on 0.4.0.1-alpha.
1981 o Minor bugfixes (rust, build):
1982 - Fix a syntax warning given by newer versions of Rust that was
1983 creating problems for our continuous integration. Fixes bug 33212;
1984 bugfix on 0.3.5.1-alpha.
1986 o Minor bugfixes (scripts):
1987 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
1988 bugfix on 0.4.0.1-alpha.
1990 o Minor bugfixes (testing):
1991 - Use the same code to find the tor binary in all of our test
1992 scripts. This change makes sure we are always using the coverage
1993 binary when coverage is enabled. Fixes bug 32368; bugfix
1995 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
1996 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
1997 - Our option-validation tests no longer depend on specially
1998 configured non-default, non-passing sets of options. Previously,
1999 the tests had been written to assume that options would _not_ be
2000 set to their defaults, which led to needless complexity and
2001 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
2003 o Minor bugfixes (TLS bug handling):
2004 - When encountering a bug in buf_read_from_tls(), return a "MISC"
2005 error code rather than "WANTWRITE". This change might help avoid
2006 some CPU-wasting loops if the bug is ever triggered. Bug reported
2007 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
2009 o Deprecated features:
2010 - Deprecate the ClientAutoIPv6ORPort option. This option was not
2011 true "Happy Eyeballs", and often failed on connections that
2012 weren't reliably dual-stack. Closes ticket 32942. Patch by
2016 - Provide a quickstart guide for a Circuit Padding Framework, and
2017 documentation for researchers to implement and study circuit
2018 padding machines. Closes ticket 28804.
2019 - Add documentation in 'HelpfulTools.md' to describe how to build a
2020 tag file. Closes ticket 32779.
2021 - Create a high-level description of the long-term software
2022 architecture goals. Closes ticket 32206.
2023 - Describe the --dump-config command in the manual page. Closes
2025 - Unite coding advice from this_not_that.md in torguts repo into our
2026 coding standards document. Resolves ticket 31853.
2029 - Our Doxygen configuration no longer generates LaTeX output. The
2030 reference manual produced by doing this was over 4000 pages long,
2031 and generally unusable. Closes ticket 32099.
2032 - The option "TestingEstimatedDescriptorPropagationTime" is now
2033 marked as obsolete. It has had no effect since 0.3.0.7, when
2034 clients stopped rejecting consensuses "from the future". Closes
2036 - We no longer support consensus methods before method 28; these
2037 methods were only used by authorities running versions of Tor that
2038 are now at end-of-life. In effect, this means that clients,
2039 relays, and authorities now assume that authorities will be
2040 running version 0.3.5.x or later. Closes ticket 32695.
2043 - Avoid conflicts between the fake sockets in tor's unit tests, and
2044 real file descriptors. Resolves issues running unit tests with
2045 GitHub Actions, where the process that embeds or launches the
2046 tests has already opened a large number of file descriptors. Fixes
2047 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
2049 - Add more test cases for tor's UTF-8 validation function. Also,
2050 check the arguments passed to the function for consistency. Closes
2052 - Improve test coverage for relay and dirauth config code, focusing
2053 on option validation and normalization. Closes ticket 32213.
2054 - Improve the consistency of test_parseconf.sh output, and run all
2055 the tests, even if one fails. Closes ticket 32213.
2056 - Run the practracker unit tests in the pre-commit git hook. Closes
2059 o Code simplification and refactoring (channel):
2060 - Channel layer had a variable length cell handler that was not used
2061 and thus removed. Closes ticket 32892.
2063 o Code simplification and refactoring (configuration):
2064 - Immutability is now implemented as a flag on individual
2065 configuration options rather than as part of the option-transition
2066 checking code. Closes ticket 32344.
2067 - Instead of keeping a list of configuration options to check for
2068 relative paths, check all the options whose type is "FILENAME".
2069 Solves part of ticket 32339.
2070 - Our default log (which ordinarily sends NOTICE-level messages to
2071 standard output) is now handled in a more logical manner.
2072 Previously, we replaced the configured log options if they were
2073 empty. Now, we interpret an empty set of log options as meaning
2074 "use the default log". Closes ticket 31999.
2075 - Remove some unused arguments from the options_validate() function,
2076 to simplify our code and tests. Closes ticket 32187.
2077 - Simplify the options_validate() code so that it looks at the
2078 default options directly, rather than taking default options as an
2079 argument. This change lets us simplify its interface. Closes
2081 - Use our new configuration architecture to move most authority-
2082 related options to the directory authority module. Closes
2084 - When parsing the command line, handle options that determine our
2085 "quiet level" and our mode of operation (e.g., --dump-config and
2086 so on) all in one table. Closes ticket 32003.
2088 o Code simplification and refactoring (controller):
2089 - Create a new abstraction for formatting control protocol reply
2090 lines based on key-value pairs. Refactor some existing control
2091 protocol code to take advantage of this. Closes ticket 30984.
2092 - Create a helper function that can fetch network status or
2093 microdesc consensuses. Closes ticket 31684.
2095 o Code simplification and refactoring (dirauth modularization):
2096 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
2097 Closes ticket 32163.
2098 - Replace some confusing identifiers in process_descs.c. Closes
2100 - Simplify some relay and dirauth config code. Closes ticket 32213.
2102 o Code simplification and refactoring (mainloop):
2103 - Simplify the ip_address_changed() function by removing redundant
2104 checks. Closes ticket 33091.
2106 o Code simplification and refactoring (misc):
2107 - Make all the structs we declare follow the same naming convention
2108 of ending with "_t". Closes ticket 32415.
2109 - Move and rename some configuration-related code for clarity.
2110 Closes ticket 32304.
2111 - Our include.am files are now broken up by subdirectory.
2112 Previously, src/core/include.am covered all of the subdirectories
2113 in "core", "feature", and "app". Closes ticket 32137.
2114 - Remove underused NS*() macros from test code: they make our tests
2115 more confusing, especially for code-formatting tools. Closes
2118 o Code simplification and refactoring (relay modularization):
2119 - Disable relay_periodic when the relay module is disabled. Closes
2121 - Disable relay_sys when the relay module is disabled. Closes
2124 o Code simplification and refactoring (tool support):
2125 - Add numerous missing dependencies to our include files, so that
2126 they can be included in different reasonable orders and still
2127 compile. Addresses part of ticket 32764.
2128 - Fix some parts of our code that were difficult for Coccinelle to
2129 parse. Related to ticket 31705.
2130 - Fix some small issues in our code that prevented automatic
2131 formatting tools from working. Addresses part of ticket 32764.
2133 o Documentation (manpage):
2134 - Alphabetize the Server and Directory server sections of the tor
2135 manpage. Also split Statistics options into their own section of
2136 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
2137 Google Season of Docs.
2138 - Document the __OwningControllerProcess torrc option and specify
2139 its polling interval. Resolves issue 32971.
2140 - Split "Circuit Timeout" options and "Node Selection" options into
2141 their own sections of the tor manpage. Closes tickets 32928 and
2142 32929. Work by Swati Thacker as part of Google Season of Docs.
2143 - Alphabetize the Client Options section of the tor manpage. Closes
2145 - Alphabetize the General Options section of the tor manpage. Closes
2147 - In the tor(1) manpage, reword and improve formatting of the
2148 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
2149 32277. Based on work by Swati Thacker as part of Google Season
2151 - In the tor(1) manpage, reword and improve formatting of the FILES,
2152 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
2153 Swati Thacker as part of Google Season of Docs.
2155 o Testing (Appveyor CI):
2156 - In our Appveyor Windows CI, copy required DLLs to test and app
2157 directories, before running tor's tests. This ensures that tor.exe
2158 and test*.exe use the correct version of each DLL. This fix is not
2159 required, but we hope it will avoid DLL search issues in future.
2160 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
2161 - On Appveyor, skip the crypto/openssl_version test, which is
2162 failing because of a mismatched library installation. Fix
2165 o Testing (circuit, EWMA):
2166 - Add unit tests for circuitmux and EWMA subsystems. Closes
2169 o Testing (Travis CI):
2170 - Remove a redundant distcheck job. Closes ticket 33194.
2171 - Sort the Travis jobs in order of speed: putting the slowest jobs
2172 first takes full advantage of Travis job concurrency. Closes
2174 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2175 previously configured to fast_finish (which requires
2176 allow_failure), to speed up the build. Closes ticket 33195.
2177 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2178 tool to produce detailed diagnostic output. Closes ticket 32792.
2181 Changes in version 0.4.2.7 - 2020-03-18
2182 This is the third stable release in the 0.4.2.x series. It backports
2183 numerous fixes from later releases, including a fix for TROVE-2020-
2184 002, a major denial-of-service vulnerability that affected all
2185 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
2186 an attacker could cause Tor instances to consume a huge amount of CPU,
2187 disrupting their operations for several seconds or minutes. This
2188 attack could be launched by anybody against a relay, or by a directory
2189 cache against any client that had connected to it. The attacker could
2190 launch this attack as much as they wanted, thereby disrupting service
2191 or creating patterns that could aid in traffic analysis. This issue
2192 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
2194 We do not have reason to believe that this attack is currently being
2195 exploited in the wild, but nonetheless we advise everyone to upgrade
2196 as soon as packages are available.
2198 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2199 - Fix a denial-of-service bug that could be used by anyone to
2200 consume a bunch of CPU on any Tor relay or authority, or by
2201 directories to consume a bunch of CPU on clients or hidden
2202 services. Because of the potential for CPU consumption to
2203 introduce observable timing patterns, we are treating this as a
2204 high-severity security issue. Fixes bug 33119; bugfix on
2205 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2206 as TROVE-2020-002 and CVE-2020-10592.
2208 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
2209 - Avoid a remotely triggered memory leak in the case that a circuit
2210 padding machine is somehow negotiated twice on the same circuit.
2211 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2212 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2214 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
2215 - Directory authorities will now send a 503 (not enough bandwidth)
2216 code to clients when under bandwidth pressure. Known relays and
2217 other authorities will always be answered regardless of the
2218 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
2220 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2221 - Stop allowing failures on the Travis CI stem tests job. It looks
2222 like all the stem hangs we were seeing before are now fixed.
2223 Closes ticket 33075.
2225 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2226 - Lowercase the configured value of BridgeDistribution before adding
2227 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2229 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2230 - If we encounter a bug when flushing a buffer to a TLS connection,
2231 only log the bug once per invocation of the Tor process.
2232 Previously we would log with every occurrence, which could cause
2233 us to run out of disk space. Fixes bug 33093; bugfix
2236 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2237 - Fix an assertion failure that could result from a corrupted
2238 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2239 bugfix on 0.3.3.1-alpha. This issue is also tracked
2242 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2243 - Fix a syntax warning given by newer versions of Rust that was
2244 creating problems for our continuous integration. Fixes bug 33212;
2245 bugfix on 0.3.5.1-alpha.
2247 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2248 - Remove a redundant distcheck job. Closes ticket 33194.
2249 - Sort the Travis jobs in order of speed: putting the slowest jobs
2250 first takes full advantage of Travis job concurrency. Closes
2252 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2253 previously configured to fast_finish (which requires
2254 allow_failure), to speed up the build. Closes ticket 33195.
2255 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2256 tool to produce detailed diagnostic output. Closes ticket 32792.
2259 Changes in version 0.4.1.9 - 2020-03-18
2260 Tor 0.4.1.9 backports important fixes from later Tor releases,
2261 including a fix for TROVE-2020-002, a major denial-of-service
2262 vulnerability that affected all released Tor instances since
2263 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
2264 instances to consume a huge amount of CPU, disrupting their operations
2265 for several seconds or minutes. This attack could be launched by
2266 anybody against a relay, or by a directory cache against any client
2267 that had connected to it. The attacker could launch this attack as
2268 much as they wanted, thereby disrupting service or creating patterns
2269 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
2270 and is also tracked as CVE-2020-10592.
2272 We do not have reason to believe that this attack is currently being
2273 exploited in the wild, but nonetheless we advise everyone to upgrade
2274 as soon as packages are available.
2276 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2277 - Fix a denial-of-service bug that could be used by anyone to
2278 consume a bunch of CPU on any Tor relay or authority, or by
2279 directories to consume a bunch of CPU on clients or hidden
2280 services. Because of the potential for CPU consumption to
2281 introduce observable timing patterns, we are treating this as a
2282 high-severity security issue. Fixes bug 33119; bugfix on
2283 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2284 as TROVE-2020-002 and CVE-2020-10592.
2286 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
2287 - Avoid a remotely triggered memory leak in the case that a circuit
2288 padding machine is somehow negotiated twice on the same circuit.
2289 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2290 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2292 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2293 - Lowercase the configured value of BridgeDistribution before adding
2294 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2296 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2297 - If we encounter a bug when flushing a buffer to a TLS connection,
2298 only log the bug once per invocation of the Tor process.
2299 Previously we would log with every occurrence, which could cause
2300 us to run out of disk space. Fixes bug 33093; bugfix
2303 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2304 - Fix an assertion failure that could result from a corrupted
2305 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2306 bugfix on 0.3.3.1-alpha. This issue is also tracked
2309 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2310 - Fix a syntax warning given by newer versions of Rust that was
2311 creating problems for our continuous integration. Fixes bug 33212;
2312 bugfix on 0.3.5.1-alpha.
2314 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2315 - Remove a redundant distcheck job. Closes ticket 33194.
2316 - Sort the Travis jobs in order of speed: putting the slowest jobs
2317 first takes full advantage of Travis job concurrency. Closes
2319 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2320 previously configured to fast_finish (which requires
2321 allow_failure), to speed up the build. Closes ticket 33195.
2322 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2323 tool to produce detailed diagnostic output. Closes ticket 32792.
2326 Changes in version 0.3.5.10 - 2020-03-18
2327 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
2328 fix for TROVE-2020-002, a major denial-of-service vulnerability that
2329 affected all released Tor instances since 0.2.1.5-alpha. Using this
2330 vulnerability, an attacker could cause Tor instances to consume a huge
2331 amount of CPU, disrupting their operations for several seconds or
2332 minutes. This attack could be launched by anybody against a relay, or
2333 by a directory cache against any client that had connected to it. The
2334 attacker could launch this attack as much as they wanted, thereby
2335 disrupting service or creating patterns that could aid in traffic
2336 analysis. This issue was found by OSS-Fuzz, and is also tracked
2339 We do not have reason to believe that this attack is currently being
2340 exploited in the wild, but nonetheless we advise everyone to upgrade
2341 as soon as packages are available.
2343 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2344 - Fix a denial-of-service bug that could be used by anyone to
2345 consume a bunch of CPU on any Tor relay or authority, or by
2346 directories to consume a bunch of CPU on clients or hidden
2347 services. Because of the potential for CPU consumption to
2348 introduce observable timing patterns, we are treating this as a
2349 high-severity security issue. Fixes bug 33119; bugfix on
2350 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2351 as TROVE-2020-002 and CVE-2020-10592.
2353 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2354 - Correct how we use libseccomp. Particularly, stop assuming that
2355 rules are applied in a particular order or that more rules are
2356 processed after the first match. Neither is the case! In
2357 libseccomp <2.4.0 this lead to some rules having no effect.
2358 libseccomp 2.4.0 changed how rules are generated, leading to a
2359 different ordering, which in turn led to a fatal crash during
2360 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2363 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2364 - Stop allowing failures on the Travis CI stem tests job. It looks
2365 like all the stem hangs we were seeing before are now fixed.
2366 Closes ticket 33075.
2368 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2369 - Lowercase the configured value of BridgeDistribution before adding
2370 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2372 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
2373 - When running Tor with an option like --verify-config or
2374 --dump-config that does not start the event loop, avoid crashing
2375 if we try to exit early because of an error. Fixes bug 32407;
2376 bugfix on 0.3.3.1-alpha.
2378 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2379 - If we encounter a bug when flushing a buffer to a TLS connection,
2380 only log the bug once per invocation of the Tor process.
2381 Previously we would log with every occurrence, which could cause
2382 us to run out of disk space. Fixes bug 33093; bugfix
2385 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2386 - Fix an assertion failure that could result from a corrupted
2387 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2388 bugfix on 0.3.3.1-alpha. This issue is also tracked
2391 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2392 - Fix a syntax warning given by newer versions of Rust that was
2393 creating problems for our continuous integration. Fixes bug 33212;
2394 bugfix on 0.3.5.1-alpha.
2396 o Testing (backport from 0.4.3.1-alpha):
2397 - Re-enable the Travis CI macOS Chutney build, but don't let it
2398 prevent the Travis job from finishing. (The Travis macOS jobs are
2399 slow, so we don't want to have it delay the whole CI process.)
2400 Closes ticket 32629.
2401 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2402 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2403 fix the sandbox errors in 32722. Closes ticket 32240.
2405 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2406 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2408 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2409 - Remove a redundant distcheck job. Closes ticket 33194.
2410 - Sort the Travis jobs in order of speed: putting the slowest jobs
2411 first takes full advantage of Travis job concurrency. Closes
2413 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2414 previously configured to fast_finish (which requires
2415 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2416 tool to produce detailed diagnostic output. Closes ticket 32792.
2419 Changes in version 0.4.2.6 - 2020-01-30
2420 This is the second stable release in the 0.4.2.x series. It backports
2421 several bugfixes from 0.4.3.1-alpha, including some that had affected
2422 the Linux seccomp2 sandbox or Windows services. If you're running with
2423 one of those configurations, you'll probably want to upgrade;
2424 otherwise, you should be fine with 0.4.2.5.
2426 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2427 - Correct how we use libseccomp. Particularly, stop assuming that
2428 rules are applied in a particular order or that more rules are
2429 processed after the first match. Neither is the case! In
2430 libseccomp <2.4.0 this led to some rules having no effect.
2431 libseccomp 2.4.0 changed how rules are generated, leading to a
2432 different ordering, which in turn led to a fatal crash during
2433 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2435 - Fix crash when reloading logging configuration while the
2436 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2437 0.4.1.7. Patch by Peter Gerber.
2439 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
2440 - Use GCC/Clang's printf-checking feature to make sure that
2441 tor_assertf() arguments are correctly typed. Fixes bug 32765;
2442 bugfix on 0.4.1.1-alpha.
2444 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
2445 - Avoid a possible crash when trying to log a (fatal) assertion
2446 failure about mismatched magic numbers in configuration objects.
2447 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
2449 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
2450 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
2451 test_practracker.sh script. Doing so caused a test failure. Fixes
2452 bug 32705; bugfix on 0.4.2.1-alpha.
2453 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
2454 skipping practracker checks. Fixes bug 32705; bugfix
2457 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2458 - Initialize the publish/subscribe system when running as a windows
2459 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2461 o Testing (backport from 0.4.3.1-alpha):
2462 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2463 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2464 fix the sandbox errors in 32722. Closes ticket 32240.
2465 - Re-enable the Travis CI macOS Chutney build, but don't let it
2466 prevent the Travis job from finishing. (The Travis macOS jobs are
2467 slow, so we don't want to have it delay the whole CI process.)
2468 Closes ticket 32629.
2470 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2471 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2474 Changes in version 0.4.1.8 - 2020-01-30
2475 This release backports several bugfixes from later release series,
2476 including some that had affected the Linux seccomp2 sandbox or Windows
2477 services. If you're running with one of those configurations, you'll
2478 probably want to upgrade; otherwise, you should be fine with your
2479 current version of 0.4.1.x.
2481 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2482 - Correct how we use libseccomp. Particularly, stop assuming that
2483 rules are applied in a particular order or that more rules are
2484 processed after the first match. Neither is the case! In
2485 libseccomp <2.4.0 this led to some rules having no effect.
2486 libseccomp 2.4.0 changed how rules are generated, leading to a
2487 different ordering, which in turn led to a fatal crash during
2488 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2490 - Fix crash when reloading logging configuration while the
2491 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2492 0.4.1.7. Patch by Peter Gerber.
2494 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
2495 - When running Tor with an option like --verify-config or
2496 --dump-config that does not start the event loop, avoid crashing
2497 if we try to exit early because of an error. Fixes bug 32407;
2498 bugfix on 0.3.3.1-alpha.
2500 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2501 - Initialize the publish/subscribe system when running as a windows
2502 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2504 o Testing (backport from 0.4.3.1-alpha):
2505 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2506 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2507 fix the sandbox errors in 32722. Closes ticket 32240.
2508 - Re-enable the Travis CI macOS Chutney build, but don't let it
2509 prevent the Travis job from finishing. (The Travis macOS jobs are
2510 slow, so we don't want to have it delay the whole CI process.)
2511 Closes ticket 32629.
2513 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2514 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2517 Changes in version 0.4.2.5 - 2019-12-09
2518 This is the first stable release in the 0.4.2.x series. This series
2519 improves reliability and stability, and includes several stability and
2520 correctness improvements for onion services. It also fixes many smaller
2521 bugs present in previous series.
2523 Per our support policy, we will support the 0.4.2.x series for nine
2524 months, or until three months after the release of a stable 0.4.3.x:
2525 whichever is longer. If you need longer-term support, please stick
2526 with 0.3.5.x, which will we plan to support until Feb 2022.
2528 Below are the changes since 0.4.1.4-rc. For a complete list of only
2529 the changes since 0.4.2.4-rc, see the ChangeLog file.
2531 o Major features (directory authorities):
2532 - Directory authorities now reject relays running all currently
2533 deprecated release series. The currently supported release series
2534 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2536 o Major features (onion service v3, denial of service):
2537 - Add onion service introduction denial of service defenses. Intro
2538 points can now rate-limit client introduction requests, using
2539 parameters that can be sent by the service within the
2540 ESTABLISH_INTRO cell. If the cell extension for this is not used,
2541 the intro point will honor the consensus parameters. Closes
2544 o Major bugfixes (circuit build, guard):
2545 - When considering upgrading circuits from "waiting for guard" to
2546 "open", always ignore circuits that are marked for close.
2547 Previously we could end up in the situation where a subsystem is
2548 notified of a circuit opening, but the circuit is still marked for
2549 close, leading to undesirable behavior. Fixes bug 30871; bugfix
2552 o Major bugfixes (crash, Linux, Android):
2553 - Tolerate systems (including some Android installations) where
2554 madvise and MADV_DONTDUMP are available at build-time, but not at
2555 run time. Previously, these systems would notice a failed syscall
2556 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2557 - Tolerate systems (including some Linux installations) where
2558 madvise and/or MADV_DONTFORK are available at build-time, but not
2559 at run time. Previously, these systems would notice a failed
2560 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2562 o Major bugfixes (embedded Tor):
2563 - Avoid a possible crash when restarting Tor in embedded mode and
2564 enabling a different set of publish/subscribe messages. Fixes bug
2565 31898; bugfix on 0.4.1.1-alpha.
2567 o Major bugfixes (relay):
2568 - Relays now respect their AccountingMax bandwidth again. When
2569 relays entered "soft" hibernation (which typically starts when
2570 we've hit 90% of our AccountingMax), we had stopped checking
2571 whether we should enter hard hibernation. Soft hibernation refuses
2572 new connections and new circuits, but the existing circuits can
2573 continue, meaning that relays could have exceeded their configured
2574 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2576 o Major bugfixes (torrc parsing):
2577 - Stop ignoring torrc options after an %include directive, when the
2578 included directory ends with a file that does not contain any
2579 config options (but does contain comments or whitespace). Fixes
2580 bug 31408; bugfix on 0.3.1.1-alpha.
2582 o Major bugfixes (v3 onion services):
2583 - Onion services now always use the exact number of intro points
2584 configured with the HiddenServiceNumIntroductionPoints option (or
2585 fewer if nodes are excluded). Before, a service could sometimes
2586 pick more intro points than configured. Fixes bug 31548; bugfix
2589 o Minor feature (onion services, control port):
2590 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
2591 (v3) onion services. Previously it defaulted to RSA1024 (v2).
2592 Closes ticket 29669.
2594 o Minor features (auto-formatting scripts):
2595 - When annotating C macros, never generate a line that our check-
2596 spaces script would reject. Closes ticket 31759.
2597 - When annotating C macros, try to remove cases of double-negation.
2598 Closes ticket 31779.
2600 o Minor features (best practices tracker):
2601 - Our best-practices tracker now integrates with our include-checker
2602 tool to keep track of how many layering violations we have not yet
2603 fixed. We hope to reduce this number over time to improve Tor's
2604 modularity. Closes ticket 31176.
2605 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
2606 practracker from the environment. We may want this for continuous
2607 integration. Closes ticket 31309.
2608 - Give a warning rather than an error when a practracker exception
2609 is violated by a small amount, add a --list-overbroad option to
2610 practracker that lists exceptions that are stricter than they need
2611 to be, and provide an environment variable for disabling
2612 practracker. Closes ticket 30752.
2613 - Our best-practices tracker now looks at headers as well as C
2614 files. Closes ticket 31175.
2616 o Minor features (build system):
2617 - Make pkg-config use --prefix when cross-compiling, if
2618 PKG_CONFIG_PATH is not set. Closes ticket 32191.
2619 - Add --disable-manpage and --disable-html-manual options to
2620 configure script. This will enable shortening build times by not
2621 building documentation. Resolves issue 19381.
2623 o Minor features (compilation):
2624 - Log a more useful error message when we are compiling and one of
2625 the compile-time hardening options we have selected can be linked
2626 but not executed. Closes ticket 27530.
2628 o Minor features (configuration):
2629 - The configuration code has been extended to allow splitting
2630 configuration data across multiple objects. Previously, all
2631 configuration data needed to be kept in a single object, which
2632 tended to become bloated. Closes ticket 31240.
2634 o Minor features (continuous integration):
2635 - When building on Appveyor and Travis, pass the "-k" flag to make,
2636 so that we are informed of all compilation failures, not just the
2637 first one or two. Closes ticket 31372.
2638 - When running CI builds on Travis, put some random data in
2639 ~/.torrc, to make sure no tests are reading the Tor configuration
2640 file from its default location. Resolves issue 30102.
2642 o Minor features (debugging):
2643 - Log a nonfatal assertion failure if we encounter a configuration
2644 line whose command is "CLEAR" but which has a nonempty value. This
2645 should be impossible, according to the rules of our configuration
2646 line parsing. Closes ticket 31529.
2648 o Minor features (geoip):
2649 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2650 Country database. Closes ticket 32685.
2652 o Minor features (git hooks):
2653 - Our pre-commit git hook now checks for a special file before
2654 running practracker, so that practracker only runs on branches
2655 that are based on master. Since the pre-push hook calls the pre-
2656 commit hook, practracker will also only run before pushes of
2657 branches based on master. Closes ticket 30979.
2659 o Minor features (git scripts):
2660 - Add a "--" command-line argument, to separate git-push-all.sh
2661 script arguments from arguments that are passed through to git
2662 push. Closes ticket 31314.
2663 - Add a -r <remote-name> argument to git-push-all.sh, so the script
2664 can push test branches to a personal remote. Closes ticket 31314.
2665 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
2666 git-push-all.sh, which makes these scripts create, merge forward,
2667 and push test branches. Closes ticket 31314.
2668 - Add a -u argument to git-merge-forward.sh, so that the script can
2669 re-use existing test branches after a merge failure and fix.
2670 Closes ticket 31314.
2671 - Add a TOR_GIT_PUSH env var, which sets the default git push
2672 command and arguments for git-push-all.sh. Closes ticket 31314.
2673 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
2674 script push master and maint branches with a delay between each
2675 branch. These delays trigger the CI jobs in a set order, which
2676 should show the most likely failures first. Also make pushes
2677 atomic by default, and make the script pass any command-line
2678 arguments to git push. Closes ticket 29879.
2679 - Call the shellcheck script from the pre-commit hook. Closes
2681 - Skip pushing test branches that are the same as a remote
2682 maint/release/master branch in git-push-all.sh by default. Add a
2683 -s argument, so git-push-all.sh can push all test branches. Closes
2686 o Minor features (IPv6, logging):
2687 - Log IPv6 addresses as well as IPv4 addresses when describing
2688 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
2690 o Minor features (maintenance scripts):
2691 - Add a Coccinelle script to detect bugs caused by incrementing or
2692 decrementing a variable inside a call to log_debug(). Since
2693 log_debug() is a macro whose arguments are conditionally
2694 evaluated, it is usually an error to do this. One such bug was
2695 30628, in which SENDME cells were miscounted by a decrement
2696 operator inside a log_debug() call. Closes ticket 30743.
2698 o Minor features (onion service v3):
2699 - Do not allow single hop clients to fetch or post an HS descriptor
2700 from an HSDir. Closes ticket 24964.
2702 o Minor features (onion service):
2703 - Disallow single-hop clients at the introduction point. We've
2704 removed Tor2web support a while back and single-hop rendezvous
2705 attempts are blocked at the relays. This change should remove load
2706 off the network from spammy clients. Close ticket 24963.
2708 o Minor features (onion services v3):
2709 - Assist users who try to setup v2 client authorization in v3 onion
2710 services by pointing them to the right documentation. Closes
2713 o Minor features (stem tests):
2714 - Change "make test-stem" so it only runs the stem tests that use
2715 tor. This change makes test-stem faster and more reliable. Closes
2718 o Minor features (testing):
2719 - When running tests that attempt to look up hostnames, replace the
2720 libc name lookup functions with ones that do not actually touch
2721 the network. This way, the tests complete more quickly in the
2722 presence of a slow or missing DNS resolver. Closes ticket 31841.
2723 - Add a script to invoke "tor --dump-config" and "tor
2724 --verify-config" with various configuration options, and see
2725 whether tor's resulting configuration or error messages are what
2726 we expect. Use it for integration testing of our +Option and
2727 /Option flags. Closes ticket 31637.
2728 - Improve test coverage for our existing configuration parsing and
2729 management API. Closes ticket 30893.
2730 - Add integration tests to make sure that practracker gives the
2731 outputs we expect. Closes ticket 31477.
2732 - The practracker self-tests are now run as part of the Tor test
2733 suite. Closes ticket 31304.
2735 o Minor features (testing, continuous integration):
2736 - Disable all but one Travis CI macOS build, to mitigate slow
2737 scheduling of Travis macOS jobs. Closes ticket 32177.
2738 - Run the chutney IPv6 networks as part of Travis CI. Closes
2740 - Simplify the Travis CI build matrix, and optimise for build time.
2741 Closes ticket 31859.
2742 - Use Windows Server 2019 instead of Windows Server 2016 in our
2743 Appveyor builds. Closes ticket 32086.
2745 o Minor features (token bucket):
2746 - Implement a generic token bucket that uses a single counter, for
2747 use in anti-DoS onion service work. Closes ticket 30687.
2749 o Minor bugfixes (Appveyor continuous integration):
2750 - Avoid spurious errors when Appveyor CI fails before the install
2751 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2753 o Minor bugfixes (best practices tracker):
2754 - Fix a few issues in the best-practices script, including tests,
2755 tab tolerance, error reporting, and directory-exclusion logic.
2756 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
2757 - When running check-best-practices, only consider files in the src
2758 subdirectory. Previously we had recursively considered all
2759 subdirectories, which made us get confused by the temporary
2760 directories made by "make distcheck". Fixes bug 31578; bugfix
2763 o Minor bugfixes (build system):
2764 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
2765 32124; bugfix on 0.3.4.1-alpha.
2766 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
2768 - Stop failing when jemalloc is requested, but tcmalloc is not
2769 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
2770 - When pkg-config is not installed, or a library that depends on
2771 pkg-config is not found, tell the user what to do to fix the
2772 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
2773 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2774 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2776 o Minor bugfixes (chutney, makefiles, documentation):
2777 - "make test-network-all" now shows the warnings from each test-
2778 network.sh run on the console, so developers see new warnings
2779 early. We've also improved the documentation for this feature, and
2780 renamed a Makefile variable so the code is self-documenting. Fixes
2781 bug 30455; bugfix on 0.3.0.4-rc.
2783 o Minor bugfixes (client, onion service v3):
2784 - Fix a BUG() assertion that occurs within a very small race window
2785 between when a client intro circuit opens and when its descriptor
2786 gets cleaned up from the cache. The circuit is now closed early,
2787 which will trigger a re-fetch of the descriptor and continue the
2788 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2790 o Minor bugfixes (code quality):
2791 - Fix "make check-includes" so it runs correctly on out-of-tree
2792 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
2794 o Minor bugfixes (compilation):
2795 - Add more stub functions to fix compilation on Android with link-
2796 time optimization when --disable-module-dirauth is used.
2797 Previously, these compilation settings would make the compiler
2798 look for functions that didn't exist. Fixes bug 31552; bugfix
2800 - Suppress spurious float-conversion warnings from GCC when calling
2801 floating-point classifier functions on FreeBSD. Fixes part of bug
2802 31687; bugfix on 0.3.1.5-alpha.
2804 o Minor bugfixes (configuration):
2805 - Invalid floating-point values in the configuration file are now
2806 treated as errors in the configuration. Previously, they were
2807 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
2809 o Minor bugfixes (connections):
2810 - Avoid trying to read data from closed connections, which can cause
2811 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2812 30344; bugfix on 0.1.1.1-alpha.
2814 o Minor bugfixes (controller protocol):
2815 - Fix the MAPADDRESS controller command to accept one or more
2816 arguments. Previously, it required two or more arguments, and
2817 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2819 o Minor bugfixes (coverity):
2820 - Add an assertion when parsing a BEGIN cell so that coverity can be
2821 sure that we are not about to dereference a NULL address. Fixes
2822 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
2823 - In our siphash implementation, when building for coverity, use
2824 memcpy in place of a switch statement, so that coverity can tell
2825 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
2826 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
2827 - Fix several coverity warnings from our unit tests. Fixes bug
2828 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
2830 o Minor bugfixes (crash):
2831 - When running Tor with an option like --verify-config or
2832 --dump-config that does not start the event loop, avoid crashing
2833 if we try to exit early because of an error. Fixes bug 32407;
2834 bugfix on 0.3.3.1-alpha.
2836 o Minor bugfixes (developer tooling):
2837 - Only log git script changes in the post-merge script when the
2838 merge was to the master branch. Fixes bug 31040; bugfix
2841 o Minor bugfixes (directory authorities):
2842 - Return a distinct status when formatting annotations fails. Fixes
2843 bug 30780; bugfix on 0.2.0.8-alpha.
2845 o Minor bugfixes (error handling):
2846 - Always lock the backtrace buffer before it is used. Fixes bug
2847 31734; bugfix on 0.2.5.3-alpha.
2848 - On abort, try harder to flush the output buffers of log messages.
2849 On some platforms (macOS), log messages could be discarded when
2850 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2851 - Report the tor version whenever an assertion fails. Previously, we
2852 only reported the Tor version on some crashes, and some non-fatal
2853 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2854 - When tor aborts due to an error, close log file descriptors before
2855 aborting. Closing the logs makes some OSes flush log file buffers,
2856 rather than deleting buffered log lines. Fixes bug 31594; bugfix
2859 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
2860 - When extracting an IPv6 address from a PF-based proxy, verify that
2861 we are actually configured to receive an IPv6 address, and log an
2862 internal error if not. Fixes part of bug 31687; bugfix
2865 o Minor bugfixes (git hooks):
2866 - Remove a duplicate call to practracker from the pre-push hook. The
2867 pre-push hook already calls the pre-commit hook, which calls
2868 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
2870 o Minor bugfixes (git scripts):
2871 - Stop hard-coding the bash path in the git scripts. Some OSes don't
2872 have bash in /usr/bin, others have an ancient bash at this path.
2873 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
2874 - Stop hard-coding the tor master branch name and worktree path in
2875 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
2876 - Allow git-push-all.sh to be run from any directory. Previously,
2877 the script only worked if run from an upstream worktree directory.
2878 Closes ticket 31678.
2880 o Minor bugfixes (guards):
2881 - When tor is missing descriptors for some primary entry guards,
2882 make the log message less alarming. It's normal for descriptors to
2883 expire, as long as tor fetches new ones soon after. Fixes bug
2884 31657; bugfix on 0.3.3.1-alpha.
2886 o Minor bugfixes (ipv6):
2887 - Check for private IPv6 addresses alongside their IPv4 equivalents
2888 when authorities check descriptors. Previously, we only checked
2889 for private IPv4 addresses. Fixes bug 31088; bugfix on
2890 0.2.3.21-rc. Patch by Neel Chauhan.
2891 - When parsing microdescriptors, we should check the IPv6 exit
2892 policy alongside IPv4. Previously, we checked both exit policies
2893 for only router info structures, while microdescriptors were
2894 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
2897 o Minor bugfixes (logging):
2898 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2899 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2900 - Disable backtrace signal handlers when shutting down tor. Fixes
2901 bug 31614; bugfix on 0.2.5.2-alpha.
2902 - Rate-limit our the logging message about the obsolete .exit
2903 notation. Previously, there was no limit on this warning, which
2904 could potentially be triggered many times by a hostile website.
2905 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2906 - When initialising log domain masks, only set known log domains.
2907 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
2908 - Change log level of message "Hash of session info was not as
2909 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2911 - Fix a code issue that would have broken our parsing of log domains
2912 as soon as we had 33 of them. Fortunately, we still only have 29.
2913 Fixes bug 31451; bugfix on 0.4.1.4-rc.
2915 o Minor bugfixes (logging, protocol violations):
2916 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2917 cell on a connection using the obsolete v1 link protocol. Log a
2918 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2920 o Minor bugfixes (mainloop, periodic events, in-process API):
2921 - Reset the periodic events' "enabled" flag when Tor is shut down
2922 cleanly. Previously, this flag was left on, which caused periodic
2923 events not to be re-enabled when Tor was relaunched in-process
2924 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2927 o Minor bugfixes (memory management):
2928 - Stop leaking a small amount of memory in nt_service_install(), in
2929 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
2932 o Minor bugfixes (modules):
2933 - Explain what the optional Directory Authority module is, and what
2934 happens when it is disabled. Fixes bug 31825; bugfix
2937 o Minor bugfixes (multithreading):
2938 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2939 31736; bugfix on 0.0.7.
2941 o Minor bugfixes (networking, IP addresses):
2942 - When parsing addresses via Tor's internal DNS lookup API, reject
2943 IPv4 addresses in square brackets, and accept IPv6 addresses in
2944 square brackets. This change completes the work started in 23082,
2945 making address parsing consistent between tor's internal DNS
2946 lookup and address parsing APIs. Fixes bug 30721; bugfix
2948 - When parsing addresses via Tor's internal address:port parsing and
2949 DNS lookup APIs, require IPv6 addresses with ports to have square
2950 brackets. But allow IPv6 addresses without ports, whether or not
2951 they have square brackets. Fixes bug 30721; bugfix
2954 o Minor bugfixes (onion service v3):
2955 - When purging the client descriptor cache, close any introduction
2956 point circuits associated with purged cache entries. This avoids
2957 picking those circuits later when connecting to the same
2958 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
2960 o Minor bugfixes (onion services):
2961 - In the hs_ident_circuit_t data structure, remove the unused field
2962 circuit_type and the respective argument in hs_ident_circuit_new().
2963 This field was set by clients (for introduction) and services (for
2964 introduction and rendezvous) but was never used afterwards. Fixes
2965 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
2967 o Minor bugfixes (operator tools):
2968 - Make tor-print-ed-signing-cert(1) print certificate expiration
2969 date in RFC 1123 and UNIX timestamp formats, to make output
2970 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
2972 o Minor bugfixes (process management):
2973 - Remove overly strict assertions that triggered when a pluggable
2974 transport failed to launch. Fixes bug 31091; bugfix
2976 - Remove an assertion in the Unix process backend. This assertion
2977 would trigger when we failed to find the executable for a child
2978 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2980 o Minor bugfixes (relay):
2981 - Avoid crashing when starting with a corrupt keys directory where
2982 the old ntor key and the new ntor key are identical. Fixes bug
2983 30916; bugfix on 0.2.4.8-alpha.
2985 o Minor bugfixes (rust):
2986 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2987 31463; bugfix on 0.3.5.4-alpha.
2988 - Raise the minimum rustc version to 1.31.0, as checked by configure
2989 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
2991 o Minor bugfixes (sendme, code structure):
2992 - Rename the trunnel SENDME file definition from sendme.trunnel to
2993 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
2994 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
2996 o Minor bugfixes (statistics):
2997 - Stop removing the ed25519 signature if the extra info file is too
2998 big. If the signature data was removed, but the keyword was kept,
2999 this could result in an unparseable extra info file. Fixes bug
3000 30958; bugfix on 0.2.7.2-alpha.
3002 o Minor bugfixes (subsystems):
3003 - Make the subsystem init order match the subsystem module
3004 dependencies. Call windows process security APIs as early as
3005 possible. Initialize logging before network and time, so that
3006 network and time can use logging. Fixes bug 31615; bugfix
3009 o Minor bugfixes (testing):
3010 - Avoid intermittent test failures due to a test that had relied on
3011 inconsistent timing sources. Fixes bug 31995; bugfix
3013 - When testing port rebinding, don't busy-wait for tor to log.
3014 Instead, actually sleep for a short time before polling again.
3015 Also improve the formatting of control commands and log messages.
3016 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3017 - Teach the util/socketpair_ersatz test to work correctly when we
3018 have no network stack configured. Fixes bug 30804; bugfix
3021 o Minor bugfixes (tests, SunOS):
3022 - Avoid a map_anon_nofork test failure due to a signed/unsigned
3023 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
3025 o Minor bugfixes (tls, logging):
3026 - Log bugs about the TLS read buffer's length only once, rather than
3027 filling the logs with similar warnings. Fixes bug 31939; bugfix
3030 o Minor bugfixes (v2 single onion services):
3031 - Always retry v2 single onion service intro and rend circuits with
3032 a 3-hop path. Previously, v2 single onion services used a 3-hop
3033 path when rendezvous circuits were retried after a remote or
3034 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3035 23818; bugfix on 0.2.9.3-alpha.
3037 o Minor bugfixes (v3 onion services):
3038 - When cleaning up intro circuits for a v3 onion service, don't
3039 remove circuits that have an established or pending circuit, even
3040 if they ran out of retries. This way, we don't remove a circuit on
3041 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
3043 o Minor bugfixes (v3 single onion services):
3044 - Always retry v3 single onion service intro and rend circuits with
3045 a 3-hop path. Previously, v3 single onion services used a 3-hop
3046 path when rend circuits were retried after a remote or delayed
3047 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
3048 bugfix on 0.3.2.1-alpha.
3049 - Make v3 single onion services fall back to a 3-hop intro, when all
3050 intro points are unreachable via a 1-hop path. Previously, v3
3051 single onion services failed when all intro nodes were unreachable
3052 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3054 o Code simplification and refactoring:
3055 - Refactor connection_control_process_inbuf() to reduce the size of
3056 a practracker exception. Closes ticket 31840.
3057 - Refactor the microdescs_parse_from_string() function into smaller
3058 pieces, for better comprehensibility. Closes ticket 31675.
3059 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
3060 tests and fuzzers, rather than using hard-coded values. Closes
3062 - Interface for function `decrypt_desc_layer` cleaned up. Closes
3066 - Correct the description of "GuardLifetime". Fixes bug 31189;
3067 bugfix on 0.3.0.1-alpha.
3068 - Make clear in the man page, in both the bandwidth section and the
3069 AccountingMax section, that Tor counts in powers of two, not
3070 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
3071 bytes. Resolves ticket 32106.
3072 - Document the signal-safe logging behaviour in the tor man page.
3073 Also add some comments to the relevant functions. Closes
3075 - Explain why we can't destroy the backtrace buffer mutex. Explain
3076 why we don't need to destroy the log mutex. Closes ticket 31736.
3077 - The Tor source code repository now includes a (somewhat dated)
3078 description of Tor's modular architecture, in doc/HACKING/design.
3079 This is based on the old "tor-guts.git" repository, which we are
3080 adopting and superseding. Closes ticket 31849.
3081 - Improve documentation in circuit padding subsystem. Patch by
3082 Tobias Pulls. Closes ticket 31113.
3083 - Include an example usage for IPv6 ORPort in our sample torrc.
3084 Closes ticket 31320; patch from Ali Raheem.
3085 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3086 notice.html so that operators no longer have to host it
3087 themselves. Closes ticket 31089.
3090 - No longer include recommended package digests in votes as detailed
3091 in proposal 301. The RecommendedPackages torrc option is
3092 deprecated and will no longer have any effect. "package" lines
3093 will still be considered when computing consensuses for consensus
3094 methods that include them. (This change has no effect on the list
3095 of recommended Tor versions, which is still in use.) Closes
3097 - Remove torctl.in from contrib/dist directory. Resolves
3101 - Require C99 standards-conforming code in Travis CI, but allow GNU
3102 gcc extensions. Also activates clang's -Wtypedef-redefinition
3103 warnings. Build some jobs with -std=gnu99, and some jobs without.
3104 Closes ticket 32500.
3105 - Run shellcheck for all non-third-party shell scripts that are
3106 shipped with Tor. Closes ticket 29533.
3107 - When checking shell scripts, ignore any user-created directories.
3108 Closes ticket 30967.
3110 o Code simplification and refactoring (config handling):
3111 - Extract our variable manipulation code from confparse.c to a new
3112 lower-level typedvar.h module. Closes ticket 30864.
3113 - Lower another layer of object management from confparse.c to a
3114 more general tool. Now typed structure members are accessible via
3115 an abstract type. Implements ticket 30914.
3116 - Move our backend logic for working with configuration and state
3117 files into a lower-level library, since it no longer depends on
3118 any tor-specific functionality. Closes ticket 31626.
3119 - Numerous simplifications in configuration-handling logic: remove
3120 duplicated macro definitions, replace magical names with flags,
3121 and refactor "TestingTorNetwork" to use the same default-option
3122 logic as the rest of Tor. Closes ticket 30935.
3123 - Replace our ad-hoc set of flags for configuration variables and
3124 configuration variable types with fine-grained orthogonal flags
3125 corresponding to the actual behavior we want. Closes ticket 31625.
3127 o Code simplification and refactoring (misc):
3128 - Eliminate some uses of lower-level control reply abstractions,
3129 primarily in the onion_helper functions. Closes ticket 30889.
3130 - Rework bootstrap tracking to use the new publish-subscribe
3131 subsystem. Closes ticket 29976.
3132 - Rewrite format_node_description() and router_get_verbose_nickname()
3133 to use strlcpy() and strlcat(). The previous implementation used
3134 memcpy() and pointer arithmetic, which was error-prone. Closes
3135 ticket 31545. This is CID 1452819.
3136 - Split extrainfo_dump_to_string() into smaller functions. Closes
3138 - Use the ptrdiff_t type consistently for expressing variable
3139 offsets and pointer differences. Previously we incorrectly (but
3140 harmlessly) used int and sometimes off_t for these cases. Closes
3142 - Use the subsystems mechanism to manage the main event loop code.
3143 Closes ticket 30806.
3144 - Various simplifications and minor improvements to the circuit
3145 padding machines. Patch by Tobias Pulls. Closes tickets 31112
3148 o Documentation (hard-coded directories):
3149 - Improve the documentation for the DirAuthority and FallbackDir
3150 torrc options. Closes ticket 30955.
3152 o Documentation (tor.1 man page):
3153 - Fix typo in tor.1 man page: the option is "--help", not "-help".
3154 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
3156 o Testing (continuous integration):
3157 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3158 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3159 until we can fix some Bionic permissions issues (see ticket
3160 32240). Related to ticket 31919.
3161 - Install the mingw OpenSSL package in Appveyor. This makes sure
3162 that the OpenSSL headers and libraries match in Tor's Appveyor
3163 builds. (This bug was triggered by an Appveyor image update.)
3164 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3165 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3168 Changes in version 0.4.1.7 - 2019-12-09
3169 This release backports several bugfixes to improve stability and
3170 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
3171 including all relays relying on AccountingMax, should upgrade.
3173 o Major features (directory authorities, backport from 0.4.2.2-alpha):
3174 - Directory authorities now reject relays running all currently
3175 deprecated release series. The currently supported release series
3176 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
3178 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
3179 - Avoid a possible crash when restarting Tor in embedded mode and
3180 enabling a different set of publish/subscribe messages. Fixes bug
3181 31898; bugfix on 0.4.1.1-alpha.
3183 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3184 - Relays now respect their AccountingMax bandwidth again. When
3185 relays entered "soft" hibernation (which typically starts when
3186 we've hit 90% of our AccountingMax), we had stopped checking
3187 whether we should enter hard hibernation. Soft hibernation refuses
3188 new connections and new circuits, but the existing circuits can
3189 continue, meaning that relays could have exceeded their configured
3190 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3192 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3193 - Stop ignoring torrc options after an %include directive, when the
3194 included directory ends with a file that does not contain any
3195 config options (but does contain comments or whitespace). Fixes
3196 bug 31408; bugfix on 0.3.1.1-alpha.
3198 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3199 - Onion services now always use the exact number of intro points
3200 configured with the HiddenServiceNumIntroductionPoints option (or
3201 fewer if nodes are excluded). Before, a service could sometimes
3202 pick more intro points than configured. Fixes bug 31548; bugfix
3205 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3206 - When building on Appveyor and Travis, pass the "-k" flag to make,
3207 so that we are informed of all compilation failures, not just the
3208 first one or two. Closes ticket 31372.
3210 o Minor features (geoip, backport from 0.4.2.5):
3211 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3212 Country database. Closes ticket 32685.
3214 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3215 - Avoid spurious errors when Appveyor CI fails before the install step.
3216 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3218 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3219 - Fix a BUG() assertion that occurs within a very small race window
3220 between when a client intro circuit opens and when its descriptor
3221 gets cleaned up from the cache. The circuit is now closed early,
3222 which will trigger a re-fetch of the descriptor and continue the
3223 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3225 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3226 - Avoid trying to read data from closed connections, which can cause
3227 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3228 30344; bugfix on 0.1.1.1-alpha.
3230 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3231 - On abort, try harder to flush the output buffers of log messages.
3232 On some platforms (macOS), log messages could be discarded when
3233 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3234 - Report the tor version whenever an assertion fails. Previously, we
3235 only reported the Tor version on some crashes, and some non-fatal
3236 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3237 - When tor aborts due to an error, close log file descriptors before
3238 aborting. Closing the logs makes some OSes flush log file buffers,
3239 rather than deleting buffered log lines. Fixes bug 31594; bugfix
3242 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3243 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
3244 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
3245 - Disable backtrace signal handlers when shutting down tor. Fixes
3246 bug 31614; bugfix on 0.2.5.2-alpha.
3247 - Rate-limit our the logging message about the obsolete .exit
3248 notation. Previously, there was no limit on this warning, which
3249 could potentially be triggered many times by a hostile website.
3250 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3252 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3253 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3254 cell on a connection using the obsolete v1 link protocol. Log a
3255 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3257 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3258 - Reset the periodic events' "enabled" flag when Tor is shut down
3259 cleanly. Previously, this flag was left on, which caused periodic
3260 events not to be re-enabled when Tor was relaunched in-process
3261 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3264 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
3265 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
3266 31736; bugfix on 0.0.7.
3268 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
3269 - Remove overly strict assertions that triggered when a pluggable
3270 transport failed to launch. Fixes bug 31091; bugfix
3272 - Remove an assertion in the Unix process backend. This assertion
3273 would trigger when we failed to find the executable for a child
3274 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3276 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3277 - Avoid crashing when starting with a corrupt keys directory where
3278 the old ntor key and the new ntor key are identical. Fixes bug
3279 30916; bugfix on 0.2.4.8-alpha.
3281 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3282 - When testing port rebinding, don't busy-wait for tor to log.
3283 Instead, actually sleep for a short time before polling again.
3284 Also improve the formatting of control commands and log messages.
3285 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3287 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
3288 - Avoid a map_anon_nofork test failure due to a signed/unsigned
3289 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
3291 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3292 - Log bugs about the TLS read buffer's length only once, rather than
3293 filling the logs with similar warnings. Fixes bug 31939; bugfix
3296 o Documentation (backport from 0.4.2.2-alpha):
3297 - Explain why we can't destroy the backtrace buffer mutex. Explain
3298 why we don't need to destroy the log mutex. Closes ticket 31736.
3300 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3301 - Disable all but one Travis CI macOS build, to mitigate slow
3302 scheduling of Travis macOS jobs. Closes ticket 32177.
3303 - Run the chutney IPv6 networks as part of Travis CI. Closes
3305 - Simplify the Travis CI build matrix, and optimise for build time.
3306 Closes ticket 31859.
3307 - Use Windows Server 2019 instead of Windows Server 2016 in our
3308 Appveyor builds. Closes ticket 32086.
3310 o Testing (continuous integration, backport from 0.4.2.4-rc):
3311 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3312 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3313 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3314 until we can fix some Bionic permissions issues (see ticket
3315 32240). Related to ticket 31919.
3316 - Install the mingw OpenSSL package in Appveyor. This makes sure
3317 that the OpenSSL headers and libraries match in Tor's Appveyor
3318 builds. (This bug was triggered by an Appveyor image update.)
3319 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3321 o Testing (continuous integration, backport from 0.4.2.5):
3322 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3323 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3324 Build some jobs with -std=gnu99, and some jobs without.
3325 Closes ticket 32500.
3328 Changes in version 0.4.0.6 - 2019-12-09
3329 This is the second stable release in the 0.4.0.x series. This release
3330 backports several bugfixes to improve stability and correctness. Anyone
3331 experiencing build problems or crashes with 0.4.0.5, including all relays
3332 relying on AccountingMax, should upgrade.
3334 Note that, per our support policy, support for the 0.4.0.x series will end
3335 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
3336 latest stable release, or downgrade to 0.3.5.x, which will get long-term
3337 support until 1 Feb 2022.
3339 o Directory authority changes (backport from 0.4.1.5):
3340 - The directory authority "dizum" has a new IP address. Closes
3343 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
3344 - Consider our directory information to have changed when our list
3345 of bridges changes. Previously, Tor would not re-compute the
3346 status of its directory information when bridges changed, and
3347 therefore would not realize that it was no longer able to build
3348 circuits. Fixes part of bug 29875.
3349 - Do not count previously configured working bridges towards our
3350 total of working bridges. Previously, when Tor's list of bridges
3351 changed, it would think that the old bridges were still usable,
3352 and delay fetching router descriptors for the new ones. Fixes part
3353 of bug 29875; bugfix on 0.3.0.1-alpha.
3355 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
3356 - When considering upgrading circuits from "waiting for guard" to
3357 "open", always ignore circuits that are marked for close. Otherwise,
3358 we can end up in the situation where a subsystem is notified that
3359 a closing circuit has just opened, leading to undesirable
3360 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3362 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
3363 - Properly clean up the introduction point map when circuits change
3364 purpose from onion service circuits to pathbias, measurement, or
3365 other circuit types. This should fix some service-side instances
3366 of introduction point failure. Fixes bug 29034; bugfix
3369 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
3370 - Fix an unreachable bug in which an introduction point could try to
3371 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3372 to encode, leading the relay to assert(). We've consolidated the
3373 ABI values into Trunnel now. Fixes bug 30454; bugfix
3375 - Clients can now handle unknown status codes from INTRODUCE_ACK
3376 cells. (The NACK behavior will stay the same.) This will allow us
3377 to extend status codes in the future without breaking the normal
3378 client behavior. Fixes another part of bug 30454; bugfix
3381 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3382 - Relays now respect their AccountingMax bandwidth again. When
3383 relays entered "soft" hibernation (which typically starts when
3384 we've hit 90% of our AccountingMax), we had stopped checking
3385 whether we should enter hard hibernation. Soft hibernation refuses
3386 new connections and new circuits, but the existing circuits can
3387 continue, meaning that relays could have exceeded their configured
3388 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3390 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3391 - Stop ignoring torrc options after an %include directive, when the
3392 included directory ends with a file that does not contain any
3393 config options (but does contain comments or whitespace). Fixes
3394 bug 31408; bugfix on 0.3.1.1-alpha.
3396 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3397 - Onion services now always use the exact number of intro points
3398 configured with the HiddenServiceNumIntroductionPoints option (or
3399 fewer if nodes are excluded). Before, a service could sometimes
3400 pick more intro points than configured. Fixes bug 31548; bugfix
3403 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3404 - Add a "--list-modules" command to print a list of which compile-
3405 time modules are enabled. Closes ticket 30452.
3407 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
3408 - Remove sudo configuration lines from .travis.yml as they are no
3409 longer needed with current Travis build environment. Resolves
3412 o Minor features (continuous integration, backport from 0.4.1.4-rc):
3413 - Our Travis configuration now uses Chutney to run some network
3414 integration tests automatically. Closes ticket 29280.
3416 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3417 - When building on Appveyor and Travis, pass the "-k" flag to make,
3418 so that we are informed of all compilation failures, not just the
3419 first one or two. Closes ticket 31372.
3421 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
3422 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3423 in December 2018 (of which ~122 were still functional), with a
3424 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3425 in June 2019. Closes ticket 28795.
3427 o Minor features (geoip, backport from 0.4.2.5):
3428 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3429 Country database. Closes ticket 32685.
3431 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3432 - Change "make test-stem" so it only runs the stem tests that use
3433 tor. This change makes test-stem faster and more reliable. Closes
3436 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3437 - Avoid spurious errors when Appveyor CI fails before the install step.
3438 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3440 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3441 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3442 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3444 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
3445 - Fix a logic error that prevented the SessionGroup sub-option from
3446 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3448 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
3449 - On relays, properly check that a padding machine is absent before
3450 logging a warning about it being absent. Fixes bug 30649; bugfix
3453 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3454 - Fix a BUG() assertion that occurs within a very small race window
3455 between when a client intro circuit opens and when its descriptor
3456 gets cleaned up from the cache. The circuit is now closed early,
3457 which will trigger a re-fetch of the descriptor and continue the
3458 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3460 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
3461 - Don't believe clock skew results from NETINFO cells that appear to
3462 arrive before we sent the VERSIONS cells they are responding to.
3463 Previously, we would accept them up to 3 minutes "in the past".
3464 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3466 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
3467 - Fix a compilation warning on Windows about casting a function
3468 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3471 o Minor bugfixes (compilation, backport from 0.4.1.5):
3472 - Avoid using labs() on time_t, which can cause compilation warnings
3473 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3475 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3476 - Suppress spurious float-conversion warnings from GCC when calling
3477 floating-point classifier functions on FreeBSD. Fixes part of bug
3478 31687; bugfix on 0.3.1.5-alpha.
3480 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3481 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3482 due to missing declarations of abort(), and prevent other such
3483 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3485 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3486 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3487 want authentication along with configured (but unused!)
3488 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3490 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3491 - Avoid trying to read data from closed connections, which can cause
3492 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3493 30344; bugfix on 0.1.1.1-alpha.
3495 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3496 - Allow the test-stem job to fail in Travis, because it sometimes
3497 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3498 - Skip test_rebind on macOS in Travis, because it is unreliable on
3499 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3500 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3501 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3503 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3504 - Avoid a set of possible code paths that could try to use freed
3505 memory in routerlist_free() while Tor was exiting. Fixes bug
3506 31003; bugfix on 0.1.2.2-alpha.
3508 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3509 - Stop crashing after parsing an unknown descriptor purpose
3510 annotation. We think this bug can only be triggered by modifying a
3511 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3513 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3514 - Move the "bandwidth-file-headers" line in directory authority
3515 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3518 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3519 - On abort, try harder to flush the output buffers of log messages.
3520 On some platforms (macOS), log messages could be discarded when
3521 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3522 - Report the tor version whenever an assertion fails. Previously, we
3523 only reported the Tor version on some crashes, and some non-fatal
3524 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3526 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3527 - When extracting an IPv6 address from a PF-based proxy, verify that
3528 we are actually configured to receive an IPv6 address, and log an
3529 internal error if not. Fixes part of bug 31687; bugfix
3532 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3533 - When tor is missing descriptors for some primary entry guards,
3534 make the log message less alarming. It's normal for descriptors to
3535 expire, as long as tor fetches new ones soon after. Fixes bug
3536 31657; bugfix on 0.3.3.1-alpha.
3538 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3539 - Do not log a warning when running with an OpenSSL version other
3540 than the one Tor was compiled with, if the two versions should be
3541 compatible. Previously, we would warn whenever the version was
3542 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3544 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3545 - Change log level of message "Hash of session info was not as
3546 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3549 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3550 - Rate-limit our the logging message about the obsolete .exit
3551 notation. Previously, there was no limit on this warning, which
3552 could potentially be triggered many times by a hostile website.
3553 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3555 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3556 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3557 cell on a connection using the obsolete v1 link protocol. Log a
3558 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3560 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3561 - Reset the periodic events' "enabled" flag when Tor is shut down
3562 cleanly. Previously, this flag was left on, which caused periodic
3563 events not to be re-enabled when Tor was relaunched in-process
3564 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3567 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
3568 - Avoid a minor memory leak that could occur on relays when failing
3569 to create a "keys" directory. Fixes bug 30148; bugfix
3572 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
3573 - Fix a trivial memory leak when parsing an invalid value
3574 from a download schedule in the configuration. Fixes bug
3575 30894; bugfix on 0.3.4.1-alpha.
3577 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
3578 - Fix usage of minherit() on NetBSD and other platforms that define
3579 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3580 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3582 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
3583 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3584 implemenation) when failing to load an onion service client
3585 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3587 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
3588 - When purging the DNS cache because of an out-of-memory condition,
3589 try purging just the older entries at first. Previously, we would
3590 always purge the whole thing. Fixes bug 29617; bugfix
3593 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
3594 - Avoid crashing in our tor_vasprintf() implementation on systems
3595 that define neither vasprintf() nor _vscprintf(). (This bug has
3596 been here long enough that we question whether people are running
3597 Tor on such systems, but we're applying the fix out of caution.)
3598 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3601 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
3602 - Remove overly strict assertions that triggered when a pluggable
3603 transport failed to launch. Fixes bug 31091; bugfix
3605 - Remove an assertion in the Unix process backend. This assertion
3606 would trigger when we failed to find the executable for a child
3607 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3609 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3610 - Avoid crashing when starting with a corrupt keys directory where
3611 the old ntor key and the new ntor key are identical. Fixes bug
3612 30916; bugfix on 0.2.4.8-alpha.
3614 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
3615 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3616 31463; bugfix on 0.3.5.4-alpha.
3618 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3619 - When testing port rebinding, don't busy-wait for tor to log.
3620 Instead, actually sleep for a short time before polling again.
3621 Also improve the formatting of control commands and log messages.
3622 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3624 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3625 - Log bugs about the TLS read buffer's length only once, rather than
3626 filling the logs with similar warnings. Fixes bug 31939; bugfix
3629 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
3630 - Always retry v2 single onion service intro and rend circuits with
3631 a 3-hop path. Previously, v2 single onion services used a 3-hop
3632 path when rendezvous circuits were retried after a remote or
3633 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3634 23818; bugfix on 0.2.9.3-alpha.
3635 - Make v3 single onion services fall back to a 3-hop intro, when all
3636 intro points are unreachable via a 1-hop path. Previously, v3
3637 single onion services failed when all intro nodes were unreachable
3638 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3640 o Documentation (backport from 0.4.2.1-alpha):
3641 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3642 notice.html so that operators no longer have to host it
3643 themselves. Closes ticket 31089.
3645 o Testing (backport from 0.4.1.2-alpha):
3646 - Specify torrc paths (with empty files) when launching tor in
3647 integration tests; refrain from reading user and system torrcs.
3648 Resolves issue 29702.
3650 o Testing (continuous integration, backport from 0.4.1.1-alpha):
3651 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3653 o Testing (continuous integration, backport from 0.4.1.5):
3654 - In Travis, make stem log a controller trace to the console, and
3655 tail stem's tor log after failure. Closes ticket 30591.
3656 - In Travis, only run the stem tests that use a tor binary. Closes
3659 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3660 - Disable all but one Travis CI macOS build, to mitigate slow
3661 scheduling of Travis macOS jobs. Closes ticket 32177.
3662 - Run the chutney IPv6 networks as part of Travis CI. Closes
3664 - Simplify the Travis CI build matrix, and optimise for build time.
3665 Closes ticket 31859.
3666 - Use Windows Server 2019 instead of Windows Server 2016 in our
3667 Appveyor builds. Closes ticket 32086.
3669 o Testing (continuous integration, backport from 0.4.2.4-rc):
3670 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3671 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3672 until we can fix some Bionic permissions issues (see ticket
3673 32240). Related to ticket 31919.
3674 - Install the mingw OpenSSL package in Appveyor. This makes sure
3675 that the OpenSSL headers and libraries match in Tor's Appveyor
3676 builds. (This bug was triggered by an Appveyor image update.)
3677 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3678 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3680 o Testing (continuous integration, backport from 0.4.2.5):
3681 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3682 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3683 Build some jobs with -std=gnu99, and some jobs without.
3684 Closes ticket 32500.
3687 Changes in version 0.3.5.9 - 2019-12-09
3688 Tor 0.3.5.9 backports serveral fixes from later releases, including
3689 several that affect bridge users, relay stability, onion services,
3692 o Directory authority changes (backport from 0.4.1.5):
3693 - The directory authority "dizum" has a new IP address. Closes
3696 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
3697 - Consider our directory information to have changed when our list
3698 of bridges changes. Previously, Tor would not re-compute the
3699 status of its directory information when bridges changed, and
3700 therefore would not realize that it was no longer able to build
3701 circuits. Fixes part of bug 29875.
3702 - Do not count previously configured working bridges towards our
3703 total of working bridges. Previously, when Tor's list of bridges
3704 changed, it would think that the old bridges were still usable,
3705 and delay fetching router descriptors for the new ones. Fixes part
3706 of bug 29875; bugfix on 0.3.0.1-alpha.
3708 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
3709 - When considering upgrading circuits from "waiting for guard" to
3710 "open", always ignore circuits that are marked for close. Otherwise,
3711 we can end up in the situation where a subsystem is notified that
3712 a closing circuit has just opened, leading to undesirable
3713 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3715 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
3716 - When running with NSS, disable TLS 1.2 ciphersuites that use
3717 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3718 these ciphersuites don't work -- which caused relays to fail to
3719 handshake with one another when these ciphersuites were enabled.
3720 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3722 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
3723 - Properly clean up the introduction point map when circuits change
3724 purpose from onion service circuits to pathbias, measurement, or
3725 other circuit types. This should fix some service-side instances
3726 of introduction point failure. Fixes bug 29034; bugfix
3729 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
3730 - Fix an unreachable bug in which an introduction point could try to
3731 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3732 to encode, leading the relay to assert(). We've consolidated the
3733 ABI values into Trunnel now. Fixes bug 30454; bugfix
3735 - Clients can now handle unknown status codes from INTRODUCE_ACK
3736 cells. (The NACK behavior will stay the same.) This will allow us
3737 to extend status codes in the future without breaking the normal
3738 client behavior. Fixes another part of bug 30454; bugfix
3741 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3742 - Stop ignoring torrc options after an %include directive, when the
3743 included directory ends with a file that does not contain any
3744 config options (but does contain comments or whitespace). Fixes
3745 bug 31408; bugfix on 0.3.1.1-alpha.
3747 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3748 - Onion services now always use the exact number of intro points
3749 configured with the HiddenServiceNumIntroductionPoints option (or
3750 fewer if nodes are excluded). Before, a service could sometimes
3751 pick more intro points than configured. Fixes bug 31548; bugfix
3754 o Minor features (address selection, backport from 0.4.0.3-alpha):
3755 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3756 private for others. This subnet is the RFC 6598 (Carrier Grade
3757 NAT) IP range, and is deployed by many ISPs as an alternative to
3758 RFC 1918 that does not break existing internal networks. Tor now
3759 blocks SOCKS and control ports on these addresses and warns users
3760 if client ports or ExtORPorts are listening on a RFC 6598 address.
3761 Closes ticket 28525. Patch by Neel Chauhan.
3763 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
3764 - Make bandwidth authorities ignore relays that are reported in the
3765 bandwidth file with the flag "vote=0". This change allows us to
3766 report unmeasured relays for diagnostic reasons without including
3767 their bandwidth in the bandwidth authorities' vote. Closes
3770 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3771 - Add a "--list-modules" command to print a list of which compile-
3772 time modules are enabled. Closes ticket 30452.
3774 o Minor features (continuous integration, backport from 0.4.0.4-rc):
3775 - On Travis Rust builds, cleanup Rust registry and refrain from
3776 caching the "target/" directory to speed up builds. Resolves
3779 o Minor features (continuous integration, backport from 0.4.0.5):
3780 - In Travis, tell timelimit to use stem's backtrace signals, and
3781 launch python directly from timelimit, so python receives the
3782 signals from timelimit, rather than make. Closes ticket 30117.
3784 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
3785 - Remove sudo configuration lines from .travis.yml as they are no
3786 longer needed with current Travis build environment. Resolves
3789 o Minor features (continuous integration, backport from 0.4.1.4-rc):
3790 - Our Travis configuration now uses Chutney to run some network
3791 integration tests automatically. Closes ticket 29280.
3793 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3794 - When building on Appveyor and Travis, pass the "-k" flag to make,
3795 so that we are informed of all compilation failures, not just the
3796 first one or two. Closes ticket 31372.
3798 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
3799 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3800 in December 2018 (of which ~122 were still functional), with a
3801 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3802 in June 2019. Closes ticket 28795.
3804 o Minor features (geoip, backport from 0.4.2.5):
3805 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3806 Country database. Closes ticket 32685.
3808 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
3809 - Try to log an error from NSS (if there is any) and a more useful
3810 description of our situation if we are using NSS and a call to
3811 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
3813 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3814 - Change "make test-stem" so it only runs the stem tests that use
3815 tor. This change makes test-stem faster and more reliable. Closes
3818 o Minor bugfixes (security, backport from 0.4.0.4-rc):
3819 - Verify in more places that we are not about to create a buffer
3820 with more than INT_MAX bytes, to avoid possible OOB access in the
3821 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
3822 fixed by Tobias Stoeckmann.
3823 - Fix a potential double free bug when reading huge bandwidth files.
3824 The issue is not exploitable in the current Tor network because
3825 the vulnerable code is only reached when directory authorities
3826 read bandwidth files, but bandwidth files come from a trusted
3827 source (usually the authorities themselves). Furthermore, the
3828 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
3829 which are not used by any of the current authorities. Fixes bug
3830 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
3833 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
3834 - Reset coverage state on disk after Travis CI has finished. This
3835 should prevent future coverage merge errors from causing the test
3836 suite for the "process" subsystem to fail. The process subsystem
3837 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
3839 - Terminate test-stem if it takes more than 9.5 minutes to run.
3840 (Travis terminates the job after 10 minutes of no output.)
3841 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
3843 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3844 - Avoid spurious errors when Appveyor CI fails before the install step.
3845 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3847 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3848 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3849 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3851 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
3852 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
3853 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
3856 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
3857 - Fix a logic error that prevented the SessionGroup sub-option from
3858 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3860 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3861 - Fix a BUG() assertion that occurs within a very small race window
3862 between when a client intro circuit opens and when its descriptor
3863 gets cleaned up from the cache. The circuit is now closed early,
3864 which will trigger a re-fetch of the descriptor and continue the
3865 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3867 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
3868 - Don't believe clock skew results from NETINFO cells that appear to
3869 arrive before we sent the VERSIONS cells they are responding to.
3870 Previously, we would accept them up to 3 minutes "in the past".
3871 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3873 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
3874 - Fix a compilation warning on Windows about casting a function
3875 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3878 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
3879 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
3880 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3882 o Minor bugfixes (compilation, backport from 0.4.1.5):
3883 - Avoid using labs() on time_t, which can cause compilation warnings
3884 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3886 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3887 - Suppress spurious float-conversion warnings from GCC when calling
3888 floating-point classifier functions on FreeBSD. Fixes part of bug
3889 31687; bugfix on 0.3.1.5-alpha.
3891 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3892 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3893 due to missing declarations of abort(), and prevent other such
3894 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3896 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3897 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3898 want authentication along with configured (but unused!)
3899 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3901 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3902 - Avoid trying to read data from closed connections, which can cause
3903 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3904 30344; bugfix on 0.1.1.1-alpha.
3906 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3907 - Allow the test-stem job to fail in Travis, because it sometimes
3908 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3909 - Skip test_rebind on macOS in Travis, because it is unreliable on
3910 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3911 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3912 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3914 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3915 - Avoid a set of possible code paths that could try to use freed
3916 memory in routerlist_free() while Tor was exiting. Fixes bug
3917 31003; bugfix on 0.1.2.2-alpha.
3919 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3920 - Stop crashing after parsing an unknown descriptor purpose
3921 annotation. We think this bug can only be triggered by modifying a
3922 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3924 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3925 - Move the "bandwidth-file-headers" line in directory authority
3926 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3929 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3930 - On abort, try harder to flush the output buffers of log messages.
3931 On some platforms (macOS), log messages could be discarded when
3932 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3933 - Report the tor version whenever an assertion fails. Previously, we
3934 only reported the Tor version on some crashes, and some non-fatal
3935 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3937 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3938 - When extracting an IPv6 address from a PF-based proxy, verify that
3939 we are actually configured to receive an IPv6 address, and log an
3940 internal error if not. Fixes part of bug 31687; bugfix
3943 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3944 - When tor is missing descriptors for some primary entry guards,
3945 make the log message less alarming. It's normal for descriptors to
3946 expire, as long as tor fetches new ones soon after. Fixes bug
3947 31657; bugfix on 0.3.3.1-alpha.
3949 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
3950 - Avoid logging that we are relaxing a circuit timeout when that
3951 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
3953 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
3954 - Correct a misleading error message when IPv4Only or IPv6Only is
3955 used but the resolved address can not be interpreted as an address
3956 of the specified IP version. Fixes bug 13221; bugfix on
3957 0.2.3.9-alpha. Patch from Kris Katterjohn.
3958 - Log the correct port number for listening sockets when "auto" is
3959 used to let Tor pick the port number. Previously, port 0 was
3960 logged instead of the actual port number. Fixes bug 29144; bugfix
3961 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3962 - Stop logging a BUG() warning when Tor is waiting for exit
3963 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3965 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3966 - Do not log a warning when running with an OpenSSL version other
3967 than the one Tor was compiled with, if the two versions should be
3968 compatible. Previously, we would warn whenever the version was
3969 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3971 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3972 - Change log level of message "Hash of session info was not as
3973 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3976 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3977 - Rate-limit our the logging message about the obsolete .exit
3978 notation. Previously, there was no limit on this warning, which
3979 could potentially be triggered many times by a hostile website.
3980 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3982 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3983 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3984 cell on a connection using the obsolete v1 link protocol. Log a
3985 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3987 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3988 - Reset the periodic events' "enabled" flag when Tor is shut down
3989 cleanly. Previously, this flag was left on, which caused periodic
3990 events not to be re-enabled when Tor was relaunched in-process
3991 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3994 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
3995 - Avoid a minor memory leak that could occur on relays when failing
3996 to create a "keys" directory. Fixes bug 30148; bugfix
3999 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
4000 - Fix a trivial memory leak when parsing an invalid value
4001 from a download schedule in the configuration. Fixes bug
4002 30894; bugfix on 0.3.4.1-alpha.
4004 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
4005 - Refactor the shared random state's memory management so that it
4006 actually takes ownership of the shared random value pointers.
4007 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
4009 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
4010 - Stop leaking parts of the shared random state in the shared-random
4011 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
4013 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
4014 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
4015 implemenation) when failing to load an onion service client
4016 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
4018 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
4019 - When purging the DNS cache because of an out-of-memory condition,
4020 try purging just the older entries at first. Previously, we would
4021 always purge the whole thing. Fixes bug 29617; bugfix
4024 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
4025 - Avoid crashing in our tor_vasprintf() implementation on systems
4026 that define neither vasprintf() nor _vscprintf(). (This bug has
4027 been here long enough that we question whether people are running
4028 Tor on such systems, but we're applying the fix out of caution.)
4029 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4032 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
4033 - Avoid crashing when starting with a corrupt keys directory where
4034 the old ntor key and the new ntor key are identical. Fixes bug
4035 30916; bugfix on 0.2.4.8-alpha.
4037 o Minor bugfixes (rust, backport from 0.4.0.5):
4038 - Abort on panic in all build profiles, instead of potentially
4039 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
4041 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4042 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4043 31463; bugfix on 0.3.5.4-alpha.
4045 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
4046 - Allow connections to single onion services to remain idle without
4047 being disconnected. Previously, relays acting as rendezvous points
4048 for single onion services were mistakenly closing idle rendezvous
4049 circuits after 60 seconds, thinking that they were unused
4050 directory-fetching circuits that had served their purpose. Fixes
4051 bug 29665; bugfix on 0.2.1.26.
4053 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
4054 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
4055 relay and bridge extra-info documents. Fixes bug 29017; bugfix
4058 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
4059 - Downgrade some LOG_ERR messages in the address/* tests to
4060 warnings. The LOG_ERR messages were occurring when we had no
4061 configured network. We were failing the unit tests, because we
4062 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
4063 29530; bugfix on 0.3.5.8.
4064 - Fix our gcov wrapper script to look for object files at the
4065 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
4067 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
4068 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
4069 recent test-network.sh to use new chutney features in CI. Fixes
4070 bug 29703; bugfix on 0.2.9.1-alpha.
4071 - Fix a test failure on Windows caused by an unexpected "BUG"
4072 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
4075 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
4076 - When testing port rebinding, don't busy-wait for tor to log.
4077 Instead, actually sleep for a short time before polling again.
4078 Also improve the formatting of control commands and log messages.
4079 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4081 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
4082 - When classifying a client's selection of TLS ciphers, if the
4083 client ciphers are not yet available, do not cache the result.
4084 Previously, we had cached the unavailability of the cipher list
4085 and never looked again, which in turn led us to assume that the
4086 client only supported the ancient V1 link protocol. This, in turn,
4087 was causing Stem integration tests to stall in some cases. Fixes
4088 bug 30021; bugfix on 0.2.4.8-alpha.
4090 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
4091 - Log bugs about the TLS read buffer's length only once, rather than
4092 filling the logs with similar warnings. Fixes bug 31939; bugfix
4095 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4096 - Always retry v2 single onion service intro and rend circuits with
4097 a 3-hop path. Previously, v2 single onion services used a 3-hop
4098 path when rendezvous circuits were retried after a remote or
4099 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4100 23818; bugfix on 0.2.9.3-alpha.
4101 - Make v3 single onion services fall back to a 3-hop intro, when all
4102 intro points are unreachable via a 1-hop path. Previously, v3
4103 single onion services failed when all intro nodes were unreachable
4104 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4106 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
4107 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
4108 Windows Server 2012 R2 job. The remaining 2 jobs still provide
4109 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
4110 fast_finish, so failed jobs terminate the build immediately. Fixes
4111 bug 29601; bugfix on 0.3.5.4-alpha.
4113 o Documentation (backport from 0.4.2.1-alpha):
4114 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4115 notice.html so that operators no longer have to host it
4116 themselves. Closes ticket 31089.
4118 o Testing (backport from 0.4.1.2-alpha):
4119 - Specify torrc paths (with empty files) when launching tor in
4120 integration tests; refrain from reading user and system torrcs.
4121 Resolves issue 29702.
4123 o Testing (continuous integration, backport from 0.4.1.1-alpha):
4124 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4126 o Testing (continuous integration, backport from 0.4.1.5):
4127 - In Travis, make stem log a controller trace to the console, and
4128 tail stem's tor log after failure. Closes ticket 30591.
4129 - In Travis, only run the stem tests that use a tor binary. Closes
4132 o Testing (continuous integration, backport from 0.4.2.3-alpha):
4133 - Disable all but one Travis CI macOS build, to mitigate slow
4134 scheduling of Travis macOS jobs. Closes ticket 32177.
4135 - Run the chutney IPv6 networks as part of Travis CI. Closes
4137 - Simplify the Travis CI build matrix, and optimise for build time.
4138 Closes ticket 31859.
4139 - Use Windows Server 2019 instead of Windows Server 2016 in our
4140 Appveyor builds. Closes ticket 32086.
4142 o Testing (continuous integration, backport from 0.4.2.4-rc):
4143 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4144 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4145 until we can fix some Bionic permissions issues (see ticket
4146 32240). Related to ticket 31919.
4147 - Install the mingw OpenSSL package in Appveyor. This makes sure
4148 that the OpenSSL headers and libraries match in Tor's Appveyor
4149 builds. (This bug was triggered by an Appveyor image update.)
4150 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4151 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4153 o Testing (continuous integration, backport from 0.4.2.5):
4154 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
4155 extensions. Also activates clang's -Wtypedef-redefinition warnings.
4156 Build some jobs with -std=gnu99, and some jobs without.
4157 Closes ticket 32500.
4160 Changes in version 0.4.1.6 - 2019-09-19
4161 This release backports several bugfixes to improve stability and
4162 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
4163 or experiencing reliability issues with single onion services, should
4166 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
4167 - Tolerate systems (including some Android installations) where
4168 madvise and MADV_DONTDUMP are available at build-time, but not at
4169 run time. Previously, these systems would notice a failed syscall
4170 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
4171 - Tolerate systems (including some Linux installations) where
4172 madvise and/or MADV_DONTFORK are available at build-time, but not
4173 at run time. Previously, these systems would notice a failed
4174 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
4176 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4177 - Change "make test-stem" so it only runs the stem tests that use
4178 tor. This change makes test-stem faster and more reliable. Closes
4181 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
4182 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4183 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4185 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4186 - Add more stub functions to fix compilation on Android with link-
4187 time optimization when --disable-module-dirauth is used.
4188 Previously, these compilation settings would make the compiler
4189 look for functions that didn't exist. Fixes bug 31552; bugfix
4191 - Suppress spurious float-conversion warnings from GCC when calling
4192 floating-point classifier functions on FreeBSD. Fixes part of bug
4193 31687; bugfix on 0.3.1.5-alpha.
4195 o Minor bugfixes (controller protocol):
4196 - Fix the MAPADDRESS controller command to accept one or more
4197 arguments. Previously, it required two or more arguments, and ignored
4198 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4200 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4201 - When extracting an IPv6 address from a PF-based proxy, verify that
4202 we are actually configured to receive an IPv6 address, and log an
4203 internal error if not. Fixes part of bug 31687; bugfix
4206 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4207 - When tor is missing descriptors for some primary entry guards,
4208 make the log message less alarming. It's normal for descriptors to
4209 expire, as long as tor fetches new ones soon after. Fixes bug
4210 31657; bugfix on 0.3.3.1-alpha.
4212 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4213 - Change log level of message "Hash of session info was not as
4214 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4217 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4218 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4219 31463; bugfix on 0.3.5.4-alpha.
4221 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4222 - Always retry v2 single onion service intro and rend circuits with
4223 a 3-hop path. Previously, v2 single onion services used a 3-hop
4224 path when rendezvous circuits were retried after a remote or
4225 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4226 23818; bugfix on 0.2.9.3-alpha.
4228 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
4229 - Always retry v3 single onion service intro and rend circuits with
4230 a 3-hop path. Previously, v3 single onion services used a 3-hop
4231 path when rend circuits were retried after a remote or delayed
4232 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
4233 bugfix on 0.3.2.1-alpha.
4234 - Make v3 single onion services fall back to a 3-hop intro, when all
4235 intro points are unreachable via a 1-hop path. Previously, v3
4236 single onion services failed when all intro nodes were unreachable
4237 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4239 o Documentation (backport from 0.4.2.1-alpha):
4240 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4241 notice.html so that operators no longer have to host it
4242 themselves. Closes ticket 31089.
4245 Changes in version 0.4.1.5 - 2019-08-20
4246 This is the first stable release in the 0.4.1.x series. This series
4247 adds experimental circuit-level padding, authenticated SENDME cells to
4248 defend against certain attacks, and several performance improvements
4249 to save on CPU consumption. It fixes bugs in bootstrapping and v3
4250 onion services. It also includes numerous smaller features and
4251 bugfixes on earlier versions.
4253 Per our support policy, we will support the 0.4.1.x series for nine
4254 months, or until three months after the release of a stable 0.4.2.x:
4255 whichever is longer. If you need longer-term support, please stick
4256 with 0.3.5.x, which will we plan to support until Feb 2022.
4258 Below are the changes since 0.4.0.5. For a list of only the changes
4259 since 0.4.1.4-rc, see the ChangeLog file.
4261 o Directory authority changes:
4262 - The directory authority "dizum" has a new IP address. Closes
4265 o Major features (circuit padding):
4266 - Onion service clients now add padding cells at the start of their
4267 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
4268 look more like general purpose Exit traffic. The overhead for this
4269 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
4270 extra upstream cell and 10 downstream cells for INTRODUCE
4271 circuits. This feature is only enabled when also supported by the
4272 circuit's middle node. (Clients may specify fixed middle nodes
4273 with the MiddleNodes option, and may force-disable this feature
4274 with the CircuitPadding option.) Closes ticket 28634.
4276 o Major features (code organization):
4277 - Tor now includes a generic publish-subscribe message-passing
4278 subsystem that we can use to organize intermodule dependencies. We
4279 hope to use this to reduce dependencies between modules that don't
4280 need to be related, and to generally simplify our codebase. Closes
4283 o Major features (controller protocol):
4284 - Controller commands are now parsed using a generalized parsing
4285 subsystem. Previously, each controller command was responsible for
4286 parsing its own input, which led to strange inconsistencies.
4287 Closes ticket 30091.
4289 o Major features (flow control):
4290 - Implement authenticated SENDMEs as detailed in proposal 289. A
4291 SENDME cell now includes the digest of the traffic that it
4292 acknowledges, so that once an end point receives the SENDME, it
4293 can confirm the other side's knowledge of the previous cells that
4294 were sent, and prevent certain types of denial-of-service attacks.
4295 This behavior is controlled by two new consensus parameters: see
4296 the proposal for more details. Fixes ticket 26288.
4298 o Major features (performance):
4299 - Our node selection algorithm now excludes nodes in linear time.
4300 Previously, the algorithm was quadratic, which could slow down
4301 heavily used onion services. Closes ticket 30307.
4303 o Major features (performance, RNG):
4304 - Tor now constructs a fast secure pseudorandom number generator for
4305 each thread, to use when performance is critical. This PRNG is
4306 based on AES-CTR, using a buffering construction similar to
4307 libottery and the (newer) OpenBSD arc4random() code. It
4308 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
4309 small outputs. Although we believe it to be cryptographically
4310 strong, we are only using it when necessary for performance.
4311 Implements tickets 29023 and 29536.
4313 o Major bugfixes (bridges):
4314 - Consider our directory information to have changed when our list
4315 of bridges changes. Previously, Tor would not re-compute the
4316 status of its directory information when bridges changed, and
4317 therefore would not realize that it was no longer able to build
4318 circuits. Fixes part of bug 29875.
4319 - Do not count previously configured working bridges towards our
4320 total of working bridges. Previously, when Tor's list of bridges
4321 changed, it would think that the old bridges were still usable,
4322 and delay fetching router descriptors for the new ones. Fixes part
4323 of bug 29875; bugfix on 0.3.0.1-alpha.
4325 o Major bugfixes (circuit build, guard):
4326 - On relays, properly check that a padding machine is absent before
4327 logging a warning about it being absent. Fixes bug 30649; bugfix
4329 - When considering upgrading circuits from "waiting for guard" to
4330 "open", always ignore circuits that are marked for close. Otherwise,
4331 we can end up in the situation where a subsystem is notified that
4332 a closing circuit has just opened, leading to undesirable
4333 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
4335 o Major bugfixes (onion service reachability):
4336 - Properly clean up the introduction point map when circuits change
4337 purpose from onion service circuits to pathbias, measurement, or
4338 other circuit types. This should fix some service-side instances
4339 of introduction point failure. Fixes bug 29034; bugfix
4342 o Major bugfixes (onion service v3):
4343 - Fix an unreachable bug in which an introduction point could try to
4344 send an INTRODUCE_ACK with a status code that Trunnel would refuse
4345 to encode, leading the relay to assert(). We've consolidated the
4346 ABI values into Trunnel now. Fixes bug 30454; bugfix
4348 - Clients can now handle unknown status codes from INTRODUCE_ACK
4349 cells. (The NACK behavior will stay the same.) This will allow us
4350 to extend status codes in the future without breaking the normal
4351 client behavior. Fixes another part of bug 30454; bugfix
4354 o Minor features (authenticated SENDME):
4355 - Ensure that there is enough randomness on every circuit to prevent
4356 an attacker from successfully predicting the hashes they will need
4357 to include in authenticated SENDME cells. At a random interval, if
4358 we have not sent randomness already, we now leave some extra space
4359 at the end of a cell that we can fill with random bytes. Closes
4362 o Minor features (circuit padding logging):
4363 - Demote noisy client-side warn logs about circuit padding to protocol
4364 warnings. Add additional log messages and circuit ID fields to help
4365 with bug 30992 and any other future issues.
4367 o Minor features (circuit padding):
4368 - We now use a fast PRNG when scheduling circuit padding. Part of
4370 - Allow the padding machine designer to pick the edges of their
4371 histogram instead of trying to compute them automatically using an
4372 exponential formula. Resolves some undefined behavior in the case
4373 of small histograms and allows greater flexibility on machine
4374 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
4375 - Allow circuit padding machines to hold a circuit open until they
4376 are done padding it. Closes ticket 28780.
4378 o Minor features (compile-time modules):
4379 - Add a "--list-modules" command to print a list of which compile-
4380 time modules are enabled. Closes ticket 30452.
4382 o Minor features (continuous integration):
4383 - Our Travis configuration now uses Chutney to run some network
4384 integration tests automatically. Closes ticket 29280.
4385 - When running coverage builds on Travis, we now set
4386 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
4388 - Remove sudo configuration lines from .travis.yml as they are no
4389 longer needed with current Travis build environment. Resolves
4391 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4393 o Minor features (controller):
4394 - Add onion service version 3 support to the HSFETCH command.
4395 Previously, only version 2 onion services were supported. Closes
4396 ticket 25417. Patch by Neel Chauhan.
4398 o Minor features (debugging):
4399 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
4400 logging of additional information during assert failure. Now we
4401 can use format strings to include information for trouble
4402 shooting. Resolves ticket 29662.
4404 o Minor features (defense in depth):
4405 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
4406 case a bug causes them to be used later. Closes ticket 30176.
4407 Patch from Tobias Stoeckmann.
4408 - Tor now uses a cryptographically strong PRNG even for decisions
4409 that we do not believe are security-sensitive. Previously, for
4410 performance reasons, we had used a trivially predictable linear
4411 congruential generator algorithm for certain load-balancing and
4412 statistical sampling decisions. Now we use our fast RNG in those
4413 cases. Closes ticket 29542.
4415 o Minor features (developer tools):
4416 - Tor's "practracker" test script now checks for files and functions
4417 that seem too long and complicated. Existing overlong functions
4418 and files are accepted for now, but should eventually be
4419 refactored. Closes ticket 29221.
4420 - Add some scripts used for git maintenance to scripts/git. Closes
4422 - Call practracker from pre-push and pre-commit git hooks to let
4423 developers know if they made any code style violations. Closes
4425 - Add a script to check that each header has a well-formed and
4426 unique guard macro. Closes ticket 29756.
4428 o Minor features (fallback directory list):
4429 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4430 in December 2018 (of which ~122 were still functional), with a
4431 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
4432 in June 2019. Closes ticket 28795.
4434 o Minor features (geoip):
4435 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
4436 Country database. Closes ticket 30852.
4437 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
4438 Country database. Closes ticket 30522.
4440 o Minor features (HTTP tunnel):
4441 - Return an informative web page when the HTTPTunnelPort is used as
4442 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
4444 o Minor features (IPv6, v3 onion services):
4445 - Make v3 onion services put IPv6 addresses in service descriptors.
4446 Before this change, service descriptors only contained IPv4
4447 addresses. Implements 26992.
4449 o Minor features (logging):
4450 - Give a more useful assertion failure message if we think we have
4451 minherit() but we fail to make a region non-inheritable. Give a
4452 compile-time warning if our support for minherit() is incomplete.
4453 Closes ticket 30686.
4455 o Minor features (maintenance):
4456 - Add a new "make autostyle" target that developers can use to apply
4457 all automatic Tor style and consistency conversions to the
4458 codebase. Closes ticket 30539.
4460 o Minor features (modularity):
4461 - The "--disable-module-dirauth" compile-time option now disables
4462 even more dirauth-only code. Closes ticket 30345.
4464 o Minor features (performance):
4465 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
4466 1.1.1 and later), since they tend to be faster than tiny-keccak.
4467 Closes ticket 28837.
4469 o Minor features (testing):
4470 - The circuitpadding tests now use a reproducible RNG implementation,
4471 so that if a test fails, we can learn why. Part of ticket 28878.
4472 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
4473 to set the RNG seed for tests that use a reproducible RNG. Part of
4475 - When running tests in coverage mode, take additional care to make
4476 our coverage deterministic, so that we can accurately track
4477 changes in code coverage. Closes ticket 30519.
4478 - Tor's unit test code now contains helper functions to replace the
4479 PRNG with a deterministic or reproducible version for testing.
4480 Previously, various tests implemented this in various ways.
4481 Implements ticket 29732.
4482 - We now have a script, cov-test-determinism.sh, to identify places
4483 where our unit test coverage has become nondeterministic. Closes
4485 - Check that representative subsets of values of `int` and `unsigned
4486 int` can be represented by `void *`. Resolves issue 29537.
4488 o Minor bugfixes (bridge authority):
4489 - Bridge authorities now set bridges as running or non-running when
4490 about to dump their status to a file. Previously, they set bridges
4491 as running in response to a GETINFO command, but those shouldn't
4492 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
4493 Patch by Neel Chauhan.
4495 o Minor bugfixes (channel padding statistics):
4496 - Channel padding write totals and padding-enabled totals are now
4497 counted properly in relay extrainfo descriptors. Fixes bug 29231;
4498 bugfix on 0.3.1.1-alpha.
4500 o Minor bugfixes (circuit isolation):
4501 - Fix a logic error that prevented the SessionGroup sub-option from
4502 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
4504 o Minor bugfixes (circuit padding):
4505 - Add a "CircuitPadding" torrc option to disable circuit padding.
4506 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
4507 - Allow circuit padding machines to specify that they do not
4508 contribute much overhead, and provide consensus flags and torrc
4509 options to force clients to only use these low overhead machines.
4510 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
4511 - Provide a consensus parameter to fully disable circuit padding, to
4512 be used in emergency network overload situations. Fixes bug 30173;
4513 bugfix on 0.4.0.1-alpha.
4514 - The circuit padding subsystem will no longer schedule padding if
4515 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
4516 - Inspect a circuit-level cell queue before sending padding, to
4517 avoid sending padding while too much data is already queued. Fixes
4518 bug 29204; bugfix on 0.4.0.1-alpha.
4519 - Avoid calling monotime_absolute_usec() in circuit padding machines
4520 that do not use token removal or circuit RTT estimation. Fixes bug
4521 29085; bugfix on 0.4.0.1-alpha.
4523 o Minor bugfixes (clock skew detection):
4524 - Don't believe clock skew results from NETINFO cells that appear to
4525 arrive before we sent the VERSIONS cells they are responding to.
4526 Previously, we would accept them up to 3 minutes "in the past".
4527 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4529 o Minor bugfixes (compatibility, standards compliance):
4530 - Fix a bug that would invoke undefined behavior on certain
4531 operating systems when trying to asprintf() a string exactly
4532 INT_MAX bytes long. We don't believe this is exploitable, but it's
4533 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
4534 Found and fixed by Tobias Stoeckmann.
4536 o Minor bugfixes (compilation warning):
4537 - Fix a compilation warning on Windows about casting a function
4538 pointer for GetTickCount64(). Fixes bug 31374; bugfix on
4541 o Minor bugfixes (compilation):
4542 - Avoid using labs() on time_t, which can cause compilation warnings
4543 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4545 o Minor bugfixes (compilation, unusual configurations):
4546 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
4547 due to missing declarations of abort(), and prevent other such
4548 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
4550 o Minor bugfixes (configuration, proxies):
4551 - Fix a bug that prevented us from supporting SOCKS5 proxies that
4552 want authentication along with configured (but unused!)
4553 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
4555 o Minor bugfixes (continuous integration):
4556 - Allow the test-stem job to fail in Travis, because it sometimes
4557 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
4558 - Skip test_rebind on macOS in Travis, because it is unreliable on
4559 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4560 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
4561 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4563 o Minor bugfixes (controller protocol):
4564 - Teach the controller parser to distinguish an object preceded by
4565 an argument list from one without. Previously, it couldn't
4566 distinguish an argument list from the first line of a multiline
4567 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
4569 o Minor bugfixes (crash on exit):
4570 - Avoid a set of possible code paths that could try to use freed
4571 memory in routerlist_free() while Tor was exiting. Fixes bug
4572 31003; bugfix on 0.1.2.2-alpha.
4574 o Minor bugfixes (developer tooling):
4575 - Fix pre-push hook to allow fixup and squash commits when pushing
4576 to non-upstream git remote. Fixes bug 30286; bugfix
4579 o Minor bugfixes (directory authorities):
4580 - Stop crashing after parsing an unknown descriptor purpose
4581 annotation. We think this bug can only be triggered by modifying a
4582 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
4583 - Move the "bandwidth-file-headers" line in directory authority
4584 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
4586 - Directory authorities with IPv6 support now always mark themselves
4587 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
4588 Patch by Neel Chauhan.
4590 o Minor bugfixes (documentation):
4591 - Improve the documentation for using MapAddress with ".exit". Fixes
4592 bug 30109; bugfix on 0.1.0.1-rc.
4593 - Improve the monotonic time module and function documentation to
4594 explain what "monotonic" actually means, and document some results
4595 that have surprised people. Fixes bug 29640; bugfix
4597 - Use proper formatting when providing an example on quoting options
4598 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
4600 o Minor bugfixes (logging):
4601 - Do not log a warning when running with an OpenSSL version other
4602 than the one Tor was compiled with, if the two versions should be
4603 compatible. Previously, we would warn whenever the version was
4604 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
4605 - Warn operators when the MyFamily option is set but ContactInfo is
4606 missing, as the latter should be set too. Fixes bug 25110; bugfix
4609 o Minor bugfixes (memory leaks):
4610 - Avoid a minor memory leak that could occur on relays when failing
4611 to create a "keys" directory. Fixes bug 30148; bugfix
4613 - Fix a trivial memory leak when parsing an invalid value from a
4614 download schedule in the configuration. Fixes bug 30894; bugfix
4617 o Minor bugfixes (NetBSD):
4618 - Fix usage of minherit() on NetBSD and other platforms that define
4619 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
4620 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
4622 o Minor bugfixes (onion services):
4623 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
4624 implemenation) when failing to load an onion service client
4625 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
4626 - When refusing to launch a controller's HSFETCH request because of
4627 rate-limiting, respond to the controller with a new response,
4628 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
4629 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
4631 - When relaunching a circuit to a rendezvous service, mark the
4632 circuit as needing high-uptime routers as appropriate. Fixes bug
4633 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
4634 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
4635 (IPv6 support for v3 onion services is still incomplete: see
4636 ticket 23493 for details.) Fixes bug 23588; bugfix on
4637 0.3.2.1-alpha. Patch by Neel Chauhan.
4639 o Minor bugfixes (onion services, performance):
4640 - When building circuits to onion services, call tor_addr_parse()
4641 less often. Previously, we called tor_addr_parse() in
4642 circuit_is_acceptable() even if its output wasn't used. This
4643 change should improve performance when building circuits. Fixes
4644 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
4646 o Minor bugfixes (out-of-memory handler):
4647 - When purging the DNS cache because of an out-of-memory condition,
4648 try purging just the older entries at first. Previously, we would
4649 always purge the whole thing. Fixes bug 29617; bugfix
4652 o Minor bugfixes (performance):
4653 - When checking whether a node is a bridge, use a fast check to make
4654 sure that its identity is set. Previously, we used a constant-time
4655 check, which is not necessary in this case. Fixes bug 30308;
4656 bugfix on 0.3.5.1-alpha.
4658 o Minor bugfixes (pluggable transports):
4659 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
4660 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
4662 o Minor bugfixes (portability):
4663 - Avoid crashing in our tor_vasprintf() implementation on systems
4664 that define neither vasprintf() nor _vscprintf(). (This bug has
4665 been here long enough that we question whether people are running
4666 Tor on such systems, but we're applying the fix out of caution.)
4667 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4670 o Minor bugfixes (probability distributions):
4671 - Refactor and improve parts of the probability distribution code
4672 that made Coverity complain. Fixes bug 29805; bugfix
4675 o Minor bugfixes (python):
4676 - Stop assuming that /usr/bin/python3 exists. For scripts that work
4677 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
4678 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
4680 o Minor bugfixes (relay):
4681 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
4682 is auto, act as if ExitRelay is 1. Previously, we would ignore
4683 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
4684 0.3.5.1-alpha. Patch by Neel Chauhan.
4686 o Minor bugfixes (static analysis):
4687 - Fix several spurious Coverity warnings about the unit tests, to
4688 lower our chances of missing real warnings in the future. Fixes
4689 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
4691 o Minor bugfixes (stats):
4692 - When ExtraInfoStatistics is 0, stop including bandwidth usage
4693 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
4694 bridge statistics by country in extra-info documents. Fixes bug
4695 29018; bugfix on 0.2.4.1-alpha.
4697 o Minor bugfixes (testing):
4698 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
4699 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
4700 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
4701 - Fix some incorrect code in the v3 onion service unit tests. Fixes
4702 bug 29243; bugfix on 0.3.2.1-alpha.
4703 - In the "routerkeys/*" tests, check the return values of mkdir()
4704 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
4705 Found by Coverity as CID 1444254.
4706 - Split test_utils_general() into several smaller test functions.
4707 This makes it easier to perform resource deallocation on assert
4708 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
4709 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
4711 o Minor bugfixes (tor-resolve):
4712 - Fix a memory leak in tor-resolve that could happen if Tor gave it
4713 a malformed SOCKS response. (Memory leaks in tor-resolve don't
4714 actually matter, but it's good to fix them anyway.) Fixes bug
4715 30151; bugfix on 0.4.0.1-alpha.
4717 o Code simplification and refactoring:
4718 - Abstract out the low-level formatting of replies on the control
4719 port. Implements ticket 30007.
4720 - Add several assertions in an attempt to fix some Coverity
4721 warnings. Closes ticket 30149.
4722 - Introduce a connection_dir_buf_add() helper function that checks
4723 for compress_state of dir_connection_t and automatically writes a
4724 string to directory connection with or without compression.
4725 Resolves issue 28816.
4726 - Make the base32_decode() API return the number of bytes written,
4727 for consistency with base64_decode(). Closes ticket 28913.
4728 - Move most relay-only periodic events out of mainloop.c into the
4729 relay subsystem. Closes ticket 30414.
4730 - Refactor and encapsulate parts of the codebase that manipulate
4731 crypt_path_t objects. Resolves issue 30236.
4732 - Refactor several places in our code that Coverity incorrectly
4733 believed might have memory leaks. Closes ticket 30147.
4734 - Remove redundant return values in crypto_format, and the
4735 associated return value checks elsewhere in the code. Make the
4736 implementations in crypto_format consistent, and remove redundant
4737 code. Resolves ticket 29660.
4738 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
4739 it is not a constant-time function. Closes ticket 30309.
4740 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
4741 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
4742 bugfix on 0.3.2.1-alpha.
4743 - Simplify v3 onion service link specifier handling code. Fixes bug
4744 23576; bugfix on 0.3.2.1-alpha.
4745 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
4746 code. Resolves ticket 29108.
4747 - Split control.c into several submodules, in preparation for
4748 distributing its current responsibilities throughout the codebase.
4749 Closes ticket 29894.
4750 - Start to move responsibility for knowing about periodic events to
4751 the appropriate subsystems, so that the mainloop doesn't need to
4752 know all the periodic events in the rest of the codebase.
4753 Implements tickets 30293 and 30294.
4756 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
4757 Closes ticket 30630.
4758 - Document how to find git commits and tags for bug fixes in
4759 CodingStandards.md. Update some file documentation. Closes
4763 - Remove the linux-tor-prio.sh script from contrib/operator-tools
4764 directory. Resolves issue 29434.
4765 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
4766 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
4770 - Specify torrc paths (with empty files) when launching tor in
4771 integration tests; refrain from reading user and system torrcs.
4772 Resolves issue 29702.
4774 o Code simplification and refactoring (shell scripts):
4775 - Clean up many of our shell scripts to fix shellcheck warnings.
4776 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
4777 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
4778 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
4779 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
4780 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
4781 nagios-check-tor-authority-cert (ticket 29071),
4782 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
4783 (ticket 29060), test_key_expiration.sh (ticket 30002),
4784 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
4787 o Testing (chutney):
4788 - In "make test-network-all", test IPv6-only v3 single onion
4789 services, using the chutney network single-onion-v23-ipv6-md.
4790 Closes ticket 27251.
4792 o Testing (continuous integration):
4793 - In Travis, make stem log a controller trace to the console, and tail
4794 stem's tor log after failure. Closes ticket 30591.
4795 - In Travis, only run the stem tests that use a tor binary.
4796 Closes ticket 30694.
4799 Changes in version 0.4.0.5 - 2019-05-02
4800 This is the first stable release in the 0.4.0.x series. It contains
4801 improvements for power management and bootstrap reporting, as well as
4802 preliminary backend support for circuit padding to prevent some kinds
4803 of traffic analysis. It also continues our work in refactoring Tor for
4804 long-term maintainability.
4806 Per our support policy, we will support the 0.4.0.x series for nine
4807 months, or until three months after the release of a stable 0.4.1.x:
4808 whichever is longer. If you need longer-term support, please stick
4809 with 0.3.5.x, which will we plan to support until Feb 2022.
4811 Below are the changes since 0.3.5.7. For a complete list of changes
4812 since 0.4.0.4-rc, see the ChangeLog file.
4814 o Major features (battery management, client, dormant mode):
4815 - When Tor is running as a client, and it is unused for a long time,
4816 it can now enter a "dormant" state. When Tor is dormant, it avoids
4817 network and CPU activity until it is reawoken either by a user
4818 request or by a controller command. For more information, see the
4819 configuration options starting with "Dormant". Implements tickets
4821 - The client's memory of whether it is "dormant", and how long it
4822 has spent idle, persists across invocations. Implements
4824 - There is a DormantOnFirstStartup option that integrators can use
4825 if they expect that in many cases, Tor will be installed but
4828 o Major features (bootstrap reporting):
4829 - When reporting bootstrap progress, report the first connection
4830 uniformly, regardless of whether it's a connection for building
4831 application circuits. This allows finer-grained reporting of early
4832 progress than previously possible, with the improvements of ticket
4833 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
4834 - When reporting bootstrap progress, treat connecting to a proxy or
4835 pluggable transport as separate from having successfully used that
4836 proxy or pluggable transport to connect to a relay. Closes tickets
4839 o Major features (circuit padding):
4840 - Implement preliminary support for the circuit padding portion of
4841 Proposal 254. The implementation supports Adaptive Padding (aka
4842 WTF-PAD) state machines for use between experimental clients and
4843 relays. Support is also provided for APE-style state machines that
4844 use probability distributions instead of histograms to specify
4845 inter-packet delay. At the moment, Tor does not provide any
4846 padding state machines that are used in normal operation: for now,
4847 this feature exists solely for experimentation. Closes
4850 o Major features (refactoring):
4851 - Tor now uses an explicit list of its own subsystems when
4852 initializing and shutting down. Previously, these systems were
4853 managed implicitly in various places throughout the codebase.
4854 (There may still be some subsystems using the old system.) Closes
4857 o Major bugfixes (cell scheduler, KIST, security):
4858 - Make KIST consider the outbuf length when computing what it can
4859 put in the outbuf. Previously, KIST acted as though the outbuf
4860 were empty, which could lead to the outbuf becoming too full. It
4861 is possible that an attacker could exploit this bug to cause a Tor
4862 client or relay to run out of memory and crash. Fixes bug 29168;
4863 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4864 TROVE-2019-001 and CVE-2019-8955.
4866 o Major bugfixes (networking):
4867 - Gracefully handle empty username/password fields in SOCKS5
4868 username/password auth message and allow SOCKS5 handshake to
4869 continue. Previously, we had rejected these handshakes, breaking
4870 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
4872 o Major bugfixes (NSS, relay):
4873 - When running with NSS, disable TLS 1.2 ciphersuites that use
4874 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
4875 these ciphersuites don't work -- which caused relays to fail to
4876 handshake with one another when these ciphersuites were enabled.
4877 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
4879 o Major bugfixes (windows, startup):
4880 - When reading a consensus file from disk, detect whether it was
4881 written in text mode, and re-read it in text mode if so. Always
4882 write consensus files in binary mode so that we can map them into
4883 memory later. Previously, we had written in text mode, which
4884 confused us when we tried to map the file on windows. Fixes bug
4885 28614; bugfix on 0.4.0.1-alpha.
4887 o Minor features (address selection):
4888 - Treat the subnet 100.64.0.0/10 as public for some purposes;
4889 private for others. This subnet is the RFC 6598 (Carrier Grade
4890 NAT) IP range, and is deployed by many ISPs as an alternative to
4891 RFC 1918 that does not break existing internal networks. Tor now
4892 blocks SOCKS and control ports on these addresses and warns users
4893 if client ports or ExtORPorts are listening on a RFC 6598 address.
4894 Closes ticket 28525. Patch by Neel Chauhan.
4896 o Minor features (bandwidth authority):
4897 - Make bandwidth authorities ignore relays that are reported in the
4898 bandwidth file with the flag "vote=0". This change allows us to
4899 report unmeasured relays for diagnostic reasons without including
4900 their bandwidth in the bandwidth authorities' vote. Closes
4902 - When a directory authority is using a bandwidth file to obtain the
4903 bandwidth values that will be included in the next vote, serve
4904 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
4907 o Minor features (bootstrap reporting):
4908 - When reporting bootstrap progress, stop distinguishing between
4909 situations where only internal paths are available and situations
4910 where external paths are available. Previously, Tor would often
4911 erroneously report that it had only internal paths. Closes
4914 o Minor features (compilation):
4915 - Compile correctly when OpenSSL is built with engine support
4916 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4917 Patches from "Mangix".
4919 o Minor features (continuous integration):
4920 - On Travis Rust builds, cleanup Rust registry and refrain from
4921 caching the "target/" directory to speed up builds. Resolves
4923 - Log Python version during each Travis CI job. Resolves
4925 - In Travis, tell timelimit to use stem's backtrace signals, and
4926 launch python directly from timelimit, so python receives the
4927 signals from timelimit, rather than make. Closes ticket 30117.
4929 o Minor features (controller):
4930 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
4931 Implements ticket 28843.
4933 o Minor features (developer tooling):
4934 - Check that bugfix versions in changes files look like Tor versions
4935 from the versions spec. Warn when bugfixes claim to be on a future
4936 release. Closes ticket 27761.
4937 - Provide a git pre-commit hook that disallows committing if we have
4938 any failures in our code and changelog formatting checks. It is
4939 now available in scripts/maint/pre-commit.git-hook. Implements
4941 - Provide a git hook script to prevent "fixup!" and "squash!"
4942 commits from ending up in the master branch, as scripts/main/pre-
4943 push.git-hook. Closes ticket 27993.
4945 o Minor features (diagnostic):
4946 - Add more diagnostic log messages in an attempt to solve the issue
4947 of NUL bytes appearing in a microdescriptor cache. Related to
4950 o Minor features (directory authority):
4951 - When a directory authority is using a bandwidth file to obtain
4952 bandwidth values, include the digest of that file in the vote.
4953 Closes ticket 26698.
4954 - Directory authorities support a new consensus algorithm, under
4955 which the family lines in microdescriptors are encoded in a
4956 canonical form. This change makes family lines more compressible
4957 in transit, and on the client. Closes ticket 28266; implements
4960 o Minor features (directory authority, relay):
4961 - Authorities now vote on a "StaleDesc" flag to indicate that a
4962 relay's descriptor is so old that the relay should upload again
4963 soon. Relays treat this flag as a signal to upload a new
4964 descriptor. This flag will eventually let us remove the
4965 'published' date from routerstatus entries, and make our consensus
4966 diffs much smaller. Closes ticket 26770; implements proposal 293.
4968 o Minor features (dormant mode):
4969 - Add a DormantCanceledByStartup option to tell Tor that it should
4970 treat a startup event as cancelling any previous dormant state.
4971 Integrators should use this option with caution: it should only be
4972 used if Tor is being started because of something that the user
4973 did, and not if Tor is being automatically started in the
4974 background. Closes ticket 29357.
4976 o Minor features (fallback directory mirrors):
4977 - Update the fallback whitelist based on operator opt-ins and opt-
4978 outs. Closes ticket 24805, patch by Phoul.
4980 o Minor features (FreeBSD):
4981 - On FreeBSD-based systems, warn relay operators if the
4982 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
4983 Closes ticket 28518.
4985 o Minor features (geoip):
4986 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
4987 Country database. Closes ticket 29992.
4989 o Minor features (HTTP standards compliance):
4990 - Stop sending the header "Content-type: application/octet-stream"
4991 along with transparently compressed documents: this confused
4992 browsers. Closes ticket 28100.
4994 o Minor features (IPv6):
4995 - We add an option ClientAutoIPv6ORPort, to make clients randomly
4996 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
4997 every time a node is loaded from a new consensus or bridge config.
4998 We expect that this option will enable clients to bootstrap more
4999 quickly without having to determine whether they support IPv4,
5000 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
5001 - When using addrs_in_same_network_family(), avoid choosing circuit
5002 paths that pass through the same IPv6 subnet more than once.
5003 Previously, we only checked IPv4 subnets. Closes ticket 24393.
5004 Patch by Neel Chauhan.
5006 o Minor features (log messages):
5007 - Improve log message in v3 onion services that could print out
5008 negative revision counters. Closes ticket 27707. Patch
5011 o Minor features (memory usage):
5012 - Save memory by storing microdescriptor family lists with a more
5013 compact representation. Closes ticket 27359.
5014 - Tor clients now use mmap() to read consensus files from disk, so
5015 that they no longer need keep the full text of a consensus in
5016 memory when parsing it or applying a diff. Closes ticket 27244.
5018 o Minor features (NSS, diagnostic):
5019 - Try to log an error from NSS (if there is any) and a more useful
5020 description of our situation if we are using NSS and a call to
5021 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
5023 o Minor features (parsing):
5024 - Directory authorities now validate that router descriptors and
5025 ExtraInfo documents are in a valid subset of UTF-8, and reject
5026 them if they are not. Closes ticket 27367.
5028 o Minor features (performance):
5029 - Cache the results of summarize_protocol_flags(), so that we don't
5030 have to parse the same protocol-versions string over and over.
5031 This should save us a huge number of malloc calls on startup, and
5032 may reduce memory fragmentation with some allocators. Closes
5034 - Remove a needless memset() call from get_token_arguments, thereby
5035 speeding up the tokenization of directory objects by about 20%.
5036 Closes ticket 28852.
5037 - Replace parse_short_policy() with a faster implementation, to
5038 improve microdescriptor parsing time. Closes ticket 28853.
5039 - Speed up directory parsing a little by avoiding use of the non-
5040 inlined strcmp_len() function. Closes ticket 28856.
5041 - Speed up microdescriptor parsing by about 30%, to help improve
5042 startup time. Closes ticket 28839.
5044 o Minor features (pluggable transports):
5045 - Add support for emitting STATUS updates to Tor's control port from
5046 a pluggable transport process. Closes ticket 28846.
5047 - Add support for logging to Tor's logging subsystem from a
5048 pluggable transport process. Closes ticket 28180.
5050 o Minor features (process management):
5051 - Add a new process API for handling child processes. This new API
5052 allows Tor to have bi-directional communication with child
5053 processes on both Unix and Windows. Closes ticket 28179.
5054 - Use the subsystem manager to initialize and shut down the process
5055 module. Closes ticket 28847.
5057 o Minor features (relay):
5058 - When listing relay families, list them in canonical form including
5059 the relay's own identity, and try to give a more useful set of
5060 warnings. Part of ticket 28266 and proposal 298.
5062 o Minor features (required protocols):
5063 - Before exiting because of a missing required protocol, Tor will
5064 now check the publication time of the consensus, and not exit
5065 unless the consensus is newer than the Tor program's own release
5066 date. Previously, Tor would not check the consensus publication
5067 time, and so might exit because of a missing protocol that might
5068 no longer be required in a current consensus. Implements proposal
5069 297; closes ticket 27735.
5071 o Minor features (testing):
5072 - Treat all unexpected ERR and BUG messages as test failures. Closes
5074 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
5075 networks. Closes ticket 28840. Patch by Rob Jansen.
5076 - Use the approx_time() function when setting the "Expires" header
5077 in directory replies, to make them more testable. Needed for
5080 o Minor bugfixes (security):
5081 - Fix a potential double free bug when reading huge bandwidth files.
5082 The issue is not exploitable in the current Tor network because
5083 the vulnerable code is only reached when directory authorities
5084 read bandwidth files, but bandwidth files come from a trusted
5085 source (usually the authorities themselves). Furthermore, the
5086 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
5087 which are not used by any of the current authorities. Fixes bug
5088 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
5090 - Verify in more places that we are not about to create a buffer
5091 with more than INT_MAX bytes, to avoid possible OOB access in the
5092 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
5093 fixed by Tobias Stoeckmann.
5095 o Minor bugfix (continuous integration):
5096 - Reset coverage state on disk after Travis CI has finished. This
5097 should prevent future coverage merge errors from causing the test
5098 suite for the "process" subsystem to fail. The process subsystem
5099 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
5101 - Terminate test-stem if it takes more than 9.5 minutes to run.
5102 (Travis terminates the job after 10 minutes of no output.)
5103 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
5105 o Minor bugfixes (build, compatibility, rust):
5106 - Update Cargo.lock file to match the version made by the latest
5107 version of Rust, so that "make distcheck" will pass again. Fixes
5108 bug 29244; bugfix on 0.3.3.4-alpha.
5110 o Minor bugfixes (C correctness):
5111 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
5112 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
5115 o Minor bugfixes (client, clock skew):
5116 - Bootstrap successfully even when Tor's clock is behind the clocks
5117 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
5118 - Select guards even if the consensus has expired, as long as the
5119 consensus is still reasonably live. Fixes bug 24661; bugfix
5122 o Minor bugfixes (compilation):
5123 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
5124 29169; bugfix on 0.4.0.1-alpha.
5125 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
5126 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
5127 - Compile correctly on OpenBSD; previously, we were missing some
5128 headers required in order to detect it properly. Fixes bug 28938;
5129 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5131 o Minor bugfixes (directory clients):
5132 - Mark outdated dirservers when Tor only has a reasonably live
5133 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
5135 o Minor bugfixes (directory mirrors):
5136 - Even when a directory mirror's clock is behind the clocks on the
5137 authorities, we now allow the mirror to serve "future"
5138 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
5140 o Minor bugfixes (DNS):
5141 - Gracefully handle an empty or absent resolve.conf file by falling
5142 back to using "localhost" as a DNS server (and hoping it works).
5143 Previously, we would just stop running as an exit. Fixes bug
5144 21900; bugfix on 0.2.1.10-alpha.
5146 o Minor bugfixes (documentation):
5147 - Describe the contents of the v3 onion service client authorization
5148 files correctly: They hold public keys, not private keys. Fixes
5149 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
5151 o Minor bugfixes (guards):
5152 - In count_acceptable_nodes(), the minimum number is now one bridge
5153 or guard node, and two non-guard nodes for a circuit. Previously,
5154 we had added up the sum of all nodes with a descriptor, but that
5155 could cause us to build failing circuits when we had either too
5156 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
5157 0.2.3.1-alpha. Patch by Neel Chauhan.
5159 o Minor bugfixes (IPv6):
5160 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
5161 IPv6 socket was bound using an address family of AF_INET instead
5162 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
5165 o Minor bugfixes (linux seccomp sandbox):
5166 - Fix startup crash when experimental sandbox support is enabled.
5167 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
5169 o Minor bugfixes (logging):
5170 - Correct a misleading error message when IPv4Only or IPv6Only is
5171 used but the resolved address can not be interpreted as an address
5172 of the specified IP version. Fixes bug 13221; bugfix on
5173 0.2.3.9-alpha. Patch from Kris Katterjohn.
5174 - Log the correct port number for listening sockets when "auto" is
5175 used to let Tor pick the port number. Previously, port 0 was
5176 logged instead of the actual port number. Fixes bug 29144; bugfix
5177 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5178 - Stop logging a BUG() warning when Tor is waiting for exit
5179 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
5180 - Avoid logging that we are relaxing a circuit timeout when that
5181 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
5182 - Log more information at "warning" level when unable to read a
5183 private key; log more information at "info" level when unable to
5184 read a public key. We had warnings here before, but they were lost
5185 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
5186 - Rework rep_hist_log_link_protocol_counts() to iterate through all
5187 link protocol versions when logging incoming/outgoing connection
5188 counts. Tor no longer skips version 5, and we won't have to
5189 remember to update this function when new link protocol version is
5190 developed. Fixes bug 28920; bugfix on 0.2.6.10.
5192 o Minor bugfixes (memory management):
5193 - Refactor the shared random state's memory management so that it
5194 actually takes ownership of the shared random value pointers.
5195 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
5196 - Stop leaking parts of the shared random state in the shared-random
5197 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
5199 o Minor bugfixes (misc):
5200 - The amount of total available physical memory is now determined
5201 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
5202 when it is defined and a 64-bit variant is not available. Fixes
5203 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
5205 o Minor bugfixes (networking):
5206 - Introduce additional checks into tor_addr_parse() to reject
5207 certain incorrect inputs that previously were not detected. Fixes
5208 bug 23082; bugfix on 0.2.0.10-alpha.
5210 o Minor bugfixes (onion service v3, client):
5211 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
5212 connection waiting for a descriptor that we actually have in the
5213 cache. It turns out that this can actually happen, though it is
5214 rare. Now, tor will recover and retry the descriptor. Fixes bug
5215 28669; bugfix on 0.3.2.4-alpha.
5217 o Minor bugfixes (onion services):
5218 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
5219 than one private key for a hidden service. Fixes bug 29040; bugfix
5221 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
5222 "debug" level. Tor used to log it as a warning, which caused very
5223 long log lines to appear for some users. Fixes bug 29135; bugfix
5225 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5226 as a warning. Instead, log it as a protocol warning, because there
5227 is nothing that relay operators can do to fix it. Fixes bug 29029;
5228 bugfix on 0.2.5.7-rc.
5230 o Minor bugfixes (periodic events):
5231 - Refrain from calling routerlist_remove_old_routers() from
5232 check_descriptor_callback(). Instead, create a new hourly periodic
5233 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
5235 o Minor bugfixes (pluggable transports):
5236 - Make sure that data is continously read from standard output and
5237 standard error pipes of a pluggable transport child-process, to
5238 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
5239 bugfix on 0.2.3.6-alpha.
5241 o Minor bugfixes (rust):
5242 - Abort on panic in all build profiles, instead of potentially
5243 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
5245 o Minor bugfixes (scheduler):
5246 - When re-adding channels to the pending list, check the correct
5247 channel's sched_heap_idx. This issue has had no effect in mainline
5248 Tor, but could have led to bugs down the road in improved versions
5249 of our circuit scheduling code. Fixes bug 29508; bugfix
5252 o Minor bugfixes (shellcheck):
5253 - Look for scripts in their correct locations during "make
5254 shellcheck". Previously we had looked in the wrong place during
5255 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
5257 o Minor bugfixes (single onion services):
5258 - Allow connections to single onion services to remain idle without
5259 being disconnected. Previously, relays acting as rendezvous points
5260 for single onion services were mistakenly closing idle rendezvous
5261 circuits after 60 seconds, thinking that they were unused
5262 directory-fetching circuits that had served their purpose. Fixes
5263 bug 29665; bugfix on 0.2.1.26.
5265 o Minor bugfixes (stats):
5266 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
5267 relay and bridge extra-info documents. Fixes bug 29017; bugfix
5270 o Minor bugfixes (testing):
5271 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
5272 recent test-network.sh to use new chutney features in CI. Fixes
5273 bug 29703; bugfix on 0.2.9.1-alpha.
5274 - Fix a test failure on Windows caused by an unexpected "BUG"
5275 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
5277 - Downgrade some LOG_ERR messages in the address/* tests to
5278 warnings. The LOG_ERR messages were occurring when we had no
5279 configured network. We were failing the unit tests, because we
5280 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
5281 29530; bugfix on 0.3.5.8.
5282 - Fix our gcov wrapper script to look for object files at the
5283 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
5284 - Decrease the false positive rate of stochastic probability
5285 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
5286 - Fix intermittent failures on an adaptive padding test. Fixes one
5287 case of bug 29122; bugfix on 0.4.0.1-alpha.
5288 - Disable an unstable circuit-padding test that was failing
5289 intermittently because of an ill-defined small histogram. Such
5290 histograms will be allowed again after 29298 is implemented. Fixes
5291 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
5292 - Detect and suppress "bug" warnings from the util/time test on
5293 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
5294 - Do not log an error-level message if we fail to find an IPv6
5295 network interface from the unit tests. Fixes bug 29160; bugfix
5297 - Instead of relying on hs_free_all() to clean up all onion service
5298 objects in test_build_descriptors(), we now deallocate them one by
5299 one. This lets Coverity know that we are not leaking memory there
5300 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
5301 - Check the time in the "Expires" header using approx_time(). Fixes
5302 bug 30001; bugfix on 0.4.0.4-rc.
5304 o Minor bugfixes (TLS protocol):
5305 - When classifying a client's selection of TLS ciphers, if the
5306 client ciphers are not yet available, do not cache the result.
5307 Previously, we had cached the unavailability of the cipher list
5308 and never looked again, which in turn led us to assume that the
5309 client only supported the ancient V1 link protocol. This, in turn,
5310 was causing Stem integration tests to stall in some cases. Fixes
5311 bug 30021; bugfix on 0.2.4.8-alpha.
5313 o Minor bugfixes (UI):
5314 - Lower log level of unlink() errors during bootstrap. Fixes bug
5315 29930; bugfix on 0.4.0.1-alpha.
5317 o Minor bugfixes (usability):
5318 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
5319 Some users took this phrasing to mean that the mentioned guard was
5320 under their control or responsibility, which it is not. Fixes bug
5321 28895; bugfix on Tor 0.3.0.1-alpha.
5323 o Minor bugfixes (Windows, CI):
5324 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
5325 Windows Server 2012 R2 job. The remaining 2 jobs still provide
5326 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
5327 fast_finish, so failed jobs terminate the build immediately. Fixes
5328 bug 29601; bugfix on 0.3.5.4-alpha.
5330 o Code simplification and refactoring:
5331 - Introduce a connection_dir_buf_add() helper function that detects
5332 whether compression is in use, and adds a string accordingly.
5333 Resolves issue 28816.
5334 - Refactor handle_get_next_bandwidth() to use
5335 connection_dir_buf_add(). Implements ticket 29897.
5336 - Reimplement NETINFO cell parsing and generation to rely on
5337 trunnel-generated wire format handling code. Closes ticket 27325.
5338 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
5340 - Rework SOCKS wire format handling to rely on trunnel-generated
5341 parsing/generation code. Resolves ticket 27620.
5342 - Split out bootstrap progress reporting from control.c into a
5343 separate file. Part of ticket 27402.
5344 - The .may_include files that we use to describe our directory-by-
5345 directory dependency structure now describe a noncircular
5346 dependency graph over the directories that they cover. Our
5347 checkIncludes.py tool now enforces this noncircularity. Closes
5351 - Clarify that Tor performs stream isolation among *Port listeners
5352 by default. Resolves issue 29121.
5353 - In the manpage entry describing MapAddress torrc setting, use
5354 example IP addresses from ranges specified for use in documentation
5355 by RFC 5737. Resolves issue 28623.
5356 - Mention that you cannot add a new onion service if Tor is already
5357 running with Sandbox enabled. Closes ticket 28560.
5358 - Improve ControlPort documentation. Mention that it accepts
5359 address:port pairs, and can be used multiple times. Closes
5361 - Document the exact output of "tor --version". Closes ticket 28889.
5364 - Remove the old check-tor script. Resolves issue 29072.
5365 - Stop responding to the 'GETINFO status/version/num-concurring' and
5366 'GETINFO status/version/num-versioning' control port commands, as
5367 those were deprecated back in 0.2.0.30. Also stop listing them in
5368 output of 'GETINFO info/names'. Resolves ticket 28757.
5369 - The scripts used to generate and maintain the list of fallback
5370 directories have been extracted into a new "fallback-scripts"
5371 repository. Closes ticket 27914.
5374 - Run shellcheck for scripts in the in scripts/ directory. Closes
5376 - Add unit tests for tokenize_string() and get_next_token()
5377 functions. Resolves ticket 27625.
5379 o Code simplification and refactoring (onion service v3):
5380 - Consolidate the authorized client descriptor cookie computation
5381 code from client and service into one function. Closes
5384 o Code simplification and refactoring (shell scripts):
5385 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
5387 - Fix issues that shellcheck found in chutney-git-bisect.sh.
5388 Resolves ticket 28006.
5389 - Fix issues that shellcheck found in updateRustDependencies.sh.
5390 Resolves ticket 28012.
5391 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
5392 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
5393 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
5394 - Fix shellcheck warnings in scripts/test/coverage. Resolves
5398 Changes in version 0.3.5.8 - 2019-02-21
5399 Tor 0.3.5.8 backports several fixes from later releases, including fixes
5400 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
5403 It also includes a fix for a medium-severity security bug affecting Tor
5404 0.3.2.1-alpha and later. All Tor instances running an affected release
5405 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5407 o Major bugfixes (cell scheduler, KIST, security):
5408 - Make KIST consider the outbuf length when computing what it can
5409 put in the outbuf. Previously, KIST acted as though the outbuf
5410 were empty, which could lead to the outbuf becoming too full. It
5411 is possible that an attacker could exploit this bug to cause a Tor
5412 client or relay to run out of memory and crash. Fixes bug 29168;
5413 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5414 TROVE-2019-001 and CVE-2019-8955.
5416 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
5417 - Gracefully handle empty username/password fields in SOCKS5
5418 username/password auth messsage and allow SOCKS5 handshake to
5419 continue. Previously, we had rejected these handshakes, breaking
5420 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
5422 o Minor features (compilation, backport from 0.4.0.2-alpha):
5423 - Compile correctly when OpenSSL is built with engine support
5424 disabled, or with deprecated APIs disabled. Closes ticket 29026.
5425 Patches from "Mangix".
5427 o Minor features (geoip):
5428 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5429 Country database. Closes ticket 29478.
5431 o Minor features (testing, backport from 0.4.0.2-alpha):
5432 - Treat all unexpected ERR and BUG messages as test failures. Closes
5435 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
5436 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
5437 connection waiting for a descriptor that we actually have in the
5438 cache. It turns out that this can actually happen, though it is
5439 rare. Now, tor will recover and retry the descriptor. Fixes bug
5440 28669; bugfix on 0.3.2.4-alpha.
5442 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
5443 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
5444 IPv6 socket was bound using an address family of AF_INET instead
5445 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
5448 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5449 - Update Cargo.lock file to match the version made by the latest
5450 version of Rust, so that "make distcheck" will pass again. Fixes
5451 bug 29244; bugfix on 0.3.3.4-alpha.
5453 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
5454 - Select guards even if the consensus has expired, as long as the
5455 consensus is still reasonably live. Fixes bug 24661; bugfix
5458 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
5459 - Compile correctly on OpenBSD; previously, we were missing some
5460 headers required in order to detect it properly. Fixes bug 28938;
5461 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5463 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
5464 - Describe the contents of the v3 onion service client authorization
5465 files correctly: They hold public keys, not private keys. Fixes
5466 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
5468 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
5469 - Rework rep_hist_log_link_protocol_counts() to iterate through all
5470 link protocol versions when logging incoming/outgoing connection
5471 counts. Tor no longer skips version 5, and we won't have to
5472 remember to update this function when new link protocol version is
5473 developed. Fixes bug 28920; bugfix on 0.2.6.10.
5475 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
5476 - Log more information at "warning" level when unable to read a
5477 private key; log more information at "info" level when unable to
5478 read a public key. We had warnings here before, but they were lost
5479 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
5481 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
5482 - The amount of total available physical memory is now determined
5483 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
5484 when it is defined and a 64-bit variant is not available. Fixes
5485 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
5487 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5488 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
5489 than one private key for a hidden service. Fixes bug 29040; bugfix
5491 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
5492 "debug" level. Tor used to log it as a warning, which caused very
5493 long log lines to appear for some users. Fixes bug 29135; bugfix
5495 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5496 as a warning. Instead, log it as a protocol warning, because there
5497 is nothing that relay operators can do to fix it. Fixes bug 29029;
5498 bugfix on 0.2.5.7-rc.
5500 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
5501 - Mark outdated dirservers when Tor only has a reasonably live
5502 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
5504 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
5505 - Detect and suppress "bug" warnings from the util/time test on
5506 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
5507 - Do not log an error-level message if we fail to find an IPv6
5508 network interface from the unit tests. Fixes bug 29160; bugfix
5511 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
5512 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
5513 Some users took this phrasing to mean that the mentioned guard was
5514 under their control or responsibility, which it is not. Fixes bug
5515 28895; bugfix on Tor 0.3.0.1-alpha.
5518 Changes in version 0.3.4.11 - 2019-02-21
5519 Tor 0.3.4.11 is the third stable release in its series. It includes
5520 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
5521 later. All Tor instances running an affected release should upgrade to
5522 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5524 o Major bugfixes (cell scheduler, KIST, security):
5525 - Make KIST consider the outbuf length when computing what it can
5526 put in the outbuf. Previously, KIST acted as though the outbuf
5527 were empty, which could lead to the outbuf becoming too full. It
5528 is possible that an attacker could exploit this bug to cause a Tor
5529 client or relay to run out of memory and crash. Fixes bug 29168;
5530 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5531 TROVE-2019-001 and CVE-2019-8955.
5533 o Minor features (geoip):
5534 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5535 Country database. Closes ticket 29478.
5537 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5538 - Update Cargo.lock file to match the version made by the latest
5539 version of Rust, so that "make distcheck" will pass again. Fixes
5540 bug 29244; bugfix on 0.3.3.4-alpha.
5542 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5543 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5544 as a warning. Instead, log it as a protocol warning, because there
5545 is nothing that relay operators can do to fix it. Fixes bug 29029;
5546 bugfix on 0.2.5.7-rc.
5549 Changes in version 0.3.3.12 - 2019-02-21
5550 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
5551 0.3.2.1-alpha and later. All Tor instances running an affected release
5552 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5554 This release marks the end of support for the Tor 0.3.3.x series. We
5555 recommend that users switch to either the Tor 0.3.4 series (supported
5556 until at least 10 June 2019), or the Tor 0.3.5 series, which will
5557 receive long-term support until at least 1 Feb 2022.
5559 o Major bugfixes (cell scheduler, KIST, security):
5560 - Make KIST consider the outbuf length when computing what it can
5561 put in the outbuf. Previously, KIST acted as though the outbuf
5562 were empty, which could lead to the outbuf becoming too full. It
5563 is possible that an attacker could exploit this bug to cause a Tor
5564 client or relay to run out of memory and crash. Fixes bug 29168;
5565 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5566 TROVE-2019-001 and CVE-2019-8955.
5568 o Minor features (geoip):
5569 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5570 Country database. Closes ticket 29478.
5572 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5573 - Update Cargo.lock file to match the version made by the latest
5574 version of Rust, so that "make distcheck" will pass again. Fixes
5575 bug 29244; bugfix on 0.3.3.4-alpha.
5577 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5578 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5579 as a warning. Instead, log it as a protocol warning, because there
5580 is nothing that relay operators can do to fix it. Fixes bug 29029;
5581 bugfix on 0.2.5.7-rc.
5584 Changes in version 0.3.3.11 - 2019-01-07
5585 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
5586 numerous fixes, including an important fix for anyone using OpenSSL
5587 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
5588 to this version, or to a later series.
5590 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
5591 We anticipate that this will be the last release of Tor 0.3.3, unless
5592 some major bug is before then. Some time between now and then, users
5593 should switch to either the Tor 0.3.4 series (supported until at least
5594 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
5595 support until at least 1 Feb 2022.
5597 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
5598 - Fix our usage of named groups when running as a TLS 1.3 client in
5599 OpenSSL 1.1.1. Previously, we only initialized EC groups when
5600 running as a relay, which caused clients to fail to negotiate TLS
5601 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
5604 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
5605 - Fix a use-after-free error that could be caused by passing Tor an
5606 impossible set of options that would fail during options_act().
5607 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5609 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
5610 - Only run one online rust build in Travis, to reduce network
5611 errors. Skip offline rust builds on Travis for Linux gcc, because
5612 they're redundant. Implements ticket 27252.
5613 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5614 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5615 Linux with default settings, because all the non-default builds
5616 use gcc on Linux. Implements ticket 27252.
5618 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5619 - Use the Travis Homebrew addon to install packages on macOS during
5620 Travis CI. The package list is the same, but the Homebrew addon
5621 does not do a `brew update` by default. Implements ticket 27738.
5623 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
5624 - Replace the 150 fallbacks originally introduced in Tor
5625 0.3.3.1-alpha in January 2018 (of which ~115 were still
5626 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
5627 removed) generated in December 2018. Closes ticket 24803.
5629 o Minor features (geoip):
5630 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
5631 Country database. Closes ticket 29012.
5633 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
5634 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
5635 key export function from handling long labels. When this bug is
5636 detected, Tor will disable TLS 1.3. We recommend upgrading to a
5637 version of OpenSSL without this bug when it becomes available.
5638 Closes ticket 28973.
5640 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
5641 - Update relay descriptor on bandwidth changes only when the uptime
5642 is smaller than 24h, in order to reduce the efficiency of guard
5643 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5645 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
5646 - Avoid undefined behavior in an end-of-string check when parsing
5647 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5650 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5651 - Rewrite our assertion macros so that they no longer suppress the
5652 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5654 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
5655 - Initialize a variable unconditionally in aes_new_cipher(), since
5656 some compilers cannot tell that we always initialize it before
5657 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
5659 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
5660 - Log additional info when we get a relay that shares an ed25519 ID
5661 with a different relay, instead making a BUG() warning. Fixes bug
5662 27800; bugfix on 0.3.2.1-alpha.
5664 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
5665 - When a user requests a group-readable DataDirectory, give it to
5666 them. Previously, when the DataDirectory and the CacheDirectory
5667 were the same, the default setting (0) for
5668 CacheDirectoryGroupReadable would override the setting for
5669 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5672 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5673 - When the onion service directory can't be created or has the wrong
5674 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5677 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5678 - Close all SOCKS request (for the same .onion) if the newly fetched
5679 descriptor is unusable. Before that, we would close only the first
5680 one leaving the other hanging and let to time out by themselves.
5681 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5683 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5684 - Don't warn so loudly when Tor is unable to decode an onion
5685 descriptor. This can now happen as a normal use case if a client
5686 gets a descriptor with client authorization but the client is not
5687 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5689 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
5690 - When deleting an ephemeral onion service (DEL_ONION), do not close
5691 any rendezvous circuits in order to let the existing client
5692 connections finish by themselves or closed by the application. The
5693 HS v2 is doing that already so now we have the same behavior for
5694 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5696 o Minor bugfixes (HTTP tunnel):
5697 - Fix a bug warning when closing an HTTP tunnel connection due to
5698 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
5701 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
5702 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5703 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5705 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5706 - Ensure circuitmux queues are empty before scheduling or sending
5707 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5709 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5710 - Reject protocol names containing bytes other than alphanumeric
5711 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5714 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5715 - Compute protover votes correctly in the rust version of the
5716 protover code. Previously, the protover rewrite in 24031 allowed
5717 repeated votes from the same voter for the same protocol version
5718 to be counted multiple times in protover_compute_vote(). Fixes bug
5719 27649; bugfix on 0.3.3.5-rc.
5720 - Reject protover names that contain invalid characters. Fixes bug
5721 27687; bugfix on 0.3.3.1-alpha.
5723 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5724 - protover_all_supported() would attempt to allocate up to 16GB on
5725 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5726 bugfix on 0.3.3.5-rc.
5728 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
5729 - Fix a potential null dereference in protover_all_supported(). Add
5730 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5731 - Return a string that can be safely freed by C code, not one
5732 created by the rust allocator, in protover_all_supported(). Fixes
5733 bug 27740; bugfix on 0.3.3.1-alpha.
5734 - Fix an API mismatch in the rust implementation of
5735 protover_compute_vote(). This bug could have caused crashes on any
5736 directory authorities running Tor with Rust (which we do not yet
5737 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5739 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5740 - If a unit test running in a subprocess exits abnormally or with a
5741 nonzero status code, treat the test as having failed, even if the
5742 test reported success. Without this fix, memory leaks don't cause
5743 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5744 bugfix on 0.2.2.4-alpha.
5746 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
5747 - Treat backtrace test failures as expected on BSD-derived systems
5748 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5749 (FreeBSD failures have been treated as expected since 18204 in
5750 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5752 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
5753 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5754 bugfix on 0.3.0.1-alpha.
5757 Changes in version 0.3.4.10 - 2019-01-07
5758 Tor 0.3.4.9 is the second stable release in its series; it backports
5759 numerous fixes, including an important fix for relays, and for anyone
5760 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
5763 As a reminder, the Tor 0.3.4 series will be supported until 10 June
5764 2019. Some time between now and then, users should switch to the Tor
5765 0.3.5 series, which will receive long-term support until at least 1
5768 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
5769 - Fix our usage of named groups when running as a TLS 1.3 client in
5770 OpenSSL 1.1.1. Previously, we only initialized EC groups when
5771 running as a relay, which caused clients to fail to negotiate TLS
5772 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
5775 o Major bugfixes (relay, directory, backport from 0.3.5.7):
5776 - Always reactivate linked connections in the main loop so long as
5777 any linked connection has been active. Previously, connections
5778 serving directory information wouldn't get reactivated after the
5779 first chunk of data was sent (usually 32KB), which would prevent
5780 clients from bootstrapping. Fixes bug 28912; bugfix on
5781 0.3.4.1-alpha. Patch by "cypherpunks3".
5783 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
5784 - Always show the configure and test logs, and upload them as build
5785 artifacts, when building for Windows using Appveyor CI.
5788 o Minor features (controller, backport from 0.3.5.1-alpha):
5789 - For purposes of CIRC_BW-based dropped cell detection, track half-
5790 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
5791 bias check cells to arrive without counting it as dropped until
5792 either the END arrives, or the windows are empty. Closes
5795 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
5796 - Replace the 150 fallbacks originally introduced in Tor
5797 0.3.3.1-alpha in January 2018 (of which ~115 were still
5798 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
5799 removed) generated in December 2018. Closes ticket 24803.
5801 o Minor features (geoip):
5802 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
5803 Country database. Closes ticket 28395.
5805 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
5806 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
5807 key export function from handling long labels. When this bug is
5808 detected, Tor will disable TLS 1.3. We recommend upgrading to a
5809 version of OpenSSL without this bug when it becomes available.
5810 Closes ticket 28973.
5812 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
5813 - Initialize a variable unconditionally in aes_new_cipher(), since
5814 some compilers cannot tell that we always initialize it before
5815 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
5817 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
5818 - Avoid a logging a BUG() stacktrace when closing connection held
5819 open because the write side is rate limited but not the read side.
5820 Now, the connection read side is simply shut down until Tor is
5821 able to flush the connection and close it. Fixes bug 27750; bugfix
5824 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
5825 - Manually configure the zstd compiler options, when building using
5826 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
5827 not come with a pkg-config file. Fixes bug 28454; bugfix
5829 - Stop using an external OpenSSL install, and stop installing MSYS2
5830 packages, when building using mingw on Appveyor Windows CI. Fixes
5831 bug 28399; bugfix on 0.3.4.1-alpha.
5833 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
5834 - Explicitly specify the path to the OpenSSL library and do not
5835 download OpenSSL from Pacman, but instead use the library that is
5836 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
5838 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
5839 - When a user requests a group-readable DataDirectory, give it to
5840 them. Previously, when the DataDirectory and the CacheDirectory
5841 were the same, the default setting (0) for
5842 CacheDirectoryGroupReadable would override the setting for
5843 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5846 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
5847 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5848 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5850 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5851 - Don't warn so loudly when Tor is unable to decode an onion
5852 descriptor. This can now happen as a normal use case if a client
5853 gets a descriptor with client authorization but the client is not
5854 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5856 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
5857 - When deleting an ephemeral onion service (DEL_ONION), do not close
5858 any rendezvous circuits in order to let the existing client
5859 connections finish by themselves or closed by the application. The
5860 HS v2 is doing that already so now we have the same behavior for
5861 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5863 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
5864 - Update relay descriptor on bandwidth changes only when the uptime
5865 is smaller than 24h, in order to reduce the efficiency of guard
5866 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5868 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
5869 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5870 bugfix on 0.3.0.1-alpha.
5873 Changes in version 0.3.5.7 - 2019-01-07
5874 Tor 0.3.5.7 is the first stable release in its series; it includes
5875 compilation and portability fixes, and a fix for a severe problem
5876 affecting directory caches.
5878 The Tor 0.3.5 series includes several new features and performance
5879 improvements, including client authorization for v3 onion services,
5880 cleanups to bootstrap reporting, support for improved bandwidth-
5881 measurement tools, experimental support for NSS in place of OpenSSL,
5882 and much more. It also begins a full reorganization of Tor's code
5883 layout, for improved modularity and maintainability in the future.
5884 Finally, there is the usual set of performance improvements and
5885 bugfixes that we try to do in every release series.
5887 There are a couple of changes in the 0.3.5 that may affect
5888 compatibility. First, the default version for newly created onion
5889 services is now v3. Use the HiddenServiceVersion option if you want to
5890 override this. Second, some log messages related to bootstrapping have
5891 changed; if you use stem, you may need to update to the latest version
5892 so it will recognize them.
5894 We have designated 0.3.5 as a "long-term support" (LTS) series: we
5895 will continue to patch major bugs in typical configurations of 0.3.5
5896 until at least 1 Feb 2022. (We do not plan to provide long-term
5897 support for embedding, Rust support, NSS support, running a directory
5898 authority, or unsupported platforms. For these, you will need to stick
5899 with the latest stable release.)
5901 Below are the changes since 0.3.4.9. For a complete list of changes
5902 since 0.3.5.6-rc, see the ChangeLog file.
5904 o Major features (bootstrap):
5905 - Don't report directory progress until after a connection to a
5906 relay or bridge has succeeded. Previously, we'd report 80%
5907 progress based on cached directory information when we couldn't
5908 even connect to the network. Closes ticket 27169.
5910 o Major features (new code layout):
5911 - Nearly all of Tor's source code has been moved around into more
5912 logical places. The "common" directory is now divided into a set
5913 of libraries in "lib", and files in the "or" directory have been
5914 split into "core" (logic absolutely needed for onion routing),
5915 "feature" (independent modules in Tor), and "app" (to configure
5916 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
5917 more information. Closes ticket 26481.
5919 This refactoring is not complete: although the libraries have been
5920 refactored to be acyclic, the main body of Tor is still too
5921 interconnected. We will attempt to improve this in the future.
5923 o Major features (onion services v3):
5924 - Implement onion service client authorization at the descriptor
5925 level: only authorized clients can decrypt a service's descriptor
5926 to find out how to contact it. A new torrc option was added to
5927 control this client side: ClientOnionAuthDir <path>. On the
5928 service side, if the "authorized_clients/" directory exists in the
5929 onion service directory path, client configurations are read from
5930 the files within. See the manpage for more details. Closes ticket
5931 27547. Patch done by Suphanat Chunhapanya (haxxpop).
5932 - Improve revision counter generation in next-gen onion services.
5933 Onion services can now scale by hosting multiple instances on
5934 different hosts without synchronization between them, which was
5935 previously impossible because descriptors would get rejected by
5936 HSDirs. Addresses ticket 25552.
5937 - Version 3 onion services can now use the per-service
5938 HiddenServiceExportCircuitID option to differentiate client
5939 circuits. It communicates with the service by using the HAProxy
5940 protocol to assign virtual IP addresses to inbound client
5941 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
5943 o Major features (onion services, UI change):
5944 - For a newly created onion service, the default version is now 3.
5945 Tor still supports existing version 2 services, but the operator
5946 now needs to set "HiddenServiceVersion 2" in order to create a new
5947 version 2 service. For existing services, Tor now learns the
5948 version by reading the key file. Closes ticket 27215.
5950 o Major features (portability, cryptography, experimental, TLS):
5951 - Tor now has the option to compile with the NSS library instead of
5952 OpenSSL. This feature is experimental, and we expect that bugs may
5953 remain. It is mainly intended for environments where Tor's
5954 performance is not CPU-bound, and where NSS is already known to be
5955 installed. To try it out, configure Tor with the --enable-nss
5956 flag. Closes tickets 26631, 26815, and 26816.
5958 If you are experimenting with this option and using an old cached
5959 consensus, Tor may fail to start. To solve this, delete your
5960 "cached-consensus" and "cached-microdesc-consensus" files,
5961 (if present), and restart Tor.
5963 o Major features (relay, UI change):
5964 - Relays no longer run as exits by default. If the "ExitRelay"
5965 option is auto (or unset), and no exit policy is specified with
5966 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
5967 Previously in this case, we allowed exit traffic and logged a
5968 warning message. Closes ticket 21530. Patch by Neel Chauhan.
5969 - Tor now validates that the ContactInfo config option is valid UTF-
5970 8 when parsing torrc. Closes ticket 27428.
5972 o Major bugfixes (compilation):
5973 - Fix compilation on ARM (and other less-used CPUs) when compiling
5974 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5976 o Major bugfixes (compilation, rust):
5977 - Rust tests can now build and run successfully with the
5978 --enable-fragile-hardening option enabled. Doing this currently
5979 requires the rust beta channel; it will be possible with stable
5980 rust once Rust version 1.31 is released. Patch from Alex Crichton.
5981 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
5983 o Major bugfixes (directory authority):
5984 - Actually check that the address we get from DirAuthority
5985 configuration line is valid IPv4. Explicitly disallow DirAuthority
5986 address to be a DNS hostname. Fixes bug 26488; bugfix
5989 o Major bugfixes (embedding, main loop):
5990 - When DisableNetwork becomes set, actually disable periodic events
5991 that are already enabled. (Previously, we would refrain from
5992 enabling new ones, but we would leave the old ones turned on.)
5993 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
5995 o Major bugfixes (main loop, bootstrap):
5996 - Make sure Tor bootstraps and works properly if only the
5997 ControlPort is set. Prior to this fix, Tor would only bootstrap
5998 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5999 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
6001 o Major bugfixes (onion service v3):
6002 - On an intro point for a version 3 onion service, stop closing
6003 introduction circuits on a NACK. This lets the client decide
6004 whether to reuse the circuit or discard it. Previously, we closed
6005 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
6006 0.3.2.1-alpha. Patch by Neel Chaunan.
6008 o Major bugfixes (OpenSSL, portability):
6009 - Fix our usage of named groups when running as a TLS 1.3 client in
6010 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6011 running as a relay, which caused clients to fail to negotiate TLS
6012 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6015 o Major bugfixes (relay bandwidth statistics):
6016 - When we close relayed circuits, report the data in the circuit
6017 queues as being written in our relay bandwidth stats. This
6018 mitigates guard discovery and other attacks that close circuits
6019 for the explicit purpose of noticing this discrepancy in
6020 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
6022 o Major bugfixes (relay):
6023 - When our write bandwidth limit is exhausted, stop writing on the
6024 connection. Previously, we had a typo in the code that would make
6025 us stop reading instead, leading to relay connections being stuck
6026 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
6028 - Always reactivate linked connections in the main loop so long as
6029 any linked connection has been active. Previously, connections
6030 serving directory information wouldn't get reactivated after the
6031 first chunk of data was sent (usually 32KB), which would prevent
6032 clients from bootstrapping. Fixes bug 28912; bugfix on
6033 0.3.4.1-alpha. Patch by "cypherpunks3".
6035 o Major bugfixes (restart-in-process):
6036 - Fix a use-after-free error that could be caused by passing Tor an
6037 impossible set of options that would fail during options_act().
6038 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6040 o Minor features (admin tools):
6041 - Add a new --key-expiration option to print the expiration date of
6042 the signing cert in an ed25519_signing_cert file. Resolves
6045 o Minor features (build):
6046 - If you pass the "--enable-pic" option to configure, Tor will try
6047 to tell the compiler to build position-independent code suitable
6048 to link into a dynamic library. (The default remains -fPIE, for
6049 code suitable for a relocatable executable.) Closes ticket 23846.
6051 o Minor features (code correctness, testing):
6052 - Tor's build process now includes a "check-includes" make target to
6053 verify that no module of Tor relies on any headers from a higher-
6054 level module. We hope to use this feature over time to help
6055 refactor our codebase. Closes ticket 26447.
6057 o Minor features (code layout):
6058 - We have a new "lowest-level" error-handling API for use by code
6059 invoked from within the logging module. With this interface, the
6060 logging code is no longer at risk of calling into itself if a
6061 failure occurs while it is trying to log something. Closes
6064 o Minor features (compilation):
6065 - When possible, place our warning flags in a separate file, to
6066 avoid flooding verbose build logs. Closes ticket 28924.
6067 - Tor's configure script now supports a --with-malloc= option to
6068 select your malloc implementation. Supported options are
6069 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
6070 default). Addresses part of ticket 20424. Based on a patch from
6073 o Minor features (config):
6074 - The "auto" keyword in torrc is now case-insensitive. Closes
6077 o Minor features (continuous integration):
6078 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
6080 - Add new CI job to Travis configuration to run stem-based
6081 integration tests. Closes ticket 27913.
6082 - Use the Travis Homebrew addon to install packages on macOS during
6083 Travis CI. The package list is the same, but the Homebrew addon
6084 does not do a `brew update` by default. Implements ticket 27738.
6085 - Report what program produced the mysterious core file that we
6086 occasionally see on Travis CI during make distcheck. Closes
6088 - Don't do a distcheck with --disable-module-dirauth in Travis.
6089 Implements ticket 27252.
6090 - Install libcap-dev and libseccomp2-dev so these optional
6091 dependencies get tested on Travis CI. Closes ticket 26560.
6092 - Only run one online rust build in Travis, to reduce network
6093 errors. Skip offline rust builds on Travis for Linux gcc, because
6094 they're redundant. Implements ticket 27252.
6095 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6096 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6097 Linux with default settings, because all the non-default builds
6098 use gcc on Linux. Implements ticket 27252.
6100 o Minor features (continuous integration, Windows):
6101 - Always show the configure and test logs, and upload them as build
6102 artifacts, when building for Windows using Appveyor CI.
6104 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
6105 Appveyor's CI. Closes ticket 28318.
6107 o Minor features (controller):
6108 - Emit CIRC_BW events as soon as we detect that we processed an
6109 invalid or otherwise dropped cell on a circuit. This allows
6110 vanguards and other controllers to react more quickly to dropped
6111 cells. Closes ticket 27678.
6112 - For purposes of CIRC_BW-based dropped cell detection, track half-
6113 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6114 bias check cells to arrive without counting it as dropped until
6115 either the END arrives, or the windows are empty. Closes
6117 - Implement a 'GETINFO md/all' controller command to enable getting
6118 all known microdescriptors. Closes ticket 8323.
6119 - The GETINFO command now support an "uptime" argument, to return
6120 Tor's uptime in seconds. Closes ticket 25132.
6122 o Minor features (denial-of-service avoidance):
6123 - Make our OOM handler aware of the DNS cache so that it doesn't
6124 fill up the memory. This check is important for our DoS mitigation
6125 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
6127 o Minor features (development):
6128 - Tor's makefile now supports running the "clippy" Rust style tool
6129 on our Rust code. Closes ticket 22156.
6131 o Minor features (directory authority):
6132 - There is no longer an artificial upper limit on the length of
6133 bandwidth lines. Closes ticket 26223.
6134 - When a bandwidth file is used to obtain the bandwidth measurements,
6135 include this bandwidth file headers in the votes. Closes
6137 - Improved support for networks with only a single authority or a
6138 single fallback directory. Patch from Gabriel Somlo. Closes
6141 o Minor features (embedding API):
6142 - The Tor controller API now supports a function to launch Tor with
6143 a preconstructed owning controller FD, so that embedding
6144 applications don't need to manage controller ports and
6145 authentication. Closes ticket 24204.
6146 - The Tor controller API now has a function that returns the name
6147 and version of the backend implementing the API. Closes
6150 o Minor features (fallback directory list):
6151 - Replace the 150 fallbacks originally introduced in Tor
6152 0.3.3.1-alpha in January 2018 (of which ~115 were still
6153 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6154 removed) generated in December 2018. Closes ticket 24803.
6156 o Minor features (geoip):
6157 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6158 Country database. Closes ticket 29012.
6160 o Minor features (memory management):
6161 - Get Libevent to use the same memory allocator as Tor, by calling
6162 event_set_mem_functions() during initialization. Resolves
6165 o Minor features (memory usage):
6166 - When not using them, store legacy TAP public onion keys in DER-
6167 encoded format, rather than as expanded public keys. This should
6168 save several megabytes on typical clients. Closes ticket 27246.
6170 o Minor features (OpenSSL bug workaround):
6171 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6172 key export function from handling long labels. When this bug is
6173 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6174 version of OpenSSL without this bug when it becomes available.
6175 Closes ticket 28973.
6177 o Minor features (OpenSSL):
6178 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
6179 than our own. Resolves ticket 19979.
6181 o Minor features (performance):
6182 - Remove about 96% of the work from the function that we run at
6183 startup to test our curve25519_basepoint implementation. Since
6184 this function has yet to find an actual failure, we now only run
6185 it for 8 iterations instead of 200. Based on our profile
6186 information, this change should save around 8% of our startup time
6187 on typical desktops, and may have a similar effect on other
6188 platforms. Closes ticket 28838.
6189 - Stop re-validating our hardcoded Diffie-Hellman parameters on
6190 every startup. Doing this wasted time and cycles, especially on
6191 low-powered devices. Closes ticket 28851.
6193 o Minor features (Rust, code quality):
6194 - Improve rust code quality in the rust protover implementation by
6195 making it more idiomatic. Includes changing an internal API to
6196 take &str instead of &String. Closes ticket 26492.
6198 o Minor features (testing):
6199 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
6200 chutney. Implements ticket 27211.
6202 o Minor features (tor-resolve):
6203 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
6204 Side-effect of the refactoring for ticket 26526.
6206 o Minor features (UI):
6207 - Log each included configuration file or directory as we read it,
6208 to provide more visibility about where Tor is reading from. Patch
6209 from Unto Sten; closes ticket 27186.
6210 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
6211 Closes ticket 26703.
6213 o Minor bugfixes (32-bit OSX and iOS, timing):
6214 - Fix an integer overflow bug in our optimized 32-bit millisecond-
6215 difference algorithm for 32-bit Apple platforms. Previously, it
6216 would overflow when calculating the difference between two times
6217 more than 47 days apart. Fixes part of bug 27139; bugfix
6219 - Improve the precision of our 32-bit millisecond difference
6220 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
6221 bugfix on 0.3.4.1-alpha.
6222 - Relax the tolerance on the mainloop/update_time_jumps test when
6223 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
6226 o Minor bugfixes (bootstrap):
6227 - Try harder to get descriptors in non-exit test networks, by using
6228 the mid weight for the third hop when there are no exits. Fixes
6229 bug 27237; bugfix on 0.2.6.2-alpha.
6231 o Minor bugfixes (C correctness):
6232 - Avoid casting smartlist index to int implicitly, as it may trigger
6233 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
6234 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
6235 - Use time_t for all values in
6236 predicted_ports_prediction_time_remaining(). Rework the code that
6237 computes difference between durations/timestamps. Fixes bug 27165;
6238 bugfix on 0.3.1.1-alpha.
6240 o Minor bugfixes (client, memory usage):
6241 - When not running as a directory cache, there is no need to store
6242 the text of the current consensus networkstatus in RAM.
6243 Previously, however, clients would store it anyway, at a cost of
6244 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
6247 o Minor bugfixes (client, ReachableAddresses):
6248 - Instead of adding a "reject *:*" line to ReachableAddresses when
6249 loading the configuration, add one to the policy after parsing it
6250 in parse_reachable_addresses(). This prevents extra "reject *.*"
6251 lines from accumulating on reloads. Fixes bug 20874; bugfix on
6252 0.1.1.5-alpha. Patch by Neel Chauhan.
6254 o Minor bugfixes (code quality):
6255 - Rename sandbox_getaddrinfo() and other functions to no longer
6256 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
6257 bugfix on 0.2.7.1-alpha.
6259 o Minor bugfixes (code safety):
6260 - Rewrite our assertion macros so that they no longer suppress the
6261 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6264 o Minor bugfixes (compilation):
6265 - Initialize a variable unconditionally in aes_new_cipher(), since
6266 some compilers cannot tell that we always initialize it before
6267 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6269 o Minor bugfixes (configuration):
6270 - Refuse to start with relative file paths and RunAsDaemon set
6271 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
6274 o Minor bugfixes (configuration, Onion Services):
6275 - In rend_service_parse_port_config(), disallow any input to remain
6276 after address-port pair was parsed. This will catch address and
6277 port being whitespace-separated by mistake of the user. Fixes bug
6278 27044; bugfix on 0.2.9.10.
6280 o Minor bugfixes (connection, relay):
6281 - Avoid a logging a BUG() stacktrace when closing connection held
6282 open because the write side is rate limited but not the read side.
6283 Now, the connection read side is simply shut down until Tor is
6284 able to flush the connection and close it. Fixes bug 27750; bugfix
6287 o Minor bugfixes (continuous integration, Windows):
6288 - Stop reinstalling identical packages in our Windows CI. Fixes bug
6289 27464; bugfix on 0.3.4.1-alpha.
6290 - Install only the necessary mingw packages during our appveyor
6291 builds. This change makes the build a little faster, and prevents
6292 a conflict with a preinstalled mingw openssl that appveyor now
6293 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
6294 - Explicitly specify the path to the OpenSSL library and do not
6295 download OpenSSL from Pacman, but instead use the library that is
6296 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
6297 - Manually configure the zstd compiler options, when building using
6298 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
6299 not come with a pkg-config file. Fixes bug 28454; bugfix
6301 - Stop using an external OpenSSL install, and stop installing MSYS2
6302 packages, when building using mingw on Appveyor Windows CI. Fixes
6303 bug 28399; bugfix on 0.3.4.1-alpha.
6305 o Minor bugfixes (controller):
6306 - Consider all routerinfo errors other than "not a server" to be
6307 transient for the purpose of "GETINFO exit-policy/*" controller
6308 request. Print stacktrace in the unlikely case of failing to
6309 recompute routerinfo digest. Fixes bug 27034; bugfix
6312 o Minor bugfixes (correctness):
6313 - Fix an unreached code path where we checked the value of
6314 "hostname" inside send_resolved_hostname_cell(). Previously, we
6315 used it before checking it; now we check it first. Fixes bug
6316 28879; bugfix on 0.1.2.7-alpha.
6318 o Minor bugfixes (directory connection shutdown):
6319 - Avoid a double-close when shutting down a stalled directory
6320 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
6322 o Minor bugfixes (directory permissions):
6323 - When a user requests a group-readable DataDirectory, give it to
6324 them. Previously, when the DataDirectory and the CacheDirectory
6325 were the same, the default setting (0) for
6326 CacheDirectoryGroupReadable would override the setting for
6327 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6330 o Minor bugfixes (HTTP tunnel):
6331 - Fix a bug warning when closing an HTTP tunnel connection due to an
6332 HTTP request we couldn't handle. Fixes bug 26470; bugfix
6335 o Minor bugfixes (ipv6):
6336 - In addrs_in_same_network_family(), we choose the subnet size based
6337 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
6338 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
6339 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
6341 o Minor bugfixes (Linux seccomp2 sandbox):
6342 - Permit the "shutdown()" system call, which is apparently used by
6343 OpenSSL under some circumstances. Fixes bug 28183; bugfix
6346 o Minor bugfixes (logging):
6347 - Stop talking about the Named flag in log messages. Clients have
6348 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
6350 - As a precaution, do an early return from log_addr_has_changed() if
6351 Tor is running as client. Also, log a stack trace for debugging as
6352 this function should only be called when Tor runs as server. Fixes
6353 bug 26892; bugfix on 0.1.1.9-alpha.
6354 - Refrain from mentioning bug 21018 in the logs, as it is already
6355 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
6357 o Minor bugfixes (logging, documentation):
6358 - When SafeLogging is enabled, scrub IP address in
6359 channel_tls_process_netinfo_cell(). Also, add a note to manpage
6360 that scrubbing is not guaranteed on loglevels below Notice. Fixes
6361 bug 26882; bugfix on 0.2.4.10-alpha.
6363 o Minor bugfixes (memory leaks):
6364 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6365 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6366 - Fix a small memory leak when calling Tor with --dump-config. Fixes
6367 bug 27893; bugfix on 0.3.2.1-alpha.
6369 o Minor bugfixes (netflow padding):
6370 - Ensure circuitmux queues are empty before scheduling or sending
6371 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6373 o Minor bugfixes (onion service v2):
6374 - Log at level "info", not "warning", in the case that we do not
6375 have a consensus when a .onion request comes in. This can happen
6376 normally while bootstrapping. Fixes bug 27040; bugfix
6379 o Minor bugfixes (onion service v3):
6380 - When deleting an ephemeral onion service (DEL_ONION), do not close
6381 any rendezvous circuits in order to let the existing client
6382 connections finish by themselves or closed by the application. The
6383 HS v2 is doing that already so now we have the same behavior for
6384 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6385 - Build the service descriptor's signing key certificate before
6386 uploading, so we always have a fresh one: leaving no chances for
6387 it to expire service side. Fixes bug 27838; bugfix
6389 - Stop dumping a stack trace when trying to connect to an intro
6390 point without having a descriptor for it. Fixes bug 27774; bugfix
6392 - When selecting a v3 rendezvous point, don't only look at the
6393 protover, but also check whether the curve25519 onion key is
6394 present. This way we avoid picking a relay that supports the v3
6395 rendezvous but for which we don't have the microdescriptor. Fixes
6396 bug 27797; bugfix on 0.3.2.1-alpha.
6397 - Close all SOCKS request (for the same .onion) if the newly fetched
6398 descriptor is unusable. Before that, we would close only the first
6399 one leaving the other hanging and let to time out by themselves.
6400 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6401 - When the onion service directory can't be created or has the wrong
6402 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6404 - When replacing a descriptor in the client cache, make sure to
6405 close all client introduction circuits for the old descriptor, so
6406 we don't end up with unusable leftover circuits. Fixes bug 27471;
6407 bugfix on 0.3.2.1-alpha.
6409 o Minor bugfixes (OS compatibility):
6410 - Properly handle configuration changes that move a listener to/from
6411 wildcard IP address. If the first attempt to bind a socket fails,
6412 close the old listener and try binding the socket again. Fixes bug
6413 17873; bugfix on 0.0.8pre-1.
6415 o Minor bugfixes (performance)::
6416 - Rework node_is_a_configured_bridge() to no longer call
6417 node_get_all_orports(), which was performing too many memory
6418 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
6420 o Minor bugfixes (protover):
6421 - Reject protocol names containing bytes other than alphanumeric
6422 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6425 o Minor bugfixes (protover, rust):
6426 - Reject extra commas in version strings. Fixes bug 27197; bugfix
6428 - protover_all_supported() would attempt to allocate up to 16GB on
6429 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6430 bugfix on 0.3.3.5-rc.
6431 - Compute protover votes correctly in the rust version of the
6432 protover code. Previously, the protover rewrite in 24031 allowed
6433 repeated votes from the same voter for the same protocol version
6434 to be counted multiple times in protover_compute_vote(). Fixes bug
6435 27649; bugfix on 0.3.3.5-rc.
6436 - Reject protover names that contain invalid characters. Fixes bug
6437 27687; bugfix on 0.3.3.1-alpha.
6439 o Minor bugfixes (relay shutdown, systemd):
6440 - Notify systemd of ShutdownWaitLength so it can be set to longer
6441 than systemd's TimeoutStopSec. In Tor's systemd service file, set
6442 TimeoutSec to 60 seconds to allow Tor some time to shut down.
6443 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
6445 o Minor bugfixes (relay statistics):
6446 - Update relay descriptor on bandwidth changes only when the uptime
6447 is smaller than 24h, in order to reduce the efficiency of guard
6448 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6450 o Minor bugfixes (relay):
6451 - Consider the fact that we'll be making direct connections to our
6452 entry and guard nodes when computing the fraction of nodes that
6453 have their descriptors. Also, if we are using bridges and there is
6454 at least one bridge with a full descriptor, treat the fraction of
6455 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
6456 Patch by Neel Chauhan.
6457 - Update the message logged on relays when DirCache is disabled.
6458 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
6459 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
6461 o Minor bugfixes (testing):
6462 - Stop running stem's unit tests as part of "make test-stem", but
6463 continue to run stem's unit and online tests during "make test-
6464 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
6465 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6466 bugfix on 0.3.0.1-alpha.
6467 - Make the hs_service tests use the same time source when creating
6468 the introduction point and when testing it. Now tests work better
6469 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
6471 - Revise the "conditionvar_timeout" test so that it succeeds even on
6472 heavily loaded systems where the test threads are not scheduled
6473 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
6474 - Fix two unit tests to work when HOME environment variable is not
6475 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
6476 - If a unit test running in a subprocess exits abnormally or with a
6477 nonzero status code, treat the test as having failed, even if the
6478 test reported success. Without this fix, memory leaks don't cause
6479 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6480 bugfix on 0.2.2.4-alpha.
6481 - When logging a version mismatch in our openssl_version tests,
6482 report the actual offending version strings. Fixes bug 26152;
6483 bugfix on 0.2.9.1-alpha.
6484 - Fix forking tests on Windows when there is a space somewhere in
6485 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
6487 o Minor bugfixes (Windows):
6488 - Correctly identify Windows 8.1, Windows 10, and Windows Server
6489 2008 and later from their NT versions. Fixes bug 28096; bugfix on
6490 0.2.2.34; reported by Keifer Bly.
6491 - On recent Windows versions, the GetVersionEx() function may report
6492 an earlier Windows version than the running OS. To avoid user
6493 confusion, add "[or later]" to Tor's version string on affected
6494 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
6496 - Remove Windows versions that were never supported by the
6497 GetVersionEx() function. Stop duplicating the latest Windows
6498 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
6499 reported by Keifer Bly.
6501 o Code simplification and refactoring:
6502 - When parsing a port configuration, make it more obvious to static
6503 analyzer tools that we always initialize the address. Closes
6505 - Divide more large Tor source files -- especially ones that span
6506 multiple areas of functionality -- into smaller parts, including
6507 onion.c and main.c. Closes ticket 26747.
6508 - Divide the "routerparse.c" module into separate modules for each
6509 group of parsed objects. Closes ticket 27924.
6510 - Move protover_rust.c to the same place protover.c was moved to.
6511 Closes ticket 27814.
6512 - Split directory.c into separate pieces for client, server, and
6513 common functionality. Closes ticket 26744.
6514 - Split the non-statistics-related parts from the rephist.c and
6515 geoip.c modules. Closes ticket 27892.
6516 - Split the router.c file into relay-only and shared components, to
6517 help with future modularization. Closes ticket 27864.
6518 - Divide the routerlist.c and dirserv.c modules into smaller parts.
6519 Closes ticket 27799.
6520 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
6521 longer needed. Closes ticket 26502.
6522 - Include paths to header files within Tor are now qualified by
6523 directory within the top-level src directory.
6524 - Many structures have been removed from the centralized "or.h"
6525 header, and moved into their own headers. This will allow us to
6526 reduce the number of places in the code that rely on each
6527 structure's contents and layout. Closes ticket 26383.
6528 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
6529 - Remove GetAdaptersAddresses_fn_t. The code that used it was
6530 removed as part of the 26481 refactor. Closes ticket 27467.
6531 - Rework Tor SOCKS server code to use Trunnel and benefit from
6532 autogenerated functions for parsing and generating SOCKS wire
6533 format. New implementation is cleaner, more maintainable and
6534 should be less prone to heartbleed-style vulnerabilities.
6535 Implements a significant fraction of ticket 3569.
6536 - Split sampled_guards_update_from_consensus() and
6537 select_entry_guard_for_circuit() into subfunctions. In
6538 entry_guards_update_primary() unite three smartlist enumerations
6539 into one and move smartlist comparison code out of the function.
6540 Closes ticket 21349.
6541 - Tor now assumes that you have standards-conformant stdint.h and
6542 inttypes.h headers when compiling. Closes ticket 26626.
6543 - Unify our bloom filter logic. Previously we had two copies of this
6544 code: one for routerlist filtering, and one for address set
6545 calculations. Closes ticket 26510.
6546 - Use the simpler strcmpstart() helper in
6547 rend_parse_v2_service_descriptor instead of strncmp(). Closes
6549 - Utility functions that can perform a DNS lookup are now wholly
6550 separated from those that can't, in separate headers and C
6551 modules. Closes ticket 26526.
6554 - In the tor-resolve(1) manpage, fix the reference to socks-
6555 extensions.txt by adding a web URL. Resolves ticket 27853.
6556 - Mention that we require Python to be 2.7 or newer for some
6557 integration tests that we ship with Tor. Resolves ticket 27677.
6558 - Copy paragraph and URL to Tor's code of conduct document from
6559 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
6560 - Remove old instructions from INSTALL document. Closes ticket 26588.
6561 - Warn users that they should not include MyFamily line(s) in their
6562 torrc when running Tor bridge. Closes ticket 26908.
6565 - Tor no longer supports building with the dmalloc library. For
6566 debugging memory issues, we suggest using gperftools or msan
6567 instead. Closes ticket 26426.
6568 - Tor no longer attempts to run on Windows environments without the
6569 GetAdaptersAddresses() function. This function has existed since
6570 Windows XP, which is itself already older than we support.
6571 - Remove Tor2web functionality for version 2 onion services. The
6572 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
6573 (This feature was never shipped in vanilla Tor and it was only
6574 possible to use this feature by building the support at compile
6575 time. Tor2webMode is not implemented for version 3 onion services.)
6576 Closes ticket 26367.
6579 - Increase logging and tag all log entries with timestamps in
6580 test_rebind.py. Provides diagnostics for issue 28229.
6582 o Code simplification and refactoring (shared random, dirauth):
6583 - Change many tor_assert() to use BUG() instead. The idea is to not
6584 crash a dirauth but rather scream loudly with a stacktrace and let
6585 it continue run. The shared random subsystem is very resilient and
6586 if anything wrong happens with it, at worst a non coherent value
6587 will be put in the vote and discarded by the other authorities.
6588 Closes ticket 19566.
6590 o Documentation (onion services):
6591 - Improve HSv3 client authorization by making some options more
6592 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
6593 - Document in the man page that changing ClientOnionAuthDir value or
6594 adding a new file in the directory will not work at runtime upon
6595 sending a HUP if Sandbox 1. Closes ticket 28128.
6596 - Note in the man page that the only real way to fully revoke an
6597 onion service v3 client authorization is by restarting the tor
6598 process. Closes ticket 28275.
6601 Changes in version 0.3.4.9 - 2018-11-02
6602 Tor 0.3.4.9 is the second stable release in its series; it backports
6603 numerous fixes, including a fix for a bandwidth management bug that
6604 was causing memory exhaustion on relays. Anyone running an earlier
6605 version of Tor 0.3.4.9 should upgrade.
6607 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
6608 - Fix compilation on ARM (and other less-used CPUs) when compiling
6609 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
6611 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
6612 - Make sure Tor bootstraps and works properly if only the
6613 ControlPort is set. Prior to this fix, Tor would only bootstrap
6614 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
6615 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
6617 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
6618 - When our write bandwidth limit is exhausted, stop writing on the
6619 connection. Previously, we had a typo in the code that would make
6620 us stop reading instead, leading to relay connections being stuck
6621 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
6624 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
6625 - Fix a use-after-free error that could be caused by passing Tor an
6626 impossible set of options that would fail during options_act().
6627 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6629 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
6630 - Don't do a distcheck with --disable-module-dirauth in Travis.
6631 Implements ticket 27252.
6632 - Only run one online rust build in Travis, to reduce network
6633 errors. Skip offline rust builds on Travis for Linux gcc, because
6634 they're redundant. Implements ticket 27252.
6635 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6636 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6637 Linux with default settings, because all the non-default builds
6638 use gcc on Linux. Implements ticket 27252.
6640 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
6641 - Use the Travis Homebrew addon to install packages on macOS during
6642 Travis CI. The package list is the same, but the Homebrew addon
6643 does not do a `brew update` by default. Implements ticket 27738.
6645 o Minor features (geoip):
6646 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
6647 Country database. Closes ticket 27991.
6649 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
6650 - Fix an integer overflow bug in our optimized 32-bit millisecond-
6651 difference algorithm for 32-bit Apple platforms. Previously, it
6652 would overflow when calculating the difference between two times
6653 more than 47 days apart. Fixes part of bug 27139; bugfix
6655 - Improve the precision of our 32-bit millisecond difference
6656 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
6657 bugfix on 0.3.4.1-alpha.
6658 - Relax the tolerance on the mainloop/update_time_jumps test when
6659 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
6662 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
6663 - Avoid undefined behavior in an end-of-string check when parsing
6664 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6667 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
6668 - Only install the necessary mingw packages during our appveyor
6669 builds. This change makes the build a little faster, and prevents
6670 a conflict with a preinstalled mingw openssl that appveyor now
6671 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
6673 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
6674 - Rewrite our assertion macros so that they no longer suppress the
6675 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6677 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
6678 - Stop reinstalling identical packages in our Windows CI. Fixes bug
6679 27464; bugfix on 0.3.4.1-alpha.
6681 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
6682 - Log additional info when we get a relay that shares an ed25519 ID
6683 with a different relay, instead making a BUG() warning. Fixes bug
6684 27800; bugfix on 0.3.2.1-alpha.
6686 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
6687 - Avoid a double-close when shutting down a stalled directory
6688 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
6690 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
6691 - Fix a bug warning when closing an HTTP tunnel connection due to an
6692 HTTP request we couldn't handle. Fixes bug 26470; bugfix
6695 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
6696 - Ensure circuitmux queues are empty before scheduling or sending
6697 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6699 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
6700 - When the onion service directory can't be created or has the wrong
6701 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6704 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
6705 - Close all SOCKS request (for the same .onion) if the newly fetched
6706 descriptor is unusable. Before that, we would close only the first
6707 one leaving the other hanging and let to time out by themselves.
6708 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6710 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6711 - When selecting a v3 rendezvous point, don't only look at the
6712 protover, but also check whether the curve25519 onion key is
6713 present. This way we avoid picking a relay that supports the v3
6714 rendezvous but for which we don't have the microdescriptor. Fixes
6715 bug 27797; bugfix on 0.3.2.1-alpha.
6717 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
6718 - Reject protocol names containing bytes other than alphanumeric
6719 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6722 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
6723 - Compute protover votes correctly in the rust version of the
6724 protover code. Previously, the protover rewrite in 24031 allowed
6725 repeated votes from the same voter for the same protocol version
6726 to be counted multiple times in protover_compute_vote(). Fixes bug
6727 27649; bugfix on 0.3.3.5-rc.
6728 - Reject protover names that contain invalid characters. Fixes bug
6729 27687; bugfix on 0.3.3.1-alpha.
6731 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
6732 - protover_all_supported() would attempt to allocate up to 16GB on
6733 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6734 bugfix on 0.3.3.5-rc.
6736 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
6737 - Fix an API mismatch in the rust implementation of
6738 protover_compute_vote(). This bug could have caused crashes on any
6739 directory authorities running Tor with Rust (which we do not yet
6740 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6742 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
6743 - Fix a potential null dereference in protover_all_supported(). Add
6744 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6745 - Return a string that can be safely freed by C code, not one
6746 created by the rust allocator, in protover_all_supported(). Fixes
6747 bug 27740; bugfix on 0.3.3.1-alpha.
6749 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
6750 - If a unit test running in a subprocess exits abnormally or with a
6751 nonzero status code, treat the test as having failed, even if the
6752 test reported success. Without this fix, memory leaks don't cause
6753 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6754 bugfix on 0.2.2.4-alpha.
6756 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
6757 - Make the hs_service tests use the same time source when creating
6758 the introduction point and when testing it. Now tests work better
6759 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
6762 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
6763 - Treat backtrace test failures as expected on BSD-derived systems
6764 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6765 (FreeBSD failures have been treated as expected since 18204 in
6766 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6769 Changes in version 0.2.9.17 - 2018-09-10
6770 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
6772 o Minor features (compatibility, backport from 0.3.4.8):
6773 - Tell OpenSSL to maintain backward compatibility with previous
6774 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6775 ciphers are disabled by default. Closes ticket 27344.
6777 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6778 - Enable macOS builds in our Travis CI configuration. Closes
6780 - Install libcap-dev and libseccomp2-dev so these optional
6781 dependencies get tested on Travis CI. Closes ticket 26560.
6782 - Run asciidoc during Travis CI. Implements ticket 27087.
6783 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6785 o Minor features (geoip):
6786 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6787 Country database. Closes ticket 27089.
6789 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6790 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6791 tell the compiler not to include the system malloc implementation.
6792 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6794 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6795 - Silence a spurious compiler warning on the GetAdaptersAddresses
6796 function pointer cast. This issue is already fixed by 26481 in
6797 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6798 bugfix on 0.2.3.11-alpha.
6799 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6800 supported, and always fails. Some compilers warn about the
6801 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6804 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6805 - Don't link or search for pthreads when building for Windows, even
6806 if we are using build environment (like mingw) that provides a
6807 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6809 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6810 - Skip a pair of unreliable key generation tests on Windows, until
6811 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6812 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6814 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6815 - Pass the module flags to distcheck configure, and log the flags
6816 before running configure. (Backported to 0.2.9 and later as a
6817 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6819 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6820 - When a Travis build fails, and showing a log fails, keep trying to
6821 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6822 - When we use echo in Travis, don't pass a --flag as the first
6823 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6825 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6826 - When voting for recommended versions, make sure that all of the
6827 versions are well-formed and parsable. Fixes bug 26485; bugfix
6830 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6831 - Fix a bug in out sandboxing rules for the openat() syscall.
6832 Previously, no openat() call would be permitted, which would break
6833 filesystem operations on recent glibc versions. Fixes bug 25440;
6834 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6836 o Minor bugfixes (onion services, backport from 0.3.4.8):
6837 - Silence a spurious compiler warning in
6838 rend_client_send_introduction(). Fixes bug 27463; bugfix
6841 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6842 - Log a protocol warning when single onion services or Tor2web clients
6843 fail to authenticate direct connections to relays.
6844 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6846 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6847 - Disable core dumps in test_bt.sh, to avoid failures in "make
6848 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6850 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6851 - Before running make test-network-all, delete old logs and test
6852 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6855 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6856 - Our "tortls/cert_matches_key" unit test no longer relies on
6857 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6858 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6859 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6861 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6862 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6863 27185; bugfix on 0.2.2.2-alpha.
6866 Changes in version 0.3.2.12 - 2018-09-10
6867 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
6869 o Minor features (compatibility, backport from 0.3.4.8):
6870 - Tell OpenSSL to maintain backward compatibility with previous
6871 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6872 ciphers are disabled by default. Closes ticket 27344.
6874 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6875 - Enable macOS builds in our Travis CI configuration. Closes
6877 - Install libcap-dev and libseccomp2-dev so these optional
6878 dependencies get tested on Travis CI. Closes ticket 26560.
6879 - Run asciidoc during Travis CI. Implements ticket 27087.
6880 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6882 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6883 - Use cargo cache in our Travis CI configuration. Closes
6886 o Minor features (controller, backport from 0.3.4.6-rc):
6887 - The control port now exposes the list of HTTPTunnelPorts and
6888 ExtOrPorts via GETINFO net/listeners/httptunnel and
6889 net/listeners/extor respectively. Closes ticket 26647.
6891 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6892 - Authorities no longer vote to make the subprotocol version
6893 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6894 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6896 o Minor features (geoip):
6897 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6898 Country database. Closes ticket 27089.
6900 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6901 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6902 tell the compiler not to include the system malloc implementation.
6903 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6904 - Don't try to use a pragma to temporarily disable the
6905 -Wunused-const-variable warning if the compiler doesn't support
6906 it. Fixes bug 26785; bugfix on 0.3.2.11.
6908 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6909 - Silence a spurious compiler warning on the GetAdaptersAddresses
6910 function pointer cast. This issue is already fixed by 26481 in
6911 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6912 bugfix on 0.2.3.11-alpha.
6913 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6914 supported, and always fails. Some compilers warn about the
6915 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6918 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6919 - Don't link or search for pthreads when building for Windows, even
6920 if we are using build environment (like mingw) that provides a
6921 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6923 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6924 - Skip a pair of unreliable key generation tests on Windows, until
6925 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6926 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6928 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6929 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6930 - Pass the module flags to distcheck configure, and log the flags
6931 before running configure. (Backported to 0.2.9 and later as a
6932 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6934 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6935 - When a Travis build fails, and showing a log fails, keep trying to
6936 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6937 - When we use echo in Travis, don't pass a --flag as the first
6938 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6940 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6941 - When voting for recommended versions, make sure that all of the
6942 versions are well-formed and parsable. Fixes bug 26485; bugfix
6945 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6946 - Fix a bug in out sandboxing rules for the openat() syscall.
6947 Previously, no openat() call would be permitted, which would break
6948 filesystem operations on recent glibc versions. Fixes bug 25440;
6949 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6951 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6952 - Improve the log message when connection initiators fail to
6953 authenticate direct connections to relays. Fixes bug 26927; bugfix
6956 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6957 - Fix bug that causes services to not ever rotate their descriptors
6958 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6961 o Minor bugfixes (onion services, backport from 0.3.4.8):
6962 - Silence a spurious compiler warning in
6963 rend_client_send_introduction(). Fixes bug 27463; bugfix
6966 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6967 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6969 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6970 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6971 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6972 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6974 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6975 - Log a protocol warning when single onion services or Tor2web clients
6976 fail to authenticate direct connections to relays.
6977 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6979 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6980 - Disable core dumps in test_bt.sh, to avoid failures in "make
6981 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6983 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6984 - When running make test-network-all, use the mixed+hs-v2 network.
6985 (A previous fix to chutney removed v3 onion services from the
6986 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6987 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6988 - Before running make test-network-all, delete old logs and test
6989 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6992 o Minor bugfixes (testing, openssl compatibility):
6993 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
6994 internals. Previously, it relied on unsupported OpenSSL behavior in
6995 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
6996 bugfix on 0.2.5.1-alpha.
6998 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6999 - Our "tortls/cert_matches_key" unit test no longer relies on
7000 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7001 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7002 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7004 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7005 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7006 27185; bugfix on 0.2.2.2-alpha.
7009 Changes in version 0.3.3.10 - 2018-09-10
7010 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
7012 o Minor features (bug workaround, backport from 0.3.4.7-rc):
7013 - Compile correctly on systems that provide the C11 stdatomic.h
7014 header, but where C11 atomic functions don't actually compile.
7015 Closes ticket 26779; workaround for Debian issue 903709.
7017 o Minor features (compatibility, backport from 0.3.4.8):
7018 - Tell OpenSSL to maintain backward compatibility with previous
7019 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7020 ciphers are disabled by default. Closes ticket 27344.
7022 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7023 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
7024 - Enable macOS builds in our Travis CI configuration. Closes
7026 - Install libcap-dev and libseccomp2-dev so these optional
7027 dependencies get tested on Travis CI. Closes ticket 26560.
7028 - Run asciidoc during Travis CI. Implements ticket 27087.
7029 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7031 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
7032 - Use cargo cache in our Travis CI configuration. Closes
7035 o Minor features (controller, backport from 0.3.4.6-rc):
7036 - The control port now exposes the list of HTTPTunnelPorts and
7037 ExtOrPorts via GETINFO net/listeners/httptunnel and
7038 net/listeners/extor respectively. Closes ticket 26647.
7040 o Minor features (directory authorities, backport from 0.3.4.7-rc):
7041 - Authorities no longer vote to make the subprotocol version
7042 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7043 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7045 o Minor features (geoip):
7046 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7047 Country database. Closes ticket 27089.
7049 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7050 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7051 tell the compiler not to include the system malloc implementation.
7052 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7053 - Don't try to use a pragma to temporarily disable the
7054 -Wunused-const-variable warning if the compiler doesn't support
7055 it. Fixes bug 26785; bugfix on 0.3.2.11.
7057 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7058 - Silence a spurious compiler warning on the GetAdaptersAddresses
7059 function pointer cast. This issue is already fixed by 26481 in
7060 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7061 bugfix on 0.2.3.11-alpha.
7062 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7063 supported, and always fails. Some compilers warn about the
7064 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7067 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7068 - Don't link or search for pthreads when building for Windows, even
7069 if we are using build environment (like mingw) that provides a
7070 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7072 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7073 - Skip a pair of unreliable key generation tests on Windows, until
7074 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7075 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7077 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7078 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7079 - Pass the module flags to distcheck configure, and log the flags
7080 before running configure. (Backported to 0.2.9 and later as a
7081 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7083 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7084 - When a Travis build fails, and showing a log fails, keep trying to
7085 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7086 - When we use echo in Travis, don't pass a --flag as the first
7087 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7089 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7090 - When voting for recommended versions, make sure that all of the
7091 versions are well-formed and parsable. Fixes bug 26485; bugfix
7094 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
7095 - Always call tor_free_all() when leaving tor_run_main(). When we
7096 did not, restarting tor in-process would cause an assertion
7097 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
7099 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7100 - Fix a bug in our sandboxing rules for the openat() syscall.
7101 Previously, no openat() call would be permitted, which would break
7102 filesystem operations on recent glibc versions. Fixes bug 25440;
7103 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7105 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
7106 - Improve the log message when connection initiators fail to
7107 authenticate direct connections to relays. Fixes bug 26927; bugfix
7110 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
7111 - Fix bug that causes services to not ever rotate their descriptors
7112 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7115 o Minor bugfixes (onion services, backport from 0.3.4.8):
7116 - Silence a spurious compiler warning in
7117 rend_client_send_introduction(). Fixes bug 27463; bugfix
7120 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
7121 - Work around two different bugs in the OS X 10.10 and later SDKs
7122 that would prevent us from successfully targeting earlier versions
7123 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
7125 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
7126 - Fix compilation of the unit tests on GNU/Hurd, which does not
7127 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
7130 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
7131 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7133 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
7134 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
7135 - Protover parsing was accepting the presence of whitespace in
7136 version strings, which the C implementation would choke on, e.g.
7137 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
7138 - Protover parsing was ignoring a 2nd hyphen and everything after
7139 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
7141 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
7142 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
7143 - cd to ${abs_top_builddir}/src/rust before running cargo in
7144 src/test/test_rust.sh. This makes the working directory consistent
7145 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
7147 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7148 - Log a protocol warning when single onion services or Tor2web clients
7149 fail to authenticate direct connections to relays.
7150 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7152 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7153 - Disable core dumps in test_bt.sh, to avoid failures in "make
7154 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7156 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7157 - When running make test-network-all, use the mixed+hs-v2 network.
7158 (A previous fix to chutney removed v3 onion services from the
7159 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
7160 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
7161 - Before running make test-network-all, delete old logs and test
7162 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7165 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7166 - Our "tortls/cert_matches_key" unit test no longer relies on
7167 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7168 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7169 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7171 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
7172 - Stop sending ed25519 link specifiers in v3 onion service introduce
7173 cells and descriptors, when the rendezvous or introduction point
7174 doesn't support ed25519 link authentication. Fixes bug 26627;
7175 bugfix on 0.3.2.4-alpha.
7177 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7178 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7179 27185; bugfix on 0.2.2.2-alpha.
7182 Changes in version 0.3.4.8 - 2018-09-10
7183 Tor 0.3.4.8 is the first stable release in its series; it includes
7184 compilation and portability fixes.
7186 The Tor 0.3.4 series includes improvements for running Tor in
7187 low-power and embedded environments, which should help performance in
7188 general. We've begun work on better modularity, and included preliminary
7189 changes on the directory authority side to accommodate a new bandwidth
7190 measurement system. We've also integrated more continuous-integration
7191 systems into our development process, and made corresponding changes to
7192 Tor's testing infrastructure. Finally, we've continued to refine
7193 our anti-denial-of-service code.
7195 Below are the changes since 0.3.3.9. For a list of only the changes
7196 since 0.3.4.7-rc, see the ChangeLog file.
7198 o New system requirements:
7199 - Tor no longer tries to support old operating systems without
7200 mmap() or some local equivalent. Apparently, compilation on such
7201 systems has been broken for some time, without anybody noticing or
7202 complaining. Closes ticket 25398.
7204 o Major features (directory authority, modularization):
7205 - The directory authority subsystem has been modularized. The code
7206 is now located in src/or/dirauth/, and is compiled in by default.
7207 To disable the module, the configure option
7208 --disable-module-dirauth has been added. This module may be
7209 disabled by default in some future release. Closes ticket 25610.
7211 o Major features (main loop, CPU usage):
7212 - When Tor is disabled (via DisableNetwork or via hibernation), it
7213 no longer needs to run any per-second events. This change should
7214 make it easier for mobile applications to disable Tor while the
7215 device is sleeping, or Tor is not running. Closes ticket 26063.
7216 - Tor no longer enables all of its periodic events by default.
7217 Previously, Tor would enable all possible main loop events,
7218 regardless of whether it needed them. Furthermore, many of these
7219 events are now disabled when Tor is hibernating or DisableNetwork
7220 is set. This is a big step towards reducing client CPU usage by
7221 reducing the amount of wake-ups the daemon does. Closes tickets
7223 - The bandwidth-limitation logic has been refactored so that
7224 bandwidth calculations are performed on-demand, rather than every
7225 TokenBucketRefillInterval milliseconds. This change should improve
7226 the granularity of our bandwidth calculations, and limit the
7227 number of times that the Tor process needs to wake up when it is
7228 idle. Closes ticket 25373.
7229 - Move responsibility for many operations from a once-per-second
7230 callback to a callback that is only scheduled as needed. Moving
7231 this functionality has allowed us to disable the callback when
7232 Tor's network is disabled. Once enough items are removed from our
7233 once-per-second callback, we can eliminate it entirely to conserve
7234 CPU when idle. The functionality removed includes: closing
7235 connections, circuits, and channels (ticket 25932); consensus
7236 voting (25937); flushing log callbacks (25951); honoring delayed
7237 SIGNEWNYM requests (25949); rescanning the consensus cache
7238 (25931); saving the state file to disk (25948); warning relay
7239 operators about unreachable ports (25952); and keeping track of
7240 Tor's uptime (26009).
7242 o Minor features (accounting):
7243 - When Tor becomes dormant, it now uses a scheduled event to wake up
7244 at the right time. Previously, we would use the per-second timer
7245 to check whether to wake up, but we no longer have any per-second
7246 timers enabled when the network is disabled. Closes ticket 26064.
7248 o Minor features (bug workaround):
7249 - Compile correctly on systems that provide the C11 stdatomic.h
7250 header, but where C11 atomic functions don't actually compile.
7251 Closes ticket 26779; workaround for Debian issue 903709.
7253 o Minor features (code quality):
7254 - Add optional spell-checking for the Tor codebase, using the
7255 "misspell" program. To use this feature, run "make check-typos".
7256 Closes ticket 25024.
7258 o Minor features (compatibility):
7259 - Tell OpenSSL to maintain backward compatibility with previous
7260 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7261 ciphers are disabled by default. Closes ticket 27344.
7262 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
7263 the no-deprecated option, and builds correctly with them. Closes
7264 tickets 19429, 19981, and 25353.
7266 o Minor features (compilation):
7267 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7268 tell the compiler not to include the system malloc implementation.
7269 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7270 - Don't try to use a pragma to temporarily disable the
7271 -Wunused-const-variable warning if the compiler doesn't support
7272 it. Fixes bug 26785; bugfix on 0.3.2.11.
7273 - When building Tor, prefer to use Python 3 over Python 2, and more
7274 recent (contemplated) versions over older ones. Closes
7277 o Minor features (compression, zstd):
7278 - When running with zstd, Tor now considers using advanced functions
7279 that the zstd maintainers have labeled as potentially unstable. To
7280 prevent breakage, Tor will only use this functionality when the
7281 runtime version of the zstd library matches the version with which
7282 Tor was compiled. Closes ticket 25162.
7284 o Minor features (configuration):
7285 - The "DownloadSchedule" options have been renamed to end with
7286 "DownloadInitialDelay". The old names are still allowed, but will
7287 produce a warning. Comma-separated lists are still permitted for
7288 these options, but all values after the first are ignored (as they
7289 have been since 0.2.9). Closes ticket 23354.
7291 o Minor features (continuous integration):
7292 - Log the compiler path and version during Appveyor builds.
7293 Implements ticket 27449.
7294 - Show config.log and test-suite.log after failed Appveyor builds.
7295 Also upload the zipped full logs as a build artifact. Implements
7297 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
7298 - Enable macOS builds in our Travis CI configuration. Closes
7300 - Install libcap-dev and libseccomp2-dev so these optional
7301 dependencies get tested on Travis CI. Closes ticket 26560.
7302 - Only post Appveyor IRC notifications when the build fails.
7303 Implements ticket 27275.
7304 - Run asciidoc during Travis CI. Implements ticket 27087.
7305 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7306 - Add the necessary configuration files for continuous integration
7307 testing on Windows, via the Appveyor platform. Closes ticket
7308 25549. Patches from Marcin Cieślak and Isis Lovecruft.
7310 o Minor features (continuous integration, rust):
7311 - Use cargo cache in our Travis CI configuration. Closes
7314 o Minor features (control port):
7315 - Introduce GETINFO "current-time/{local,utc}" to return the local
7316 and UTC times respectively in ISO format. This helps a controller
7317 like Tor Browser detect a time-related error. Closes ticket 25511.
7318 Patch by Neel Chauhan.
7319 - Introduce new fields to the CIRC_BW event. There are two new
7320 fields in each of the read and written directions. The DELIVERED
7321 fields report the total valid data on the circuit, as measured by
7322 the payload sizes of verified and error-checked relay command
7323 cells. The OVERHEAD fields report the total unused bytes in each
7324 of these cells. Closes ticket 25903.
7326 o Minor features (controller):
7327 - The control port now exposes the list of HTTPTunnelPorts and
7328 ExtOrPorts via GETINFO net/listeners/httptunnel and
7329 net/listeners/extor respectively. Closes ticket 26647.
7331 o Minor features (directory authorities):
7332 - Stop warning about incomplete bw lines before the first complete
7333 bw line has been found, so that additional header lines can be
7334 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
7335 - Authorities no longer vote to make the subprotocol version
7336 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7337 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7339 o Minor features (directory authority):
7340 - Directory authorities now open their key-pinning files as O_SYNC,
7341 to limit their chances of accidentally writing partial lines.
7342 Closes ticket 23909.
7344 o Minor features (directory authority, forward compatibility):
7345 - Make the lines of the measured bandwidth file able to contain
7346 their entries in any order. Previously, the node_id entry needed
7347 to come first. Closes ticket 26004.
7349 o Minor features (entry guards):
7350 - Introduce a new torrc option NumPrimaryGuards for controlling the
7351 number of primary guards. Closes ticket 25843.
7353 o Minor features (geoip):
7354 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7355 Country database. Closes ticket 27089.
7357 o Minor features (performance):
7358 - Avoid a needless call to malloc() when processing an incoming
7359 relay cell. Closes ticket 24914.
7360 - Make our timing-wheel code run a tiny bit faster on 32-bit
7361 platforms, by preferring 32-bit math to 64-bit. Closes
7363 - Avoid a needless malloc()/free() pair every time we handle an ntor
7364 handshake. Closes ticket 25150.
7366 o Minor features (Rust, portability):
7367 - Rust cross-compilation is now supported. Closes ticket 25895.
7369 o Minor features (testing):
7370 - Add a unit test for voting_schedule_get_start_of_next_interval().
7371 Closes ticket 26014, and helps make unit test coverage
7373 - A new unittests module specifically for testing the functions in
7374 the (new-ish) bridges.c module has been created with new
7375 unittests, raising the code coverage percentages. Closes 25425.
7376 - We now have improved testing for addressmap_get_virtual_address()
7377 function. This should improve our test coverage, and make our test
7378 coverage more deterministic. Closes ticket 25993.
7380 o Minor features (timekeeping, circuit scheduling):
7381 - When keeping track of how busy each circuit have been recently on
7382 a given connection, use coarse-grained monotonic timers rather
7383 than gettimeofday(). This change should marginally increase
7384 accuracy and performance. Implements part of ticket 25927.
7386 o Minor features (unit tests):
7387 - Test complete bandwidth measurements files, and test that
7388 incomplete bandwidth lines only give warnings when the end of the
7389 header has not been detected. Fixes bug 25947; bugfix
7392 o Minor bugfixes (bandwidth management):
7393 - Consider ourselves "low on write bandwidth" if we have exhausted
7394 our write bandwidth some time in the last second. This was the
7395 documented behavior before, but the actual behavior was to change
7396 this value every TokenBucketRefillInterval. Fixes bug 25828;
7397 bugfix on 0.2.3.5-alpha.
7399 o Minor bugfixes (C correctness):
7400 - Add a missing lock acquisition in the shutdown code of the control
7401 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
7402 Coverity; this is CID 1433643.
7404 o Minor bugfixes (code style):
7405 - Fixed multiple includes of transports.h in src/or/connection.c
7406 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
7407 - Remove the unused variable n_possible from the function
7408 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
7410 o Minor bugfixes (compilation):
7411 - Silence a spurious compiler warning on the GetAdaptersAddresses
7412 function pointer cast. This issue is already fixed by 26481 in
7413 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7414 bugfix on 0.2.3.11-alpha.
7415 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7416 supported, and always fails. Some compilers warn about the
7417 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7419 - Fix a compilation warning on some versions of GCC when building
7420 code that calls routerinfo_get_my_routerinfo() twice, assuming
7421 that the second call will succeed if the first one did. Fixes bug
7422 26269; bugfix on 0.2.8.2-alpha.
7423 - Refrain from compiling unit testing related object files when
7424 --disable-unittests is set to configure script. Fixes bug 24891;
7425 bugfix on 0.2.5.1-alpha.
7426 - The --enable-fatal-warnings flag now affects Rust code as well.
7427 Closes ticket 26245.
7428 - Avoid a compiler warning when casting the return value of
7429 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
7430 26283; bugfix on 0.2.4.10-alpha.
7432 o Minor bugfixes (compilation, windows):
7433 - Don't link or search for pthreads when building for Windows, even
7434 if we are using build environment (like mingw) that provides a
7435 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7437 o Minor bugfixes (continuous integration):
7438 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7439 - Skip a pair of unreliable key generation tests on Windows, until
7440 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7441 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7443 o Minor bugfixes (control port):
7444 - Respond with more human-readable error messages to GETINFO exit-
7445 policy/* requests. Also, let controller know if an error is
7446 transient (response code 551) or not (response code 552). Fixes
7447 bug 25852; bugfix on 0.2.8.1-alpha.
7448 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
7449 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
7450 on 0.3.3.1-alpha. Patch by "akwizgran".
7451 - Make CIRC_BW event reflect the total of all data sent on a
7452 circuit, including padding and dropped cells. Also fix a mis-
7453 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
7454 bugfix on 0.2.5.2-alpha.
7456 o Minor bugfixes (correctness, flow control):
7457 - Upon receiving a stream-level SENDME cell, verify that our window
7458 has not grown too large. Fixes bug 26214; bugfix on svn
7461 o Minor bugfixes (directory authority):
7462 - When voting for recommended versions, make sure that all of the
7463 versions are well-formed and parsable. Fixes bug 26485; bugfix
7466 o Minor bugfixes (directory client):
7467 - When unverified-consensus is verified, rename it to cached-
7468 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
7469 - Fixed launching a certificate fetch always during the scheduled
7470 periodic consensus fetch by fetching only in those cases when
7471 consensus are waiting for certs. Fixes bug 24740; bugfix
7474 o Minor bugfixes (error reporting):
7475 - Improve tolerance for directory authorities with skewed clocks.
7476 Previously, an authority with a clock more than 60 seconds ahead
7477 could cause a client with a correct clock to warn that the
7478 client's clock was behind. Now the clocks of a majority of
7479 directory authorities have to be ahead of the client before this
7480 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
7482 o Minor bugfixes (in-process restart):
7483 - Always call tor_free_all() when leaving tor_run_main(). When we
7484 did not, restarting tor in-process would cause an assertion
7485 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
7487 o Minor bugfixes (Linux seccomp2 sandbox):
7488 - Fix a bug in our sandboxing rules for the openat() syscall.
7489 Previously, no openat() call would be permitted, which would break
7490 filesystem operations on recent glibc versions. Fixes bug 25440;
7491 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7493 o Minor bugfixes (logging):
7494 - Improve the log message when connection initiators fail to
7495 authenticate direct connections to relays. Fixes bug 26927; bugfix
7498 o Minor bugfixes (onion services):
7499 - Silence a spurious compiler warning in
7500 rend_client_send_introduction(). Fixes bug 27463; bugfix
7502 - Fix bug that causes services to not ever rotate their descriptors
7503 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7505 - Recompute some consensus information after detecting a clock jump,
7506 or after transitioning from a non-live consensus to a live
7507 consensus. We do this to avoid having an outdated state, and
7508 miscalculating the index for next-generation onion services. Fixes
7509 bug 24977; bugfix on 0.3.2.1-alpha.
7511 o Minor bugfixes (portability):
7512 - Fix compilation of the unit tests on GNU/Hurd, which does not
7513 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
7515 - Work around two different bugs in the OS X 10.10 and later SDKs
7516 that would prevent us from successfully targeting earlier versions
7517 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
7518 - Do not align mmap length, as it is not required by POSIX, and the
7519 getpagesize function is deprecated. Fixes bug 25399; bugfix
7522 o Minor bugfixes (portability, FreeBSD):
7523 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
7524 does not stringify on FreeBSD, so we switch to tor_asprintf().
7525 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
7527 o Minor bugfixes (relay statistics):
7528 - When a relay is collecting internal statistics about how many
7529 create cell requests it has seen of each type, accurately count
7530 the requests from relays that temporarily fall out of the
7531 consensus. (To be extra conservative, we were already ignoring
7532 requests from clients in our counts, and we continue ignoring them
7533 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
7535 o Minor bugfixes (rust):
7536 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7538 - Protover parsing was accepting the presence of whitespace in
7539 version strings, which the C implementation would choke on, e.g.
7540 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
7541 - Protover parsing was ignoring a 2nd hyphen and everything after
7542 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
7544 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
7545 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
7546 - cd to ${abs_top_builddir}/src/rust before running cargo in
7547 src/test/test_rust.sh. This makes the working directory consistent
7548 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
7550 o Minor bugfixes (single onion services, Tor2web):
7551 - Log a protocol warning when single onion services or Tor2web
7552 clients fail to authenticate direct connections to relays. Fixes
7553 bug 26924; bugfix on 0.2.9.1-alpha.
7555 o Minor bugfixes (test coverage tools):
7556 - Update our "cov-diff" script to handle output from the latest
7557 version of gcov, and to remove extraneous timestamp information
7558 from its output. Fixes bugs 26101 and 26102; bugfix
7561 o Minor bugfixes (testing):
7562 - Disable core dumps in test_bt.sh, to avoid failures in "make
7563 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7564 - When testing workqueue event-cancellation, make sure that we
7565 actually cancel an event, and that cancel each event with equal
7566 probability. (It was previously possible, though extremely
7567 unlikely, for our event-canceling test not to cancel any events.)
7568 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
7569 - Repeat part of the test in test_client_pick_intro() a number of
7570 times, to give it consistent coverage. Fixes bug 25996; bugfix
7572 - Remove randomness from the hs_common/responsible_hsdirs test, so
7573 that it always takes the same path through the function it tests.
7574 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
7575 - Change the behavior of the "channel/outbound" test so that it
7576 never causes a 10-second rollover for the EWMA circuitmux code.
7577 Previously, this behavior would happen randomly, and result in
7578 fluctuating test coverage. Fixes bug 25994; bugfix
7580 - Use X509_new() to allocate certificates that will be freed later
7581 with X509_free(). Previously, some parts of the unit tests had
7582 used tor_malloc_zero(), which is incorrect, and which caused test
7583 failures on Windows when they were built with extra hardening.
7584 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
7586 - While running the circuit_timeout test, fix the PRNG to a
7587 deterministic AES stream, so that the test coverage from this test
7588 will itself be deterministic. Fixes bug 25995; bugfix
7591 o Minor bugfixes (testing, bootstrap):
7592 - When calculating bootstrap progress, check exit policies and the
7593 exit flag. Previously, Tor would only check the exit flag, which
7594 caused race conditions in small and fast networks like chutney.
7595 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
7597 o Minor bugfixes (testing, chutney):
7598 - When running make test-network-all, use the mixed+hs-v2 network.
7599 (A previous fix to chutney removed v3 onion services from the
7600 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
7601 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
7602 - Before running make test-network-all, delete old logs and test
7603 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7606 o Minor bugfixes (testing, openssl compatibility):
7607 - Our "tortls/cert_matches_key" unit test no longer relies on
7608 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7609 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7610 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7612 o Minor bugfixes (v3 onion services):
7613 - Stop sending ed25519 link specifiers in v3 onion service introduce
7614 cells and descriptors, when the rendezvous or introduction point
7615 doesn't support ed25519 link authentication. Fixes bug 26627;
7616 bugfix on 0.3.2.4-alpha.
7618 o Minor bugfixes (vanguards):
7619 - Allow the last hop in a vanguard circuit to be the same as our
7620 first, to prevent the adversary from influencing guard node choice
7621 by choice of last hop. Also prevent the creation of A - B - A
7622 paths, or A - A paths, which are forbidden by relays. Fixes bug
7623 25870; bugfix on 0.3.3.1-alpha.
7625 o Minor bugfixes (Windows, compilation):
7626 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7627 27185; bugfix on 0.2.2.2-alpha.
7629 o Code simplification and refactoring:
7630 - Remove duplicate code in parse_{c,s}method_line and bootstrap
7631 their functionalities into a single function. Fixes bug 6236;
7632 bugfix on 0.2.3.6-alpha.
7633 - We remove the PortForwarding and PortForwardingHelper options,
7634 related functions, and the port_forwarding tests. These options
7635 were used by the now-deprecated Vidalia to help ordinary users
7636 become Tor relays or bridges. Closes ticket 25409. Patch by
7638 - In order to make the OR and dir checking function in router.c less
7639 confusing we renamed some functions and
7640 consider_testing_reachability() has been split into
7641 router_should_check_reachability() and
7642 router_do_reachability_checks(). Also we improved the documentation
7643 in some functions. Closes ticket 18918.
7644 - Initial work to isolate Libevent usage to a handful of modules in
7645 our codebase, to simplify our call structure, and so that we can
7646 more easily change event loops in the future if needed. Closes
7648 - Introduce a function to call getsockname() and return tor_addr_t,
7649 to save a little complexity throughout the codebase. Closes
7651 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
7652 as hsdir_index is always present. Also, we move hsdir_index_t into
7653 or.h. Closes ticket 23094. Patch by Neel Chauhan.
7654 - Merge functions used for describing nodes and suppress the
7655 functions that do not allocate memory for the output buffer
7656 string. NODE_DESC_BUF_LEN constant and format_node_description()
7657 function cannot be used externally from router.c module anymore.
7658 Closes ticket 25432. Patch by valentecaio.
7659 - Our main loop has been simplified so that all important operations
7660 happen inside events. Previously, some operations had to happen
7661 outside the event loop, to prevent infinite sequences of event
7662 activations. Closes ticket 25374.
7663 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
7664 it in register_intro_circ() and service_intro_point_new(). This
7665 prevents the digest from being re-calculated each time. Closes
7666 ticket 23107. Patch by Neel Chauhan.
7667 - Refactor token-bucket implementations to use a common backend.
7668 Closes ticket 25766.
7669 - Remove extern declaration of stats_n_seconds_working variable from
7670 main, protecting its accesses with get_uptime() and reset_uptime()
7671 functions. Closes ticket 25081, patch by “valentecaio”.
7672 - Remove our previous logic for "cached gettimeofday()" -- our
7673 coarse monotonic timers are fast enough for this purpose, and far
7674 less error-prone. Implements part of ticket 25927.
7675 - Remove the return value for fascist_firewall_choose_address_base(),
7676 and sister functions such as fascist_firewall_choose_address_node()
7677 and fascist_firewall_choose_address_rs(). Also, while we're here,
7678 initialize the ap argument as leaving it uninitialized can pose a
7679 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
7680 - Rename two fields of connection_t struct. timestamp_lastwritten is
7681 renamed to timestamp_last_write_allowed and timestamp_lastread is
7682 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
7684 - Since Tor requires C99, remove our old workaround code for libc
7685 implementations where free(NULL) doesn't work. Closes ticket 24484.
7686 - Use our standard rate-limiting code to deal with excessive
7687 libevent failures, rather than the hand-rolled logic we had
7688 before. Closes ticket 26016.
7689 - We remove the return value of node_get_prim_orport() and
7690 node_get_prim_dirport(), and introduce node_get_prim_orport() in
7691 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
7692 check for a null address. Closes ticket 23873. Patch by
7694 - We switch to should_record_bridge_info() in
7695 geoip_note_client_seen() and options_need_geoip_info() instead of
7696 accessing the configuration values directly. Fixes bug 25290;
7697 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
7699 o Deprecated features:
7700 - As we are not recommending 0.2.5 anymore, we require relays that
7701 once had an ed25519 key associated with their RSA key to always
7702 have that key, instead of allowing them to drop back to a version
7703 that didn't support ed25519. This means they need to use a new RSA
7704 key if they want to downgrade to an older version of tor without
7705 ed25519. Closes ticket 20522.
7708 - Directory authorities will no longer support voting according to
7709 any consensus method before consensus method 25. This keeps
7710 authorities compatible with all authorities running 0.2.9.8 and
7711 later, and does not break any clients or relays. Implements ticket
7712 24378 and proposal 290.
7713 - The PortForwarding and PortForwardingHelper features have been
7714 removed. The reasoning is, given that implementations of NAT
7715 traversal protocols within common consumer grade routers are
7716 frequently buggy, and that the target audience for a NAT punching
7717 feature is a perhaps less-technically-inclined relay operator,
7718 when the helper fails to setup traversal the problems are usually
7719 deep, ugly, and very router specific, making them horrendously
7720 impossible for technical support to reliable assist with, and thus
7721 resulting in frustration all around. Unfortunately, relay
7722 operators who would like to run relays behind NATs will need to
7723 become more familiar with the port forwarding configurations on
7724 their local router. Closes 25409.
7725 - The TestingEnableTbEmptyEvent option has been removed. It was used
7726 in testing simulations to measure how often connection buckets
7727 were emptied, in order to improve our scheduling, but it has not
7728 been actively used in years. Closes ticket 25760.
7729 - The old "round-robin" circuit multiplexer (circuitmux)
7730 implementation has been removed, along with a fairly large set of
7731 code that existed to support it. It has not been the default
7732 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
7733 but it still required an unreasonable amount of memory and CPU.
7734 Closes ticket 25268.
7737 Changes in version 0.3.3.9 - 2018-07-13
7738 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
7739 bridge relays should upgrade.
7741 o Directory authority changes:
7742 - The "Bifroest" bridge authority has been retired; the new bridge
7743 authority is "Serge", and it is operated by George from the
7744 TorBSD project. Closes ticket 26771.
7747 Changes in version 0.3.2.11 - 2018-07-13
7748 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
7749 bridge relays should upgrade. We also take this opportunity to backport
7752 o Directory authority changes:
7753 - The "Bifroest" bridge authority has been retired; the new bridge
7754 authority is "Serge", and it is operated by George from the
7755 TorBSD project. Closes ticket 26771.
7757 o Directory authority changes (backport from 0.3.3.7):
7758 - Add an IPv6 address for the "dannenberg" directory authority.
7759 Closes ticket 26343.
7761 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7762 - When directory authorities read a zero-byte bandwidth file, they
7763 would previously log a warning with the contents of an
7764 uninitialised buffer. They now log a warning about the empty file
7765 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7767 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
7768 - Correctly detect when onion services get disabled after HUP. Fixes
7769 bug 25761; bugfix on 0.3.2.1.
7771 o Minor features (sandbox, backport from 0.3.3.4-alpha):
7772 - Explicitly permit the poll() system call when the Linux
7773 seccomp2-based sandbox is enabled: apparently, some versions of
7774 libc use poll() when calling getpwnam(). Closes ticket 25313.
7776 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
7777 - Update the Travis CI configuration to use the stable Rust channel,
7778 now that we have decided to require that. Closes ticket 25714.
7780 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7781 - Our .travis.yml configuration now includes support for testing the
7782 results of "make distcheck". (It's not uncommon for "make check"
7783 to pass but "make distcheck" to fail.) Closes ticket 25814.
7784 - Our Travis CI configuration now integrates with the Coveralls
7785 coverage analysis tool. Closes ticket 25818.
7787 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
7788 - Add several checks to detect whether Tor relays are uploading
7789 their descriptors without specifying why they regenerated them.
7790 Diagnostic for ticket 25686.
7792 o Minor features (compilation, backport from 0.3.4.4-rc):
7793 - When building Tor, prefer to use Python 3 over Python 2, and more
7794 recent (contemplated) versions over older ones. Closes
7797 o Minor features (geoip):
7798 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7799 Country database. Closes ticket 26674.
7801 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7802 - Upon receiving a malformed connected cell, stop processing the
7803 cell immediately. Previously we would mark the connection for
7804 close, but continue processing the cell as if the connection were
7805 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7807 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7808 - Allow the nanosleep() system call, which glibc uses to implement
7809 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7811 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7812 - When running the hs_ntor_ref.py test, make sure only to pass
7813 strings (rather than "bytes" objects) to the Python subprocess
7814 module. Python 3 on Windows seems to require this. Fixes bug
7815 26535; bugfix on 0.3.1.1-alpha.
7816 - When running the ntor_ref.py test, make sure only to pass strings
7817 (rather than "bytes" objects) to the Python subprocess module.
7818 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7821 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7822 - Work around a change in OpenSSL 1.1.1 where return values that
7823 would previously indicate "no password" now indicate an empty
7824 password. Without this workaround, Tor instances running with
7825 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7826 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7828 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
7829 - Document that the PerConnBW{Rate,Burst} options will fall back to
7830 their corresponding consensus parameters only if those parameters
7831 are set. Previously we had claimed that these values would always
7832 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7834 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7835 - Fix a compilation warning on some versions of GCC when building
7836 code that calls routerinfo_get_my_routerinfo() twice, assuming
7837 that the second call will succeed if the first one did. Fixes bug
7838 26269; bugfix on 0.2.8.2-alpha.
7840 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7841 - Don't consider Tor running as a client if the ControlPort is open,
7842 but no actual client ports are open. Fixes bug 26062; bugfix
7845 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7846 - Prevent a possible out-of-bounds smartlist read in
7847 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7849 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
7850 - Fix a very unlikely (impossible, we believe) null pointer
7851 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7852 Coverity; this is CID 1430932.
7854 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7855 - Fix a memory leak when a v3 onion service is configured and gets a
7856 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7857 - When parsing the descriptor signature, look for the token plus an
7858 extra white-space at the end. This is more correct but also will
7859 allow us to support new fields that might start with "signature".
7860 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7862 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
7863 - Relays now correctly block attempts to re-extend to the previous
7864 relay by Ed25519 identity. Previously they would warn in this
7865 case, but not actually reject the attempt. Fixes bug 26158; bugfix
7868 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7869 - Avoid a crash when running with DirPort set but ORPort turned off.
7870 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7872 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
7873 - Silence unused-const-variable warnings in zstd.h with some GCC
7874 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7876 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
7877 - Avoid intermittent test failures due to a test that had relied on
7878 onion service introduction point creation finishing within 5
7879 seconds of real clock time. Fixes bug 25450; bugfix
7882 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
7883 - Fix a C99 compliance issue in our configuration script that caused
7884 compilation issues when compiling Tor with certain versions of
7885 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7887 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7888 - Fix a number of small memory leaks identified by coverity. Fixes
7889 bug 26467; bugfix on numerous Tor versions.
7891 o Code simplification and refactoring (backport from 0.3.3.5-rc):
7892 - Move the list of default directory authorities to its own file.
7893 Closes ticket 24854. Patch by "beastr0".
7896 Changes in version 0.2.9.16 - 2018-07-13
7897 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
7898 bridge relays should upgrade. We also take this opportunity to backport
7901 o Directory authority changes:
7902 - The "Bifroest" bridge authority has been retired; the new bridge
7903 authority is "Serge", and it is operated by George from the
7904 TorBSD project. Closes ticket 26771.
7906 o Directory authority changes (backport from 0.3.3.7):
7907 - Add an IPv6 address for the "dannenberg" directory authority.
7908 Closes ticket 26343.
7910 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7911 - When directory authorities read a zero-byte bandwidth file, they
7912 would previously log a warning with the contents of an
7913 uninitialised buffer. They now log a warning about the empty file
7914 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7916 o Minor features (sandbox, backport from 0.3.3.4-alpha):
7917 - Explicitly permit the poll() system call when the Linux
7918 seccomp2-based sandbox is enabled: apparently, some versions of
7919 libc use poll() when calling getpwnam(). Closes ticket 25313.
7921 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7922 - Our .travis.yml configuration now includes support for testing the
7923 results of "make distcheck". (It's not uncommon for "make check"
7924 to pass but "make distcheck" to fail.) Closes ticket 25814.
7925 - Our Travis CI configuration now integrates with the Coveralls
7926 coverage analysis tool. Closes ticket 25818.
7928 o Minor features (compilation, backport from 0.3.4.4-rc):
7929 - When building Tor, prefer to use Python 3 over Python 2, and more
7930 recent (contemplated) versions over older ones. Closes
7933 o Minor features (geoip):
7934 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7935 Country database. Closes ticket 26674.
7937 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7938 - Upon receiving a malformed connected cell, stop processing the
7939 cell immediately. Previously we would mark the connection for
7940 close, but continue processing the cell as if the connection were
7941 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7943 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7944 - Allow the nanosleep() system call, which glibc uses to implement
7945 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7947 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7948 - When running the ntor_ref.py test, make sure only to pass strings
7949 (rather than "bytes" objects) to the Python subprocess module.
7950 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7953 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7954 - Work around a change in OpenSSL 1.1.1 where return values that
7955 would previously indicate "no password" now indicate an empty
7956 password. Without this workaround, Tor instances running with
7957 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7958 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7960 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7961 - Fix a compilation warning on some versions of GCC when building
7962 code that calls routerinfo_get_my_routerinfo() twice, assuming
7963 that the second call will succeed if the first one did. Fixes bug
7964 26269; bugfix on 0.2.8.2-alpha.
7966 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7967 - Don't consider Tor running as a client if the ControlPort is open,
7968 but no actual client ports are open. Fixes bug 26062; bugfix
7971 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7972 - Prevent a possible out-of-bounds smartlist read in
7973 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7975 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
7976 - Fix a very unlikely (impossible, we believe) null pointer
7977 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7978 Coverity; this is CID 1430932.
7980 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7981 - Fix a number of small memory leaks identified by coverity. Fixes
7982 bug 26467; bugfix on numerous Tor versions.
7984 o Code simplification and refactoring (backport from 0.3.3.5-rc):
7985 - Move the list of default directory authorities to its own file.
7986 Closes ticket 24854. Patch by "beastr0".
7989 Changes in version 0.3.3.8 - 2018-07-09
7990 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
7991 fixes for a memory leak affecting directory authorities.
7993 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
7994 - Stop leaking memory on directory authorities when planning to
7995 vote. This bug was crashing authorities by exhausting their
7996 memory. Fixes bug 26435; bugfix on 0.3.3.6.
7998 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
7999 - Make sure that failing tests in Rust will actually cause the build
8000 to fail: previously, they were ignored. Fixes bug 26258; bugfix
8003 o Minor features (compilation, backport from 0.3.4.4-rc):
8004 - When building Tor, prefer to use Python 3 over Python 2, and more
8005 recent (contemplated) versions over older ones. Closes
8008 o Minor features (geoip):
8009 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8010 Country database. Closes ticket 26674.
8012 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8013 - Add several checks to detect whether Tor relays are uploading
8014 their descriptors without specifying why they regenerated them.
8015 Diagnostic for ticket 25686.
8017 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
8018 - Don't count path selection failures as circuit build failures.
8019 This change should eliminate cases where Tor blames its guard or
8020 the network for situations like insufficient microdescriptors
8021 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
8024 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8025 - Fix a compilation warning on some versions of GCC when building
8026 code that calls routerinfo_get_my_routerinfo() twice, assuming
8027 that the second call will succeed if the first one did. Fixes bug
8028 26269; bugfix on 0.2.8.2-alpha.
8030 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
8031 - Handle the HSADDRESS= argument to the HSPOST command properly.
8032 (Previously, this argument was misparsed and thus ignored.) Fixes
8033 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
8035 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8036 - Fix a number of small memory leaks identified by coverity. Fixes
8037 bug 26467; bugfix on numerous Tor versions.
8039 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
8040 - Relays now correctly block attempts to re-extend to the previous
8041 relay by Ed25519 identity. Previously they would warn in this
8042 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8045 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
8046 - When shutting down, Tor now clears all the flags in the control.c
8047 module. This should prevent a bug where authentication cookies are
8048 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
8050 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8051 - When running the hs_ntor_ref.py test, make sure only to pass
8052 strings (rather than "bytes" objects) to the Python subprocess
8053 module. Python 3 on Windows seems to require this. Fixes bug
8054 26535; bugfix on 0.3.1.1-alpha.
8055 - When running the ntor_ref.py test, make sure only to pass strings
8056 (rather than "bytes" objects) to the Python subprocess module.
8057 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8061 Changes in version 0.3.3.7 - 2018-06-12
8062 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
8063 fixes for bugs affecting compatibility and stability.
8065 o Directory authority changes:
8066 - Add an IPv6 address for the "dannenberg" directory authority.
8067 Closes ticket 26343.
8069 o Minor features (geoip):
8070 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
8071 Country database. Closes ticket 26351.
8073 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8074 - Work around a change in OpenSSL 1.1.1 where return values that
8075 would previously indicate "no password" now indicate an empty
8076 password. Without this workaround, Tor instances running with
8077 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8078 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8080 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
8081 - Silence unused-const-variable warnings in zstd.h with some GCC
8082 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
8084 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
8085 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
8086 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
8087 miscounting the total number of circuits for these field values.)
8088 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
8090 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8091 - Prevent a possible out-of-bounds smartlist read in
8092 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8094 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
8095 - Only select relays when they have the descriptors we prefer to use
8096 for them. This change fixes a bug where we could select a relay
8097 because it had _some_ descriptor, but reject it later with a
8098 nonfatal assertion error because it didn't have the exact one we
8099 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
8102 Changes in version 0.3.3.6 - 2018-05-22
8103 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
8104 backports several important fixes from the 0.3.4.1-alpha.
8106 The Tor 0.3.3 series includes controller support and other
8107 improvements for v3 onion services, official support for embedding Tor
8108 within other applications, and our first non-trivial module written in
8109 the Rust programming language. (Rust is still not enabled by default
8110 when building Tor.) And as usual, there are numerous other smaller
8111 bugfixes, features, and improvements.
8113 Below are the changes since 0.3.2.10. For a list of only the changes
8114 since 0.3.3.5-rc, see the ChangeLog file.
8116 o New system requirements:
8117 - When built with Rust, Tor now depends on version 0.2.39 of the
8118 libc crate. Closes tickets 25310 and 25664.
8120 o Major features (embedding):
8121 - There is now a documented stable API for programs that need to
8122 embed Tor. See tor_api.h for full documentation and known bugs.
8123 Closes ticket 23684.
8124 - Tor now has support for restarting in the same process.
8125 Controllers that run Tor using the "tor_api.h" interface can now
8126 restart Tor after Tor has exited. This support is incomplete,
8127 however: we fixed crash bugs that prevented it from working at
8128 all, but many bugs probably remain, including a possibility of
8129 security issues. Implements ticket 24581.
8131 o Major features (IPv6, directory documents):
8132 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
8133 consensus. This information makes it easier for IPv6 clients to
8134 bootstrap and choose reachable entry guards. Implements
8136 - Add consensus method 28, which removes IPv6 ORPorts from
8137 microdescriptors. Now that the consensus contains IPv6 ORPorts,
8138 they are redundant in microdescs. This change will be used by Tor
8139 clients on 0.2.8.x and later. (That is to say, with all Tor
8140 clients that have IPv6 bootstrap and guard support.) Implements
8142 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
8143 set by different numbers of authorities. Fixes 23870
8146 o Major features (onion service v3, control port):
8147 - The control port now supports commands and events for v3 onion
8148 services. It is now possible to create ephemeral v3 services using
8149 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
8150 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
8151 DEL_ONION) have been extended to support v3 onion services. Closes
8152 ticket 20699; implements proposal 284.
8154 o Major features (onion services):
8155 - Provide torrc options to pin the second and third hops of onion
8156 service circuits to a list of nodes. The option HSLayer2Guards
8157 pins the second hop, and the option HSLayer3Guards pins the third
8158 hop. These options are for use in conjunction with experiments
8159 with "vanguards" for preventing guard enumeration attacks. Closes
8161 - When v3 onion service clients send introduce cells, they now
8162 include the IPv6 address of the rendezvous point, if it has one.
8163 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
8164 in future Tor versions, IPv6-only v3 single onion services will be
8165 able to use IPv6 addresses to connect directly to the rendezvous
8166 point. Closes ticket 23577. Patch by Neel Chauhan.
8168 o Major features (relay):
8169 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
8170 operator to use a more reasonable ("reduced") exit policy, rather
8171 than the default one. If you want to run an exit node without
8172 thinking too hard about which ports to allow, this one is for you.
8173 Closes ticket 13605. Patch from Neel Chauhan.
8175 o Major features (rust, portability, experimental):
8176 - Tor now ships with an optional implementation of one of its
8177 smaller modules (protover.c) in the Rust programming language. To
8178 try it out, install a Rust build environment, and configure Tor
8179 with "--enable-rust --enable-cargo-online-mode". This should not
8180 cause any user-visible changes, but should help us gain more
8181 experience with Rust, and plan future Rust integration work.
8182 Implementation by Chelsea Komlo. Closes ticket 22840.
8184 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
8185 - When directory authorities read a zero-byte bandwidth file, they
8186 would previously log a warning with the contents of an
8187 uninitialised buffer. They now log a warning about the empty file
8188 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8190 o Major bugfixes (security, directory authority, denial-of-service):
8191 - Fix a bug that could have allowed an attacker to force a directory
8192 authority to use up all its RAM by passing it a maliciously
8193 crafted protocol versions string. Fixes bug 25517; bugfix on
8194 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
8196 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
8197 - Avoid a rare assertion failure in the circuit build timeout code
8198 if we fail to allow any circuits to actually complete. Fixes bug
8199 25733; bugfix on 0.2.2.2-alpha.
8201 o Major bugfixes (netflow padding):
8202 - Stop adding unneeded channel padding right after we finish
8203 flushing to a connection that has been trying to flush for many
8204 seconds. Instead, treat all partial or complete flushes as
8205 activity on the channel, which will defer the time until we need
8206 to add padding. This fix should resolve confusing and scary log
8207 messages like "Channel padding timeout scheduled 221453ms in the
8208 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8210 o Major bugfixes (networking):
8211 - Tor will no longer reject IPv6 address strings from Tor Browser
8212 when they are passed as hostnames in SOCKS5 requests. Fixes bug
8213 25036, bugfix on Tor 0.3.1.2.
8215 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8216 - Correctly detect when onion services get disabled after HUP. Fixes
8217 bug 25761; bugfix on 0.3.2.1.
8219 o Major bugfixes (performance, load balancing):
8220 - Directory authorities no longer vote in favor of the Guard flag
8221 for relays without directory support. Starting in Tor
8222 0.3.0.1-alpha, clients have been avoiding using such relays in the
8223 Guard position, leading to increasingly broken load balancing for
8224 the 5%-or-so of Guards that don't advertise directory support.
8225 Fixes bug 22310; bugfix on 0.3.0.6.
8227 o Major bugfixes (relay):
8228 - If we have failed to connect to a relay and received a connection
8229 refused, timeout, or similar error (at the TCP level), do not try
8230 that same address/port again for 60 seconds after the failure has
8231 occurred. Fixes bug 24767; bugfix on 0.0.6.
8233 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
8234 - Impose a limit on circuit cell queue size. The limit can be
8235 controlled by a consensus parameter. Fixes bug 25226; bugfix
8238 o Minor features (cleanup):
8239 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
8240 when it stops. Closes ticket 23271.
8242 o Minor features (compatibility, backport from 0.3.4.1-alpha):
8243 - Avoid some compilation warnings with recent versions of LibreSSL.
8244 Closes ticket 26006.
8246 o Minor features (config options):
8247 - Change the way the default value for MaxMemInQueues is calculated.
8248 We now use 40% of the hardware RAM if the system has 8 GB RAM or
8249 more. Otherwise we use the former value of 75%. Closes
8252 o Minor features (continuous integration):
8253 - Update the Travis CI configuration to use the stable Rust channel,
8254 now that we have decided to require that. Closes ticket 25714.
8256 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8257 - Our .travis.yml configuration now includes support for testing the
8258 results of "make distcheck". (It's not uncommon for "make check"
8259 to pass but "make distcheck" to fail.) Closes ticket 25814.
8260 - Our Travis CI configuration now integrates with the Coveralls
8261 coverage analysis tool. Closes ticket 25818.
8263 o Minor features (defensive programming):
8264 - Most of the functions in Tor that free objects have been replaced
8265 with macros that free the objects and set the corresponding
8266 pointers to NULL. This change should help prevent a large class of
8267 dangling pointer bugs. Closes ticket 24337.
8268 - Where possible, the tor_free() macro now only evaluates its input
8269 once. Part of ticket 24337.
8270 - Check that microdesc ed25519 ids are non-zero in
8271 node_get_ed25519_id() before returning them. Implements ticket
8272 24001, patch by "aruna1234".
8274 o Minor features (directory authority):
8275 - When directory authorities are unable to add signatures to a
8276 pending consensus, log the reason why. Closes ticket 24849.
8278 o Minor features (embedding):
8279 - Tor can now start with a preauthenticated control connection
8280 created by the process that launched it. This feature is meant for
8281 use by programs that want to launch and manage a Tor process
8282 without allowing other programs to manage it as well. For more
8283 information, see the __OwningControllerFD option documented in
8284 control-spec.txt. Closes ticket 23900.
8285 - On most errors that would cause Tor to exit, it now tries to
8286 return from the tor_main() function, rather than calling the
8287 system exit() function. Most users won't notice a difference here,
8288 but it should be significant for programs that run Tor inside a
8289 separate thread: they should now be able to survive Tor's exit
8290 conditions rather than having Tor shut down the entire process.
8291 Closes ticket 23848.
8292 - Applications that want to embed Tor can now tell Tor not to
8293 register any of its own POSIX signal handlers, using the
8294 __DisableSignalHandlers option. Closes ticket 24588.
8296 o Minor features (fallback directory list):
8297 - Avoid selecting fallbacks that change their IP addresses too
8298 often. Select more fallbacks by ignoring the Guard flag, and
8299 allowing lower cutoffs for the Running and V2Dir flags. Also allow
8300 a lower bandwidth, and a higher number of fallbacks per operator
8301 (5% of the list). Implements ticket 24785.
8302 - Update the fallback whitelist and blacklist based on opt-ins and
8303 relay changes. Closes tickets 22321, 24678, 22527, 24135,
8306 o Minor features (fallback directory mirror configuration):
8307 - Add a nickname to each fallback in a C comment. This makes it
8308 easier for operators to find their relays, and allows stem to use
8309 nicknames to identify fallbacks. Implements ticket 24600.
8310 - Add a type and version header to the fallback directory mirror
8311 file. Also add a delimiter to the end of each fallback entry. This
8312 helps external parsers like stem and Relay Search. Implements
8314 - Add an extrainfo cache flag for each fallback in a C comment. This
8315 allows stem to use fallbacks to fetch extra-info documents, rather
8316 than using authorities. Implements ticket 22759.
8317 - Add the generateFallbackDirLine.py script for automatically
8318 generating fallback directory mirror lines from relay fingerprints.
8319 No more typos! Add the lookupFallbackDirContact.py script for
8320 automatically looking up operator contact info from relay
8321 fingerprints. Implements ticket 24706, patch by teor and atagar.
8322 - Reject any fallback directory mirror that serves an expired
8323 consensus. Implements ticket 20942, patch by "minik".
8324 - Remove commas and equals signs from external string inputs to the
8325 fallback list. This avoids format confusion attacks. Implements
8327 - Remove the "weight=10" line from fallback directory mirror
8328 entries. Ticket 24681 will maintain the current fallback weights
8329 by changing Tor's default fallback weight to 10. Implements
8331 - Stop logging excessive information about fallback netblocks.
8332 Implements ticket 24791.
8334 o Minor features (forward-compatibility):
8335 - If a relay supports some link authentication protocol that we do
8336 not recognize, then include that relay's ed25519 key when telling
8337 other relays to extend to it. Previously, we treated future
8338 versions as if they were too old to support ed25519 link
8339 authentication. Closes ticket 20895.
8341 o Minor features (geoip):
8342 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
8343 database. Closes ticket 26104.
8345 o Minor features (heartbeat):
8346 - Add onion service information to our heartbeat logs, displaying
8347 stats about the activity of configured onion services. Closes
8350 o Minor features (instrumentation, development):
8351 - Add the MainloopStats option to allow developers to get
8352 instrumentation information from the main event loop via the
8353 heartbeat messages. We hope to use this to improve Tor's behavior
8354 when it's trying to sleep. Closes ticket 24605.
8356 o Minor features (IPv6):
8357 - Make IPv6-only clients wait for microdescs for relays, even if we
8358 were previously using descriptors (or were using them as a bridge)
8359 and have a cached descriptor for them. Implements ticket 23827.
8360 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
8361 them, rather than waiting to download microdescriptors. Implements
8364 o Minor features (log messages):
8365 - Improve log message in the out-of-memory handler to include
8366 information about memory usage from the different compression
8367 backends. Closes ticket 25372.
8368 - Improve a warning message that happens when we fail to re-parse an
8369 old router because of an expired certificate. Closes ticket 20020.
8370 - Make the log more quantitative when we hit MaxMemInQueues
8371 threshold exposing some values. Closes ticket 24501.
8373 o Minor features (logging):
8374 - Clarify the log messages produced when getrandom() or a related
8375 entropy-generation mechanism gives an error. Closes ticket 25120.
8376 - Added support for the Android logging subsystem. Closes
8379 o Minor features (performance):
8380 - Support predictive circuit building for onion service circuits
8381 with multiple layers of guards. Closes ticket 23101.
8382 - Use stdatomic.h where available, rather than mutexes, to implement
8383 atomic_counter_t. Closes ticket 23953.
8385 o Minor features (performance, 32-bit):
8386 - Improve performance on 32-bit systems by avoiding 64-bit division
8387 when calculating the timestamp in milliseconds for channel padding
8388 computations. Implements ticket 24613.
8389 - Improve performance on 32-bit systems by avoiding 64-bit division
8390 when timestamping cells and buffer chunks for OOM calculations.
8391 Implements ticket 24374.
8393 o Minor features (performance, OSX, iOS):
8394 - Use the mach_approximate_time() function (when available) to
8395 implement coarse monotonic time. Having a coarse time function
8396 should avoid a large number of system calls, and improve
8397 performance slightly, especially under load. Closes ticket 24427.
8399 o Minor features (performance, windows):
8400 - Improve performance on Windows Vista and Windows 7 by adjusting
8401 TCP send window size according to the recommendation from
8402 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
8405 o Minor features (sandbox):
8406 - Explicitly permit the poll() system call when the Linux
8407 seccomp2-based sandbox is enabled: apparently, some versions of
8408 libc use poll() when calling getpwnam(). Closes ticket 25313.
8410 o Minor features (storage, configuration):
8411 - Users can store cached directory documents somewhere other than
8412 the DataDirectory by using the CacheDirectory option. Similarly,
8413 the storage location for relay's keys can be overridden with the
8414 KeyDirectory option. Closes ticket 22703.
8416 o Minor features (testing):
8417 - Add a "make test-rust" target to run the rust tests only. Closes
8420 o Minor features (testing, debugging, embedding):
8421 - For development purposes, Tor now has a mode in which it runs for
8422 a few seconds, then stops, and starts again without exiting the
8423 process. This mode is meant to help us debug various issues with
8424 ticket 23847. To use this feature, compile with
8425 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
8426 environment variable. This is expected to crash a lot, and is
8427 really meant for developers only. It will likely be removed in a
8428 future release. Implements ticket 24583.
8430 o Minor bugfixes (build, rust):
8431 - Fix output of autoconf checks to display success messages for Rust
8432 dependencies and a suitable rustc compiler version. Fixes bug
8433 24612; bugfix on 0.3.1.3-alpha.
8434 - Don't pass the --quiet option to cargo: it seems to suppress some
8435 errors, which is not what we want to do when building. Fixes bug
8436 24518; bugfix on 0.3.1.7.
8437 - Build correctly when building from outside Tor's source tree with
8438 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
8441 o Minor bugfixes (C correctness):
8442 - Fix a very unlikely (impossible, we believe) null pointer
8443 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8444 Coverity; this is CID 1430932.
8446 o Minor bugfixes (channel, client):
8447 - Better identify client connection when reporting to the geoip
8448 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
8450 o Minor bugfixes (circuit, cannibalization):
8451 - Don't cannibalize preemptively-built circuits if we no longer
8452 recognize their first hop. This situation can happen if our Guard
8453 relay went off the consensus after the circuit was created. Fixes
8454 bug 24469; bugfix on 0.0.6.
8456 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8457 - Don't consider Tor running as a client if the ControlPort is open,
8458 but no actual client ports are open. Fixes bug 26062; bugfix
8461 o Minor bugfixes (compilation):
8462 - Fix a C99 compliance issue in our configuration script that caused
8463 compilation issues when compiling Tor with certain versions of
8464 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
8466 o Minor bugfixes (controller):
8467 - Restore the correct operation of the RESOLVE command, which had
8468 been broken since we added the ability to enable/disable DNS on
8469 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
8470 - Avoid a (nonfatal) assertion failure when extending a one-hop
8471 circuit from the controller to become a multihop circuit. Fixes
8472 bug 24903; bugfix on 0.2.5.2-alpha.
8474 o Minor bugfixes (correctness):
8475 - Remove a nonworking, unnecessary check to see whether a circuit
8476 hop's identity digest was set when the circuit failed. Fixes bug
8477 24927; bugfix on 0.2.4.4-alpha.
8479 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8480 - Upon receiving a malformed connected cell, stop processing the
8481 cell immediately. Previously we would mark the connection for
8482 close, but continue processing the cell as if the connection were
8483 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8485 o Minor bugfixes (directory authorities, IPv6):
8486 - When creating a routerstatus (vote) from a routerinfo (descriptor),
8487 set the IPv6 address to the unspecified IPv6 address, and
8488 explicitly initialize the port to zero. Fixes bug 24488; bugfix
8491 o Minor bugfixes (documentation):
8492 - Document that the PerConnBW{Rate,Burst} options will fall back to
8493 their corresponding consensus parameters only if those parameters
8494 are set. Previously we had claimed that these values would always
8495 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
8497 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
8498 - Stop saying in the manual that clients cache ipv4 dns answers from
8499 exit relays. We haven't used them since 0.2.6.3-alpha, and in
8500 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
8501 we forgot to say so in the man page. Fixes bug 26052; bugfix
8504 o Minor bugfixes (exit relay DNS retries):
8505 - Re-attempt timed-out DNS queries 3 times before failure, since our
8506 timeout is 5 seconds for them, but clients wait 10-15. Also allow
8507 slightly more timeouts per resolver when an exit has multiple
8508 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
8510 o Minor bugfixes (fallback directory mirrors):
8511 - Make updateFallbackDirs.py search harder for python. (Some OSs
8512 don't put it in /usr/bin.) Fixes bug 24708; bugfix
8515 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
8516 - When hibernating, close connections normally and allow them to
8517 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
8519 - Do not attempt to launch self-reachability tests when entering
8520 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8521 - Resolve several bugs related to descriptor fetching on bridge
8522 clients with bandwidth accounting enabled. (This combination is
8523 not recommended!) Fixes a case of bug 12062; bugfix
8525 - When hibernating, do not attempt to launch DNS checks. Fixes a
8526 case of bug 12062; bugfix on 0.1.2.2-alpha.
8527 - When hibernating, do not try to upload or download descriptors.
8528 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8530 o Minor bugfixes (IPv6, bridges):
8531 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
8532 bugfix on 0.2.8.2-alpha.
8533 - Tor now sets IPv6 address in the routerstatus as well as in the
8534 router descriptors when updating addresses for a bridge. Closes
8535 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
8537 o Minor bugfixes (Linux seccomp2 sandbox):
8538 - When running with the sandbox enabled, reload configuration files
8539 correctly even when %include was used. Previously we would crash.
8540 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
8542 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8543 - Allow the nanosleep() system call, which glibc uses to implement
8544 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8546 o Minor bugfixes (logging):
8547 - Fix a (mostly harmless) race condition when invoking
8548 LOG_PROTOCOL_WARN message from a subthread while the torrc options
8549 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
8551 o Minor bugfixes (man page, SocksPort):
8552 - Remove dead code from the old "SocksSocket" option, and rename
8553 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
8554 option still works, but is deprecated. Fixes bug 24343; bugfix
8557 o Minor bugfixes (memory leaks):
8558 - Avoid possible at-exit memory leaks related to use of Libevent's
8559 event_base_once() function. (This function tends to leak memory if
8560 the event_base is closed before the event fires.) Fixes bug 24584;
8561 bugfix on 0.2.8.1-alpha.
8562 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
8565 o Minor bugfixes (network IPv6 test):
8566 - Tor's test scripts now check if "ping -6 ::1" works when the user
8567 runs "make test-network-all". Fixes bug 24677; bugfix on
8568 0.2.9.3-alpha. Patch by "ffmancera".
8570 o Minor bugfixes (networking):
8571 - string_is_valid_hostname() will not consider IP strings to be
8572 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
8574 o Minor bugfixes (onion service v3):
8575 - Avoid an assertion failure when the next onion service descriptor
8576 rotation type is out of sync with the consensus's valid-after
8577 time. Instead, log a warning message with extra information, so we
8578 can better hunt down the cause of this assertion. Fixes bug 25306;
8579 bugfix on 0.3.2.1-alpha.
8581 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
8582 - Fix a memory leak when a v3 onion service is configured and gets a
8583 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
8584 - When parsing the descriptor signature, look for the token plus an
8585 extra white-space at the end. This is more correct but also will
8586 allow us to support new fields that might start with "signature".
8587 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
8589 o Minor bugfixes (onion services):
8590 - If we are configured to offer a single onion service, don't log
8591 long-term established one hop rendezvous points in the heartbeat.
8592 Fixes bug 25116; bugfix on 0.2.9.6-rc.
8594 o Minor bugfixes (performance):
8595 - Reduce the number of circuits that will be opened at once during
8596 the circuit build timeout phase. This is done by increasing the
8597 idle timeout to 3 minutes, and lowering the maximum number of
8598 concurrent learning circuits to 10. Fixes bug 24769; bugfix
8600 - Avoid calling protocol_list_supports_protocol() from inside tight
8601 loops when running with cached routerinfo_t objects. Instead,
8602 summarize the relevant protocols as flags in the routerinfo_t, as
8603 we do for routerstatus_t objects. This change simplifies our code
8604 a little, and saves a large amount of short-term memory allocation
8605 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
8607 o Minor bugfixes (performance, timeouts):
8608 - Consider circuits for timeout as soon as they complete a hop. This
8609 is more accurate than applying the timeout in
8610 circuit_expire_building() because that function is only called
8611 once per second, which is now too slow for typical timeouts on the
8612 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
8613 - Use onion service circuits (and other circuits longer than 3 hops)
8614 to calculate a circuit build timeout. Previously, Tor only
8615 calculated its build timeout based on circuits that planned to be
8616 exactly 3 hops long. With this change, we include measurements
8617 from all circuits at the point where they complete their third
8618 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
8620 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
8621 - Avoid a crash when running with DirPort set but ORPort turned off.
8622 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
8624 o Minor bugfixes (Rust FFI):
8625 - Fix a minor memory leak which would happen whenever the C code
8626 would call the Rust implementation of
8627 protover_get_supported_protocols(). This was due to the C version
8628 returning a static string, whereas the Rust version newly allocated
8629 a CString to pass across the FFI boundary. Consequently, the C
8630 code was not expecting to need to free() what it was given. Fixes
8631 bug 25127; bugfix on 0.3.2.1-alpha.
8633 o Minor bugfixes (spelling):
8634 - Use the "misspell" tool to detect and fix typos throughout the
8635 source code. Fixes bug 23650; bugfix on various versions of Tor.
8636 Patch from Deepesh Pathak.
8638 o Minor bugfixes (testing):
8639 - Avoid intermittent test failures due to a test that had relied on
8640 onion service introduction point creation finishing within 5
8641 seconds of real clock time. Fixes bug 25450; bugfix
8643 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
8644 bugfix on 0.2.3.1-alpha.
8646 o Minor bugfixes (unit test, monotonic time):
8647 - Increase a constant (1msec to 10msec) in the monotonic time test
8648 that makes sure the nsec/usec/msec times read are synchronized.
8649 This change was needed to accommodate slow systems like armel or
8650 when the clock_gettime() is not a VDSO on the running kernel.
8651 Fixes bug 25113; bugfix on 0.2.9.1.
8653 o Code simplification and refactoring:
8654 - Move the list of default directory authorities to its own file.
8655 Closes ticket 24854. Patch by "beastr0".
8656 - Remove the old (deterministic) directory retry logic entirely:
8657 We've used exponential backoff exclusively for some time. Closes
8659 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
8661 - Remove a series of counters used to track circuit extend attempts
8662 and connection status but that in reality we aren't using for
8663 anything other than stats logged by a SIGUSR1 signal. Closes
8665 - Remove /usr/athena from search path in configure.ac. Closes
8667 - Remove duplicate code in node_has_curve25519_onion_key() and
8668 node_get_curve25519_onion_key(), and add a check for a zero
8669 microdesc curve25519 onion key. Closes ticket 23966, patch by
8670 "aruna1234" and teor.
8671 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
8672 memory allocations with large numbers of OR connections (e.g.
8673 relays). Closes ticket 24119.
8674 - Separate the function that deletes ephemeral files when Tor
8676 - Small changes to Tor's buf_t API to make it suitable for use as a
8677 general-purpose safe string constructor. Closes ticket 22342.
8678 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
8679 avoid source code identifier confusion. Closes ticket 24467.
8680 - The tor_git_revision[] constant no longer needs to be redeclared
8681 by everything that links against the rest of Tor. Done as part of
8682 ticket 23845, to simplify our external API.
8683 - We make extend_info_from_node() use node_get_curve25519_onion_key()
8684 introduced in ticket 23577 to access the curve25519 public keys
8685 rather than accessing it directly. Closes ticket 23760. Patch by
8687 - Add a function to log channels' scheduler state changes to aid
8688 debugging efforts. Closes ticket 24531.
8691 - Improved the documentation of AccountingStart parameter. Closes
8693 - Update the documentation for "Log" to include the current list of
8694 logging domains. Closes ticket 25378.
8695 - Add documentation on how to build tor with Rust dependencies
8696 without having to be online. Closes ticket 22907; bugfix
8698 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
8699 traffic. Closes ticket 24318.
8700 - Document that OutboundBindAddress doesn't apply to DNS requests.
8701 Closes ticket 22145. Patch from Aruna Maurya.
8703 o Code simplification and refactoring (channels):
8704 - Remove the incoming and outgoing channel queues. These were never
8705 used, but still took up a step in our fast path.
8706 - The majority of the channel unit tests have been rewritten and the
8707 code coverage has now been raised to 83.6% for channel.c. Closes
8709 - Remove other dead code from the channel subsystem: All together,
8710 this cleanup has removed more than 1500 lines of code overall and
8711 adding very little except for unit test.
8713 o Code simplification and refactoring (circuit rendezvous):
8714 - Split the client-side rendezvous circuit lookup into two
8715 functions: one that returns only established circuits and another
8716 that returns all kinds of circuits. Closes ticket 23459.
8718 o Code simplification and refactoring (controller):
8719 - Make most of the variables in networkstatus_getinfo_by_purpose()
8720 const. Implements ticket 24489.
8722 o Documentation (backport from 0.3.4.1-alpha):
8723 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
8724 ticket 25857. Patch from "CTassisF".
8726 o Documentation (man page):
8727 - The HiddenServiceVersion torrc option accepts only one number:
8728 either version 2 or 3. Closes ticket 25026; bugfix
8731 o Documentation (manpage, denial of service):
8732 - Provide more detail about the denial-of-service options, by
8733 listing each mitigation and explaining how they relate. Closes
8737 Changes in version 0.3.1.10 - 2018-03-03
8738 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
8741 It includes an important security fix for a remote crash attack
8742 against directory authorities, tracked as TROVE-2018-001.
8744 This release also backports our new system for improved resistance to
8745 denial-of-service attacks against relays.
8747 This release also fixes several minor bugs and annoyances from
8750 All directory authorities should upgrade to one of the versions
8751 released today. Relays running 0.3.1.x may wish to update to one of
8752 the versions released today, for the DoS mitigations.
8754 Please note: according to our release calendar, Tor 0.3.1 will no
8755 longer be supported after 1 July 2018. If you will be running Tor
8756 after that date, you should make sure to plan to upgrade to the latest
8757 stable version, or downgrade to 0.2.9 (which will receive long-term
8760 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8761 - Fix a protocol-list handling bug that could be used to remotely crash
8762 directory authorities with a null-pointer exception. Fixes bug 25074;
8763 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8766 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
8767 - Give relays some defenses against the recent network overload. We
8768 start with three defenses (default parameters in parentheses).
8769 First: if a single client address makes too many concurrent
8770 connections (>100), hang up on further connections. Second: if a
8771 single client address makes circuits too quickly (more than 3 per
8772 second, with an allowed burst of 90) while also having too many
8773 connections open (3), refuse new create cells for the next while
8774 (1-2 hours). Third: if a client asks to establish a rendezvous
8775 point to you directly, ignore the request. These defenses can be
8776 manually controlled by new torrc options, but relays will also
8777 take guidance from consensus parameters, so there's no need to
8778 configure anything manually. Implements ticket 24902.
8780 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
8781 - Update the sandbox rules so that they should now work correctly
8782 with Glibc 2.26. Closes ticket 24315.
8784 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
8785 - Fix an "off by 2" error in counting rendezvous failures on the
8786 onion service side. While we thought we would stop the rendezvous
8787 attempt after one failed circuit, we were actually making three
8788 circuit attempts before giving up. Now switch to a default of 2,
8789 and allow the consensus parameter "hs_service_max_rdv_failures" to
8790 override. Fixes bug 24895; bugfix on 0.0.6.
8792 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
8793 - Add Link protocol version 5 to the supported protocols list. Fixes
8794 bug 25070; bugfix on 0.3.1.1-alpha.
8796 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
8797 - Fix a set of false positives where relays would consider
8798 connections to other relays as being client-only connections (and
8799 thus e.g. deserving different link padding schemes) if those
8800 relays fell out of the consensus briefly. Now we look only at the
8801 initial handshake and whether the connection authenticated as a
8802 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8804 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
8805 - Make our OOM handler aware of the geoip client history cache so it
8806 doesn't fill up the memory. This check is important for IPv6 and
8807 our DoS mitigation subsystem. Closes ticket 25122.
8809 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
8810 - Change relay bandwidth reporting stats interval from 4 hours to 24
8811 hours in order to reduce the efficiency of guard discovery
8812 attacks. Fixes ticket 23856.
8814 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
8815 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8816 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8817 since they neither disabled TLS 1.3 nor enabled any of the
8818 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8819 Closes ticket 24978.
8821 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
8822 - The fallback directory list has been re-generated based on the
8823 current status of the network. Tor uses fallback directories to
8824 bootstrap when it doesn't yet have up-to-date directory
8825 information. Closes ticket 24801.
8826 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8827 prefer to bootstrap from fallback directory mirrors. This is a
8828 follow-up to 24679, which removed weights from the default
8829 fallbacks. Implements ticket 24681.
8831 o Minor features (geoip):
8832 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8835 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
8836 - Use the actual observed address of an incoming relay connection,
8837 not the canonical address of the relay from its descriptor, when
8838 making decisions about how to handle the incoming connection.
8839 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8841 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
8842 - Directory authorities, when refusing a descriptor from a rejected
8843 relay, now explicitly tell the relay (in its logs) to set a valid
8844 ContactInfo address and contact the bad-relays@ mailing list.
8845 Fixes bug 25170; bugfix on 0.2.9.1.
8847 o Minor bugfixes (address selection, backport from 0.3.2.9):
8848 - When the fascist_firewall_choose_address_ functions don't find a
8849 reachable address, set the returned address to the null address
8850 and port. This is a precautionary measure, because some callers do
8851 not check the return value. Fixes bug 24736; bugfix
8854 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
8855 - Fetch descriptors aggressively whenever we lack enough to build
8856 circuits, regardless of how many descriptors we are missing.
8857 Previously, we would delay launching the fetch when we had fewer
8858 than 15 missing descriptors, even if some of those descriptors
8859 were blocking circuits from building. Fixes bug 23985; bugfix on
8860 0.1.1.11-alpha. The effects of this bug became worse in
8861 0.3.0.3-alpha, when we began treating missing descriptors from our
8862 primary guards as a reason to delay circuits.
8863 - Don't try fetching microdescriptors from relays that have failed
8864 to deliver them in the past. Fixes bug 23817; bugfix
8867 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
8868 - Fix a signed/unsigned comparison warning introduced by our fix to
8869 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8871 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
8872 - Avoid a crash when attempting to use the seccomp2 sandbox together
8873 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8876 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8877 - Fix a possible crash on malformed consensus. If a consensus had
8878 contained an unparseable protocol line, it could have made clients
8879 and relays crash with a null-pointer exception. To exploit this
8880 issue, however, an attacker would need to be able to subvert the
8881 directory authority system. Fixes bug 25251; bugfix on
8882 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8884 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
8885 - Recover better from empty or corrupt files in the consensus cache
8886 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8887 - When a consensus diff calculation is only partially successful,
8888 only record the successful parts as having succeeded. Partial
8889 success can happen if (for example) one compression method fails
8890 but the others succeed. Previously we misrecorded all the
8891 calculations as having succeeded, which would later cause a
8892 nonfatal assertion failure. Fixes bug 24086; bugfix
8895 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
8896 - Tor now updates its guard state when it reads a consensus
8897 regardless of whether it's missing descriptors. That makes tor use
8898 its primary guards to fetch descriptors in some edge cases where
8899 it would previously have used fallback directories. Fixes bug
8900 23862; bugfix on 0.3.0.1-alpha.
8902 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8903 - Don't treat inability to store a cached consensus object as a bug:
8904 it can happen normally when we are out of disk space. Fixes bug
8905 24859; bugfix on 0.3.1.1-alpha.
8907 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
8908 - When queuing DESTROY cells on a channel, only queue the circuit-id
8909 and reason fields: not the entire 514-byte cell. This fix should
8910 help mitigate any bugs or attacks that fill up these queues, and
8911 free more RAM for other uses. Fixes bug 24666; bugfix
8914 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
8915 - When closing a connection via close_connection_immediately(), we
8916 mark it as "not blocked on bandwidth", to prevent later calls from
8917 trying to unblock it, and give it permission to read. This fixes a
8918 backtrace warning that can happen on relays under various
8919 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8921 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
8922 - When selecting relays by bandwidth, avoid a rounding error that
8923 could sometimes cause load to be imbalanced incorrectly.
8924 Previously, we would always round upwards; now, we round towards
8925 the nearest integer. This had the biggest effect when a relay's
8926 weight adjustments should have given it weight 0, but it got
8927 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8928 - When calculating the fraction of nodes that have descriptors, and
8929 all nodes in the network have zero bandwidths, count the number of
8930 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8931 - Actually log the total bandwidth in compute_weighted_bandwidths().
8932 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8934 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8935 - Improve the performance of our consensus-diff application code
8936 when Tor is built with the --enable-fragile-hardening option set.
8937 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8939 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8940 - Don't exit the Tor process if setrlimit() fails to change the file
8941 limit (which can happen sometimes on some versions of OSX). Fixes
8942 bug 21074; bugfix on 0.0.9pre5.
8944 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
8945 - Fix a bug in the bit-counting parts of our timing-wheel code on
8946 MSVC. (Note that MSVC is still not a supported build platform, due
8947 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
8950 o Minor bugfixes (relay, partial backport):
8951 - Make the internal channel_is_client() function look at what sort
8952 of connection handshake the other side used, rather than whether
8953 the other side ever sent a create_fast cell to us. Backports part
8954 of the fixes from bugs 22805 and 24898.
8956 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8957 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8959 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8960 bugfix on 0.2.9.4-alpha.
8962 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8963 - Update the "rust dependencies" submodule to be a project-level
8964 repository, rather than a user repository. Closes ticket 25323.
8967 Changes in version 0.2.9.15 - 2018-03-03
8968 Tor 0.2.9.15 backports important security and stability bugfixes from
8971 It includes an important security fix for a remote crash attack
8972 against directory authorities, tracked as TROVE-2018-001.
8974 This release also backports our new system for improved resistance to
8975 denial-of-service attacks against relays.
8977 This release also fixes several minor bugs and annoyances from
8980 All directory authorities should upgrade to one of the versions
8981 released today. Relays running 0.2.9.x may wish to update to one of
8982 the versions released today, for the DoS mitigations.
8984 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8985 - Fix a protocol-list handling bug that could be used to remotely crash
8986 directory authorities with a null-pointer exception. Fixes bug 25074;
8987 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8990 o Major features (denial-of-service mitigation):
8991 - Give relays some defenses against the recent network overload. We
8992 start with three defenses (default parameters in parentheses).
8993 First: if a single client address makes too many concurrent
8994 connections (>100), hang up on further connections. Second: if a
8995 single client address makes circuits too quickly (more than 3 per
8996 second, with an allowed burst of 90) while also having too many
8997 connections open (3), refuse new create cells for the next while
8998 (1-2 hours). Third: if a client asks to establish a rendezvous
8999 point to you directly, ignore the request. These defenses can be
9000 manually controlled by new torrc options, but relays will also
9001 take guidance from consensus parameters, so there's no need to
9002 configure anything manually. Implements ticket 24902.
9004 o Major bugfixes (bootstrapping):
9005 - Fetch descriptors aggressively whenever we lack enough to build
9006 circuits, regardless of how many descriptors we are missing.
9007 Previously, we would delay launching the fetch when we had fewer
9008 than 15 missing descriptors, even if some of those descriptors
9009 were blocking circuits from building. Fixes bug 23985; bugfix on
9010 0.1.1.11-alpha. The effects of this bug became worse in
9011 0.3.0.3-alpha, when we began treating missing descriptors from our
9012 primary guards as a reason to delay circuits.
9014 o Major bugfixes (onion services, retry behavior):
9015 - Fix an "off by 2" error in counting rendezvous failures on the
9016 onion service side. While we thought we would stop the rendezvous
9017 attempt after one failed circuit, we were actually making three
9018 circuit attempts before giving up. Now switch to a default of 2,
9019 and allow the consensus parameter "hs_service_max_rdv_failures" to
9020 override. Fixes bug 24895; bugfix on 0.0.6.
9022 o Minor feature (relay statistics):
9023 - Change relay bandwidth reporting stats interval from 4 hours to 24
9024 hours in order to reduce the efficiency of guard discovery
9025 attacks. Fixes ticket 23856.
9027 o Minor features (compatibility, OpenSSL):
9028 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9029 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9030 since they neither disabled TLS 1.3 nor enabled any of the
9031 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9032 Closes ticket 24978.
9034 o Minor features (denial-of-service avoidance):
9035 - Make our OOM handler aware of the geoip client history cache so it
9036 doesn't fill up the memory. This check is important for IPv6 and
9037 our DoS mitigation subsystem. Closes ticket 25122.
9039 o Minor features (fallback directory mirrors):
9040 - The fallback directory list has been re-generated based on the
9041 current status of the network. Tor uses fallback directories to
9042 bootstrap when it doesn't yet have up-to-date directory
9043 information. Closes ticket 24801.
9044 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9045 prefer to bootstrap from fallback directory mirrors. This is a
9046 follow-up to 24679, which removed weights from the default
9047 fallbacks. Implements ticket 24681.
9049 o Minor features (geoip):
9050 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9053 o Minor features (linux seccomp2 sandbox):
9054 - Update the sandbox rules so that they should now work correctly
9055 with Glibc 2.26. Closes ticket 24315.
9057 o Minor bugfix (channel connection):
9058 - Use the actual observed address of an incoming relay connection,
9059 not the canonical address of the relay from its descriptor, when
9060 making decisions about how to handle the incoming connection.
9061 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9063 o Minor bugfix (directory authority):
9064 - Directory authorities, when refusing a descriptor from a rejected
9065 relay, now explicitly tell the relay (in its logs) to set a valid
9066 ContactInfo address and contact the bad-relays@ mailing list.
9067 Fixes bug 25170; bugfix on 0.2.9.1.
9069 o Minor bugfixes (address selection):
9070 - When the fascist_firewall_choose_address_ functions don't find a
9071 reachable address, set the returned address to the null address
9072 and port. This is a precautionary measure, because some callers do
9073 not check the return value. Fixes bug 24736; bugfix
9076 o Minor bugfixes (compilation):
9077 - Fix a signed/unsigned comparison warning introduced by our fix to
9078 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9080 o Minor bugfixes (control port, linux seccomp2 sandbox):
9081 - Avoid a crash when attempting to use the seccomp2 sandbox together
9082 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9085 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9086 - Fix a possible crash on malformed consensus. If a consensus had
9087 contained an unparseable protocol line, it could have made clients
9088 and relays crash with a null-pointer exception. To exploit this
9089 issue, however, an attacker would need to be able to subvert the
9090 directory authority system. Fixes bug 25251; bugfix on
9091 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9093 o Minor bugfixes (memory usage):
9094 - When queuing DESTROY cells on a channel, only queue the circuit-id
9095 and reason fields: not the entire 514-byte cell. This fix should
9096 help mitigate any bugs or attacks that fill up these queues, and
9097 free more RAM for other uses. Fixes bug 24666; bugfix
9100 o Minor bugfixes (network layer):
9101 - When closing a connection via close_connection_immediately(), we
9102 mark it as "not blocked on bandwidth", to prevent later calls from
9103 trying to unblock it, and give it permission to read. This fixes a
9104 backtrace warning that can happen on relays under various
9105 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9107 o Minor bugfixes (OSX):
9108 - Don't exit the Tor process if setrlimit() fails to change the file
9109 limit (which can happen sometimes on some versions of OSX). Fixes
9110 bug 21074; bugfix on 0.0.9pre5.
9112 o Minor bugfixes (path selection):
9113 - When selecting relays by bandwidth, avoid a rounding error that
9114 could sometimes cause load to be imbalanced incorrectly.
9115 Previously, we would always round upwards; now, we round towards
9116 the nearest integer. This had the biggest effect when a relay's
9117 weight adjustments should have given it weight 0, but it got
9118 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9119 - When calculating the fraction of nodes that have descriptors, and
9120 all nodes in the network have zero bandwidths, count the number of
9121 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9122 - Actually log the total bandwidth in compute_weighted_bandwidths().
9123 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9125 o Minor bugfixes (portability, msvc):
9126 - Fix a bug in the bit-counting parts of our timing-wheel code on
9127 MSVC. (Note that MSVC is still not a supported build platform, due
9128 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9131 o Minor bugfixes (relay):
9132 - Make the internal channel_is_client() function look at what sort
9133 of connection handshake the other side used, rather than whether
9134 the other side ever sent a create_fast cell to us. Backports part
9135 of the fixes from bugs 22805 and 24898.
9137 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9138 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9140 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9141 bugfix on 0.2.9.4-alpha.
9144 Changes in version 0.3.2.10 - 2018-03-03
9145 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
9146 backports a number of bugfixes, including important fixes for security
9149 It includes an important security fix for a remote crash attack
9150 against directory authorities, tracked as TROVE-2018-001.
9152 Additionally, it backports a fix for a bug whose severity we have
9153 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
9154 triggered in order to crash relays with a use-after-free pattern. As
9155 such, we are now tracking that bug as TROVE-2018-002 and
9156 CVE-2018-0491, and backporting it to earlier releases. This bug
9157 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
9160 This release also backports our new system for improved resistance to
9161 denial-of-service attacks against relays.
9163 This release also fixes several minor bugs and annoyances from
9166 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
9167 today, for the fix to TROVE-2018-002. Directory authorities should
9168 also upgrade. (Relays on earlier versions might want to update too for
9169 the DoS mitigations.)
9171 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9172 - Fix a protocol-list handling bug that could be used to remotely crash
9173 directory authorities with a null-pointer exception. Fixes bug 25074;
9174 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9177 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
9178 - Avoid adding the same channel twice in the KIST scheduler pending
9179 list, which could lead to remote denial-of-service use-after-free
9180 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
9182 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
9183 - Give relays some defenses against the recent network overload. We
9184 start with three defenses (default parameters in parentheses).
9185 First: if a single client address makes too many concurrent
9186 connections (>100), hang up on further connections. Second: if a
9187 single client address makes circuits too quickly (more than 3 per
9188 second, with an allowed burst of 90) while also having too many
9189 connections open (3), refuse new create cells for the next while
9190 (1-2 hours). Third: if a client asks to establish a rendezvous
9191 point to you directly, ignore the request. These defenses can be
9192 manually controlled by new torrc options, but relays will also
9193 take guidance from consensus parameters, so there's no need to
9194 configure anything manually. Implements ticket 24902.
9196 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
9197 - Fix an "off by 2" error in counting rendezvous failures on the
9198 onion service side. While we thought we would stop the rendezvous
9199 attempt after one failed circuit, we were actually making three
9200 circuit attempts before giving up. Now switch to a default of 2,
9201 and allow the consensus parameter "hs_service_max_rdv_failures" to
9202 override. Fixes bug 24895; bugfix on 0.0.6.
9203 - New-style (v3) onion services now obey the "max rendezvous circuit
9204 attempts" logic. Previously they would make as many rendezvous
9205 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
9206 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
9208 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
9209 - Add Link protocol version 5 to the supported protocols list. Fixes
9210 bug 25070; bugfix on 0.3.1.1-alpha.
9212 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
9213 - Fix a set of false positives where relays would consider
9214 connections to other relays as being client-only connections (and
9215 thus e.g. deserving different link padding schemes) if those
9216 relays fell out of the consensus briefly. Now we look only at the
9217 initial handshake and whether the connection authenticated as a
9218 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
9220 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
9221 - The scheduler subsystem was failing to promptly notice changes in
9222 consensus parameters, making it harder to switch schedulers
9223 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
9225 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
9226 - Make our OOM handler aware of the geoip client history cache so it
9227 doesn't fill up the memory. This check is important for IPv6 and
9228 our DoS mitigation subsystem. Closes ticket 25122.
9230 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
9231 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9232 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9233 since they neither disabled TLS 1.3 nor enabled any of the
9234 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9235 Closes ticket 24978.
9237 o Minor features (geoip):
9238 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9241 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
9242 - When logging a failure to create an onion service's descriptor,
9243 also log what the problem with the descriptor was. Diagnostic
9246 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
9247 - Use the actual observed address of an incoming relay connection,
9248 not the canonical address of the relay from its descriptor, when
9249 making decisions about how to handle the incoming connection.
9250 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9252 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9253 - Fix a possible crash on malformed consensus. If a consensus had
9254 contained an unparseable protocol line, it could have made clients
9255 and relays crash with a null-pointer exception. To exploit this
9256 issue, however, an attacker would need to be able to subvert the
9257 directory authority system. Fixes bug 25251; bugfix on
9258 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9260 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
9261 - Directory authorities, when refusing a descriptor from a rejected
9262 relay, now explicitly tell the relay (in its logs) to set a valid
9263 ContactInfo address and contact the bad-relays@ mailing list.
9264 Fixes bug 25170; bugfix on 0.2.9.1.
9266 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
9267 - When building with Rust on OSX, link against libresolv, to work
9268 around the issue at https://github.com/rust-lang/rust/issues/46797.
9269 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
9271 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
9272 - Remove a BUG() statement when a client fetches an onion descriptor
9273 that has a lower revision counter than the one in its cache. This
9274 can happen in normal circumstances due to HSDir desync. Fixes bug
9275 24976; bugfix on 0.3.2.1-alpha.
9277 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
9278 - Don't treat inability to store a cached consensus object as a bug:
9279 it can happen normally when we are out of disk space. Fixes bug
9280 24859; bugfix on 0.3.1.1-alpha.
9282 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
9283 - Improve the performance of our consensus-diff application code
9284 when Tor is built with the --enable-fragile-hardening option set.
9285 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
9287 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
9288 - Don't exit the Tor process if setrlimit() fails to change the file
9289 limit (which can happen sometimes on some versions of OSX). Fixes
9290 bug 21074; bugfix on 0.0.9pre5.
9292 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9293 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9295 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9296 bugfix on 0.2.9.4-alpha.
9298 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
9299 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
9300 25005; bugfix on 0.3.2.7-rc.
9302 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
9303 - Look at the "HSRend" protocol version, not the "HSDir" protocol
9304 version, when deciding whether a consensus entry can support the
9305 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
9306 bugfix on 0.3.2.1-alpha.
9308 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
9309 - Update the "rust dependencies" submodule to be a project-level
9310 repository, rather than a user repository. Closes ticket 25323.
9312 o Documentation (backport from 0.3.3.1-alpha)
9313 - Document that operators who run more than one relay or bridge are
9314 expected to set MyFamily and ContactInfo correctly. Closes
9318 Changes in version 0.3.2.9 - 2018-01-09
9319 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
9321 The 0.3.2 series includes our long-anticipated new onion service
9322 design, with numerous security features. (For more information, see
9323 our blog post at https://blog.torproject.org/fall-harvest.) We also
9324 have a new circuit scheduler algorithm for improved performance on
9325 relays everywhere (see https://blog.torproject.org/kist-and-tell),
9326 along with many smaller features and bugfixes.
9328 Per our stable release policy, we plan to support each stable release
9329 series for at least the next nine months, or for three months after
9330 the first stable release of the next series: whichever is longer. If
9331 you need a release with long-term support, we recommend that you stay
9332 with the 0.2.9 series.
9334 Below is a list of the changes since 0.3.1.7. For a list of all
9335 changes since 0.3.2.8-rc, see the ChangeLog file.
9337 o Directory authority changes:
9338 - Add "Bastet" as a ninth directory authority to the default list.
9339 Closes ticket 23910.
9340 - The directory authority "Longclaw" has changed its IP address.
9341 Closes ticket 23592.
9342 - Remove longclaw's IPv6 address, as it will soon change. Authority
9343 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9344 3/8 directory authorities with IPv6 addresses, but there are also
9345 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9346 - Add an IPv6 address for the "bastet" directory authority. Closes
9349 o Major features (next-generation onion services):
9350 - Tor now supports the next-generation onion services protocol for
9351 clients and services! As part of this release, the core of
9352 proposal 224 has been implemented and is available for
9353 experimentation and testing by our users. This newer version of
9354 onion services ("v3") features many improvements over the legacy
9357 a) Better crypto (replaced SHA1/DH/RSA1024
9358 with SHA3/ed25519/curve25519)
9360 b) Improved directory protocol, leaking much less information to
9363 c) Improved directory protocol, with smaller surface for
9366 d) Better onion address security against impersonation.
9368 e) More extensible introduction/rendezvous protocol.
9370 f) A cleaner and more modular codebase.
9372 You can identify a next-generation onion address by its length:
9373 they are 56 characters long, as in
9374 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
9376 In the future, we will release more options and features for v3
9377 onion services, but we first need a testing period, so that the
9378 current codebase matures and becomes more robust. Planned features
9379 include: offline keys, advanced client authorization, improved
9380 guard algorithms, and statistics. For full details, see
9383 Legacy ("v2") onion services will still work for the foreseeable
9384 future, and will remain the default until this new codebase gets
9385 tested and hardened. Service operators who want to experiment with
9386 the new system can use the 'HiddenServiceVersion 3' torrc
9387 directive along with the regular onion service configuration
9388 options. For more information, see our blog post at
9389 "https://blog.torproject.org/fall-harvest". Enjoy!
9391 o Major feature (scheduler, channel):
9392 - Tor now uses new schedulers to decide which circuits should
9393 deliver cells first, in order to improve congestion at relays. The
9394 first type is called "KIST" ("Kernel Informed Socket Transport"),
9395 and is only available on Linux-like systems: it uses feedback from
9396 the kernel to prevent the kernel's TCP buffers from growing too
9397 full. The second new scheduler type is called "KISTLite": it
9398 behaves the same as KIST, but runs on systems without kernel
9399 support for inspecting TCP implementation details. The old
9400 scheduler is still available, under the name "Vanilla". To change
9401 the default scheduler preference order, use the new "Schedulers"
9402 option. (The default preference order is "KIST,KISTLite,Vanilla".)
9404 Matt Traudt implemented KIST, based on research by Rob Jansen,
9405 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
9406 more information, see the design paper at
9407 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
9408 followup implementation paper at https://arxiv.org/abs/1709.01044.
9409 Closes ticket 12541. For more information, see our blog post at
9410 "https://blog.torproject.org/kist-and-tell".
9412 o Major bugfixes (security, general):
9413 - Fix a denial of service bug where an attacker could use a
9414 malformed directory object to cause a Tor instance to pause while
9415 OpenSSL would try to read a passphrase from the terminal. (Tor
9416 instances run without a terminal, which is the case for most Tor
9417 packages, are not impacted.) Fixes bug 24246; bugfix on every
9418 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9419 Found by OSS-Fuzz as testcase 6360145429790720.
9421 o Major bugfixes (security, directory authority):
9422 - Fix a denial of service issue where an attacker could crash a
9423 directory authority using a malformed router descriptor. Fixes bug
9424 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9427 o Major bugfixes (security, onion service v2):
9428 - Fix a use-after-free error that could crash v2 Tor onion services
9429 when they failed to open circuits while expiring introduction
9430 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9431 also tracked as TROVE-2017-013 and CVE-2017-8823.
9432 - When checking for replays in the INTRODUCE1 cell data for a
9433 (legacy) onion service, correctly detect replays in the RSA-
9434 encrypted part of the cell. We were previously checking for
9435 replays on the entire cell, but those can be circumvented due to
9436 the malleability of Tor's legacy hybrid encryption. This fix helps
9437 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9438 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9441 o Major bugfixes (security, relay):
9442 - When running as a relay, make sure that we never build a path
9443 through ourselves, even in the case where we have somehow lost the
9444 version of our descriptor appearing in the consensus. Fixes part
9445 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9446 as TROVE-2017-012 and CVE-2017-8822.
9447 - When running as a relay, make sure that we never choose ourselves
9448 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9449 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9451 o Major bugfixes (bootstrapping):
9452 - Fetch descriptors aggressively whenever we lack enough to build
9453 circuits, regardless of how many descriptors we are missing.
9454 Previously, we would delay launching the fetch when we had fewer
9455 than 15 missing descriptors, even if some of those descriptors
9456 were blocking circuits from building. Fixes bug 23985; bugfix on
9457 0.1.1.11-alpha. The effects of this bug became worse in
9458 0.3.0.3-alpha, when we began treating missing descriptors from our
9459 primary guards as a reason to delay circuits.
9460 - Don't try fetching microdescriptors from relays that have failed
9461 to deliver them in the past. Fixes bug 23817; bugfix
9464 o Major bugfixes (circuit prediction):
9465 - Fix circuit prediction logic so that a client doesn't treat a port
9466 as being "handled" by a circuit if that circuit already has
9467 isolation settings on it. This change should make Tor clients more
9468 responsive by improving their chances of having a pre-created
9469 circuit ready for use when a request arrives. Fixes bug 18859;
9470 bugfix on 0.2.3.3-alpha.
9472 o Major bugfixes (exit relays, DNS):
9473 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9474 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9475 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9476 identifying and finding a workaround to this bug and to Moritz,
9477 Arthur Edelstein, and Roger for helping to track it down and
9480 o Major bugfixes (relay, crash, assertion failure):
9481 - Fix a timing-based assertion failure that could occur when the
9482 circuit out-of-memory handler freed a connection's output buffer.
9483 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9485 o Major bugfixes (usability, control port):
9486 - Report trusted clock skew indications as bootstrap errors, so
9487 controllers can more easily alert users when their clocks are
9488 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
9490 o Minor features (bridge):
9491 - Bridge relays can now set the BridgeDistribution config option to
9492 add a "bridge-distribution-request" line to their bridge
9493 descriptor, which tells BridgeDB how they'd like their bridge
9494 address to be given out. (Note that as of Oct 2017, BridgeDB does
9495 not yet implement this feature.) As a side benefit, this feature
9496 provides a way to distinguish bridge descriptors from non-bridge
9497 descriptors. Implements tickets 18329.
9498 - When handling the USERADDR command on an ExtOrPort, warn when the
9499 transports provides a USERADDR with no port. In a future version,
9500 USERADDR commands of this format may be rejected. Detects problems
9501 related to ticket 23080.
9503 o Minor features (bug detection):
9504 - Log a warning message with a stack trace for any attempt to call
9505 get_options() during option validation. This pattern has caused
9506 subtle bugs in the past. Closes ticket 22281.
9508 o Minor features (build, compilation):
9509 - The "check-changes" feature is now part of the "make check" tests;
9510 we'll use it to try to prevent misformed changes files from
9511 accumulating. Closes ticket 23564.
9512 - Tor builds should now fail if there are any mismatches between the
9513 C type representing a configuration variable and the C type the
9514 data-driven parser uses to store a value there. Previously, we
9515 needed to check these by hand, which sometimes led to mistakes.
9516 Closes ticket 23643.
9518 o Minor features (client):
9519 - You can now use Tor as a tunneled HTTP proxy: use the new
9520 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
9521 requests. Closes ticket 22407.
9522 - Add an extra check to make sure that we always use the newer guard
9523 selection code for picking our guards. Closes ticket 22779.
9524 - When downloading (micro)descriptors, don't split the list into
9525 multiple requests unless we want at least 32 descriptors.
9526 Previously, we split at 4, not 32, which led to significant
9527 overhead in HTTP request size and degradation in compression
9528 performance. Closes ticket 23220.
9529 - Improve log messages when missing descriptors for primary guards.
9530 Resolves ticket 23670.
9532 o Minor features (command line):
9533 - Add a new commandline option, --key-expiration, which prints when
9534 the current signing key is going to expire. Implements ticket
9535 17639; patch by Isis Lovecruft.
9537 o Minor features (control port):
9538 - If an application tries to use the control port as an HTTP proxy,
9539 respond with a meaningful "This is the Tor control port" message,
9540 and log the event. Closes ticket 1667. Patch from Ravi
9542 - Provide better error message for GETINFO desc/(id|name) when not
9543 fetching router descriptors. Closes ticket 5847. Patch by
9545 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
9546 whether Tor will try to download router descriptors and
9547 microdescriptors respectively. Closes ticket 22684.
9548 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
9549 so controllers can tell whether the geoip databases are loaded.
9550 Closes ticket 23237.
9551 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
9552 events. Closes ticket 19254. Patch by "DonnchaC".
9554 o Minor features (development support):
9555 - Developers can now generate a call-graph for Tor using the
9556 "calltool" python program, which post-processes object dumps. It
9557 should work okay on many Linux and OSX platforms, and might work
9558 elsewhere too. To run it, install calltool from
9559 https://gitweb.torproject.org/user/nickm/calltool.git and run
9560 "make callgraph". Closes ticket 19307.
9562 o Minor features (directory authority):
9563 - Make the "Exit" flag assignment only depend on whether the exit
9564 policy allows connections to ports 80 and 443. Previously relays
9565 would get the Exit flag if they allowed connections to one of
9566 these ports and also port 6667. Resolves ticket 23637.
9568 o Minor features (ed25519):
9569 - Add validation function to checks for torsion components in
9570 ed25519 public keys, used by prop224 client-side code. Closes
9571 ticket 22006. Math help by Ian Goldberg.
9573 o Minor features (exit relay, DNS):
9574 - Improve the clarity and safety of the log message from evdns when
9575 receiving an apparently spoofed DNS reply. Closes ticket 3056.
9577 o Minor features (fallback directory mirrors):
9578 - The fallback directory list has been re-generated based on the
9579 current status of the network. Tor uses fallback directories to
9580 bootstrap when it doesn't yet have up-to-date directory
9581 information. Closes ticket 24801.
9582 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9583 prefer to bootstrap from fallback directory mirrors. This is a
9584 follow-up to 24679, which removed weights from the default
9585 fallbacks. Implements ticket 24681.
9587 o Minor features (geoip):
9588 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
9591 o Minor features (integration, hardening):
9592 - Add a new NoExec option to prevent Tor from running other
9593 programs. When this option is set to 1, Tor will never try to run
9594 another program, regardless of the settings of
9595 PortForwardingHelper, ClientTransportPlugin, or
9596 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
9597 without restarting Tor. Closes ticket 22976.
9599 o Minor features (linux seccomp2 sandbox):
9600 - Update the sandbox rules so that they should now work correctly
9601 with Glibc 2.26. Closes ticket 24315.
9603 o Minor features (logging):
9604 - Provide better warnings when the getrandom() syscall fails. Closes
9606 - Downgrade a pair of log messages that could occur when an exit's
9607 resolver gave us an unusual (but not forbidden) response. Closes
9609 - Improve the message we log when re-enabling circuit build timeouts
9610 after having received a consensus. Closes ticket 20963.
9611 - Log more circuit information whenever we are about to try to
9612 package a relay cell on a circuit with a nonexistent n_chan.
9613 Attempt to diagnose ticket 8185.
9614 - Improve info-level log identification of particular circuits, to
9615 help with debugging. Closes ticket 23645.
9616 - Improve the warning message for specifying a relay by nickname.
9617 The previous message implied that nickname registration was still
9618 part of the Tor network design, which it isn't. Closes
9620 - If the sandbox filter fails to load, suggest to the user that
9621 their kernel might not support seccomp2. Closes ticket 23090.
9623 o Minor features (onion service, circuit, logging):
9624 - Improve logging of many callsite in the circuit subsystem to print
9625 the circuit identifier(s).
9626 - Log when we cleanup an intro point from a service so we know when
9627 and for what reason it happened. Closes ticket 23604.
9629 o Minor features (portability):
9630 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
9631 (It doesn't yet work with the sandbox enabled.) Closes
9633 - Check at configure time whether uint8_t is the same type as
9634 unsigned char. Lots of existing code already makes this
9635 assumption, and there could be strict aliasing issues if the
9636 assumption is violated. Closes ticket 22410.
9638 o Minor features (relay):
9639 - When choosing which circuits can be expired as unused, consider
9640 circuits from clients even if those clients used regular CREATE
9641 cells to make them; and do not consider circuits from relays even
9642 if they were made with CREATE_FAST. Part of ticket 22805.
9643 - Reject attempts to use relative file paths when RunAsDaemon is
9644 set. Previously, Tor would accept these, but the directory-
9645 changing step of RunAsDaemon would give strange and/or confusing
9646 results. Closes ticket 22731.
9648 o Minor features (relay statistics):
9649 - Change relay bandwidth reporting stats interval from 4 hours to 24
9650 hours in order to reduce the efficiency of guard discovery
9651 attacks. Fixes ticket 23856.
9653 o Minor features (reverted deprecations):
9654 - The ClientDNSRejectInternalAddresses flag can once again be set in
9655 non-testing Tor networks, so long as they do not use the default
9656 directory authorities. This change also removes the deprecation of
9657 this flag from 0.2.9.2-alpha. Closes ticket 21031.
9659 o Minor features (robustness):
9660 - Change several fatal assertions when flushing buffers into non-
9661 fatal assertions, to prevent any recurrence of 23690.
9663 o Minor features (startup, safety):
9664 - When configured to write a PID file, Tor now exits if it is unable
9665 to do so. Previously, it would warn and continue. Closes
9668 o Minor features (static analysis):
9669 - The BUG() macro has been changed slightly so that Coverity no
9670 longer complains about dead code if the bug is impossible. Closes
9673 o Minor features (testing):
9674 - Our fuzzing tests now test the encrypted portions of v3 onion
9675 service descriptors. Implements more of 21509.
9676 - Add a unit test to make sure that our own generated platform
9677 string will be accepted by directory authorities. Closes
9679 - The default chutney network tests now include tests for the v3
9680 onion service design. Make sure you have the latest version of
9681 chutney if you want to run these. Closes ticket 22437.
9682 - Add a unit test to verify that we can parse a hardcoded v2 onion
9683 service descriptor. Closes ticket 15554.
9685 o Minor bugfixes (address selection):
9686 - When the fascist_firewall_choose_address_ functions don't find a
9687 reachable address, set the returned address to the null address
9688 and port. This is a precautionary measure, because some callers do
9689 not check the return value. Fixes bug 24736; bugfix
9692 o Minor bugfixes (bootstrapping):
9693 - When warning about state file clock skew, report the correct
9694 direction for the detected skew. Fixes bug 23606; bugfix
9697 o Minor bugfixes (bridge clients, bootstrap):
9698 - Retry directory downloads when we get our first bridge descriptor
9699 during bootstrap or while reconnecting to the network. Keep
9700 retrying every time we get a bridge descriptor, until we have a
9701 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
9702 - Stop delaying bridge descriptor fetches when we have cached bridge
9703 descriptors. Instead, only delay bridge descriptor fetches when we
9704 have at least one reachable bridge. Fixes part of bug 24367;
9705 bugfix on 0.2.0.3-alpha.
9706 - Stop delaying directory fetches when we have cached bridge
9707 descriptors. Instead, only delay bridge descriptor fetches when
9708 all our bridges are definitely unreachable. Fixes part of bug
9709 24367; bugfix on 0.2.0.3-alpha.
9711 o Minor bugfixes (bridge):
9712 - Overwrite the bridge address earlier in the process of retrieving
9713 its descriptor, to make sure we reach it on the configured
9714 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
9716 o Minor bugfixes (build, compilation):
9717 - Fix a compilation warning when building with zstd support on
9718 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9719 and fixed by Andreas Stieger.
9720 - When searching for OpenSSL, don't accept any OpenSSL library that
9721 lacks TLSv1_1_method(): Tor doesn't build with those versions.
9722 Additionally, look in /usr/local/opt/openssl, if it's present.
9723 These changes together repair the default build on OSX systems
9724 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
9725 - Fix a signed/unsigned comparison warning introduced by our fix to
9726 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9727 - Fix a memory leak warning in one of the libevent-related
9728 configuration tests that could occur when manually specifying
9729 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
9730 Found and patched by Alex Xu.
9731 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
9732 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9734 o Minor bugfixes (certificate handling):
9735 - Fix a time handling bug in Tor certificates set to expire after
9736 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
9737 Coverity as CID 1415728.
9739 o Minor bugfixes (client):
9740 - By default, do not enable storage of client-side DNS values. These
9741 values were unused by default previously, but they should not have
9742 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
9744 o Minor bugfixes (client, usability):
9745 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
9746 SOCKS4a requests that contain IP address strings, even when
9747 SafeSocks in enabled, as this prevents user from connecting to
9748 known IP addresses without relying on DNS for resolving. SafeSocks
9749 still rejects SOCKS connections that connect to IP addresses when
9750 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
9751 bugfix on Tor 0.2.6.2-alpha.
9753 o Minor bugfixes (code correctness):
9754 - Call htons() in extend_cell_format() for encoding a 16-bit value.
9755 Previously we used ntohs(), which happens to behave the same on
9756 all the platforms we support, but which isn't really correct.
9757 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
9758 - For defense-in-depth, make the controller's write_escaped_data()
9759 function robust to extremely long inputs. Fixes bug 19281; bugfix
9760 on 0.1.1.1-alpha. Reported by Guido Vranken.
9761 - Fix several places in our codebase where a C compiler would be
9762 likely to eliminate a check, based on assuming that undefined
9763 behavior had not happened elsewhere in the code. These cases are
9764 usually a sign of redundant checking or dubious arithmetic. Found
9765 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
9766 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
9769 o Minor bugfixes (compression):
9770 - Handle a pathological case when decompressing Zstandard data when
9771 the output buffer size is zero. Fixes bug 23551; bugfix
9774 o Minor bugfixes (consensus expiry):
9775 - Check for adequate directory information correctly. Previously, Tor
9776 would reconsider whether it had sufficient directory information
9777 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
9779 o Minor bugfixes (control port, linux seccomp2 sandbox):
9780 - Avoid a crash when attempting to use the seccomp2 sandbox together
9781 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9784 o Minor bugfixes (control port, onion services):
9785 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
9786 HS_DESC event when a service is not able to upload a descriptor.
9787 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
9789 o Minor bugfixes (directory cache):
9790 - Recover better from empty or corrupt files in the consensus cache
9791 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
9792 - When a consensus diff calculation is only partially successful,
9793 only record the successful parts as having succeeded. Partial
9794 success can happen if (for example) one compression method fails
9795 but the others succeed. Previously we misrecorded all the
9796 calculations as having succeeded, which would later cause a
9797 nonfatal assertion failure. Fixes bug 24086; bugfix
9800 o Minor bugfixes (directory client):
9801 - On failure to download directory information, delay retry attempts
9802 by a random amount based on the "decorrelated jitter" algorithm.
9803 Our previous delay algorithm tended to produce extra-long delays
9804 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
9806 o Minor bugfixes (directory protocol):
9807 - Directory servers now include a "Date:" http header for response
9808 codes other than 200. Clients starting with a skewed clock and a
9809 recent consensus were getting "304 Not modified" responses from
9810 directory authorities, so without the Date header, the client
9811 would never hear about a wrong clock. Fixes bug 23499; bugfix
9813 - Make clients wait for 6 seconds before trying to download a
9814 consensus from an authority. Fixes bug 17750; bugfix
9817 o Minor bugfixes (documentation):
9818 - Document better how to read gcov, and what our gcov postprocessing
9819 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
9820 - Fix manpage to not refer to the obsolete (and misspelled)
9821 UseEntryGuardsAsDirectoryGuards parameter in the description of
9822 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
9824 o Minor bugfixes (DoS-resistance):
9825 - If future code asks if there are any running bridges, without
9826 checking if bridges are enabled, log a BUG warning rather than
9827 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
9829 o Minor bugfixes (entry guards):
9830 - Tor now updates its guard state when it reads a consensus
9831 regardless of whether it's missing descriptors. That makes tor use
9832 its primary guards to fetch descriptors in some edge cases where
9833 it would previously have used fallback directories. Fixes bug
9834 23862; bugfix on 0.3.0.1-alpha.
9836 o Minor bugfixes (format strictness):
9837 - Restrict several data formats to decimal. Previously, the
9838 BuildTimeHistogram entries in the state file, the "bw=" entries in
9839 the bandwidth authority file, and the process IDs passed to the
9840 __OwningControllerProcess option could all be specified in hex or
9841 octal as well as in decimal. This was not an intentional feature.
9842 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
9845 o Minor bugfixes (heartbeat):
9846 - If we fail to write a heartbeat message, schedule a retry for the
9847 minimum heartbeat interval number of seconds in the future. Fixes
9848 bug 19476; bugfix on 0.2.3.1-alpha.
9850 o Minor bugfixes (logging):
9851 - Suppress a log notice when relay descriptors arrive. We already
9852 have a bootstrap progress for this so no need to log notice
9853 everytime tor receives relay descriptors. Microdescriptors behave
9854 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
9855 - Remove duplicate log messages regarding opening non-local
9856 SocksPorts upon parsing config and opening listeners at startup.
9857 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
9858 - Use a more comprehensible log message when telling the user
9859 they've excluded every running exit node. Fixes bug 7890; bugfix
9861 - When logging the number of descriptors we intend to download per
9862 directory request, do not log a number higher than then the number
9863 of descriptors we're fetching in total. Fixes bug 19648; bugfix
9865 - When warning about a directory owned by the wrong user, log the
9866 actual name of the user owning the directory. Previously, we'd log
9867 the name of the process owner twice. Fixes bug 23487; bugfix
9869 - Fix some messages on unexpected errors from the seccomp2 library.
9870 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
9871 - The tor specification says hop counts are 1-based, so fix two log
9872 messages that mistakenly logged 0-based hop counts. Fixes bug
9873 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
9874 Credit to Xiaofan Li for reporting this issue.
9876 o Minor bugfixes (logging, relay shutdown, annoyance):
9877 - When a circuit is marked for close, do not attempt to package any
9878 cells for channels on that circuit. Previously, we would detect
9879 this condition lower in the call stack, when we noticed that the
9880 circuit had no attached channel, and log an annoying message.
9881 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9883 o Minor bugfixes (memory safety, defensive programming):
9884 - Clear the target address when node_get_prim_orport() returns
9885 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9887 o Minor bugfixes (memory usage):
9888 - When queuing DESTROY cells on a channel, only queue the circuit-id
9889 and reason fields: not the entire 514-byte cell. This fix should
9890 help mitigate any bugs or attacks that fill up these queues, and
9891 free more RAM for other uses. Fixes bug 24666; bugfix
9894 o Minor bugfixes (network layer):
9895 - When closing a connection via close_connection_immediately(), we
9896 mark it as "not blocked on bandwidth", to prevent later calls from
9897 trying to unblock it, and give it permission to read. This fixes a
9898 backtrace warning that can happen on relays under various
9899 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9901 o Minor bugfixes (onion services):
9902 - The introduction circuit was being timed out too quickly while
9903 waiting for the rendezvous circuit to complete. Keep the intro
9904 circuit around longer instead of timing out and reopening new ones
9905 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
9906 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9907 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9909 - When handling multiple SOCKS request for the same .onion address,
9910 only fetch the service descriptor once.
9911 - Avoid a possible double close of a circuit by the intro point on
9912 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9913 bugfix on 0.3.0.1-alpha.
9914 - When reloading configured onion services, copy all information
9915 from the old service object. Previously, some data was omitted,
9916 causing delays in descriptor upload, and other bugs. Fixes bug
9917 23790; bugfix on 0.2.1.9-alpha.
9919 o Minor bugfixes (path selection):
9920 - When selecting relays by bandwidth, avoid a rounding error that
9921 could sometimes cause load to be imbalanced incorrectly.
9922 Previously, we would always round upwards; now, we round towards
9923 the nearest integer. This had the biggest effect when a relay's
9924 weight adjustments should have given it weight 0, but it got
9925 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9926 - When calculating the fraction of nodes that have descriptors, and
9927 all nodes in the network have zero bandwidths, count the number of
9928 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9929 - Actually log the total bandwidth in compute_weighted_bandwidths().
9930 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9932 o Minor bugfixes (portability):
9933 - Stop using the PATH_MAX variable, which is not defined on GNU
9934 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
9935 - Fix a bug in the bit-counting parts of our timing-wheel code on
9936 MSVC. (Note that MSVC is still not a supported build platform, due
9937 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9940 o Minor bugfixes (relay):
9941 - When uploading our descriptor for the first time after startup,
9942 report the reason for uploading as "Tor just started" rather than
9943 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
9944 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9945 relays, to prevent spurious address resolutions and descriptor
9946 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9947 bugfix on in 0.2.8.1-alpha.
9948 - Avoid a crash when transitioning from client mode to bridge mode.
9949 Previously, we would launch the worker threads whenever our
9950 "public server" mode changed, but not when our "server" mode
9951 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9953 o Minor bugfixes (testing):
9954 - Fix a spurious fuzzing-only use of an uninitialized value. Found
9955 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
9956 - Test that IPv6-only clients can use microdescriptors when running
9957 "make test-network-all". Requires chutney master 61c28b9 or later.
9958 Closes ticket 24109.
9959 - Prevent scripts/test/coverage from attempting to move gcov output
9960 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
9961 - Capture and detect several "Result does not fit" warnings in unit
9962 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
9964 - Fix additional channelpadding unit test failures by using mocked
9965 time instead of actual time for all tests. Fixes bug 23608; bugfix
9967 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
9968 to correctly handle cases where a caller gives it an RSA key of
9969 under 160 bits. (This is not actually a bug in Tor itself, but
9970 rather in our fuzzing code.) Fixes bug 24247; bugfix on
9971 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
9972 - Fix a broken unit test for the OutboundAddress option: the parsing
9973 function was never returning an error on failure. Fixes bug 23366;
9974 bugfix on 0.3.0.3-alpha.
9975 - Fix a signed-integer overflow in the unit tests for
9976 dir/download_status_random_backoff, which was untriggered until we
9977 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
9979 o Minor bugfixes (usability, control port):
9980 - Stop making an unnecessary routerlist check in NETINFO clock skew
9981 detection; this was preventing clients from reporting NETINFO clock
9982 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
9984 o Code simplification and refactoring:
9985 - Remove various ways of testing circuits and connections for
9986 "clientness"; instead, favor channel_is_client(). Part of
9988 - Extract the code for handling newly-open channels into a separate
9989 function from the general code to handle channel state
9990 transitions. This change simplifies our callgraph, reducing the
9991 size of the largest strongly connected component by roughly a
9992 factor of two. Closes ticket 22608.
9993 - Remove dead code for largely unused statistics on the number of
9994 times we've attempted various public key operations. Fixes bug
9995 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
9996 - Remove several now-obsolete functions for asking about old
9997 variants directory authority status. Closes ticket 22311; patch
9999 - Remove some of the code that once supported "Named" and "Unnamed"
10000 routers. Authorities no longer vote for these flags. Closes
10002 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
10003 and old hidden services, to indicate that they aren't suitable for
10004 new protocols or formats. Closes ticket 23026.
10005 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
10006 22521. Patch from Neel Chauhan.
10007 - Split the enormous circuit_send_next_onion_skin() function into
10008 multiple subfunctions. Closes ticket 22804.
10009 - Split the portions of the buffer.c module that handle particular
10010 protocols into separate modules. Part of ticket 23149.
10011 - Use our test macros more consistently, to produce more useful
10012 error messages when our unit tests fail. Add coccinelle patches to
10013 allow us to re-check for test macro uses. Closes ticket 22497.
10015 o Deprecated features:
10016 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
10017 now deprecated; they do not apply to relays, and they have had no
10018 effect on clients since 0.2.8.x. Closes ticket 19704.
10019 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
10020 only applies to direct unencrypted HTTP connections to your
10021 directory server, which your Tor probably isn't using. Closes
10025 - Add notes in man page regarding OS support for the various
10026 scheduler types. Attempt to use less jargon in the scheduler
10027 section. Closes ticket 24254.
10028 - Clarify that the Address option is entirely about setting an
10029 advertised IPv4 address. Closes ticket 18891.
10030 - Clarify the manpage's use of the term "address" to clarify what
10031 kind of address is intended. Closes ticket 21405.
10032 - Document that onion service subdomains are allowed, and ignored.
10033 Closes ticket 18736.
10034 - Clarify in the manual that "Sandbox 1" is only supported on Linux
10035 kernels. Closes ticket 22677.
10036 - Document all values of PublishServerDescriptor in the manpage.
10037 Closes ticket 15645.
10038 - Improve the documentation for the directory port part of the
10039 DirAuthority line. Closes ticket 20152.
10040 - Restore documentation for the authorities' "approved-routers"
10041 file. Closes ticket 21148.
10043 o Removed features:
10044 - The AllowDotExit option has been removed as unsafe. It has been
10045 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
10046 - The ClientDNSRejectInternalAddresses flag can no longer be set on
10047 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
10048 Closes ticket 21031.
10049 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
10050 nobody was using it any longer. Closes ticket 22377.
10053 Changes in version 0.3.1.9 - 2017-12-01:
10054 Tor 0.3.1.9 backports important security and stability fixes from the
10055 0.3.2 development series. All Tor users should upgrade to this
10056 release, or to another of the releases coming out today.
10058 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10059 - Fix a denial of service bug where an attacker could use a
10060 malformed directory object to cause a Tor instance to pause while
10061 OpenSSL would try to read a passphrase from the terminal. (Tor
10062 instances run without a terminal, which is the case for most Tor
10063 packages, are not impacted.) Fixes bug 24246; bugfix on every
10064 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10065 Found by OSS-Fuzz as testcase 6360145429790720.
10066 - Fix a denial of service issue where an attacker could crash a
10067 directory authority using a malformed router descriptor. Fixes bug
10068 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10070 - When checking for replays in the INTRODUCE1 cell data for a
10071 (legacy) onion service, correctly detect replays in the RSA-
10072 encrypted part of the cell. We were previously checking for
10073 replays on the entire cell, but those can be circumvented due to
10074 the malleability of Tor's legacy hybrid encryption. This fix helps
10075 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10076 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10079 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10080 - Fix a use-after-free error that could crash v2 Tor onion services
10081 when they failed to open circuits while expiring introduction
10082 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10083 also tracked as TROVE-2017-013 and CVE-2017-8823.
10085 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10086 - When running as a relay, make sure that we never build a path
10087 through ourselves, even in the case where we have somehow lost the
10088 version of our descriptor appearing in the consensus. Fixes part
10089 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10090 as TROVE-2017-012 and CVE-2017-8822.
10091 - When running as a relay, make sure that we never choose ourselves
10092 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
10093 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
10095 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10096 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10097 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10098 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10099 identifying and finding a workaround to this bug and to Moritz,
10100 Arthur Edelstein, and Roger for helping to track it down and
10103 o Minor features (bridge):
10104 - Bridges now include notice in their descriptors that they are
10105 bridges, and notice of their distribution status, based on their
10106 publication settings. Implements ticket 18329. For more fine-
10107 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10110 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10111 - Add an IPv6 address for the "bastet" directory authority. Closes
10114 o Minor features (geoip):
10115 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10118 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10119 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10120 relays, to prevent spurious address resolutions and descriptor
10121 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10122 bugfix on in 0.2.8.1-alpha.
10124 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10125 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10126 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10128 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10129 - When a circuit is marked for close, do not attempt to package any
10130 cells for channels on that circuit. Previously, we would detect
10131 this condition lower in the call stack, when we noticed that the
10132 circuit had no attached channel, and log an annoying message.
10133 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10135 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
10136 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
10137 so it matches dir-spec.txt. Fixes bug 24262; bugfix
10140 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10141 - Avoid a crash when transitioning from client mode to bridge mode.
10142 Previously, we would launch the worker threads whenever our
10143 "public server" mode changed, but not when our "server" mode
10144 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10147 Changes in version 0.3.0.13 - 2017-12-01
10148 Tor 0.3.0.13 backports important security and stability bugfixes from
10149 later Tor releases. All Tor users should upgrade to this release, or
10150 to another of the releases coming out today.
10152 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
10153 2018. If you need a release with long-term support, please stick with
10154 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10156 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10157 - Fix a denial of service bug where an attacker could use a
10158 malformed directory object to cause a Tor instance to pause while
10159 OpenSSL would try to read a passphrase from the terminal. (Tor
10160 instances run without a terminal, which is the case for most Tor
10161 packages, are not impacted.) Fixes bug 24246; bugfix on every
10162 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10163 Found by OSS-Fuzz as testcase 6360145429790720.
10164 - Fix a denial of service issue where an attacker could crash a
10165 directory authority using a malformed router descriptor. Fixes bug
10166 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10168 - When checking for replays in the INTRODUCE1 cell data for a
10169 (legacy) onion service, correctly detect replays in the RSA-
10170 encrypted part of the cell. We were previously checking for
10171 replays on the entire cell, but those can be circumvented due to
10172 the malleability of Tor's legacy hybrid encryption. This fix helps
10173 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10174 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10177 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10178 - Fix a use-after-free error that could crash v2 Tor onion services
10179 when they failed to open circuits while expiring introduction
10180 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10181 also tracked as TROVE-2017-013 and CVE-2017-8823.
10183 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10184 - When running as a relay, make sure that we never build a path
10185 through ourselves, even in the case where we have somehow lost the
10186 version of our descriptor appearing in the consensus. Fixes part
10187 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10188 as TROVE-2017-012 and CVE-2017-8822.
10189 - When running as a relay, make sure that we never choose ourselves
10190 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
10191 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
10193 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10194 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10195 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10196 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10197 identifying and finding a workaround to this bug and to Moritz,
10198 Arthur Edelstein, and Roger for helping to track it down and
10201 o Minor features (security, windows, backport from 0.3.1.1-alpha):
10202 - Enable a couple of pieces of Windows hardening: one
10203 (HeapEnableTerminationOnCorruption) that has been on-by-default
10204 since Windows 8, and unavailable before Windows 7; and one
10205 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10206 affect us, but shouldn't do any harm. Closes ticket 21953.
10208 o Minor features (bridge, backport from 0.3.1.9):
10209 - Bridges now include notice in their descriptors that they are
10210 bridges, and notice of their distribution status, based on their
10211 publication settings. Implements ticket 18329. For more fine-
10212 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10215 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10216 - Add an IPv6 address for the "bastet" directory authority. Closes
10219 o Minor features (geoip):
10220 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10223 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10224 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10225 relays, to prevent spurious address resolutions and descriptor
10226 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10227 bugfix on in 0.2.8.1-alpha.
10229 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10230 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10231 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10233 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10234 - When a circuit is marked for close, do not attempt to package any
10235 cells for channels on that circuit. Previously, we would detect
10236 this condition lower in the call stack, when we noticed that the
10237 circuit had no attached channel, and log an annoying message.
10238 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10240 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10241 - Avoid a crash when transitioning from client mode to bridge mode.
10242 Previously, we would launch the worker threads whenever our
10243 "public server" mode changed, but not when our "server" mode
10244 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10246 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10247 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10248 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10251 Changes in version 0.2.9.14 - 2017-12-01
10252 Tor 0.3.0.13 backports important security and stability bugfixes from
10253 later Tor releases. All Tor users should upgrade to this release, or
10254 to another of the releases coming out today.
10256 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10257 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10258 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10259 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10260 identifying and finding a workaround to this bug and to Moritz,
10261 Arthur Edelstein, and Roger for helping to track it down and
10264 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10265 - Fix a denial of service bug where an attacker could use a
10266 malformed directory object to cause a Tor instance to pause while
10267 OpenSSL would try to read a passphrase from the terminal. (Tor
10268 instances run without a terminal, which is the case for most Tor
10269 packages, are not impacted.) Fixes bug 24246; bugfix on every
10270 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10271 Found by OSS-Fuzz as testcase 6360145429790720.
10272 - Fix a denial of service issue where an attacker could crash a
10273 directory authority using a malformed router descriptor. Fixes bug
10274 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10276 - When checking for replays in the INTRODUCE1 cell data for a
10277 (legacy) onion service, correctly detect replays in the RSA-
10278 encrypted part of the cell. We were previously checking for
10279 replays on the entire cell, but those can be circumvented due to
10280 the malleability of Tor's legacy hybrid encryption. This fix helps
10281 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10282 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10285 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10286 - Fix a use-after-free error that could crash v2 Tor onion services
10287 when they failed to open circuits while expiring introduction
10288 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10289 also tracked as TROVE-2017-013 and CVE-2017-8823.
10291 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10292 - When running as a relay, make sure that we never build a path
10293 through ourselves, even in the case where we have somehow lost the
10294 version of our descriptor appearing in the consensus. Fixes part
10295 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10296 as TROVE-2017-012 and CVE-2017-8822.
10298 o Minor features (bridge, backport from 0.3.1.9):
10299 - Bridges now include notice in their descriptors that they are
10300 bridges, and notice of their distribution status, based on their
10301 publication settings. Implements ticket 18329. For more fine-
10302 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10305 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10306 - Add an IPv6 address for the "bastet" directory authority. Closes
10309 o Minor features (geoip):
10310 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10313 o Minor features (security, windows, backport from 0.3.1.1-alpha):
10314 - Enable a couple of pieces of Windows hardening: one
10315 (HeapEnableTerminationOnCorruption) that has been on-by-default
10316 since Windows 8, and unavailable before Windows 7; and one
10317 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10318 affect us, but shouldn't do any harm. Closes ticket 21953.
10320 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10321 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10322 relays, to prevent spurious address resolutions and descriptor
10323 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10324 bugfix on in 0.2.8.1-alpha.
10326 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10327 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10328 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10330 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10331 - When a circuit is marked for close, do not attempt to package any
10332 cells for channels on that circuit. Previously, we would detect
10333 this condition lower in the call stack, when we noticed that the
10334 circuit had no attached channel, and log an annoying message.
10335 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10337 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10338 - Avoid a crash when transitioning from client mode to bridge mode.
10339 Previously, we would launch the worker threads whenever our
10340 "public server" mode changed, but not when our "server" mode
10341 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10343 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10344 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10345 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10348 Changes in version 0.2.8.17 - 2017-12-01
10349 Tor 0.2.8.17 backports important security and stability bugfixes from
10350 later Tor releases. All Tor users should upgrade to this release, or
10351 to another of the releases coming out today.
10353 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10354 2018. If you need a release with long-term support, please upgrade with
10355 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10357 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10358 - Fix a denial of service bug where an attacker could use a
10359 malformed directory object to cause a Tor instance to pause while
10360 OpenSSL would try to read a passphrase from the terminal. (Tor
10361 instances run without a terminal, which is the case for most Tor
10362 packages, are not impacted.) Fixes bug 24246; bugfix on every
10363 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10364 Found by OSS-Fuzz as testcase 6360145429790720.
10365 - When checking for replays in the INTRODUCE1 cell data for a
10366 (legacy) onion service, correctly detect replays in the RSA-
10367 encrypted part of the cell. We were previously checking for
10368 replays on the entire cell, but those can be circumvented due to
10369 the malleability of Tor's legacy hybrid encryption. This fix helps
10370 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10371 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10374 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10375 - Fix a use-after-free error that could crash v2 Tor onion services
10376 when they failed to open circuits while expiring introduction
10377 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10378 also tracked as TROVE-2017-013 and CVE-2017-8823.
10380 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10381 - When running as a relay, make sure that we never build a path through
10382 ourselves, even in the case where we have somehow lost the version of
10383 our descriptor appearing in the consensus. Fixes part of bug 21534;
10384 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
10387 o Minor features (bridge, backport from 0.3.1.9):
10388 - Bridges now include notice in their descriptors that they are
10389 bridges, and notice of their distribution status, based on their
10390 publication settings. Implements ticket 18329. For more fine-
10391 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10394 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10395 - Add an IPv6 address for the "bastet" directory authority. Closes
10398 o Minor features (geoip):
10399 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10402 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10403 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10404 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10407 Changes in version 0.2.5.16 - 2017-12-01
10408 Tor 0.2.5.13 backports important security and stability bugfixes from
10409 later Tor releases. All Tor users should upgrade to this release, or
10410 to another of the releases coming out today.
10412 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10413 2018. If you need a release with long-term support, please upgrade to
10414 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10416 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10417 - Fix a denial of service bug where an attacker could use a
10418 malformed directory object to cause a Tor instance to pause while
10419 OpenSSL would try to read a passphrase from the terminal. (Tor
10420 instances run without a terminal, which is the case for most Tor
10421 packages, are not impacted.) Fixes bug 24246; bugfix on every
10422 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10423 Found by OSS-Fuzz as testcase 6360145429790720.
10424 - When checking for replays in the INTRODUCE1 cell data for a
10425 (legacy) onion service, correctly detect replays in the RSA-
10426 encrypted part of the cell. We were previously checking for
10427 replays on the entire cell, but those can be circumvented due to
10428 the malleability of Tor's legacy hybrid encryption. This fix helps
10429 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10430 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10433 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10434 - When running as a relay, make sure that we never build a path
10435 through ourselves, even in the case where we have somehow lost the
10436 version of our descriptor appearing in the consensus. Fixes part
10437 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10438 as TROVE-2017-012 and CVE-2017-8822.
10440 o Minor features (bridge, backport from 0.3.1.9):
10441 - Bridges now include notice in their descriptors that they are
10442 bridges, and notice of their distribution status, based on their
10443 publication settings. Implements ticket 18329. For more fine-
10444 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10447 o Minor features (geoip):
10448 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10452 Changes in version 0.2.5.15 - 2017-10-25
10453 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
10454 series. It also adds a new directory authority, Bastet.
10456 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10457 2018. If you need a release with long-term support, please upgrade to
10458 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10460 o Directory authority changes:
10461 - Add "Bastet" as a ninth directory authority to the default list.
10462 Closes ticket 23910.
10463 - The directory authority "Longclaw" has changed its IP address.
10464 Closes ticket 23592.
10466 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10467 - Avoid an assertion failure bug affecting our implementation of
10468 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10469 handling of "0xx" differs from what we had expected. Fixes bug
10470 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10472 o Minor features (geoip):
10473 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10476 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10477 - Fix a memset() off the end of an array when packing cells. This
10478 bug should be harmless in practice, since the corrupted bytes are
10479 still in the same structure, and are always padding bytes,
10480 ignored, or immediately overwritten, depending on compiler
10481 behavior. Nevertheless, because the memset()'s purpose is to make
10482 sure that any other cell-handling bugs can't expose bytes to the
10483 network, we need to fix it. Fixes bug 22737; bugfix on
10484 0.2.4.11-alpha. Fixes CID 1401591.
10486 o Build features (backport from 0.3.1.5-alpha):
10487 - Tor's repository now includes a Travis Continuous Integration (CI)
10488 configuration file (.travis.yml). This is meant to help new
10489 developers and contributors who fork Tor to a Github repository be
10490 better able to test their changes, and understand what we expect
10491 to pass. To use this new build feature, you must fork Tor to your
10492 Github account, then go into the "Integrations" menu in the
10493 repository settings for your fork and enable Travis, then push
10494 your changes. Closes ticket 22636.
10497 Changes in version 0.2.8.16 - 2017-10-25
10498 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
10499 series, including a bugfix for a crash issue that had affected relays
10500 under memory pressure. It also adds a new directory authority, Bastet.
10502 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10503 2018. If you need a release with long-term support, please stick with
10504 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10506 o Directory authority changes:
10507 - Add "Bastet" as a ninth directory authority to the default list.
10508 Closes ticket 23910.
10509 - The directory authority "Longclaw" has changed its IP address.
10510 Closes ticket 23592.
10512 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10513 - Fix a timing-based assertion failure that could occur when the
10514 circuit out-of-memory handler freed a connection's output buffer.
10515 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10517 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10518 - Remove longclaw's IPv6 address, as it will soon change. Authority
10519 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10520 3/8 directory authorities with IPv6 addresses, but there are also
10521 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10523 o Minor features (geoip):
10524 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10528 Changes in version 0.2.9.13 - 2017-10-25
10529 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
10530 series, including a bugfix for a crash issue that had affected relays
10531 under memory pressure. It also adds a new directory authority, Bastet.
10533 o Directory authority changes:
10534 - Add "Bastet" as a ninth directory authority to the default list.
10535 Closes ticket 23910.
10536 - The directory authority "Longclaw" has changed its IP address.
10537 Closes ticket 23592.
10539 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10540 - Fix a timing-based assertion failure that could occur when the
10541 circuit out-of-memory handler freed a connection's output buffer.
10542 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10544 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10545 - Remove longclaw's IPv6 address, as it will soon change. Authority
10546 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10547 3/8 directory authorities with IPv6 addresses, but there are also
10548 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10550 o Minor features (geoip):
10551 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10554 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10555 - When a directory authority rejects a descriptor or extrainfo with
10556 a given digest, mark that digest as undownloadable, so that we do
10557 not attempt to download it again over and over. We previously
10558 tried to avoid downloading such descriptors by other means, but we
10559 didn't notice if we accidentally downloaded one anyway. This
10560 behavior became problematic in 0.2.7.2-alpha, when authorities
10561 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10564 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10565 - Clear the address when node_get_prim_orport() returns early.
10566 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10568 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10569 - When running as a Windows service, set the ID of the main thread
10570 correctly. Failure to do so made us fail to send log messages to
10571 the controller in 0.2.1.16-rc, slowed down controller event
10572 delivery in 0.2.7.3-rc and later, and crash with an assertion
10573 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10574 Patch and diagnosis from "Vort".
10577 Changes in version 0.3.0.12 - 2017-10-25
10578 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
10579 series, including a bugfix for a crash issue that had affected relays
10580 under memory pressure. It also adds a new directory authority, Bastet.
10582 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
10583 2018. If you need a release with long-term support, please stick with
10584 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10586 o Directory authority changes:
10587 - Add "Bastet" as a ninth directory authority to the default list.
10588 Closes ticket 23910.
10589 - The directory authority "Longclaw" has changed its IP address.
10590 Closes ticket 23592.
10592 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10593 - Fix a timing-based assertion failure that could occur when the
10594 circuit out-of-memory handler freed a connection's output buffer.
10595 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10597 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10598 - Remove longclaw's IPv6 address, as it will soon change. Authority
10599 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10600 3/8 directory authorities with IPv6 addresses, but there are also
10601 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10603 o Minor features (geoip):
10604 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10607 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10608 - When a directory authority rejects a descriptor or extrainfo with
10609 a given digest, mark that digest as undownloadable, so that we do
10610 not attempt to download it again over and over. We previously
10611 tried to avoid downloading such descriptors by other means, but we
10612 didn't notice if we accidentally downloaded one anyway. This
10613 behavior became problematic in 0.2.7.2-alpha, when authorities
10614 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10617 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10618 - Avoid a possible double close of a circuit by the intro point on
10619 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10620 bugfix on 0.3.0.1-alpha.
10622 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10623 - Clear the address when node_get_prim_orport() returns early.
10624 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10626 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10627 - When running as a Windows service, set the ID of the main thread
10628 correctly. Failure to do so made us fail to send log messages to
10629 the controller in 0.2.1.16-rc, slowed down controller event
10630 delivery in 0.2.7.3-rc and later, and crash with an assertion
10631 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10632 Patch and diagnosis from "Vort".
10635 Changes in version 0.3.1.8 - 2017-10-25
10636 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
10637 It includes several bugfixes, including a bugfix for a crash issue
10638 that had affected relays under memory pressure. It also adds
10639 a new directory authority, Bastet.
10641 o Directory authority changes:
10642 - Add "Bastet" as a ninth directory authority to the default list.
10643 Closes ticket 23910.
10644 - The directory authority "Longclaw" has changed its IP address.
10645 Closes ticket 23592.
10647 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10648 - Fix a timing-based assertion failure that could occur when the
10649 circuit out-of-memory handler freed a connection's output buffer.
10650 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10652 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10653 - Remove longclaw's IPv6 address, as it will soon change. Authority
10654 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10655 3/8 directory authorities with IPv6 addresses, but there are also
10656 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10658 o Minor features (geoip):
10659 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10662 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
10663 - Fix a compilation warning when building with zstd support on
10664 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10665 and fixed by Andreas Stieger.
10667 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
10668 - Handle a pathological case when decompressing Zstandard data when
10669 the output buffer size is zero. Fixes bug 23551; bugfix
10672 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
10673 - Remove the length limit on HTTP status lines that authorities can
10674 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
10676 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10677 - Avoid a possible double close of a circuit by the intro point on
10678 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10679 bugfix on 0.3.0.1-alpha.
10681 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10682 - Clear the address when node_get_prim_orport() returns early.
10683 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10685 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
10686 - Fix additional channelpadding unit test failures by using mocked
10687 time instead of actual time for all tests. Fixes bug 23608; bugfix
10691 Changes in version 0.2.8.15 - 2017-09-18
10692 Tor 0.2.8.15 backports a collection of bugfixes from later
10695 Most significantly, it includes a fix for TROVE-2017-008, a
10696 security bug that affects hidden services running with the
10697 SafeLogging option disabled. For more information, see
10698 https://trac.torproject.org/projects/tor/ticket/23490
10700 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
10701 2018. We suggest that you upgrade to the latest stable release if
10702 possible. If you can't, we recommend that you upgrade at least to
10703 0.2.9, which will be supported until 2020.
10705 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10706 - Avoid an assertion failure bug affecting our implementation of
10707 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10708 handling of "0xx" differs from what we had expected. Fixes bug
10709 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10712 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10715 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10716 - Backport a fix for an "unused variable" warning that appeared
10717 in some versions of mingw. Fixes bug 22838; bugfix on
10720 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10721 - Fix a memset() off the end of an array when packing cells. This
10722 bug should be harmless in practice, since the corrupted bytes are
10723 still in the same structure, and are always padding bytes,
10724 ignored, or immediately overwritten, depending on compiler
10725 behavior. Nevertheless, because the memset()'s purpose is to make
10726 sure that any other cell-handling bugs can't expose bytes to the
10727 network, we need to fix it. Fixes bug 22737; bugfix on
10728 0.2.4.11-alpha. Fixes CID 1401591.
10730 o Build features (backport from 0.3.1.5-alpha):
10731 - Tor's repository now includes a Travis Continuous Integration (CI)
10732 configuration file (.travis.yml). This is meant to help new
10733 developers and contributors who fork Tor to a Github repository be
10734 better able to test their changes, and understand what we expect
10735 to pass. To use this new build feature, you must fork Tor to your
10736 Github account, then go into the "Integrations" menu in the
10737 repository settings for your fork and enable Travis, then push
10738 your changes. Closes ticket 22636.
10741 Changes in version 0.2.9.12 - 2017-09-18
10742 Tor 0.2.9.12 backports a collection of bugfixes from later
10745 Most significantly, it includes a fix for TROVE-2017-008, a
10746 security bug that affects hidden services running with the
10747 SafeLogging option disabled. For more information, see
10748 https://trac.torproject.org/projects/tor/ticket/23490
10750 o Major features (security, backport from 0.3.0.2-alpha):
10751 - Change the algorithm used to decide DNS TTLs on client and server
10752 side, to better resist DNS-based correlation attacks like the
10753 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10754 Feamster. Now relays only return one of two possible DNS TTL
10755 values, and clients are willing to believe DNS TTL values up to 3
10756 hours long. Closes ticket 19769.
10758 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
10759 - Fix a rare crash when sending a begin cell on a circuit whose
10760 linked directory connection had already been closed. Fixes bug
10761 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
10763 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
10764 - Fix a bug that prevented exit nodes from caching DNS records for
10765 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10767 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10768 - Fix a typo that had prevented TPROXY-based transparent proxying
10769 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10770 Patch from "d4fq0fQAgoJ".
10772 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10773 - Avoid an assertion failure bug affecting our implementation of
10774 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10775 handling of "0xx" differs from what we had expected. Fixes bug
10776 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10778 o Minor features (code style, backport from 0.3.1.3-alpha):
10779 - Add "Falls through" comments to our codebase, in order to silence
10780 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10781 Stieger. Closes ticket 22446.
10783 o Minor features (geoip):
10784 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10787 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
10788 - Roll over monthly accounting at the configured hour and minute,
10789 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10790 Found by Andrey Karpov with PVS-Studio.
10792 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
10793 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10794 bugfix on 0.2.8.1-alpha.
10795 - Fix warnings when building with libscrypt and openssl scrypt support
10796 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10797 - When building with certain versions the mingw C header files, avoid
10798 float-conversion warnings when calling the C functions isfinite(),
10799 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
10801 o Minor bugfixes (compilation, backport from 0.3.1.7):
10802 - Avoid compiler warnings in the unit tests for running tor_sscanf()
10803 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10805 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10806 - Backport a fix for an "unused variable" warning that appeared
10807 in some versions of mingw. Fixes bug 22838; bugfix on
10810 o Minor bugfixes (controller, backport from 0.3.1.7):
10811 - Do not crash when receiving a HSPOST command with an empty body.
10812 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10813 - Do not crash when receiving a POSTDESCRIPTOR command with an
10814 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10816 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10817 - Avoid Coverity build warnings related to our BUG() macro. By
10818 default, Coverity treats BUG() as the Linux kernel does: an
10819 instant abort(). We need to override that so our BUG() macro
10820 doesn't prevent Coverity from analyzing functions that use it.
10821 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10823 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10824 - Fix a memset() off the end of an array when packing cells. This
10825 bug should be harmless in practice, since the corrupted bytes are
10826 still in the same structure, and are always padding bytes,
10827 ignored, or immediately overwritten, depending on compiler
10828 behavior. Nevertheless, because the memset()'s purpose is to make
10829 sure that any other cell-handling bugs can't expose bytes to the
10830 network, we need to fix it. Fixes bug 22737; bugfix on
10831 0.2.4.11-alpha. Fixes CID 1401591.
10833 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10834 - When setting the maximum number of connections allowed by the OS,
10835 always allow some extra file descriptors for other files. Fixes
10836 bug 22797; bugfix on 0.2.0.10-alpha.
10838 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10839 - Avoid a sandbox failure when trying to re-bind to a socket and
10840 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10842 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10843 - Permit the fchmod system call, to avoid crashing on startup when
10844 starting with the seccomp2 sandbox and an unexpected set of
10845 permissions on the data directory or its contents. Fixes bug
10846 22516; bugfix on 0.2.5.4-alpha.
10848 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
10849 - Avoid a double-marked-circuit warning that could happen when we
10850 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
10853 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10854 - Reject version numbers with non-numeric prefixes (such as +, -, or
10855 whitespace). Disallowing whitespace prevents differential version
10856 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10857 and part of 21508; bugfix on 0.0.8pre1.
10859 o Build features (backport from 0.3.1.5-alpha):
10860 - Tor's repository now includes a Travis Continuous Integration (CI)
10861 configuration file (.travis.yml). This is meant to help new
10862 developers and contributors who fork Tor to a Github repository be
10863 better able to test their changes, and understand what we expect
10864 to pass. To use this new build feature, you must fork Tor to your
10865 Github account, then go into the "Integrations" menu in the
10866 repository settings for your fork and enable Travis, then push
10867 your changes. Closes ticket 22636.
10870 Changes in version 0.3.0.11 - 2017-09-18
10871 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
10874 Most significantly, it includes a fix for TROVE-2017-008, a
10875 security bug that affects hidden services running with the
10876 SafeLogging option disabled. For more information, see
10877 https://trac.torproject.org/projects/tor/ticket/23490
10879 o Minor features (code style, backport from 0.3.1.7):
10880 - Add "Falls through" comments to our codebase, in order to silence
10881 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10882 Stieger. Closes ticket 22446.
10885 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10888 o Minor bugfixes (compilation, backport from 0.3.1.7):
10889 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10890 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10892 o Minor bugfixes (controller, backport from 0.3.1.7):
10893 - Do not crash when receiving a HSPOST command with an empty body.
10894 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10895 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10896 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10898 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10899 - When setting the maximum number of connections allowed by the OS,
10900 always allow some extra file descriptors for other files. Fixes
10901 bug 22797; bugfix on 0.2.0.10-alpha.
10903 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
10904 - Remove a forgotten debugging message when an introduction point
10905 successfully establishes a hidden service prop224 circuit with
10907 - Change three other log_warn() for an introduction point to
10908 protocol warnings, because they can be failure from the network
10909 and are not relevant to the operator. Fixes bug 23078; bugfix on
10910 0.3.0.1-alpha and 0.3.0.2-alpha.
10913 Changes in version 0.3.1.7 - 2017-09-18
10914 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
10916 With the 0.3.1 series, Tor now serves and downloads directory
10917 information in more compact formats, to save on bandwidth overhead. It
10918 also contains a new padding system to resist netflow-based traffic
10919 analysis, and experimental support for building parts of Tor in Rust
10920 (though no parts of Tor are in Rust yet). There are also numerous
10921 small features, bugfixes on earlier release series, and groundwork for
10922 the hidden services revamp of 0.3.2.
10924 This release also includes a fix for TROVE-2017-008, a security bug
10925 that affects hidden services running with the SafeLogging option
10926 disabled. For more information, see
10927 https://trac.torproject.org/projects/tor/ticket/23490
10929 Per our stable release policy, we plan to support each stable release
10930 series for at least the next nine months, or for three months after
10931 the first stable release of the next series: whichever is longer. If
10932 you need a release with long-term support, we recommend that you stay
10933 with the 0.2.9 series.
10935 Below is a list of the changes since 0.3.0. For a list of all
10936 changes since 0.3.1.6-rc, see the ChangeLog file.
10938 o New dependencies:
10939 - To build with zstd and lzma support, Tor now requires the
10940 pkg-config tool at build time.
10942 o Major bugfixes (security, hidden services, loggging):
10943 - Fix a bug where we could log uninitialized stack when a certain
10944 hidden service error occurred while SafeLogging was disabled.
10945 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
10946 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
10948 o Major features (build system, continuous integration):
10949 - Tor's repository now includes a Travis Continuous Integration (CI)
10950 configuration file (.travis.yml). This is meant to help new
10951 developers and contributors who fork Tor to a Github repository be
10952 better able to test their changes, and understand what we expect
10953 to pass. To use this new build feature, you must fork Tor to your
10954 Github account, then go into the "Integrations" menu in the
10955 repository settings for your fork and enable Travis, then push
10956 your changes. Closes ticket 22636.
10958 o Major features (directory protocol):
10959 - Tor relays and authorities can now serve clients an abbreviated
10960 version of the consensus document, containing only the changes
10961 since an older consensus document that the client holds. Clients
10962 now request these documents when available. When both client and
10963 server use this new protocol, they will use far less bandwidth (up
10964 to 94% less) to keep the client's consensus up-to-date. Implements
10965 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
10966 - Tor can now compress directory traffic with lzma or with zstd
10967 compression algorithms, which can deliver better bandwidth
10968 performance. Because lzma is computationally expensive, it's only
10969 used for documents that can be compressed once and served many
10970 times. Support for these algorithms requires that tor is built
10971 with the libzstd and/or liblzma libraries available. Implements
10972 proposal 278; closes ticket 21662.
10973 - Relays now perform the more expensive compression operations, and
10974 consensus diff generation, in worker threads. This separation
10975 avoids delaying the main thread when a new consensus arrives.
10977 o Major features (experimental):
10978 - Tor can now build modules written in Rust. To turn this on, pass
10979 the "--enable-rust" flag to the configure script. It's not time to
10980 get excited yet: currently, there is no actual Rust functionality
10981 beyond some simple glue code, and a notice at startup to tell you
10982 that Rust is running. Still, we hope that programmers and
10983 packagers will try building Tor with Rust support, so that we can
10984 find issues and solve portability problems. Closes ticket 22106.
10986 o Major features (traffic analysis resistance):
10987 - Connections between clients and relays now send a padding cell in
10988 each direction every 1.5 to 9.5 seconds (tunable via consensus
10989 parameters). This padding will not resist specialized
10990 eavesdroppers, but it should be enough to make many ISPs' routine
10991 network flow logging less useful in traffic analysis against
10994 Padding is negotiated using Tor's link protocol, so both relays
10995 and clients must upgrade for this to take effect. Clients may
10996 still send padding despite the relay's version by setting
10997 ConnectionPadding 1 in torrc, and may disable padding by setting
10998 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
10999 users with the torrc option ReducedConnectionPadding. Implements
11000 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
11001 - Relays will publish 24 hour totals of padding and non-padding cell
11002 counts to their extra-info descriptors, unless PaddingStatistics 0
11003 is set in torrc. These 24 hour totals are also rounded to
11004 multiples of 10000.
11006 o Major bugfixes (hidden service, relay, security):
11007 - Fix a remotely triggerable assertion failure when a hidden service
11008 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11009 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11010 - Fix a remotely triggerable assertion failure caused by receiving a
11011 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11012 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11015 o Major bugfixes (path selection, security):
11016 - When choosing which guard to use for a circuit, avoid the exit's
11017 family along with the exit itself. Previously, the new guard
11018 selection logic avoided the exit, but did not consider its family.
11019 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11020 006 and CVE-2017-0377.
11022 o Major bugfixes (connection usage):
11023 - We use NETINFO cells to try to determine if both relays involved
11024 in a connection will agree on the canonical status of that
11025 connection. We prefer the connections where this is the case for
11026 extend cells, and try to close connections where relays disagree
11027 on their canonical status early. Also, we now prefer the oldest
11028 valid connection for extend cells. These two changes should reduce
11029 the number of long-term connections that are kept open between
11030 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
11031 - Relays now log hourly statistics (look for
11032 "channel_check_for_duplicates" lines) on the total number of
11033 connections to other relays. If the number of connections per
11034 relay is unexpectedly large, this log message is at notice level.
11035 Otherwise it is at info.
11037 o Major bugfixes (entry guards):
11038 - When starting with an old consensus, do not add new entry guards
11039 unless the consensus is "reasonably live" (under 1 day old). Fixes
11040 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11041 - Don't block bootstrapping when a primary bridge is offline and we
11042 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11043 21969; bugfix on 0.3.0.3-alpha.
11045 o Major bugfixes (linux TPROXY support):
11046 - Fix a typo that had prevented TPROXY-based transparent proxying
11047 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11048 Patch from "d4fq0fQAgoJ".
11050 o Major bugfixes (openbsd, denial-of-service):
11051 - Avoid an assertion failure bug affecting our implementation of
11052 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11053 handling of "0xx" differs from what we had expected. Fixes bug
11054 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11056 o Major bugfixes (relay, link handshake):
11057 - When performing the v3 link handshake on a TLS connection, report
11058 that we have the x509 certificate that we actually used on that
11059 connection, even if we have changed certificates since that
11060 connection was first opened. Previously, we would claim to have
11061 used our most recent x509 link certificate, which would sometimes
11062 make the link handshake fail. Fixes one case of bug 22460; bugfix
11065 o Major bugfixes (relays, key management):
11066 - Regenerate link and authentication certificates whenever the key
11067 that signs them changes; also, regenerate link certificates
11068 whenever the signed key changes. Previously, these processes were
11069 only weakly coupled, and we relays could (for minutes to hours)
11070 wind up with an inconsistent set of keys and certificates, which
11071 other relays would not accept. Fixes two cases of bug 22460;
11072 bugfix on 0.3.0.1-alpha.
11073 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11074 send the certificate that matches the x509 certificate that we
11075 used on the TLS connection. Previously, there was a race condition
11076 if the TLS context rotated after we began the TLS handshake but
11077 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11080 o Minor features (security, windows):
11081 - Enable a couple of pieces of Windows hardening: one
11082 (HeapEnableTerminationOnCorruption) that has been on-by-default
11083 since Windows 8, and unavailable before Windows 7; and one
11084 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11085 affect us, but shouldn't do any harm. Closes ticket 21953.
11087 o Minor features (bridge authority):
11088 - Add "fingerprint" lines to the networkstatus-bridges file produced
11089 by bridge authorities. Closes ticket 22207.
11091 o Minor features (code style):
11092 - Add "Falls through" comments to our codebase, in order to silence
11093 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11094 Stieger. Closes ticket 22446.
11096 o Minor features (config options):
11097 - Allow "%include" directives in torrc configuration files. These
11098 directives import the settings from other files, or from all the
11099 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
11100 - Make SAVECONF return an error when overwriting a torrc that has
11101 includes. Using SAVECONF with the FORCE option will allow it to
11102 overwrite torrc even if includes are used. Related to ticket 1922.
11103 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
11104 will work without the FORCE option. Related to ticket 1922.
11106 o Minor features (controller):
11107 - Warn the first time that a controller requests data in the long-
11108 deprecated 'GETINFO network-status' format. Closes ticket 21703.
11110 o Minor features (defaults):
11111 - The default value for UseCreateFast is now 0: clients which
11112 haven't yet received a consensus document will now use a proper
11113 ntor handshake to talk to their directory servers whenever they
11114 can. Closes ticket 21407.
11115 - Onion key rotation and expiry intervals are now defined as a
11116 network consensus parameter, per proposal 274. The default
11117 lifetime of an onion key is increased from 7 to 28 days. Old onion
11118 keys will expire after 7 days by default. This change will make
11119 consensus diffs much smaller, and save significant bandwidth.
11120 Closes ticket 21641.
11122 o Minor features (defensive programming):
11123 - Create a pair of consensus parameters, nf_pad_tor2web and
11124 nf_pad_single_onion, to disable netflow padding in the consensus
11125 for non-anonymous connections in case the overhead is high. Closes
11128 o Minor features (diagnostic):
11129 - Add a stack trace to the bug warnings that can be logged when
11130 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
11131 attempt for bug 23105.
11132 - Add logging messages to try to diagnose a rare bug that seems to
11133 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
11134 think this is happening because of incorrect system clocks, but
11135 we'd like to know for certain. Diagnostic for bug 22466.
11136 - Avoid an assertion failure, and log a better error message, when
11137 unable to remove a file from the consensus cache on Windows.
11138 Attempts to mitigate and diagnose bug 22752.
11140 o Minor features (directory authority):
11141 - Improve the message that authorities report to relays that present
11142 RSA/Ed25519 keypairs that conflict with previously pinned keys.
11143 Closes ticket 22348.
11145 o Minor features (directory cache, consensus diff):
11146 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
11147 operators with low-resource environments to adjust the number of
11148 consensuses they'll store and generate diffs from. Most cache
11149 operators should leave it unchanged. Helps to work around
11152 o Minor features (fallback directory list):
11153 - Update the fallback directory mirror whitelist and blacklist based
11154 on operator emails. Closes task 21121.
11155 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11156 December 2016 (of which ~126 were still functional) with a list of
11157 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11158 2017. Resolves ticket 21564.
11160 o Minor features (geoip):
11161 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11164 o Minor features (hidden services, logging):
11165 - Log a message when a hidden service descriptor has fewer
11166 introduction points than specified in
11167 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
11168 - Log a message when a hidden service reaches its introduction point
11169 circuit limit, and when that limit is reset. Follow up to ticket
11170 21594; closes ticket 21622.
11171 - Warn user if multiple entries in EntryNodes and at least one
11172 HiddenService are used together. Pinning EntryNodes along with a
11173 hidden service can be possibly harmful; for instance see ticket
11174 14917 or 21155. Closes ticket 21155.
11176 o Minor features (linux seccomp2 sandbox):
11177 - We now have a document storage backend compatible with the Linux
11178 seccomp2 sandbox. This backend is used for consensus documents and
11179 diffs between them; in the long term, we'd like to use it for
11180 unparseable directory material too. Closes ticket 21645
11181 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
11182 from 1MB to 16MB. This was necessary with the glibc allocator in
11183 order to allow worker threads to allocate more memory -- which in
11184 turn is necessary because of our new use of worker threads for
11185 compression. Closes ticket 22096.
11187 o Minor features (logging):
11188 - Log files are no longer created world-readable by default.
11189 (Previously, most distributors would store the logs in a non-
11190 world-readable location to prevent inappropriate access. This
11191 change is an extra precaution.) Closes ticket 21729; patch
11194 o Minor features (performance):
11195 - Our Keccak (SHA-3) implementation now accesses memory more
11196 efficiently, especially on little-endian systems. Closes
11198 - Add an O(1) implementation of channel_find_by_global_id(), to
11199 speed some controller functions.
11201 o Minor features (relay, configuration):
11202 - The MyFamily option may now be repeated as many times as desired,
11203 for relays that want to configure large families. Closes ticket
11204 4998; patch by Daniel Pinto.
11206 o Minor features (relay, performance):
11207 - Always start relays with at least two worker threads, to prevent
11208 priority inversion on slow tasks. Part of the fix for bug 22883.
11209 - Allow background work to be queued with different priorities, so
11210 that a big pile of slow low-priority jobs will not starve out
11211 higher priority jobs. This lays the groundwork for a fix for
11214 o Minor features (safety):
11215 - Add an explicit check to extrainfo_parse_entry_from_string() for
11216 NULL inputs. We don't believe this can actually happen, but it may
11217 help silence a warning from the Clang analyzer. Closes
11220 o Minor features (testing):
11221 - Add more tests for compression backend initialization. Closes
11223 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
11224 When Tor is compiled with this option, we disable a number of
11225 redundant memory-safety failsafes that are intended to stop bugs
11226 from becoming security issues. This makes it easier to hunt for
11227 bugs that would be security issues without the failsafes turned
11228 on. Closes ticket 21439.
11229 - Add a general event-tracing instrumentation support to Tor. This
11230 subsystem will enable developers and researchers to add fine-
11231 grained instrumentation to their Tor instances, for use when
11232 examining Tor network performance issues. There are no trace
11233 events yet, and event-tracing is off by default unless enabled at
11234 compile time. Implements ticket 13802.
11235 - Improve our version parsing tests: add tests for typical version
11236 components, add tests for invalid versions, including numeric
11237 range and non-numeric prefixes. Unit tests 21278, 21450, and
11238 21507. Partially implements 21470.
11240 o Minor bugfixes (bandwidth accounting):
11241 - Roll over monthly accounting at the configured hour and minute,
11242 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11243 Found by Andrey Karpov with PVS-Studio.
11245 o Minor bugfixes (code correctness):
11246 - Accurately identify client connections by their lack of peer
11247 authentication. This means that we bail out earlier if asked to
11248 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
11251 o Minor bugfixes (compilation warnings):
11252 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
11253 22915; bugfix on 0.2.8.1-alpha.
11254 - Fix warnings when building with libscrypt and openssl scrypt
11255 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11256 - When building with certain versions of the mingw C header files,
11257 avoid float-conversion warnings when calling the C functions
11258 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11261 o Minor bugfixes (compilation):
11262 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
11263 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11265 o Minor bugfixes (compression):
11266 - When spooling compressed data to an output buffer, don't try to
11267 spool more data when there is no more data to spool and we are not
11268 trying to flush the input. Previously, we would sometimes launch
11269 compression requests with nothing to do, which interferes with our
11270 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
11272 o Minor bugfixes (configuration):
11273 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11274 bug 22252; bugfix on 0.2.9.3-alpha.
11276 o Minor bugfixes (connection lifespan):
11277 - Allow more control over how long TLS connections are kept open:
11278 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
11279 single option called CircuitsAvailableTimeout. Also, allow the
11280 consensus to control the default values for both this preference
11281 and the lifespan of relay-to-relay connections. Fixes bug 17592;
11282 bugfix on 0.2.5.5-alpha.
11283 - Increase the initial circuit build timeout testing frequency, to
11284 help ensure that ReducedConnectionPadding clients finish learning
11285 a timeout before their orconn would expire. The initial testing
11286 rate was set back in the days of TAP and before the Tor Browser
11287 updater, when we had to be much more careful about new clients
11288 making lots of circuits. With this change, a circuit build timeout
11289 is learned in about 15-20 minutes, instead of 100-120 minutes.
11291 o Minor bugfixes (controller):
11292 - Do not crash when receiving a HSPOST command with an empty body.
11293 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11294 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
11295 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11296 - GETINFO onions/current and onions/detached no longer respond with
11297 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
11298 - Trigger HS descriptor events on the control port when the client
11299 fails to pick a hidden service directory for a hidden service.
11300 This can happen if all the hidden service directories are in
11301 ExcludeNodes, or they have all been queried within the last 15
11302 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
11304 o Minor bugfixes (correctness):
11305 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11306 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11308 o Minor bugfixes (coverity build support):
11309 - Avoid Coverity build warnings related to our BUG() macro. By
11310 default, Coverity treats BUG() as the Linux kernel does: an
11311 instant abort(). We need to override that so our BUG() macro
11312 doesn't prevent Coverity from analyzing functions that use it.
11313 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11315 o Minor bugfixes (defensive programming):
11316 - Detect and break out of infinite loops in our compression code. We
11317 don't think that any such loops exist now, but it's best to be
11318 safe. Closes ticket 22672.
11319 - Fix a memset() off the end of an array when packing cells. This
11320 bug should be harmless in practice, since the corrupted bytes are
11321 still in the same structure, and are always padding bytes,
11322 ignored, or immediately overwritten, depending on compiler
11323 behavior. Nevertheless, because the memset()'s purpose is to make
11324 sure that any other cell-handling bugs can't expose bytes to the
11325 network, we need to fix it. Fixes bug 22737; bugfix on
11326 0.2.4.11-alpha. Fixes CID 1401591.
11328 o Minor bugfixes (directory authority):
11329 - When a directory authority rejects a descriptor or extrainfo with
11330 a given digest, mark that digest as undownloadable, so that we do
11331 not attempt to download it again over and over. We previously
11332 tried to avoid downloading such descriptors by other means, but we
11333 didn't notice if we accidentally downloaded one anyway. This
11334 behavior became problematic in 0.2.7.2-alpha, when authorities
11335 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11337 - When rejecting a router descriptor for running an obsolete version
11338 of Tor without ntor support, warn about the obsolete tor version,
11339 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11340 - Prevent the shared randomness subsystem from asserting when
11341 initialized by a bridge authority with an incomplete configuration
11342 file. Fixes bug 21586; bugfix on 0.2.9.8.
11344 o Minor bugfixes (error reporting, windows):
11345 - When formatting Windows error messages, use the English format to
11346 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
11349 o Minor bugfixes (exit-side DNS):
11350 - Fix an untriggerable assertion that checked the output of a
11351 libevent DNS error, so that the assertion actually behaves as
11352 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
11353 Karpov using PVS-Studio.
11355 o Minor bugfixes (fallback directories):
11356 - Make the usage example in updateFallbackDirs.py actually work, and
11357 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
11358 - Decrease the guard flag average required to be a fallback. This
11359 allows us to keep relays that have their guard flag removed when
11360 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11361 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
11362 bugfix on 0.2.8.1-alpha.
11363 - Make sure fallback directory mirrors have the same address, port,
11364 and relay identity key for at least 30 days before they are
11365 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11367 o Minor bugfixes (file limits, osx):
11368 - When setting the maximum number of connections allowed by the OS,
11369 always allow some extra file descriptors for other files. Fixes
11370 bug 22797; bugfix on 0.2.0.10-alpha.
11372 o Minor bugfixes (hidden services):
11373 - Increase the number of circuits that a service is allowed to
11374 open over a specific period of time. The value was lower than it
11375 should be (8 vs 12) in the normal case of 3 introduction points.
11376 Fixes bug 22159; bugfix on 0.3.0.5-rc.
11377 - Fix a BUG warning during HSv3 descriptor decoding that could be
11378 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
11379 on 0.3.0.1-alpha. Bug found by "haxxpop".
11380 - Stop printing a cryptic warning when a hidden service gets a
11381 request to connect to a virtual port that it hasn't configured.
11382 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
11383 - Simplify hidden service descriptor creation by using an existing
11384 flag to check if an introduction point is established. Fixes bug
11385 21599; bugfix on 0.2.7.2-alpha.
11387 o Minor bugfixes (link handshake):
11388 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11389 months, and regenerate it when it is within one month of expiring.
11390 Previously, we had generated this certificate at startup with a
11391 ten-year lifetime, but that could lead to weird behavior when Tor
11392 was started with a grossly inaccurate clock. Mitigates bug 22466;
11393 mitigation on 0.3.0.1-alpha.
11395 o Minor bugfixes (linux seccomp2 sandbox):
11396 - Avoid a sandbox failure when trying to re-bind to a socket and
11397 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11398 - Permit the fchmod system call, to avoid crashing on startup when
11399 starting with the seccomp2 sandbox and an unexpected set of
11400 permissions on the data directory or its contents. Fixes bug
11401 22516; bugfix on 0.2.5.4-alpha.
11403 o Minor bugfixes (logging):
11404 - When decompressing, do not warn if we fail to decompress using a
11405 compression method that we merely guessed. Fixes part of bug
11406 22670; bugfix on 0.1.1.14-alpha.
11407 - When decompressing, treat mismatch between content-encoding and
11408 actual compression type as a protocol warning. Fixes part of bug
11409 22670; bugfix on 0.1.1.9-alpha.
11410 - Downgrade "assigned_to_cpuworker failed" message to info-level
11411 severity. In every case that can reach it, either a better warning
11412 has already been logged, or no warning is warranted. Fixes bug
11413 22356; bugfix on 0.2.6.3-alpha.
11414 - Log a better message when a directory authority replies to an
11415 upload with an unexpected status code. Fixes bug 11121; bugfix
11417 - Downgrade a log statement about unexpected relay cells from "bug"
11418 to "protocol warning", because there is at least one use case
11419 where it can be triggered by a buggy tor implementation. Fixes bug
11420 21293; bugfix on 0.1.1.14-alpha.
11422 o Minor bugfixes (logging, relay):
11423 - Remove a forgotten debugging message when an introduction point
11424 successfully establishes a hidden service prop224 circuit with
11426 - Change three other log_warn() for an introduction point to
11427 protocol warnings, because they can be failure from the network
11428 and are not relevant to the operator. Fixes bug 23078; bugfix on
11429 0.3.0.1-alpha and 0.3.0.2-alpha.
11431 o Minor bugfixes (relay):
11432 - Inform the geoip and rephist modules about all requests, even on
11433 relays that are only fetching microdescriptors. Fixes a bug
11434 related to 21585; bugfix on 0.3.0.1-alpha.
11436 o Minor bugfixes (memory leaks):
11437 - Fix a small memory leak at exit from the backtrace handler code.
11438 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
11439 - When directory authorities reject a router descriptor due to
11440 keypinning, free the router descriptor rather than leaking the
11441 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11442 - Fix a small memory leak when validating a configuration that uses
11443 two or more AF_UNIX sockets for the same port type. Fixes bug
11444 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
11446 o Minor bugfixes (process behavior):
11447 - When exiting because of an error, always exit with a nonzero exit
11448 status. Previously, we would fail to report an error in our exit
11449 status in cases related to __OwningControllerProcess failure,
11450 lockfile contention, and Ed25519 key initialization. Fixes bug
11451 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
11452 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
11455 o Minor bugfixes (robustness, error handling):
11456 - Improve our handling of the cases where OpenSSL encounters a
11457 memory error while encoding keys and certificates. We haven't
11458 observed these errors in the wild, but if they do happen, we now
11459 detect and respond better. Fixes bug 19418; bugfix on all versions
11460 of Tor. Reported by Guido Vranken.
11462 o Minor bugfixes (testing):
11463 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11464 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11465 - Use unbuffered I/O for utility functions around the
11466 process_handle_t type. This fixes unit test failures reported on
11467 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
11468 - Make display of captured unit test log messages consistent. Fixes
11469 bug 21510; bugfix on 0.2.9.3-alpha.
11470 - Make test-network.sh always call chutney's test-network.sh.
11471 Previously, this only worked on systems which had bash installed,
11472 due to some bash-specific code in the script. Fixes bug 19699;
11473 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
11474 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11475 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11476 - The unit tests now pass on systems where localhost is misconfigured
11477 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
11480 o Minor bugfixes (voting consistency):
11481 - Reject version numbers with non-numeric prefixes (such as +, -, or
11482 whitespace). Disallowing whitespace prevents differential version
11483 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11484 and part of 21508; bugfix on 0.0.8pre1.
11486 o Minor bugfixes (Windows service):
11487 - When running as a Windows service, set the ID of the main thread
11488 correctly. Failure to do so made us fail to send log messages to
11489 the controller in 0.2.1.16-rc, slowed down controller event
11490 delivery in 0.2.7.3-rc and later, and crash with an assertion
11491 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11492 Patch and diagnosis from "Vort".
11494 o Minor bugfixes (windows, relay):
11495 - Resolve "Failure from drain_fd: No error" warnings on Windows
11496 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
11498 o Code simplification and refactoring:
11499 - Break up the 630-line function connection_dir_client_reached_eof()
11500 into a dozen smaller functions. This change should help
11501 maintainability and readability of the client directory code.
11502 - Isolate our use of the openssl headers so that they are only
11503 included from our crypto wrapper modules, and from tests that
11504 examine those modules' internals. Closes ticket 21841.
11505 - Simplify our API to launch directory requests, making it more
11506 extensible and less error-prone. Now it's easier to add extra
11507 headers to directory requests. Closes ticket 21646.
11508 - Our base64 decoding functions no longer overestimate the output
11509 space that they need when parsing unpadded inputs. Closes
11511 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
11512 Resolves ticket 22213.
11513 - The logic that directory caches use to spool request to clients,
11514 serving them one part at a time so as not to allocate too much
11515 memory, has been refactored for consistency. Previously there was
11516 a separate spooling implementation per type of spoolable data. Now
11517 there is one common spooling implementation, with extensible data
11518 types. Closes ticket 21651.
11519 - Tor's compression module now supports multiple backends. Part of
11520 the implementation for proposal 278; closes ticket 21663.
11523 - Add a manpage description for the key-pinning-journal file. Closes
11525 - Correctly note that bandwidth accounting values are stored in the
11526 state file, and the bw_accounting file is now obsolete. Closes
11528 - Document more of the files in the Tor data directory, including
11529 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
11530 approved-routers, sr-random, and diff-cache. Found while fixing
11532 - Clarify the manpage for the (deprecated) torify script. Closes
11534 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
11535 Closes ticket 21873.
11536 - Correct documentation about the default DataDirectory value.
11537 Closes ticket 21151.
11538 - Document the default behavior of NumEntryGuards and
11539 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
11541 - Document key=value pluggable transport arguments for Bridge lines
11542 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
11543 - Note that bandwidth-limiting options don't affect TCP headers or
11544 DNS. Closes ticket 17170.
11546 o Removed features (configuration options, all in ticket 22060):
11547 - These configuration options are now marked Obsolete, and no longer
11548 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
11549 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
11550 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
11551 in 0.2.9.2-alpha and have now been removed. The previous default
11552 behavior is now always chosen; the previous (less secure) non-
11553 default behavior is now unavailable.
11554 - CloseHSClientCircuitsImmediatelyOnTimeout and
11555 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
11556 0.2.9.2-alpha and now have been removed. HS circuits never close
11557 on circuit build timeout; they have a longer timeout period.
11558 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
11559 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
11560 (and others) to configure listen-only and advertise-only addresses.
11562 o Removed features (tools):
11563 - We've removed the tor-checkkey tool from src/tools. Long ago, we
11564 used it to help people detect RSA keys that were generated by
11565 versions of Debian affected by CVE-2008-0166. But those keys have
11566 been out of circulation for ages, and this tool is no longer
11567 required. Closes ticket 21842.
11570 Changes in version 0.3.0.10 - 2017-08-02
11571 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
11572 from the current Tor alpha series. OpenBSD users and TPROXY users
11573 should upgrade; others are probably okay sticking with 0.3.0.9.
11575 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
11576 - Tor's repository now includes a Travis Continuous Integration (CI)
11577 configuration file (.travis.yml). This is meant to help new
11578 developers and contributors who fork Tor to a Github repository be
11579 better able to test their changes, and understand what we expect
11580 to pass. To use this new build feature, you must fork Tor to your
11581 Github account, then go into the "Integrations" menu in the
11582 repository settings for your fork and enable Travis, then push
11583 your changes. Closes ticket 22636.
11585 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11586 - Fix a typo that had prevented TPROXY-based transparent proxying
11587 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11588 Patch from "d4fq0fQAgoJ".
11590 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11591 - Avoid an assertion failure bug affecting our implementation of
11592 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11593 handling of "0xbar" differs from what we had expected. Fixes bug
11594 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11596 o Minor features (backport from 0.3.1.5-alpha):
11597 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11600 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
11601 - Roll over monthly accounting at the configured hour and minute,
11602 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11603 Found by Andrey Karpov with PVS-Studio.
11605 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
11606 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11607 bugfix on 0.2.8.1-alpha.
11608 - Fix warnings when building with libscrypt and openssl scrypt
11609 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11610 - When building with certain versions of the mingw C header files,
11611 avoid float-conversion warnings when calling the C functions
11612 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11615 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11616 - Backport a fix for an "unused variable" warning that appeared
11617 in some versions of mingw. Fixes bug 22838; bugfix on
11620 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
11621 - Avoid Coverity build warnings related to our BUG() macro. By
11622 default, Coverity treats BUG() as the Linux kernel does: an
11623 instant abort(). We need to override that so our BUG() macro
11624 doesn't prevent Coverity from analyzing functions that use it.
11625 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11627 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
11628 - When rejecting a router descriptor for running an obsolete version
11629 of Tor without ntor support, warn about the obsolete tor version,
11630 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11632 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
11633 - Avoid a sandbox failure when trying to re-bind to a socket and
11634 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11636 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
11637 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11638 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11641 Changes in version 0.3.0.9 - 2017-06-29
11642 Tor 0.3.0.9 fixes a path selection bug that would allow a client
11643 to use a guard that was in the same network family as a chosen exit
11644 relay. This is a security regression; all clients running earlier
11645 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
11648 This release also backports several other bugfixes from the 0.3.1.x
11651 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
11652 - When choosing which guard to use for a circuit, avoid the exit's
11653 family along with the exit itself. Previously, the new guard
11654 selection logic avoided the exit, but did not consider its family.
11655 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11656 006 and CVE-2017-0377.
11658 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
11659 - Don't block bootstrapping when a primary bridge is offline and we
11660 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11661 21969; bugfix on 0.3.0.3-alpha.
11663 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
11664 - When starting with an old consensus, do not add new entry guards
11665 unless the consensus is "reasonably live" (under 1 day old). Fixes
11666 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11668 o Minor features (geoip):
11669 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11672 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
11673 - Reject version numbers with non-numeric prefixes (such as +, -, or
11674 whitespace). Disallowing whitespace prevents differential version
11675 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11676 and part of 21508; bugfix on 0.0.8pre1.
11678 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
11679 - Permit the fchmod system call, to avoid crashing on startup when
11680 starting with the seccomp2 sandbox and an unexpected set of
11681 permissions on the data directory or its contents. Fixes bug
11682 22516; bugfix on 0.2.5.4-alpha.
11684 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
11685 - Fix a memset() off the end of an array when packing cells. This
11686 bug should be harmless in practice, since the corrupted bytes are
11687 still in the same structure, and are always padding bytes,
11688 ignored, or immediately overwritten, depending on compiler
11689 behavior. Nevertheless, because the memset()'s purpose is to make
11690 sure that any other cell-handling bugs can't expose bytes to the
11691 network, we need to fix it. Fixes bug 22737; bugfix on
11692 0.2.4.11-alpha. Fixes CID 1401591.
11695 Changes in version 0.3.0.8 - 2017-06-08
11696 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
11697 remotely crash a hidden service with an assertion failure. Anyone
11698 running a hidden service should upgrade to this version, or to some
11699 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11701 Tor 0.3.0.8 also includes fixes for several key management bugs
11702 that sometimes made relays unreliable, as well as several other
11703 bugfixes described below.
11705 o Major bugfixes (hidden service, relay, security, backport
11706 from 0.3.1.3-alpha):
11707 - Fix a remotely triggerable assertion failure when a hidden service
11708 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11709 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11710 - Fix a remotely triggerable assertion failure caused by receiving a
11711 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11712 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11715 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11716 - When performing the v3 link handshake on a TLS connection, report
11717 that we have the x509 certificate that we actually used on that
11718 connection, even if we have changed certificates since that
11719 connection was first opened. Previously, we would claim to have
11720 used our most recent x509 link certificate, which would sometimes
11721 make the link handshake fail. Fixes one case of bug 22460; bugfix
11724 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
11725 - Regenerate link and authentication certificates whenever the key
11726 that signs them changes; also, regenerate link certificates
11727 whenever the signed key changes. Previously, these processes were
11728 only weakly coupled, and we relays could (for minutes to hours)
11729 wind up with an inconsistent set of keys and certificates, which
11730 other relays would not accept. Fixes two cases of bug 22460;
11731 bugfix on 0.3.0.1-alpha.
11732 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11733 send the certificate that matches the x509 certificate that we
11734 used on the TLS connection. Previously, there was a race condition
11735 if the TLS context rotated after we began the TLS handshake but
11736 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11739 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
11740 - Stop rejecting v3 hidden service descriptors because their size
11741 did not match an old padding rule. Fixes bug 22447; bugfix on
11744 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11745 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11746 December 2016 (of which ~126 were still functional) with a list of
11747 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11748 2017. Resolves ticket 21564.
11750 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
11751 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11752 bug 22252; bugfix on 0.2.9.3-alpha.
11754 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11755 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11756 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11758 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
11759 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11760 months, and regenerate it when it is within one month of expiring.
11761 Previously, we had generated this certificate at startup with a
11762 ten-year lifetime, but that could lead to weird behavior when Tor
11763 was started with a grossly inaccurate clock. Mitigates bug 22466;
11764 mitigation on 0.3.0.1-alpha.
11766 o Minor bugfixes (memory leak, directory authority, backport from
11768 - When directory authorities reject a router descriptor due to
11769 keypinning, free the router descriptor rather than leaking the
11770 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11773 Changes in version 0.2.9.11 - 2017-06-08
11774 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
11775 remotely crash a hidden service with an assertion failure. Anyone
11776 running a hidden service should upgrade to this version, or to some
11777 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11778 are not affected by TROVE-2017-004.)
11780 Tor 0.2.9.11 also backports fixes for several key management bugs
11781 that sometimes made relays unreliable, as well as several other
11782 bugfixes described below.
11784 o Major bugfixes (hidden service, relay, security, backport
11785 from 0.3.1.3-alpha):
11786 - Fix a remotely triggerable assertion failure caused by receiving a
11787 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11788 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11791 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11792 - When performing the v3 link handshake on a TLS connection, report
11793 that we have the x509 certificate that we actually used on that
11794 connection, even if we have changed certificates since that
11795 connection was first opened. Previously, we would claim to have
11796 used our most recent x509 link certificate, which would sometimes
11797 make the link handshake fail. Fixes one case of bug 22460; bugfix
11800 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11801 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11802 December 2016 (of which ~126 were still functional) with a list of
11803 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11804 2017. Resolves ticket 21564.
11806 o Minor features (future-proofing, backport from 0.3.0.7):
11807 - Tor no longer refuses to download microdescriptors or descriptors if
11808 they are listed as "published in the future". This change will
11809 eventually allow us to stop listing meaningful "published" dates
11810 in microdescriptor consensuses, and thereby allow us to reduce the
11811 resources required to download consensus diffs by over 50%.
11812 Implements part of ticket 21642; implements part of proposal 275.
11814 o Minor features (directory authorities, backport from 0.3.0.4-rc)
11815 - Directory authorities now reject relays running versions
11816 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
11817 suffer from bug 20499 and don't keep their consensus cache
11818 up-to-date. Resolves ticket 20509.
11820 o Minor features (geoip):
11821 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11824 o Minor bugfixes (control port, backport from 0.3.0.6):
11825 - The GETINFO extra-info/digest/<digest> command was broken because
11826 of a wrong base16 decode return value check, introduced when
11827 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11829 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11830 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11831 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11833 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
11834 - The getpid() system call is now permitted under the Linux seccomp2
11835 sandbox, to avoid crashing with versions of OpenSSL (and other
11836 libraries) that attempt to learn the process's PID by using the
11837 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11840 o Minor bugfixes (memory leak, directory authority, backport
11841 from 0.3.1.2-alpha):
11842 - When directory authorities reject a router descriptor due to
11843 keypinning, free the router descriptor rather than leaking the
11844 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11846 Changes in version 0.2.8.14 - 2017-06-08
11847 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11848 remotely crash a hidden service with an assertion failure. Anyone
11849 running a hidden service should upgrade to this version, or to some
11850 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11851 are not affected by TROVE-2017-004.)
11853 o Major bugfixes (hidden service, relay, security):
11854 - Fix a remotely triggerable assertion failure caused by receiving a
11855 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11856 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11859 o Minor features (geoip):
11860 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11863 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11864 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11865 December 2016 (of which ~126 were still functional) with a list of
11866 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11867 2017. Resolves ticket 21564.
11869 o Minor bugfixes (correctness):
11870 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11871 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11873 Changes in version 0.2.7.8 - 2017-06-08
11874 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11875 remotely crash a hidden service with an assertion failure. Anyone
11876 running a hidden service should upgrade to this version, or to some
11877 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11878 are not affected by TROVE-2017-004.)
11880 o Major bugfixes (hidden service, relay, security):
11881 - Fix a remotely triggerable assertion failure caused by receiving a
11882 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11883 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11886 o Minor features (geoip):
11887 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11890 o Minor bugfixes (correctness):
11891 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11892 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11895 Changes in version 0.2.6.12 - 2017-06-08
11896 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
11897 remotely crash a hidden service with an assertion failure. Anyone
11898 running a hidden service should upgrade to this version, or to some
11899 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11900 are not affected by TROVE-2017-004.)
11902 o Major bugfixes (hidden service, relay, security):
11903 - Fix a remotely triggerable assertion failure caused by receiving a
11904 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11905 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11908 o Minor features (geoip):
11909 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11912 o Minor bugfixes (correctness):
11913 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11914 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11916 Changes in version 0.2.5.14 - 2017-06-08
11917 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
11918 remotely crash a hidden service with an assertion failure. Anyone
11919 running a hidden service should upgrade to this version, or to some
11920 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11921 are not affected by TROVE-2017-004.)
11923 o Major bugfixes (hidden service, relay, security):
11924 - Fix a remotely triggerable assertion failure caused by receiving a
11925 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11926 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11929 o Minor features (geoip):
11930 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11933 o Minor bugfixes (correctness):
11934 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11935 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11937 Changes in version 0.2.4.29 - 2017-06-08
11938 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
11939 remotely crash a hidden service with an assertion failure. Anyone
11940 running a hidden service should upgrade to this version, or to some
11941 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11942 are not affected by TROVE-2017-004.)
11944 o Major bugfixes (hidden service, relay, security):
11945 - Fix a remotely triggerable assertion failure caused by receiving a
11946 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11947 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11950 o Minor features (geoip):
11951 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11954 o Minor bugfixes (correctness):
11955 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11956 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11959 Changes in version 0.3.0.7 - 2017-05-15
11960 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
11961 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
11962 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
11963 clients are not affected.
11965 o Major bugfixes (hidden service directory, security):
11966 - Fix an assertion failure in the hidden service directory code, which
11967 could be used by an attacker to remotely cause a Tor relay process to
11968 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
11969 should upgrade. This security issue is tracked as TROVE-2017-002.
11970 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
11973 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11976 o Minor features (future-proofing):
11977 - Tor no longer refuses to download microdescriptors or descriptors
11978 if they are listed as "published in the future". This change will
11979 eventually allow us to stop listing meaningful "published" dates
11980 in microdescriptor consensuses, and thereby allow us to reduce the
11981 resources required to download consensus diffs by over 50%.
11982 Implements part of ticket 21642; implements part of proposal 275.
11984 o Minor bugfixes (Linux seccomp2 sandbox):
11985 - The getpid() system call is now permitted under the Linux seccomp2
11986 sandbox, to avoid crashing with versions of OpenSSL (and other
11987 libraries) that attempt to learn the process's PID by using the
11988 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11992 Changes in version 0.3.0.6 - 2017-04-26
11993 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
11995 With the 0.3.0 series, clients and relays now use Ed25519 keys to
11996 authenticate their link connections to relays, rather than the old
11997 RSA1024 keys that they used before. (Circuit crypto has been
11998 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
11999 the guard selection and replacement algorithm to behave more robustly
12000 in the presence of unreliable networks, and to resist guard-
12003 This series also includes numerous other small features and bugfixes,
12004 along with more groundwork for the upcoming hidden-services revamp.
12006 Per our stable release policy, we plan to support the Tor 0.3.0
12007 release series for at least the next nine months, or for three months
12008 after the first stable release of the 0.3.1 series: whichever is
12009 longer. If you need a release with long-term support, we recommend
12010 that you stay with the 0.2.9 series.
12012 Below are the changes since 0.2.9.10. For a list of only the changes
12013 since 0.3.0.5-rc, see the ChangeLog file.
12015 o Major features (directory authority, security):
12016 - The default for AuthDirPinKeys is now 1: directory authorities
12017 will reject relays where the RSA identity key matches a previously
12018 seen value, but the Ed25519 key has changed. Closes ticket 18319.
12020 o Major features (guard selection algorithm):
12021 - Tor's guard selection algorithm has been redesigned from the
12022 ground up, to better support unreliable networks and restrictive
12023 sets of entry nodes, and to better resist guard-capture attacks by
12024 hostile local networks. Implements proposal 271; closes
12027 o Major features (next-generation hidden services):
12028 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
12029 prop224 aka "Next Generation Hidden Services". Service and clients
12030 don't use this functionality yet. Closes ticket 19043. Based on
12031 initial code by Alec Heifetz.
12032 - Relays now support the HSDir version 3 protocol, so that they can
12033 can store and serve v3 descriptors. This is part of the next-
12034 generation onion service work detailed in proposal 224. Closes
12037 o Major features (protocol, ed25519 identity keys):
12038 - Clients now support including Ed25519 identity keys in the EXTEND2
12039 cells they generate. By default, this is controlled by a consensus
12040 parameter, currently disabled. You can turn this feature on for
12041 testing by setting ExtendByEd25519ID in your configuration. This
12042 might make your traffic appear different than the traffic
12043 generated by other users, however. Implements part of ticket
12044 15056; part of proposal 220.
12045 - Relays now understand requests to extend to other relays by their
12046 Ed25519 identity keys. When an Ed25519 identity key is included in
12047 an EXTEND2 cell, the relay will only extend the circuit if the
12048 other relay can prove ownership of that identity. Implements part
12049 of ticket 15056; part of proposal 220.
12050 - Relays now use Ed25519 to prove their Ed25519 identities and to
12051 one another, and to clients. This algorithm is faster and more
12052 secure than the RSA-based handshake we've been doing until now.
12053 Implements the second big part of proposal 220; Closes
12056 o Major features (security):
12057 - Change the algorithm used to decide DNS TTLs on client and server
12058 side, to better resist DNS-based correlation attacks like the
12059 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
12060 Feamster. Now relays only return one of two possible DNS TTL
12061 values, and clients are willing to believe DNS TTL values up to 3
12062 hours long. Closes ticket 19769.
12064 o Major bugfixes (client, onion service, also in 0.2.9.9):
12065 - Fix a client-side onion service reachability bug, where multiple
12066 socks requests to an onion service (or a single slow request)
12067 could cause us to mistakenly mark some of the service's
12068 introduction points as failed, and we cache that failure so
12069 eventually we run out and can't reach the service. Also resolves a
12070 mysterious "Remote server sent bogus reason code 65021" log
12071 warning. The bug was introduced in ticket 17218, where we tried to
12072 remember the circuit end reason as a uint16_t, which mangled
12073 negative values. Partially fixes bug 21056 and fixes bug 20307;
12074 bugfix on 0.2.8.1-alpha.
12076 o Major bugfixes (crash, directory connections):
12077 - Fix a rare crash when sending a begin cell on a circuit whose
12078 linked directory connection had already been closed. Fixes bug
12079 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
12081 o Major bugfixes (directory authority):
12082 - During voting, when marking a relay as a probable sybil, do not
12083 clear its BadExit flag: sybils can still be bad in other ways
12084 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12087 o Major bugfixes (DNS):
12088 - Fix a bug that prevented exit nodes from caching DNS records for
12089 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
12091 o Major bugfixes (IPv6 Exits):
12092 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12093 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12094 exit policy rejects that port on more than an IPv6 /16 of
12095 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12096 which rejected a relay's own IPv6 address by default. Fixes bug
12097 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12099 o Major bugfixes (parsing):
12100 - Fix an integer underflow bug when comparing malformed Tor
12101 versions. This bug could crash Tor when built with
12102 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12103 0.2.9.8, which were built with -ftrapv by default. In other cases
12104 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12105 on 0.0.8pre1. Found by OSS-Fuzz.
12106 - When parsing a malformed content-length field from an HTTP
12107 message, do not read off the end of the buffer. This bug was a
12108 potential remote denial-of-service attack against Tor clients and
12109 relays. A workaround was released in October 2016, to prevent this
12110 bug from crashing Tor. This is a fix for the underlying issue,
12111 which should no longer matter (if you applied the earlier patch).
12112 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
12113 using AFL (http://lcamtuf.coredump.cx/afl/).
12115 o Major bugfixes (scheduler):
12116 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
12117 caused the channel scheduler to behave more or less randomly,
12118 rather than preferring channels with higher-priority circuits.
12119 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
12121 o Major bugfixes (security, also in 0.2.9.9):
12122 - Downgrade the "-ftrapv" option from "always on" to "only on when
12123 --enable-expensive-hardening is provided." This hardening option,
12124 like others, can turn survivable bugs into crashes--and having it
12125 on by default made a (relatively harmless) integer overflow bug
12126 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
12127 bugfix on 0.2.9.1-alpha.
12129 o Minor feature (client):
12130 - Enable IPv6 traffic on the SocksPort by default. To disable this,
12131 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
12133 o Minor feature (fallback scripts):
12134 - Add a check_existing mode to updateFallbackDirs.py, which checks
12135 if fallbacks in the hard-coded list are working. Closes ticket
12136 20174. Patch by haxxpop.
12138 o Minor feature (protocol versioning):
12139 - Add new protocol version for proposal 224. HSIntro now advertises
12140 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
12142 o Minor features (ciphersuite selection):
12143 - Allow relays to accept a wider range of ciphersuites, including
12144 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
12145 - Clients now advertise a list of ciphersuites closer to the ones
12146 preferred by Firefox. Closes part of ticket 15426.
12148 o Minor features (controller):
12149 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
12150 shared-random values to the controller. Closes ticket 19925.
12151 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
12152 rather than "unrecognized." Closes ticket 20389; patch from
12155 o Minor features (controller, configuration):
12156 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
12157 and so on, now comes with a __*Port variant that will not be saved
12158 to the torrc file by the controller's SAVECONF command. This
12159 change allows TorBrowser to set up a single-use domain socket for
12160 each time it launches Tor. Closes ticket 20956.
12161 - The GETCONF command can now query options that may only be
12162 meaningful in context-sensitive lists. This allows the controller
12163 to query the mixed SocksPort/__SocksPort style options introduced
12164 in feature 20956. Implements ticket 21300.
12166 o Minor features (diagnostic, directory client):
12167 - Warn when we find an unexpected inconsistency in directory
12168 download status objects. Prevents some negative consequences of
12171 o Minor features (directory authorities):
12172 - Directory authorities now reject descriptors that claim to be
12173 malformed versions of Tor. Helps prevent exploitation of
12175 - Reject version numbers with components that exceed INT32_MAX.
12176 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12177 Fixes bug 21450; bugfix on 0.0.8pre1.
12179 o Minor features (directory authority):
12180 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
12181 default) to control whether authorities should try to probe relays
12182 by their Ed25519 link keys. This option will go away in a few
12183 releases--unless we encounter major trouble in our ed25519 link
12184 protocol rollout, in which case it will serve as a safety option.
12186 o Minor features (directory cache):
12187 - Relays and bridges will now refuse to serve the consensus they
12188 have if they know it is too old for a client to use. Closes
12191 o Minor features (ed25519 link handshake):
12192 - Advertise support for the ed25519 link handshake using the
12193 subprotocol-versions mechanism, so that clients can tell which
12194 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
12196 o Minor features (entry guards):
12197 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
12198 break regression tests.
12199 - Require UseEntryGuards when UseBridges is set, in order to make
12200 sure bridges aren't bypassed. Resolves ticket 20502.
12202 o Minor features (fallback directories):
12203 - Allow 3 fallback relays per operator, which is safe now that we
12204 are choosing 200 fallback relays. Closes ticket 20912.
12205 - Annotate updateFallbackDirs.py with the bandwidth and consensus
12206 weight for each candidate fallback. Closes ticket 20878.
12207 - Display the relay fingerprint when downloading consensuses from
12208 fallbacks. Closes ticket 20908.
12209 - Exclude relays affected by bug 20499 from the fallback list.
12210 Exclude relays from the fallback list if they are running versions
12211 known to be affected by bug 20499, or if in our tests they deliver
12212 a stale consensus (i.e. one that expired more than 24 hours ago).
12213 Closes ticket 20539.
12214 - Make it easier to change the output sort order of fallbacks.
12215 Closes ticket 20822.
12216 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
12218 - Require fallback directories to have the same address and port for
12219 7 days (now that we have enough relays with this stability).
12220 Relays whose OnionOO stability timer is reset on restart by bug
12221 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
12222 this issue. Closes ticket 20880; maintains short-term fix
12224 - Require fallbacks to have flags for 90% of the time (weighted
12225 decaying average), rather than 95%. This allows at least 73% of
12226 clients to bootstrap in the first 5 seconds without contacting an
12227 authority. Part of ticket 18828.
12228 - Select 200 fallback directories for each release. Closes
12231 o Minor features (fingerprinting resistance, authentication):
12232 - Extend the length of RSA keys used for TLS link authentication to
12233 2048 bits. (These weren't used for forward secrecy; for forward
12234 secrecy, we used P256.) Closes ticket 13752.
12236 o Minor features (geoip):
12237 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
12240 o Minor features (geoip, also in 0.2.9.9):
12241 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
12244 o Minor features (infrastructure):
12245 - Implement smartlist_add_strdup() function. Replaces the use of
12246 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
12248 o Minor features (linting):
12249 - Enhance the changes file linter to warn on Tor versions that are
12250 prefixed with "tor-". Closes ticket 21096.
12252 o Minor features (logging):
12253 - In several places, describe unset ed25519 keys as "<unset>",
12254 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
12256 o Minor features (portability, compilation):
12257 - Autoconf now checks to determine if OpenSSL structures are opaque,
12258 instead of explicitly checking for OpenSSL version numbers. Part
12260 - Support building with recent LibreSSL code that uses opaque
12261 structures. Closes ticket 21359.
12263 o Minor features (relay):
12264 - We now allow separation of exit and relay traffic to different
12265 source IP addresses, using the OutboundBindAddressExit and
12266 OutboundBindAddressOR options respectively. Closes ticket 17975.
12267 Written by Michael Sonntag.
12269 o Minor features (reliability, crash):
12270 - Try better to detect problems in buffers where they might grow (or
12271 think they have grown) over 2 GB in size. Diagnostic for
12274 o Minor features (testing):
12275 - During 'make test-network-all', if tor logs any warnings, ask
12276 chutney to output them. Requires a recent version of chutney with
12277 the 21572 patch. Implements 21570.
12279 o Minor bugfix (control protocol):
12280 - The reply to a "GETINFO config/names" request via the control
12281 protocol now spells the type "Dependent" correctly. This is a
12282 breaking change in the control protocol. (The field seems to be
12283 ignored by the most common known controllers.) Fixes bug 18146;
12284 bugfix on 0.1.1.4-alpha.
12285 - The GETINFO extra-info/digest/<digest> command was broken because
12286 of a wrong base16 decode return value check, introduced when
12287 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12289 o Minor bugfix (logging):
12290 - Don't recommend the use of Tor2web in non-anonymous mode.
12291 Recommending Tor2web is a bad idea because the client loses all
12292 anonymity. Tor2web should only be used in specific cases by users
12293 who *know* and understand the issues. Fixes bug 21294; bugfix
12296 o Minor bugfixes (bug resilience):
12297 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
12298 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
12299 Hans Jerry Illikainen.
12301 o Minor bugfixes (build):
12302 - Replace obsolete Autoconf macros with their modern equivalent and
12303 prevent similar issues in the future. Fixes bug 20990; bugfix
12306 o Minor bugfixes (certificate expiration time):
12307 - Avoid using link certificates that don't become valid till some
12308 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
12310 o Minor bugfixes (client):
12311 - Always recover from failures in extend_info_from_node(), in an
12312 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
12313 bugfix on 0.2.3.1-alpha.
12314 - When clients that use bridges start up with a cached consensus on
12315 disk, they were ignoring it and downloading a new one. Now they
12316 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
12318 o Minor bugfixes (code correctness):
12319 - Repair a couple of (unreachable or harmless) cases of the risky
12320 comparison-by-subtraction pattern that caused bug 21278.
12322 o Minor bugfixes (config):
12323 - Don't assert on startup when trying to get the options list and
12324 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
12325 options so of course they aren't ready yet. Fixes bug 21062;
12326 bugfix on 0.2.9.3-alpha.
12328 o Minor bugfixes (configuration):
12329 - Accept non-space whitespace characters after the severity level in
12330 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
12331 - Support "TByte" and "TBytes" units in options given in bytes.
12332 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
12333 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
12335 o Minor bugfixes (configure, autoconf):
12336 - Rename the configure option --enable-expensive-hardening to
12337 --enable-fragile-hardening. Expensive hardening makes the tor
12338 daemon abort when some kinds of issues are detected. Thus, it
12339 makes tor more at risk of remote crashes but safer against RCE or
12340 heartbleed bug category. We now try to explain this issue in a
12341 message from the configure script. Fixes bug 21290; bugfix
12344 o Minor bugfixes (consensus weight):
12345 - Add new consensus method that initializes bw weights to 1 instead
12346 of 0. This prevents a zero weight from making it all the way to
12347 the end (happens in small testing networks) and causing an error.
12348 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
12350 o Minor bugfixes (crash prevention):
12351 - Fix an (currently untriggerable, but potentially dangerous) crash
12352 bug when base32-encoding inputs whose sizes are not a multiple of
12353 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
12355 o Minor bugfixes (dead code):
12356 - Remove a redundant check for PidFile changes at runtime in
12357 options_transition_allowed(): this check is already performed
12358 regardless of whether the sandbox is active. Fixes bug 21123;
12359 bugfix on 0.2.5.4-alpha.
12361 o Minor bugfixes (descriptors):
12362 - Correctly recognise downloaded full descriptors as valid, even
12363 when using microdescriptors as circuits. This affects clients with
12364 FetchUselessDescriptors set, and may affect directory authorities.
12365 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
12367 o Minor bugfixes (directory mirrors):
12368 - Allow relays to use directory mirrors without a DirPort: these
12369 relays need to be contacted over their ORPorts using a begindir
12370 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
12371 - Clarify the message logged when a remote relay is unexpectedly
12372 missing an ORPort or DirPort: users were confusing this with a
12373 local port. Fixes another case of bug 20711; bugfix
12376 o Minor bugfixes (directory system):
12377 - Bridges and relays now use microdescriptors (like clients do)
12378 rather than old-style router descriptors. Now bridges will blend
12379 in with clients in terms of the circuits they build. Fixes bug
12380 6769; bugfix on 0.2.3.2-alpha.
12381 - Download all consensus flavors, descriptors, and authority
12382 certificates when FetchUselessDescriptors is set, regardless of
12383 whether tor is a directory cache or not. Fixes bug 20667; bugfix
12384 on all recent tor versions.
12386 o Minor bugfixes (documentation):
12387 - Update the tor manual page to document every option that can not
12388 be changed while tor is running. Fixes bug 21122.
12390 o Minor bugfixes (ed25519 certificates):
12391 - Correctly interpret ed25519 certificates that would expire some
12392 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
12394 o Minor bugfixes (fallback directories):
12395 - Avoid checking fallback candidates' DirPorts if they are down in
12396 OnionOO. When a relay operator has multiple relays, this
12397 prioritizes relays that are up over relays that are down. Fixes
12398 bug 20926; bugfix on 0.2.8.3-alpha.
12399 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
12400 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
12401 - Stop failing when a relay has no uptime data in
12402 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
12404 o Minor bugfixes (hidden service):
12405 - Clean up the code for expiring intro points with no associated
12406 circuits. It was causing, rarely, a service with some expiring
12407 introduction points to not open enough additional introduction
12408 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
12409 - Resolve two possible underflows which could lead to creating and
12410 closing a lot of introduction point circuits in a non-stop loop.
12411 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
12412 - Stop setting the torrc option HiddenServiceStatistics to "0" just
12413 because we're not a bridge or relay. Instead, we preserve whatever
12414 value the user set (or didn't set). Fixes bug 21150; bugfix
12417 o Minor bugfixes (hidden services):
12418 - Make hidden services check for failed intro point connections,
12419 even when they have exceeded their intro point creation limit.
12420 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
12421 - Make hidden services with 8 to 10 introduction points check for
12422 failed circuits immediately after startup. Previously, they would
12423 wait for 5 minutes before performing their first checks. Fixes bug
12424 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
12425 - Stop ignoring misconfigured hidden services. Instead, refuse to
12426 start tor until the misconfigurations have been corrected. Fixes
12427 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
12430 o Minor bugfixes (IPv6):
12431 - Make IPv6-using clients try harder to find an IPv6 directory
12432 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
12433 - When IPv6 addresses have not been downloaded yet (microdesc
12434 consensus documents don't list relay IPv6 addresses), use hard-
12435 coded addresses for authorities, fallbacks, and configured
12436 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
12437 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
12439 o Minor bugfixes (memory leak at exit):
12440 - Fix a small harmless memory leak at exit of the previously unused
12441 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
12444 o Minor bugfixes (onion services):
12445 - Allow the number of introduction points to be as low as 0, rather
12446 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
12448 o Minor bugfixes (portability):
12449 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
12450 It is supported by OpenBSD itself, and also by most OpenBSD
12451 variants (such as Bitrig). Fixes bug 20980; bugfix
12454 o Minor bugfixes (portability, also in 0.2.9.9):
12455 - Avoid crashing when Tor is built using headers that contain
12456 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
12457 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
12459 - Fix Libevent detection on platforms without Libevent 1 headers
12460 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
12462 o Minor bugfixes (relay):
12463 - Avoid a double-marked-circuit warning that could happen when we
12464 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12466 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
12467 initializing the keys would reset the DataDirectory to 0700
12468 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
12469 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
12471 o Minor bugfixes (testing):
12472 - Fix Raspbian build issues related to missing socket errno in
12473 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
12474 - Remove undefined behavior from the backtrace generator by removing
12475 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
12476 - Use bash in src/test/test-network.sh. This ensures we reliably
12477 call chutney's newer tools/test-network.sh when available. Fixes
12478 bug 21562; bugfix on 0.2.9.1-alpha.
12480 o Minor bugfixes (tor-resolve):
12481 - The tor-resolve command line tool now rejects hostnames over 255
12482 characters in length. Previously, it would silently truncate them,
12483 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12484 Patch by "junglefowl".
12486 o Minor bugfixes (unit tests):
12487 - Allow the unit tests to pass even when DNS lookups of bogus
12488 addresses do not fail as expected. Fixes bug 20862 and 20863;
12489 bugfix on unit tests introduced in 0.2.8.1-alpha
12490 through 0.2.9.4-alpha.
12492 o Minor bugfixes (util):
12493 - When finishing writing a file to disk, if we were about to replace
12494 the file with the temporary file created before and we fail to
12495 replace it, remove the temporary file so it doesn't stay on disk.
12496 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
12498 o Minor bugfixes (Windows services):
12499 - Be sure to initialize the monotonic time subsystem before using
12500 it, even when running as an NT service. Fixes bug 21356; bugfix
12503 o Minor bugfixes (Windows):
12504 - Check for getpagesize before using it to mmap files. This fixes
12505 compilation in some MinGW environments. Fixes bug 20530; bugfix on
12506 0.1.2.1-alpha. Reported by "ice".
12508 o Code simplification and refactoring:
12509 - Abolish all global guard context in entrynodes.c; replace with new
12510 guard_selection_t structure as preparation for proposal 271.
12511 Closes ticket 19858.
12512 - Extract magic numbers in circuituse.c into defined variables.
12513 - Introduce rend_service_is_ephemeral() that tells if given onion
12514 service is ephemeral. Replace unclear NULL-checkings for service
12515 directory with this function. Closes ticket 20526.
12516 - Refactor circuit_is_available_for_use to remove unnecessary check.
12517 - Refactor circuit_predict_and_launch_new for readability and
12518 testability. Closes ticket 18873.
12519 - Refactor code to manipulate global_origin_circuit_list into
12520 separate functions. Closes ticket 20921.
12521 - Refactor large if statement in purpose_needs_anonymity to use
12522 switch statement instead. Closes part of ticket 20077.
12523 - Refactor the hashing API to return negative values for errors, as
12524 is done as throughout the codebase. Closes ticket 20717.
12525 - Remove data structures that were used to index or_connection
12526 objects by their RSA identity digests. These structures are fully
12527 redundant with the similar structures used in the
12528 channel abstraction.
12529 - Remove duplicate code in the channel_write_*cell() functions.
12530 Closes ticket 13827; patch from Pingl.
12531 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
12532 use only purpose_needs_anonymity. Closes part of ticket 20077.
12533 - The code to generate and parse EXTEND and EXTEND2 cells has been
12534 replaced with code automatically generated by the
12537 o Documentation (formatting):
12538 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
12539 blocks were incorrectly appearing. Closes ticket 20885.
12541 o Documentation (man page):
12542 - Clarify many options in tor.1 and add some min/max values for
12543 HiddenService options. Closes ticket 21058.
12546 - Change '1' to 'weight_scale' in consensus bw weights calculation
12547 comments, as that is reality. Closes ticket 20273. Patch
12549 - Clarify that when ClientRejectInternalAddresses is enabled (which
12550 is the default), multicast DNS hostnames for machines on the local
12551 network (of the form *.local) are also rejected. Closes
12553 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
12554 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
12555 - Include the "TBits" unit in Tor's man page. Fixes part of bug
12556 20622; bugfix on 0.2.5.1-alpha.
12557 - Small fixes to the fuzzing documentation. Closes ticket 21472.
12558 - Stop the man page from incorrectly stating that HiddenServiceDir
12559 must already exist. Fixes 20486.
12560 - Update the description of the directory server options in the
12561 manual page, to clarify that a relay no longer needs to set
12562 DirPort in order to be a directory cache. Closes ticket 21720.
12564 o Removed features:
12565 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
12566 limit for relays running on a single IP applies to authority IP
12567 addresses as well as to non-authority IP addresses. Closes
12569 - The UseDirectoryGuards torrc option no longer exists: all users
12570 that use entry guards will also use directory guards. Related to
12571 proposal 271; implements part of ticket 20831.
12574 - Add tests for networkstatus_compute_bw_weights_v10.
12575 - Add unit tests circuit_predict_and_launch_new.
12576 - Extract dummy_origin_circuit_new so it can be used by other
12578 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
12579 from "overcaffeinated".
12580 - Perform the coding style checks when running the tests and fail
12581 when coding style violations are found. Closes ticket 5500.
12584 Changes in version 0.2.8.13 - 2017-03-03
12585 Tor 0.2.8.13 backports a security fix from later Tor
12586 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
12587 this release, if for some reason they cannot upgrade to a later
12588 release series, and if they build Tor with the --enable-expensive-hardening
12591 Note that support for Tor 0.2.8.x is ending next year: we will not issue
12592 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
12593 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12595 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12596 - Fix an integer underflow bug when comparing malformed Tor
12597 versions. This bug could crash Tor when built with
12598 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12599 0.2.9.8, which were built with -ftrapv by default. In other cases
12600 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12601 on 0.0.8pre1. Found by OSS-Fuzz.
12603 o Minor features (geoip):
12604 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12608 Changes in version 0.2.7.7 - 2017-03-03
12609 Tor 0.2.7.7 backports a number of security fixes from later Tor
12610 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
12611 this release, if for some reason they cannot upgrade to a later
12614 Note that support for Tor 0.2.7.x is ending this year: we will not issue
12615 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
12616 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12618 o Directory authority changes (backport from 0.2.8.5-rc):
12619 - Urras is no longer a directory authority. Closes ticket 19271.
12621 o Directory authority changes (backport from 0.2.9.2-alpha):
12622 - The "Tonga" bridge authority has been retired; the new bridge
12623 authority is "Bifroest". Closes tickets 19728 and 19690.
12625 o Directory authority key updates (backport from 0.2.8.1-alpha):
12626 - Update the V3 identity key for the dannenberg directory authority:
12627 it was changed on 18 November 2015. Closes task 17906. Patch
12630 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12631 - Fix a bug in parsing that could cause clients to read a single
12632 byte past the end of an allocated region. This bug could be used
12633 to cause hardened clients (built with --enable-expensive-hardening)
12634 to crash if they tried to visit a hostile hidden service. Non-
12635 hardened clients are only affected depending on the details of
12636 their platform's memory allocator. Fixes bug 21018; bugfix on
12637 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12638 2016-12-002 and as CVE-2016-1254.
12640 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12641 - Stop a crash that could occur when a client running with DNSPort
12642 received a query with multiple address types, and the first
12643 address type was not supported. Found and fixed by Scott Dial.
12644 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12645 - Prevent a class of security bugs caused by treating the contents
12646 of a buffer chunk as if they were a NUL-terminated string. At
12647 least one such bug seems to be present in all currently used
12648 versions of Tor, and would allow an attacker to remotely crash
12649 most Tor instances, especially those compiled with extra compiler
12650 hardening. With this defense in place, such bugs can't crash Tor,
12651 though we should still fix them as they occur. Closes ticket
12652 20384 (TROVE-2016-10-001).
12654 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12655 - Avoid a difficult-to-trigger heap corruption attack when extending
12656 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12657 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12658 Reported by Guido Vranken.
12660 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12661 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12662 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12664 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12665 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12666 pointer to the previous (uninitialized) key value. The impact here
12667 should be limited to a difficult-to-trigger crash, if OpenSSL is
12668 running an engine that makes key generation failures possible, or
12669 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12670 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12673 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12674 - Fix an integer underflow bug when comparing malformed Tor
12675 versions. This bug could crash Tor when built with
12676 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12677 0.2.9.8, which were built with -ftrapv by default. In other cases
12678 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12679 on 0.0.8pre1. Found by OSS-Fuzz.
12681 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12682 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12683 zero size. Check size argument to memwipe() for underflow. Fixes
12684 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12687 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12688 - Make Tor survive errors involving connections without a
12689 corresponding event object. Previously we'd fail with an
12690 assertion; now we produce a log message. Related to bug 16248.
12692 o Minor features (geoip):
12693 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12697 Changes in version 0.2.6.11 - 2017-03-03
12698 Tor 0.2.6.11 backports a number of security fixes from later Tor
12699 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
12700 this release, if for some reason they cannot upgrade to a later
12703 Note that support for Tor 0.2.6.x is ending this year: we will not issue
12704 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
12705 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12707 o Directory authority changes (backport from 0.2.8.5-rc):
12708 - Urras is no longer a directory authority. Closes ticket 19271.
12710 o Directory authority changes (backport from 0.2.9.2-alpha):
12711 - The "Tonga" bridge authority has been retired; the new bridge
12712 authority is "Bifroest". Closes tickets 19728 and 19690.
12714 o Directory authority key updates (backport from 0.2.8.1-alpha):
12715 - Update the V3 identity key for the dannenberg directory authority:
12716 it was changed on 18 November 2015. Closes task 17906. Patch
12719 o Major features (security fixes, backport from 0.2.9.4-alpha):
12720 - Prevent a class of security bugs caused by treating the contents
12721 of a buffer chunk as if they were a NUL-terminated string. At
12722 least one such bug seems to be present in all currently used
12723 versions of Tor, and would allow an attacker to remotely crash
12724 most Tor instances, especially those compiled with extra compiler
12725 hardening. With this defense in place, such bugs can't crash Tor,
12726 though we should still fix them as they occur. Closes ticket
12727 20384 (TROVE-2016-10-001).
12729 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12730 - Fix a bug in parsing that could cause clients to read a single
12731 byte past the end of an allocated region. This bug could be used
12732 to cause hardened clients (built with --enable-expensive-hardening)
12733 to crash if they tried to visit a hostile hidden service. Non-
12734 hardened clients are only affected depending on the details of
12735 their platform's memory allocator. Fixes bug 21018; bugfix on
12736 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12737 2016-12-002 and as CVE-2016-1254.
12739 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12740 - Stop a crash that could occur when a client running with DNSPort
12741 received a query with multiple address types, and the first
12742 address type was not supported. Found and fixed by Scott Dial.
12743 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12745 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12746 - Fix an error that could cause us to read 4 bytes before the
12747 beginning of an openssl string. This bug could be used to cause
12748 Tor to crash on systems with unusual malloc implementations, or
12749 systems with unusual hardening installed. Fixes bug 17404; bugfix
12752 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12753 - Avoid a difficult-to-trigger heap corruption attack when extending
12754 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12755 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12756 Reported by Guido Vranken.
12758 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12759 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12760 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12762 o Major bugfixes (guard selection, backport from 0.2.7.6):
12763 - Actually look at the Guard flag when selecting a new directory
12764 guard. When we implemented the directory guard design, we
12765 accidentally started treating all relays as if they have the Guard
12766 flag during guard selection, leading to weaker anonymity and worse
12767 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12770 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12771 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12772 pointer to the previous (uninitialized) key value. The impact here
12773 should be limited to a difficult-to-trigger crash, if OpenSSL is
12774 running an engine that makes key generation failures possible, or
12775 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12776 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12779 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12780 - Fix an integer underflow bug when comparing malformed Tor
12781 versions. This bug could crash Tor when built with
12782 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12783 0.2.9.8, which were built with -ftrapv by default. In other cases
12784 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12785 on 0.0.8pre1. Found by OSS-Fuzz.
12787 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12788 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12789 zero size. Check size argument to memwipe() for underflow. Fixes
12790 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12793 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12794 - Make Tor survive errors involving connections without a
12795 corresponding event object. Previously we'd fail with an
12796 assertion; now we produce a log message. Related to bug 16248.
12798 o Minor features (geoip):
12799 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12802 o Minor bugfixes (compilation, backport from 0.2.7.6):
12803 - Fix a compilation warning with Clang 3.6: Do not check the
12804 presence of an address which can never be NULL. Fixes bug 17781.
12807 Changes in version 0.2.5.13 - 2017-03-03
12808 Tor 0.2.5.13 backports a number of security fixes from later Tor
12809 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
12810 this release, if for some reason they cannot upgrade to a later
12813 Note that support for Tor 0.2.5.x is ending next year: we will not issue
12814 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
12815 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12817 o Directory authority changes (backport from 0.2.8.5-rc):
12818 - Urras is no longer a directory authority. Closes ticket 19271.
12820 o Directory authority changes (backport from 0.2.9.2-alpha):
12821 - The "Tonga" bridge authority has been retired; the new bridge
12822 authority is "Bifroest". Closes tickets 19728 and 19690.
12824 o Directory authority key updates (backport from 0.2.8.1-alpha):
12825 - Update the V3 identity key for the dannenberg directory authority:
12826 it was changed on 18 November 2015. Closes task 17906. Patch
12829 o Major features (security fixes, backport from 0.2.9.4-alpha):
12830 - Prevent a class of security bugs caused by treating the contents
12831 of a buffer chunk as if they were a NUL-terminated string. At
12832 least one such bug seems to be present in all currently used
12833 versions of Tor, and would allow an attacker to remotely crash
12834 most Tor instances, especially those compiled with extra compiler
12835 hardening. With this defense in place, such bugs can't crash Tor,
12836 though we should still fix them as they occur. Closes ticket
12837 20384 (TROVE-2016-10-001).
12839 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12840 - Fix a bug in parsing that could cause clients to read a single
12841 byte past the end of an allocated region. This bug could be used
12842 to cause hardened clients (built with --enable-expensive-hardening)
12843 to crash if they tried to visit a hostile hidden service. Non-
12844 hardened clients are only affected depending on the details of
12845 their platform's memory allocator. Fixes bug 21018; bugfix on
12846 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12847 2016-12-002 and as CVE-2016-1254.
12849 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12850 - Stop a crash that could occur when a client running with DNSPort
12851 received a query with multiple address types, and the first
12852 address type was not supported. Found and fixed by Scott Dial.
12853 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12855 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12856 - Fix an error that could cause us to read 4 bytes before the
12857 beginning of an openssl string. This bug could be used to cause
12858 Tor to crash on systems with unusual malloc implementations, or
12859 systems with unusual hardening installed. Fixes bug 17404; bugfix
12862 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12863 - Avoid a difficult-to-trigger heap corruption attack when extending
12864 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12865 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12866 Reported by Guido Vranken.
12868 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12869 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12870 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12872 o Major bugfixes (guard selection, backport from 0.2.7.6):
12873 - Actually look at the Guard flag when selecting a new directory
12874 guard. When we implemented the directory guard design, we
12875 accidentally started treating all relays as if they have the Guard
12876 flag during guard selection, leading to weaker anonymity and worse
12877 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12880 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12881 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12882 pointer to the previous (uninitialized) key value. The impact here
12883 should be limited to a difficult-to-trigger crash, if OpenSSL is
12884 running an engine that makes key generation failures possible, or
12885 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12886 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12889 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12890 - Fix an integer underflow bug when comparing malformed Tor
12891 versions. This bug could crash Tor when built with
12892 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12893 0.2.9.8, which were built with -ftrapv by default. In other cases
12894 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12895 on 0.0.8pre1. Found by OSS-Fuzz.
12897 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12898 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12899 zero size. Check size argument to memwipe() for underflow. Fixes
12900 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12903 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12904 - Make Tor survive errors involving connections without a
12905 corresponding event object. Previously we'd fail with an
12906 assertion; now we produce a log message. Related to bug 16248.
12908 o Minor features (geoip):
12909 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12912 o Minor bugfixes (compilation, backport from 0.2.7.6):
12913 - Fix a compilation warning with Clang 3.6: Do not check the
12914 presence of an address which can never be NULL. Fixes bug 17781.
12916 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
12917 - Check for failures from crypto_early_init, and refuse to continue.
12918 A previous typo meant that we could keep going with an
12919 uninitialized crypto library, and would have OpenSSL initialize
12920 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12921 when implementing ticket 4900. Patch by "teor".
12923 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12924 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12925 a client authorized hidden service. Fixes bug 15823; bugfix
12929 Changes in version 0.2.4.28 - 2017-03-03
12930 Tor 0.2.4.28 backports a number of security fixes from later Tor
12931 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
12932 this release, if for some reason they cannot upgrade to a later
12935 Note that support for Tor 0.2.4.x is ending soon: we will not issue
12936 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
12937 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
12939 o Directory authority changes (backport from 0.2.8.5-rc):
12940 - Urras is no longer a directory authority. Closes ticket 19271.
12942 o Directory authority changes (backport from 0.2.9.2-alpha):
12943 - The "Tonga" bridge authority has been retired; the new bridge
12944 authority is "Bifroest". Closes tickets 19728 and 19690.
12946 o Directory authority key updates (backport from 0.2.8.1-alpha):
12947 - Update the V3 identity key for the dannenberg directory authority:
12948 it was changed on 18 November 2015. Closes task 17906. Patch
12951 o Major features (security fixes, backport from 0.2.9.4-alpha):
12952 - Prevent a class of security bugs caused by treating the contents
12953 of a buffer chunk as if they were a NUL-terminated string. At
12954 least one such bug seems to be present in all currently used
12955 versions of Tor, and would allow an attacker to remotely crash
12956 most Tor instances, especially those compiled with extra compiler
12957 hardening. With this defense in place, such bugs can't crash Tor,
12958 though we should still fix them as they occur. Closes ticket
12959 20384 (TROVE-2016-10-001).
12961 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12962 - Fix a bug in parsing that could cause clients to read a single
12963 byte past the end of an allocated region. This bug could be used
12964 to cause hardened clients (built with --enable-expensive-hardening)
12965 to crash if they tried to visit a hostile hidden service. Non-
12966 hardened clients are only affected depending on the details of
12967 their platform's memory allocator. Fixes bug 21018; bugfix on
12968 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12969 2016-12-002 and as CVE-2016-1254.
12971 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12972 - Fix an error that could cause us to read 4 bytes before the
12973 beginning of an openssl string. This bug could be used to cause
12974 Tor to crash on systems with unusual malloc implementations, or
12975 systems with unusual hardening installed. Fixes bug 17404; bugfix
12978 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12979 - Avoid a difficult-to-trigger heap corruption attack when extending
12980 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12981 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12982 Reported by Guido Vranken.
12984 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12985 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12986 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12988 o Major bugfixes (guard selection, backport from 0.2.7.6):
12989 - Actually look at the Guard flag when selecting a new directory
12990 guard. When we implemented the directory guard design, we
12991 accidentally started treating all relays as if they have the Guard
12992 flag during guard selection, leading to weaker anonymity and worse
12993 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12996 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12997 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12998 pointer to the previous (uninitialized) key value. The impact here
12999 should be limited to a difficult-to-trigger crash, if OpenSSL is
13000 running an engine that makes key generation failures possible, or
13001 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13002 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13005 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13006 - Fix an integer underflow bug when comparing malformed Tor
13007 versions. This bug could crash Tor when built with
13008 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13009 0.2.9.8, which were built with -ftrapv by default. In other cases
13010 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13011 on 0.0.8pre1. Found by OSS-Fuzz.
13013 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13014 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13015 zero size. Check size argument to memwipe() for underflow. Fixes
13016 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13019 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13020 - Make Tor survive errors involving connections without a
13021 corresponding event object. Previously we'd fail with an
13022 assertion; now we produce a log message. Related to bug 16248.
13024 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
13025 - Make it harder for attackers to overload hidden services with
13026 introductions, by blocking multiple introduction requests on the
13027 same circuit. Resolves ticket 15515.
13029 o Minor features (geoip):
13030 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13033 o Minor bugfixes (compilation, backport from 0.2.7.6):
13034 - Fix a compilation warning with Clang 3.6: Do not check the
13035 presence of an address which can never be NULL. Fixes bug 17781.
13037 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13038 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13039 a client authorized hidden service. Fixes bug 15823; bugfix
13043 Changes in version 0.2.9.10 - 2017-03-01
13044 Tor 0.2.9.10 backports a security fix from later Tor release. It also
13045 includes fixes for some major issues affecting directory authorities,
13046 LibreSSL compatibility, and IPv6 correctness.
13048 The Tor 0.2.9.x release series is now marked as a long-term-support
13049 series. We intend to backport security fixes to 0.2.9.x until at
13050 least January of 2020.
13052 o Major bugfixes (directory authority, 0.3.0.3-alpha):
13053 - During voting, when marking a relay as a probable sybil, do not
13054 clear its BadExit flag: sybils can still be bad in other ways
13055 too. (We still clear the other flags.) Fixes bug 21108; bugfix
13058 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
13059 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
13060 any IPv6 addresses. Instead, only reject a port over IPv6 if the
13061 exit policy rejects that port on more than an IPv6 /16 of
13062 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
13063 which rejected a relay's own IPv6 address by default. Fixes bug
13064 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
13066 o Major bugfixes (parsing, also in 0.3.0.4-rc):
13067 - Fix an integer underflow bug when comparing malformed Tor
13068 versions. This bug could crash Tor when built with
13069 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13070 0.2.9.8, which were built with -ftrapv by default. In other cases
13071 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13072 on 0.0.8pre1. Found by OSS-Fuzz.
13074 o Minor features (directory authorities, also in 0.3.0.4-rc):
13075 - Directory authorities now reject descriptors that claim to be
13076 malformed versions of Tor. Helps prevent exploitation of
13078 - Reject version numbers with components that exceed INT32_MAX.
13079 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
13080 Fixes bug 21450; bugfix on 0.0.8pre1.
13082 o Minor features (geoip):
13083 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13086 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
13087 - Autoconf now checks to determine if OpenSSL structures are opaque,
13088 instead of explicitly checking for OpenSSL version numbers. Part
13090 - Support building with recent LibreSSL code that uses opaque
13091 structures. Closes ticket 21359.
13093 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
13094 - Repair a couple of (unreachable or harmless) cases of the risky
13095 comparison-by-subtraction pattern that caused bug 21278.
13097 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
13098 - The tor-resolve command line tool now rejects hostnames over 255
13099 characters in length. Previously, it would silently truncate them,
13100 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13101 Patch by "junglefowl".
13104 Changes in version 0.2.9.9 - 2017-01-23
13105 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
13106 cause relays and clients to crash, even if they were not built with
13107 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13108 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13109 version should upgrade.
13111 This release also resolves a client-side onion service reachability
13112 bug, and resolves a pair of small portability issues.
13114 o Major bugfixes (security):
13115 - Downgrade the "-ftrapv" option from "always on" to "only on when
13116 --enable-expensive-hardening is provided." This hardening option,
13117 like others, can turn survivable bugs into crashes -- and having
13118 it on by default made a (relatively harmless) integer overflow bug
13119 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13120 bugfix on 0.2.9.1-alpha.
13122 o Major bugfixes (client, onion service):
13123 - Fix a client-side onion service reachability bug, where multiple
13124 socks requests to an onion service (or a single slow request)
13125 could cause us to mistakenly mark some of the service's
13126 introduction points as failed, and we cache that failure so
13127 eventually we run out and can't reach the service. Also resolves a
13128 mysterious "Remote server sent bogus reason code 65021" log
13129 warning. The bug was introduced in ticket 17218, where we tried to
13130 remember the circuit end reason as a uint16_t, which mangled
13131 negative values. Partially fixes bug 21056 and fixes bug 20307;
13132 bugfix on 0.2.8.1-alpha.
13134 o Minor features (geoip):
13135 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13138 o Minor bugfixes (portability):
13139 - Avoid crashing when Tor is built using headers that contain
13140 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13141 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13143 - Fix Libevent detection on platforms without Libevent 1 headers
13144 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13147 Changes in version 0.2.8.12 - 2016-12-19
13148 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
13149 below) where Tor clients could crash when attempting to visit a
13150 hostile hidden service. Clients are recommended to upgrade as packages
13151 become available for their systems.
13153 It also includes an updated list of fallback directories, backported
13156 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
13157 backported to 0.2.8 in the future.
13159 o Major bugfixes (parsing, security, backported from 0.2.9.8):
13160 - Fix a bug in parsing that could cause clients to read a single
13161 byte past the end of an allocated region. This bug could be used
13162 to cause hardened clients (built with --enable-expensive-hardening)
13163 to crash if they tried to visit a hostile hidden service. Non-
13164 hardened clients are only affected depending on the details of
13165 their platform's memory allocator. Fixes bug 21018; bugfix on
13166 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13167 2016-12-002 and as CVE-2016-1254.
13169 o Minor features (fallback directory list, backported from 0.2.9.8):
13170 - Replace the 81 remaining fallbacks of the 100 originally
13171 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13172 fallbacks (123 new, 54 existing, 27 removed) generated in December
13173 2016. Resolves ticket 20170.
13175 o Minor features (geoip, backported from 0.2.9.7-rc):
13176 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13180 Changes in version 0.2.9.8 - 2016-12-19
13181 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
13183 The Tor 0.2.9 series makes mandatory a number of security features
13184 that were formerly optional. It includes support for a new shared-
13185 randomness protocol that will form the basis for next generation
13186 hidden services, includes a single-hop hidden service mode for
13187 optimizing .onion services that don't actually want to be hidden,
13188 tries harder not to overload the directory authorities with excessive
13189 downloads, and supports a better protocol versioning scheme for
13190 improved compatibility with other implementations of the Tor protocol.
13192 And of course, there are numerous other bugfixes and improvements.
13194 This release also includes a fix for a medium-severity issue (bug
13195 21018 below) where Tor clients could crash when attempting to visit a
13196 hostile hidden service. Clients are recommended to upgrade as packages
13197 become available for their systems.
13199 Below are listed the changes since Tor 0.2.8.11. For a list of
13200 changes since 0.2.9.7-rc, see the ChangeLog file.
13202 o New system requirements:
13203 - When building with OpenSSL, Tor now requires version 1.0.1 or
13204 later. OpenSSL 1.0.0 and earlier are no longer supported by the
13205 OpenSSL team, and should not be used. Closes ticket 20303.
13206 - Tor now requires Libevent version 2.0.10-stable or later. Older
13207 versions of Libevent have less efficient backends for several
13208 platforms, and lack the DNS code that we use for our server-side
13209 DNS support. This implements ticket 19554.
13210 - Tor now requires zlib version 1.2 or later, for security,
13211 efficiency, and (eventually) gzip support. (Back when we started,
13212 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
13213 released in 2003. We recommend the latest version.)
13215 o Deprecated features:
13216 - A number of DNS-cache-related sub-options for client ports are now
13217 deprecated for security reasons, and may be removed in a future
13218 version of Tor. (We believe that client-side DNS caching is a bad
13219 idea for anonymity, and you should not turn it on.) The options
13220 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
13221 UseIPv4Cache, and UseIPv6Cache.
13222 - A number of options are deprecated for security reasons, and may
13223 be removed in a future version of Tor. The options are:
13224 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
13225 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
13226 CloseHSClientCircuitsImmediatelyOnTimeout,
13227 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
13228 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
13229 UseNTorHandshake, and WarnUnsafeSocks.
13230 - The *ListenAddress options are now deprecated as unnecessary: the
13231 corresponding *Port options should be used instead. These options
13232 may someday be removed. The affected options are:
13233 ControlListenAddress, DNSListenAddress, DirListenAddress,
13234 NATDListenAddress, ORListenAddress, SocksListenAddress,
13235 and TransListenAddress.
13237 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
13238 - Fix a bug in parsing that could cause clients to read a single
13239 byte past the end of an allocated region. This bug could be used
13240 to cause hardened clients (built with --enable-expensive-hardening)
13241 to crash if they tried to visit a hostile hidden service. Non-
13242 hardened clients are only affected depending on the details of
13243 their platform's memory allocator. Fixes bug 21018; bugfix on
13244 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13245 2016-12-002 and as CVE-2016-1254.
13247 o Major features (build, hardening):
13248 - Tor now builds with -ftrapv by default on compilers that support
13249 it. This option detects signed integer overflow (which C forbids),
13250 and turns it into a hard-failure. We do not apply this option to
13251 code that needs to run in constant time to avoid side-channels;
13252 instead, we use -fwrapv in that code. Closes ticket 17983.
13253 - When --enable-expensive-hardening is selected, stop applying the
13254 clang/gcc sanitizers to code that needs to run in constant time.
13255 Although we are aware of no introduced side-channels, we are not
13256 able to prove that there are none. Related to ticket 17983.
13258 o Major features (circuit building, security):
13259 - Authorities, relays, and clients now require ntor keys in all
13260 descriptors, for all hops (except for rare hidden service protocol
13261 cases), for all circuits, and for all other roles. Part of
13263 - Authorities, relays, and clients only use ntor, except for
13264 rare cases in the hidden service protocol. Part of ticket 19163.
13266 o Major features (compilation):
13267 - Our big list of extra GCC warnings is now enabled by default when
13268 building with GCC (or with anything like Clang that claims to be
13269 GCC-compatible). To make all warnings into fatal compilation
13270 errors, pass --enable-fatal-warnings to configure. Closes
13272 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
13273 turn on C and POSIX extensions. (Previously, we attempted to do
13274 this on an ad hoc basis.) Closes ticket 19139.
13276 o Major features (directory authorities, hidden services):
13277 - Directory authorities can now perform the shared randomness
13278 protocol specified by proposal 250. Using this protocol, directory
13279 authorities generate a global fresh random value every day. In the
13280 future, this value will be used by hidden services to select
13281 HSDirs. This release implements the directory authority feature;
13282 the hidden service side will be implemented in the future as part
13283 of proposal 224. Resolves ticket 16943; implements proposal 250.
13285 o Major features (downloading, random exponential backoff):
13286 - When we fail to download an object from a directory service, wait
13287 for an (exponentially increasing) randomized amount of time before
13288 retrying, rather than a fixed interval as we did before. This
13289 prevents a group of Tor instances from becoming too synchronized,
13290 or a single Tor instance from becoming too predictable, in its
13291 download schedule. Closes ticket 15942.
13293 o Major features (resource management):
13294 - Tor can now notice it is about to run out of sockets, and
13295 preemptively close connections of lower priority. (This feature is
13296 off by default for now, since the current prioritizing method is
13297 yet not mature enough. You can enable it by setting
13298 "DisableOOSCheck 0", but watch out: it might close some sockets
13299 you would rather have it keep.) Closes ticket 18640.
13301 o Major features (single-hop "hidden" services):
13302 - Add experimental HiddenServiceSingleHopMode and
13303 HiddenServiceNonAnonymousMode options. When both are set to 1,
13304 every hidden service on that Tor instance becomes a non-anonymous
13305 Single Onion Service. Single Onions make one-hop (direct)
13306 connections to their introduction and rendezvous points. One-hop
13307 circuits make Single Onion servers easily locatable, but clients
13308 remain location-anonymous. This is compatible with the existing
13309 hidden service implementation, and works on the current Tor
13310 network without any changes to older relays or clients. Implements
13311 proposal 260, completes ticket 17178. Patch by teor and asn.
13313 o Major features (subprotocol versions):
13314 - Tor directory authorities now vote on a set of recommended
13315 "subprotocol versions", and on a set of required subprotocol
13316 versions. Clients and relays that lack support for a _required_
13317 subprotocol version will not start; those that lack support for a
13318 _recommended_ subprotocol version will warn the user to upgrade.
13319 This change allows compatible implementations of the Tor protocol(s)
13320 to exist without pretending to be 100% bug-compatible with
13321 particular releases of Tor itself. Closes ticket 19958; implements
13322 part of proposal 264.
13324 o Major bugfixes (circuit building):
13325 - Hidden service client-to-intro-point and service-to-rendezvous-
13326 point circuits use the TAP key supplied by the protocol, to avoid
13327 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
13329 o Major bugfixes (download scheduling):
13330 - Avoid resetting download status for consensuses hourly, since we
13331 already have another, smarter retry mechanism. Fixes bug 8625;
13332 bugfix on 0.2.0.9-alpha.
13333 - If a consensus expires while we are waiting for certificates to
13334 download, stop waiting for certificates.
13335 - If we stop waiting for certificates less than a minute after we
13336 started downloading them, do not consider the certificate download
13337 failure a separate failure. Fixes bug 20533; bugfix
13339 - When using exponential backoff in test networks, use a lower
13340 exponent, so the delays do not vary as much. This helps test
13341 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
13343 o Major bugfixes (exit policies):
13344 - Avoid disclosing exit outbound bind addresses, configured port
13345 bind addresses, and local interface addresses in relay descriptors
13346 by default under ExitPolicyRejectPrivate. Instead, only reject
13347 these (otherwise unlisted) addresses if
13348 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
13349 0.2.7.2-alpha. Patch by teor.
13351 o Major bugfixes (hidden services):
13352 - Allow Tor clients with appropriate controllers to work with
13353 FetchHidServDescriptors set to 0. Previously, this option also
13354 disabled descriptor cache lookup, thus breaking hidden services
13355 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
13356 - Clients now require hidden services to include the TAP keys for
13357 their intro points in the hidden service descriptor. This prevents
13358 an inadvertent upgrade to ntor, which a malicious hidden service
13359 could use to distinguish clients by consensus version. Fixes bug
13360 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
13362 o Major bugfixes (relay, resolver, logging):
13363 - For relays that don't know their own address, avoid attempting a
13364 local hostname resolve for each descriptor we download. This
13365 will cut down on the number of "Success: chose address 'x.x.x.x'"
13366 log lines, and also avoid confusing clock jumps if the resolver
13367 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
13369 o Minor features (port flags):
13370 - Add new flags to the *Port options to give finer control over which
13371 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
13372 and the synthetic flag OnionTrafficOnly, which is equivalent to
13373 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
13374 18693; patch by "teor".
13376 o Minor features (build, hardening):
13377 - Detect and work around a libclang_rt problem that would prevent
13378 clang from finding __mulodi4() on some 32-bit platforms, and thus
13379 keep -ftrapv from linking on those systems. Closes ticket 19079.
13380 - When building on a system without runtime support for the runtime
13381 hardening options, try to log a useful warning at configuration
13382 time, rather than an incomprehensible warning at link time. If
13383 expensive hardening was requested, this warning becomes an error.
13384 Closes ticket 18895.
13386 o Minor features (client, directory):
13387 - Since authorities now omit all routers that lack the Running and
13388 Valid flags, we assume that any relay listed in the consensus must
13389 have those flags. Closes ticket 20001; implements part of
13392 o Minor features (code safety):
13393 - In our integer-parsing functions, ensure that the maximum value we
13394 allow is no smaller than the minimum value. Closes ticket 19063;
13395 patch from "U+039b".
13397 o Minor features (compilation, portability):
13398 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
13401 o Minor features (config):
13402 - Warn users when descriptor and port addresses are inconsistent.
13403 Mitigates bug 13953; patch by teor.
13405 o Minor features (controller):
13406 - Allow controllers to configure basic client authorization on
13407 hidden services when they create them with the ADD_ONION controller
13408 command. Implements ticket 15588. Patch by "special".
13409 - Fire a STATUS_SERVER controller event whenever the hibernation
13410 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
13411 - Implement new GETINFO queries for all downloads that use
13412 download_status_t to schedule retries. This allows controllers to
13413 examine the schedule for pending downloads. Closes ticket 19323.
13415 o Minor features (development tools, etags):
13416 - Teach the "make tags" Makefile target how to correctly find
13417 "MOCK_IMPL" function definitions. Patch from nherring; closes
13420 o Minor features (directory authority):
13421 - After voting, if the authorities decide that a relay is not
13422 "Valid", they no longer include it in the consensus at all. Closes
13423 ticket 20002; implements part of proposal 272.
13424 - Directory authorities now only give the Guard flag to a relay if
13425 they are also giving it the Stable flag. This change allows us to
13426 simplify path selection for clients. It should have minimal effect
13427 in practice, since >99% of Guards already have the Stable flag.
13428 Implements ticket 18624.
13429 - Directory authorities now write their v3-status-votes file out to
13430 disk earlier in the consensus process, so we have a record of the
13431 votes even if we abort the consensus process. Resolves
13434 o Minor features (fallback directory list, new since 0.2.9.7-rc):
13435 - Replace the 81 remaining fallbacks of the 100 originally
13436 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13437 fallbacks (123 new, 54 existing, 27 removed) generated in December
13438 2016. Resolves ticket 20170.
13440 o Minor features (hidden service):
13441 - Stop being so strict about the payload length of "rendezvous1"
13442 cells. We used to be locked in to the "TAP" handshake length, and
13443 now we can handle better handshakes like "ntor". Resolves
13446 o Minor features (infrastructure, time):
13447 - Tor now includes an improved timer backend, so that we can
13448 efficiently support tens or hundreds of thousands of concurrent
13449 timers, as will be needed for some of our planned anti-traffic-
13450 analysis work. This code is based on William Ahern's "timeout.c"
13451 project, which implements a "tickless hierarchical timing wheel".
13452 Closes ticket 18365.
13453 - Tor now uses the operating system's monotonic timers (where
13454 available) for internal fine-grained timing. Previously we would
13455 look at the system clock, and then attempt to compensate for the
13456 clock running backwards. Closes ticket 18908.
13458 o Minor features (logging):
13459 - Add a set of macros to check nonfatal assertions, for internal
13460 use. Migrating more of our checks to these should help us avoid
13461 needless crash bugs. Closes ticket 18613.
13462 - Provide a more useful warning message when configured with an
13463 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
13464 - When dumping unparseable router descriptors, optionally store them
13465 in separate files, named by digest, up to a configurable size
13466 limit. You can change the size limit by setting the
13467 MaxUnparseableDescSizeToLog option, and disable this feature by
13468 setting that option to 0. Closes ticket 18322.
13470 o Minor features (performance):
13471 - Change the "optimistic data" extension from "off by default" to
13472 "on by default". The default was ordinarily overridden by a
13473 consensus option, but when clients were bootstrapping for the
13474 first time, they would not have a consensus to get the option
13475 from. Changing this default saves a round-trip during startup.
13476 Closes ticket 18815.
13478 o Minor features (relay, usability):
13479 - When the directory authorities refuse a bad relay's descriptor,
13480 encourage the relay operator to contact us. Many relay operators
13481 won't notice this line in their logs, but it's a win if even a few
13482 learn why we don't like what their relay was doing. Resolves
13485 o Minor features (security, TLS):
13486 - Servers no longer support clients that lack AES ciphersuites.
13487 (3DES is no longer considered an acceptable cipher.) We believe
13488 that no such Tor clients currently exist, since Tor has required
13489 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
13491 o Minor features (testing):
13492 - Disable memory protections on OpenBSD when performing our unit
13493 tests for memwipe(). The test deliberately invokes undefined
13494 behavior, and the OpenBSD protections interfere with this. Patch
13495 from "rubiate". Closes ticket 20066.
13496 - Move the test-network.sh script to chutney, and modify tor's test-
13497 network.sh to call the (newer) chutney version when available.
13498 Resolves ticket 19116. Patch by teor.
13499 - Use the lcov convention for marking lines as unreachable, so that
13500 we don't count them when we're generating test coverage data.
13501 Update our coverage tools to understand this convention. Closes
13503 - Our link-handshake unit tests now check that when invalid
13504 handshakes fail, they fail with the error messages we expected.
13505 - Our unit testing code that captures log messages no longer
13506 prevents them from being written out if the user asked for them
13507 (by passing --debug or --info or --notice or --warn to the "test"
13508 binary). This change prevents us from missing unexpected log
13509 messages simply because we were looking for others. Related to
13511 - The unit tests now log all warning messages with the "BUG" flag.
13512 Previously, they only logged errors by default. This change will
13513 help us make our testing code more correct, and make sure that we
13514 only hit this code when we mean to. In the meantime, however,
13515 there will be more warnings in the unit test logs than before.
13516 This is preparatory work for ticket 19999.
13517 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
13518 assertion as a test failure.
13519 - We've done significant work to make the unit tests run faster.
13521 o Minor features (testing, ipv6):
13522 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
13523 tests. Remove bridges+hs, as it's somewhat redundant. This
13524 requires a recent chutney version that supports IPv6 clients,
13525 relays, and authorities. Closes ticket 20069; patch by teor.
13526 - Add the single-onion and single-onion-ipv6 chutney targets to
13527 "make test-network-all". This requires a recent chutney version
13528 with the single onion network flavors (git c72a652 or later).
13529 Closes ticket 20072; patch by teor.
13531 o Minor features (Tor2web):
13532 - Make Tor2web clients respect ReachableAddresses. This feature was
13533 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
13534 0.2.8.7. Implements feature 20034. Patch by teor.
13536 o Minor features (unix domain sockets):
13537 - When configuring a unix domain socket for a SocksPort,
13538 ControlPort, or Hidden service, you can now wrap the address in
13539 quotes, using C-style escapes inside the quotes. This allows unix
13540 domain socket paths to contain spaces. Resolves ticket 18753.
13542 o Minor features (user interface):
13543 - Tor now supports the ability to declare options deprecated, so
13544 that we can recommend that people stop using them. Previously, this
13545 was done in an ad-hoc way. There is a new --list-deprecated-options
13546 command-line option to list all of the deprecated options. Closes
13549 o Minor features (virtual addresses):
13550 - Increase the maximum number of bits for the IPv6 virtual network
13551 prefix from 16 to 104. In this way, the condition for address
13552 allocation is less restrictive. Closes ticket 20151; feature
13555 o Minor bug fixes (circuits):
13556 - Use the CircuitBuildTimeout option whenever
13557 LearnCircuitBuildTimeout is disabled. Previously, we would respect
13558 the option when a user disabled it, but not when it was disabled
13559 because some other option was set. Fixes bug 20073; bugfix on
13560 0.2.4.12-alpha. Patch by teor.
13562 o Minor bugfixes (build):
13563 - The current Git revision when building from a local repository is
13564 now detected correctly when using git worktrees. Fixes bug 20492;
13565 bugfix on 0.2.3.9-alpha.
13567 o Minor bugfixes (relay address discovery):
13568 - Stop reordering IP addresses returned by the OS. This makes it
13569 more likely that Tor will guess the same relay IP address every
13570 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
13571 Reported by René Mayrhofer, patch by "cypherpunks".
13573 o Minor bugfixes (memory allocation):
13574 - Change how we allocate memory for large chunks on buffers, to
13575 avoid a (currently impossible) integer overflow, and to waste less
13576 space when allocating unusually large chunks. Fixes bug 20081;
13577 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
13579 o Minor bugfixes (bootstrap):
13580 - Remember the directory server we fetched the consensus or previous
13581 certificates from, and use it to fetch future authority
13582 certificates. This change improves bootstrapping performance.
13583 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
13585 o Minor bugfixes (circuits):
13586 - Make sure extend_info_from_router() is only called on servers.
13587 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
13589 o Minor bugfixes (client, fascistfirewall):
13590 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
13591 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
13593 o Minor bugfixes (client, unix domain sockets):
13594 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
13595 the client address is meaningless. Fixes bug 20261; bugfix
13598 o Minor bugfixes (code style):
13599 - Fix an integer signedness conversion issue in the case conversion
13600 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
13602 o Minor bugfixes (compilation):
13603 - Build correctly on versions of libevent2 without support for
13604 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
13606 - When building with Clang, use a full set of GCC warnings.
13607 (Previously, we included only a subset, because of the way we
13608 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
13609 - Detect Libevent2 functions correctly on systems that provide
13610 libevent2, but where libevent1 is linked with -levent. Fixes bug
13611 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
13612 - Run correctly when built on Windows build environments that
13613 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
13615 o Minor bugfixes (configuration):
13616 - When parsing quoted configuration values from the torrc file,
13617 handle Windows line endings correctly. Fixes bug 19167; bugfix on
13618 0.2.0.16-alpha. Patch from "Pingl".
13620 o Minor bugfixes (directory authority):
13621 - Authorities now sort the "package" lines in their votes, for ease
13622 of debugging. (They are already sorted in consensus documents.)
13623 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
13624 - Die with a more useful error when the operator forgets to place
13625 the authority_signing_key file into the keys directory. This
13626 avoids an uninformative assert & traceback about having an invalid
13627 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
13628 - When allowing private addresses, mark Exits that only exit to
13629 private locations as such. Fixes bug 20064; bugfix
13631 - When parsing a detached signature, make sure we use the length of
13632 the digest algorithm instead of a hardcoded DIGEST256_LEN in
13633 order to avoid comparing bytes out-of-bounds with a smaller digest
13634 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
13636 o Minor bugfixes (getpass):
13637 - Defensively fix a non-triggerable heap corruption at do_getpass()
13638 to protect ourselves from mistakes in the future. Fixes bug
13639 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
13642 o Minor bugfixes (guard selection):
13643 - Don't mark guards as unreachable if connection_connect() fails.
13644 That function fails for local reasons, so it shouldn't reveal
13645 anything about the status of the guard. Fixes bug 14334; bugfix
13647 - Use a single entry guard even if the NumEntryGuards consensus
13648 parameter is not provided. Fixes bug 17688; bugfix
13651 o Minor bugfixes (hidden services):
13652 - Increase the minimum number of internal circuits we preemptively
13653 build from 2 to 3, so a circuit is available when a client
13654 connects to another onion service. Fixes bug 13239; bugfix
13656 - Allow hidden services to run on IPv6 addresses even when the
13657 IPv6Exit option is not set. Fixes bug 18357; bugfix
13659 - Stop logging intro point details to the client log on certain
13660 error conditions. Fixed as part of bug 20012; bugfix on
13661 0.2.4.8-alpha. Patch by teor.
13662 - When deleting an ephemeral hidden service, close its intro points
13663 even if they are not completely open. Fixes bug 18604; bugfix
13665 - When configuring hidden services, check every hidden service
13666 directory's permissions. Previously, we only checked the last
13667 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
13669 o Minor bugfixes (IPv6, testing):
13670 - Check for IPv6 correctly on Linux when running test networks.
13671 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
13673 o Minor bugfixes (Linux seccomp2 sandbox):
13674 - Add permission to run the sched_yield() and sigaltstack() system
13675 calls, in order to support versions of Tor compiled with asan or
13676 ubsan code that use these calls. Now "sandbox 1" and
13677 "--enable-expensive-hardening" should be compatible on more
13678 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
13680 o Minor bugfixes (logging):
13681 - Downgrade a harmless log message about the
13682 pending_entry_connections list from "warn" to "info". Mitigates
13684 - Log a more accurate message when we fail to dump a microdescriptor.
13685 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
13686 - When logging a directory ownership mismatch, log the owning
13687 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
13688 - When we are unable to remove the bw_accounting file, do not warn
13689 if the reason we couldn't remove it was that it didn't exist.
13690 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
13692 o Minor bugfixes (memory leak):
13693 - Fix a series of slow memory leaks related to parsing torrc files
13694 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
13695 - Avoid a small memory leak when informing worker threads about
13696 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
13697 - Fix a small memory leak when receiving AF_UNIX connections on a
13698 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
13699 - When moving a signed descriptor object from a source to an
13700 existing destination, free the allocated memory inside that
13701 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
13702 - Fix a memory leak and use-after-free error when removing entries
13703 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
13704 0.2.5.5-alpha. Patch from "cypherpunks".
13705 - Fix a small, uncommon memory leak that could occur when reading a
13706 truncated ed25519 key file. Fixes bug 18956; bugfix
13709 o Minor bugfixes (option parsing):
13710 - Count unix sockets when counting client listeners (SOCKS, Trans,
13711 NATD, and DNS). This has no user-visible behavior changes: these
13712 options are set once, and never read. Required for correct
13713 behavior in ticket 17178. Fixes bug 19677; bugfix on
13714 0.2.6.3-alpha. Patch by teor.
13716 o Minor bugfixes (options):
13717 - Check the consistency of UseEntryGuards and EntryNodes more
13718 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
13720 - Stop changing the configured value of UseEntryGuards on
13721 authorities and Tor2web clients. Fixes bug 20074; bugfix on
13722 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
13725 o Minor bugfixes (relay):
13726 - Ensure relays don't make multiple connections during bootstrap.
13727 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
13728 - Do not try to parallelize workers more than 16x without the user
13729 explicitly configuring us to do so, even if we do detect more than
13730 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13732 o Minor bugfixes (testing):
13733 - The test-stem and test-network makefile targets now depend only on
13734 the tor binary that they are testing. Previously, they depended on
13735 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
13736 patch from "cypherpunks".
13737 - Allow clients to retry HSDirs much faster in test networks. Fixes
13738 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
13739 - Avoid a unit test failure on systems with over 16 detectable CPU
13740 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13741 - Let backtrace tests work correctly under AddressSanitizer:
13742 disable ASAN's detection of segmentation faults while running
13743 test_bt.sh, so that we can make sure that our own backtrace
13744 generation code works. Fixes bug 18934; bugfix
13745 on 0.2.5.2-alpha. Patch from "cypherpunks".
13746 - Fix the test-network-all target on out-of-tree builds by using the
13747 correct path to the test driver script. Fixes bug 19421; bugfix
13749 - Stop spurious failures in the local interface address discovery
13750 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
13752 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
13753 removed the ECDH ciphers which caused the tests to fail on
13754 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
13755 - The tor_tls_server_info_callback unit test no longer crashes when
13756 debug-level logging is turned on. Fixes bug 20041; bugfix
13759 o Minor bugfixes (time):
13760 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
13761 bugfix on all released tor versions.
13762 - When computing the difference between two times in milliseconds,
13763 we now round to the nearest millisecond correctly. Previously, we
13764 could sometimes round in the wrong direction. Fixes bug 19428;
13765 bugfix on 0.2.2.2-alpha.
13767 o Minor bugfixes (Tor2web):
13768 - Prevent Tor2web clients from running hidden services: these services
13769 are not anonymous due to the one-hop client paths. Fixes bug
13770 19678. Patch by teor.
13772 o Minor bugfixes (user interface):
13773 - Display a more accurate number of suppressed messages in the log
13774 rate-limiter. Previously, there was a potential integer overflow
13775 in the counter. Now, if the number of messages hits a maximum, the
13776 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
13778 - Fix a typo in the passphrase prompt for the ed25519 identity key.
13779 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
13781 o Code simplification and refactoring:
13782 - Remove redundant declarations of the MIN macro. Closes
13784 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
13785 Closes ticket 18462; patch from "icanhasaccount".
13786 - Split the 600-line directory_handle_command_get function into
13787 separate functions for different URL types. Closes ticket 16698.
13790 - Add module-level internal documentation for 36 C files that
13791 previously didn't have a high-level overview. Closes ticket 20385.
13792 - Correct the IPv6 syntax in our documentation for the
13793 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
13794 - Correct the minimum bandwidth value in torrc.sample, and queue a
13795 corresponding change for torrc.minimal. Closes ticket 20085.
13796 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
13797 ticket 19153. Patch from "U+039b".
13798 - Module-level documentation for several more modules. Closes
13799 tickets 19287 and 19290.
13800 - Document the --passphrase-fd option in the tor manpage. Fixes bug
13801 19504; bugfix on 0.2.7.3-rc.
13802 - Document the default PathsNeededToBuildCircuits value that's used
13803 by clients when the directory authorities don't set
13804 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
13805 Patch by teor, reported by Jesse V.
13806 - Fix manual for the User option: it takes a username, not a UID.
13807 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
13809 - Fix the description of the --passphrase-fd option in the
13810 tor-gencert manpage. The option is used to pass the number of a
13811 file descriptor to read the passphrase from, not to read the file
13812 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
13815 - We no longer include the (dead, deprecated) bufferevent code in
13816 Tor. Closes ticket 19450. Based on a patch from "U+039b".
13818 o Removed features:
13819 - Remove support for "GET /tor/bytes.txt" DirPort request, and
13820 "GETINFO dir-usage" controller request, which were only available
13821 via a compile-time option in Tor anyway. Feature was added in
13822 0.2.2.1-alpha. Resolves ticket 19035.
13823 - There is no longer a compile-time option to disable support for
13824 TransPort. (If you don't want TransPort, just don't use it.) Patch
13825 from "U+039b". Closes ticket 19449.
13828 - Run more workqueue tests as part of "make check". These had
13829 previously been implemented, but you needed to know special
13830 command-line options to enable them.
13831 - We now have unit tests for our code to reject zlib "compression
13832 bombs". (Fortunately, the code works fine.)
13835 Changes in version 0.2.8.11 - 2016-12-08
13836 Tor 0.2.8.11 backports fixes for additional portability issues that
13837 could prevent Tor from building correctly on OSX Sierra, or with
13838 OpenSSL 1.1. Affected users should upgrade; others can safely stay
13841 o Minor bugfixes (portability):
13842 - Avoid compilation errors when building on OSX Sierra. Sierra began
13843 to support the getentropy() and clock_gettime() APIs, but created
13844 a few problems in doing so. Tor 0.2.9 has a more thorough set of
13845 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
13846 monotonic time interfaces. Fixes bug 20865. Bugfix
13849 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13850 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13851 architectures. Closes ticket 20588.
13854 Changes in version 0.2.8.10 - 2016-12-02
13855 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
13856 unusable after they left standby mode. It also backports fixes for
13857 a few portability issues and a small but problematic memory leak.
13859 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
13860 - When Tor leaves standby because of a new application request, open
13861 circuits as needed to serve that request. Previously, we would
13862 potentially wait a very long time. Fixes part of bug 19969; bugfix
13865 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
13866 - Clients now respond to new application stream requests immediately
13867 when they arrive, rather than waiting up to one second before
13868 starting to handle them. Fixes part of bug 19969; bugfix
13871 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
13872 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13873 successfully targeting earlier versions of OSX. Resolves
13876 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13877 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13878 20551; bugfix on 0.2.1.1-alpha.
13880 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
13881 - Work around a memory leak in OpenSSL 1.1 when encoding public
13882 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13884 o Minor features (geoip):
13885 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13889 Changes in version 0.2.8.9 - 2016-10-17
13890 Tor 0.2.8.9 backports a fix for a security hole in previous versions
13891 of Tor that would allow a remote attacker to crash a Tor client,
13892 hidden service, relay, or authority. All Tor users should upgrade to
13893 this version, or to 0.2.9.4-alpha. Patches will be released for older
13896 o Major features (security fixes, also in 0.2.9.4-alpha):
13897 - Prevent a class of security bugs caused by treating the contents
13898 of a buffer chunk as if they were a NUL-terminated string. At
13899 least one such bug seems to be present in all currently used
13900 versions of Tor, and would allow an attacker to remotely crash
13901 most Tor instances, especially those compiled with extra compiler
13902 hardening. With this defense in place, such bugs can't crash Tor,
13903 though we should still fix them as they occur. Closes ticket
13904 20384 (TROVE-2016-10-001).
13906 o Minor features (geoip):
13907 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
13911 Changes in version 0.2.8.8 - 2016-09-23
13912 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
13913 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
13914 who select public relays as their bridges.
13916 o Major bugfixes (crash):
13917 - Fix a complicated crash bug that could affect Tor clients
13918 configured to use bridges when replacing a networkstatus consensus
13919 in which one of their bridges was mentioned. OpenBSD users saw
13920 more crashes here, but all platforms were potentially affected.
13921 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
13923 o Major bugfixes (relay, OOM handler):
13924 - Fix a timing-dependent assertion failure that could occur when we
13925 tried to flush from a circuit after having freed its cells because
13926 of an out-of-memory condition. Fixes bug 20203; bugfix on
13927 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
13930 o Minor feature (fallback directories):
13931 - Remove broken fallbacks from the hard-coded fallback directory
13932 list. Closes ticket 20190; patch by teor.
13934 o Minor features (geoip):
13935 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
13939 Changes in version 0.2.8.7 - 2016-08-24
13940 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
13941 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
13942 who sets the ReachableAddresses option, and all bridges, are strongly
13943 encouraged to upgrade.
13945 o Directory authority changes:
13946 - The "Tonga" bridge authority has been retired; the new bridge
13947 authority is "Bifroest". Closes tickets 19728 and 19690.
13949 o Major bugfixes (client, security):
13950 - Only use the ReachableAddresses option to restrict the first hop
13951 in a path. In earlier versions of 0.2.8.x, it would apply to
13952 every hop in the path, with a possible degradation in anonymity
13953 for anyone using an uncommon ReachableAddress setting. Fixes bug
13954 19973; bugfix on 0.2.8.2-alpha.
13956 o Minor features (geoip):
13957 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
13960 o Minor bugfixes (compilation):
13961 - Remove an inappropriate "inline" in tortls.c that was causing
13962 warnings on older versions of GCC. Fixes bug 19903; bugfix
13965 o Minor bugfixes (fallback directories):
13966 - Avoid logging a NULL string pointer when loading fallback
13967 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
13968 and 0.2.8.1-alpha. Report and patch by "rubiate".
13971 Changes in version 0.2.8.6 - 2016-08-02
13973 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
13975 The Tor 0.2.8 series improves client bootstrapping performance,
13976 completes the authority-side implementation of improved identity
13977 keys for relays, and includes numerous bugfixes and performance
13978 improvements throughout the program. This release continues to
13979 improve the coverage of Tor's test suite. For a full list of
13980 changes since Tor 0.2.7, see the ReleaseNotes file.
13982 Below is a list of the changes since Tor 0.2.7.
13984 o New system requirements:
13985 - Tor no longer attempts to support platforms where the "time_t"
13986 type is unsigned. (To the best of our knowledge, only OpenVMS does
13987 this, and Tor has never actually built on OpenVMS.) Closes
13989 - Tor no longer supports versions of OpenSSL with a broken
13990 implementation of counter mode. (This bug was present in OpenSSL
13991 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
13992 longer runs with, these versions.
13993 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
13994 later (released in 2008 and 2009 respectively). If you are
13995 building Tor from the git repository instead of from the source
13996 distribution, and your tools are older than this, you will need to
13997 upgrade. Closes ticket 17732.
13999 o Directory authority changes:
14000 - Update the V3 identity key for the dannenberg directory authority:
14001 it was changed on 18 November 2015. Closes task 17906. Patch
14003 - Urras is no longer a directory authority. Closes ticket 19271.
14005 o Major features (directory system):
14006 - Include a trial list of default fallback directories, based on an
14007 opt-in survey of suitable relays. Doing this should make clients
14008 bootstrap more quickly and reliably, and reduce the load on the
14009 directory authorities. Closes ticket 15775. Patch by teor.
14010 Candidates identified using an OnionOO script by weasel, teor,
14011 gsathya, and karsten.
14012 - Previously only relays that explicitly opened a directory port
14013 (DirPort) accepted directory requests from clients. Now all
14014 relays, with and without a DirPort, accept and serve tunneled
14015 directory requests that they receive through their ORPort. You can
14016 disable this behavior using the new DirCache option. Closes
14018 - When bootstrapping multiple consensus downloads at a time, use the
14019 first one that starts downloading, and close the rest. This
14020 reduces failures when authorities or fallback directories are slow
14021 or down. Together with the code for feature 15775, this feature
14022 should reduces failures due to fallback churn. Implements ticket
14023 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
14024 mikeperry and teor.
14026 o Major features (security, Linux):
14027 - When Tor starts as root on Linux and is told to switch user ID, it
14028 can now retain the capability to bind to low ports. By default,
14029 Tor will do this only when it's switching user ID and some low
14030 ports have been configured. You can change this behavior with the
14031 new option KeepBindCapabilities. Closes ticket 8195.
14033 o Major bugfixes (client, bootstrapping):
14034 - Check if bootstrap consensus downloads are still needed when the
14035 linked connection attaches. This prevents tor making unnecessary
14036 begindir-style connections, which are the only directory
14037 connections tor clients make since the fix for 18483 was merged.
14038 - Fix some edge cases where consensus download connections may not
14039 have been closed, even though they were not needed. Related to fix
14041 - Make relays retry consensus downloads the correct number of times,
14042 rather than the more aggressive client retry count. Fixes part of
14045 o Major bugfixes (dns proxy mode, crash):
14046 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14047 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14049 o Major bugfixes (ed25519, voting):
14050 - Actually enable support for authorities to match routers by their
14051 Ed25519 identities. Previously, the code had been written, but
14052 some debugging code that had accidentally been left in the
14053 codebase made it stay turned off. Fixes bug 17702; bugfix
14055 - When collating votes by Ed25519 identities, authorities now
14056 include a "NoEdConsensus" flag if the ed25519 value (or lack
14057 thereof) for a server does not reflect the majority consensus.
14058 Related to bug 17668; bugfix on 0.2.7.2-alpha.
14059 - When generating a vote with keypinning disabled, never include two
14060 entries for the same ed25519 identity. This bug was causing
14061 authorities to generate votes that they could not parse when a
14062 router violated key pinning by changing its RSA identity but
14063 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
14064 18318. Bugfix on 0.2.7.2-alpha.
14066 o Major bugfixes (key management):
14067 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14068 pointer to the previous (uninitialized) key value. The impact here
14069 should be limited to a difficult-to-trigger crash, if OpenSSL is
14070 running an engine that makes key generation failures possible, or
14071 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14072 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14075 o Major bugfixes (security, client, DNS proxy):
14076 - Stop a crash that could occur when a client running with DNSPort
14077 received a query with multiple address types, and the first
14078 address type was not supported. Found and fixed by Scott Dial.
14079 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14081 o Major bugfixes (security, compilation):
14082 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
14083 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
14084 cause a compiler warning, thereby making other checks fail, and
14085 needlessly disabling compiler-hardening support. Fixes one case of
14086 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
14087 - Repair hardened builds under the clang compiler. Previously, our
14088 use of _FORTIFY_SOURCE would conflict with clang's address
14089 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
14091 o Major bugfixes (security, pointers):
14092 - Avoid a difficult-to-trigger heap corruption attack when extending
14093 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14094 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14095 Reported by Guido Vranken.
14097 o Major bugfixes (testing):
14098 - Fix a bug that would block 'make test-network-all' on systems where
14099 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
14101 o Major bugfixes (user interface):
14102 - Correctly give a warning in the cases where a relay is specified
14103 by nickname, and one such relay is found, but it is not officially
14104 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
14106 o Minor features (accounting):
14107 - Added two modes to the AccountingRule option: One for limiting
14108 only the number of bytes sent ("AccountingRule out"), and one for
14109 limiting only the number of bytes received ("AccountingRule in").
14110 Closes ticket 15989; patch from "unixninja92".
14112 o Minor features (bug-resistance):
14113 - Make Tor survive errors involving connections without a
14114 corresponding event object. Previously we'd fail with an
14115 assertion; now we produce a log message. Related to bug 16248.
14116 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
14117 level code, to harden against accidental failures to NUL-
14118 terminate. Part of ticket 17852. Patch from jsturgix. Found
14121 o Minor features (build):
14122 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
14123 as having possible IPFW support. Closes ticket 18448. Patch from
14124 Steven Chamberlain.
14125 - Since our build process now uses "make distcheck", we no longer
14126 force "make dist" to depend on "make check". Closes ticket 17893;
14127 patch from "cypherpunks".
14128 - Tor now builds once again with the recent OpenSSL 1.1 development
14129 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
14130 tracking OpenSSL 1.1 development as it has progressed, and fixing
14131 numerous compatibility issues as they arose. See tickets
14132 17549, 17921, 17984, 19499, and 18286.
14133 - When building manual pages, set the timezone to "UTC", so that the
14134 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
14135 Patch from intrigeri.
14137 o Minor features (clients):
14138 - Make clients, onion services, and bridge relays always use an
14139 encrypted begindir connection for directory requests. Resolves
14140 ticket 18483. Patch by teor.
14142 o Minor features (controller):
14143 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
14144 controllers can examine the the reject rules added by
14145 ExitPolicyRejectPrivate. This makes it easier for stem to display
14147 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
14148 tickets 16774 and 17817. Patch by George Tankersley.
14149 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
14150 service descriptor from a service's local hidden service
14151 descriptor cache. Closes ticket 14846.
14153 o Minor features (crypto):
14154 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
14155 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
14157 - Improve performance when hashing non-multiple of 8 sized buffers,
14158 based on Andrew Moon's public domain SipHash-2-4 implementation.
14159 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
14160 - Validate the hard-coded Diffie-Hellman parameters and ensure that
14161 p is a safe prime, and g is a suitable generator. Closes
14163 - When allocating a digest state object, allocate no more space than
14164 we actually need. Previously, we would allocate as much space as
14165 the state for the largest algorithm would need. This change saves
14166 up to 672 bytes per circuit. Closes ticket 17796.
14168 o Minor features (directory downloads):
14169 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
14170 directory mirrors. The default is 1; set it to 0 to disable
14171 fallbacks. Implements ticket 17576. Patch by teor.
14172 - Wait for busy authorities and fallback directories to become non-
14173 busy when bootstrapping. (A similar change was made in 6c443e987d
14174 for directory caches chosen from the consensus.) Closes ticket
14175 17864; patch by teor.
14177 o Minor features (geoip):
14178 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
14181 o Minor features (hidden service directory):
14182 - Streamline relay-side hsdir handling: when relays consider whether
14183 to accept an uploaded hidden service descriptor, they no longer
14184 check whether they are one of the relays in the network that is
14185 "supposed" to handle that descriptor. Implements ticket 18332.
14187 o Minor features (IPv6):
14188 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
14189 to 1, tor prefers IPv6 directory addresses.
14190 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
14191 avoids using IPv4 for client OR and directory connections.
14192 - Add address policy assume_action support for IPv6 addresses.
14193 - Add an argument 'ipv6=address:orport' to the DirAuthority and
14194 FallbackDir torrc options, to specify an IPv6 address for an
14195 authority or fallback directory. Add hard-coded ipv6 addresses for
14196 directory authorities that have them. Closes ticket 17327; patch
14197 from Nick Mathewson and teor.
14198 - Allow users to configure directory authorities and fallback
14199 directory servers with IPv6 addresses and ORPorts. Resolves
14201 - Limit IPv6 mask bits to 128.
14202 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
14203 17638; bugfix on 0.0.2pre8. Patch by teor.
14204 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
14205 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
14206 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
14207 - Warn when comparing against an AF_UNSPEC address in a policy, it's
14208 almost always a bug. Closes ticket 17863; patch by teor.
14209 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
14210 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
14212 o Minor features (Linux seccomp2 sandbox):
14213 - Reject attempts to change our Address with "Sandbox 1" enabled.
14214 Changing Address with Sandbox turned on would never actually work,
14215 but previously it would fail in strange and confusing ways. Found
14216 while fixing 18548.
14218 o Minor features (logging):
14219 - When logging to syslog, allow a tag to be added to the syslog
14220 identity (the string prepended to every log message). The tag can
14221 be configured with SyslogIdentityTag and defaults to none. Setting
14222 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
14225 o Minor features (portability):
14226 - Use timingsafe_memcmp() where available. Closes ticket 17944;
14227 patch from <logan@hackers.mu>.
14229 o Minor features (relay, address discovery):
14230 - Add a family argument to get_interface_addresses_raw() and
14231 subfunctions to make network interface address interogation more
14232 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
14233 types of interfaces from the operating system. Resolves
14235 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
14236 fails to enumerate interface addresses using the platform-specific
14237 API, have it rely on the UDP socket fallback technique to try and
14238 find out what IP addresses (both IPv4 and IPv6) our machine has.
14239 Resolves ticket 17951.
14241 o Minor features (replay cache):
14242 - The replay cache now uses SHA256 instead of SHA1. Implements
14243 feature 8961. Patch by teor, issue reported by rransom.
14245 o Minor features (robustness):
14246 - Exit immediately with an error message if the code attempts to use
14247 Libevent without having initialized it. This should resolve some
14248 frequently-made mistakes in our unit tests. Closes ticket 18241.
14250 o Minor features (security, clock):
14251 - Warn when the system clock appears to move back in time (when the
14252 state file was last written in the future). Tor doesn't know that
14253 consensuses have expired if the clock is in the past. Patch by
14254 teor. Implements ticket 17188.
14256 o Minor features (security, exit policies):
14257 - ExitPolicyRejectPrivate now rejects more private addresses by
14258 default. Specifically, it now rejects the relay's outbound bind
14259 addresses (if configured), and the relay's configured port
14260 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
14261 0.2.0.11-alpha. Patch by teor.
14263 o Minor features (security, memory erasure):
14264 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14265 zero size. Check size argument to memwipe() for underflow. Fixes
14266 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14268 - Set the unused entries in a smartlist to NULL. This helped catch
14269 a (harmless) bug, and shouldn't affect performance too much.
14270 Implements ticket 17026.
14271 - Use SecureMemoryWipe() function to securely clean memory on
14272 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
14273 Implements feature 17986.
14274 - Use explicit_bzero or memset_s when present. Previously, we'd use
14275 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
14276 from <logan@hackers.mu> and <selven@hackers.mu>.
14278 o Minor features (security, RNG):
14279 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
14280 positively are not allowed to fail. Previously we depended on
14281 internal details of OpenSSL's behavior. Closes ticket 17686.
14282 - Never use the system entropy output directly for anything besides
14283 seeding the PRNG. When we want to generate important keys, instead
14284 of using system entropy directly, we now hash it with the PRNG
14285 stream. This may help resist certain attacks based on broken OS
14286 entropy implementations. Closes part of ticket 17694.
14287 - Use modern system calls (like getentropy() or getrandom()) to
14288 generate strong entropy on platforms that have them. Closes
14291 o Minor features (security, win32):
14292 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
14293 attack. Fixes bug 18123; bugfix on all tor versions. Patch
14296 o Minor features (unix domain sockets):
14297 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
14298 Unix domain sockets without checking the permissions on the parent
14299 directory. (Tor checks permissions by default because some
14300 operating systems only check permissions on the parent directory.
14301 However, some operating systems do look at permissions on the
14302 socket, and tor's default check is unneeded.) Closes ticket 18458.
14305 o Minor features (unix file permissions):
14306 - Defer creation of Unix sockets until after setuid. This avoids
14307 needing CAP_CHOWN and CAP_FOWNER when using systemd's
14308 CapabilityBoundingSet, or chown and fowner when using SELinux.
14309 Implements part of ticket 17562. Patch from Jamie Nguyen.
14310 - If any directory created by Tor is marked as group readable, the
14311 filesystem group is allowed to be either the default GID or the
14312 root user. Allowing root to read the DataDirectory prevents the
14313 need for CAP_READ_SEARCH when using systemd's
14314 CapabilityBoundingSet, or dac_read_search when using SELinux.
14315 Implements part of ticket 17562. Patch from Jamie Nguyen.
14316 - Introduce a new DataDirectoryGroupReadable option. If it is set to
14317 1, the DataDirectory will be made readable by the default GID.
14318 Implements part of ticket 17562. Patch from Jamie Nguyen.
14320 o Minor bugfixes (accounting):
14321 - The max bandwidth when using 'AccountRule sum' is now correctly
14322 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
14323 from "unixninja92".
14325 o Minor bugfixes (assert, portability):
14326 - Fix an assertion failure in memarea.c on systems where "long" is
14327 shorter than the size of a pointer. Fixes bug 18716; bugfix
14330 o Minor bugfixes (bootstrap):
14331 - Consistently use the consensus download schedule for authority
14332 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
14334 o Minor bugfixes (build):
14335 - Avoid spurious failures from configure files related to calling
14336 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
14337 0.2.0.1-alpha. Patch from "cypherpunks".
14338 - Do not link the unit tests against both the testing and non-
14339 testing versions of the static libraries. Fixes bug 18490; bugfix
14341 - Resolve warnings when building on systems that are concerned with
14342 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
14344 - Silence spurious clang-scan warnings in the ed25519_donna code by
14345 explicitly initializing some objects. Fixes bug 18384; bugfix on
14346 0.2.7.2-alpha. Patch by teor.
14347 - When libscrypt.h is found, but no libscrypt library can be linked,
14348 treat libscrypt as absent. Fixes bug 19161; bugfix
14350 - Cause the unit tests to compile correctly on mingw64 versions that
14351 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
14352 - Don't try to use the pthread_condattr_setclock() function unless
14353 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
14354 17819; bugfix on 0.2.6.3-alpha.
14355 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
14357 - Fix search for libevent libraries on OpenBSD (and other systems
14358 that install libevent 1 and libevent 2 in parallel). Fixes bug
14359 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
14360 - Isolate environment variables meant for tests from the rest of the
14361 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
14362 - Mark all object files that include micro-revision.i as depending
14363 on it, so as to make parallel builds more reliable. Fixes bug
14364 17826; bugfix on 0.2.5.1-alpha.
14365 - Remove config.log only from make distclean, not from make clean.
14366 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
14367 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
14369 - Remove an #endif from configure.ac so that we correctly detect the
14370 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
14373 o Minor bugfixes (client, bootstrap):
14374 - Count receipt of new microdescriptors as progress towards
14375 bootstrapping. Previously, with EntryNodes set, Tor might not
14376 successfully repopulate the guard set on bootstrapping. Fixes bug
14377 16825; bugfix on 0.2.3.1-alpha.
14379 o Minor bugfixes (code correctness):
14380 - Fix a bad memory handling bug that would occur if we had queued a
14381 cell on a channel's incoming queue. Fortunately, we can't actually
14382 queue a cell like that as our code is constructed today, but it's
14383 best to avoid this kind of error, even if there isn't any code
14384 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
14385 - Assert that allocated memory held by the reputation code is freed
14386 according to its internal counters. Fixes bug 17753; bugfix
14388 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
14390 - Update to the latest version of Trunnel, which tries harder to
14391 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
14392 by clang address sanitizer. Fixes bug 18373; bugfix
14394 - When closing an entry connection, generate a warning if we should
14395 have sent an end cell for it but we haven't. Fixes bug 17876;
14396 bugfix on 0.2.3.2-alpha.
14398 o Minor bugfixes (configuration):
14399 - Fix a tiny memory leak when parsing a port configuration ending in
14400 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
14402 o Minor bugfixes (containers):
14403 - If we somehow attempt to construct a heap with more than
14404 1073741822 elements, avoid an integer overflow when maintaining
14405 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
14407 o Minor bugfixes (controller, microdescriptors):
14408 - Make GETINFO dir/status-vote/current/consensus conform to the
14409 control specification by returning "551 Could not open cached
14410 consensus..." when not caching consensuses. Fixes bug 18920;
14411 bugfix on 0.2.2.6-alpha.
14413 o Minor bugfixes (crypto):
14414 - Check the return value of HMAC() and assert on failure. Fixes bug
14415 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
14417 o Minor bugfixes (directories):
14418 - When fetching extrainfo documents, compare their SHA256 digests
14419 and Ed25519 signing key certificates with the routerinfo that led
14420 us to fetch them, rather than with the most recent routerinfo.
14421 Otherwise we generate many spurious warnings about mismatches.
14422 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
14423 - When generating a URL for a directory server on an IPv6 address,
14424 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
14425 on 0.2.3.9-alpha. Patch from Malek.
14427 o Minor bugfixes (downloading):
14428 - Predict more correctly whether we'll be downloading over HTTP when
14429 we determine the maximum length of a URL. This should avoid a
14430 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
14433 o Minor bugfixes (exit policies, security):
14434 - Refresh an exit relay's exit policy when interface addresses
14435 change. Previously, tor only refreshed the exit policy when the
14436 configured external address changed. Fixes bug 18208; bugfix on
14437 0.2.7.3-rc. Patch by teor.
14439 o Minor bugfixes (fallback directories):
14440 - Mark fallbacks as "too busy" when they return a 503 response,
14441 rather than just marking authorities. Fixes bug 17572; bugfix on
14442 0.2.4.7-alpha. Patch by teor.
14443 - When requesting extrainfo descriptors from a trusted directory
14444 server, check whether it is an authority or a fallback directory
14445 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
14446 0.2.4.7-alpha. Reported by atagar, patch by teor.
14448 o Minor bugfixes (hidden service, client):
14449 - Handle the case where the user makes several fast consecutive
14450 requests to the same .onion address. Previously, the first six
14451 requests would each trigger a descriptor fetch, each picking a
14452 directory (there are 6 overall) and the seventh one would fail
14453 because no directories were left, thereby triggering a close on
14454 all current directory connections asking for the hidden service.
14455 The solution here is to not close the connections if we have
14456 pending directory fetches. Fixes bug 15937; bugfix
14459 o Minor bugfixes (hidden service, control port):
14460 - Add the onion address to the HS_DESC event for the UPLOADED action
14461 both on success or failure. It was previously hardcoded with
14462 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
14464 o Minor bugfixes (hidden service, directory):
14465 - Bridges now refuse "rendezvous2" (hidden service descriptor)
14466 publish attempts. Suggested by ticket 18332.
14468 o Minor bugfixes (IPv6):
14469 - Update the limits in max_dl_per_request for IPv6 address length.
14470 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
14472 o Minor bugfixes (Linux seccomp2 sandbox):
14473 - Allow more syscalls when running with "Sandbox 1" enabled:
14474 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
14475 some systems, these are required for Tor to start. Fixes bug
14476 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
14477 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
14478 so that get_interface_address6_via_udp_socket_hack() can work.
14479 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
14480 - Allow the setrlimit syscall, and the prlimit and prlimit64
14481 syscalls, which some libc implementations use under the hood.
14482 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
14483 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
14484 enabled and no DNS resolvers configured. This should help TAILS
14485 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
14486 - Fix a crash when using offline master ed25519 keys with the Linux
14487 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
14488 - Allow statistics to be written to disk when "Sandbox 1" is
14489 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
14490 0.2.6.1-alpha respectively.
14492 o Minor bugfixes (logging):
14493 - In log messages that include a function name, use __FUNCTION__
14494 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
14495 with clang __PRETTY_FUNCTION__ has extra information we don't
14496 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
14498 - Remove needless quotes from a log message about unparseable
14499 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
14500 - Scrub service name in "unrecognized service ID" log messages.
14501 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
14502 - When logging information about an unparsable networkstatus vote or
14503 consensus, do not say "vote" when we mean consensus. Fixes bug
14504 18368; bugfix on 0.2.0.8-alpha.
14505 - When we can't generate a signing key because OfflineMasterKey is
14506 set, do not imply that we should have been able to load it. Fixes
14507 bug 18133; bugfix on 0.2.7.2-alpha.
14508 - When logging a malformed hostname received through socks4, scrub
14509 it if SafeLogging says we should. Fixes bug 17419; bugfix
14512 o Minor bugfixes (memory safety):
14513 - Avoid freeing an uninitialized pointer when opening a socket fails
14514 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
14515 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
14517 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
14518 18672; bugfix on 0.2.5.1-alpha.
14519 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
14522 o Minor bugfixes (pluggable transports):
14523 - Avoid reporting a spurious error when we decide that we don't need
14524 to terminate a pluggable transport because it has already exited.
14525 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
14527 o Minor bugfixes (pointer arithmetic):
14528 - Fix a bug in memarea_alloc() that could have resulted in remote
14529 heap write access, if Tor had ever passed an unchecked size to
14530 memarea_alloc(). Fortunately, all the sizes we pass to
14531 memarea_alloc() are pre-checked to be less than 128 kilobytes.
14532 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
14535 o Minor bugfixes (private directory):
14536 - Prevent a race condition when creating private directories. Fixes
14537 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
14538 Patch from jsturgix. Found with Flawfinder.
14540 o Minor bugfixes (relays):
14541 - Check that both the ORPort and DirPort (if present) are reachable
14542 before publishing a relay descriptor. Otherwise, relays publish a
14543 descriptor with DirPort 0 when the DirPort reachability test takes
14544 longer than the ORPort reachability test. Fixes bug 18050; bugfix
14545 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
14546 - Resolve some edge cases where we might launch an ORPort
14547 reachability check even when DisableNetwork is set. Noticed while
14548 fixing bug 18616; bugfix on 0.2.3.9-alpha.
14550 o Minor bugfixes (relays, hidden services):
14551 - Refuse connection requests to private OR addresses unless
14552 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
14553 then refuse to send any cells to a private address. Fixes bugs
14554 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
14556 o Minor bugfixes (security, hidden services):
14557 - Prevent hidden services connecting to client-supplied rendezvous
14558 addresses that are reserved as internal or multicast. Fixes bug
14559 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
14561 o Minor bugfixes (statistics):
14562 - Consistently check for overflow in round_*_to_next_multiple_of
14563 functions, and add unit tests with additional and maximal values.
14564 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
14565 - Handle edge cases in the laplace functions: avoid division by
14566 zero, avoid taking the log of zero, and silence clang type
14567 conversion warnings using round and trunc. Add unit tests for edge
14568 cases with maximal values. Fixes part of bug 13192; bugfix
14570 - We now include consensus downloads via IPv6 in our directory-
14571 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
14573 o Minor bugfixes (test networks, IPv6):
14574 - Allow internal IPv6 addresses in descriptors in test networks.
14575 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
14578 o Minor bugfixes (testing):
14579 - Check the full results of SHA256 and SHA512 digests in the unit
14580 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
14581 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
14583 - Fix a small memory leak that would occur when the
14584 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
14585 bugfix on 0.2.5.2-alpha.
14586 - Make unit tests pass on IPv6-only systems, and systems without
14587 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
14588 bugfix on 0.2.7.3-rc. Patch by teor.
14589 - The test for log_heartbeat was incorrectly failing in timezones
14590 with non-integer offsets. Instead of comparing the end of the time
14591 string against a constant, compare it to the output of
14592 format_local_iso_time when given the correct input. Fixes bug
14593 18039; bugfix on 0.2.5.4-alpha.
14594 - We no longer disable assertions in the unit tests when coverage is
14595 enabled. Instead, we require you to say --disable-asserts-in-tests
14596 to the configure script if you need assertions disabled in the
14597 unit tests (for example, if you want to perform branch coverage).
14598 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
14600 o Minor bugfixes (time handling):
14601 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
14602 field. Otherwise, our unit tests crash on Windows. Fixes bug
14603 18977; bugfix on 0.2.2.25-alpha.
14604 - Avoid overflow in tor_timegm when parsing dates in and after 2038
14605 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
14606 0.0.2pre14. Patch by teor.
14608 o Minor bugfixes (tor-gencert):
14609 - Correctly handle the case where an authority operator enters a
14610 passphrase but sends an EOF before sending a newline. Fixes bug
14611 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
14613 o Code simplification and refactoring:
14614 - Clean up a little duplicated code in
14615 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
14617 - Decouple the list of streams waiting to be attached to circuits
14618 from the overall connection list. This change makes it possible to
14619 attach streams quickly while simplifying Tor's callgraph and
14620 avoiding O(N) scans of the entire connection list. Closes
14622 - Extract the more complicated parts of circuit_mark_for_close()
14623 into a new function that we run periodically before circuits are
14624 freed. This change removes more than half of the functions
14625 currently in the "blob". Closes ticket 17218.
14626 - Move logging of redundant policy entries in
14627 policies_parse_exit_policy_internal into its own function. Closes
14628 ticket 17608; patch from "juce".
14629 - Quote all the string interpolations in configure.ac -- even those
14630 which we are pretty sure can't contain spaces. Closes ticket
14631 17744. Patch from zerosion.
14632 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
14633 use them. Closes ticket 17926.
14634 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
14635 inplace, so there's no need to have a separate implementation for
14636 the non-inplace code. Closes ticket 18258. Patch from Malek.
14637 - Simplify return types for some crypto functions that can't
14638 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
14639 - When a direct directory request fails immediately on launch,
14640 instead of relaunching that request from inside the code that
14641 launches it, instead mark the connection for teardown. This change
14642 simplifies Tor's callback and prevents the directory-request
14643 launching code from invoking itself recursively. Closes
14647 - Add a description of the correct use of the '--keygen' command-
14648 line option. Closes ticket 17583; based on text by 's7r'.
14649 - Change build messages to refer to "Fedora" instead of "Fedora
14650 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
14651 Patches from "icanhasaccount" and "cypherpunks".
14652 - Document the contents of the 'datadir/keys' subdirectory in the
14653 manual page. Closes ticket 17621.
14654 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
14655 - Explain actual minima for BandwidthRate. Closes ticket 16382.
14656 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
14657 - Mention torspec URL in the manpage and point the reader to it
14658 whenever we mention a document that belongs in torspce. Fixes
14660 - Stop recommending use of nicknames to identify relays in our
14661 MapAddress documentation. Closes ticket 18312.
14663 o Removed features:
14664 - Remove client-side support for connecting to Tor relays running
14665 versions of Tor before 0.2.3.6-alpha. These relays didn't support
14666 the v3 TLS handshake protocol, and are no longer allowed on the
14667 Tor network. Implements the client side of ticket 11150. Based on
14668 patches by Tom van der Woerdt.
14669 - We no longer maintain an internal freelist in memarea.c.
14670 Allocators should be good enough to make this code unnecessary,
14671 and it's doubtful that it ever had any performance benefit.
14674 - Add unit tests to check for common RNG failure modes, such as
14675 returning all zeroes, identical values, or incrementing values
14676 (OpenSSL's rand_predictable feature). Patch by teor.
14677 - Always test both ed25519 backends, so that we can be sure that our
14678 batch-open replacement code works. Part of ticket 16794.
14679 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
14680 portion of ticket 16831.
14681 - Fix several warnings from clang's address sanitizer produced in
14683 - Log more information when the backtrace tests fail. Closes ticket
14684 17892. Patch from "cypherpunks."
14685 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
14686 util_format.c, directory.c, and options_validate.c. Closes tickets
14687 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
14689 - Treat backtrace test failures as expected on FreeBSD until we
14690 solve bug 17808. Closes ticket 18204.
14691 - Unit tests for directory_handle_command_get. Closes ticket 17004.
14692 Patch from Reinaldo de Souza Jr.
14695 Changes in version 0.2.7.6 - 2015-12-10
14696 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
14697 well as a minor bug in hidden service reliability.
14699 o Major bugfixes (guard selection):
14700 - Actually look at the Guard flag when selecting a new directory
14701 guard. When we implemented the directory guard design, we
14702 accidentally started treating all relays as if they have the Guard
14703 flag during guard selection, leading to weaker anonymity and worse
14704 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14707 o Minor features (geoip):
14708 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
14711 o Minor bugfixes (compilation):
14712 - When checking for net/pfvar.h, include netinet/in.h if possible.
14713 This fixes transparent proxy detection on OpenBSD. Fixes bug
14714 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
14715 - Fix a compilation warning with Clang 3.6: Do not check the
14716 presence of an address which can never be NULL. Fixes bug 17781.
14718 o Minor bugfixes (correctness):
14719 - When displaying an IPv6 exit policy, include the mask bits
14720 correctly even when the number is greater than 31. Fixes bug
14721 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
14722 - The wrong list was used when looking up expired intro points in a
14723 rend service object, causing what we think could be reachability
14724 issues for hidden services, and triggering a BUG log. Fixes bug
14725 16702; bugfix on 0.2.7.2-alpha.
14726 - Fix undefined behavior in the tor_cert_checksig function. Fixes
14727 bug 17722; bugfix on 0.2.7.2-alpha.
14730 Changes in version 0.2.7.5 - 2015-11-20
14731 The Tor 0.2.7 release series is dedicated to the memory of Tor user
14732 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
14733 tirelessly to advocate human rights regardless of national borders,
14734 and oppose the encroachments of mass surveillance. He opposed national
14735 exceptionalism, he brought clarity to legal and policy debates, he
14736 understood and predicted the impact of mass surveillance on the world,
14737 and he laid the groundwork for resisting it. While serving on the Tor
14738 Project's board of directors, he brought us his uncompromising focus
14739 on technical excellence in the service of humankind. Caspar was an
14740 inimitable force for good and a wonderful friend. He was kind,
14741 humorous, generous, gallant, and believed we should protect one
14742 another without exception. We honor him here for his ideals, his
14743 efforts, and his accomplishments. Please honor his memory with works
14744 that would make him proud.
14746 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
14748 The 0.2.7 series adds a more secure identity key type for relays,
14749 improves cryptography performance, resolves several longstanding
14750 hidden-service performance issues, improves controller support for
14751 hidden services, and includes small bugfixes and performance
14752 improvements throughout the program. This release series also includes
14753 more tests than before, and significant simplifications to which parts
14754 of Tor invoke which others. For a full list of changes, see below.
14756 o New system requirements:
14757 - Tor no longer includes workarounds to support Libevent versions
14758 before 1.3e. Libevent 2.0 or later is recommended. Closes
14760 - Tor no longer supports copies of OpenSSL that are missing support
14761 for Elliptic Curve Cryptography. (We began using ECC when
14762 available in 0.2.4.8-alpha, for more safe and efficient key
14763 negotiation.) In particular, support for at least one of P256 or
14764 P224 is now required, with manual configuration needed if only
14765 P224 is available. Resolves ticket 16140.
14766 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
14767 on an operating system that has not upgraded to OpenSSL 1.0 or
14768 later, and you compile Tor from source, you will need to install a
14769 more recent OpenSSL to link Tor against.) These versions of
14770 OpenSSL are still supported by the OpenSSL, but the numerous
14771 cryptographic improvements in later OpenSSL releases makes them a
14772 clear choice. Resolves ticket 16034.
14774 o Major features (controller):
14775 - Add the ADD_ONION and DEL_ONION commands that allow the creation
14776 and management of hidden services via the controller. Closes
14778 - New "GETINFO onions/current" and "GETINFO onions/detached"
14779 commands to get information about hidden services created via the
14780 controller. Part of ticket 6411.
14781 - New HSFETCH command to launch a request for a hidden service
14782 descriptor. Closes ticket 14847.
14783 - New HSPOST command to upload a hidden service descriptor. Closes
14784 ticket 3523. Patch by "DonnchaC".
14786 o Major features (Ed25519 identity keys, Proposal 220):
14787 - Add support for offline encrypted Ed25519 master keys. To use this
14788 feature on your tor relay, run "tor --keygen" to make a new master
14789 key (or to make a new signing key if you already have a master
14790 key). Closes ticket 13642.
14791 - All relays now maintain a stronger identity key, using the Ed25519
14792 elliptic curve signature format. This master key is designed so
14793 that it can be kept offline. Relays also generate an online
14794 signing key, and a set of other Ed25519 keys and certificates.
14795 These are all automatically regenerated and rotated as needed.
14796 Implements part of ticket 12498.
14797 - Directory authorities now vote on Ed25519 identity keys along with
14798 RSA1024 keys. Implements part of ticket 12498.
14799 - Directory authorities track which Ed25519 identity keys have been
14800 used with which RSA1024 identity keys, and do not allow them to
14801 vary freely. Implements part of ticket 12498.
14802 - Microdescriptors now include Ed25519 identity keys. Implements
14803 part of ticket 12498.
14804 - Add a --newpass option to allow changing or removing the
14805 passphrase of an encrypted key with tor --keygen. Implements part
14807 - Add a new OfflineMasterKey option to tell Tor never to try loading
14808 or generating a secret Ed25519 identity key. You can use this in
14809 combination with tor --keygen to manage offline and/or encrypted
14810 Ed25519 keys. Implements ticket 16944.
14811 - On receiving a HUP signal, check to see whether the Ed25519
14812 signing key has changed, and reload it if so. Closes ticket 16790.
14813 - Significant usability improvements for Ed25519 key management. Log
14814 messages are better, and the code can recover from far more
14815 failure conditions. Thanks to "s7r" for reporting and diagnosing
14818 o Major features (ECC performance):
14819 - Improve the runtime speed of Ed25519 signature verification by
14820 using Ed25519-donna's batch verification support. Implements
14822 - Improve the speed of Ed25519 operations and Curve25519 keypair
14823 generation when built targeting 32 bit x86 platforms with SSE2
14824 available. Implements ticket 16535.
14825 - Improve the runtime speed of Ed25519 operations by using the
14826 public-domain Ed25519-donna by Andrew M. ("floodyberry").
14827 Implements ticket 16467.
14828 - Improve the runtime speed of the ntor handshake by using an
14829 optimized curve25519 basepoint scalarmult implementation from the
14830 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
14831 ideas by Adam Langley. Implements ticket 9663.
14833 o Major features (Hidden services):
14834 - Hidden services, if using the EntryNodes option, are required to
14835 use more than one EntryNode, in order to avoid a guard discovery
14836 attack. (This would only affect people who had configured hidden
14837 services and manually specified the EntryNodes option with a
14838 single entry-node. The impact was that it would be easy to
14839 remotely identify the guard node used by such a hidden service.
14840 See ticket for more information.) Fixes ticket 14917.
14841 - Add the torrc option HiddenServiceNumIntroductionPoints, to
14842 specify a fixed number of introduction points. Its maximum value
14843 is 10 and default is 3. Using this option can increase a hidden
14844 service's reliability under load, at the cost of making it more
14845 visible that the hidden service is facing extra load. Closes
14847 - Remove the adaptive algorithm for choosing the number of
14848 introduction points, which used to change the number of
14849 introduction points (poorly) depending on the number of
14850 connections the HS sees. Closes ticket 4862.
14852 o Major features (onion key cross-certification):
14853 - Relay descriptors now include signatures of their own identity
14854 keys, made using the TAP and ntor onion keys. These signatures
14855 allow relays to prove ownership of their own onion keys. Because
14856 of this change, microdescriptors will no longer need to include
14857 RSA identity keys. Implements proposal 228; closes ticket 12499.
14859 o Major bugfixes (client-side privacy, also in 0.2.6.9):
14860 - Properly separate out each SOCKSPort when applying stream
14861 isolation. The error occurred because each port's session group
14862 was being overwritten by a default value when the listener
14863 connection was initialized. Fixes bug 16247; bugfix on
14864 0.2.6.3-alpha. Patch by "jojelino".
14866 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
14867 - Stop refusing to store updated hidden service descriptors on a
14868 client. This reverts commit 9407040c59218 (which indeed fixed bug
14869 14219, but introduced a major hidden service reachability
14870 regression detailed in bug 16381). This is a temporary fix since
14871 we can live with the minor issue in bug 14219 (it just results in
14872 some load on the network) but the regression of 16381 is too much
14873 of a setback. First-round fix for bug 16381; bugfix
14876 o Major bugfixes (hidden services):
14877 - Revert commit that made directory authorities assign the HSDir
14878 flag to relays without a DirPort; this was bad because such relays
14879 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
14881 - When cannibalizing a circuit for an introduction point, always
14882 extend to the chosen exit node (creating a 4 hop circuit).
14883 Previously Tor would use the current circuit exit node, which
14884 changed the original choice of introduction point, and could cause
14885 the hidden service to skip excluded introduction points or
14886 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
14889 o Major bugfixes (memory leaks):
14890 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
14891 17398; bugfix on 0.2.6.1-alpha.
14893 o Major bugfixes (open file limit):
14894 - The open file limit wasn't checked before calling
14895 tor_accept_socket_nonblocking(), which would make Tor exceed the
14896 limit. Now, before opening a new socket, Tor validates the open
14897 file limit just before, and if the max has been reached, return an
14898 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
14900 o Major bugfixes (security, correctness):
14901 - Fix an error that could cause us to read 4 bytes before the
14902 beginning of an openssl string. This bug could be used to cause
14903 Tor to crash on systems with unusual malloc implementations, or
14904 systems with unusual hardening installed. Fixes bug 17404; bugfix
14907 o Major bugfixes (stability, also in 0.2.6.10):
14908 - Stop crashing with an assertion failure when parsing certain kinds
14909 of malformed or truncated microdescriptors. Fixes bug 16400;
14910 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
14911 by "cypherpunks_backup".
14912 - Stop random client-side assertion failures that could occur when
14913 connecting to a busy hidden service, or connecting to a hidden
14914 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
14917 o Minor features (client, SOCKS):
14918 - Add GroupWritable and WorldWritable options to unix-socket based
14919 SocksPort and ControlPort options. These options apply to a single
14920 socket, and override {Control,Socks}SocketsGroupWritable. Closes
14922 - Relax the validation done to hostnames in SOCKS5 requests, and
14923 allow a single trailing '.' to cope with clients that pass FQDNs
14924 using that syntax to explicitly indicate that the domain name is
14925 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
14926 - Relax the validation of hostnames in SOCKS5 requests, allowing the
14927 character '_' to appear, in order to cope with domains observed in
14928 the wild that are serving non-RFC compliant records. Resolves
14931 o Minor features (client-side privacy):
14932 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
14933 lifespan when IsolateSOCKSAuth and streams with SOCKS
14934 authentication are attached to the circuit. This allows
14935 applications like TorBrowser to manage circuit lifetime on their
14936 own. Implements feature 15482.
14937 - When logging malformed hostnames from SOCKS5 requests, respect
14938 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
14940 o Minor features (clock-jump tolerance):
14941 - Recover better when our clock jumps back many hours, like might
14942 happen for Tails or Whonix users who start with a very wrong
14943 hardware clock, use Tor to discover a more accurate time, and then
14944 fix their clock. Resolves part of ticket 8766.
14946 o Minor features (command-line interface):
14947 - Make --hash-password imply --hush to prevent unnecessary noise.
14948 Closes ticket 15542. Patch from "cypherpunks".
14949 - Print a warning whenever we find a relative file path being used
14950 as torrc option. Resolves issue 14018.
14952 o Minor features (compilation):
14953 - Give a warning as early as possible when trying to build with an
14954 unsupported OpenSSL version. Closes ticket 16901.
14955 - Use C99 variadic macros when the compiler is not GCC. This avoids
14956 failing compilations on MSVC, and fixes a log-file-based race
14957 condition in our old workarounds. Original patch from Gisle Vanem.
14959 o Minor features (control protocol):
14960 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
14961 the control protocol. Resolves ticket 15358.
14963 o Minor features (controller):
14964 - Add DirAuthority lines for default directory authorities to the
14965 output of the "GETINFO config/defaults" command if not already
14966 present. Implements ticket 14840.
14967 - Controllers can now use "GETINFO hs/client/desc/id/..." to
14968 retrieve items from the client's hidden service descriptor cache.
14969 Closes ticket 14845.
14970 - Implement a new controller command "GETINFO status/fresh-relay-
14971 descs" to fetch a descriptor/extrainfo pair that was generated on
14972 demand just for the controller's use. Implements ticket 14784.
14974 o Minor features (directory authorities):
14975 - Directory authorities no longer vote against the "Fast", "Stable",
14976 and "HSDir" flags just because they were going to vote against
14977 "Running": if the consensus turns out to be that the router was
14978 running, then the authority's vote should count. Patch from Peter
14979 Retzlaff; closes issue 8712.
14981 o Minor features (directory authorities, security, also in 0.2.6.9):
14982 - The HSDir flag given by authorities now requires the Stable flag.
14983 For the current network, this results in going from 2887 to 2806
14984 HSDirs. Also, it makes it harder for an attacker to launch a sybil
14985 attack by raising the effort for a relay to become Stable to
14986 require at the very least 7 days, while maintaining the 96 hours
14987 uptime requirement for HSDir. Implements ticket 8243.
14989 o Minor features (DoS-resistance):
14990 - Make it harder for attackers to overload hidden services with
14991 introductions, by blocking multiple introduction requests on the
14992 same circuit. Resolves ticket 15515.
14994 o Minor features (geoip):
14995 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
14998 o Minor features (hidden services):
14999 - Add the new options "HiddenServiceMaxStreams" and
15000 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
15001 limit the maximum number of simultaneous streams per circuit, and
15002 optionally tear down the circuit when the limit is exceeded. Part
15004 - Client now uses an introduction point failure cache to know when
15005 to fetch or keep a descriptor in their cache. Previously, failures
15006 were recorded implicitly, but not explicitly remembered. Closes
15008 - Relays need to have the Fast flag to get the HSDir flag. As this
15009 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
15010 drop. This change should make some attacks against the hidden
15011 service directory system harder. Fixes ticket 15963.
15012 - Turn on hidden service statistics collection by setting the torrc
15013 option HiddenServiceStatistics to "1" by default. (This keeps
15014 track only of the fraction of traffic used by hidden services, and
15015 the total number of hidden services in existence.) Closes
15017 - To avoid leaking HS popularity, don't cycle the introduction point
15018 when we've handled a fixed number of INTRODUCE2 cells but instead
15019 cycle it when a random number of introductions is reached, thus
15020 making it more difficult for an attacker to find out the amount of
15021 clients that have used the introduction point for a specific HS.
15022 Closes ticket 15745.
15024 o Minor features (logging):
15025 - Include the Tor version in all LD_BUG log messages, since people
15026 tend to cut and paste those into the bugtracker. Implements
15029 o Minor features (pluggable transports):
15030 - When launching managed pluggable transports on Linux systems,
15031 attempt to have the kernel deliver a SIGTERM on tor exit if the
15032 pluggable transport process is still running. Resolves
15034 - When launching managed pluggable transports, setup a valid open
15035 stdin in the child process that can be used to detect if tor has
15036 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
15037 can be used by implementations to detect this new behavior.
15038 Resolves ticket 15435.
15040 o Minor bugfixes (torrc exit policies):
15041 - In each instance above, usage advice is provided to avoid the
15042 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
15043 16069; bugfix on 0.2.4.7-alpha.
15044 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
15045 produce IPv6 wildcard addresses. Previously they would produce
15046 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
15047 of bug 16069; bugfix on 0.2.4.7-alpha.
15048 - When parsing torrc ExitPolicies, we now issue an info-level
15049 message when expanding an "accept/reject *" line to include both
15050 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
15051 - When parsing torrc ExitPolicies, we now warn for a number of cases
15052 where the user's intent is likely to differ from Tor's actual
15053 behavior. These include: using an IPv4 address with an accept6 or
15054 reject6 line; using "private" on an accept6 or reject6 line; and
15055 including any ExitPolicy lines after accept *:* or reject *:*.
15056 Related to ticket 16069.
15058 o Minor bugfixes (command-line interface):
15059 - When "--quiet" is provided along with "--validate-config", do not
15060 write anything to stdout on success. Fixes bug 14994; bugfix
15062 - When complaining about bad arguments to "--dump-config", use
15063 stderr, not stdout.
15064 - Print usage information for --dump-config when it is used without
15065 an argument. Also, fix the error message to use different wording
15066 and add newline at the end. Fixes bug 15541; bugfix
15069 o Minor bugfixes (compilation):
15070 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15071 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15072 - Repair compilation with the most recent (unreleased, alpha)
15073 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
15075 o Minor bugfixes (compilation, also in 0.2.6.9):
15076 - Build with --enable-systemd correctly when libsystemd is
15077 installed, but systemd is not. Fixes bug 16164; bugfix on
15078 0.2.6.3-alpha. Patch from Peter Palfrader.
15080 o Minor bugfixes (configuration, unit tests):
15081 - Only add the default fallback directories when the DirAuthorities,
15082 AlternateDirAuthority, and FallbackDir directory config options
15083 are set to their defaults. The default fallback directory list is
15084 currently empty, this fix will only change tor's behavior when it
15085 has default fallback directories. Includes unit tests for
15086 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
15087 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
15089 o Minor bugfixes (controller):
15090 - Add the descriptor ID in each HS_DESC control event. It was
15091 missing, but specified in control-spec.txt. Fixes bug 15881;
15092 bugfix on 0.2.5.2-alpha.
15094 o Minor bugfixes (correctness):
15095 - For correctness, avoid modifying a constant string in
15096 handle_control_postdescriptor. Fixes bug 15546; bugfix
15098 - Remove side-effects from tor_assert() calls. This was harmless,
15099 because we never disable assertions, but it is bad style and
15100 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
15102 - When calling channel_free_list(), avoid calling smartlist_remove()
15103 while inside a FOREACH loop. This partially reverts commit
15104 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
15105 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
15107 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
15108 - Check for failures from crypto_early_init, and refuse to continue.
15109 A previous typo meant that we could keep going with an
15110 uninitialized crypto library, and would have OpenSSL initialize
15111 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15112 when implementing ticket 4900. Patch by "teor".
15114 o Minor bugfixes (hidden service):
15115 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15116 a client authorized hidden service. Fixes bug 15823; bugfix
15118 - Remove an extraneous newline character from the end of hidden
15119 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
15121 o Minor bugfixes (Linux seccomp2 sandbox):
15122 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
15123 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
15124 - Allow bridge authorities to run correctly under the seccomp2
15125 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
15126 - Add the "hidserv-stats" filename to our sandbox filter for the
15127 HiddenServiceStatistics option to work properly. Fixes bug 17354;
15128 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
15130 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
15131 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15132 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15133 on 0.2.6.3-alpha. Patch from "teor".
15135 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
15136 - Allow systemd connections to work with the Linux seccomp2 sandbox
15137 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
15139 - Fix sandboxing to work when running as a relay, by allowing the
15140 renaming of secret_id_key, and allowing the eventfd2 and futex
15141 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
15144 o Minor bugfixes (logging):
15145 - When building Tor under Clang, do not include an extra set of
15146 parentheses in log messages that include function names. Fixes bug
15147 15269; bugfix on every released version of Tor when compiled with
15148 recent enough Clang.
15150 o Minor bugfixes (network):
15151 - When attempting to use fallback technique for network interface
15152 lookup, disregard loopback and multicast addresses since they are
15153 unsuitable for public communications.
15155 o Minor bugfixes (open file limit):
15156 - Fix set_max_file_descriptors() to set by default the max open file
15157 limit to the current limit when setrlimit() fails. Fixes bug
15158 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
15160 o Minor bugfixes (portability):
15161 - Check correctly for Windows socket errors in the workqueue
15162 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
15163 - Try harder to normalize the exit status of the Tor process to the
15164 standard-provided range. Fixes bug 16975; bugfix on every version
15166 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
15167 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
15169 o Minor bugfixes (relay):
15170 - Ensure that worker threads actually exit when a fatal error or
15171 shutdown is indicated. This fix doesn't currently affect the
15172 behavior of Tor, because Tor workers never indicates fatal error
15173 or shutdown except in the unit tests. Fixes bug 16868; bugfix
15175 - Fix a rarely-encountered memory leak when failing to initialize
15176 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
15177 from "cypherpunks".
15178 - Unblock threads before releasing the work queue mutex to ensure
15179 predictable scheduling behavior. Fixes bug 16644; bugfix
15182 o Minor bugfixes (security, exit policies):
15183 - ExitPolicyRejectPrivate now also rejects the relay's published
15184 IPv6 address (if any), and any publicly routable IPv4 or IPv6
15185 addresses on any local interfaces. ticket 17027. Patch by "teor".
15186 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
15188 o Minor bugfixes (statistics):
15189 - Disregard the ConnDirectionStatistics torrc options when Tor is
15190 not a relay since in that mode of operation no sensible data is
15191 being collected and because Tor might run into measurement hiccups
15192 when running as a client for some time, then becoming a relay.
15193 Fixes bug 15604; bugfix on 0.2.2.35.
15195 o Minor bugfixes (systemd):
15196 - Tor's systemd unit file no longer contains extraneous spaces.
15197 These spaces would sometimes confuse tools like deb-systemd-
15198 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
15200 o Minor bugfixes (test networks):
15201 - When self-testing reachability, use ExtendAllowPrivateAddresses to
15202 determine if local/private addresses imply reachability. The
15203 previous fix used TestingTorNetwork, which implies
15204 ExtendAllowPrivateAddresses, but this excluded rare configurations
15205 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
15206 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
15207 issue discovered by CJ Ess.
15209 o Minor bugfixes (tests, also in 0.2.6.9):
15210 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
15211 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
15213 o Code simplification and refactoring:
15214 - Change the function that's called when we need to retry all
15215 downloads so that it only reschedules the downloads to happen
15216 immediately, rather than launching them all at once itself. This
15217 further simplifies Tor's callgraph.
15218 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
15219 to ensure they remain consistent and visible everywhere.
15220 - Move some format-parsing functions out of crypto.c and
15221 crypto_curve25519.c into crypto_format.c and/or util_format.c.
15222 - Move the client-only parts of init_keys() into a separate
15223 function. Closes ticket 16763.
15224 - Move the hacky fallback code out of get_interface_address6() into
15225 separate function and get it covered with unit-tests. Resolves
15227 - Refactor hidden service client-side cache lookup to intelligently
15228 report its various failure cases, and disentangle failure cases
15229 involving a lack of introduction points. Closes ticket 14391.
15230 - Remove some vestigial workarounds for the MSVC6 compiler. We
15231 haven't supported that in ages.
15232 - Remove the unused "nulterminate" argument from buf_pullup().
15233 - Simplify the microdesc_free() implementation so that it no longer
15234 appears (to code analysis tools) to potentially invoke a huge
15235 suite of other microdesc functions.
15236 - Simply the control graph further by deferring the inner body of
15237 directory_all_unreachable() into a callback. Closes ticket 16762.
15238 - The link authentication code has been refactored for better
15239 testability and reliability. It now uses code generated with the
15240 "trunnel" binary encoding generator, to reduce the risk of bugs
15241 due to programmer error. Done as part of ticket 12498.
15242 - Treat the loss of an owning controller as equivalent to a SIGTERM
15243 signal. This removes a tiny amount of duplicated code, and
15244 simplifies our callgraph. Closes ticket 16788.
15245 - Use our own Base64 encoder instead of OpenSSL's, to allow more
15246 control over the output. Part of ticket 15652.
15247 - When generating an event to send to the controller, we no longer
15248 put the event over the network immediately. Instead, we queue
15249 these events, and use a Libevent callback to deliver them. This
15250 change simplifies Tor's callgraph by reducing the number of
15251 functions from which all other Tor functions are reachable. Closes
15253 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
15254 that try to scan or compile every file on Unix won't decide that
15258 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
15259 - Improve the descriptions of statistics-related torrc options in
15260 the manpage to describe rationale and possible uses cases. Fixes
15262 - Improve the layout and formatting of ./configure --help messages.
15263 Closes ticket 15024. Patch from "cypherpunks".
15264 - Include a specific and (hopefully) accurate documentation of the
15265 torrc file's meta-format in doc/torrc_format.txt. This is mainly
15266 of interest to people writing programs to parse or generate torrc
15267 files. This document is not a commitment to long-term
15268 compatibility; some aspects of the current format are a bit
15269 ridiculous. Closes ticket 2325.
15270 - Include the TUNING document in our source tarball. It is referred
15271 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
15273 - Note that HiddenServicePorts can take a unix domain socket. Closes
15275 - Recommend a 40 GB example AccountingMax in torrc.sample rather
15276 than a 4 GB max. Closes ticket 16742.
15277 - Standardize on the term "server descriptor" in the manual page.
15278 Previously, we had used "router descriptor", "server descriptor",
15279 and "relay descriptor" interchangeably. Part of ticket 14987.
15280 - Advise users on how to configure separate IPv4 and IPv6 exit
15281 policies in the manpage and sample torrcs. Related to ticket 16069.
15282 - Fix an error in the manual page and comments for
15283 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
15284 required "ORPort connectivity". While this is true, it is in no
15285 way unique to the HSDir flag. Of all the flags, only HSDirs need a
15286 DirPort configured in order for the authorities to assign that
15287 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
15289 - Fix the usage message of tor-resolve(1) so that it no longer lists
15290 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
15293 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
15294 and always use the internal Base64 decoder. The internal decoder
15295 has been part of tor since 0.2.0.10-alpha, and no one should
15296 be using the OpenSSL one. Part of ticket 15652.
15297 - Remove the 'tor_strclear()' function; use memwipe() instead.
15298 Closes ticket 14922.
15299 - Remove the code that would try to aggressively flush controller
15300 connections while writing to them. This code was introduced in
15301 0.1.2.7-alpha, in order to keep output buffers from exceeding
15302 their limits. But there is no longer a maximum output buffer size,
15303 and flushing data in this way caused some undesirable recursions
15304 in our call graph. Closes ticket 16480.
15305 - The internal pure-C tor-fw-helper tool is now removed from the Tor
15306 distribution, in favor of the pure-Go clone available from
15307 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
15308 used by the C tor-fw-helper are not, in our opinion, very
15309 confidence- inspiring in their secure-programming techniques.
15310 Closes ticket 13338.
15312 o Removed features:
15313 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
15314 fingerprinting we now recommend pluggable transports; for forward-
15315 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
15316 - Remove the HidServDirectoryV2 option. Now all relays offer to
15317 store hidden service descriptors. Related to 16543.
15318 - Remove the VoteOnHidServDirectoriesV2 option, since all
15319 authorities have long set it to 1. Closes ticket 16543.
15320 - Remove the undocumented "--digests" command-line option. It
15321 complicated our build process, caused subtle build issues on
15322 multiple platforms, and is now redundant since we started
15323 including git version identifiers. Closes ticket 14742.
15324 - Tor no longer contains checks for ancient directory cache versions
15325 that didn't know about microdescriptors.
15326 - Tor no longer contains workarounds for stat files generated by
15327 super-old versions of Tor that didn't choose guards sensibly.
15330 - The test-network.sh script now supports performance testing.
15331 Requires corresponding chutney performance testing changes. Patch
15332 by "teor". Closes ticket 14175.
15333 - Add a new set of callgraph analysis scripts that use clang to
15334 produce a list of which Tor functions are reachable from which
15335 other Tor functions. We're planning to use these to help simplify
15336 our code structure by identifying illogical dependencies.
15337 - Add new 'test-full' and 'test-full-online' targets to run all
15338 tests, including integration tests with stem and chutney.
15339 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
15340 by-side in the same parent directory. Closes ticket 16903. Patch
15342 - Document use of coverity, clang static analyzer, and clang dynamic
15343 undefined behavior and address sanitizers in doc/HACKING. Include
15344 detailed usage instructions in the blacklist. Patch by "teor".
15345 Closes ticket 15817.
15346 - Make "bridges+hs" the default test network. This tests almost all
15347 tor functionality during make test-network, while allowing tests
15348 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
15349 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
15350 (chutney). Patches by "teor".
15351 - Make the test-workqueue test work on Windows by initializing the
15352 network before we begin.
15353 - New make target (make test-network-all) to run multiple applicable
15354 chutney test cases. Patch from Teor; closes 16953.
15355 - Now that OpenSSL has its own scrypt implementation, add an unit
15356 test that checks for interoperability between libscrypt_scrypt()
15357 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
15358 and rely on EVP_PBE_scrypt() whenever possible. Resolves
15360 - The link authentication protocol code now has extensive tests.
15361 - The relay descriptor signature testing code now has
15363 - The test_workqueue program now runs faster, and is enabled by
15364 default as a part of "make check".
15365 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
15366 functions in dns.c. Implements a portion of ticket 16831.
15367 - Use environment variables rather than autoconf substitutions to
15368 send variables from the build system to the test scripts. This
15369 change should be easier to maintain, and cause 'make distcheck' to
15370 work better than before. Fixes bug 17148.
15371 - When building Tor with testing coverage enabled, run Chutney tests
15372 (if any) using the 'tor-cov' coverage binary.
15373 - When running test-network or test-stem, check for the absence of
15374 stem/chutney before doing any build operations.
15375 - Add a test to verify that the compiler does not eliminate our
15376 memwipe() implementation. Closes ticket 15377.
15377 - Add make rule `check-changes` to verify the format of changes
15378 files. Closes ticket 15180.
15379 - Add unit tests for control_event_is_interesting(). Add a compile-
15380 time check that the number of events doesn't exceed the capacity
15381 of control_event_t.event_mask. Closes ticket 15431, checks for
15382 bugs similar to 13085. Patch by "teor".
15383 - Command-line argument tests moved to Stem. Resolves ticket 14806.
15384 - Integrate the ntor, backtrace, and zero-length keys tests into the
15385 automake test suite. Closes ticket 15344.
15386 - Remove assertions during builds to determine Tor's test coverage.
15387 We don't want to trigger these even in assertions, so including
15388 them artificially makes our branch coverage look worse than it is.
15389 This patch provides the new test-stem-full and coverage-html-full
15390 configure options. Implements ticket 15400.
15391 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
15392 explicitly manage consensus flags in testing networks. Patch by
15393 "robgjansen", modified by "teor". Implements part of ticket 14882.
15394 - Check for matching value in server response in ntor_ref.py. Fixes
15395 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
15397 - Set the severity correctly when testing
15398 get_interface_addresses_ifaddrs() and
15399 get_interface_addresses_win32(), so that the tests fail gracefully
15400 instead of triggering an assertion. Fixes bug 15759; bugfix on
15401 0.2.6.3-alpha. Reported by Nicolas Derive.
15403 Changes in version 0.2.6.10 - 2015-07-12
15404 Tor version 0.2.6.10 fixes some significant stability and hidden
15405 service client bugs, bulletproofs the cryptography init process, and
15406 fixes a bug when using the sandbox code with some older versions of
15407 Linux. Everyone running an older version, especially an older version
15408 of 0.2.6, should upgrade.
15410 o Major bugfixes (hidden service clients, stability):
15411 - Stop refusing to store updated hidden service descriptors on a
15412 client. This reverts commit 9407040c59218 (which indeed fixed bug
15413 14219, but introduced a major hidden service reachability
15414 regression detailed in bug 16381). This is a temporary fix since
15415 we can live with the minor issue in bug 14219 (it just results in
15416 some load on the network) but the regression of 16381 is too much
15417 of a setback. First-round fix for bug 16381; bugfix
15420 o Major bugfixes (stability):
15421 - Stop crashing with an assertion failure when parsing certain kinds
15422 of malformed or truncated microdescriptors. Fixes bug 16400;
15423 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
15424 by "cypherpunks_backup".
15425 - Stop random client-side assertion failures that could occur when
15426 connecting to a busy hidden service, or connecting to a hidden
15427 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
15430 o Minor features (geoip):
15431 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
15432 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
15434 o Minor bugfixes (crypto error-handling):
15435 - Check for failures from crypto_early_init, and refuse to continue.
15436 A previous typo meant that we could keep going with an
15437 uninitialized crypto library, and would have OpenSSL initialize
15438 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15439 when implementing ticket 4900. Patch by "teor".
15441 o Minor bugfixes (Linux seccomp2 sandbox):
15442 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15443 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15444 on 0.2.6.3-alpha. Patch from "teor".
15447 Changes in version 0.2.6.9 - 2015-06-11
15448 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
15449 requirements for receiving an HSDir flag, and addresses some other small
15450 bugs in the systemd and sandbox code. Clients using circuit isolation
15451 should upgrade; all directory authorities should upgrade.
15453 o Major bugfixes (client-side privacy):
15454 - Properly separate out each SOCKSPort when applying stream
15455 isolation. The error occurred because each port's session group was
15456 being overwritten by a default value when the listener connection
15457 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
15460 o Minor feature (directory authorities, security):
15461 - The HSDir flag given by authorities now requires the Stable flag.
15462 For the current network, this results in going from 2887 to 2806
15463 HSDirs. Also, it makes it harder for an attacker to launch a sybil
15464 attack by raising the effort for a relay to become Stable which
15465 takes at the very least 7 days to do so and by keeping the 96
15466 hours uptime requirement for HSDir. Implements ticket 8243.
15468 o Minor bugfixes (compilation):
15469 - Build with --enable-systemd correctly when libsystemd is
15470 installed, but systemd is not. Fixes bug 16164; bugfix on
15471 0.2.6.3-alpha. Patch from Peter Palfrader.
15473 o Minor bugfixes (Linux seccomp2 sandbox):
15474 - Fix sandboxing to work when running as a relaymby renaming of
15475 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
15476 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
15477 - Allow systemd connections to work with the Linux seccomp2 sandbox
15478 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
15481 o Minor bugfixes (tests):
15482 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
15483 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
15486 Changes in version 0.2.6.8 - 2015-05-21
15487 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
15488 fixes an authority-side bug in assigning the HSDir flag. All directory
15489 authorities should upgrade.
15491 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
15492 - Revert commit that made directory authorities assign the HSDir
15493 flag to relays without a DirPort; this was bad because such relays
15494 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
15497 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
15498 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15499 a client authorized hidden service. Fixes bug 15823; bugfix
15502 o Minor features (geoip):
15503 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
15504 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
15508 Changes in version 0.2.6.7 - 2015-04-06
15509 Tor 0.2.6.7 fixes two security issues that could be used by an
15510 attacker to crash hidden services, or crash clients visiting hidden
15511 services. Hidden services should upgrade as soon as possible; clients
15512 should upgrade whenever packages become available.
15514 This release also contains two simple improvements to make hidden
15515 services a bit less vulnerable to denial-of-service attacks.
15517 o Major bugfixes (security, hidden service):
15518 - Fix an issue that would allow a malicious client to trigger an
15519 assertion failure and halt a hidden service. Fixes bug 15600;
15520 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15521 - Fix a bug that could cause a client to crash with an assertion
15522 failure when parsing a malformed hidden service descriptor. Fixes
15523 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15525 o Minor features (DoS-resistance, hidden service):
15526 - Introduction points no longer allow multiple INTRODUCE1 cells to
15527 arrive on the same circuit. This should make it more expensive for
15528 attackers to overwhelm hidden services with introductions.
15529 Resolves ticket 15515.
15530 - Decrease the amount of reattempts that a hidden service performs
15531 when its rendezvous circuits fail. This reduces the computational
15532 cost for running a hidden service under heavy load. Resolves
15536 Changes in version 0.2.5.12 - 2015-04-06
15537 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
15538 could be used by an attacker to crash hidden services, or crash clients
15539 visiting hidden services. Hidden services should upgrade as soon as
15540 possible; clients should upgrade whenever packages become available.
15542 This release also backports a simple improvement to make hidden
15543 services a bit less vulnerable to denial-of-service attacks.
15545 o Major bugfixes (security, hidden service):
15546 - Fix an issue that would allow a malicious client to trigger an
15547 assertion failure and halt a hidden service. Fixes bug 15600;
15548 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15549 - Fix a bug that could cause a client to crash with an assertion
15550 failure when parsing a malformed hidden service descriptor. Fixes
15551 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15553 o Minor features (DoS-resistance, hidden service):
15554 - Introduction points no longer allow multiple INTRODUCE1 cells to
15555 arrive on the same circuit. This should make it more expensive for
15556 attackers to overwhelm hidden services with introductions.
15557 Resolves ticket 15515.
15560 Changes in version 0.2.4.27 - 2015-04-06
15561 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
15562 could be used by an attacker to crash hidden services, or crash clients
15563 visiting hidden services. Hidden services should upgrade as soon as
15564 possible; clients should upgrade whenever packages become available.
15566 This release also backports a simple improvement to make hidden
15567 services a bit less vulnerable to denial-of-service attacks.
15569 o Major bugfixes (security, hidden service):
15570 - Fix an issue that would allow a malicious client to trigger an
15571 assertion failure and halt a hidden service. Fixes bug 15600;
15572 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15573 - Fix a bug that could cause a client to crash with an assertion
15574 failure when parsing a malformed hidden service descriptor. Fixes
15575 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15577 o Minor features (DoS-resistance, hidden service):
15578 - Introduction points no longer allow multiple INTRODUCE1 cells to
15579 arrive on the same circuit. This should make it more expensive for
15580 attackers to overwhelm hidden services with introductions.
15581 Resolves ticket 15515.
15584 Changes in version 0.2.6.6 - 2015-03-24
15585 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
15587 It adds numerous safety, security, correctness, and performance
15588 improvements. Client programs can be configured to use more kinds of
15589 sockets, AutomapHosts works better, the multithreading backend is
15590 improved, cell transmission is refactored, test coverage is much
15591 higher, more denial-of-service attacks are handled, guard selection is
15592 improved to handle long-term guards better, pluggable transports
15593 should work a bit better, and some annoying hidden service performance
15594 bugs should be addressed.
15596 o New compiler and system requirements:
15597 - Tor 0.2.6.x requires that your compiler support more of the C99
15598 language standard than before. The 'configure' script now detects
15599 whether your compiler supports C99 mid-block declarations and
15600 designated initializers. If it does not, Tor will not compile.
15602 We may revisit this requirement if it turns out that a significant
15603 number of people need to build Tor with compilers that don't
15604 bother implementing a 15-year-old standard. Closes ticket 13233.
15605 - Tor no longer supports systems without threading support. When we
15606 began working on Tor, there were several systems that didn't have
15607 threads, or where the thread support wasn't able to run the
15608 threads of a single process on multiple CPUs. That no longer
15609 holds: every system where Tor needs to run well now has threading
15610 support. Resolves ticket 12439.
15612 o Deprecated versions and removed support:
15613 - Tor relays older than 0.2.4.18-rc are no longer allowed to
15614 advertise themselves on the network. Closes ticket 13555.
15615 - Tor clients no longer support connecting to hidden services
15616 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
15617 option has been removed. (There shouldn't be any hidden services
15618 running these versions on the network.) Closes ticket 7803.
15620 o Directory authority changes:
15621 - The directory authority Faravahar has a new IP address. This
15622 closes ticket 14487.
15623 - Remove turtles as a directory authority.
15624 - Add longclaw as a new (v3) directory authority. This implements
15625 ticket 13296. This keeps the directory authority count at 9.
15627 o Major features (bridges):
15628 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
15629 transports if they are configured via the "TOR_PT_PROXY"
15630 environment variable. Implements proposal 232. Resolves
15633 o Major features (changed defaults):
15634 - Prevent relay operators from unintentionally running exits: When a
15635 relay is configured as an exit node, we now warn the user unless
15636 the "ExitRelay" option is set to 1. We warn even more loudly if
15637 the relay is configured with the default exit policy, since this
15638 can indicate accidental misconfiguration. Setting "ExitRelay 0"
15639 stops Tor from running as an exit relay. Closes ticket 10067.
15641 o Major features (client performance, hidden services):
15642 - Allow clients to use optimistic data when connecting to a hidden
15643 service, which should remove a round-trip from hidden service
15644 initialization. See proposal 181 for details. Implements
15647 o Major features (directory system):
15648 - Upon receiving an unparseable directory object, if its digest
15649 matches what we expected, then don't try to download it again.
15650 Previously, when we got a descriptor we didn't like, we would keep
15651 trying to download it over and over. Closes ticket 11243.
15652 - When downloading server- or microdescriptors from a directory
15653 server, we no longer launch multiple simultaneous requests to the
15654 same server. This reduces load on the directory servers,
15655 especially when directory guards are in use. Closes ticket 9969.
15656 - When downloading server- or microdescriptors over a tunneled
15657 connection, do not limit the length of our requests to what the
15658 Squid proxy is willing to handle. Part of ticket 9969.
15659 - Authorities can now vote on the correct digests and latest
15660 versions for different software packages. This allows packages
15661 that include Tor to use the Tor authority system as a way to get
15662 notified of updates and their correct digests. Implements proposal
15663 227. Closes ticket 10395.
15665 o Major features (guards):
15666 - Introduce the Guardfraction feature to improves load balancing on
15667 guard nodes. Specifically, it aims to reduce the traffic gap that
15668 guard nodes experience when they first get the Guard flag. This is
15669 a required step if we want to increase the guard lifetime to 9
15670 months or greater. Closes ticket 9321.
15672 o Major features (hidden services):
15673 - Make HS port scanning more difficult by immediately closing the
15674 circuit when a user attempts to connect to a nonexistent port.
15675 Closes ticket 13667.
15676 - Add a HiddenServiceStatistics option that allows Tor relays to
15677 gather and publish statistics about the overall size and volume of
15678 hidden service usage. Specifically, when this option is turned on,
15679 an HSDir will publish an approximate number of hidden services
15680 that have published descriptors to it the past 24 hours. Also, if
15681 a relay has acted as a hidden service rendezvous point, it will
15682 publish the approximate amount of rendezvous cells it has relayed
15683 the past 24 hours. The statistics themselves are obfuscated so
15684 that the exact values cannot be derived. For more details see
15685 proposal 238, "Better hidden service stats from Tor relays". This
15686 feature is currently disabled by default. Implements feature 13192.
15688 o Major features (performance):
15689 - Make the CPU worker implementation more efficient by avoiding the
15690 kernel and lengthening pipelines. The original implementation used
15691 sockets to transfer data from the main thread to the workers, and
15692 didn't allow any thread to be assigned more than a single piece of
15693 work at once. The new implementation avoids communications
15694 overhead by making requests in shared memory, avoiding kernel IO
15695 where possible, and keeping more requests in flight at once.
15696 Implements ticket 9682.
15698 o Major features (relay):
15699 - Raise the minimum acceptable configured bandwidth rate for bridges
15700 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
15701 20 KiB/sec.) Closes ticket 13822.
15702 - Complete revision of the code that relays use to decide which cell
15703 to send next. Formerly, we selected the best circuit to write on
15704 each channel, but we didn't select among channels in any
15705 sophisticated way. Now, we choose the best circuits globally from
15706 among those whose channels are ready to deliver traffic.
15708 This patch implements a new inter-cmux comparison API, a global
15709 high/low watermark mechanism and a global scheduler loop for
15710 transmission prioritization across all channels as well as among
15711 circuits on one channel. This schedule is currently tuned to
15712 (tolerantly) avoid making changes in network performance, but it
15713 should form the basis for major circuit performance increases in
15714 the future. Code by Andrea; tuning by Rob Jansen; implements
15717 o Major features (sample torrc):
15718 - Add a new, infrequently-changed "torrc.minimal". This file is
15719 similar to torrc.sample, but it will change as infrequently as
15720 possible, for the benefit of users whose systems prompt them for
15721 intervention whenever a default configuration file is changed.
15722 Making this change allows us to update torrc.sample to be a more
15723 generally useful "sample torrc".
15725 o Major features (security, unix domain sockets):
15726 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
15727 applications can reach Tor without having to create AF_INET or
15728 AF_INET6 sockets, meaning they can completely disable their
15729 ability to make non-Tor network connections. To create a socket of
15730 this type, use "SocksPort unix:/path/to/socket". Implements
15732 - Support mapping hidden service virtual ports to AF_UNIX sockets.
15733 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
15734 Implements ticket 11485.
15736 o Major bugfixes (client, automap):
15737 - Repair automapping with IPv6 addresses. This automapping should
15738 have worked previously, but one piece of debugging code that we
15739 inserted to detect a regression actually caused the regression to
15740 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
15741 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
15744 o Major bugfixes (crash, OSX, security):
15745 - Fix a remote denial-of-service opportunity caused by a bug in
15746 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
15749 o Major bugfixes (directory authorities):
15750 - Do not assign the HSDir flag to relays if they are not Valid, or
15751 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
15753 o Major bugfixes (directory bandwidth performance):
15754 - Don't flush the zlib buffer aggressively when compressing
15755 directory information for clients. This should save about 7% of
15756 the bandwidth currently used for compressed descriptors and
15757 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
15759 o Major bugfixes (exit node stability):
15760 - Fix an assertion failure that could occur under high DNS load.
15761 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15762 diagnosed and fixed by "cypherpunks".
15764 o Major bugfixes (FreeBSD IPFW transparent proxy):
15765 - Fix address detection with FreeBSD transparent proxies, when
15766 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
15769 o Major bugfixes (hidden services):
15770 - When closing an introduction circuit that was opened in parallel
15771 with others, don't mark the introduction point as unreachable.
15772 Previously, the first successful connection to an introduction
15773 point would make the other introduction points get marked as
15774 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
15776 o Major bugfixes (Linux seccomp2 sandbox):
15777 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
15778 crash during attempts to call wait4. Fixes bug 15088; bugfix on
15779 0.2.5.1-alpha. Patch from "sanic".
15781 o Major bugfixes (mixed relay-client operation):
15782 - When running as a relay and client at the same time (not
15783 recommended), if we decide not to use a new guard because we want
15784 to retry older guards, only close the locally-originating circuits
15785 passing through that guard. Previously we would close all the
15786 circuits through that guard. Fixes bug 9819; bugfix on
15787 0.2.1.1-alpha. Reported by "skruffy".
15789 o Major bugfixes (pluggable transports):
15790 - Initialize the extended OR Port authentication cookie before
15791 launching pluggable transports. This prevents a race condition
15792 that occurred when server-side pluggable transports would cache the
15793 authentication cookie before it has been (re)generated. Fixes bug
15794 15240; bugfix on 0.2.5.1-alpha.
15796 o Major bugfixes (relay, stability, possible security):
15797 - Fix a bug that could lead to a relay crashing with an assertion
15798 failure if a buffer of exactly the wrong layout is passed to
15799 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15800 0.2.0.10-alpha. Patch from "cypherpunks".
15801 - Do not assert if the 'data' pointer on a buffer is advanced to the
15802 very end of the buffer; log a BUG message instead. Only assert if
15803 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15805 o Minor features (build):
15806 - New --disable-system-torrc compile-time option to prevent Tor from
15807 looking for the system-wide torrc or torrc-defaults files.
15808 Resolves ticket 13037.
15810 o Minor features (client):
15811 - Clients are now willing to send optimistic data (before they
15812 receive a 'connected' cell) to relays of any version. (Relays
15813 without support for optimistic data are no longer supported on the
15814 Tor network.) Resolves ticket 13153.
15816 o Minor features (client):
15817 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
15818 is enabled, reject requests with IP addresses as hostnames.
15819 Resolves ticket 13315.
15821 o Minor features (controller):
15822 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
15823 write an unscheduled heartbeat message to the log. Implements
15825 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
15826 events so controllers can observe circuit isolation inputs. Closes
15828 - ControlPort now supports the unix:/path/to/socket syntax as an
15829 alternative to the ControlSocket option, for consistency with
15830 SocksPort and HiddenServicePort. Closes ticket 14451.
15831 - New "GETINFO bw-event-cache" to get information about recent
15832 bandwidth events. Closes ticket 14128. Useful for controllers to
15833 get recent bandwidth history after the fix for ticket 13988.
15834 - Messages about problems in the bootstrap process now include
15835 information about the server we were trying to connect to when we
15836 noticed the problem. Closes ticket 15006.
15838 o Minor features (Denial of service resistance):
15839 - Count the total number of bytes used storing hidden service
15840 descriptors against the value of MaxMemInQueues. If we're low on
15841 memory, and more than 20% of our memory is used holding hidden
15842 service descriptors, free them until no more than 10% of our
15843 memory holds hidden service descriptors. Free the least recently
15844 fetched descriptors first. Resolves ticket 13806.
15845 - When we have recently been under memory pressure (over 3/4 of
15846 MaxMemInQueues is allocated), then allocate smaller zlib objects
15847 for small requests. Closes ticket 11791.
15849 o Minor features (directory authorities):
15850 - Don't list relays with a bandwidth estimate of 0 in the consensus.
15851 Implements a feature proposed during discussion of bug 13000.
15852 - In tor-gencert, report an error if the user provides the same
15853 argument more than once.
15854 - If a directory authority can't find a best consensus method in the
15855 votes that it holds, it now falls back to its favorite consensus
15856 method. Previously, it fell back to method 1. Neither of these is
15857 likely to get enough signatures, but "fall back to favorite"
15858 doesn't require us to maintain support an obsolete consensus
15859 method. Implements part of proposal 215.
15861 o Minor features (geoip):
15862 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
15863 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
15866 o Minor features (guard nodes):
15867 - Reduce the time delay before saving guard status to disk from 10
15868 minutes to 30 seconds (or from one hour to 10 minutes if
15869 AvoidDiskWrites is set). Closes ticket 12485.
15871 o Minor features (heartbeat):
15872 - On relays, report how many connections we negotiated using each
15873 version of the Tor link protocols. This information will let us
15874 know if removing support for very old versions of the Tor
15875 protocols is harming the network. Closes ticket 15212.
15877 o Minor features (hidden service):
15878 - Make Sybil attacks against hidden services harder by changing the
15879 minimum time required to get the HSDir flag from 25 hours up to 96
15880 hours. Addresses ticket 14149.
15881 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
15882 services to disable the anti-scanning feature introduced in
15883 0.2.6.2-alpha. With this option not set, a connection to an
15884 unlisted port closes the circuit. With this option set, only a
15885 RELAY_DONE cell is sent. Closes ticket 14084.
15886 - When re-enabling the network, don't try to build introduction
15887 circuits until we have successfully built a circuit. This makes
15888 hidden services come up faster when the network is re-enabled.
15889 Patch from "akwizgran". Closes ticket 13447.
15890 - When we fail to retrieve a hidden service descriptor, send the
15891 controller an "HS_DESC FAILED" controller event. Implements
15893 - New HiddenServiceDirGroupReadable option to cause hidden service
15894 directories and hostname files to be created group-readable. Patch
15895 from "anon", David Stainton, and "meejah". Closes ticket 11291.
15897 o Minor features (interface):
15898 - Implement "-f -" command-line option to read torrc configuration
15899 from standard input, if you don't want to store the torrc file in
15900 the file system. Implements feature 13865.
15902 o Minor features (logging):
15903 - Add a count of unique clients to the bridge heartbeat message.
15904 Resolves ticket 6852.
15905 - Suppress "router info incompatible with extra info" message when
15906 reading extrainfo documents from cache. (This message got loud
15907 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
15909 - Elevate hidden service authorized-client message from DEBUG to
15910 INFO. Closes ticket 14015.
15911 - On Unix-like systems, you can now use named pipes as the target of
15912 the Log option, and other options that try to append to files.
15913 Closes ticket 12061. Patch from "carlo von lynX".
15914 - When opening a log file at startup, send it every log message that
15915 we generated between startup and opening it. Previously, log
15916 messages that were generated before opening the log file were only
15917 logged to stdout. Closes ticket 6938.
15918 - Add a TruncateLogFile option to overwrite logs instead of
15919 appending to them. Closes ticket 5583.
15920 - Quiet some log messages in the heartbeat and at startup. Closes
15923 o Minor features (portability, Solaris):
15924 - Threads are no longer disabled by default on Solaris; we believe
15925 that the versions of Solaris with broken threading support are all
15926 obsolete by now. Resolves ticket 9495.
15928 o Minor features (relay):
15929 - Re-check our address after we detect a changed IP address from
15930 getsockname(). This ensures that the controller command "GETINFO
15931 address" will report the correct value. Resolves ticket 11582.
15933 - A new AccountingRule option lets Relays set whether they'd like
15934 AccountingMax to be applied separately to inbound and outbound
15935 traffic, or applied to the sum of inbound and outbound traffic.
15936 Resolves ticket 961. Patch by "chobe".
15937 - When identity keypair is generated for first time, log a
15938 congratulatory message that links to the new relay lifecycle
15939 document. Implements feature 10427.
15941 o Minor features (security, memory wiping):
15942 - Ensure we securely wipe keys from memory after
15943 crypto_digest_get_digest and init_curve25519_keypair_from_file
15944 have finished using them. Resolves ticket 13477.
15946 o Minor features (security, out-of-memory handling):
15947 - When handling an out-of-memory condition, allocate less memory for
15948 temporary data structures. Fixes issue 10115.
15949 - When handling an out-of-memory condition, consider more types of
15950 buffers, including those on directory connections, and zlib
15951 buffers. Resolves ticket 11792.
15953 o Minor features (stability):
15954 - Add assertions in our hash-table iteration code to check for
15955 corrupted values that could cause infinite loops. Closes
15958 o Minor features (systemd):
15959 - Various improvements and modernizations in systemd hardening
15960 support. Closes ticket 13805. Patch from Craig Andrews.
15961 - Where supported, when running with systemd, report successful
15962 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
15963 - When running with systemd, support systemd watchdog messages. Part
15964 of ticket 11016. Patch by Michael Scherer.
15966 o Minor features (testing networks):
15967 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
15968 the "Exit" flag regardless of their uptime, bandwidth, or exit
15969 policy. TestingTorNetwork must be set for this option to have any
15970 effect. Previously, authorities would take up to 35 minutes to
15971 give nodes the Exit flag in a test network. Partially implements
15973 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
15974 and the default on a testing network to 2 minutes. Drop the
15975 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
15976 keep the default on a testing network at 30 seconds. This reduces
15977 HS bootstrap time to around 25 seconds. Also, change the default
15978 time in test-network.sh to match. Closes ticket 13401. Patch
15980 - Create TestingDirAuthVoteHSDir to correspond to
15981 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
15982 HSDir flag for the listed relays regardless of uptime or ORPort
15983 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
15984 Partial implementation for ticket 14067. Patch by "teor".
15986 o Minor features (tor2web mode):
15987 - Introduce the config option Tor2webRendezvousPoints, which allows
15988 clients in Tor2webMode to select a specific Rendezvous Point to be
15989 used in HS circuits. This might allow better performance for
15990 Tor2Web nodes. Implements ticket 12844.
15992 o Minor features (transparent proxy):
15993 - Update the transparent proxy option checks to allow for both ipfw
15994 and pf on OS X. Closes ticket 14002.
15995 - Use the correct option when using IPv6 with transparent proxy
15996 support on Linux. Resolves 13808. Patch by Francisco Blas
15999 o Minor features (validation):
16000 - Check all date/time values passed to tor_timegm and
16001 parse_rfc1123_time for validity, taking leap years into account.
16002 Improves HTTP header validation. Implemented with bug 13476.
16003 - In correct_tm(), limit the range of values returned by system
16004 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
16005 This means we don't have to deal with negative or too large dates,
16006 even if a clock is wrong. Otherwise we might fail to read a file
16007 written by us which includes such a date. Fixes bug 13476.
16008 - Stop allowing invalid address patterns like "*/24" that contain
16009 both a wildcard address and a bit prefix length. This affects all
16010 our address-range parsing code. Fixes bug 7484; bugfix
16013 o Minor bugfixes (bridge clients):
16014 - When configured to use a bridge without an identity digest (not
16015 recommended), avoid launching an extra channel to it when
16016 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
16018 o Minor bugfixes (bridges):
16019 - When DisableNetwork is set, do not launch pluggable transport
16020 plugins, and if any are running, terminate them. Fixes bug 13213;
16021 bugfix on 0.2.3.6-alpha.
16023 o Minor bugfixes (C correctness):
16024 - Fix several instances of possible integer overflow/underflow/NaN.
16025 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
16027 - In circuit_build_times_calculate_timeout() in circuitstats.c,
16028 avoid dividing by zero in the pareto calculations. This traps
16029 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
16031 - Fix an integer overflow in format_time_interval(). Fixes bug
16032 13393; bugfix on 0.2.0.10-alpha.
16033 - Set the correct day of year value when the system's localtime(_r)
16034 or gmtime(_r) functions fail to set struct tm. Not externally
16035 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
16036 - Avoid unlikely signed integer overflow in tor_timegm on systems
16037 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
16039 o Minor bugfixes (certificate handling):
16040 - If an authority operator accidentally makes a signing certificate
16041 with a future publication time, do not discard its real signing
16042 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
16043 - Remove any old authority certificates that have been superseded
16044 for at least two days. Previously, we would keep superseded
16045 certificates until they expired, if they were published close in
16046 time to the certificate that superseded them. Fixes bug 11454;
16047 bugfix on 0.2.1.8-alpha.
16049 o Minor bugfixes (client):
16050 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
16051 BadExit flag are not considered worthy candidates. Fixes bug
16052 13066; bugfix on 0.1.2.3-alpha.
16053 - Use the consensus schedule for downloading consensuses, and not
16054 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
16055 - Handle unsupported or malformed SOCKS5 requests properly by
16056 responding with the appropriate error message before closing the
16057 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
16059 o Minor bugfixes (client, automapping):
16060 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16061 no value follows the option. Fixes bug 14142; bugfix on
16062 0.2.4.7-alpha. Patch by "teor".
16063 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16064 14195; bugfix on 0.1.0.1-rc.
16065 - Prevent changes to other options from removing the wildcard value
16066 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
16068 - Allow MapAddress and AutomapHostsOnResolve to work together when
16069 an address is mapped into another address type (like .onion) that
16070 must be automapped at resolve time. Fixes bug 7555; bugfix
16073 o Minor bugfixes (client, bridges):
16074 - When we are using bridges and we had a network connectivity
16075 problem, only retry connecting to our currently configured
16076 bridges, not all bridges we know about and remember using. Fixes
16077 bug 14216; bugfix on 0.2.2.17-alpha.
16079 o Minor bugfixes (client, DNS):
16080 - Report the correct cached DNS expiration times on SOCKS port or in
16081 DNS replies. Previously, we would report everything as "never
16082 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
16083 - Avoid a small memory leak when we find a cached answer for a
16084 reverse DNS lookup in a client-side DNS cache. (Remember, client-
16085 side DNS caching is off by default, and is not recommended.) Fixes
16086 bug 14259; bugfix on 0.2.0.1-alpha.
16088 o Minor bugfixes (client, IPv6):
16089 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
16090 flag is not set; and not because the NoIPv4Traffic flag was set.
16091 Previously we'd looked at the NoIPv4Traffic flag for both types of
16092 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
16094 o Minor bugfixes (client, microdescriptors):
16095 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
16096 computing which microdescriptors to download. This keeps us from
16097 erroneous download behavior if two microdescriptor digests ever
16098 have the same first 160 bits. Fixes part of bug 13399; bugfix
16100 - Reset a router's status if its microdescriptor digest changes,
16101 even if the first 160 bits remain the same. Fixes part of bug
16102 13399; bugfix on 0.2.3.1-alpha.
16104 o Minor bugfixes (client, torrc):
16105 - Stop modifying the value of our DirReqStatistics torrc option just
16106 because we're not a bridge or relay. This bug was causing Tor
16107 Browser users to write "DirReqStatistics 0" in their torrc files
16108 as if they had chosen to change the config. Fixes bug 4244; bugfix
16110 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
16111 that our options have changed every time we SIGHUP. Fixes bug
16112 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
16114 o Minor bugfixes (compilation):
16115 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
16117 - Silence clang warnings under --enable-expensive-hardening,
16118 including implicit truncation of 64 bit values to 32 bit, const
16119 char assignment to self, tautological compare, and additional
16120 parentheses around equality tests. Fixes bug 13577; bugfix
16122 - Fix a clang warning about checking whether an address in the
16123 middle of a structure is NULL. Fixes bug 14001; bugfix
16125 - The address of an array in the middle of a structure will always
16126 be non-NULL. clang recognises this and complains. Disable the
16127 tautologous and redundant check to silence this warning. Fixes bug
16128 14001; bugfix on 0.2.1.2-alpha.
16129 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
16130 Addresses ticket 14188.
16131 - Build without warnings with the stock OpenSSL srtp.h header, which
16132 has a duplicate declaration of SSL_get_selected_srtp_profile().
16133 Fixes bug 14220; this is OpenSSL's bug, not ours.
16134 - Do not compile any code related to Tor2Web mode when Tor2Web mode
16135 is not enabled at compile time. Previously, this code was included
16136 in a disabled state. See discussion on ticket 12844.
16137 - Allow our configure script to build correctly with autoconf 2.62
16138 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
16139 - Improve the error message from ./configure to make it clear that
16140 when asciidoc has not been found, the user will have to either add
16141 --disable-asciidoc argument or install asciidoc. Resolves
16144 o Minor bugfixes (controller):
16145 - Report "down" in response to the "GETINFO entry-guards" command
16146 when relays are down with an unreachable_since value. Previously,
16147 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
16148 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
16149 14116; bugfix on 0.2.2.9-alpha.
16151 o Minor bugfixes (controller):
16152 - Return an error when the second or later arguments of the
16153 "setevents" controller command are invalid events. Previously we
16154 would return success while silently skipping invalid events. Fixes
16155 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
16157 o Minor bugfixes (directory authority):
16158 - Allow directory authorities to fetch more data from one another if
16159 they find themselves missing lots of votes. Previously, they had
16160 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16161 bugfix on 0.1.2.5-alpha.
16162 - Do not attempt to download extrainfo documents which we will be
16163 unable to validate with a matching server descriptor. Fixes bug
16164 13762; bugfix on 0.2.0.1-alpha.
16165 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
16166 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
16167 - Enlarge the buffer to read bwauth generated files to avoid an
16168 issue when parsing the file in dirserv_read_measured_bandwidths().
16169 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16170 - When running as a v3 directory authority, advertise that you serve
16171 extra-info documents so that clients who want them can find them
16172 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
16174 o Minor bugfixes (directory system):
16175 - Always believe that v3 directory authorities serve extra-info
16176 documents, whether they advertise "caches-extra-info" or not.
16177 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
16178 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
16179 Previously, directories offering BRIDGE_DIRINFO and some other
16180 flag (i.e. microdescriptors or extrainfo) would be ignored when
16181 looking for bridges. Partially fixes bug 13163; bugfix
16184 o Minor bugfixes (file handling):
16185 - Stop failing when key files are zero-length. Instead, generate new
16186 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
16187 on all versions of Tor. Patch by "teor".
16188 - Stop generating a fresh .old RSA onion key file when the .old file
16189 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
16190 - Avoid overwriting .old key files with empty key files.
16191 - Skip loading zero-length extrainfo store, router store, stats,
16192 state, and key files.
16193 - Avoid crashing when trying to reload a torrc specified as a
16194 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
16197 o Minor bugfixes (hidden services):
16198 - Close the introduction circuit when we have no more usable intro
16199 points, instead of waiting for it to time out. This also ensures
16200 that no follow-up HS descriptor fetch is triggered when the
16201 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
16202 - When fetching a hidden service descriptor for a down service that
16203 was recently up, do not keep refetching until we try the same
16204 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
16205 - Correctly send a controller event when we find that a rendezvous
16206 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
16207 - Pre-check directory permissions for new hidden-services to avoid
16208 at least one case of "Bug: Acting on config options left us in a
16209 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
16210 - When fetching hidden service descriptors, we now check not only
16211 for whether we got the hidden service we had in mind, but also
16212 whether we got the particular descriptors we wanted. This prevents
16213 a class of inefficient but annoying DoS attacks by hidden service
16214 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
16217 o Minor bugfixes (Linux seccomp2 sandbox):
16218 - Make transparent proxy support work along with the seccomp2
16219 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
16220 by Francisco Blas Izquierdo Riera.
16221 - Fix a memory leak in tor-resolve when running with the sandbox
16222 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
16223 - Allow glibc fatal errors to be sent to stderr before Tor exits.
16224 Previously, glibc would try to write them to /dev/tty, and the
16225 sandbox would trap the call and make Tor exit prematurely. Fixes
16226 bug 14759; bugfix on 0.2.5.1-alpha.
16228 o Minor bugfixes (logging):
16229 - Avoid crashing when there are more log domains than entries in
16230 domain_list. Bugfix on 0.2.3.1-alpha.
16231 - Downgrade warnings about RSA signature failures to info log level.
16232 Emit a warning when an extra info document is found incompatible
16233 with a corresponding router descriptor. Fixes bug 9812; bugfix
16235 - Make connection_ap_handshake_attach_circuit() log the circuit ID
16236 correctly. Fixes bug 13701; bugfix on 0.0.6.
16238 o Minor bugfixes (networking):
16239 - Check for orconns and use connection_or_close_for_error() rather
16240 than connection_mark_for_close() directly in the getsockopt()
16241 failure case of connection_handle_write_impl(). Fixes bug 11302;
16242 bugfix on 0.2.4.4-alpha.
16244 o Minor bugfixes (parsing):
16245 - Stop accepting milliseconds (or other junk) at the end of
16246 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
16247 - Support two-number and three-number version numbers correctly, in
16248 case we change the Tor versioning system in the future. Fixes bug
16249 13661; bugfix on 0.0.8pre1.
16251 o Minor bugfixes (portability):
16252 - Fix the ioctl()-based network interface lookup code so that it
16253 will work on systems that have variable-length struct ifreq, for
16255 - Use the correct datatype in the SipHash-2-4 function to prevent
16256 compilers from assuming any sort of alignment. Fixes bug 15436;
16257 bugfix on 0.2.5.3-alpha.
16259 o Minor bugfixes (preventative security, C safety):
16260 - When reading a hexadecimal, base-32, or base-64 encoded value from
16261 a string, always overwrite the whole output buffer. This prevents
16262 some bugs where we would look at (but fortunately, not reveal)
16263 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
16265 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
16266 just the part that's used. This makes it harder for data leak bugs
16267 to occur in the event of other programming failures. Resolves
16270 o Minor bugfixes (relay):
16271 - When generating our family list, remove spaces from around the
16272 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
16273 - If our previous bandwidth estimate was 0 bytes, allow publishing a
16274 new relay descriptor immediately. Fixes bug 13000; bugfix
16277 o Minor bugfixes (shutdown):
16278 - When shutting down, always call event_del() on lingering read or
16279 write events before freeing them. Otherwise, we risk double-frees
16280 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
16283 o Minor bugfixes (small memory leaks):
16284 - Avoid leaking memory when using IPv6 virtual address mappings.
16285 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
16288 o Minor bugfixes (statistics):
16289 - Increase period over which bandwidth observations are aggregated
16290 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
16292 o Minor bugfixes (systemd support):
16293 - Run correctly under systemd with the RunAsDaemon option set. Fixes
16294 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
16295 - Inform the systemd supervisor about more changes in the Tor
16296 process status. Implements part of ticket 14141. Patch from
16299 o Minor bugfixes (testing networks):
16300 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
16301 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
16302 - Stop using the default authorities in networks which provide both
16303 AlternateDirAuthority and AlternateBridgeAuthority. Partially
16304 fixes bug 13163; bugfix on 0.2.0.13-alpha.
16306 o Minor bugfixes (testing networks, fast startup):
16307 - Allow Tor to build circuits using a consensus with no exits. If
16308 the consensus has no exits (typical of a bootstrapping test
16309 network), allow Tor to build circuits once enough descriptors have
16310 been downloaded. This assists in bootstrapping a testing Tor
16311 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
16313 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
16314 header to directory servers. This allows us to obtain consensuses
16315 promptly when the consensus interval is very short. This assists
16316 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
16317 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
16318 - Stop assuming that private addresses are local when checking
16319 reachability in a TestingTorNetwork. Instead, when testing, assume
16320 all OR connections are remote. (This is necessary due to many test
16321 scenarios running all relays on localhost.) This assists in
16322 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
16323 0.1.0.1-rc. Patch by "teor".
16324 - Avoid building exit circuits from a consensus with no exits. Now
16325 thanks to our fix for 13718, we accept a no-exit network as not
16326 wholly lost, but we need to remember not to try to build exit
16327 circuits on it. Closes ticket 13814; patch by "teor".
16328 - Stop requiring exits to have non-zero bandwithcapacity in a
16329 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
16330 ignore exit bandwidthcapacity. This assists in bootstrapping a
16331 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
16332 on 0.2.0.3-alpha. Patch by "teor".
16333 - Add "internal" to some bootstrap statuses when no exits are
16334 available. If the consensus does not contain Exits, Tor will only
16335 build internal circuits. In this case, relevant statuses will
16336 contain the word "internal" as indicated in the Tor control-
16337 spec.txt. When bootstrap completes, Tor will be ready to build
16338 internal circuits. If a future consensus contains Exits, exit
16339 circuits may become available. Fixes part of bug 13718; bugfix on
16340 0.2.4.10-alpha. Patch by "teor".
16341 - Decrease minimum consensus interval to 10 seconds when
16342 TestingTorNetwork is set, or 5 seconds for the first consensus.
16343 Fix assumptions throughout the code that assume larger intervals.
16344 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
16346 - Avoid excluding guards from path building in minimal test
16347 networks, when we're in a test network and excluding guards would
16348 exclude all relays. This typically occurs in incredibly small tor
16349 networks, and those using "TestingAuthVoteGuard *". Fixes part of
16350 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
16352 o Minor bugfixes (testing):
16353 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
16354 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
16355 - Stop spawn test failures due to a race condition between the
16356 SIGCHLD handler updating the process status, and the test reading
16357 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
16358 - Avoid passing an extra backslash when creating a temporary
16359 directory for running the unit tests on Windows. Fixes bug 12392;
16360 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
16362 o Minor bugfixes (TLS):
16363 - Check more thoroughly throughout the TLS code for possible
16364 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
16366 o Minor bugfixes (transparent proxy):
16367 - Use getsockname, not getsockopt, to retrieve the address for a
16368 TPROXY-redirected connection. Fixes bug 13796; bugfix
16371 o Minor bugfixes (windows):
16372 - Remove code to special-case handling of NTE_BAD_KEYSET when
16373 acquiring windows CryptoAPI context. This error can't actually
16374 occur for the parameters we're providing. Fixes bug 10816; bugfix
16377 o Minor bugfixes (zlib):
16378 - Avoid truncating a zlib stream when trying to finalize it with an
16379 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
16381 o Code simplification and refactoring:
16382 - Change the entry_is_live() function to take named bitfield
16383 elements instead of an unnamed list of booleans. Closes
16385 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
16386 Resolves ticket 12205.
16387 - Use calloc and reallocarray functions instead of multiply-
16388 then-malloc. This makes it less likely for us to fall victim to an
16389 integer overflow attack when allocating. Resolves ticket 12855.
16390 - Use the standard macro name SIZE_MAX, instead of our
16392 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
16393 functions which take them as arguments. Replace 0 with NO_DIRINFO
16394 in a function call for clarity. Seeks to prevent future issues
16396 - Avoid 4 null pointer errors under clang static analysis by using
16397 tor_assert() to prove that the pointers aren't null. Fixes
16399 - Rework the API of policies_parse_exit_policy() to use a bitmask to
16400 represent parsing options, instead of a confusing mess of
16401 booleans. Resolves ticket 8197.
16402 - Introduce a helper function to parse ExitPolicy in
16403 or_options_t structure.
16404 - Move fields related to isolating and configuring client ports into
16405 a shared structure. Previously, they were duplicated across
16406 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
16407 to copy them correctly had been the cause of at least one bug in
16408 the past. Closes ticket 8546.
16409 - Refactor the get_interface_addresses_raw() doom-function into
16410 multiple smaller and simpler subfunctions. Cover the resulting
16411 subfunctions with unit-tests. Fixes a significant portion of
16413 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
16414 only for version <= 0.2.2.24 which is now deprecated. Closes
16416 - Remove a test for a long-defunct broken version-one
16418 - Refactor main loop to extract the 'loop' part. This makes it
16419 easier to run Tor under Shadow. Closes ticket 15176.
16420 - Stop using can_complete_circuits as a global variable; access it
16421 with a function instead.
16422 - Avoid using operators directly as macro arguments: this lets us
16423 apply coccinelle transformations to our codebase more directly.
16424 Closes ticket 13172.
16425 - Combine the functions used to parse ClientTransportPlugin and
16426 ServerTransportPlugin into a single function. Closes ticket 6456.
16427 - Add inline functions and convenience macros for inspecting channel
16428 state. Refactor the code to use convenience macros instead of
16429 checking channel state directly. Fixes issue 7356.
16430 - Document all members of was_router_added_t and rename
16431 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
16432 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
16433 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
16434 constant instead of hardcoded value. Fixes issue 13840.
16435 - Refactor our generic strmap and digestmap types into a single
16436 implementation, so that we can add a new digest256map
16440 - Add a doc/TUNING document with tips for handling large numbers of
16441 TCP connections when running busy Tor relay. Update the warning
16442 message to point to this file when running out of sockets
16443 operating system is allowing to use simultaneously. Resolves
16445 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
16446 for writing the OpenBSD-specific tips. Resolves ticket 13702.
16447 - Make the tor-resolve documentation match its help string and its
16448 options. Resolves part of ticket 14325.
16449 - Log a more useful error message from tor-resolve when failing to
16450 look up a hidden service address. Resolves part of ticket 14325.
16451 - Document the bridge-authority-only 'networkstatus-bridges' file.
16452 Closes ticket 13713; patch from "tom".
16453 - Fix typo in PredictedPortsRelevanceTime option description in
16454 manpage. Resolves issue 13707.
16455 - Stop suggesting that users specify relays by nickname: it isn't a
16456 good idea. Also, properly cross-reference how to specify relays in
16457 all parts of manual documenting options that take a list of
16458 relays. Closes ticket 13381.
16459 - Clarify the HiddenServiceDir option description in manpage to make
16460 it clear that relative paths are taken with respect to the current
16461 working directory. Also clarify that this behavior is not
16462 guaranteed to remain indefinitely. Fixes issue 13913.
16464 o Distribution (systemd):
16465 - systemd unit file: only allow tor to write to /var/lib/tor and
16466 /var/log/tor. The rest of the filesystem is accessible for reading
16467 only. Patch by intrigeri; resolves ticket 12751.
16468 - systemd unit file: ensure that the process and all its children
16469 can never gain new privileges. Patch by intrigeri; resolves
16471 - systemd unit file: set up /var/run/tor as writable for the Tor
16472 service. Patch by intrigeri; resolves ticket 13196.
16474 o Downgraded warnings:
16475 - Don't warn when we've attempted to contact a relay using the wrong
16476 ntor onion key. Closes ticket 9635.
16479 - Remove some lingering dead code that once supported mempools.
16480 Mempools were disabled by default in 0.2.5, and removed entirely
16481 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
16484 o Removed features (directory authorities):
16485 - Remove code that prevented authorities from listing Tor relays
16486 affected by CVE-2011-2769 as guards. These relays are already
16487 rejected altogether due to the minimum version requirement of
16488 0.2.3.16-alpha. Closes ticket 13152.
16489 - The "AuthDirRejectUnlisted" option no longer has any effect, as
16490 the fingerprints file (approved-routers) has been deprecated.
16491 - Directory authorities do not support being Naming dirauths anymore.
16492 The "NamingAuthoritativeDir" config option is now obsolete.
16493 - Directory authorities do not support giving out the BadDirectory
16495 - Directory authorities no longer advertise or support consensus
16496 methods 1 through 12 inclusive. These consensus methods were
16497 obsolete and/or insecure: maintaining the ability to support them
16498 served no good purpose. Implements part of proposal 215; closes
16501 o Removed features:
16502 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
16503 longer silently accepted as an alias for "ExitNodes".
16504 - The --enable-mempool and --enable-buf-freelists options, which
16505 were originally created to work around bad malloc implementations,
16506 no longer exist. They were off-by-default in 0.2.5. Closes
16508 - We no longer remind the user about configuration options that have
16509 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
16510 - Remove our old, non-weighted bandwidth-based node selection code.
16511 Previously, we used it as a fallback when we couldn't perform
16512 weighted bandwidth-based node selection. But that would only
16513 happen in the cases where we had no consensus, or when we had a
16514 consensus generated by buggy or ancient directory authorities. In
16515 either case, it's better to use the more modern, better maintained
16516 algorithm, with reasonable defaults for the weights. Closes
16518 - Remove the --disable-curve25519 configure option. Relays and
16519 clients now are required to support curve25519 and the
16521 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
16522 used to be deprecated synonyms for "StrictNodes", are now marked
16523 obsolete. Resolves ticket 12226.
16524 - Clients don't understand the BadDirectory flag in the consensus
16525 anymore, and ignore it.
16527 o Removed platform support:
16528 - We no longer include special code to build on Windows CE; as far
16529 as we know, nobody has used Tor on Windows CE in a very long time.
16530 Closes ticket 11446.
16532 o Testing (test-network.sh):
16533 - Stop using "echo -n", as some shells' built-in echo doesn't
16534 support "-n". Instead, use "/bin/echo -n". Partially fixes
16536 - Stop an apparent test-network hang when used with make -j2. Fixes
16538 - Add a --delay option to test-network.sh, which configures the
16539 delay before the chutney network tests for data transmission.
16540 Partially implements ticket 13161.
16543 - Test that tor does not fail when key files are zero-length. Check
16544 that tor generates new keys, and overwrites the empty key files.
16545 - Test that tor generates new keys when keys are missing
16546 (existing behavior).
16547 - Test that tor does not overwrite key files that already contain
16548 data (existing behavior). Tests bug 13111. Patch by "teor".
16549 - New "make test-stem" target to run stem integration tests.
16550 Requires that the "STEM_SOURCE_DIR" environment variable be set.
16551 Closes ticket 14107.
16552 - Make the test_cmdline_args.py script work correctly on Windows.
16553 Patch from Gisle Vanem.
16554 - Move the slower unit tests into a new "./src/test/test-slow"
16555 binary that can be run independently of the other tests. Closes
16557 - New tests for many parts of channel, relay, and circuitmux
16558 functionality. Code by Andrea; part of 9262.
16559 - New tests for parse_transport_line(). Part of ticket 6456.
16560 - In the unit tests, use chgrp() to change the group of the unit
16561 test temporary directory to the current user, so that the sticky
16562 bit doesn't interfere with tests that check directory groups.
16564 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
16566 - Refactor the function that chooses guard nodes so that it can more
16567 easily be tested; write some tests for it.
16568 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
16569 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
16570 - Create unit tests for format_time_interval(). With bug 13393.
16571 - Add unit tests for tor_timegm signed overflow, tor_timegm and
16572 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
16573 tests (visible) fixes in bug 13476.
16574 - Add a "coverage-html" make target to generate HTML-visualized
16575 coverage results when building with --enable-coverage. (Requires
16576 lcov.) Patch from Kevin Murray.
16577 - Enable the backtrace handler (where supported) when running the
16579 - Revise all unit tests that used the legacy test_* macros to
16580 instead use the recommended tt_* macros. This patch was generated
16581 with coccinelle, to avoid manual errors. Closes ticket 13119.
16583 Changes in version 0.2.5.11 - 2015-03-17
16584 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
16586 It backports several bugfixes from the 0.2.6 branch, including a
16587 couple of medium-level security fixes for relays and exit nodes.
16588 It also updates the list of directory authorities.
16590 o Directory authority changes:
16591 - Remove turtles as a directory authority.
16592 - Add longclaw as a new (v3) directory authority. This implements
16593 ticket 13296. This keeps the directory authority count at 9.
16594 - The directory authority Faravahar has a new IP address. This
16595 closes ticket 14487.
16597 o Major bugfixes (crash, OSX, security):
16598 - Fix a remote denial-of-service opportunity caused by a bug in
16599 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16602 o Major bugfixes (relay, stability, possible security):
16603 - Fix a bug that could lead to a relay crashing with an assertion
16604 failure if a buffer of exactly the wrong layout was passed to
16605 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16606 0.2.0.10-alpha. Patch from 'cypherpunks'.
16607 - Do not assert if the 'data' pointer on a buffer is advanced to the
16608 very end of the buffer; log a BUG message instead. Only assert if
16609 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16611 o Major bugfixes (exit node stability):
16612 - Fix an assertion failure that could occur under high DNS load.
16613 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16614 diagnosed and fixed by "cypherpunks".
16616 o Major bugfixes (Linux seccomp2 sandbox):
16617 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16618 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16619 0.2.5.1-alpha. Patch from "sanic".
16621 o Minor features (controller):
16622 - New "GETINFO bw-event-cache" to get information about recent
16623 bandwidth events. Closes ticket 14128. Useful for controllers to
16624 get recent bandwidth history after the fix for ticket 13988.
16626 o Minor features (geoip):
16627 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16628 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16631 o Minor bugfixes (client, automapping):
16632 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16633 no value follows the option. Fixes bug 14142; bugfix on
16634 0.2.4.7-alpha. Patch by "teor".
16635 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16636 14195; bugfix on 0.1.0.1-rc.
16638 o Minor bugfixes (compilation):
16639 - Build without warnings with the stock OpenSSL srtp.h header, which
16640 has a duplicate declaration of SSL_get_selected_srtp_profile().
16641 Fixes bug 14220; this is OpenSSL's bug, not ours.
16643 o Minor bugfixes (directory authority):
16644 - Allow directory authorities to fetch more data from one another if
16645 they find themselves missing lots of votes. Previously, they had
16646 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16647 bugfix on 0.1.2.5-alpha.
16648 - Enlarge the buffer to read bwauth generated files to avoid an
16649 issue when parsing the file in dirserv_read_measured_bandwidths().
16650 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16652 o Minor bugfixes (statistics):
16653 - Increase period over which bandwidth observations are aggregated
16654 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
16656 o Minor bugfixes (preventative security, C safety):
16657 - When reading a hexadecimal, base-32, or base-64 encoded value from
16658 a string, always overwrite the whole output buffer. This prevents
16659 some bugs where we would look at (but fortunately, not reveal)
16660 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
16664 Changes in version 0.2.4.26 - 2015-03-17
16665 Tor 0.2.4.26 includes an updated list of directory authorities. It
16666 also backports a couple of stability and security bugfixes from 0.2.5
16669 o Directory authority changes:
16670 - Remove turtles as a directory authority.
16671 - Add longclaw as a new (v3) directory authority. This implements
16672 ticket 13296. This keeps the directory authority count at 9.
16673 - The directory authority Faravahar has a new IP address. This
16674 closes ticket 14487.
16676 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
16677 - Fix an assertion failure that could occur under high DNS load.
16678 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16679 diagnosed and fixed by "cypherpunks".
16681 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
16682 - Fix a bug that could lead to a relay crashing with an assertion
16683 failure if a buffer of exactly the wrong layout was passed to
16684 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16685 0.2.0.10-alpha. Patch from 'cypherpunks'.
16686 - Do not assert if the 'data' pointer on a buffer is advanced to the
16687 very end of the buffer; log a BUG message instead. Only assert if
16688 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16690 o Minor features (geoip):
16691 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16692 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16695 Changes in version 0.2.5.10 - 2014-10-24
16696 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
16698 It adds several new security features, including improved
16699 denial-of-service resistance for relays, new compiler hardening
16700 options, and a system-call sandbox for hardened installations on Linux
16701 (requires seccomp2). The controller protocol has several new features,
16702 resolving IPv6 addresses should work better than before, and relays
16703 should be a little more CPU-efficient. We've added support for more
16704 OpenBSD and FreeBSD transparent proxy types. We've improved the build
16705 system and testing infrastructure to allow unit testing of more parts
16706 of the Tor codebase. Finally, we've addressed several nagging pluggable
16707 transport usability issues, and included numerous other small bugfixes
16708 and features mentioned below.
16710 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
16711 have accumulated many known flaws; everyone should upgrade.
16713 o Major features (security):
16714 - The ntor handshake is now on-by-default, no matter what the
16715 directory authorities recommend. Implements ticket 8561.
16716 - Make the "tor-gencert" tool used by directory authority operators
16717 create 2048-bit signing keys by default (rather than 1024-bit, since
16718 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16719 - Warn about attempts to run hidden services and relays in the same
16720 process: that's probably not a good idea. Closes ticket 12908.
16721 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
16722 today support TLS 1.0 or later, so we can safely turn off support
16723 for this old (and insecure) protocol. Fixes bug 13426.
16725 o Major features (relay security, DoS-resistance):
16726 - When deciding whether we have run out of memory and we need to
16727 close circuits, also consider memory allocated in buffers for
16728 streams attached to each circuit.
16730 This change, which extends an anti-DoS feature introduced in
16731 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
16732 better resist more memory-based DoS attacks than before. Since the
16733 MaxMemInCellQueues option now applies to all queues, it is renamed
16734 to MaxMemInQueues. This feature fixes bug 10169.
16735 - Avoid hash-flooding denial-of-service attacks by using the secure
16736 SipHash-2-4 hash function for our hashtables. Without this
16737 feature, an attacker could degrade performance of a targeted
16738 client or server by flooding their data structures with a large
16739 number of entries to be stored at the same hash table position,
16740 thereby slowing down the Tor instance. With this feature, hash
16741 table positions are derived from a randomized cryptographic key,
16742 and an attacker cannot predict which entries will collide. Closes
16744 - If you don't specify MaxMemInQueues yourself, Tor now tries to
16745 pick a good value based on your total system memory. Previously,
16746 the default was always 8 GB. You can still override the default by
16747 setting MaxMemInQueues yourself. Resolves ticket 11396.
16749 o Major features (bridges and pluggable transports):
16750 - Add support for passing arguments to managed pluggable transport
16751 proxies. Implements ticket 3594.
16752 - Bridges now track GeoIP information and the number of their users
16753 even when pluggable transports are in use, and report usage
16754 statistics in their extra-info descriptors. Resolves tickets 4773
16756 - Don't launch pluggable transport proxies if we don't have any
16757 bridges configured that would use them. Now we can list many
16758 pluggable transports, and Tor will dynamically start one when it
16759 hears a bridge address that needs it. Resolves ticket 5018.
16760 - The bridge directory authority now assigns status flags (Stable,
16761 Guard, etc) to bridges based on thresholds calculated over all
16762 Running bridges. Now bridgedb can finally make use of its features
16763 to e.g. include at least one Stable bridge in its answers. Fixes
16766 o Major features (controller):
16767 - Extend ORCONN controller event to include an "ID" parameter,
16768 and add four new controller event types CONN_BW, CIRC_BW,
16769 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
16770 The new events are emitted in private Tor networks only, with the
16771 goal of being able to better track performance and load during
16772 full-network simulations. Implements proposal 218 and ticket 7359.
16774 o Major features (relay performance):
16775 - Speed up server-side lookups of rendezvous and introduction point
16776 circuits by using hashtables instead of linear searches. These
16777 functions previously accounted between 3 and 7% of CPU usage on
16778 some busy relays. Resolves ticket 9841.
16779 - Avoid wasting CPU when extending a circuit over a channel that is
16780 nearly out of circuit IDs. Previously, we would do a linear scan
16781 over possible circuit IDs before finding one or deciding that we
16782 had exhausted our possibilities. Now, we try at most 64 random
16783 circuit IDs before deciding that we probably won't succeed. Fixes
16784 a possible root cause of ticket 11553.
16786 o Major features (seccomp2 sandbox, Linux only):
16787 - Use the seccomp2 syscall filtering facility on Linux to limit
16788 which system calls Tor can invoke. This is an experimental,
16789 Linux-only feature to provide defense-in-depth against unknown
16790 attacks. To try turning it on, set "Sandbox 1" in your torrc
16791 file. Please be ready to report bugs. We hope to add support
16792 for better sandboxing in the future, including more fine-grained
16793 filters, better division of responsibility, and support for more
16794 platforms. This work has been done by Cristian-Matei Toader for
16795 Google Summer of Code. Resolves tickets 11351 and 11465.
16797 o Major features (testing networks):
16798 - Make testing Tor networks bootstrap better: lower directory fetch
16799 retry schedules and maximum interval without directory requests,
16800 and raise maximum download tries. Implements ticket 6752.
16801 - Add make target 'test-network' to run tests on a Chutney network.
16802 Implements ticket 8530.
16804 o Major features (other):
16805 - On some platforms (currently: recent OSX versions, glibc-based
16806 platforms that support the ELF format, and a few other
16807 Unix-like operating systems), Tor can now dump stack traces
16808 when a crash occurs or an assertion fails. By default, traces
16809 are dumped to stderr (if possible) and to any logs that are
16810 reporting errors. Implements ticket 9299.
16812 o Deprecated versions:
16813 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
16814 attention for some while.
16816 o Major bugfixes (security, directory authorities):
16817 - Directory authorities now include a digest of each relay's
16818 identity key as a part of its microdescriptor.
16820 This is a workaround for bug 11743 (reported by "cypherpunks"),
16821 where Tor clients do not support receiving multiple
16822 microdescriptors with the same SHA256 digest in the same
16823 consensus. When clients receive a consensus like this, they only
16824 use one of the relays. Without this fix, a hostile relay could
16825 selectively disable some client use of target relays by
16826 constructing a router descriptor with a different identity and the
16827 same microdescriptor parameters and getting the authorities to
16828 list it in a microdescriptor consensus. This fix prevents an
16829 attacker from causing a microdescriptor collision, because the
16830 router's identity is not forgeable.
16832 o Major bugfixes (openssl bug workaround):
16833 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
16834 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
16835 bug 13471. This is a workaround for an OpenSSL bug.
16837 o Major bugfixes (client):
16838 - Perform circuit cleanup operations even when circuit
16839 construction operations are disabled (because the network is
16840 disabled, or because there isn't enough directory information).
16841 Previously, when we were not building predictive circuits, we
16842 were not closing expired circuits either. Fixes bug 8387; bugfix on
16843 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
16844 became more strict about when we have "enough directory information
16845 to build circuits".
16847 o Major bugfixes (client, pluggable transports):
16848 - When managing pluggable transports, use OS notification facilities
16849 to learn if they have crashed, and don't attempt to kill any
16850 process that has already exited. Fixes bug 8746; bugfix
16853 o Major bugfixes (relay denial of service):
16854 - Instead of writing destroy cells directly to outgoing connection
16855 buffers, queue them and intersperse them with other outgoing cells.
16856 This can prevent a set of resource starvation conditions where too
16857 many pending destroy cells prevent data cells from actually getting
16858 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
16859 bugfix on 0.2.0.1-alpha.
16861 o Major bugfixes (relay):
16862 - Avoid queuing or sending destroy cells for circuit ID zero when we
16863 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
16864 Found and fixed by "cypherpunks".
16865 - Fix ORPort reachability detection on relays running behind a
16866 proxy, by correctly updating the "local" mark on the controlling
16867 channel when changing the address of an or_connection_t after the
16868 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
16869 - Use a direct dirport connection when uploading non-anonymous
16870 descriptors to the directory authorities. Previously, relays would
16871 incorrectly use tunnel connections under a fairly wide variety of
16872 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
16873 - When a circuit accidentally has the same circuit ID for its
16874 forward and reverse direction, correctly detect the direction of
16875 cells using that circuit. Previously, this bug made roughly one
16876 circuit in a million non-functional. Fixes bug 12195; this is a
16877 bugfix on every version of Tor.
16879 o Minor features (security):
16880 - New --enable-expensive-hardening option to enable security
16881 hardening options that consume nontrivial amounts of CPU and
16882 memory. Right now, this includes AddressSanitizer and UbSan, which
16883 are supported in newer versions of GCC and Clang. Closes ticket
16885 - Authorities now assign the Guard flag to the fastest 25% of the
16886 network (it used to be the fastest 50%). Also raise the consensus
16887 weight that guarantees the Guard flag from 250 to 2000. For the
16888 current network, this results in about 1100 guards, down from 2500.
16889 This step paves the way for moving the number of entry guards
16890 down to 1 (proposal 236) while still providing reasonable expected
16891 performance for most users. Implements ticket 12690.
16893 o Minor features (security, memory management):
16894 - Memory allocation tricks (mempools and buffer freelists) are now
16895 disabled by default. You can turn them back on with
16896 --enable-mempools and --enable-buf-freelists respectively. We're
16897 disabling these features because malloc performance is good enough
16898 on most platforms, and a similar feature in OpenSSL exacerbated
16899 exploitation of the Heartbleed attack. Resolves ticket 11476.
16901 o Minor features (bridge client):
16902 - Report a more useful failure message when we can't connect to a
16903 bridge because we don't have the right pluggable transport
16904 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
16906 o Minor features (bridge):
16907 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
16908 cookie file for the ExtORPort g+r by default.
16910 o Minor features (bridges, pluggable transports):
16911 - Bridges now write the SHA1 digest of their identity key
16912 fingerprint (that is, a hash of a hash of their public key) to
16913 notice-level logs, and to a new hashed-fingerprint file. This
16914 information will help bridge operators look up their bridge in
16915 Globe and similar tools. Resolves ticket 10884.
16916 - Improve the message that Tor displays when running as a bridge
16917 using pluggable transports without an Extended ORPort listener.
16918 Also, log the message in the log file too. Resolves ticket 11043.
16919 - Add threshold cutoffs to the networkstatus document created by
16920 the Bridge Authority. Fixes bug 1117.
16921 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16922 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16923 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16924 Vidalia set this option for us.) Implements ticket 10297.
16926 o Minor features (build):
16927 - The configure script has a --disable-seccomp option to turn off
16928 support for libseccomp on systems that have it, in case it (or
16929 Tor's use of it) is broken. Resolves ticket 11628.
16930 - Assume that a user using ./configure --host wants to cross-compile,
16931 and give an error if we cannot find a properly named
16932 tool-chain. Add a --disable-tool-name-check option to proceed
16933 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16934 - If we run ./configure and the compiler recognizes -fstack-protector
16935 but the linker rejects it, warn the user about a potentially missing
16936 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16937 - Add support for `--library-versions` flag. Implements ticket 6384.
16938 - Return the "unexpected sendme" warnings to a warn severity, but make
16939 them rate limited, to help diagnose ticket 8093.
16940 - Detect a missing asciidoc, and warn the user about it, during
16941 configure rather than at build time. Fixes issue 6506. Patch from
16944 o Minor features (client):
16945 - Add a new option, PredictedPortsRelevanceTime, to control how long
16946 after having received a request to connect to a given port Tor
16947 will try to keep circuits ready in anticipation of future requests
16948 for that port. Patch from "unixninja92"; implements ticket 9176.
16950 o Minor features (config options and command line):
16951 - Add an --allow-missing-torrc commandline option that tells Tor to
16952 run even if the configuration file specified by -f is not available.
16953 Implements ticket 10060.
16954 - Add support for the TPROXY transparent proxying facility on Linux.
16955 See documentation for the new TransProxyType option for more
16956 details. Implementation by "thomo". Closes ticket 10582.
16958 o Minor features (config options):
16959 - Config (torrc) lines now handle fingerprints which are missing
16960 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16961 - Support a --dump-config option to print some or all of the
16962 configured options. Mainly useful for debugging the command-line
16963 option parsing code. Helps resolve ticket 4647.
16964 - Raise awareness of safer logging: notify user of potentially
16965 unsafe config options, like logging more verbosely than severity
16966 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16967 - Add a new configuration option TestingV3AuthVotingStartOffset
16968 that bootstraps a network faster by changing the timing for
16969 consensus votes. Addresses ticket 8532.
16970 - Add a new torrc option "ServerTransportOptions" that allows
16971 bridge operators to pass configuration parameters to their
16972 pluggable transports. Resolves ticket 8929.
16973 - The config (torrc) file now accepts bandwidth and space limits in
16974 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16975 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16978 o Minor features (controller):
16979 - Make the entire exit policy available from the control port via
16980 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
16982 - Because of the fix for ticket 11396, the real limit for memory
16983 usage may no longer match the configured MaxMemInQueues value. The
16984 real limit is now exposed via GETINFO limits/max-mem-in-queues.
16985 - Add a new "HS_DESC" controller event that reports activities
16986 related to hidden service descriptors. Resolves ticket 8510.
16987 - New "DROPGUARDS" controller command to forget all current entry
16988 guards. Not recommended for ordinary use, since replacing guards
16989 too frequently makes several attacks easier. Resolves ticket 9934;
16991 - Implement the TRANSPORT_LAUNCHED control port event that
16992 notifies controllers about new launched pluggable
16993 transports. Resolves ticket 5609.
16995 o Minor features (diagnostic):
16996 - When logging a warning because of bug 7164, additionally check the
16997 hash table for consistency (as proposed on ticket 11737). This may
16998 help diagnose bug 7164.
16999 - When we log a heartbeat, log how many one-hop circuits we have
17000 that are at least 30 minutes old, and log status information about
17001 a few of them. This is an attempt to track down bug 8387.
17002 - When encountering an unexpected CR while writing text to a file on
17003 Windows, log the name of the file. Should help diagnosing
17005 - Give more specific warnings when a client notices that an onion
17006 handshake has failed. Fixes ticket 9635.
17007 - Add significant new logging code to attempt to diagnose bug 12184,
17008 where relays seem to run out of available circuit IDs.
17009 - Improve the diagnostic log message for bug 8387 even further to
17010 try to improve our odds of figuring out why one-hop directory
17011 circuits sometimes do not get closed.
17012 - Add more log messages to diagnose bug 7164, which causes
17013 intermittent "microdesc_free() called but md was still referenced"
17014 warnings. We now include more information, to figure out why we
17015 might be cleaning a microdescriptor for being too old if it's
17016 still referenced by a live node_t object.
17017 - Log current accounting state (bytes sent and received + remaining
17018 time for the current accounting period) in the relay's heartbeat
17019 message. Implements ticket 5526; patch from Peter Retzlaff.
17021 o Minor features (geoip):
17022 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17025 o Minor features (interface):
17026 - Generate a warning if any ports are listed in the SocksPolicy,
17027 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
17028 AuthDirBadExit options. (These options only support address
17029 ranges.) Fixes part of ticket 11108.
17031 o Minor features (kernel API usage):
17032 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
17033 sockets in a single system call. Implements ticket 5129.
17035 o Minor features (log messages):
17036 - When ServerTransportPlugin is set on a bridge, Tor can write more
17037 useful statistics about bridge use in its extrainfo descriptors,
17038 but only if the Extended ORPort ("ExtORPort") is set too. Add a
17039 log message to inform the user in this case. Resolves ticket 9651.
17040 - When receiving a new controller connection, log the origin address.
17041 Resolves ticket 9698; patch from "sigpipe".
17042 - When logging OpenSSL engine status at startup, log the status of
17043 more engines. Fixes ticket 10043; patch from Joshua Datko.
17045 o Minor features (log verbosity):
17046 - Demote the message that we give when a flushing connection times
17047 out for too long from NOTICE to INFO. It was usually meaningless.
17048 Resolves ticket 5286.
17049 - Don't log so many notice-level bootstrapping messages at startup
17050 about downloading descriptors. Previously, we'd log a notice
17051 whenever we learned about more routers. Now, we only log a notice
17052 at every 5% of progress. Fixes bug 9963.
17053 - Warn less verbosely when receiving a malformed
17054 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
17056 o Minor features (performance):
17057 - If we're using the pure-C 32-bit curve25519_donna implementation
17058 of curve25519, build it with the -fomit-frame-pointer option to
17059 make it go faster on register-starved hosts. This improves our
17060 handshake performance by about 6% on i386 hosts without nacl.
17061 Closes ticket 8109.
17063 o Minor features (relay):
17064 - If a circuit timed out for at least 3 minutes, check if we have a
17065 new external IP address, and publish a new descriptor with the new
17066 IP address if it changed. Resolves ticket 2454.
17068 o Minor features (testing):
17069 - If Python is installed, "make check" now runs extra tests beyond
17070 the unit test scripts.
17071 - When bootstrapping a test network, sometimes very few relays get
17072 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
17073 specify a set of relays which should be voted Guard regardless of
17074 their uptime or bandwidth. Addresses ticket 9206.
17076 o Minor features (transparent proxy, *BSD):
17077 - Support FreeBSD's ipfw firewall interface for TransPort ports on
17078 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
17079 10267; patch from "yurivict".
17080 - Support OpenBSD's divert-to rules with the pf firewall for
17081 transparent proxy ports. To enable it, set "TransProxyType
17082 pf-divert". This allows Tor to run a TransPort transparent proxy
17083 port on OpenBSD 4.4 or later without root privileges. See the
17084 pf.conf(5) manual page for information on configuring pf to use
17085 divert-to rules. Closes ticket 10896; patch from Dana Koch.
17087 o Minor bugfixes (bridge client):
17088 - Stop accepting bridge lines containing hostnames. Doing so would
17089 cause clients to perform DNS requests on the hostnames, which was
17090 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
17092 o Minor bugfixes (bridges):
17093 - Avoid potential crashes or bad behavior when launching a
17094 server-side managed proxy with ORPort or ExtORPort temporarily
17095 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
17096 - Fix a bug where the first connection works to a bridge that uses a
17097 pluggable transport with client-side parameters, but we don't send
17098 the client-side parameters on subsequent connections. (We don't
17099 use any pluggable transports with client-side parameters yet,
17100 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
17101 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
17103 o Minor bugfixes (build, auxiliary programs):
17104 - Stop preprocessing the "torify" script with autoconf, since
17105 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
17107 - The tor-fw-helper program now follows the standard convention and
17108 exits with status code "0" on success. Fixes bug 9030; bugfix on
17109 0.2.3.1-alpha. Patch by Arlo Breault.
17110 - Corrected ./configure advice for what openssl dev package you should
17111 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
17113 o Minor bugfixes (client):
17114 - Avoid "Tried to open a socket with DisableNetwork set" warnings
17115 when starting a client with bridges configured and DisableNetwork
17116 set. (Tor launcher starts Tor with DisableNetwork set the first
17117 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
17118 - Improve the log message when we can't connect to a hidden service
17119 because all of the hidden service directory nodes hosting its
17120 descriptor are excluded. Improves on our fix for bug 10722, which
17121 was a bugfix on 0.2.0.10-alpha.
17122 - Raise a control port warning when we fail to connect to all of
17123 our bridges. Previously, we didn't inform the controller, and
17124 the bootstrap process would stall. Fixes bug 11069; bugfix on
17126 - Exit immediately when a process-owning controller exits.
17127 Previously, tor relays would wait for a little while after their
17128 controller exited, as if they had gotten an INT signal -- but this
17129 was problematic, since there was no feedback for the user. To do a
17130 clean shutdown, controllers should send an INT signal and give Tor
17131 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
17132 - Stop attempting to connect to bridges before our pluggable
17133 transports are configured (harmless but resulted in some erroneous
17134 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
17135 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
17136 generating incorrect SOCKS5 responses, and confusing client
17137 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
17139 o Minor bugfixes (client, DNSPort):
17140 - When using DNSPort, try to respond to AAAA requests with AAAA
17141 answers. Previously, we hadn't looked at the request type when
17142 deciding which answer type to prefer. Fixes bug 10468; bugfix on
17144 - When receiving a DNS query for an unsupported record type, reply
17145 with no answer rather than with a NOTIMPL error. This behavior
17146 isn't correct either, but it will break fewer client programs, we
17147 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
17150 o Minor bugfixes (client, logging during bootstrap):
17151 - Only report the first fatal bootstrap error on a given OR
17152 connection. This stops us from telling the controller bogus error
17153 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
17154 - Avoid generating spurious warnings when starting with
17155 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
17158 o Minor bugfixes (closing OR connections):
17159 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
17160 check if it's an or_connection_t and correctly call
17161 connection_or_close_for_error() rather than
17162 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
17164 - When closing all connections on setting DisableNetwork to 1, use
17165 connection_or_close_normally() rather than closing OR connections
17166 out from under the channel layer. Fixes bug 11306; bugfix on
17169 o Minor bugfixes (code correctness):
17170 - Previously we used two temporary files when writing descriptors to
17171 disk; now we only use one. Fixes bug 1376.
17172 - Remove an erroneous (but impossible and thus harmless) pointer
17173 comparison that would have allowed compilers to skip a bounds
17174 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
17175 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
17176 - Fix an always-true assertion in pluggable transports code so it
17177 actually checks what it was trying to check. Fixes bug 10046;
17178 bugfix on 0.2.3.9-alpha. Found by "dcb".
17180 o Minor bugfixes (command line):
17181 - Use a single command-line parser for parsing torrc options on the
17182 command line and for finding special command-line options to avoid
17183 inconsistent behavior for torrc option arguments that have the same
17184 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
17186 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
17187 9573; bugfix on 0.0.9pre5.
17189 o Minor bugfixes (compilation):
17190 - Compile correctly with builds and forks of OpenSSL (such as
17191 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
17192 0.2.1.1-alpha. Patch from "dhill".
17193 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
17194 turned off (that is, without support for v2 link handshakes). Fixes
17195 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
17196 - In routerlist_assert_ok(), don't take the address of a
17197 routerinfo's cache_info member unless that routerinfo is non-NULL.
17198 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
17199 - Fix a large number of false positive warnings from the clang
17200 analyzer static analysis tool. This should make real warnings
17201 easier for clang analyzer to find. Patch from "teor". Closes
17203 - Resolve GCC complaints on OpenBSD about discarding constness in
17204 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
17205 on 0.1.1.23. Patch from Dana Koch.
17206 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
17207 treatment of long and time_t as comparable types. Fixes part of
17208 bug 11633. Patch from Dana Koch.
17209 - When deciding whether to build the 64-bit curve25519
17210 implementation, detect platforms where we can compile 128-bit
17211 arithmetic but cannot link it. Fixes bug 11729; bugfix on
17212 0.2.4.8-alpha. Patch from "conradev".
17213 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
17214 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
17215 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
17217 - Build and run correctly on systems like OpenBSD-current that have
17218 patched OpenSSL to remove get_cipher_by_char and/or its
17219 implementations. Fixes issue 13325.
17221 o Minor bugfixes (controller and command-line):
17222 - If changing a config option via "setconf" fails in a recoverable
17223 way, we used to nonetheless write our new control ports to the
17224 file described by the "ControlPortWriteToFile" option. Now we only
17225 write out that file if we successfully switch to the new config
17226 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
17228 o Minor bugfixes (directory server):
17229 - No longer accept malformed http headers when parsing urls from
17230 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
17231 bugfix on 0.0.6pre1.
17232 - When sending a compressed set of descriptors or microdescriptors,
17233 make sure to finalize the zlib stream. Previously, we would write
17234 all the compressed data, but if the last descriptor we wanted to
17235 send was missing or too old, we would not mark the stream as
17236 finished. This caused problems for decompression tools. Fixes bug
17237 11648; bugfix on 0.1.1.23.
17239 o Minor bugfixes (hidden service):
17240 - Only retry attempts to connect to a chosen rendezvous point 8
17241 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
17243 o Minor bugfixes (interface):
17244 - Reject relative control socket paths and emit a warning. Previously,
17245 single-component control socket paths would be rejected, but Tor
17246 would not log why it could not validate the config. Fixes bug 9258;
17247 bugfix on 0.2.3.16-alpha.
17249 o Minor bugfixes (log messages):
17250 - Fix a bug where clients using bridges would report themselves
17251 as 50% bootstrapped even without a live consensus document.
17252 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
17253 - Suppress a warning where, if there's only one directory authority
17254 in the network, we would complain that votes and signatures cannot
17255 be uploaded to other directory authorities. Fixes bug 10842;
17256 bugfix on 0.2.2.26-beta.
17257 - Report bootstrapping progress correctly when we're downloading
17258 microdescriptors. We had updated our "do we have enough microdescs
17259 to begin building circuits?" logic most recently in 0.2.4.10-alpha
17260 (see bug 5956), but we left the bootstrap status event logic at
17261 "how far through getting 1/4 of them are we?" Fixes bug 9958;
17262 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
17264 o Minor bugfixes (logging):
17265 - Downgrade "Unexpected onionskin length after decryption" warning
17266 to a protocol-warn, since there's nothing relay operators can do
17267 about a client that sends them a malformed create cell. Resolves
17268 bug 12996; bugfix on 0.0.6rc1.
17269 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
17270 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
17271 - When logging information about an EXTEND2 or EXTENDED2 cell, log
17272 their names correctly. Fixes part of bug 12700; bugfix
17274 - When logging information about a relay cell whose command we don't
17275 recognize, log its command as an integer. Fixes part of bug 12700;
17276 bugfix on 0.2.1.10-alpha.
17277 - Escape all strings from the directory connection before logging
17278 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
17279 - Squelch a spurious LD_BUG message "No origin circuit for
17280 successful SOCKS stream" in certain hidden service failure cases;
17282 - Downgrade the severity of the 'unexpected sendme cell from client'
17283 from 'warn' to 'protocol warning'. Closes ticket 8093.
17285 o Minor bugfixes (misc code correctness):
17286 - In munge_extrainfo_into_routerinfo(), check the return value of
17287 memchr(). This would have been a serious issue if we ever passed
17288 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
17290 - On the chance that somebody manages to build Tor on a
17291 platform where time_t is unsigned, correct the way that
17292 microdesc_add_to_cache() handles negative time arguments.
17293 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
17294 - Fix various instances of undefined behavior in channeltls.c,
17295 tor_memmem(), and eventdns.c that would cause us to construct
17296 pointers to memory outside an allocated object. (These invalid
17297 pointers were not accessed, but C does not even allow them to
17298 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
17299 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
17300 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
17301 fix some miscellaneous errors in our tests and codebase. Fixes bug
17302 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
17303 - Always check return values for unlink, munmap, UnmapViewOfFile;
17304 check strftime return values more often. In some cases all we can
17305 do is report a warning, but this may help prevent deeper bugs from
17306 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
17308 - Fix numerous warnings from the clang "scan-build" static analyzer.
17309 Some of these are programming style issues; some of them are false
17310 positives that indicated awkward code; some are undefined behavior
17311 cases related to constructing (but not using) invalid pointers;
17312 some are assumptions about API behavior; some are (harmlessly)
17313 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
17314 correct; and one or two are genuine bugs that weren't reachable
17315 from the rest of the program. Fixes bug 8793; bugfixes on many,
17318 o Minor bugfixes (node selection):
17319 - If ExcludeNodes is set, consider non-excluded hidden service
17320 directory servers before excluded ones. Do not consider excluded
17321 hidden service directory servers at all if StrictNodes is
17322 set. (Previously, we would sometimes decide to connect to those
17323 servers, and then realize before we initiated a connection that
17324 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
17325 Reported by "mr-4".
17326 - If we set the ExitNodes option but it doesn't include any nodes
17327 that have the Exit flag, we would choose not to bootstrap. Now we
17328 bootstrap so long as ExitNodes includes nodes which can exit to
17329 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
17331 o Minor bugfixes (performance):
17332 - Avoid a bug where every successful connection made us recompute
17333 the flag telling us whether we have sufficient information to
17334 build circuits. Previously, we would forget our cached value
17335 whenever we successfully opened a channel (or marked a router as
17336 running or not running for any other reason), regardless of
17337 whether we had previously believed the router to be running. This
17338 forced us to run an expensive update operation far too often.
17339 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
17340 - Avoid using tor_memeq() for checking relay cell integrity. This
17341 removes a possible performance bottleneck. Fixes part of bug
17342 12169; bugfix on 0.2.1.31.
17344 o Minor bugfixes (platform-specific):
17345 - When dumping a malformed directory object to disk, save it in
17346 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
17348 - Don't report failures from make_socket_reuseable() on incoming
17349 sockets on OSX: this can happen when incoming connections close
17350 early. Fixes bug 10081.
17352 o Minor bugfixes (pluggable transports):
17353 - Avoid another 60-second delay when starting Tor in a pluggable-
17354 transport-using configuration when we already have cached
17355 descriptors for our bridges. Fixes bug 11965; bugfix
17358 o Minor bugfixes (protocol correctness):
17359 - When receiving a VERSIONS cell with an odd number of bytes, close
17360 the connection immediately since the cell is malformed. Fixes bug
17361 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
17364 o Minor bugfixes (relay, other):
17365 - We now drop CREATE cells for already-existent circuit IDs and for
17366 zero-valued circuit IDs, regardless of other factors that might
17367 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
17369 - When rejecting DATA cells for stream_id zero, still count them
17370 against the circuit's deliver window so that we don't fail to send
17371 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
17373 o Minor bugfixes (relay, threading):
17374 - Check return code on spawn_func() in cpuworker code, so that we
17375 don't think we've spawned a nonworking cpuworker and write junk to
17376 it forever. Fix related to bug 4345; bugfix on all released Tor
17377 versions. Found by "skruffy".
17378 - Use a pthread_attr to make sure that spawn_func() cannot return an
17379 error while at the same time launching a thread. Fix related to
17380 bug 4345; bugfix on all released Tor versions. Reported
17383 o Minor bugfixes (relays and bridges):
17384 - Avoid crashing on a malformed resolv.conf file when running a
17385 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
17386 - Non-exit relays no longer launch mock DNS requests to check for
17387 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
17388 non-exit relays stopped servicing DNS requests. Fixes bug 965;
17389 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
17390 - Bridges now report complete directory request statistics. Related
17391 to bug 5824; bugfix on 0.2.2.1-alpha.
17392 - Bridges now never collect statistics that were designed for
17393 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
17395 o Minor bugfixes (testing):
17396 - Fix all valgrind warnings produced by the unit tests. There were
17397 over a thousand memory leak warnings previously, mostly produced
17398 by forgetting to free things in the unit test code. Fixes bug
17399 11618, bugfixes on many versions of Tor.
17401 o Minor bugfixes (tor-fw-helper):
17402 - Give a correct log message when tor-fw-helper fails to launch.
17403 (Previously, we would say something like "tor-fw-helper sent us a
17404 string we could not parse".) Fixes bug 9781; bugfix
17407 o Minor bugfixes (trivial memory leaks):
17408 - Fix a small memory leak when signing a directory object. Fixes bug
17409 11275; bugfix on 0.2.4.13-alpha.
17410 - Resolve some memory leaks found by coverity in the unit tests, on
17411 exit in tor-gencert, and on a failure to compute digests for our
17412 own keys when generating a v3 networkstatus vote. These leaks
17413 should never have affected anyone in practice.
17415 o Code simplification and refactoring:
17416 - Remove some old fallback code designed to keep Tor clients working
17417 in a network with only two working relays. Elsewhere in the code we
17418 have long since stopped supporting such networks, so there wasn't
17419 much point in keeping it around. Addresses ticket 9926.
17420 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
17421 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
17422 - Extract the common duplicated code for creating a subdirectory
17423 of the data directory and writing to a file in it. Fixes ticket
17424 4282; patch from Peter Retzlaff.
17425 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
17426 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
17427 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
17428 - Add a set of accessor functions for the circuit timeout data
17429 structure. Fixes ticket 6153; patch from "piet".
17430 - Clean up exit paths from connection_listener_new(). Closes ticket
17431 8789. Patch from Arlo Breault.
17432 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
17433 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
17434 - Use a doubly-linked list to implement the global circuit list.
17435 Resolves ticket 9108. Patch from Marek Majkowski.
17436 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
17437 - Remove constants and tests for PKCS1 padding; it's insecure and
17438 shouldn't be used for anything new. Fixes bug 8792; patch
17440 - Remove instances of strcpy() from the unit tests. They weren't
17441 hurting anything, since they were only in the unit tests, but it's
17442 embarrassing to have strcpy() in the code at all, and some analysis
17443 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
17444 0.2.3.8-alpha. Patch from Arlo Breault.
17445 - Remove is_internal_IP() function. Resolves ticket 4645.
17446 - Remove unused function circuit_dump_by_chan from circuitlist.c.
17447 Closes issue 9107; patch from "marek".
17448 - Change our use of the ENUM_BF macro to avoid declarations that
17450 - Get rid of router->address, since in all cases it was just the
17451 string representation of router->addr. Resolves ticket 5528.
17454 - Adjust the URLs in the README to refer to the new locations of
17455 several documents on the website. Fixes bug 12830. Patch from
17457 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
17459 - Update manpage to describe some of the files you can expect to
17460 find in Tor's DataDirectory. Addresses ticket 9839.
17461 - Clean up several option names in the manpage to match their real
17462 names, add the missing documentation for a couple of testing and
17463 directory authority options, remove the documentation for a
17464 V2-directory fetching option that no longer exists. Resolves
17466 - Correct the documentation so that it lists the correct directory
17467 for the stats files. (They are in a subdirectory called "stats",
17469 - In the manpage, move more authority-only options into the
17470 directory authority section so that operators of regular directory
17471 caches don't get confused.
17472 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
17473 11061; bugfix on 0.2.4.7-alpha.
17474 - Resolve warnings from Doxygen.
17475 - Document in the manpage that "KBytes" may also be written as
17476 "kilobytes" or "KB", that "Kbits" may also be written as
17477 "kilobits", and so forth. Closes ticket 9222.
17478 - Document that the ClientOnly config option overrides ORPort.
17479 Our old explanation made ClientOnly sound as though it did
17480 nothing at all. Resolves bug 9059.
17481 - Explain that SocksPolicy, DirPolicy, and similar options don't
17482 take port arguments. Fixes the other part of ticket 11108.
17483 - Fix a comment about the rend_server_descriptor_t.protocols field
17484 to more accurately describe its range. Also, make that field
17485 unsigned, to more accurately reflect its usage. Fixes bug 9099;
17486 bugfix on 0.2.1.5-alpha.
17487 - Fix the manpage's description of HiddenServiceAuthorizeClient:
17488 the maximum client name length is 16, not 19. Fixes bug 11118;
17489 bugfix on 0.2.1.6-alpha.
17492 - The contrib directory has been sorted and tidied. Before, it was
17493 an unsorted dumping ground for useful and not-so-useful things.
17494 Now, it is divided based on functionality, and the items which
17495 seemed to be nonfunctional or useless have been removed. Resolves
17496 ticket 8966; based on patches from "rl1987".
17498 o Removed code and features:
17499 - Clients now reject any directory authority certificates lacking
17500 a dir-key-crosscert element. These have been included since
17501 0.2.1.9-alpha, so there's no real reason for them to be optional
17502 any longer. Completes proposal 157. Resolves ticket 10162.
17503 - Remove all code that existed to support the v2 directory system,
17504 since there are no longer any v2 directory authorities. Resolves
17506 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
17507 options, which were used for designating authorities as "Hidden
17508 service authorities". There has been no use of hidden service
17509 authorities since 0.2.2.1-alpha, when we stopped uploading or
17510 downloading v0 hidden service descriptors. Fixes bug 10881; also
17511 part of a fix for bug 10841.
17512 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
17513 and MTBF calculations, but that nobody was using. Fixes bug 11742.
17514 - The TunnelDirConns and PreferTunnelledDirConns options no longer
17515 exist; tunneled directory connections have been available since
17516 0.1.2.5-alpha, and turning them off is not a good idea. This is a
17517 brute-force fix for 10849, where "TunnelDirConns 0" would break
17519 - Remove all code for the long unused v1 directory protocol.
17520 Resolves ticket 11070.
17521 - Remove all remaining code related to version-0 hidden service
17522 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
17523 the rest of bug 10841.
17524 - Remove migration code from when we renamed the "cached-routers"
17525 file to "cached-descriptors" back in 0.2.0.8-alpha. This
17526 incidentally resolves ticket 6502 by cleaning up the related code
17527 a bit. Patch from Akshay Hebbar.
17529 o Test infrastructure:
17530 - Tor now builds each source file in two modes: a mode that avoids
17531 exposing identifiers needlessly, and another mode that exposes
17532 more identifiers for testing. This lets the compiler do better at
17533 optimizing the production code, while enabling us to take more
17534 radical measures to let the unit tests test things.
17535 - The production builds no longer include functions used only in
17536 the unit tests; all functions exposed from a module only for
17537 unit-testing are now static in production builds.
17538 - Add an --enable-coverage configuration option to make the unit
17539 tests (and a new src/or/tor-cov target) to build with gcov test
17541 - Update to the latest version of tinytest.
17542 - Improve the tinytest implementation of string operation tests so
17543 that comparisons with NULL strings no longer crash the tests; they
17544 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
17545 - New macros in test.h to simplify writing mock-functions for unit
17546 tests. Part of ticket 11507. Patch from Dana Koch.
17547 - We now have rudimentary function mocking support that our unit
17548 tests can use to test functions in isolation. Function mocking
17549 lets the tests temporarily replace a function's dependencies with
17550 stub functions, so that the tests can check the function without
17551 invoking the other functions it calls.
17554 - Complete tests for the status.c module. Resolves ticket 11507.
17555 Patch from Dana Koch.
17556 - Add more unit tests for the <circid,channel>->circuit map, and
17557 the destroy-cell-tracking code to fix bug 7912.
17558 - Unit tests for failing cases of the TAP onion handshake.
17559 - More unit tests for address-manipulation functions.
17561 o Distribution (systemd):
17562 - Include a tor.service file in contrib/dist for use with systemd.
17563 Some distributions will be able to use this file unmodified;
17564 others will need to tweak it, or write their own. Patch from Jamie
17565 Nguyen; resolves ticket 8368.
17566 - Verify configuration file via ExecStartPre in the systemd unit
17567 file. Patch from intrigeri; resolves ticket 12730.
17568 - Explicitly disable RunAsDaemon in the systemd unit file. Our
17569 current systemd unit uses "Type = simple", so systemd does not
17570 expect tor to fork. If the user has "RunAsDaemon 1" in their
17571 torrc, then things won't work as expected. This is e.g. the case
17572 on Debian (and derivatives), since there we pass "--defaults-torrc
17573 /usr/share/tor/tor-service-defaults-torrc" (that contains
17574 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
17578 Changes in version 0.2.4.25 - 2014-10-20
17579 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
17580 (even though POODLE does not affect Tor). It also works around a crash
17581 bug caused by some operating systems' response to the "POODLE" attack
17582 (which does affect Tor).
17584 o Major security fixes (also in 0.2.5.9-rc):
17585 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17586 today support TLS 1.0 or later, so we can safely turn off support
17587 for this old (and insecure) protocol. Fixes bug 13426.
17589 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
17590 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
17591 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
17592 13471. This is a workaround for an OpenSSL bug.
17595 Changes in version 0.2.4.24 - 2014-09-22
17596 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
17597 connecting to hidden services, and it updates the location of one of
17598 the directory authorities.
17601 - Clients now send the correct address for their chosen rendezvous
17602 point when trying to access a hidden service. They used to send
17603 the wrong address, which would still work some of the time because
17604 they also sent the identity digest of the rendezvous point, and if
17605 the hidden service happened to try connecting to the rendezvous
17606 point from a relay that already had a connection open to it,
17607 the relay would reuse that connection. Now connections to hidden
17608 services should be more robust and faster. Also, this bug meant
17609 that clients were leaking to the hidden service whether they were
17610 on a little-endian (common) or big-endian (rare) system, which for
17611 some users might have reduced their anonymity. Fixes bug 13151;
17612 bugfix on 0.2.1.5-alpha.
17614 o Directory authority changes:
17615 - Change IP address for gabelmoo (v3 directory authority).
17617 o Minor features (geoip):
17618 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17622 Changes in version 0.2.4.23 - 2014-07-28
17623 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
17624 guard rotation, and also backports several important fixes from the
17625 Tor 0.2.5 alpha release series.
17628 - Clients now look at the "usecreatefast" consensus parameter to
17629 decide whether to use CREATE_FAST or CREATE cells for the first hop
17630 of their circuit. This approach can improve security on connections
17631 where Tor's circuit handshake is stronger than the available TLS
17632 connection security levels, but the tradeoff is more computational
17633 load on guard relays. Implements proposal 221. Resolves ticket 9386.
17634 - Make the number of entry guards configurable via a new
17635 NumEntryGuards consensus parameter, and the number of directory
17636 guards configurable via a new NumDirectoryGuards consensus
17637 parameter. Implements ticket 12688.
17640 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
17641 implementation that caused incorrect results on 32-bit
17642 implementations when certain malformed inputs were used along with
17643 a small class of private ntor keys. This bug does not currently
17644 appear to allow an attacker to learn private keys or impersonate a
17645 Tor server, but it could provide a means to distinguish 32-bit Tor
17646 implementations from 64-bit Tor implementations. Fixes bug 12694;
17647 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
17651 - Warn and drop the circuit if we receive an inbound 'relay early'
17652 cell. Those used to be normal to receive on hidden service circuits
17653 due to bug 1038, but the buggy Tor versions are long gone from
17654 the network so we can afford to resume watching for them. Resolves
17655 the rest of bug 1038; bugfix on 0.2.1.19.
17656 - Correct a confusing error message when trying to extend a circuit
17657 via the control protocol but we don't know a descriptor or
17658 microdescriptor for one of the specified relays. Fixes bug 12718;
17659 bugfix on 0.2.3.1-alpha.
17660 - Avoid an illegal read from stack when initializing the TLS
17661 module using a version of OpenSSL without all of the ciphers
17662 used by the v2 link handshake. Fixes bug 12227; bugfix on
17663 0.2.4.8-alpha. Found by "starlight".
17666 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
17670 Changes in version 0.2.4.22 - 2014-05-16
17671 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
17672 alpha release series. These include blocking all authority signing
17673 keys that may have been affected by the OpenSSL "heartbleed" bug,
17674 choosing a far more secure set of TLS ciphersuites by default, closing
17675 a couple of memory leaks that could be used to run a target relay out
17676 of RAM, and several others.
17678 o Major features (security, backport from 0.2.5.4-alpha):
17679 - Block authority signing keys that were used on authorities
17680 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
17681 don't have any evidence that these keys _were_ compromised; we're
17682 doing this to be prudent.) Resolves ticket 11464.
17684 o Major bugfixes (security, OOM):
17685 - Fix a memory leak that could occur if a microdescriptor parse
17686 fails during the tokenizing step. This bug could enable a memory
17687 exhaustion attack by directory servers. Fixes bug 11649; bugfix
17690 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
17691 - The relay ciphersuite list is now generated automatically based on
17692 uniform criteria, and includes all OpenSSL ciphersuites with
17693 acceptable strength and forward secrecy. Previously, we had left
17694 some perfectly fine ciphersuites unsupported due to omission or
17695 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
17696 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
17697 - Relays now trust themselves to have a better view than clients of
17698 which TLS ciphersuites are better than others. (Thanks to bug
17699 11513, the relay list is now well-considered, whereas the client
17700 list has been chosen mainly for anti-fingerprinting purposes.)
17701 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
17702 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
17703 AES128. Resolves ticket 11528.
17704 - Clients now try to advertise the same list of ciphersuites as
17705 Firefox 28. This change enables selection of (fast) GCM
17706 ciphersuites, disables some strange old ciphers, and stops
17707 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
17708 Resolves ticket 11438.
17710 o Minor bugfixes (configuration, security):
17711 - When running a hidden service, do not allow TunneledDirConns 0:
17712 trying to set that option together with a hidden service would
17713 otherwise prevent the hidden service from running, and also make
17714 it publish its descriptors directly over HTTP. Fixes bug 10849;
17715 bugfix on 0.2.1.1-alpha.
17717 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
17718 - Avoid sending a garbage value to the controller when a circuit is
17719 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
17721 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
17722 - Stop leaking memory when we successfully resolve a PTR record.
17723 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
17725 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
17726 - Avoid 60-second delays in the bootstrapping process when Tor is
17727 launching for a second time while using bridges. Fixes bug 9229;
17728 bugfix on 0.2.0.3-alpha.
17730 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
17731 - Give the correct URL in the warning message when trying to run a
17732 relay on an ancient version of Windows. Fixes bug 9393.
17734 o Minor bugfixes (compilation):
17735 - Fix a compilation error when compiling with --disable-curve25519.
17736 Fixes bug 9700; bugfix on 0.2.4.17-rc.
17739 - Downgrade the warning severity for the the "md was still
17740 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
17741 for trying to diagnose this bug, and the current warning in
17742 earlier versions of tor achieves nothing useful. Addresses warning
17745 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
17746 - When we run out of usable circuit IDs on a channel, log only one
17747 warning for the whole channel, and describe how many circuits
17748 there were on the channel. Fixes part of ticket 11553.
17750 o Minor features (security, backport from 0.2.5.4-alpha):
17751 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
17752 leave the default at 8GBytes), to better support Raspberry Pi
17753 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
17755 o Documentation (backport from 0.2.5.4-alpha):
17756 - Correctly document that we search for a system torrc file before
17757 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
17761 Changes in version 0.2.4.21 - 2014-02-28
17762 Tor 0.2.4.21 further improves security against potential adversaries who
17763 find breaking 1024-bit crypto doable, and backports several stability
17764 and robustness patches from the 0.2.5 branch.
17766 o Major features (client security):
17767 - When we choose a path for a 3-hop circuit, make sure it contains
17768 at least one relay that supports the NTor circuit extension
17769 handshake. Otherwise, there is a chance that we're building
17770 a circuit that's worth attacking by an adversary who finds
17771 breaking 1024-bit crypto doable, and that chance changes the game
17772 theory. Implements ticket 9777.
17775 - Do not treat streams that fail with reason
17776 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
17777 since it could also indicate an ENETUNREACH connection error. Fixes
17778 part of bug 10777; bugfix on 0.2.4.8-alpha.
17780 o Code simplification and refactoring:
17781 - Remove data structures which were introduced to implement the
17782 CellStatistics option: they are now redundant with the new timestamp
17783 field in the regular packed_cell_t data structure, which we did
17784 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
17787 - Always clear OpenSSL bignums before freeing them -- even bignums
17788 that don't contain secrets. Resolves ticket 10793. Patch by
17790 - Build without warnings under clang 3.4. (We have some macros that
17791 define static functions only some of which will get used later in
17792 the module. Starting with clang 3.4, these give a warning unless the
17793 unused attribute is set on them.) Resolves ticket 10904.
17794 - Update geoip and geoip6 files to the February 7 2014 Maxmind
17795 GeoLite2 Country database.
17798 - Set the listen() backlog limit to the largest actually supported
17799 on the system, not to the value in a header file. Fixes bug 9716;
17800 bugfix on every released Tor.
17801 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
17802 exit node as a NOROUTE error, not an INTERNAL error, since they
17803 can apparently happen when trying to connect to the wrong sort
17804 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
17805 - Fix build warnings about missing "a2x" comment when building the
17806 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
17807 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
17808 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
17809 not entirely remove it from the connection lists. Fixes bug 9602;
17810 bugfix on 0.2.4.4-alpha.
17811 - Fix a segmentation fault in our benchmark code when running with
17812 Fedora's OpenSSL package, or any other OpenSSL that provides
17813 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
17814 - Turn "circuit handshake stats since last time" log messages into a
17815 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
17817 o Documentation fixes:
17818 - Document that all but one DirPort entry must have the NoAdvertise
17819 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
17822 Changes in version 0.2.4.20 - 2013-12-22
17823 Tor 0.2.4.20 fixes potentially poor random number generation for users
17824 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
17825 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
17826 and 4) have no state file in their DataDirectory (as would happen on
17827 first start). Users who generated relay or hidden service identity
17828 keys in such a situation should discard them and generate new ones.
17830 This release also fixes a logic error that caused Tor clients to build
17831 many more preemptive circuits than they actually need.
17834 - Do not allow OpenSSL engines to replace the PRNG, even when
17835 HardwareAccel is set. The only default builtin PRNG engine uses
17836 the Intel RDRAND instruction to replace the entire PRNG, and
17837 ignores all attempts to seed it with more entropy. That's
17838 cryptographically stupid: the right response to a new alleged
17839 entropy source is never to discard all previously used entropy
17840 sources. Fixes bug 10402; works around behavior introduced in
17841 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
17843 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
17844 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
17845 - Avoid launching spurious extra circuits when a stream is pending.
17846 This fixes a bug where any circuit that _wasn't_ unusable for new
17847 streams would be treated as if it were, causing extra circuits to
17848 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
17851 - Avoid a crash bug when starting with a corrupted microdescriptor
17852 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
17853 - If we fail to dump a previously cached microdescriptor to disk, avoid
17854 freeing duplicate data later on. Fixes bug 10423; bugfix on
17855 0.2.4.13-alpha. Spotted by "bobnomnom".
17858 Changes in version 0.2.4.19 - 2013-12-11
17859 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
17860 (1986-2013). Aaron worked on diverse projects including helping to guide
17861 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
17862 transparency to the U.S government's PACER documents, and contributing
17863 design and development for Tor and Tor2Web. Aaron was one of the latest
17864 martyrs in our collective fight for civil liberties and human rights,
17865 and his death is all the more painful because he was one of us.
17867 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
17868 a new circuit handshake and link encryption that use ECC to provide
17869 better security and efficiency; makes relays better manage circuit
17870 creation requests; uses "directory guards" to reduce client enumeration
17871 risks; makes bridges collect and report statistics about the pluggable
17872 transports they support; cleans up and improves our geoip database;
17873 gets much closer to IPv6 support for clients, bridges, and relays; makes
17874 directory authorities use measured bandwidths rather than advertised
17875 ones when computing flags and thresholds; disables client-side DNS
17876 caching to reduce tracking risks; and fixes a big bug in bridge
17877 reachability testing. This release introduces two new design
17878 abstractions in the code: a new "channel" abstraction between circuits
17879 and or_connections to allow for implementing alternate relay-to-relay
17880 transports, and a new "circuitmux" abstraction storing the queue of
17881 circuits for a channel. The release also includes many stability,
17882 security, and privacy fixes.
17884 o Major features (new circuit handshake):
17885 - Tor now supports a new circuit extension handshake designed by Ian
17886 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
17887 circuit extension handshake, later called "TAP", was a bit slow
17888 (especially on the relay side), had a fragile security proof, and
17889 used weaker keys than we'd now prefer. The new circuit handshake
17890 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
17891 function, making it significantly more secure than the older
17892 handshake, and significantly faster. Tor can use one of two built-in
17893 pure-C curve25519-donna implementations by Adam Langley, or it
17894 can link against the "nacl" library for a tuned version if present.
17896 The built-in version is very fast for 64-bit systems when building
17897 with GCC. The built-in 32-bit version is still faster than the
17898 old TAP protocol, but using libnacl is better on most such hosts.
17900 Implements proposal 216; closes ticket 7202.
17902 o Major features (better link encryption):
17903 - Relays can now enable the ECDHE TLS ciphersuites when available
17904 and appropriate. These ciphersuites let us negotiate forward-secure
17905 TLS secret keys more safely and more efficiently than with our
17906 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
17907 public relays prefer the (faster) P224 group, and bridges prefer
17908 the (more common) P256 group; you can override this with the
17911 This feature requires clients running 0.2.3.17-beta or later,
17912 and requires both sides to be running OpenSSL 1.0.0 or later
17913 with ECC support. OpenSSL 1.0.1, with the compile-time option
17914 "enable-ec_nistp_64_gcc_128", is highly recommended.
17916 Implements the relay side of proposal 198; closes ticket 7200.
17918 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
17919 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
17920 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
17921 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
17922 them to solve bug 6033.)
17924 o Major features (relay performance):
17925 - Instead of limiting the number of queued onionskins (aka circuit
17926 create requests) to a fixed, hard-to-configure number, we limit
17927 the size of the queue based on how many we expect to be able to
17928 process in a given amount of time. We estimate the time it will
17929 take to process an onionskin based on average processing time
17930 of previous onionskins. Closes ticket 7291. You'll never have to
17931 configure MaxOnionsPending again.
17932 - Relays process the new "NTor" circuit-level handshake requests
17933 with higher priority than the old "TAP" circuit-level handshake
17934 requests. We still process some TAP requests to not totally starve
17935 0.2.3 clients when NTor becomes popular. A new consensus parameter
17936 "NumNTorsPerTAP" lets us tune the balance later if we need to.
17937 Implements ticket 9574.
17939 o Major features (client bootstrapping resilience):
17940 - Add a new "FallbackDir" torrc option to use when we can't use
17941 a directory mirror from the consensus (either because we lack a
17942 consensus, or because they're all down). Currently, all authorities
17943 are fallbacks by default, and there are no other default fallbacks,
17944 but that will change. This option will allow us to give clients a
17945 longer list of servers to try to get a consensus from when first
17946 connecting to the Tor network, and thereby reduce load on the
17947 directory authorities. Implements proposal 206, "Preconfigured
17948 directory sources for bootstrapping". We also removed the old
17949 "FallbackNetworkstatus" option, since we never got it working well
17950 enough to use it. Closes bug 572.
17951 - If we have no circuits open, use a relaxed timeout (the
17952 95th-percentile cutoff) until a circuit succeeds. This heuristic
17953 should allow Tor to succeed at building circuits even when the
17954 network connection drastically changes. Should help with bug 3443.
17956 o Major features (use of guards):
17957 - Support directory guards (proposal 207): when possible, clients now
17958 use their entry guards for non-anonymous directory requests. This
17959 can help prevent client enumeration. Note that this behavior only
17960 works when we have a usable consensus directory, and when options
17961 about what to download are more or less standard. In the future we
17962 should re-bootstrap from our guards, rather than re-bootstrapping
17963 from the preconfigured list of directory sources that ships with
17964 Tor. Resolves ticket 6526.
17965 - Raise the default time that a client keeps an entry guard from
17966 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17967 2012 paper. (We would make it even longer, but we need better client
17968 load balancing first.) Also, make the guard lifetime controllable
17969 via a new GuardLifetime torrc option and a GuardLifetime consensus
17970 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17972 o Major features (bridges with pluggable transports):
17973 - Bridges now report the pluggable transports they support to the
17974 bridge authority, so it can pass the supported transports on to
17975 bridgedb and/or eventually do reachability testing. Implements
17977 - Automatically forward the TCP ports of pluggable transport
17978 proxies using tor-fw-helper if PortForwarding is enabled. Implements
17981 o Major features (geoip database):
17982 - Maxmind began labelling Tor relays as being in country "A1",
17983 which breaks by-country node selection inside Tor. Now we use a
17984 script to replace "A1" ("Anonymous Proxy") entries in our geoip
17985 file with real country codes. This script fixes about 90% of "A1"
17986 entries automatically and uses manual country code assignments to
17987 fix the remaining 10%. See src/config/README.geoip for details.
17989 - Add GeoIP database for IPv6 addresses. The new config option
17991 - Update to the October 2 2013 Maxmind GeoLite Country database.
17993 o Major features (IPv6):
17994 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
17995 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
17996 to happen. Implements ticket 5535.
17997 - All kind of relays, not just bridges, can now advertise an IPv6
17998 OR port. Implements ticket 6362.
17999 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
18000 connectivity, then set the IPv6Exit flag to 1. Also make sure your
18001 exit policy reads as you would like: the address * applies to all
18002 address families, whereas *4 is IPv4 address only, and *6 is IPv6
18003 addresses only. On the client side, you'll need to wait for enough
18004 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
18005 and use Socks5. Closes ticket 5547, implements proposal 117 as
18006 revised in proposal 208.
18007 - Bridge authorities now accept IPv6 bridge addresses and include
18008 them in network status documents. Implements ticket 5534.
18009 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
18011 o Major features (directory authorities):
18012 - Directory authorities now prefer using measured bandwidths to
18013 advertised ones when computing flags and thresholds. Resolves
18015 - Directory authorities that vote measured bandwidths about more
18016 than a threshold number of relays now treat relays with
18017 unmeasured bandwidths as having bandwidth 0 when computing their
18018 flags. Resolves ticket 8435.
18019 - Directory authorities now support a new consensus method (17)
18020 where they cap the published bandwidth of relays for which
18021 insufficient bandwidth measurements exist. Fixes part of bug 2286.
18022 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
18023 serve any v2 directory information. Now we can test disabling the
18024 old deprecated v2 directory format, and see whether doing so has
18025 any effect on network load. Begins to fix bug 6783.
18027 o Major features (build and portability):
18028 - Switch to a nonrecursive Makefile structure. Now instead of each
18029 Makefile.am invoking other Makefile.am's, there is a master
18030 Makefile.am that includes the others. This change makes our build
18031 process slightly more maintainable, and improves parallelism for
18032 building with make -j. Original patch by Stewart Smith; various
18033 fixes by Jim Meyering.
18034 - Where available, we now use automake's "silent" make rules by
18035 default, so that warnings are easier to spot. You can get the old
18036 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18037 - Resume building correctly with MSVC and Makefile.nmake. This patch
18038 resolves numerous bugs and fixes reported by ultramage, including
18039 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
18041 o Security features:
18042 - Switch to a completely time-invariant approach for picking nodes
18043 weighted by bandwidth. Our old approach would run through the
18044 part of the loop after it had made its choice slightly slower
18045 than it ran through the part of the loop before it had made its
18046 choice. Addresses ticket 6538.
18047 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18048 by tor2web clients allows hidden services to identify tor2web
18049 clients through their repeated selection of the same rendezvous
18050 and introduction point circuit endpoints (their guards). Resolves
18053 o Major bugfixes (relay denial of service):
18054 - When we have too much memory queued in circuits (according to a new
18055 MaxMemInCellQueues option), close the circuits that have the oldest
18056 queued cells, on the theory that those are most responsible for
18057 us running low on memory. This prevents us from running out of
18058 memory as a relay if circuits fill up faster than they can be
18059 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
18060 Tor. This bug is a further fix beyond bug 6252, whose fix was
18061 merged into 0.2.3.21-rc.
18062 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
18063 ID: these could be used to create unexpected streams and circuits
18064 which would count as "present" to some parts of Tor but "absent"
18065 to others, leading to zombie circuits and streams or to a bandwidth
18066 denial-of-service. Fixes bug 7889; bugfix on every released version
18067 of Tor. Reported by "oftc_must_be_destroyed".
18068 - Avoid a bug where our response to TLS renegotiation under certain
18069 network conditions could lead to a busy-loop, with 100% CPU
18070 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
18072 o Major bugfixes (asserts, crashes, leaks):
18073 - Prevent the get_freelists() function from running off the end of
18074 the list of freelists if it somehow gets an unrecognized
18075 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
18077 - Avoid a memory leak where we would leak a consensus body when we
18078 find that a consensus which we couldn't previously verify due to
18079 missing certificates is now verifiable. Fixes bug 8719; bugfix
18081 - If we are unable to save a microdescriptor to the journal, do not
18082 drop it from memory and then reattempt downloading it. Fixes bug
18083 9645; bugfix on 0.2.2.6-alpha.
18084 - Fix an assertion failure that would occur when disabling the
18085 ORPort setting on a running Tor process while accounting was
18086 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
18087 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
18088 when an exit connection with optimistic data succeeds immediately
18089 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
18091 - Fix a memory leak that would occur whenever a configuration
18092 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
18094 o Major bugfixes (relay rate limiting):
18095 - When a TLS write is partially successful but incomplete, remember
18096 that the flushed part has been flushed, and notice that bytes were
18097 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
18098 bugfix on Tor 0.1.0.5-rc.
18099 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18100 to 1GB/1GB. The previous defaults were intended to be "basically
18101 infinite", but it turns out they're now limiting our 100mbit+
18102 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18103 last time we raised it).
18104 - No longer stop reading or writing on cpuworker connections when
18105 our rate limiting buckets go empty. Now we should handle circuit
18106 handshake requests more promptly. Resolves bug 9731.
18108 o Major bugfixes (client-side privacy):
18109 - When we mark a circuit as unusable for new circuits, have it
18110 continue to be unusable for new circuits even if MaxCircuitDirtiness
18111 is increased too much at the wrong time, or the system clock jumps
18112 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
18113 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
18114 which have resolved to internal addresses") is set, apply that
18115 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
18116 - When an exit relay rejects a stream with reason "exit policy", but
18117 we only know an exit policy summary (e.g. from the microdesc
18118 consensus) for it, do not mark the relay as useless for all exiting.
18119 Instead, mark just the circuit as unsuitable for that particular
18120 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
18122 o Major bugfixes (stream isolation):
18123 - Allow applications to get proper stream isolation with
18124 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
18125 username/password authentication also offer "no authentication". Tor
18126 had previously preferred "no authentication", so the applications
18127 never actually sent Tor their auth details. Now Tor selects
18128 username/password authentication if it's offered. You can disable
18129 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
18130 bug 8117; bugfix on 0.2.3.3-alpha.
18131 - Follow the socks5 protocol when offering username/password
18132 authentication. The fix for bug 8117 exposed this bug, and it
18133 turns out real-world applications like Pidgin do care. Bugfix on
18134 0.2.3.2-alpha; fixes bug 8879.
18136 o Major bugfixes (client circuit building):
18137 - Alter circuit build timeout measurement to start at the point
18138 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
18139 initialization). This should make our timeout measurements more
18140 uniform. Previously, we were sometimes including ORconn setup time
18141 in our circuit build time measurements. Should resolve bug 3443.
18142 - If the circuit build timeout logic is disabled (via the consensus,
18143 or because we are an authority), then don't build testing circuits.
18144 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
18146 o Major bugfixes (client-side DNS):
18147 - Turn off the client-side DNS cache by default. Updating and using
18148 the DNS cache is now configurable on a per-client-port
18149 level. SOCKSPort, DNSPort, etc lines may now contain
18150 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
18151 cache these types of DNS answers when we receive them from an
18152 exit node in response to an application request on this port, and
18153 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
18154 cached DNS answers of these types, we shouldn't use them. It's
18155 potentially risky to use cached DNS answers at the client, since
18156 doing so can indicate to one exit what answers we've gotten
18157 for DNS lookups in the past. With IPv6, this becomes especially
18158 problematic. Using cached DNS answers for requests on the same
18159 circuit would present less linkability risk, since all traffic
18160 on a circuit is already linkable, but it would also provide
18161 little performance benefit: the exit node caches DNS replies
18162 too. Implements a simplified version of Proposal 205. Implements
18165 o Major bugfixes (hidden service privacy):
18166 - Limit hidden service descriptors to at most ten introduction
18167 points, to slow one kind of guard enumeration. Fixes bug 9002;
18168 bugfix on 0.1.1.11-alpha.
18170 o Major bugfixes (directory fetching):
18171 - If the time to download the next old-style networkstatus is in
18172 the future, do not decline to consider whether to download the
18173 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
18175 - We used to always request authority certificates by identity digest,
18176 meaning we'd get the newest one even when we wanted one with a
18177 different signing key. Then we would complain about being given
18178 a certificate we already had, and never get the one we really
18179 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
18180 resource to request the one we want. Fixes bug 5595; bugfix on
18183 o Major bugfixes (bridge reachability):
18184 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
18185 previously they did not, which prevented them from receiving
18186 successful connections from relays for self-test or bandwidth
18187 testing. Also, when a relay is extending a circuit to a bridge,
18188 it needs to send a NETINFO cell, even when the bridge hasn't sent
18189 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
18191 o Major bugfixes (control interface):
18192 - When receiving a new configuration file via the control port's
18193 LOADCONF command, do not treat the defaults file as absent.
18194 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
18196 o Major bugfixes (directory authorities):
18197 - Stop marking every relay as having been down for one hour every
18198 time we restart a directory authority. These artificial downtimes
18199 were messing with our Stable and Guard flag calculations. Fixes
18200 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
18201 - When computing directory thresholds, ignore any rejected-as-sybil
18202 nodes during the computation so that they can't influence Fast,
18203 Guard, etc. (We should have done this for proposal 109.) Fixes
18205 - When marking a node as a likely sybil, reset its uptime metrics
18206 to zero, so that it cannot time towards getting marked as Guard,
18207 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
18209 - Fix a bug in the voting algorithm that could yield incorrect results
18210 when a non-naming authority declared too many flags. Fixes bug 9200;
18211 bugfix on 0.2.0.3-alpha.
18213 o Internal abstraction features:
18214 - Introduce new channel_t abstraction between circuits and
18215 or_connection_t to allow for implementing alternate OR-to-OR
18216 transports. A channel_t is an abstract object which can either be a
18217 cell-bearing channel, which is responsible for authenticating and
18218 handshaking with the remote OR and transmitting cells to and from
18219 it, or a listening channel, which spawns new cell-bearing channels
18220 at the request of remote ORs. Implements part of ticket 6465.
18221 - Make a channel_tls_t subclass of channel_t, adapting it to the
18222 existing or_connection_t code. The V2/V3 protocol handshaking
18223 code which formerly resided in command.c has been moved below the
18224 channel_t abstraction layer and may be found in channeltls.c now.
18225 Implements the rest of ticket 6465.
18226 - Introduce new circuitmux_t storing the queue of circuits for
18227 a channel; this encapsulates and abstracts the queue logic and
18228 circuit selection policy, and allows the latter to be overridden
18229 easily by switching out a policy object. The existing EWMA behavior
18230 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18232 o New build requirements:
18233 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18234 strongly recommended.
18235 - Tor maintainers now require Automake version 1.9 or later to build
18236 Tor from the Git repository. (Automake is not required when building
18237 from a source distribution.)
18239 o Minor features (protocol):
18240 - No longer include the "opt" prefix when generating routerinfos
18241 or v2 directories: it has been needless since Tor 0.1.2. Closes
18243 - Reject EXTEND cells sent to nonexistent streams. According to the
18244 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18245 we were only checking for stream IDs that were currently in use.
18246 Found while hunting for more instances of bug 6271. Bugfix on
18247 0.0.2pre8, which introduced incremental circuit construction.
18248 - Tor relays and clients now support a better CREATE/EXTEND cell
18249 format, allowing the sender to specify multiple address, identity,
18250 and handshake types. Implements Robert Ransom's proposal 200;
18251 closes ticket 7199.
18252 - Reject as invalid most directory objects containing a NUL.
18253 Belt-and-suspender fix for bug 8037.
18255 o Minor features (security):
18256 - Clear keys and key-derived material left on the stack in
18257 rendservice.c and rendclient.c. Check return value of
18258 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18259 These fixes should make us more forward-secure against cold-boot
18260 attacks and the like. Fixes bug 2385.
18261 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
18262 Irix's random() only return 15 bits; Solaris's random() returns more
18263 bits but its RAND_MAX says it only returns 15, and so on. Motivated
18264 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
18266 o Minor features (control protocol):
18267 - Add a "GETINFO signal/names" control port command. Implements
18269 - Provide default values for all options via "GETINFO config/defaults".
18270 Implements ticket 4971.
18271 - Allow an optional $ before the node identity digest in the
18272 controller command GETINFO ns/id/<identity>, for consistency with
18273 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
18274 - Add CACHED keyword to ADDRMAP events in the control protocol
18275 to indicate whether a DNS result will be cached or not. Resolves
18277 - Generate bootstrapping status update events correctly when fetching
18278 microdescriptors. Fixes bug 9927.
18280 o Minor features (path selection):
18281 - When deciding whether we have enough descriptors to build circuits,
18282 instead of looking at raw relay counts, look at which fraction
18283 of (bandwidth-weighted) paths we're able to build. This approach
18284 keeps clients from building circuits if their paths are likely to
18285 stand out statistically. The default fraction of paths needed is
18286 taken from the consensus directory; you can override it with the
18287 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
18288 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
18289 and we have GeoIP information, also exclude all nodes with unknown
18290 countries "??" and "A1". This behavior is controlled by the
18291 new GeoIPExcludeUnknown option: you can make such nodes always
18292 excluded with "GeoIPExcludeUnknown 1", and disable the feature
18293 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
18294 gets you the default behavior. Implements feature 7706.
18296 o Minor features (hidden services):
18297 - Improve circuit build timeout handling for hidden services.
18298 In particular: adjust build timeouts more accurately depending
18299 upon the number of hop-RTTs that a particular circuit type
18300 undergoes. Additionally, launch intro circuits in parallel
18301 if they timeout, and take the first one to reply as valid.
18302 - The Tor client now ignores sub-domain components of a .onion
18303 address. This change makes HTTP "virtual" hosting
18304 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
18305 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
18306 hosted on the same hidden service. Implements proposal 204.
18307 - Enable Tor to read configuration, state, and key information from
18308 a FIFO. Previously Tor would only read from files with a positive
18309 stat.st_size. Code from meejah; fixes bug 6044.
18311 o Minor features (clients):
18312 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
18313 microdescriptor-related dir requests, and only fall back to normal
18314 descriptors if none of their bridges can handle microdescriptors
18315 (as opposed to the fix in ticket 4013, which caused them to fall
18316 back to normal descriptors if *any* of their bridges preferred
18317 them). Resolves ticket 4994.
18318 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18319 TCP ports to forward. In the past it only accepted two ports:
18320 the ORPort and the DirPort.
18322 o Minor features (protecting client timestamps):
18323 - Clients no longer send timestamps in their NETINFO cells. These were
18324 not used for anything, and they provided one small way for clients
18325 to be distinguished from each other as they moved from network to
18326 network or behind NAT. Implements part of proposal 222.
18327 - Clients now round timestamps in INTRODUCE cells down to the nearest
18328 10 minutes. If a new Support022HiddenServices option is set to 0, or
18329 if it's set to "auto" and the feature is disabled in the consensus,
18330 the timestamp is sent as 0 instead. Implements part of proposal 222.
18331 - Stop sending timestamps in AUTHENTICATE cells. This is not such
18332 a big deal from a security point of view, but it achieves no actual
18333 good purpose, and isn't needed. Implements part of proposal 222.
18334 - Reduce down accuracy of timestamps in hidden service descriptors.
18335 Implements part of proposal 222.
18337 o Minor features (bridges):
18338 - Make bridge relays check once a minute for whether their IP
18339 address has changed, rather than only every 15 minutes. Resolves
18340 bugs 1913 and 1992.
18341 - Bridge statistics now count bridge clients connecting over IPv6:
18342 bridge statistics files now list "bridge-ip-versions" and
18343 extra-info documents list "geoip6-db-digest". The control protocol
18344 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18345 implementation by "shkoo", addressing ticket 5055.
18346 - Add a new torrc option "ServerTransportListenAddr" to let bridge
18347 operators select the address where their pluggable transports will
18348 listen for connections. Resolves ticket 7013.
18349 - Randomize the lifetime of our SSL link certificate, so censors can't
18350 use the static value for filtering Tor flows. Resolves ticket 8443;
18351 related to ticket 4014 which was included in 0.2.2.33.
18353 o Minor features (relays):
18354 - Option OutboundBindAddress can be specified multiple times and
18355 accepts IPv6 addresses. Resolves ticket 6876.
18357 o Minor features (IPv6, client side):
18358 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
18359 prefer to hand out virtual IPv6 addresses, since there are more of
18360 them and we can't run out. To override this behavior and make IPv4
18361 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
18362 or DNSPort you're using for resolving. Implements ticket 7571.
18363 - AutomapHostsOnResolve responses are now randomized, to avoid
18364 annoying situations where Tor is restarted and applications
18365 connect to the wrong addresses.
18366 - Never try more than 1000 times to pick a new virtual address when
18367 AutomapHostsOnResolve is set. That's good enough so long as we
18368 aren't close to handing out our entire virtual address space;
18369 if you're getting there, it's best to switch to IPv6 virtual
18372 o Minor features (IPv6, relay/authority side):
18373 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18374 authorities should set if they have IPv6 connectivity and want to
18375 do reachability tests for IPv6 relays. Implements feature 5974.
18376 - A relay with an IPv6 OR port now sends that address in NETINFO
18377 cells (in addition to its other address). Implements ticket 6364.
18379 o Minor features (directory authorities):
18380 - Directory authorities no long accept descriptors for any version of
18381 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18382 These versions are insecure, unsupported, or both. Implements
18384 - When directory authorities are computing thresholds for flags,
18385 never let the threshold for the Fast flag fall below 4096
18386 bytes. Also, do not consider nodes with extremely low bandwidths
18387 when deciding thresholds for various directory flags. This change
18388 should raise our threshold for Fast relays, possibly in turn
18389 improving overall network performance; see ticket 1854. Resolves
18391 - Directory authorities now include inside each vote a statement of
18392 the performance thresholds they used when assigning flags.
18393 Implements ticket 8151.
18394 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
18395 in directory authority votes to describe whether they have enough
18396 measured bandwidths to ignore advertised (relay descriptor)
18397 bandwidth claims. Resolves ticket 8711.
18399 o Minor features (path bias detection):
18400 - Path Use Bias: Perform separate accounting for successful circuit
18401 use. Keep separate statistics on stream attempt rates versus stream
18402 success rates for each guard. Provide configurable thresholds to
18403 determine when to emit log messages or disable use of guards that
18404 fail too many stream attempts. Resolves ticket 7802.
18405 - Create three levels of Path Bias log messages, as opposed to just
18406 two. These are configurable via consensus as well as via the torrc
18407 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
18408 The default values are 0.70, 0.50, and 0.30 respectively.
18409 - Separate the log message levels from the decision to drop guards,
18410 which also is available via torrc option PathBiasDropGuards.
18411 PathBiasDropGuards still defaults to 0 (off).
18412 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
18413 in combination with PathBiasExtremeRate.
18414 - Increase the default values for PathBiasScaleThreshold and
18415 PathBiasCircThreshold from (200, 20) to (300, 150).
18416 - Add in circuit usage accounting to path bias. If we try to use a
18417 built circuit but fail for any reason, it counts as path bias.
18418 Certain classes of circuits where the adversary gets to pick your
18419 destination node are exempt from this accounting. Usage accounting
18420 can be specifically disabled via consensus parameter or torrc.
18421 - Convert all internal path bias state to double-precision floating
18422 point, to avoid roundoff error and other issues.
18423 - Only record path bias information for circuits that have completed
18424 *two* hops. Assuming end-to-end tagging is the attack vector, this
18425 makes us more resilient to ambient circuit failure without any
18426 detection capability loss.
18428 o Minor features (build):
18429 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18430 dhill. Resolves ticket 6982.
18431 - Compile on win64 using mingw64. Fixes bug 7260; patches from
18433 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
18434 separate error codes; or at least, don't break for that reason.
18435 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
18437 o Build improvements (autotools):
18438 - Warn if building on a platform with an unsigned time_t: there
18439 are too many places where Tor currently assumes that time_t can
18440 hold negative values. We'd like to fix them all, but probably
18442 - Do not report status verbosely from autogen.sh unless the -v flag
18443 is specified. Fixes issue 4664. Patch from Onizuka.
18444 - Detect and reject attempts to build Tor with threading support
18445 when OpenSSL has been compiled without threading support.
18447 - Try to detect if we are ever building on a platform where
18448 memset(...,0,...) does not set the value of a double to 0.0. Such
18449 platforms are permitted by the C standard, though in practice
18450 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
18451 currently support them, but it's better to detect them and fail
18452 than to perform erroneously.
18453 - We no longer warn so much when generating manpages from their
18455 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
18456 the signs of types during autoconf. This is better than our old
18457 approach, which didn't work when cross-compiling.
18459 o Minor features (log messages, warnings):
18460 - Detect when we're running with a version of OpenSSL other than the
18461 one we compiled with. This conflict has occasionally given people
18462 hard-to-track-down errors.
18463 - Warn users who run hidden services on a Tor client with
18464 UseEntryGuards disabled that their hidden services will be
18465 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18466 attack which motivated Tor to support entry guards in the first
18467 place). Resolves ticket 6889.
18468 - Warn when we are binding low ports when hibernation is enabled;
18469 previously we had warned when we were _advertising_ low ports with
18470 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18471 - Issue a warning when running with the bufferevents backend enabled.
18472 It's still not stable, and people should know that they're likely
18473 to hit unexpected problems. Closes ticket 9147.
18475 o Minor features (log messages, notices):
18476 - Refactor resolve_my_address() so it returns the method by which we
18477 decided our public IP address (explicitly configured, resolved from
18478 explicit hostname, guessed from interfaces, learned by gethostname).
18479 Now we can provide more helpful log messages when a relay guesses
18480 its IP address incorrectly (e.g. due to unexpected lines in
18481 /etc/hosts). Resolves ticket 2267.
18482 - Track how many "TAP" and "NTor" circuit handshake requests we get,
18483 and how many we complete, and log it every hour to help relay
18484 operators follow trends in network load. Addresses ticket 9658.
18486 o Minor features (log messages, diagnostics):
18487 - If we fail to free a microdescriptor because of bug 7164, log
18488 the filename and line number from which we tried to free it.
18489 - We compute the overhead from passing onionskins back and forth to
18490 cpuworkers, and report it when dumping statistics in response to
18491 SIGUSR1. Supports ticket 7291.
18492 - Add another diagnostic to the heartbeat message: track and log
18493 overhead that TLS is adding to the data we write. If this is
18494 high, we are sending too little data to SSL_write at a time.
18495 Diagnostic for bug 7707.
18496 - Log packaged cell fullness as part of the heartbeat message.
18497 Diagnosis to try to determine the extent of bug 7743.
18498 - Add more detail to a log message about relaxed timeouts, to help
18500 - When learning a fingerprint for a bridge, log its corresponding
18501 transport type. Implements ticket 7896.
18502 - Warn more aggressively when flushing microdescriptors to a
18503 microdescriptor cache fails, in an attempt to mitigate bug 8031,
18504 or at least make it more diagnosable.
18505 - Improve the log message when "Bug/attack: unexpected sendme cell
18506 from client" occurs, to help us track bug 8093.
18507 - Improve debugging output to help track down bug 8185 ("Bug:
18508 outgoing relay cell has n_chan==NULL. Dropping.")
18510 o Minor features (log messages, quieter bootstrapping):
18511 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18512 versions and capabilities when everything is going right. Resolves
18513 part of ticket 6736.
18514 - Omit the first heartbeat log message, because it never has anything
18515 useful to say, and it clutters up the bootstrapping messages.
18516 Resolves ticket 6758.
18517 - Don't log about reloading the microdescriptor cache at startup. Our
18518 bootstrap warnings are supposed to tell the user when there's a
18519 problem, and our bootstrap notices say when there isn't. Resolves
18520 ticket 6759; bugfix on 0.2.2.6-alpha.
18521 - Don't log "I learned some more directory information" when we're
18522 reading cached directory information. Reserve it for when new
18523 directory information arrives in response to a fetch. Resolves
18525 - Don't complain about bootstrapping problems while hibernating.
18526 These complaints reflect a general code problem, but not one
18527 with any problematic effects (no connections are actually
18528 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
18530 o Minor features (testing):
18531 - In our testsuite, create temporary directories with a bit more
18532 entropy in their name to make name collisions less likely. Fixes
18534 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
18535 (P-256) Diffie-Hellman handshakes to src/or/bench.
18536 - Add benchmark functions to test onion handshake performance.
18539 - The DirServer option is now DirAuthority, for consistency with
18540 current naming patterns. You can still use the old DirServer form.
18542 o Minor bugfixes (protocol):
18543 - Fix the handling of a TRUNCATE cell when it arrives while the
18544 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
18545 - When a Tor client gets a "truncated" relay cell, the first byte of
18546 its payload specifies why the circuit was truncated. We were
18547 ignoring this 'reason' byte when tearing down the circuit, resulting
18548 in the controller not being told why the circuit closed. Now we
18549 pass the reason from the truncated cell to the controller. Bugfix
18550 on 0.1.2.3-alpha; fixes bug 7039.
18551 - Fix a misframing issue when reading the version numbers in a
18552 VERSIONS cell. Previously we would recognize [00 01 00 02] as
18553 'version 1, version 2, and version 0x100', when it should have
18554 only included versions 1 and 2. Fixes bug 8059; bugfix on
18555 0.2.0.10-alpha. Reported pseudonymously.
18556 - Make the format and order of STREAM events for DNS lookups
18557 consistent among the various ways to launch DNS lookups. Fixes
18558 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
18560 o Minor bugfixes (syscalls and disk interaction):
18561 - Always check the return values of functions fcntl() and
18562 setsockopt(). We don't believe these are ever actually failing in
18563 practice, but better safe than sorry. Also, checking these return
18564 values should please analysis tools like Coverity. Patch from
18565 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
18566 - Avoid double-closing the listener socket in our socketpair()
18567 replacement (used on Windows) in the case where the addresses on
18568 our opened sockets don't match what we expected. Fixes bug 9400;
18569 bugfix on 0.0.2pre7. Found by Coverity.
18570 - Correctly store microdescriptors and extrainfo descriptors that
18571 include an internal NUL byte. Fixes bug 8037; bugfix on
18572 0.2.0.1-alpha. Bug reported by "cypherpunks".
18573 - If for some reason we fail to write a microdescriptor while
18574 rebuilding the cache, do not let the annotations from that
18575 microdescriptor linger in the cache file, and do not let the
18576 microdescriptor stay recorded as present in its old location.
18577 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
18578 - Use direct writes rather than stdio when building microdescriptor
18579 caches, in an attempt to mitigate bug 8031, or at least make it
18582 o Minor fixes (config options):
18583 - Warn and fail if a server is configured not to advertise any
18584 ORPorts at all. (We need *something* to put in our descriptor,
18585 or we just won't work.)
18586 - Behave correctly when the user disables LearnCircuitBuildTimeout
18587 but doesn't tell us what they would like the timeout to be. Fixes
18588 bug 6304; bugfix on 0.2.2.14-alpha.
18589 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18590 to start with a triple-underscore so the controller won't touch it.
18591 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18592 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18593 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18594 - When autodetecting the number of CPUs, use the number of available
18595 CPUs in preference to the number of configured CPUs. Inform the
18596 user if this reduces the number of available CPUs. Fixes bug 8002;
18597 bugfix on 0.2.3.1-alpha.
18598 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
18599 - Make it an error when you set EntryNodes but disable UseGuardNodes,
18600 since it will (surprisingly to some users) ignore EntryNodes. Fixes
18601 bug 8180; bugfix on 0.2.3.11-alpha.
18602 - Avoid overflows when the user sets MaxCircuitDirtiness to a
18603 ridiculously high value, by imposing a (ridiculously high) 30-day
18604 maximum on MaxCircuitDirtiness.
18606 o Minor bugfixes (control protocol):
18607 - Stop sending a stray "(null)" in some cases for the server status
18608 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
18610 - The ADDRMAP command can no longer generate an ill-formed error
18611 code on a failed MAPADDRESS. It now says "internal" rather than
18612 an English sentence fragment with spaces in the middle. Bugfix on
18613 Tor 0.2.0.19-alpha.
18615 o Minor bugfixes (clients / edges):
18616 - When we receive a RELAY_END cell with the reason DONE, or with no
18617 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
18618 status as "connection refused". Previously we reported these cases
18619 as success but then immediately closed the connection. Fixes bug
18620 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
18621 - If the guard we choose first doesn't answer, we would try the
18622 second guard, but once we connected to the second guard we would
18623 abandon it and retry the first one, slowing down bootstrapping.
18624 The fix is to treat all our initially chosen guards as acceptable
18625 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
18626 - When choosing which stream on a formerly stalled circuit to wake
18627 first, make better use of the platform's weak RNG. Previously,
18628 we had been using the % ("modulo") operator to try to generate a
18629 1/N chance of picking each stream, but this behaves badly with
18630 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
18633 o Minor bugfixes (path bias detection):
18634 - If the state file's path bias counts are invalid (presumably from a
18635 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
18636 additional checks and log messages to the scaling of Path Bias
18637 counts, in case there still are remaining issues with scaling.
18638 Should help resolve bug 8235.
18639 - Prevent rounding error in path bias counts when scaling
18640 them down, and use the correct scale factor default. Also demote
18641 some path bias related log messages down a level and make others
18642 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
18643 - Remove a source of rounding error during path bias count scaling;
18644 don't count cannibalized circuits as used for path bias until we
18645 actually try to use them; and fix a circuit_package_relay_cell()
18646 warning message about n_chan==NULL. Fixes bug 7802.
18647 - Paste the description for PathBias parameters from the man
18648 page into or.h, so the code documents them too. Fixes bug 7982;
18649 bugfix on 0.2.3.17-beta.
18651 o Minor bugfixes (relays):
18652 - Stop trying to resolve our hostname so often (e.g. every time we
18653 think about doing a directory fetch). Now we reuse the cached
18654 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
18655 and 2410 (bugfix on 0.1.2.2-alpha).
18656 - When examining the list of network interfaces to find our address,
18657 do not consider non-running or disabled network interfaces. Fixes
18658 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
18660 o Minor bugfixes (blocking resistance):
18661 - Only disable TLS session ticket support when running as a TLS
18662 server. Now clients will blend better with regular Firefox
18663 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
18665 o Minor bugfixes (IPv6):
18666 - Use square brackets around IPv6 addresses in numerous places
18667 that needed them, including log messages, HTTPS CONNECT proxy
18668 requests, TransportProxy statefile entries, and pluggable transport
18669 extra-info lines. Fixes bug 7011; patch by David Fifield.
18671 o Minor bugfixes (directory authorities):
18672 - Reject consensus votes with more than 64 known-flags. We aren't even
18673 close to that limit yet, and our code doesn't handle it correctly.
18674 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
18675 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
18676 bugfix on 0.2.0.3-alpha.
18678 o Minor bugfixes (memory leaks):
18679 - Avoid leaking memory if we fail to compute a consensus signature
18680 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
18681 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
18682 on 0.2.1.1-alpha; fixes bug 7816.
18683 - Fix a memory leak during safe-cookie controller authentication.
18684 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
18685 - Free some more still-in-use memory at exit, to make hunting for
18686 memory leaks easier. Resolves bug 7029.
18688 o Minor bugfixes (code correctness):
18689 - Increase the width of the field used to remember a connection's
18690 link protocol version to two bytes. Harmless for now, since the
18691 only currently recognized versions are one byte long. Reported
18692 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
18693 - Fix a crash when debugging unit tests on Windows: deallocate a
18694 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
18695 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
18696 - When detecting the largest possible file descriptor (in order to
18697 close all file descriptors when launching a new program), actually
18698 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
18699 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
18701 - Avoid a crash if we fail to generate an extrainfo descriptor.
18702 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
18703 this is CID 718634.
18704 - Avoid an off-by-one error when checking buffer boundaries when
18705 formatting the exit status of a pluggable transport helper.
18706 This is probably not an exploitable bug, but better safe than
18707 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
18709 - Get rid of a couple of harmless clang warnings, where we compared
18710 enums to ints. These warnings are newly introduced in clang 3.2.
18712 o Minor bugfixes (code cleanliness):
18713 - Avoid use of reserved identifiers in our C code. The C standard
18714 doesn't like us declaring anything that starts with an
18715 underscore, so let's knock it off before we get in trouble. Fix
18716 for bug 1031; bugfix on the first Tor commit.
18717 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
18718 with large values. This situation was untriggered, but nevertheless
18719 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
18720 - Fix an impossible buffer overrun in the AES unit tests. Fixes
18721 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
18722 - Fix handling of rendezvous client authorization types over 8.
18723 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
18724 - Remove a couple of extraneous semicolons that were upsetting the
18725 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
18726 bugfix on 0.2.2.1-alpha.
18727 - When complaining about a client port on a public address, log
18728 which address we're complaining about. Fixes bug 4020; bugfix on
18729 0.2.3.3-alpha. Patch by Tom Fitzhenry.
18731 o Minor bugfixes (log messages, warnings):
18732 - If we encounter a write failure on a SOCKS connection before we
18733 finish our SOCKS handshake, don't warn that we closed the
18734 connection before we could send a SOCKS reply. Fixes bug 8427;
18735 bugfix on 0.1.0.1-rc.
18736 - Fix a directory authority warn caused when we have a large amount
18737 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
18738 - Downgrade "Failed to hand off onionskin" messages to "debug"
18739 severity, since they're typically redundant with the "Your computer
18740 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
18741 - Avoid spurious warnings when configuring multiple client ports of
18742 which only some are nonlocal. Previously, we had claimed that some
18743 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
18746 o Minor bugfixes (log messages, other):
18747 - Fix log messages and comments to avoid saying "GMT" when we mean
18748 "UTC". Fixes bug 6113.
18749 - When rejecting a configuration because we were unable to parse a
18750 quoted string, log an actual error message. Fixes bug 7950; bugfix
18752 - Correctly recognize that [::1] is a loopback address. Fixes
18753 bug 8377; bugfix on 0.2.1.3-alpha.
18754 - Don't log inappropriate heartbeat messages when hibernating: a
18755 hibernating node is _expected_ to drop out of the consensus,
18756 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
18757 bugfix on 0.2.3.1-alpha.
18758 - Eliminate several instances where we use "Nickname=ID" to refer to
18759 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
18760 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
18763 o Minor bugfixes (build):
18764 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
18765 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
18766 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
18768 o Documentation fixes:
18769 - Make the torify manpage no longer refer to tsocks; torify hasn't
18770 supported tsocks since 0.2.3.14-alpha.
18771 - Make the tor manpage no longer reference tsocks.
18772 - Fix the GeoIPExcludeUnknown documentation to refer to
18773 ExcludeExitNodes rather than the currently nonexistent
18774 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
18775 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18777 - Say "KBytes" rather than "KB" in the man page (for various values
18778 of K), to further reduce confusion about whether Tor counts in
18779 units of memory or fractions of units of memory. Resolves ticket 7054.
18780 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
18781 names match. Fixes bug 7768.
18782 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
18783 message is logged at notice, not at info.
18784 - Clarify the usage and risks of setting the ContactInfo torrc line
18785 for your relay or bridge. Resolves ticket 9854.
18786 - Add anchors to the manpage so we can link to the html version of
18787 the documentation for specific options. Resolves ticket 9866.
18788 - Replace remaining references to DirServer in man page and
18789 log entries. Resolves ticket 10124.
18791 o Removed features:
18792 - Stop exporting estimates of v2 and v3 directory traffic shares
18793 in extrainfo documents. They were unneeded and sometimes inaccurate.
18794 Also stop exporting any v2 directory request statistics. Resolves
18796 - Drop support for detecting and warning about versions of Libevent
18797 before 1.3e. Nothing reasonable ships with them any longer; warning
18798 the user about them shouldn't be needed. Resolves ticket 6826.
18799 - Now that all versions before 0.2.2.x are disallowed, we no longer
18800 need to work around their missing features. Remove a bunch of
18801 compatibility code.
18804 - The tor-tsocks.conf is no longer distributed or installed. We
18805 recommend that tsocks users use torsocks instead. Resolves
18807 - Remove some of the older contents of doc/ as obsolete; move others
18808 to torspec.git. Fixes bug 8965.
18810 o Code simplification:
18811 - Avoid using character buffers when constructing most directory
18812 objects: this approach was unwieldy and error-prone. Instead,
18813 build smartlists of strings, and concatenate them when done.
18814 - Rename "isin" functions to "contains", for grammar. Resolves
18816 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
18817 with the natural logarithm function from the system libm. Resolves
18819 - Start using OpenBSD's implementation of queue.h, so that we don't
18820 need to hand-roll our own pointer and list structures whenever we
18821 need them. (We can't rely on a sys/queue.h, since some operating
18822 systems don't have them, and the ones that do have them don't all
18823 present the same extensions.)
18824 - Start using OpenBSD's implementation of queue.h (originally by
18826 - Enhance our internal sscanf replacement so that we can eliminate
18827 the last remaining uses of the system sscanf. (Though those uses
18828 of sscanf were safe, sscanf itself is generally error prone, so
18829 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18831 - Replace all calls to snprintf() outside of src/ext with
18832 tor_snprintf(). Also remove the #define to replace snprintf with
18833 _snprintf on Windows; they have different semantics, and all of
18834 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
18837 - Add a wrapper function for the common "log a message with a
18839 - Split the onion.c file into separate modules for the onion queue
18840 and the different handshakes it supports.
18841 - Move the client-side address-map/virtual-address/DNS-cache code
18842 out of connection_edge.c into a new addressmap.c module.
18843 - Move the entry node code from circuitbuild.c to its own file.
18844 - Move the circuit build timeout tracking code from circuitbuild.c
18846 - Source files taken from other packages now reside in src/ext;
18847 previously they were scattered around the rest of Tor.
18848 - Move the generic "config" code into a new file, and have "config.c"
18849 hold only torrc- and state-related code. Resolves ticket 6823.
18850 - Move the core of our "choose a weighted element at random" logic
18851 into its own function, and give it unit tests. Now the logic is
18852 testable, and a little less fragile too.
18853 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18854 - Move last_reachable and testing_since from routerinfo_t to node_t.
18855 Implements ticket 5529.
18856 - Add replaycache_t structure, functions and unit tests, then refactor
18857 rend_service_introduce() to be more clear to read, improve, debug,
18858 and test. Resolves bug 6177.
18861 - Remove some now-needless code that tried to aggressively flush
18862 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18863 cell queue logic has saved us from the failure mode that this code
18864 was supposed to prevent. Removing this code will limit the number
18865 of baroque control flow paths through Tor's network logic. Reported
18866 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18867 - Remove unused code for parsing v1 directories and "running routers"
18868 documents. Fixes bug 6887.
18869 - Remove the marshalling/unmarshalling code for sending requests to
18870 cpuworkers over a socket, and instead just send structs. The
18871 recipient will always be the same Tor binary as the sender, so
18872 any encoding is overkill.
18873 - Remove the testing_since field of node_t, which hasn't been used
18874 for anything since 0.2.0.9-alpha.
18875 - Finally remove support for malloc_good_size and malloc_usable_size.
18876 We had hoped that these functions would let us eke a little more
18877 memory out of our malloc implementation. Unfortunately, the only
18878 implementations that provided these functions are also ones that
18879 are already efficient about not overallocation: they never got us
18880 more than 7 or so bytes per allocation. Removing them saves us a
18881 little code complexity and a nontrivial amount of build complexity.
18884 Changes in version 0.2.3.25 - 2012-11-19
18885 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
18886 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
18887 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
18888 programmer, and friend. Unstinting in his dedication to the cause of
18889 freedom, he inspired and helped many of us as we began our work on
18890 anonymity, and inspires us still. Please honor his memory by writing
18891 software to protect people's freedoms, and by helping others to do so.
18893 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
18894 significantly reduced directory overhead (via microdescriptors),
18895 enormous crypto performance improvements for fast relays on new
18896 enough hardware, a new v3 TLS handshake protocol that can better
18897 resist fingerprinting, support for protocol obfuscation plugins (aka
18898 pluggable transports), better scalability for hidden services, IPv6
18899 support for bridges, performance improvements like allowing clients
18900 to skip the first round-trip on the circuit ("optimistic data") and
18901 refilling token buckets more often, a new "stream isolation" design
18902 to isolate different applications on different circuits, and many
18903 stability, security, and privacy fixes.
18905 Major features (v3 directory protocol):
18906 - Clients now use microdescriptors instead of regular descriptors
18907 to build circuits. Microdescriptors are authority-generated
18908 summaries of regular descriptors' contents, designed to change very
18909 rarely (see proposal 158 for details). This feature is designed
18910 to save bandwidth, especially for clients on slow internet
18911 connections. Use "UseMicrodescriptors 0" to disable it.
18912 - Caches now download, cache, and serve microdescriptors, as well
18913 as multiple "flavors" of the consensus, including a flavor that
18914 describes microdescriptors.
18916 o Major features (build hardening):
18917 - Enable gcc and ld hardening by default. Resolves ticket 5210.
18919 o Major features (relay scaling):
18920 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
18921 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
18922 vectorized AES implementations as appropriate. These can be much,
18923 much faster than other AES implementations.
18924 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
18925 implementation. It makes AES_CTR about 7% faster than our old one
18926 (which was about 10% faster than the one OpenSSL used to provide).
18927 Resolves ticket 4526.
18928 - Use OpenSSL's EVP interface for AES encryption, so that all AES
18929 operations can use hardware acceleration (if present). Resolves
18931 - Unconditionally use OpenSSL's AES implementation instead of our
18932 old built-in one. OpenSSL's AES has been better for a while, and
18933 relatively few servers should still be on any version of OpenSSL
18934 that doesn't have good optimized assembly AES.
18936 o Major features (blocking resistance):
18937 - Update TLS cipher list to match Firefox 8 and later. Resolves
18939 - Remove support for clients falsely claiming to support standard
18940 ciphersuites that they can actually provide. As of modern OpenSSL
18941 versions, it's not necessary to fake any standard ciphersuite,
18942 and doing so prevents us from using better ciphersuites in the
18943 future, since servers can't know whether an advertised ciphersuite
18944 is really supported or not. Some hosts -- notably, ones with very
18945 old versions of OpenSSL or where OpenSSL has been built with ECC
18946 disabled -- will stand out because of this change; TBB users should
18947 not be affected. Implements the client side of proposal 198.
18948 - Implement a new handshake protocol (v3) for authenticating Tors to
18949 each other over TLS. It should be more resistant to fingerprinting
18950 than previous protocols, and should require less TLS hacking for
18951 future Tor implementations. Implements proposal 176.
18952 - Allow variable-length padding cells, to disguise the length of
18953 Tor's TLS records. Implements part of proposal 184.
18954 - While we're trying to bootstrap, record how many TLS connections
18955 fail in each state, and report which states saw the most failures
18956 in response to any bootstrap failures. This feature may speed up
18957 diagnosis of censorship events. Implements ticket 3116.
18959 o Major features (pluggable transports):
18960 - Clients and bridges can now be configured to use a separate
18961 "transport" proxy. This approach makes the censorship arms race
18962 easier by allowing bridges to use protocol obfuscation plugins.
18963 Implements proposal 180 (tickets 2841 and 3472).
18965 o Major features (DoS resistance):
18966 - Now that Tor 0.2.0.x is completely deprecated, enable the final
18967 part of "Proposal 110: Avoiding infinite length circuits" by
18968 refusing all circuit-extend requests that do not use a relay_early
18969 cell. This change helps Tor resist a class of denial-of-service
18970 attacks by limiting the maximum circuit length.
18971 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18972 could use this trick to make their circuits receive cells faster
18973 than our flow control would have allowed, or to gum up the network,
18974 or possibly to do targeted memory denial-of-service attacks on
18975 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18976 from July 2002, before the release of Tor 0.0.0.
18978 o Major features (hidden services):
18979 - Adjust the number of introduction points that a hidden service
18980 will try to maintain based on how long its introduction points
18981 remain in use and how many introductions they handle. Fixes
18983 - Add a "tor2web mode" for clients that want to connect to hidden
18984 services non-anonymously (and possibly more quickly). As a safety
18985 measure to try to keep users from turning this on without knowing
18986 what they are doing, tor2web mode must be explicitly enabled at
18987 compile time, and a copy of Tor compiled to run in tor2web mode
18988 cannot be used as a normal Tor client. Implements feature 2553.
18990 o Major features (IPv6):
18991 - Clients can now connect to private bridges over IPv6. Bridges
18992 still need at least one IPv4 address in order to connect to
18993 other relays. Note that we don't yet handle the case where the
18994 user has two bridge lines for the same bridge (one IPv4, one
18995 IPv6). Implements parts of proposal 186.
18997 o Major features (directory authorities):
18998 - Use a more secure consensus parameter voting algorithm. Now at
18999 least three directory authorities or a majority of them must
19000 vote on a given parameter before it will be included in the
19001 consensus. Implements proposal 178.
19002 - Remove the artificially low cutoff of 20KB to guarantee the Fast
19003 flag. In the past few years the average relay speed has picked
19004 up, and while the "top 7/8 of the network get the Fast flag" and
19005 "all relays with 20KB or more of capacity get the Fast flag" rules
19006 used to have the same result, now the top 7/8 of the network has
19007 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
19009 o Major features (performance):
19010 - Exit nodes now accept and queue data on not-yet-connected streams.
19011 Previously, the client wasn't allowed to send data until the
19012 stream was connected, which slowed down all connections. This
19013 change will enable clients to perform a "fast-start" on streams
19014 and send data without having to wait for a confirmation that the
19015 stream has opened. Patch from Ian Goldberg; implements the server
19016 side of Proposal 174.
19017 - When using an exit relay running 0.2.3.x, clients can now
19018 "optimistically" send data before the exit relay reports that
19019 the stream has opened. This saves a round trip when starting
19020 connections where the client speaks first (such as web browsing).
19021 This behavior is controlled by a consensus parameter (currently
19022 disabled). To turn it on or off manually, use the "OptimisticData"
19023 torrc option. Implements proposal 181; code by Ian Goldberg.
19024 - Add a new TokenBucketRefillInterval option to refill token buckets
19025 more frequently than once per second. This should improve network
19026 performance, alleviate queueing problems, and make traffic less
19027 bursty. Implements proposal 183; closes ticket 3630. Design by
19028 Florian Tschorsch and Björn Scheuermann; implementation by
19030 - Raise the threshold of server descriptors needed (75%) and exit
19031 server descriptors needed (50%) before we will declare ourselves
19032 bootstrapped. This will make clients start building circuits a
19033 little later, but makes the initially constructed circuits less
19034 skewed and less in conflict with further directory fetches. Fixes
19037 o Major features (relays):
19038 - Relays now try regenerating and uploading their descriptor more
19039 frequently if they are not listed in the consensus, or if the
19040 version of their descriptor listed in the consensus is too
19041 old. This fix should prevent situations where a server declines
19042 to re-publish itself because it has done so too recently, even
19043 though the authorities decided not to list its recent-enough
19044 descriptor. Fix for bug 3327.
19046 o Major features (stream isolation):
19047 - You can now configure Tor so that streams from different
19048 applications are isolated on different circuits, to prevent an
19049 attacker who sees your streams as they leave an exit node from
19050 linking your sessions to one another. To do this, choose some way
19051 to distinguish the applications: have them connect to different
19052 SocksPorts, or have one of them use SOCKS4 while the other uses
19053 SOCKS5, or have them pass different authentication strings to the
19054 SOCKS proxy. Then, use the new SocksPort syntax to configure the
19055 degree of isolation you need. This implements Proposal 171.
19056 - There's a new syntax for specifying multiple client ports (such as
19057 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
19058 multiple *Port entries with full addr:port syntax on each.
19059 The old *ListenAddress format is still supported, but you can't
19060 mix it with the new *Port syntax.
19062 o Major features (bufferevents):
19063 - Tor can now optionally build with the "bufferevents" buffered IO
19064 backend provided by Libevent 2. To use this feature, make sure you
19065 have the latest possible version of Libevent, and pass the
19066 --enable-bufferevents flag to configure when building Tor from
19067 source. This feature will make our networking code more flexible,
19068 let us stack layers on each other, and let us use more efficient
19069 zero-copy transports where available.
19070 - Add experimental support for running on Windows with IOCP and no
19071 kernel-space socket buffers. This feature is controlled by a new
19072 "UserspaceIOCPBuffers" config option (off by default), which has
19073 no effect unless Tor has been built with bufferevents enabled,
19074 you're running on Windows, and you've set "DisableIOCP 0". In the
19075 long run, this may help solve or mitigate bug 98.
19077 o Major features (path selection):
19078 - The EntryNodes option can now include country codes like {de} or IP
19079 addresses or network masks. Previously we had disallowed these
19080 options because we didn't have an efficient way to keep the list up
19081 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
19084 o Major features (port forwarding):
19085 - Add support for automatic port mapping on the many home routers
19086 that support NAT-PMP or UPnP. To build the support code, you'll
19087 need to have the libnatpnp library and/or the libminiupnpc library,
19088 and you'll need to enable the feature specifically by passing
19089 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
19090 it on, use the new PortForwarding option.
19092 o Major features (logging):
19093 - Add a new 'Heartbeat' log message type to periodically log a message
19094 describing Tor's status at level Notice. This feature is meant for
19095 operators who log at notice, and want to make sure that their Tor
19096 server is still working. Implementation by George Kadianakis.
19097 - Make logging resolution configurable with a new LogTimeGranularity
19098 option, and change the default from 1 millisecond to 1 second.
19099 Implements enhancement 1668.
19101 o Major features (other):
19102 - New "DisableNetwork" config option to prevent Tor from launching any
19103 connections or accepting any connections except on a control port.
19104 Bundles and controllers can set this option before letting Tor talk
19105 to the rest of the network, for example to prevent any connections
19106 to a non-bridge address. Packages like Orbot can also use this
19107 option to instruct Tor to save power when the network is off.
19108 - Try to use system facilities for enumerating local interface
19109 addresses, before falling back to our old approach (which was
19110 binding a UDP socket, and calling getsockname() on it). That
19111 approach was scaring OS X users whose draconian firewall
19112 software warned about binding to UDP sockets regardless of
19113 whether packets were sent. Now we try to use getifaddrs(),
19114 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
19115 system supports. Resolves ticket 1827.
19116 - Add experimental support for a "defaults" torrc file to be parsed
19117 before the regular torrc. Torrc options override the defaults file's
19118 options in the same way that the command line overrides the torrc.
19119 The SAVECONF controller command saves only those options which
19120 differ between the current configuration and the defaults file. HUP
19121 reloads both files. Implements task 4552.
19123 o New directory authorities:
19124 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
19125 authority. Closes ticket 5749.
19127 o Security/privacy fixes:
19128 - Avoid read-from-freed-memory and double-free bugs that could occur
19129 when a DNS request fails while launching it. Fixes bug 6480;
19130 bugfix on 0.2.0.1-alpha.
19131 - Reject any attempt to extend to an internal address. Without
19132 this fix, a router could be used to probe addresses on an internal
19133 network to see whether they were accepting connections. Fixes bug
19134 6710; bugfix on 0.0.8pre1.
19135 - Close any connection that sends unrecognized junk before the TLS
19136 handshake. Solves an issue noted in bug 4369.
19137 - The advertised platform of a relay now includes only its operating
19138 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
19139 its service pack level (for Windows) or its CPU architecture
19140 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
19141 can insert an extra string in the platform line by setting the
19142 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
19143 - Disable TLS session tickets. OpenSSL's implementation was giving
19144 our TLS session keys the lifetime of our TLS context objects, when
19145 perfect forward secrecy would want us to discard anything that
19146 could decrypt a link connection as soon as the link connection
19147 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
19148 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
19149 - Tor tries to wipe potentially sensitive data after using it, so
19150 that if some subsequent security failure exposes Tor's memory,
19151 the damage will be limited. But we had a bug where the compiler
19152 was eliminating these wipe operations when it decided that the
19153 memory was no longer visible to a (correctly running) program,
19154 hence defeating our attempt at defense in depth. We fix that
19155 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
19156 is unlikely to optimize away. Future versions of Tor may use
19157 a less ridiculously heavy approach for this. Fixes bug 7352.
19158 Reported in an article by Andrey Karpov.
19160 o Major bugfixes (crashes and asserts):
19161 - Avoid a pair of double-free and use-after-mark bugs that can
19162 occur with certain timings in canceled and re-received DNS
19163 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
19164 - Fix a denial of service attack by which any directory authority
19165 could crash all the others, or by which a single v2 directory
19166 authority could crash everybody downloading v2 directory
19167 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
19168 - Fix an assert that directory authorities could trigger on sighup
19169 during some configuration state transitions. We now don't treat
19170 it as a fatal error when the new descriptor we just generated in
19171 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19172 - Avoid segfault when starting up having run with an extremely old
19173 version of Tor and parsing its state file. Fixes bug 6801; bugfix
19176 o Major bugfixes (clients):
19177 - If we are unable to find any exit that supports our predicted ports,
19178 stop calling them predicted, so that we don't loop and build
19179 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19180 which introduced predicted ports.
19181 - Check at each new consensus whether our entry guards were picked
19182 long enough ago that we should rotate them. Previously, we only
19183 did this check at startup, which could lead to us holding a guard
19184 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19185 - When fetching a bridge descriptor from a bridge authority,
19186 always do so anonymously, whether we have been able to open
19187 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19188 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19189 but we'll need to wait for bug 6010 before it's actually usable.
19191 o Major bugfixes (directory voting):
19192 - Check more thoroughly to prevent a rogue authority from
19193 double-voting on any consensus directory parameter. Previously,
19194 authorities would crash in this case if the total number of
19195 votes for any parameter exceeded the number of active voters,
19196 but would let it pass otherwise. Partially fixes bug 5786; bugfix
19198 - When computing weight parameters, behave more robustly in the
19199 presence of a bad bwweightscale value. Previously, the authorities
19200 would crash if they agreed on a sufficiently broken weight_scale
19201 value; now, they use a reasonable default and carry on. Fixes the
19202 rest of bug 5786; bugfix on 0.2.2.17-alpha.
19203 - If authorities are unable to get a v2 consensus document from other
19204 directory authorities, they no longer fall back to fetching
19205 them from regular directory caches. Fixes bug 5635; bugfix on
19206 0.2.2.26-beta, where routers stopped downloading v2 consensus
19207 documents entirely.
19209 o Major bugfixes (relays):
19210 - Fix a bug handling SENDME cells on nonexistent streams that could
19211 result in bizarre window values. Report and patch contributed
19212 pseudonymously. Fixes part of bug 6271. This bug was introduced
19213 before the first Tor release, in svn commit r152.
19214 - Don't update the AccountingSoftLimitHitAt state file entry whenever
19215 tor gets started. This prevents a wrong average bandwidth
19216 estimate, which would cause relays to always start a new accounting
19217 interval at the earliest possible moment. Fixes bug 2003; bugfix
19218 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
19219 immensely in tracking this bug down.
19220 - Fix a possible crash bug when checking for deactivated circuits
19221 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
19222 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
19223 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19224 connections. This change should allow busy exit relays to stop
19225 running out of available sockets as quickly. Fixes bug 4950;
19226 bugfix on 0.2.2.26-beta.
19228 o Major bugfixes (blocking resistance):
19229 - Bridges no longer include their address in NETINFO cells on outgoing
19230 OR connections, to allow them to blend in better with clients.
19231 Removes another avenue for enumerating bridges. Reported by
19232 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
19233 cells were introduced.
19234 - Warn the user when HTTPProxy, but no other proxy type, is
19235 configured. This can cause surprising behavior: it doesn't send
19236 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
19237 directory traffic only. Resolves ticket 4663.
19239 o Major bugfixes (hidden services):
19240 - Improve hidden service robustness: when an attempt to connect to
19241 a hidden service ends, be willing to refetch its hidden service
19242 descriptors from each of the HSDir relays responsible for them
19243 immediately. Previously, we would not consider refetching the
19244 service's descriptors from each HSDir for 15 minutes after the last
19245 fetch, which was inconvenient if the hidden service was not running
19246 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
19247 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
19248 They used to check that the timestamp was within 30 minutes
19249 of their system clock, so they could cap the size of their
19250 replay-detection cache, but that approach unnecessarily refused
19251 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
19252 the v3 intro-point protocol (the first one which sent a timestamp
19253 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
19254 - When one of a hidden service's introduction points appears to be
19255 unreachable, stop trying it. Previously, we would keep trying
19256 to build circuits to the introduction point until we lost the
19257 descriptor, usually because the user gave up and restarted Tor.
19258 Fixes part of bug 3825.
19260 o Changes to default torrc file:
19261 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19262 port on 9050 by default anyway, so this should not change anything
19264 - Stop mentioning the deprecated *ListenAddress options in
19265 torrc.sample. Fixes bug 5438.
19266 - Document unit of bandwidth-related options in sample torrc.
19268 - Fix broken URLs in the sample torrc file, and tell readers about
19269 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19270 PublishServerDescriptor options. Addresses bug 4652.
19272 o Minor features (directory authorities):
19273 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
19274 change when the authority is deciding whether to accept a newly
19275 uploaded descriptor. Implements ticket 6423.
19276 - Directory authorities are now a little more lenient at accepting
19277 older router descriptors, or newer router descriptors that don't
19278 make big changes. This should help ameliorate past and future
19279 issues where routers think they have uploaded valid descriptors,
19280 but the authorities don't think so. Fix for ticket 2479.
19281 - Authority operators can now vote for all relays in a given
19282 set of countries to be BadDir/BadExit/Invalid/Rejected.
19283 - Provide two consensus parameters (FastFlagMinThreshold and
19284 FastFlagMaxThreshold) to control the range of allowable bandwidths
19285 for the Fast directory flag. These allow authorities to run
19286 experiments on appropriate requirements for being a "Fast" node.
19287 The AuthDirFastGuarantee config value still applies. Implements
19290 o Minor features (bridges / bridge authorities):
19291 - Make bridge SSL certificates a bit more stealthy by using random
19292 serial numbers, in the same fashion as OpenSSL when generating
19293 self-signed certificates. Implements ticket 4584.
19294 - Tag a bridge's descriptor as "never to be sent unencrypted".
19295 This shouldn't matter, since bridges don't open non-anonymous
19296 connections to the bridge authority and don't allow unencrypted
19297 directory connections from clients, but we might as well make
19298 sure. Closes bug 5139.
19299 - The Bridge Authority now writes statistics on how many bridge
19300 descriptors it gave out in total, and how many unique descriptors
19301 it gave out. It also lists how often the most and least commonly
19302 fetched descriptors were given out, as well as the median and
19303 25th/75th percentile. Implements tickets 4200 and 4294.
19305 o Minor features (IPv6):
19306 - Make the code that clients use to detect an address change be
19307 IPv6-aware, so that it won't fill clients' logs with error
19308 messages when trying to get the IPv4 address of an IPv6
19309 connection. Implements ticket 5537.
19310 - Relays now understand an IPv6 address when they get one from a
19311 directory server. Resolves ticket 4875.
19313 o Minor features (hidden services):
19314 - Expire old or over-used hidden service introduction points.
19315 Required by fix for bug 3460.
19316 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
19317 public key replay-detection cache from 60 minutes to 5 minutes. This
19318 replay-detection cache is now used only to detect multiple
19319 INTRODUCE2 cells specifying the same rendezvous point, so we can
19320 avoid launching multiple simultaneous attempts to connect to it.
19321 - When a hidden service's introduction point times out, consider
19322 trying it again during the next attempt to connect to the
19323 HS. Previously, we would not try it again unless a newly fetched
19324 descriptor contained it. Required by fixes for bugs 1297 and 3825.
19326 o Minor features (relays):
19327 - Relays now include a reason for regenerating their descriptors
19328 in an HTTP header when uploading to the authorities. This will
19329 make it easier to debug descriptor-upload issues in the future.
19330 - Turn on directory request statistics by default and include them in
19331 extra-info descriptors. Don't break if we have no GeoIP database.
19332 - Replace files in stats/ rather than appending to them. Now that we
19333 include statistics in extra-info descriptors, it makes no sense to
19334 keep old statistics forever. Implements ticket 2930.
19335 - Relays that set "ConnDirectionStatistics 1" write statistics on the
19336 bidirectional use of connections to disk every 24 hours.
19337 - Add a GeoIP file digest to the extra-info descriptor. Implements
19340 o Minor features (new config options):
19341 - New config option "DynamicDHGroups" (disabled by default) provides
19342 each bridge with a unique prime DH modulus to be used during
19343 SSL handshakes. This option attempts to help against censors
19344 who might use the Apache DH modulus as a static identifier for
19345 bridges. Addresses ticket 4548.
19346 - New config option "DisableDebuggerAttachment" (on by default)
19347 to prevent basic debugging attachment attempts by other processes.
19348 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
19349 - Ordinarily, Tor does not count traffic from private addresses (like
19350 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
19351 There is now a new option, CountPrivateBandwidth, to disable this
19352 behavior. Patch from Daniel Cagara.
19354 o Minor features (different behavior for old config options):
19355 - Allow MapAddress directives to specify matches against super-domains,
19356 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
19357 Implements issue 933.
19358 - Don't disable the DirPort when we cannot exceed our AccountingMax
19359 limit during this interval because the effective bandwidthrate is
19360 low enough. This is useful in a situation where AccountMax is only
19361 used as an additional safeguard or to provide statistics.
19362 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
19363 implements ticket 3439.
19364 - When configuring a large set of nodes in EntryNodes, and there are
19365 enough of them listed as Guard so that we don't need to consider
19366 the non-guard entries, prefer the ones listed with the Guard flag.
19367 - If you set the NumCPUs option to 0, Tor will now try to detect how
19368 many CPUs you have. This is the new default behavior.
19369 - The NodeFamily option -- which let you declare that you want to
19370 consider nodes to be part of a family whether they list themselves
19371 that way or not -- now allows IP address ranges and country codes.
19373 o Minor features (new command-line config behavior):
19374 - Slightly change behavior of "list" options (that is, config
19375 options that can appear more than once) when they appear both in
19376 torrc and on the command line. Previously, the command-line options
19377 would be appended to the ones from torrc. Now, the command-line
19378 options override the torrc options entirely. This new behavior
19379 allows the user to override list options (like exit policies and
19380 ports to listen on) from the command line, rather than simply
19381 appending to the list.
19382 - You can get the old (appending) command-line behavior for "list"
19383 options by prefixing the option name with a "+".
19384 - You can remove all the values for a "list" option from the command
19385 line without adding any new ones by prefixing the option name
19388 o Minor features (controller, new events):
19389 - Extend the control protocol to report flags that control a circuit's
19390 path selection in CIRC events and in replies to 'GETINFO
19391 circuit-status'. Implements part of ticket 2411.
19392 - Extend the control protocol to report the hidden service address
19393 and current state of a hidden-service-related circuit in CIRC
19394 events and in replies to 'GETINFO circuit-status'. Implements part
19396 - Include the creation time of a circuit in CIRC and CIRC2
19397 control-port events and the list produced by the 'GETINFO
19398 circuit-status' control-port command.
19399 - Add a new CONF_CHANGED event so that controllers can be notified
19400 of any configuration changes made by other controllers, or by the
19401 user. Implements ticket 1692.
19402 - Add a new SIGNAL event to the controller interface so that
19403 controllers can be notified when Tor handles a signal. Resolves
19404 issue 1955. Patch by John Brooks.
19406 o Minor features (controller, new getinfo options):
19407 - Expose our view of whether we have gone dormant to the controller,
19408 via a new "GETINFO dormant" value. Torbutton and other controllers
19409 can use this to avoid doing periodic requests through Tor while
19410 it's dormant (bug 4718). Resolves ticket 5954.
19411 - Add a new GETINFO option to get total bytes read and written. Patch
19412 from pipe, revised by atagar. Resolves ticket 2345.
19413 - Implement new GETINFO controller fields to provide information about
19414 the Tor process's pid, euid, username, and resource limits.
19416 o Minor features (controller, other):
19417 - Allow controllers to request an event notification whenever a
19418 circuit is cannibalized or its purpose is changed. Implements
19419 part of ticket 3457.
19420 - Use absolute path names when reporting the torrc filename in the
19421 control protocol, so a controller can more easily find the torrc
19422 file. Resolves bug 1101.
19423 - When reporting the path to the cookie file to the controller,
19424 give an absolute path. Resolves ticket 4881.
19426 o Minor features (log messages):
19427 - Add more information to a log statement that might help track down
19428 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19429 non-IP address" messages (or any Bug messages, for that matter!),
19430 please let us know about it.
19431 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19432 EntryNodes will have no effect. Resolves issue 2571.
19433 - Try to make the introductory warning message that Tor prints on
19434 startup more useful for actually finding help and information.
19435 Resolves ticket 2474.
19436 - When the system call to create a listener socket fails, log the
19437 error message explaining why. This may help diagnose bug 4027.
19439 o Minor features (other):
19440 - When we fail to initialize Libevent, retry with IOCP disabled so we
19441 don't need to turn on multi-threading support in Libevent, which in
19442 turn requires a working socketpair(). This is a workaround for bug
19443 4457, which affects Libevent versions from 2.0.1-alpha through
19445 - When starting as root and then changing our UID via the User
19446 control option, and we have a ControlSocket configured, make sure
19447 that the ControlSocket is owned by the same account that Tor will
19448 run under. Implements ticket 3421; fix by Jérémy Bobbio.
19449 - Accept attempts to include a password authenticator in the
19450 handshake, as supported by SOCKS5. This handles SOCKS clients that
19451 don't know how to omit a password when authenticating. Resolves
19453 - Check for and recover from inconsistency in the microdescriptor
19454 cache. This will make it harder for us to accidentally free a
19455 microdescriptor without removing it from the appropriate data
19456 structures. Fixes issue 3135; issue noted by "wanoskarnet".
19457 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19459 o Minor bugfixes (code security):
19460 - Prevent a null-pointer dereference when receiving a data cell
19461 for a nonexistent stream when the circuit in question has an
19462 empty deliver window. We don't believe this is triggerable,
19463 since we don't currently allow deliver windows to become empty,
19464 but the logic is tricky enough that it's better to make the code
19465 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19466 - Fix a (harmless) integer overflow in cell statistics reported by
19467 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
19468 - Fix our implementation of crypto_random_hostname() so it can't
19469 overflow on ridiculously large inputs. (No Tor version has ever
19470 provided this kind of bad inputs, but let's be correct in depth.)
19471 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
19472 - Add a (probably redundant) memory clear between iterations of
19473 the router status voting loop, to prevent future coding errors
19474 where data might leak between iterations of the loop. Resolves
19477 o Minor bugfixes (wrapper functions):
19478 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
19479 utility function used in the control-port code). This shouldn't
19480 ever happen unless Tor is completely out of memory, but if it did
19481 happen and Tor somehow recovered from it, Tor could have sent a log
19482 message to a control port in the middle of a reply to a controller
19483 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
19484 - Fix some (not actually triggerable) buffer size checks in usage of
19485 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
19487 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
19488 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
19489 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19490 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19491 - Make our replacement implementation of strtok_r() compatible with
19492 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19493 bugfix on 0.2.2.1-alpha.
19494 - Find more places in the code that should have been testing for
19495 invalid sockets using the SOCKET_OK macro. Required for a fix
19496 for bug 4533. Bugfix on 0.2.2.28-beta.
19498 o Minor bugfixes (code correctness):
19499 - Check return value of fputs() when writing authority certificate
19500 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
19501 - When building Tor on Windows with -DUNICODE (not default), ensure
19502 that error messages, filenames, and DNS server names are always
19503 NUL-terminated when we convert them to a single-byte encoding.
19504 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
19505 - Fix a memory leak when trying to launch a DNS request when the
19506 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
19508 - Correct file sizes when reading binary files on Cygwin, to avoid
19509 a bug where Tor would fail to read its state file. Fixes bug 6844;
19510 bugfix on 0.1.2.7-alpha.
19511 - Make sure to set *socket_error in all error cases in
19512 connection_connect(), so it can't produce a warning about
19513 errno being zero from errno_to_orconn_end_reason(). Bugfix on
19514 0.2.1.1-alpha; resolves ticket 6028.
19515 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
19516 bug 4532; found by "troll_un".
19518 o Minor bugfixes (clients):
19519 - Allow one-hop directory-fetching circuits the full "circuit build
19520 timeout" period, rather than just half of it, before failing them
19521 and marking the relay down. This fix should help reduce cases where
19522 clients declare relays (or worse, bridges) unreachable because
19523 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
19524 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
19526 - Ensure we don't cannibalize circuits that are longer than three hops
19527 already, so we don't end up making circuits with 5 or more
19528 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19529 0.1.0.1-rc which introduced cannibalization.
19531 o Minor bugfixes (relays):
19532 - Don't publish a new relay descriptor when we reload our onion key,
19533 unless the onion key has actually changed. Fixes bug 3263 and
19534 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
19535 - When relays refuse a "create" cell because their queue of pending
19536 create cells is too big (typically because their cpu can't keep up
19537 with the arrival rate), send back reason "resource limit" rather
19538 than reason "internal", so network measurement scripts can get a
19539 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
19540 - Exit nodes don't need to fetch certificates for authorities that
19541 they don't recognize; only directory authorities, bridges,
19542 and caches need to do that. Fixes part of bug 2297; bugfix on
19545 o Minor bugfixes (directory authority / mirrors):
19546 - Avoid O(n^2) performance characteristics when parsing a large
19547 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
19548 - Authorities no longer include any router in their microdescriptor
19549 consensuses for which they couldn't generate or agree on a
19550 microdescriptor. Fixes the second piece of bug 6404; fix on
19552 - When checking for requested signatures on the latest consensus
19553 before serving it to a client, make sure to check the right
19554 consensus flavor. Bugfix on 0.2.2.6-alpha.
19555 - Fix an edge case where TestingTorNetwork is set but the authorities
19556 and relays all have an uptime of zero, so the private Tor network
19557 could briefly lack support for hidden services. Fixes bug 3886;
19558 bugfix on 0.2.2.18-alpha.
19559 - Directory caches no longer refuse to clean out descriptors because
19560 of missing v2 networkstatus documents, unless they're configured
19561 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19562 0.2.2.26-beta. Patch by Daniel Bryg.
19563 - Don't serve or accept v2 hidden service descriptors over a relay's
19564 DirPort. It's never correct to do so, and disabling it might
19565 make it more annoying to exploit any bugs that turn up in the
19566 descriptor-parsing code. Fixes bug 7149.
19568 o Minor bugfixes (hidden services, client-side):
19569 - Assert that hidden-service-related operations are not performed
19570 using single-hop circuits. Previously, Tor would assert that
19571 client-side streams are not attached to single-hop circuits,
19572 but not that other sensitive operations on the client and service
19573 side are not performed using single-hop circuits. Fixes bug 3332;
19575 - Avoid undefined behavior when parsing the list of supported
19576 rendezvous/introduction protocols in a hidden service descriptor.
19577 Previously, Tor would have confused (as-yet-unused) protocol version
19578 numbers greater than 32 with lower ones on many platforms. Fixes
19579 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
19580 - Don't close hidden service client circuits which have almost
19581 finished connecting to their destination when they reach
19582 the normal circuit-build timeout. Previously, we would close
19583 introduction circuits which are waiting for an acknowledgement
19584 from the introduction point, and rendezvous circuits which have
19585 been specified in an INTRODUCE1 cell sent to a hidden service,
19586 after the normal CBT. Now, we mark them as 'timed out', and launch
19587 another rendezvous attempt in parallel. This behavior change can
19588 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
19589 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
19591 o Minor bugfixes (hidden services, service-side):
19592 - Don't close hidden-service-side rendezvous circuits when they
19593 reach the normal circuit-build timeout. This behavior change can
19594 be disabled using the new
19595 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
19596 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
19597 - Don't launch more than 10 service-side introduction-point circuits
19598 for a hidden service in five minutes. Previously, we would consider
19599 launching more introduction-point circuits if at least one second
19600 had passed without any introduction-point circuits failing. Fixes
19601 bug 4607; bugfix on 0.0.7pre1.
19603 o Minor bugfixes (config option behavior):
19604 - If the user tries to set MyFamily on a bridge, refuse to
19605 do so, and warn about the security implications. Fixes bug 4657;
19606 bugfix on 0.2.0.3-alpha.
19607 - The "--quiet" and "--hush" options now apply not only to Tor's
19608 behavior before logs are configured, but also to Tor's behavior in
19609 the absence of configured logs. Fixes bug 3550; bugfix on
19611 - Change the AllowDotExit rules so they should actually work.
19612 We now enforce AllowDotExit only immediately after receiving an
19613 address via SOCKS or DNSPort: other sources are free to provide
19614 .exit addresses after the resolution occurs. Fixes bug 3940;
19615 bugfix on 0.2.2.1-alpha.
19616 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
19617 don't depend on the consensus parameters or compute adaptive
19618 timeouts when it is disabled. Fixes bug 5049; bugfix on
19620 - After we pick a directory mirror, we would refuse to use it if
19621 it's in our ExcludeExitNodes list, resulting in mysterious failures
19622 to bootstrap for people who just wanted to avoid exiting from
19623 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
19624 - When told to add a bridge with the same digest as a preexisting
19625 bridge but a different addr:port, change the addr:port as
19626 requested. Previously we would not notice the change. Fixes half
19627 of bug 5603; fix on 0.2.2.26-beta.
19629 o Minor bugfixes (controller):
19630 - Allow manual 'authenticate' commands to the controller interface
19631 from netcat (nc) as well as telnet. We were rejecting them because
19632 they didn't come with the expected whitespace at the end of the
19633 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
19634 - Report a real bootstrap problem to the controller on router
19635 identity mismatch. Previously we just said "foo", which probably
19636 made a lot of sense at the time. Fixes bug 4169; bugfix on
19638 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
19639 option is set to 0 (which Vidalia version 0.2.16 now does when
19640 a SAVECONF attempt fails), perform other actions that SIGHUP
19641 usually causes (like reopening the logs). Fixes bug 5095; bugfix
19643 - Correctly handle checking the permissions on the parent
19644 directory of a control socket in the root directory. Bug found
19645 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
19647 - End AUTHCHALLENGE error messages (in the control protocol) with
19648 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
19650 o Minor bugfixes (network reading/writing):
19651 - Disable writing on marked-for-close connections when they are
19652 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
19653 bug 5263; bugfix on 0.0.2pre13, where we first added a special
19654 case for flushing marked connections.
19655 - Make sure that there are no unhandled pending TLS errors before
19656 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
19657 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
19658 Bugfix on 0.1.0.5-rc; fixes bug 4528.
19659 - Detect SSL handshake even when the initial attempt to write the
19660 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
19661 - If the client fails to set a reasonable set of ciphersuites
19662 during its v2 handshake renegotiation, allow the renegotiation to
19663 continue nevertheless (i.e. send all the required certificates).
19664 Fixes bug 4591; bugfix on 0.2.0.20-rc.
19666 o Minor bugfixes (other):
19667 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
19668 resource exhaustion, so that clients can adjust their load to
19669 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
19670 started using END_STREAM_REASON_RESOURCELIMIT.
19671 - Don't check for whether the address we're using for outbound
19672 connections has changed until after the outbound connection has
19673 completed. On Windows, getsockname() doesn't succeed until the
19674 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
19675 - Don't hold a Windows file handle open for every file mapping;
19676 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
19678 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
19679 bugfix on 0.2.1.10-alpha.
19680 - If we fail to write a microdescriptor to the disk cache, do not
19681 continue replacing the old microdescriptor file. Fixes bug 2954;
19682 bugfix on 0.2.2.6-alpha.
19684 o Minor bugfixes (log messages, path selection):
19685 - Downgrade "set buildtimeout to low value" messages to "info"
19686 severity; they were never an actual problem, there was never
19687 anything reasonable to do about them, and they tended to spam logs
19688 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
19689 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
19690 more information to it, so that we can track it down in case it
19691 returns again. Mitigates bug 5235.
19692 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
19693 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
19694 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
19695 - Issue a log message if a guard completes less than 40% of your
19696 circuits. Threshold is configurable by torrc option
19697 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
19698 additional, off-by-default code to disable guards which fail too
19699 many circuits. Addresses ticket 5458.
19701 o Minor bugfixes (log messages, client):
19702 - Downgrade "Got a certificate, but we already have it" log messages
19703 from warning to info, except when we're a dirauth. Fixes bug 5238;
19704 bugfix on 0.2.1.7-alpha.
19705 - Fix the log message describing how we work around discovering
19706 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
19707 4837; bugfix on 0.2.2.9-alpha.
19708 - When logging about a disallowed .exit name, do not also call it
19709 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
19710 - Fix a log message suggesting that people contact a non-existent
19711 email address. Fixes bug 3448.
19712 - Rephrase the log message emitted if the TestSocks check is
19713 successful. Patch from Fabian Keil; fixes bug 4094.
19714 - Log (at debug level) whenever a circuit's purpose is changed.
19715 - Log SSL state transitions at log level DEBUG, log domain
19716 HANDSHAKE. This can be useful for debugging censorship events.
19717 Implements ticket 3264.
19718 - We now log which torrc file we're using on startup. Implements
19720 - Rate-limit log messages when asked to connect anonymously to
19721 a private address. When these hit, they tended to hit fast and
19722 often. Also, don't bother trying to connect to addresses that we
19723 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
19724 reply makes us think we have been lied to, even when the address the
19725 client tried to connect to was "localhost." Resolves ticket 2822.
19727 o Minor bugfixes (log messages, non-client):
19728 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
19729 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
19730 - Don't log that we have "decided to publish new relay descriptor"
19731 unless we are actually publishing a descriptor. Fixes bug 3942;
19732 bugfix on 0.2.2.28-beta.
19733 - Log which authority we're missing votes from when we go to fetch
19734 them from the other auths.
19735 - Replace "Sending publish request" log messages with "Launching
19736 upload", so that they no longer confusingly imply that we're
19737 sending something to a directory we might not even be connected
19738 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
19739 - Warn when Tor is configured to use accounting in a way that can
19740 link a hidden service to some other hidden service or public
19741 address. Resolves ticket 6490.
19742 - Fix a minor formatting issue in one of tor-gencert's error messages.
19746 - Update to the latest version of the tinytest unit testing framework.
19747 This includes a couple of bugfixes that can be relevant for
19748 running forked unit tests on Windows, and removes all reserved
19750 - Avoid a false positive in the util/threads unit test by increasing
19751 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
19752 - Make it possible to set the TestingTorNetwork configuration
19753 option using AlternateDirAuthority and AlternateBridgeAuthority
19754 as an alternative to setting DirServer. Addresses ticket 6377.
19755 - Add a unit test for the environment_variable_names_equal() function.
19756 - A wide variety of new unit tests by Esteban Manchado Velázquez.
19757 - Numerous new unit tests for functions in util.c and address.c by
19759 - The long-disabled benchmark tests are now split into their own
19760 ./src/test/bench binary.
19761 - The benchmark tests can now use more accurate timers than
19762 gettimeofday() when such timers are available.
19763 - Use tt_assert(), not tor_assert(), for checking for test failures.
19764 This makes the unit tests more able to go on in the event that
19767 o Build improvements:
19768 - Use the dead_strip option when building Tor on OS X. This reduces
19769 binary size by almost 19% when linking openssl and libevent
19770 statically, which we do for Tor Browser Bundle.
19771 - Provide a better error message about possible OSX Asciidoc failure
19772 reasons. Fixes bug 6436.
19773 - Detect attempts to build Tor on (as yet hypothetical) versions
19774 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
19775 fix for bug 4533. Bugfix on 0.2.2.28-beta.
19776 - On Windows, we now define the _WIN32_WINNT macros only if they
19777 are not already defined. This lets the person building Tor decide,
19778 if they want, to require a later version of Windows.
19779 - Our autogen.sh script now uses autoreconf to launch autoconf,
19780 automake, and so on. This is more robust against some of the failure
19781 modes associated with running the autotools pieces on their own.
19782 - Running "make version" now displays the version of Tor that
19783 we're about to build. Idea from katmagic; resolves issue 4400.
19784 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
19785 on 0.2.2.4-alpha; fixes bug 3427.
19786 - New --enable-static-tor configure option for building Tor as
19787 statically as possible. Idea, general hackery and thoughts from
19788 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
19790 - Limited, experimental support for building with nmake and MSVC.
19792 o Build requirements:
19793 - Building Tor with bufferevent support now requires Libevent
19794 2.0.13-stable or later. Previous versions of Libevent had bugs in
19795 SSL-related bufferevents and related issues that would make Tor
19796 work badly with bufferevents. Requiring 2.0.13-stable also allows
19797 Tor with bufferevents to take advantage of Libevent APIs
19798 introduced after 2.0.8-rc.
19799 - Our build system requires automake 1.6 or later to create the
19800 Makefile.in files. Previously, you could have used 1.4.
19801 This only affects developers and people building Tor from git;
19802 people who build Tor from the source distribution without changing
19803 the Makefile.am files should be fine.
19804 - Detect when we try to build on a platform that doesn't define
19805 AF_UNSPEC to 0. We don't work there, so refuse to compile.
19807 o Build fixes (compile/link):
19808 - Format more doubles with %f, not %lf. Patch from grarpamp to make
19809 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
19811 - When building with --enable-static-tor on OpenBSD, do not
19812 erroneously attempt to link -lrt. Fixes bug 5103.
19813 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
19814 that IPv6 stuff will compile on MSVC, and compilation issues
19815 will be easier to track down. Fixes bug 5861.
19816 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
19817 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
19818 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
19819 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
19821 o Build fixes (other):
19822 - Use the _WIN32 macro throughout our code to detect Windows.
19823 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
19825 - Properly handle the case where the build-tree is not the same
19826 as the source tree when generating src/common/common_sha1.i,
19827 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
19828 bugfix on 0.2.0.1-alpha.
19829 - During configure, search for library containing cos function as
19830 libm lives in libcore on some platforms (BeOS/Haiku). Linking
19831 against libm was hard-coded before. Fixes the first part of bug
19832 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
19834 - Prevent a false positive from the check-spaces script, by disabling
19835 the "whitespace between function name and (" check for functions
19838 o Packaging (RPM) changes:
19839 - Update our default RPM spec files to work with mock and rpmbuild
19840 on RHEL/Fedora. They have an updated set of dependencies and
19841 conflicts, a fix for an ancient typo when creating the "_tor"
19842 user, and better instructions. Thanks to Ondrej Mikle for the
19843 patch series. Fixes bug 6043.
19844 - On OpenSUSE, create the /var/run/tor directory on startup if it
19845 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
19847 o Code refactoring (safety):
19848 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
19849 10 lines. Also, don't nest them. Doing so in the past has
19850 led to hard-to-debug code. The new style is to use the
19851 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
19852 - Use macros to indicate OpenSSL versions, so we don't need to worry
19853 about accidental hexadecimal bit shifts.
19854 - Use tor_sscanf() in place of scanf() in more places through the
19855 code. This makes us a little more locale-independent, and
19856 should help shut up code-analysis tools that can't tell
19857 a safe sscanf string from a dangerous one.
19858 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
19859 - Use the smartlist_add_asprintf() alias more consistently.
19861 o Code refactoring (consolidate):
19862 - A major revision to our internal node-selecting and listing logic.
19863 Tor already had at least two major ways to look at the question of
19864 "which Tor servers do we know about": a list of router descriptors,
19865 and a list of entries in the current consensus. With
19866 microdescriptors, we're adding a third. Having so many systems
19867 without an abstraction layer over them was hurting the codebase.
19868 Now, we have a new "node_t" abstraction that presents a consistent
19869 interface to a client's view of a Tor node, and holds (nearly) all
19870 of the mutable state formerly in routerinfo_t and routerstatus_t.
19871 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
19872 Libevent's notion of cached time when possible.
19873 - Remove duplicate code for invoking getrlimit() from control.c.
19874 - Use OpenSSL's built-in SSL_state_string_long() instead of our
19875 own homebrewed ssl_state_to_string() replacement. Patch from
19876 Emile Snyder. Fixes bug 4653.
19877 - Change the symmetric cipher interface so that creating and
19878 initializing a stream cipher are no longer separate functions.
19880 o Code refactoring (separate):
19881 - Make a new "entry connection" struct as an internal subtype of "edge
19882 connection", to simplify the code and make exit connections smaller.
19883 - Split connection_about_to_close() into separate functions for each
19885 - Rewrite the listener-selection logic so that parsing which ports
19886 we want to listen on is now separate from binding to the ports
19889 o Code refactoring (name changes):
19890 - Rename a handful of old identifiers, mostly related to crypto
19891 structures and crypto functions. By convention, our "create an
19892 object" functions are called "type_new()", our "free an object"
19893 functions are called "type_free()", and our types indicate that
19894 they are types only with a final "_t". But a handful of older
19895 types and functions broke these rules, with function names like
19896 "type_create" or "subsystem_op_type", or with type names like
19898 - Rename Tor functions that turn strings into addresses, so that
19899 "parse" indicates that no hostname resolution occurs, and
19900 "lookup" indicates that hostname resolution may occur. This
19901 should help prevent mistakes in the future. Fixes bug 3512.
19902 - Use the name "CERTS" consistently to refer to the new cell type;
19903 we were calling it CERT in some places and CERTS in others.
19904 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
19905 invalid value, rather than just -1.
19906 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
19907 can pick them up when the tests aren't disabled. Bugfix on
19908 0.2.2.4-alpha which introduced tinytest.
19910 o Code refactoring (other):
19911 - Defensively refactor rend_mid_rendezvous() so that protocol
19912 violations and length checks happen in the beginning. Fixes
19914 - Remove the pure attribute from all functions that used it
19915 previously. In many cases we assigned it incorrectly, because the
19916 functions might assert or call impure functions, and we don't have
19917 evidence that keeping the pure attribute is worthwhile. Implements
19918 changes suggested in ticket 4421.
19919 - Move the replay-detection cache for the RSA-encrypted parts of
19920 INTRODUCE2 cells to the introduction point data structures.
19921 Previously, we would use one replay-detection cache per hidden
19922 service. Required by fix for bug 3460.
19923 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
19924 no longer link against Libevent: they never used it, but
19925 our library structure used to force them to link it.
19927 o Removed features and files:
19928 - Remove all internal support for unpadded RSA. We never used it, and
19929 it would be a bad idea to start.
19930 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
19932 - Remove some redundant #include directives throughout the code.
19933 Patch from Andrea Gelmini.
19934 - Remove some old code to remember statistics about which descriptors
19935 we've served as a directory mirror. The feature wasn't used and
19936 is outdated now that microdescriptors are around.
19937 - Remove some old code to work around even older versions of Tor that
19938 used forked processes to handle DNS requests. Such versions of Tor
19939 are no longer in use as relays.
19940 - The "torify" script no longer supports the "tsocks" socksifier
19941 tool, since tsocks doesn't support DNS and UDP right for Tor.
19942 Everyone should be using torsocks instead. Fixes bugs 3530 and
19943 5180. Based on a patch by "ugh".
19944 - Remove the torrc.bridge file: we don't use it for anything, and
19945 it had become badly desynchronized from torrc.sample. Resolves
19949 - Begin a doc/state-contents.txt file to explain the contents of
19950 the Tor state file. Fixes bug 2987.
19951 - Clarify the documentation for the Alternate*Authority options.
19953 - Document the --defaults-torrc option, and the new semantics for
19954 overriding, extending, and clearing lists of options. Closes
19956 - Add missing man page documentation for consensus and microdesc
19957 files. Resolves ticket 6732.
19958 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
19960 o Documentation fixes:
19961 - Improve the manual's documentation for the NT Service command-line
19962 options. Addresses ticket 3964.
19963 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19964 - Document the changes to the ORPort and DirPort options, and the
19965 fact that {OR/Dir}ListenAddress is now unnecessary (and
19966 therefore deprecated). Resolves ticket 5597.
19967 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
19968 - Clarify that hidden services are TCP only. Fixes bug 6024.
19971 Changes in version 0.2.2.39 - 2012-09-11
19972 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
19976 - Fix an assertion failure in tor_timegm() that could be triggered
19977 by a badly formatted directory object. Bug found by fuzzing with
19978 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
19979 - Do not crash when comparing an address with port value 0 to an
19980 address policy. This bug could have been used to cause a remote
19981 assertion failure by or against directory authorities, or to
19982 allow some applications to crash clients. Fixes bug 6690; bugfix
19986 Changes in version 0.2.2.38 - 2012-08-12
19987 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
19988 attack that could in theory leak path information.
19991 - Avoid an uninitialized memory read when reading a vote or consensus
19992 document that has an unrecognized flavor name. This read could
19993 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
19994 - Try to leak less information about what relays a client is
19995 choosing to a side-channel attacker. Previously, a Tor client would
19996 stop iterating through the list of available relays as soon as it
19997 had chosen one, thus finishing a little earlier when it picked
19998 a router earlier in the list. If an attacker can recover this
19999 timing information (nontrivial but not proven to be impossible),
20000 they could learn some coarse-grained information about which relays
20001 a client was picking (middle nodes in particular are likelier to
20002 be affected than exits). The timing attack might be mitigated by
20003 other factors (see bug 6537 for some discussion), but it's best
20004 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
20007 Changes in version 0.2.2.37 - 2012-06-06
20008 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
20009 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
20013 - Work around a bug in OpenSSL that broke renegotiation with TLS
20014 1.1 and TLS 1.2. Without this workaround, all attempts to speak
20015 the v2 Tor connection protocol when both sides were using OpenSSL
20016 1.0.1 would fail. Resolves ticket 6033.
20017 - When waiting for a client to renegotiate, don't allow it to add
20018 any bytes to the input buffer. This fixes a potential DoS issue.
20019 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
20020 - Fix an edge case where if we fetch or publish a hidden service
20021 descriptor, we might build a 4-hop circuit and then use that circuit
20022 for exiting afterwards -- even if the new last hop doesn't obey our
20023 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
20026 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
20027 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
20030 - Tell GCC and Clang to check for any errors in format strings passed
20031 to the tor_v*(print|scan)f functions.
20034 Changes in version 0.2.2.36 - 2012-05-24
20035 Tor 0.2.2.36 updates the addresses for two of the eight directory
20036 authorities, fixes some potential anonymity and security issues,
20037 and fixes several crash bugs.
20039 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
20040 known flaws, and nobody should be using them. You should upgrade. If
20041 you're using a Linux or BSD and its packages are obsolete, stop using
20042 those packages and upgrade anyway.
20044 o Directory authority changes:
20045 - Change IP address for maatuska (v3 directory authority).
20046 - Change IP address for ides (v3 directory authority), and rename
20050 - When building or running with any version of OpenSSL earlier
20051 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
20052 versions have a bug (CVE-2011-4576) in which their block cipher
20053 padding includes uninitialized data, potentially leaking sensitive
20054 information to any peer with whom they make a SSLv3 connection. Tor
20055 does not use SSL v3 by default, but a hostile client or server
20056 could force an SSLv3 connection in order to gain information that
20057 they shouldn't have been able to get. The best solution here is to
20058 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
20059 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
20060 to make sure that the bug can't happen.
20061 - Never use a bridge or a controller-supplied node as an exit, even
20062 if its exit policy allows it. Found by wanoskarnet. Fixes bug
20063 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
20064 and 0.2.0.3-alpha (for bridge-purpose descriptors).
20065 - Only build circuits if we have a sufficient threshold of the total
20066 descriptors that are marked in the consensus with the "Exit"
20067 flag. This mitigates an attack proposed by wanoskarnet, in which
20068 all of a client's bridges collude to restrict the exit nodes that
20069 the client knows about. Fixes bug 5343.
20070 - Provide controllers with a safer way to implement the cookie
20071 authentication mechanism. With the old method, if another locally
20072 running program could convince a controller that it was the Tor
20073 process, then that program could trick the controller into telling
20074 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
20075 authentication method uses a challenge-response approach to prevent
20076 this attack. Fixes bug 5185; implements proposal 193.
20079 - Avoid logging uninitialized data when unable to decode a hidden
20080 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
20081 - Avoid a client-side assertion failure when receiving an INTRODUCE2
20082 cell on a general purpose circuit. Fixes bug 5644; bugfix on
20084 - Fix builds when the path to sed, openssl, or sha1sum contains
20085 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
20087 - Correct our replacements for the timeradd() and timersub() functions
20088 on platforms that lack them (for example, Windows). The timersub()
20089 function is used when expiring circuits, while timeradd() is
20090 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
20091 bugfix on 0.2.2.24-alpha.
20092 - Fix the SOCKET_OK test that we use to tell when socket
20093 creation fails so that it works on Win64. Fixes part of bug 4533;
20094 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
20097 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
20098 Fixes bug 5346; bugfix on 0.0.8pre3.
20099 - Make our number-parsing functions always treat too-large values
20100 as an error, even when those values exceed the width of the
20101 underlying type. Previously, if the caller provided these
20102 functions with minima or maxima set to the extreme values of the
20103 underlying integer type, these functions would return those
20104 values on overflow rather than treating overflow as an error.
20105 Fixes part of bug 5786; bugfix on 0.0.9.
20106 - Older Linux kernels erroneously respond to strange nmap behavior
20107 by having accept() return successfully with a zero-length
20108 socket. When this happens, just close the connection. Previously,
20109 we would try harder to learn the remote address: but there was
20110 no such remote address to learn, and our method for trying to
20111 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
20112 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
20113 - Correct parsing of certain date types in parse_http_time().
20114 Without this patch, If-Modified-Since would behave
20115 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
20116 Esteban Manchado Velázques.
20117 - Change the BridgePassword feature (part of the "bridge community"
20118 design, which is not yet implemented) to use a time-independent
20119 comparison. The old behavior might have allowed an adversary
20120 to use timing to guess the BridgePassword value. Fixes bug 5543;
20121 bugfix on 0.2.0.14-alpha.
20122 - Detect and reject certain misformed escape sequences in
20123 configuration values. Previously, these values would cause us
20124 to crash if received in a torrc file or over an authenticated
20125 control port. Bug found by Esteban Manchado Velázquez, and
20126 independently by Robert Connolly from Matta Consulting who further
20127 noted that it allows a post-authentication heap overflow. Patch
20128 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
20129 bugfix on 0.2.0.16-alpha.
20130 - Fix a compile warning when using the --enable-openbsd-malloc
20131 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
20132 - During configure, detect when we're building with clang version
20133 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
20134 CFLAGS. clang doesn't support them yet.
20135 - When sending an HTTP/1.1 proxy request, include a Host header.
20136 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
20137 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
20138 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
20139 - If we hit the error case where routerlist_insert() replaces an
20140 existing (old) server descriptor, make sure to remove that
20141 server descriptor from the old_routers list. Fix related to bug
20142 1776. Bugfix on 0.2.2.18-alpha.
20144 o Minor bugfixes (documentation and log messages):
20145 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
20146 Fixes bug 4856; bugfix on Tor 0.0.6.
20147 - Update "ClientOnly" man page entry to explain that there isn't
20148 really any point to messing with it. Resolves ticket 5005.
20149 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
20150 directory authority option (introduced in Tor 0.2.2.34).
20151 - Downgrade the "We're missing a certificate" message from notice
20152 to info: people kept mistaking it for a real problem, whereas it
20153 is seldom the problem even when we are failing to bootstrap. Fixes
20154 bug 5067; bugfix on 0.2.0.10-alpha.
20155 - Correctly spell "connect" in a log message on failure to create a
20156 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
20157 - Clarify the behavior of MaxCircuitDirtiness with hidden service
20158 circuits. Fixes issue 5259.
20161 - Directory authorities now reject versions of Tor older than
20162 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
20163 inclusive. These versions accounted for only a small fraction of
20164 the Tor network, and have numerous known security issues. Resolves
20166 - Update to the May 1 2012 Maxmind GeoLite Country database.
20169 - When sending or relaying a RELAY_EARLY cell, we used to convert
20170 it to a RELAY cell if the connection was using the v1 link
20171 protocol. This was a workaround for older versions of Tor, which
20172 didn't handle RELAY_EARLY cells properly. Now that all supported
20173 versions can handle RELAY_EARLY cells, and now that we're enforcing
20174 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
20175 remove this workaround. Addresses bug 4786.
20178 Changes in version 0.2.2.35 - 2011-12-16
20179 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
20180 buffers code. Absolutely everybody should upgrade.
20182 The bug relied on an incorrect calculation when making data continuous
20183 in one of our IO buffers, if the first chunk of the buffer was
20184 misaligned by just the wrong amount. The miscalculation would allow an
20185 attacker to overflow a piece of heap-allocated memory. To mount this
20186 attack, the attacker would need to either open a SOCKS connection to
20187 Tor's SocksPort (usually restricted to localhost), or target a Tor
20188 instance configured to make its connections through a SOCKS proxy
20189 (which Tor does not do by default).
20191 Good security practice requires that all heap-overflow bugs should be
20192 presumed to be exploitable until proven otherwise, so we are treating
20193 this as a potential code execution attack. Please upgrade immediately!
20194 This bug does not affect bufferevents-based builds of Tor. Special
20195 thanks to "Vektor" for reporting this issue to us!
20197 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20198 crash bugs for unusual configurations, and a long-term bug that
20199 would prevent Tor from starting on Windows machines with draconian
20202 With this release, we remind everyone that 0.2.0.x has reached its
20203 formal end-of-life. Those Tor versions have many known flaws, and
20204 nobody should be using them. You should upgrade -- ideally to the
20205 0.2.2.x series. If you're using a Linux or BSD and its packages are
20206 obsolete, stop using those packages and upgrade anyway.
20208 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20209 longer receive support after some time in early 2012.
20212 - Fix a heap overflow bug that could occur when trying to pull
20213 data into the first chunk of a buffer, when that chunk had
20214 already had some data drained from it. Fixes CVE-2011-2778;
20215 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20216 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20217 that it doesn't attempt to allocate a socketpair. This could cause
20218 some problems on Windows systems with overzealous firewalls. Fix for
20219 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20221 - If we mark an OR connection for close based on a cell we process,
20222 don't process any further cells on it. We already avoid further
20223 reads on marked-for-close connections, but now we also discard the
20224 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20225 which was the first version where we might mark a connection for
20226 close based on processing a cell on it.
20227 - Correctly sanity-check that we don't underflow on a memory
20228 allocation (and then assert) for hidden service introduction
20229 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20230 bugfix on 0.2.1.5-alpha.
20231 - Fix a memory leak when we check whether a hidden service
20232 descriptor has any usable introduction points left. Fixes bug
20233 4424. Bugfix on 0.2.2.25-alpha.
20234 - Don't crash when we're running as a relay and don't have a GeoIP
20235 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20236 we've had in the 0.2.3.x branch already.
20237 - When running as a client, do not print a misleading (and plain
20238 wrong) log message that we're collecting "directory request"
20239 statistics: clients don't collect statistics. Also don't create a
20240 useless (because empty) stats file in the stats/ directory. Fixes
20241 bug 4353; bugfix on 0.2.2.34.
20244 - Detect failure to initialize Libevent. This fix provides better
20245 detection for future instances of bug 4457.
20246 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20247 function. This was eating up hideously large amounts of time on some
20248 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20249 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20250 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20252 - Don't warn about unused log_mutex in log.c when building with
20253 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20254 0.1.0.6-rc which introduced --disable-threads.
20255 - When configuring, starting, or stopping an NT service, stop
20256 immediately after the service configuration attempt has succeeded
20257 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20258 - When sending a NETINFO cell, include the original address
20259 received for the other side, not its canonical address. Found
20260 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20261 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20262 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20263 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20264 occurred when a client tried to fetch a descriptor for a bridge
20265 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20266 - Backport fixes for a pair of compilation warnings on Windows.
20267 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20268 - If we had ever tried to call tor_addr_to_str on an address of
20269 unknown type, we would have done a strdup on an uninitialized
20270 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20271 Reported by "troll_un".
20272 - Correctly detect and handle transient lookup failures from
20273 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20274 Reported by "troll_un".
20275 - Fix null-pointer access that could occur if TLS allocation failed.
20276 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20277 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20278 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20281 - Add two new config options for directory authorities:
20282 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20283 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20284 that is always sufficient to satisfy the bandwidth requirement for
20285 the Guard flag. Now it will be easier for researchers to simulate
20286 Tor networks with different values. Resolves ticket 4484.
20287 - When Tor ignores a hidden service specified in its configuration,
20288 include the hidden service's directory in the warning message.
20289 Previously, we would only tell the user that some hidden service
20290 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20291 - Update to the December 6 2011 Maxmind GeoLite Country database.
20293 o Packaging changes:
20294 - Make it easier to automate expert package builds on Windows,
20295 by removing an absolute path from makensis.exe command.
20298 Changes in version 0.2.1.32 - 2011-12-16
20299 Tor 0.2.1.32 backports important security and privacy fixes for
20300 oldstable. This release is intended only for package maintainers and
20301 others who cannot use the 0.2.2 stable series. All others should be
20302 using Tor 0.2.2.x or newer.
20304 The Tor 0.2.1.x series will reach formal end-of-life some time in
20305 early 2012; we will stop releasing patches for it then.
20307 o Major bugfixes (also included in 0.2.2.x):
20308 - Correctly sanity-check that we don't underflow on a memory
20309 allocation (and then assert) for hidden service introduction
20310 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20311 bugfix on 0.2.1.5-alpha.
20312 - Fix a heap overflow bug that could occur when trying to pull
20313 data into the first chunk of a buffer, when that chunk had
20314 already had some data drained from it. Fixes CVE-2011-2778;
20315 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20318 - Update to the December 6 2011 Maxmind GeoLite Country database.
20321 Changes in version 0.2.2.34 - 2011-10-26
20322 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20323 can deanonymize Tor users. Everybody should upgrade.
20325 The attack relies on four components: 1) Clients reuse their TLS cert
20326 when talking to different relays, so relays can recognize a user by
20327 the identity key in her cert. 2) An attacker who knows the client's
20328 identity key can probe each guard relay to see if that identity key
20329 is connected to that guard relay right now. 3) A variety of active
20330 attacks in the literature (starting from "Low-Cost Traffic Analysis
20331 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20332 discover the guard relays that a Tor user visiting the website is using.
20333 4) Clients typically pick three guards at random, so the set of guards
20334 for a given user could well be a unique fingerprint for her. This
20335 release fixes components #1 and #2, which is enough to block the attack;
20336 the other two remain as open research problems. Special thanks to
20337 "frosty_un" for reporting the issue to us!
20339 Clients should upgrade so they are no longer recognizable by the TLS
20340 certs they present. Relays should upgrade so they no longer allow a
20341 remote attacker to probe them to test whether unpatched clients are
20342 currently connected to them.
20344 This release also fixes several vulnerabilities that allow an attacker
20345 to enumerate bridge relays. Some bridge enumeration attacks still
20346 remain; see for example proposal 188.
20348 o Privacy/anonymity fixes (clients):
20349 - Clients and bridges no longer send TLS certificate chains on
20350 outgoing OR connections. Previously, each client or bridge would
20351 use the same cert chain for all outgoing OR connections until
20352 its IP address changes, which allowed any relay that the client
20353 or bridge contacted to determine which entry guards it is using.
20354 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20355 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20356 no longer considers that connection as suitable for satisfying a
20357 circuit EXTEND request. Now relays can protect clients from the
20358 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20359 - Directory authorities no longer assign the Guard flag to relays
20360 that haven't upgraded to the above "refuse EXTEND requests
20361 to client connections" fix. Now directory authorities can
20362 protect clients from the CVE-2011-2768 issue even if neither
20363 the clients nor the relays have upgraded yet. There's a new
20364 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20365 to let us transition smoothly, else tomorrow there would be no
20368 o Privacy/anonymity fixes (bridge enumeration):
20369 - Bridge relays now do their directory fetches inside Tor TLS
20370 connections, like all the other clients do, rather than connecting
20371 directly to the DirPort like public relays do. Removes another
20372 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20373 - Bridges relays now build circuits for themselves in a more similar
20374 way to how clients build them. Removes another avenue for
20375 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20376 when bridges were introduced.
20377 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20378 that they initiated. Relays could distinguish incoming bridge
20379 connections from client connections, creating another avenue for
20380 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20381 Found by "frosty_un".
20384 - Fix a crash bug when changing node restrictions while a DNS lookup
20385 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20387 - Don't launch a useless circuit after failing to use one of a
20388 hidden service's introduction points. Previously, we would
20389 launch a new introduction circuit, but not set the hidden service
20390 which that circuit was intended to connect to, so it would never
20391 actually be used. A different piece of code would then create a
20392 new introduction circuit correctly. Bug reported by katmagic and
20393 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20396 - Change an integer overflow check in the OpenBSD_Malloc code so
20397 that GCC is less likely to eliminate it as impossible. Patch
20398 from Mansour Moufid. Fixes bug 4059.
20399 - When a hidden service turns an extra service-side introduction
20400 circuit into a general-purpose circuit, free the rend_data and
20401 intro_key fields first, so we won't leak memory if the circuit
20402 is cannibalized for use as another service-side introduction
20403 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20404 - Bridges now skip DNS self-tests, to act a little more stealthily.
20405 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20406 bridges. Patch by "warms0x".
20407 - Fix internal bug-checking logic that was supposed to catch
20408 failures in digest generation so that it will fail more robustly
20409 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20410 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20411 - Report any failure in init_keys() calls launched because our
20412 IP address has changed. Spotted by Coverity Scan. Bugfix on
20413 0.1.1.4-alpha; fixes CID 484.
20415 o Minor bugfixes (log messages and documentation):
20416 - Remove a confusing dollar sign from the example fingerprint in the
20417 man page, and also make the example fingerprint a valid one. Fixes
20418 bug 4309; bugfix on 0.2.1.3-alpha.
20419 - The next version of Windows will be called Windows 8, and it has
20420 a major version of 6, minor version of 2. Correctly identify that
20421 version instead of calling it "Very recent version". Resolves
20422 ticket 4153; reported by funkstar.
20423 - Downgrade log messages about circuit timeout calibration from
20424 "notice" to "info": they don't require or suggest any human
20425 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20426 bugfix on 0.2.2.14-alpha.
20429 - Turn on directory request statistics by default and include them in
20430 extra-info descriptors. Don't break if we have no GeoIP database.
20431 Backported from 0.2.3.1-alpha; implements ticket 3951.
20432 - Update to the October 4 2011 Maxmind GeoLite Country database.
20435 Changes in version 0.2.1.31 - 2011-10-26
20436 Tor 0.2.1.31 backports important security and privacy fixes for
20437 oldstable. This release is intended only for package maintainers and
20438 others who cannot use the 0.2.2 stable series. All others should be
20439 using Tor 0.2.2.x or newer.
20441 o Security fixes (also included in 0.2.2.x):
20442 - Replace all potentially sensitive memory comparison operations
20443 with versions whose runtime does not depend on the data being
20444 compared. This will help resist a class of attacks where an
20445 adversary can use variations in timing information to learn
20446 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20447 implementation by Robert Ransom based partially on code by DJB.)
20448 - Fix an assert in parsing router descriptors containing IPv6
20449 addresses. This one took down the directory authorities when
20450 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20452 o Privacy/anonymity fixes (also included in 0.2.2.x):
20453 - Clients and bridges no longer send TLS certificate chains on
20454 outgoing OR connections. Previously, each client or bridge would
20455 use the same cert chain for all outgoing OR connections until
20456 its IP address changes, which allowed any relay that the client
20457 or bridge contacted to determine which entry guards it is using.
20458 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20459 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20460 no longer considers that connection as suitable for satisfying a
20461 circuit EXTEND request. Now relays can protect clients from the
20462 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20463 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20464 that they initiated. Relays could distinguish incoming bridge
20465 connections from client connections, creating another avenue for
20466 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20467 Found by "frosty_un".
20468 - When receiving a hidden service descriptor, check that it is for
20469 the hidden service we wanted. Previously, Tor would store any
20470 hidden service descriptors that a directory gave it, whether it
20471 wanted them or not. This wouldn't have let an attacker impersonate
20472 a hidden service, but it did let directories pre-seed a client
20473 with descriptors that it didn't want. Bugfix on 0.0.6.
20474 - Avoid linkability based on cached hidden service descriptors: forget
20475 all hidden service descriptors cached as a client when processing a
20476 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20477 - Make the bridge directory authority refuse to answer directory
20478 requests for "all" descriptors. It used to include bridge
20479 descriptors in its answer, which was a major information leak.
20480 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20481 - Don't attach new streams to old rendezvous circuits after SIGNAL
20482 NEWNYM. Previously, we would keep using an existing rendezvous
20483 circuit if it remained open (i.e. if it were kept open by a
20484 long-lived stream, or if a new stream were attached to it before
20485 Tor could notice that it was old and no longer in use). Bugfix on
20486 0.1.1.15-rc; fixes bug 3375.
20488 o Minor bugfixes (also included in 0.2.2.x):
20489 - When we restart our relay, we might get a successful connection
20490 from the outside before we've started our reachability tests,
20491 triggering a warning: "ORPort found reachable, but I have no
20492 routerinfo yet. Failing to inform controller of success." This
20493 bug was harmless unless Tor is running under a controller
20494 like Vidalia, in which case the controller would never get a
20495 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20497 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20498 enabled. Fixes bug 1526.
20499 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20500 anything since 0.2.1.16-rc.
20501 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20502 None of the cases where we did this before were wrong, but by making
20503 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20504 - Fix a rare crash bug that could occur when a client was configured
20505 with a large number of bridges. Fixes bug 2629; bugfix on
20506 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20507 - Correct the warning displayed when a rendezvous descriptor exceeds
20508 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20510 - Fix an uncommon assertion failure when running with DNSPort under
20511 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20512 - When warning about missing zlib development packages during compile,
20513 give the correct package names. Bugfix on 0.2.0.1-alpha.
20514 - Require that introduction point keys and onion keys have public
20515 exponent 65537. Bugfix on 0.2.0.10-alpha.
20516 - Do not crash when our configuration file becomes unreadable, for
20517 example due to a permissions change, between when we start up
20518 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20520 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20522 - Always NUL-terminate the sun_path field of a sockaddr_un before
20523 passing it to the kernel. (Not a security issue: kernels are
20524 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20525 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20526 - Don't stack-allocate the list of supplementary GIDs when we're
20527 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20528 could take up to 256K, which is way too much stack. Found by
20529 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20531 o Minor bugfixes (only in 0.2.1.x):
20532 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20533 rely on them. Bugfix on 0.2.1.30.
20534 - Use git revisions instead of svn revisions when generating our
20535 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20537 o Minor features (also included in 0.2.2.x):
20538 - Adjust the expiration time on our SSL session certificates to
20539 better match SSL certs seen in the wild. Resolves ticket 4014.
20540 - Allow nameservers with IPv6 address. Resolves bug 2574.
20541 - Update to the October 4 2011 Maxmind GeoLite Country database.
20544 Changes in version 0.2.2.33 - 2011-09-13
20545 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
20546 TLS handshake that makes relays and bridges that run this new version
20547 reachable from Iran again.
20550 - Avoid an assertion failure when reloading a configuration with
20551 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20552 3923; bugfix on 0.2.2.25-alpha.
20554 o Minor features (security):
20555 - Check for replays of the public-key encrypted portion of an
20556 INTRODUCE1 cell, in addition to the current check for replays of
20557 the g^x value. This prevents a possible class of active attacks
20558 by an attacker who controls both an introduction point and a
20559 rendezvous point, and who uses the malleability of AES-CTR to
20560 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20561 that these attacks are infeasible (requiring the attacker to send
20562 on the order of zettabytes of altered cells in a short interval),
20563 but we'd rather block them off in case there are any classes of
20564 this attack that we missed. Reported by Willem Pinckaers.
20567 - Adjust the expiration time on our SSL session certificates to
20568 better match SSL certs seen in the wild. Resolves ticket 4014.
20569 - Change the default required uptime for a relay to be accepted as
20570 a HSDir (hidden service directory) from 24 hours to 25 hours.
20571 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20572 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20573 authorities to abstain from voting on assignment of the HSDir
20574 consensus flag. Related to bug 2649.
20575 - Update to the September 6 2011 Maxmind GeoLite Country database.
20577 o Minor bugfixes (documentation and log messages):
20578 - Correct the man page to explain that HashedControlPassword and
20579 CookieAuthentication can both be set, in which case either method
20580 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20581 when we decided to allow these config options to both be set. Issue
20582 raised by bug 3898.
20583 - Demote the 'replay detected' log message emitted when a hidden
20584 service receives the same Diffie-Hellman public key in two different
20585 INTRODUCE2 cells to info level. A normal Tor client can cause that
20586 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20587 fixes part of bug 2442.
20588 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20589 level. There is nothing that a hidden service's operator can do
20590 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20592 - Clarify a log message specifying the characters permitted in
20593 HiddenServiceAuthorizeClient client names. Previously, the log
20594 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20595 given the impression that every ASCII character between "+" and "_"
20596 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20599 - Provide a substitute implementation of lround() for MSVC, which
20600 apparently lacks it. Patch from Gisle Vanem.
20601 - Clean up some code issues that prevented Tor from building on older
20602 BSDs. Fixes bug 3894; reported by "grarpamp".
20603 - Search for a platform-specific version of "ar" when cross-compiling.
20604 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20607 Changes in version 0.2.2.32 - 2011-08-27
20608 The Tor 0.2.2 release series is dedicated to the memory of Andreas
20609 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
20610 a founder of the PETS community, a leader in our field, a mentor,
20611 and a friend. He left us with these words: "I had the possibility
20612 to contribute to this world that is not as it should be. I hope I
20613 could help in some areas to make the world a better place, and that
20614 I could also encourage other people to be engaged in improving the
20615 world. Please, stay engaged. This world needs you, your love, your
20616 initiative -- now I cannot be part of that anymore."
20618 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
20619 ready. More than two years in the making, this release features improved
20620 client performance and hidden service reliability, better compatibility
20621 for Android, correct behavior for bridges that listen on more than
20622 one address, more extensible and flexible directory object handling,
20623 better reporting of network statistics, improved code security, and
20624 many many other features and bugfixes.
20626 o Major features (client performance):
20627 - When choosing which cells to relay first, relays now favor circuits
20628 that have been quiet recently, to provide lower latency for
20629 low-volume circuits. By default, relays enable or disable this
20630 feature based on a setting in the consensus. They can override
20631 this default by using the new "CircuitPriorityHalflife" config
20632 option. Design and code by Ian Goldberg, Can Tang, and Chris
20634 - Directory authorities now compute consensus weightings that instruct
20635 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
20636 and no flag. Clients use these weightings to distribute network load
20637 more evenly across these different relay types. The weightings are
20638 in the consensus so we can change them globally in the future. Extra
20639 thanks to "outofwords" for finding some nasty security bugs in
20640 the first implementation of this feature.
20642 o Major features (client performance, circuit build timeout):
20643 - Tor now tracks how long it takes to build client-side circuits
20644 over time, and adapts its timeout to local network performance.
20645 Since a circuit that takes a long time to build will also provide
20646 bad performance, we get significant latency improvements by
20647 discarding the slowest 20% of circuits. Specifically, Tor creates
20648 circuits more aggressively than usual until it has enough data
20649 points for a good timeout estimate. Implements proposal 151.
20650 - Circuit build timeout constants can be controlled by consensus
20651 parameters. We set good defaults for these parameters based on
20652 experimentation on broadband and simulated high-latency links.
20653 - Circuit build time learning can be disabled via consensus parameter
20654 or by the client via a LearnCircuitBuildTimeout config option. We
20655 also automatically disable circuit build time calculation if either
20656 AuthoritativeDirectory is set, or if we fail to write our state
20657 file. Implements ticket 1296.
20659 o Major features (relays use their capacity better):
20660 - Set SO_REUSEADDR socket option on all sockets, not just
20661 listeners. This should help busy exit nodes avoid running out of
20662 useable ports just because all the ports have been used in the
20663 near past. Resolves issue 2850.
20664 - Relays now save observed peak bandwidth throughput rates to their
20665 state file (along with total usage, which was already saved),
20666 so that they can determine their correct estimated bandwidth on
20667 restart. Resolves bug 1863, where Tor relays would reset their
20668 estimated bandwidth to 0 after restarting.
20669 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
20670 should give us approximately 40-50% more Guard-flagged nodes,
20671 improving the anonymity the Tor network can provide and also
20672 decreasing the dropoff in throughput that relays experience when
20673 they first get the Guard flag.
20674 - Directory authorities now take changes in router IP address and
20675 ORPort into account when determining router stability. Previously,
20676 if a router changed its IP or ORPort, the authorities would not
20677 treat it as having any downtime for the purposes of stability
20678 calculation, whereas clients would experience downtime since the
20679 change would take a while to propagate to them. Resolves issue 1035.
20680 - New AccelName and AccelDir options add support for dynamic OpenSSL
20681 hardware crypto acceleration engines.
20683 o Major features (relays control their load better):
20684 - Exit relays now try harder to block exit attempts from unknown
20685 relays, to make it harder for people to use them as one-hop proxies
20686 a la tortunnel. Controlled by the refuseunknownexits consensus
20687 parameter (currently enabled), or you can override it on your
20688 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
20689 based on a variant of proposal 163.
20690 - Add separate per-conn write limiting to go with the per-conn read
20691 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
20692 but never per-conn write limits.
20693 - New consensus params "bwconnrate" and "bwconnburst" to let us
20694 rate-limit client connections as they enter the network. It's
20695 controlled in the consensus so we can turn it on and off for
20696 experiments. It's starting out off. Based on proposal 163.
20698 o Major features (controllers):
20699 - Export GeoIP information on bridge usage to controllers even if we
20700 have not yet been running for 24 hours. Now Vidalia bridge operators
20701 can get more accurate and immediate feedback about their
20702 contributions to the network.
20703 - Add an __OwningControllerProcess configuration option and a
20704 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
20705 that when it exits, Tor will shut down. Implements feature 3049.
20707 o Major features (directory authorities):
20708 - Directory authorities now create, vote on, and serve multiple
20709 parallel formats of directory data as part of their voting process.
20710 Partially implements Proposal 162: "Publish the consensus in
20712 - Directory authorities now agree on and publish small summaries
20713 of router information that clients can use in place of regular
20714 server descriptors. This transition will allow Tor 0.2.3 clients
20715 to use far less bandwidth for downloading information about the
20716 network. Begins the implementation of Proposal 158: "Clients
20717 download consensus + microdescriptors".
20718 - The directory voting system is now extensible to use multiple hash
20719 algorithms for signatures and resource selection. Newer formats
20720 are signed with SHA256, with a possibility for moving to a better
20721 hash algorithm in the future.
20722 - Directory authorities can now vote on arbitrary integer values as
20723 part of the consensus process. This is designed to help set
20724 network-wide parameters. Implements proposal 167.
20726 o Major features and bugfixes (node selection):
20727 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
20728 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
20729 options. Previously, we had been ambiguous in describing what
20730 counted as an "exit" node, and what operations exactly "StrictNodes
20731 0" would permit. This created confusion when people saw nodes built
20732 through unexpected circuits, and made it hard to tell real bugs from
20733 surprises. Now the intended behavior is:
20734 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
20735 a node that delivers user traffic outside the Tor network.
20736 . "Entry", in the context of EntryNodes, means a node used as the
20737 first hop of a multihop circuit. It doesn't include direct
20738 connections to directory servers.
20739 . "ExcludeNodes" applies to all nodes.
20740 . "StrictNodes" changes the behavior of ExcludeNodes only. When
20741 StrictNodes is set, Tor should avoid all nodes listed in
20742 ExcludeNodes, even when it will make user requests fail. When
20743 StrictNodes is *not* set, then Tor should follow ExcludeNodes
20744 whenever it can, except when it must use an excluded node to
20745 perform self-tests, connect to a hidden service, provide a
20746 hidden service, fulfill a .exit request, upload directory
20747 information, or fetch directory information.
20748 Collectively, the changes to implement the behavior fix bug 1090.
20749 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
20750 change during a config reload, mark and discard all our origin
20751 circuits. This fix should address edge cases where we change the
20752 config options and but then choose a circuit that we created before
20754 - Make EntryNodes config option much more aggressive even when
20755 StrictNodes is not set. Before it would prepend your requested
20756 entrynodes to your list of guard nodes, but feel free to use others
20757 after that. Now it chooses only from your EntryNodes if any of
20758 those are available, and only falls back to others if a) they're
20759 all down and b) StrictNodes is not set.
20760 - Now we refresh your entry guards from EntryNodes at each consensus
20761 fetch -- rather than just at startup and then they slowly rot as
20762 the network changes.
20763 - Add support for the country code "{??}" in torrc options like
20764 ExcludeNodes, to indicate all routers of unknown country. Closes
20766 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
20767 a node is listed in both, it's treated as excluded.
20768 - ExcludeNodes now applies to directory nodes -- as a preference if
20769 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
20770 Don't exclude all the directory authorities and set StrictNodes to 1
20771 unless you really want your Tor to break.
20772 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
20773 - ExcludeExitNodes now overrides .exit requests.
20774 - We don't use bridges listed in ExcludeNodes.
20775 - When StrictNodes is 1:
20776 . We now apply ExcludeNodes to hidden service introduction points
20777 and to rendezvous points selected by hidden service users. This
20778 can make your hidden service less reliable: use it with caution!
20779 . If we have used ExcludeNodes on ourself, do not try relay
20780 reachability self-tests.
20781 . If we have excluded all the directory authorities, we will not
20782 even try to upload our descriptor if we're a relay.
20783 . Do not honor .exit requests to an excluded node.
20784 - When the set of permitted nodes changes, we now remove any mappings
20785 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
20787 - We never cannibalize a circuit that had excluded nodes on it, even
20788 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
20789 - Improve log messages related to excluded nodes.
20791 o Major features (misc):
20792 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
20793 to help Tor build correctly for Android phones.
20794 - The options SocksPort, ControlPort, and so on now all accept a
20795 value "auto" that opens a socket on an OS-selected port. A
20796 new ControlPortWriteToFile option tells Tor to write its
20797 actual control port or ports to a chosen file. If the option
20798 ControlPortFileGroupReadable is set, the file is created as
20799 group-readable. Now users can run two Tor clients on the same
20800 system without needing to manually mess with parameters. Resolves
20801 part of ticket 3076.
20802 - Tor now supports tunneling all of its outgoing connections over
20803 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
20804 configuration options. Code by Christopher Davis.
20806 o Code security improvements:
20807 - Replace all potentially sensitive memory comparison operations
20808 with versions whose runtime does not depend on the data being
20809 compared. This will help resist a class of attacks where an
20810 adversary can use variations in timing information to learn
20811 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20812 implementation by Robert Ransom based partially on code by DJB.)
20813 - Enable Address Space Layout Randomization (ASLR) and Data Execution
20814 Prevention (DEP) by default on Windows to make it harder for
20815 attackers to exploit vulnerabilities. Patch from John Brooks.
20816 - New "--enable-gcc-hardening" ./configure flag (off by default)
20817 to turn on gcc compile time hardening options. It ensures
20818 that signed ints have defined behavior (-fwrapv), enables
20819 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
20820 with canaries (-fstack-protector-all), turns on ASLR protection if
20821 supported by the kernel (-fPIE, -pie), and adds additional security
20822 related warnings. Verified to work on Mac OS X and Debian Lenny.
20823 - New "--enable-linker-hardening" ./configure flag (off by default)
20824 to turn on ELF specific hardening features (relro, now). This does
20825 not work with Mac OS X or any other non-ELF binary format.
20826 - Always search the Windows system directory for system DLLs, and
20827 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
20828 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
20829 current and future memory pages via mlockall(). On supported
20830 platforms (modern Linux and probably BSD but not Windows or OS X),
20831 this should effectively disable any and all attempts to page out
20832 memory. This option requires that you start your Tor as root --
20833 if you use DisableAllSwap, please consider using the User option
20834 to properly reduce the privileges of your Tor.
20836 o Major bugfixes (crashes):
20837 - Fix crash bug on platforms where gmtime and localtime can return
20838 NULL. Windows 7 users were running into this one. Fixes part of bug
20839 2077. Bugfix on all versions of Tor. Found by boboper.
20840 - Introduce minimum/maximum values that clients will believe
20841 from the consensus. Now we'll have a better chance to avoid crashes
20842 or worse when a consensus param has a weird value.
20843 - Fix a rare crash bug that could occur when a client was configured
20844 with a large number of bridges. Fixes bug 2629; bugfix on
20845 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20846 - Do not crash when our configuration file becomes unreadable, for
20847 example due to a permissions change, between when we start up
20848 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20850 - If we're in the pathological case where there's no exit bandwidth
20851 but there is non-exit bandwidth, or no guard bandwidth but there
20852 is non-guard bandwidth, don't crash during path selection. Bugfix
20854 - Fix a crash bug when trying to initialize the evdns module in
20855 Libevent 2. Bugfix on 0.2.1.16-rc.
20857 o Major bugfixes (stability):
20858 - Fix an assert in parsing router descriptors containing IPv6
20859 addresses. This one took down the directory authorities when
20860 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20861 - Fix an uncommon assertion failure when running with DNSPort under
20862 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20863 - Treat an unset $HOME like an empty $HOME rather than triggering an
20864 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
20865 - More gracefully handle corrupt state files, removing asserts
20866 in favor of saving a backup and resetting state.
20867 - Instead of giving an assertion failure on an internal mismatch
20868 on estimated freelist size, just log a BUG warning and try later.
20869 Mitigates but does not fix bug 1125.
20870 - Fix an assert that got triggered when using the TestingTorNetwork
20871 configuration option and then issuing a GETINFO config-text control
20872 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
20873 - If the cached cert file is unparseable, warn but don't exit.
20875 o Privacy fixes (relays/bridges):
20876 - Don't list Windows capabilities in relay descriptors. We never made
20877 use of them, and maybe it's a bad idea to publish them. Bugfix
20879 - If the Nickname configuration option isn't given, Tor would pick a
20880 nickname based on the local hostname as the nickname for a relay.
20881 Because nicknames are not very important in today's Tor and the
20882 "Unnamed" nickname has been implemented, this is now problematic
20883 behavior: It leaks information about the hostname without being
20884 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
20885 introduced the Unnamed nickname. Reported by tagnaq.
20886 - Maintain separate TLS contexts and certificates for incoming and
20887 outgoing connections in bridge relays. Previously we would use the
20888 same TLS contexts and certs for incoming and outgoing connections.
20889 Bugfix on 0.2.0.3-alpha; addresses bug 988.
20890 - Maintain separate identity keys for incoming and outgoing TLS
20891 contexts in bridge relays. Previously we would use the same
20892 identity keys for incoming and outgoing TLS contexts. Bugfix on
20893 0.2.0.3-alpha; addresses the other half of bug 988.
20894 - Make the bridge directory authority refuse to answer directory
20895 requests for "all descriptors". It used to include bridge
20896 descriptors in its answer, which was a major information leak.
20897 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20899 o Privacy fixes (clients):
20900 - When receiving a hidden service descriptor, check that it is for
20901 the hidden service we wanted. Previously, Tor would store any
20902 hidden service descriptors that a directory gave it, whether it
20903 wanted them or not. This wouldn't have let an attacker impersonate
20904 a hidden service, but it did let directories pre-seed a client
20905 with descriptors that it didn't want. Bugfix on 0.0.6.
20906 - Start the process of disabling ".exit" address notation, since it
20907 can be used for a variety of esoteric application-level attacks
20908 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
20910 - Reject attempts at the client side to open connections to private
20911 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
20912 a randomly chosen exit node. Attempts to do so are always
20913 ill-defined, generally prevented by exit policies, and usually
20914 in error. This will also help to detect loops in transparent
20915 proxy configurations. You can disable this feature by setting
20916 "ClientRejectInternalAddresses 0" in your torrc.
20917 - Log a notice when we get a new control connection. Now it's easier
20918 for security-conscious users to recognize when a local application
20919 is knocking on their controller door. Suggested by bug 1196.
20921 o Privacy fixes (newnym):
20922 - Avoid linkability based on cached hidden service descriptors: forget
20923 all hidden service descriptors cached as a client when processing a
20924 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20925 - On SIGHUP, do not clear out all TrackHostExits mappings, client
20926 DNS cache entries, and virtual address mappings: that's what
20927 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
20928 - Don't attach new streams to old rendezvous circuits after SIGNAL
20929 NEWNYM. Previously, we would keep using an existing rendezvous
20930 circuit if it remained open (i.e. if it were kept open by a
20931 long-lived stream, or if a new stream were attached to it before
20932 Tor could notice that it was old and no longer in use). Bugfix on
20933 0.1.1.15-rc; fixes bug 3375.
20935 o Major bugfixes (relay bandwidth accounting):
20936 - Fix a bug that could break accounting on 64-bit systems with large
20937 time_t values, making them hibernate for impossibly long intervals.
20938 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
20939 - Fix a bug in bandwidth accounting that could make us use twice
20940 the intended bandwidth when our interval start changes due to
20941 daylight saving time. Now we tolerate skew in stored vs computed
20942 interval starts: if the start of the period changes by no more than
20943 50% of the period's duration, we remember bytes that we transferred
20944 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
20946 o Major bugfixes (bridges):
20947 - Bridges now use "reject *:*" as their default exit policy. Bugfix
20948 on 0.2.0.3-alpha. Fixes bug 1113.
20949 - If you configure your bridge with a known identity fingerprint,
20950 and the bridge authority is unreachable (as it is in at least
20951 one country now), fall back to directly requesting the descriptor
20952 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
20954 - Fix a bug where bridge users who configure the non-canonical
20955 address of a bridge automatically switch to its canonical
20956 address. If a bridge listens at more than one address, it
20957 should be able to advertise those addresses independently and
20958 any non-blocked addresses should continue to work. Bugfix on Tor
20959 0.2.0.3-alpha. Fixes bug 2510.
20960 - If you configure Tor to use bridge A, and then quit and
20961 configure Tor to use bridge B instead (or if you change Tor
20962 to use bridge B via the controller), it would happily continue
20963 to use bridge A if it's still reachable. While this behavior is
20964 a feature if your goal is connectivity, in some scenarios it's a
20965 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
20966 - When the controller configures a new bridge, don't wait 10 to 60
20967 seconds before trying to fetch its descriptor. Bugfix on
20968 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
20970 o Major bugfixes (directory authorities):
20971 - Many relays have been falling out of the consensus lately because
20972 not enough authorities know about their descriptor for them to get
20973 a majority of votes. When we deprecated the v2 directory protocol,
20974 we got rid of the only way that v3 authorities can hear from each
20975 other about other descriptors. Now authorities examine every v3
20976 vote for new descriptors, and fetch them from that authority. Bugfix
20978 - Authorities could be tricked into giving out the Exit flag to relays
20979 that didn't allow exiting to any ports. This bug could screw
20980 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
20981 1238. Bug discovered by Martin Kowalczyk.
20982 - If all authorities restart at once right before a consensus vote,
20983 nobody will vote about "Running", and clients will get a consensus
20984 with no usable relays. Instead, authorities refuse to build a
20985 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
20987 o Major bugfixes (stream-level fairness):
20988 - When receiving a circuit-level SENDME for a blocked circuit, try
20989 to package cells fairly from all the streams that had previously
20990 been blocked on that circuit. Previously, we had started with the
20991 oldest stream, and allowed each stream to potentially exhaust
20992 the circuit's package window. This gave older streams on any
20993 given circuit priority over newer ones. Fixes bug 1937. Detected
20994 originally by Camilo Viecco. This bug was introduced before the
20995 first Tor release, in svn commit r152: it is the new winner of
20996 the longest-lived bug prize.
20997 - Fix a stream fairness bug that would cause newer streams on a given
20998 circuit to get preference when reading bytes from the origin or
20999 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
21000 introduced before the first Tor release, in svn revision r152.
21001 - When the exit relay got a circuit-level sendme cell, it started
21002 reading on the exit streams, even if had 500 cells queued in the
21003 circuit queue already, so the circuit queue just grew and grew in
21004 some cases. We fix this by not re-enabling reading on receipt of a
21005 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
21006 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
21008 - Newly created streams were allowed to read cells onto circuits,
21009 even if the circuit's cell queue was blocked and waiting to drain.
21010 This created potential unfairness, as older streams would be
21011 blocked, but newer streams would gladly fill the queue completely.
21012 We add code to detect this situation and prevent any stream from
21013 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
21016 o Major bugfixes (hidden services):
21017 - Apply circuit timeouts to opened hidden-service-related circuits
21018 based on the correct start time. Previously, we would apply the
21019 circuit build timeout based on time since the circuit's creation;
21020 it was supposed to be applied based on time since the circuit
21021 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21022 - Improve hidden service robustness: When we find that we have
21023 extended a hidden service's introduction circuit to a relay not
21024 listed as an introduction point in the HS descriptor we currently
21025 have, retry with an introduction point from the current
21026 descriptor. Previously we would just give up. Fixes bugs 1024 and
21027 1930; bugfix on 0.2.0.10-alpha.
21028 - Directory authorities now use data collected from their own
21029 uptime observations when choosing whether to assign the HSDir flag
21030 to relays, instead of trusting the uptime value the relay reports in
21031 its descriptor. This change helps prevent an attack where a small
21032 set of nodes with frequently-changing identity keys can blackhole
21033 a hidden service. (Only authorities need upgrade; others will be
21034 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
21035 - Stop assigning the HSDir flag to relays that disable their
21036 DirPort (and thus will refuse to answer directory requests). This
21037 fix should dramatically improve the reachability of hidden services:
21038 hidden services and hidden service clients pick six HSDir relays
21039 to store and retrieve the hidden service descriptor, and currently
21040 about half of the HSDir relays will refuse to work. Bugfix on
21041 0.2.0.10-alpha; fixes part of bug 1693.
21043 o Major bugfixes (misc):
21044 - Clients now stop trying to use an exit node associated with a given
21045 destination by TrackHostExits if they fail to reach that exit node.
21046 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21047 - Fix a regression that caused Tor to rebind its ports if it receives
21048 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
21049 - Remove an extra pair of quotation marks around the error
21050 message in control-port STATUS_GENERAL BUG events. Bugfix on
21051 0.1.2.6-alpha; fixes bug 3732.
21053 o Minor features (relays):
21054 - Ensure that no empty [dirreq-](read|write)-history lines are added
21055 to an extrainfo document. Implements ticket 2497.
21056 - When bandwidth accounting is enabled, be more generous with how
21057 much bandwidth we'll use up before entering "soft hibernation".
21058 Previously, we'd refuse new connections and circuits once we'd
21059 used up 95% of our allotment. Now, we use up 95% of our allotment,
21060 AND make sure that we have no more than 500MB (or 3 hours of
21061 expected traffic, whichever is lower) remaining before we enter
21063 - Relays now log the reason for publishing a new relay descriptor,
21064 so we have a better chance of hunting down instances of bug 1810.
21065 Resolves ticket 3252.
21066 - Log a little more clearly about the times at which we're no longer
21067 accepting new connections (e.g. due to hibernating). Resolves
21069 - When AllowSingleHopExits is set, print a warning to explain to the
21070 relay operator why most clients are avoiding her relay.
21071 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
21072 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
21073 clients are already deprecated because of security bugs.
21075 o Minor features (network statistics):
21076 - Directory mirrors that set "DirReqStatistics 1" write statistics
21077 about directory requests to disk every 24 hours. As compared to the
21078 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
21079 improvements: 1) stats are written to disk exactly every 24 hours;
21080 2) estimated shares of v2 and v3 requests are determined as mean
21081 values, not at the end of a measurement period; 3) unresolved
21082 requests are listed with country code '??'; 4) directories also
21083 measure download times.
21084 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
21085 number of exit streams and transferred bytes per port to disk every
21087 - Relays that set "CellStatistics 1" write statistics on how long
21088 cells spend in their circuit queues to disk every 24 hours.
21089 - Entry nodes that set "EntryStatistics 1" write statistics on the
21090 rough number and origins of connecting clients to disk every 24
21092 - Relays that write any of the above statistics to disk and set
21093 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
21094 their extra-info documents. Implements proposal 166.
21096 o Minor features (GeoIP and statistics):
21097 - Provide a log message stating which geoip file we're parsing
21098 instead of just stating that we're parsing the geoip file.
21099 Implements ticket 2432.
21100 - Make sure every relay writes a state file at least every 12 hours.
21101 Previously, a relay could go for weeks without writing its state
21102 file, and on a crash could lose its bandwidth history, capacity
21103 estimates, client country statistics, and so on. Addresses bug 3012.
21104 - Relays report the number of bytes spent on answering directory
21105 requests in extra-info descriptors similar to {read,write}-history.
21106 Implements enhancement 1790.
21107 - Report only the top 10 ports in exit-port stats in order not to
21108 exceed the maximum extra-info descriptor length of 50 KB. Implements
21110 - If writing the state file to disk fails, wait up to an hour before
21111 retrying again, rather than trying again each second. Fixes bug
21112 2346; bugfix on Tor 0.1.1.3-alpha.
21113 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
21114 when we switch from being a public relay to a bridge. Otherwise
21115 there will still be clients that see the relay in their consensus,
21116 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
21118 - Update to the August 2 2011 Maxmind GeoLite Country database.
21120 o Minor features (clients):
21121 - When expiring circuits, use microsecond timers rather than
21122 one-second timers. This can avoid an unpleasant situation where a
21123 circuit is launched near the end of one second and expired right
21124 near the beginning of the next, and prevent fluctuations in circuit
21126 - If we've configured EntryNodes and our network goes away and/or all
21127 our entrynodes get marked down, optimistically retry them all when
21128 a new socks application request appears. Fixes bug 1882.
21129 - Always perform router selections using weighted relay bandwidth,
21130 even if we don't need a high capacity circuit at the time. Non-fast
21131 circuits now only differ from fast ones in that they can use relays
21132 not marked with the Fast flag. This "feature" could turn out to
21133 be a horrible bug; we should investigate more before it goes into
21135 - When we run out of directory information such that we can't build
21136 circuits, but then get enough that we can build circuits, log when
21137 we actually construct a circuit, so the user has a better chance of
21138 knowing what's going on. Fixes bug 1362.
21139 - Log SSL state transitions at debug level during handshake, and
21140 include SSL states in error messages. This may help debug future
21141 SSL handshake issues.
21143 o Minor features (directory authorities):
21144 - When a router changes IP address or port, authorities now launch
21145 a new reachability test for it. Implements ticket 1899.
21146 - Directory authorities now reject relays running any versions of
21147 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
21148 known bugs that keep RELAY_EARLY cells from working on rendezvous
21149 circuits. Followup to fix for bug 2081.
21150 - Directory authorities now reject relays running any version of Tor
21151 older than 0.2.0.26-rc. That version is the earliest that fetches
21152 current directory information correctly. Fixes bug 2156.
21153 - Directory authorities now do an immediate reachability check as soon
21154 as they hear about a new relay. This change should slightly reduce
21155 the time between setting up a relay and getting listed as running
21156 in the consensus. It should also improve the time between setting
21157 up a bridge and seeing use by bridge users.
21158 - Directory authorities no longer launch a TLS connection to every
21159 relay as they startup. Now that we have 2k+ descriptors cached,
21160 the resulting network hiccup is becoming a burden. Besides,
21161 authorities already avoid voting about Running for the first half
21162 hour of their uptime.
21163 - Directory authorities now log the source of a rejected POSTed v3
21164 networkstatus vote, so we can track failures better.
21165 - Backport code from 0.2.3.x that allows directory authorities to
21166 clean their microdescriptor caches. Needed to resolve bug 2230.
21168 o Minor features (hidden services):
21169 - Use computed circuit-build timeouts to decide when to launch
21170 parallel introduction circuits for hidden services. (Previously,
21171 we would retry after 15 seconds.)
21172 - Don't allow v0 hidden service authorities to act as clients.
21173 Required by fix for bug 3000.
21174 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
21175 by fix for bug 3000.
21176 - Make hidden services work better in private Tor networks by not
21177 requiring any uptime to join the hidden service descriptor
21178 DHT. Implements ticket 2088.
21179 - Log (at info level) when purging pieces of hidden-service-client
21180 state because of SIGNAL NEWNYM.
21182 o Minor features (controller interface):
21183 - New "GETINFO net/listeners/(type)" controller command to return
21184 a list of addresses and ports that are bound for listeners for a
21185 given connection type. This is useful when the user has configured
21186 "SocksPort auto" and the controller needs to know which port got
21187 chosen. Resolves another part of ticket 3076.
21188 - Have the controller interface give a more useful message than
21189 "Internal Error" in response to failed GETINFO requests.
21190 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
21191 event, to give information on the current rate of circuit timeouts
21192 over our stored history.
21193 - The 'EXTENDCIRCUIT' control port command can now be used with
21194 a circ id of 0 and no path. This feature will cause Tor to build
21195 a new 'fast' general purpose circuit using its own path selection
21197 - Added a BUILDTIMEOUT_SET controller event to describe changes
21198 to the circuit build timeout.
21199 - New controller command "getinfo config-text". It returns the
21200 contents that Tor would write if you send it a SAVECONF command,
21201 so the controller can write the file to disk itself.
21203 o Minor features (controller protocol):
21204 - Add a new ControlSocketsGroupWritable configuration option: when
21205 it is turned on, ControlSockets are group-writeable by the default
21206 group of the current user. Patch by Jérémy Bobbio; implements
21208 - Tor now refuses to create a ControlSocket in a directory that is
21209 world-readable (or group-readable if ControlSocketsGroupWritable
21210 is 0). This is necessary because some operating systems do not
21211 enforce permissions on an AF_UNIX sockets. Permissions on the
21212 directory holding the socket, however, seems to work everywhere.
21213 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
21214 not. This would lead to a cookie that is still not group readable.
21215 Closes bug 1843. Suggested by katmagic.
21216 - Future-proof the controller protocol a bit by ignoring keyword
21217 arguments we do not recognize.
21219 o Minor features (more useful logging):
21220 - Revise most log messages that refer to nodes by nickname to
21221 instead use the "$key=nickname at address" format. This should be
21222 more useful, especially since nicknames are less and less likely
21223 to be unique. Resolves ticket 3045.
21224 - When an HTTPS proxy reports "403 Forbidden", we now explain
21225 what it means rather than calling it an unexpected status code.
21226 Closes bug 2503. Patch from Michael Yakubovich.
21227 - Rate-limit a warning about failures to download v2 networkstatus
21228 documents. Resolves part of bug 1352.
21229 - Rate-limit the "your application is giving Tor only an IP address"
21230 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
21231 - Rate-limit "Failed to hand off onionskin" warnings.
21232 - When logging a rate-limited warning, we now mention how many messages
21233 got suppressed since the last warning.
21234 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
21235 2 no signature, 4 required" messages about consensus signatures
21236 easier to read, and make sure they get logged at the same severity
21237 as the messages explaining which keys are which. Fixes bug 1290.
21238 - Don't warn when we have a consensus that we can't verify because
21239 of missing certificates, unless those certificates are ones
21240 that we have been trying and failing to download. Fixes bug 1145.
21242 o Minor features (log domains):
21243 - Add documentation for configuring logging at different severities in
21244 different log domains. We've had this feature since 0.2.1.1-alpha,
21245 but for some reason it never made it into the manpage. Fixes
21247 - Make it simpler to specify "All log domains except for A and B".
21248 Previously you needed to say "[*,~A,~B]". Now you can just say
21250 - Add a "LogMessageDomains 1" option to include the domains of log
21251 messages along with the messages. Without this, there's no way
21252 to use log domains without reading the source or doing a lot
21254 - Add a new "Handshake" log domain for activities that happen
21255 during the TLS handshake.
21257 o Minor features (build process):
21258 - Make compilation with clang possible when using
21259 "--enable-gcc-warnings" by removing two warning options that clang
21260 hasn't implemented yet and by fixing a few warnings. Resolves
21262 - Detect platforms that brokenly use a signed size_t, and refuse to
21263 build there. Found and analyzed by doorss and rransom.
21264 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
21266 - Add support for statically linking zlib by specifying
21267 "--enable-static-zlib", to go with our support for statically
21268 linking openssl and libevent. Resolves bug 1358.
21269 - Instead of adding the svn revision to the Tor version string, report
21270 the git commit (when we're building from a git checkout).
21271 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
21273 - New --digests command-line switch to output the digests of the
21274 source files Tor was built with.
21275 - Generate our manpage and HTML documentation using Asciidoc. This
21276 change should make it easier to maintain the documentation, and
21277 produce nicer HTML. The build process fails if asciidoc cannot
21278 be found and building with asciidoc isn't disabled (via the
21279 "--disable-asciidoc" argument to ./configure. Skipping the manpage
21280 speeds up the build considerably.
21282 o Minor features (options / torrc):
21283 - Warn when the same option is provided more than once in a torrc
21284 file, on the command line, or in a single SETCONF statement, and
21285 the option is one that only accepts a single line. Closes bug 1384.
21286 - Warn when the user configures two HiddenServiceDir lines that point
21287 to the same directory. Bugfix on 0.0.6 (the version introducing
21288 HiddenServiceDir); fixes bug 3289.
21289 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
21290 do individual connection-level rate limiting of clients. The torrc
21291 config options with the same names trump the consensus params, if
21292 both are present. Replaces the old "bwconnrate" and "bwconnburst"
21293 consensus params which were broken from 0.2.2.7-alpha through
21294 0.2.2.14-alpha. Closes bug 1947.
21295 - New config option "WarnUnsafeSocks 0" disables the warning that
21296 occurs whenever Tor receives a socks handshake using a version of
21297 the socks protocol that can only provide an IP address (rather
21298 than a hostname). Setups that do DNS locally over Tor are fine,
21299 and we shouldn't spam the logs in that case.
21300 - New config option "CircuitStreamTimeout" to override our internal
21301 timeout schedule for how many seconds until we detach a stream from
21302 a circuit and try a new circuit. If your network is particularly
21303 slow, you might want to set this to a number like 60.
21304 - New options for SafeLogging to allow scrubbing only log messages
21305 generated while acting as a relay. Specify "SafeLogging relay" if
21306 you want to ensure that only messages known to originate from
21307 client use of the Tor process will be logged unsafely.
21308 - Time and memory units in the configuration file can now be set to
21309 fractional units. For example, "2.5 GB" is now a valid value for
21311 - Support line continuations in the torrc config file. If a line
21312 ends with a single backslash character, the newline is ignored, and
21313 the configuration value is treated as continuing on the next line.
21316 o Minor features (unit tests):
21317 - Revise our unit tests to use the "tinytest" framework, so we
21318 can run tests in their own processes, have smarter setup/teardown
21319 code, and so on. The unit test code has moved to its own
21320 subdirectory, and has been split into multiple modules.
21321 - Add a unit test for cross-platform directory-listing code.
21322 - Add some forgotten return value checks during unit tests. Found
21324 - Use GetTempDir to find the proper temporary directory location on
21325 Windows when generating temporary files for the unit tests. Patch
21328 o Minor features (misc):
21329 - The "torify" script now uses torsocks where available.
21330 - Make Libevent log messages get delivered to controllers later,
21331 and not from inside the Libevent log handler. This prevents unsafe
21332 reentrant Libevent calls while still letting the log messages
21334 - Certain Tor clients (such as those behind check.torproject.org) may
21335 want to fetch the consensus in an extra early manner. To enable this
21336 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
21337 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
21338 as only certain clients who must have this information sooner should
21340 - Expand homedirs passed to tor-checkkey. This should silence a
21341 coverity complaint about passing a user-supplied string into
21342 open() without checking it.
21343 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
21344 used on bridges, and it makes bridge scanning somewhat easier.
21345 - Create the /var/run/tor directory on startup on OpenSUSE if it is
21346 not already created. Patch from Andreas Stieger. Fixes bug 2573.
21348 o Minor bugfixes (relays):
21349 - When a relay decides that its DNS is too broken for it to serve
21350 as an exit server, it advertised itself as a non-exit, but
21351 continued to act as an exit. This could create accidental
21352 partitioning opportunities for users. Instead, if a relay is
21353 going to advertise reject *:* as its exit policy, it should
21354 really act with exit policy "reject *:*". Fixes bug 2366.
21355 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
21356 - Publish a router descriptor even if generating an extra-info
21357 descriptor fails. Previously we would not publish a router
21358 descriptor without an extra-info descriptor; this can cause fast
21359 exit relays collecting exit-port statistics to drop from the
21360 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
21361 - When we're trying to guess whether we know our IP address as
21362 a relay, we would log various ways that we failed to guess
21363 our address, but never log that we ended up guessing it
21364 successfully. Now add a log line to help confused and anxious
21365 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
21366 - For bandwidth accounting, calculate our expected bandwidth rate
21367 based on the time during which we were active and not in
21368 soft-hibernation during the last interval. Previously, we were
21369 also considering the time spent in soft-hibernation. If this
21370 was a long time, we would wind up underestimating our bandwidth
21371 by a lot, and skewing our wakeup time towards the start of the
21372 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
21373 - Demote a confusing TLS warning that relay operators might get when
21374 someone tries to talk to their ORPort. It is not the operator's
21375 fault, nor can they do anything about it. Fixes bug 1364; bugfix
21377 - Change "Application request when we're believed to be offline."
21378 notice to "Application request when we haven't used client
21379 functionality lately.", to clarify that it's not an error. Bugfix
21380 on 0.0.9.3; fixes bug 1222.
21382 o Minor bugfixes (bridges):
21383 - When a client starts or stops using bridges, never use a circuit
21384 that was built before the configuration change. This behavior could
21385 put at risk a user who uses bridges to ensure that her traffic
21386 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21388 - Do not reset the bridge descriptor download status every time we
21389 re-parse our configuration or get a configuration change. Fixes
21390 bug 3019; bugfix on 0.2.0.3-alpha.
21391 - Users couldn't configure a regular relay to be their bridge. It
21392 didn't work because when Tor fetched the bridge descriptor, it found
21393 that it already had it, and didn't realize that the purpose of the
21394 descriptor had changed. Now we replace routers with a purpose other
21395 than bridge with bridge descriptors when fetching them. Bugfix on
21396 0.1.1.9-alpha. Fixes bug 1776.
21397 - In the special case where you configure a public exit relay as your
21398 bridge, Tor would be willing to use that exit relay as the last
21399 hop in your circuit as well. Now we fail that circuit instead.
21400 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
21402 o Minor bugfixes (clients):
21403 - We now ask the other side of a stream (the client or the exit)
21404 for more data on that stream when the amount of queued data on
21405 that stream dips low enough. Previously, we wouldn't ask the
21406 other side for more data until either it sent us more data (which
21407 it wasn't supposed to do if it had exhausted its window!) or we
21408 had completely flushed all our queued data. This flow control fix
21409 should improve throughput. Fixes bug 2756; bugfix on the earliest
21410 released versions of Tor (svn commit r152).
21411 - When a client finds that an origin circuit has run out of 16-bit
21412 stream IDs, we now mark it as unusable for new streams. Previously,
21413 we would try to close the entire circuit. Bugfix on 0.0.6.
21414 - Make it explicit that we don't cannibalize one-hop circuits. This
21415 happens in the wild, but doesn't turn out to be a problem because
21416 we fortunately don't use those circuits. Many thanks to outofwords
21417 for the initial analysis and to swissknife who confirmed that
21418 two-hop circuits are actually created.
21419 - Resolve an edge case in path weighting that could make us misweight
21420 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
21421 - Make the DNSPort option work with libevent 2.x. Don't alter the
21422 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
21424 o Minor bugfixes (directory authorities):
21425 - Make directory authorities more accurate at recording when
21426 relays that have failed several reachability tests became
21427 unreachable, so we can provide more accuracy at assigning Stable,
21428 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
21429 - Directory authorities are now more robust to hops back in time
21430 when calculating router stability. Previously, if a run of uptime
21431 or downtime appeared to be negative, the calculation could give
21432 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
21434 - Directory authorities will now attempt to download consensuses
21435 if their own efforts to make a live consensus have failed. This
21436 change means authorities that restart will fetch a valid
21437 consensus, and it means authorities that didn't agree with the
21438 current consensus will still fetch and serve it if it has enough
21439 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
21440 - Never vote for a server as "Running" if we have a descriptor for
21441 it claiming to be hibernating, and that descriptor was published
21442 more recently than our last contact with the server. Bugfix on
21443 0.2.0.3-alpha; fixes bug 911.
21444 - Directory authorities no longer change their opinion of, or vote on,
21445 whether a router is Running, unless they have themselves been
21446 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
21449 o Minor bugfixes (hidden services):
21450 - Log malformed requests for rendezvous descriptors as protocol
21451 warnings, not warnings. Also, use a more informative log message
21452 in case someone sees it at log level warning without prior
21453 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
21454 - Accept hidden service descriptors if we think we might be a hidden
21455 service directory, regardless of what our consensus says. This
21456 helps robustness, since clients and hidden services can sometimes
21457 have a more up-to-date view of the network consensus than we do,
21458 and if they think that the directory authorities list us a HSDir,
21459 we might actually be one. Related to bug 2732; bugfix on
21461 - Correct the warning displayed when a rendezvous descriptor exceeds
21462 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21464 - Clients and hidden services now use HSDir-flagged relays for hidden
21465 service descriptor downloads and uploads even if the relays have no
21466 DirPort set and the client has disabled TunnelDirConns. This will
21467 eventually allow us to give the HSDir flag to relays with no
21468 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
21469 - Only limit the lengths of single HS descriptors, even when multiple
21470 HS descriptors are published to an HSDir relay in a single POST
21471 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
21473 o Minor bugfixes (controllers):
21474 - Allow GETINFO fingerprint to return a fingerprint even when
21475 we have not yet built a router descriptor. Fixes bug 3577;
21476 bugfix on 0.2.0.1-alpha.
21477 - Send a SUCCEEDED stream event to the controller when a reverse
21478 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21479 discovered by katmagic.
21480 - Remove a trailing asterisk from "exit-policy/default" in the
21481 output of the control port command "GETINFO info/names". Bugfix
21483 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
21484 2917. Bugfix on 0.1.1.1-alpha.
21485 - When we restart our relay, we might get a successful connection
21486 from the outside before we've started our reachability tests,
21487 triggering a warning: "ORPort found reachable, but I have no
21488 routerinfo yet. Failing to inform controller of success." This
21489 bug was harmless unless Tor is running under a controller
21490 like Vidalia, in which case the controller would never get a
21491 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21493 - When a controller changes TrackHostExits, remove mappings for
21494 hosts that should no longer have their exits tracked. Bugfix on
21496 - When a controller changes VirtualAddrNetwork, remove any mappings
21497 for hosts that were automapped to the old network. Bugfix on
21499 - When a controller changes one of the AutomapHosts* options, remove
21500 any mappings for hosts that should no longer be automapped. Bugfix
21502 - Fix an off-by-one error in calculating some controller command
21503 argument lengths. Fortunately, this mistake is harmless since
21504 the controller code does redundant NUL termination too. Found by
21505 boboper. Bugfix on 0.1.1.1-alpha.
21506 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
21507 would return "551 Internal error" rather than "552 Unrecognized key
21508 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
21509 - Don't spam the controller with events when we have no file
21510 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
21511 for log messages was already solved from bug 748.)
21512 - Emit a GUARD DROPPED controller event for a case we missed.
21513 - Ensure DNS requests launched by "RESOLVE" commands from the
21514 controller respect the __LeaveStreamsUnattached setconf options. The
21515 same goes for requests launched via DNSPort or transparent
21516 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
21518 o Minor bugfixes (config options):
21519 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21520 Change the limit to 512 characters by removing base64 newlines.
21521 Fixes bug 2752. Fix by Michael Yakubovich.
21522 - Complain if PublishServerDescriptor is given multiple arguments that
21523 include 0 or 1. This configuration will be rejected in the future.
21524 Bugfix on 0.2.0.1-alpha; closes bug 1107.
21525 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
21526 Bugfix on 0.2.0.13-alpha; closes bug 928.
21528 o Minor bugfixes (log subsystem fixes):
21529 - When unable to format an address as a string, report its value
21530 as "???" rather than reusing the last formatted address. Bugfix
21532 - Be more consistent in our treatment of file system paths. "~" should
21533 get expanded to the user's home directory in the Log config option.
21534 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
21535 feature for the -f and --DataDirectory options.
21537 o Minor bugfixes (memory management):
21538 - Don't stack-allocate the list of supplementary GIDs when we're
21539 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21540 could take up to 256K, which is way too much stack. Found by
21541 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21542 - Save a couple bytes in memory allocation every time we escape
21543 certain characters in a string. Patch from Florian Zumbiehl.
21545 o Minor bugfixes (protocol correctness):
21546 - When checking for 1024-bit keys, check for 1024 bits, not 128
21547 bytes. This allows Tor to correctly discard keys of length 1017
21548 through 1023. Bugfix on 0.0.9pre5.
21549 - Require that introduction point keys and onion handshake keys
21550 have a public exponent of 65537. Starts to fix bug 3207; bugfix
21552 - Handle SOCKS messages longer than 128 bytes long correctly, rather
21553 than waiting forever for them to finish. Fixes bug 2330; bugfix
21554 on 0.2.0.16-alpha. Found by doorss.
21555 - Never relay a cell for a circuit we have already destroyed.
21556 Between marking a circuit as closeable and finally closing it,
21557 it may have been possible for a few queued cells to get relayed,
21558 even though they would have been immediately dropped by the next
21559 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
21560 - Never queue a cell for a circuit that's already been marked
21562 - Fix a spec conformance issue: the network-status-version token
21563 must be the first token in a v3 consensus or vote. Discovered by
21564 "parakeep". Bugfix on 0.2.0.3-alpha.
21565 - A networkstatus vote must contain exactly one signature. Spec
21566 conformance issue. Bugfix on 0.2.0.3-alpha.
21567 - When asked about a DNS record type we don't support via a
21568 client DNSPort, reply with NOTIMPL rather than an empty
21569 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21570 - Make more fields in the controller protocol case-insensitive, since
21571 control-spec.txt said they were.
21573 o Minor bugfixes (log messages):
21574 - Fix a log message that said "bits" while displaying a value in
21575 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21577 - Downgrade "no current certificates known for authority" message from
21578 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
21579 - Correctly describe errors that occur when generating a TLS object.
21580 Previously we would attribute them to a failure while generating a
21581 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
21583 - Fix an instance where a Tor directory mirror might accidentally
21584 log the IP address of a misbehaving Tor client. Bugfix on
21586 - Stop logging at severity 'warn' when some other Tor client tries
21587 to establish a circuit with us using weak DH keys. It's a protocol
21588 violation, but that doesn't mean ordinary users need to hear about
21589 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
21590 - If your relay can't keep up with the number of incoming create
21591 cells, it would log one warning per failure into your logs. Limit
21592 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
21594 o Minor bugfixes (build fixes):
21595 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21596 - When warning about missing zlib development packages during compile,
21597 give the correct package names. Bugfix on 0.2.0.1-alpha.
21598 - Fix warnings that newer versions of autoconf produce during
21599 ./autogen.sh. These warnings appear to be harmless in our case,
21600 but they were extremely verbose. Fixes bug 2020.
21601 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
21604 o Minor bugfixes (portability):
21605 - Write several files in text mode, on OSes that distinguish text
21606 mode from binary mode (namely, Windows). These files are:
21607 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21608 that collect those statistics; 'client_keys' and 'hostname' for
21609 hidden services that use authentication; and (in the tor-gencert
21610 utility) newly generated identity and signing keys. Previously,
21611 we wouldn't specify text mode or binary mode, leading to an
21612 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21613 the DirRecordUsageByCountry option which would have triggered
21614 the assertion failure was added), although this assertion failure
21615 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21616 - Selectively disable deprecation warnings on OS X because Lion
21617 started deprecating the shipped copy of openssl. Fixes bug 3643.
21618 - Use a wide type to hold sockets when built for 64-bit Windows.
21620 - Fix an issue that prevented static linking of libevent on
21621 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
21622 where we introduced the "--with-static-libevent" configure option.
21623 - Fix a bug with our locking implementation on Windows that couldn't
21624 correctly detect when a file was already locked. Fixes bug 2504,
21625 bugfix on 0.2.1.6-alpha.
21626 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
21628 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
21629 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
21632 o Minor bugfixes (code correctness):
21633 - Always NUL-terminate the sun_path field of a sockaddr_un before
21634 passing it to the kernel. (Not a security issue: kernels are
21635 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21636 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21637 - Make connection_printf_to_buf()'s behavior sane. Its callers
21638 expect it to emit a CRLF iff the format string ends with CRLF;
21639 it actually emitted a CRLF iff (a) the format string ended with
21640 CRLF or (b) the resulting string was over 1023 characters long or
21641 (c) the format string did not end with CRLF *and* the resulting
21642 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
21643 fixes part of bug 3407.
21644 - Make send_control_event_impl()'s behavior sane. Its callers
21645 expect it to always emit a CRLF at the end of the string; it
21646 might have emitted extra control characters as well. Bugfix on
21647 0.1.1.9-alpha; fixes another part of bug 3407.
21648 - Make crypto_rand_int() check the value of its input correctly.
21649 Previously, it accepted values up to UINT_MAX, but could return a
21650 negative number if given a value above INT_MAX+1. Found by George
21651 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21652 - Fix a potential null-pointer dereference while computing a
21653 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
21655 - If we fail to compute the identity digest of a v3 legacy keypair,
21656 warn, and don't use a buffer-full of junk instead. Bugfix on
21657 0.2.1.1-alpha; fixes bug 3106.
21658 - Resolve an untriggerable issue in smartlist_string_num_isin(),
21659 where if the function had ever in the future been used to check
21660 for the presence of a too-large number, it would have given an
21661 incorrect result. (Fortunately, we only used it for 16-bit
21662 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
21663 - Be more careful about reporting the correct error from a failed
21664 connect() system call. Under some circumstances, it was possible to
21665 look at an incorrect value for errno when sending the end reason.
21666 Bugfix on 0.1.0.1-rc.
21667 - Correctly handle an "impossible" overflow cases in connection byte
21668 counting, where we write or read more than 4GB on an edge connection
21669 in a single second. Bugfix on 0.1.2.8-beta.
21670 - Avoid a double mark-for-free warning when failing to attach a
21671 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
21673 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
21674 found by "cypherpunks". This bug was introduced before the first
21675 Tor release, in svn commit r110.
21676 - Fix a bug in bandwidth history state parsing that could have been
21677 triggered if a future version of Tor ever changed the timing
21678 granularity at which bandwidth history is measured. Bugfix on
21679 Tor 0.1.1.11-alpha.
21680 - Add assertions to check for overflow in arguments to
21681 base32_encode() and base32_decode(); fix a signed-unsigned
21682 comparison there too. These bugs are not actually reachable in Tor,
21683 but it's good to prevent future errors too. Found by doorss.
21684 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
21686 - Set target port in get_interface_address6() correctly. Bugfix
21687 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
21688 - Fix an impossible-to-actually-trigger buffer overflow in relay
21689 descriptor generation. Bugfix on 0.1.0.15.
21690 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
21692 o Minor bugfixes (code improvements):
21693 - After we free an internal connection structure, overwrite it
21694 with a different memory value than we use for overwriting a freed
21695 internal circuit structure. Should help with debugging. Suggested
21697 - If OpenSSL fails to make a duplicate of a private or public key, log
21698 an error message and try to exit cleanly. May help with debugging
21699 if bug 1209 ever remanifests.
21700 - Some options used different conventions for uppercasing of acronyms
21701 when comparing manpage and source. Fix those in favor of the
21702 manpage, as it makes sense to capitalize acronyms.
21703 - Take a first step towards making or.h smaller by splitting out
21704 function definitions for all source files in src/or/. Leave
21705 structures and defines in or.h for now.
21706 - Remove a few dead assignments during router parsing. Found by
21708 - Don't use 1-bit wide signed bit fields. Found by coverity.
21709 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21710 None of the cases where we did this before were wrong, but by making
21711 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21712 - The memarea code now uses a sentinel value at the end of each area
21713 to make sure nothing writes beyond the end of an area. This might
21714 help debug some conceivable causes of bug 930.
21715 - Always treat failure to allocate an RSA key as an unrecoverable
21717 - Add some more defensive programming for architectures that can't
21718 handle unaligned integer accesses. We don't know of any actual bugs
21719 right now, but that's the best time to fix them. Fixes bug 1943.
21721 o Minor bugfixes (misc):
21722 - Fix a rare bug in rend_fn unit tests: we would fail a test when
21723 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
21724 on 0.2.0.10-alpha; fixes bug 1808.
21725 - Where available, use Libevent 2.0's periodic timers so that our
21726 once-per-second cleanup code gets called even more closely to
21727 once per second than it would otherwise. Fixes bug 943.
21728 - Ignore OutboundBindAddress when connecting to localhost.
21729 Connections to localhost need to come _from_ localhost, or else
21730 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
21732 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
21734 - If any of the v3 certs we download are unparseable, we should
21735 actually notice the failure so we don't retry indefinitely. Bugfix
21736 on 0.2.0.x; reported by "rotator".
21737 - When Tor fails to parse a descriptor of any kind, dump it to disk.
21738 Might help diagnosing bug 1051.
21739 - Make our 'torify' script more portable; if we have only one of
21740 'torsocks' or 'tsocks' installed, don't complain to the user;
21741 and explain our warning about tsocks better.
21742 - Fix some urls in the exit notice file and make it XHTML1.1 strict
21743 compliant. Based on a patch from Christian Kujau.
21745 o Documentation changes:
21746 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
21747 - Resolve all doxygen warnings except those for missing documentation.
21749 - Add doxygen documentation for more functions, fields, and types.
21750 - Convert the HACKING file to asciidoc, and add a few new sections
21751 to it, explaining how we use Git, how we make changelogs, and
21752 what should go in a patch.
21753 - Document the default socks host and port (127.0.0.1:9050) for
21755 - Removed some unnecessary files from the source distribution. The
21756 AUTHORS file has now been merged into the people page on the
21757 website. The roadmaps and design doc can now be found in the
21758 projects directory in svn.
21760 o Deprecated and removed features (config):
21761 - Remove the torrc.complete file. It hasn't been kept up to date
21762 and users will have better luck checking out the manpage.
21763 - Remove the HSAuthorityRecordStats option that version 0 hidden
21764 service authorities could use to track statistics of overall v0
21765 hidden service usage.
21766 - Remove the obsolete "NoPublish" option; it has been flagged
21767 as obsolete and has produced a warning since 0.1.1.18-rc.
21768 - Caches no longer download and serve v2 networkstatus documents
21769 unless FetchV2Networkstatus flag is set: these documents haven't
21770 haven't been used by clients or relays since 0.2.0.x. Resolves
21773 o Deprecated and removed features (controller):
21774 - The controller no longer accepts the old obsolete "addr-mappings/"
21775 or "unregistered-servers-" GETINFO values.
21776 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
21777 always on; using them is necessary for correct forward-compatible
21780 o Deprecated and removed features (misc):
21781 - Hidden services no longer publish version 0 descriptors, and clients
21782 do not request or use version 0 descriptors. However, the old hidden
21783 service authorities still accept and serve version 0 descriptors
21784 when contacted by older hidden services/clients.
21785 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21786 anything since 0.2.1.16-rc.
21787 - Remove everything related to building the expert bundle for OS X.
21788 It has confused many users, doesn't work right on OS X 10.6,
21789 and is hard to get rid of once installed. Resolves bug 1274.
21790 - Remove support for .noconnect style addresses. Nobody was using
21791 them, and they provided another avenue for detecting Tor users
21792 via application-level web tricks.
21793 - When we fixed bug 1038 we had to put in a restriction not to send
21794 RELAY_EARLY cells on rend circuits. This was necessary as long
21795 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
21796 active. Now remove this obsolete check. Resolves bug 2081.
21797 - Remove workaround code to handle directory responses from servers
21798 that had bug 539 (they would send HTTP status 503 responses _and_
21799 send a body too). Since only server versions before
21800 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
21801 keep the workaround in place.
21802 - Remove the old 'fuzzy time' logic. It was supposed to be used for
21803 handling calculations where we have a known amount of clock skew and
21804 an allowed amount of unknown skew. But we only used it in three
21805 places, and we never adjusted the known/unknown skew values. This is
21806 still something we might want to do someday, but if we do, we'll
21807 want to do it differently.
21808 - Remove the "--enable-iphone" option to ./configure. According to
21809 reports from Marco Bonetti, Tor builds fine without any special
21810 tweaking on recent iPhone SDK versions.
21813 Changes in version 0.2.1.30 - 2011-02-23
21814 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
21815 change is a slight tweak to Tor's TLS handshake that makes relays
21816 and bridges that run this new version reachable from Iran again.
21817 We don't expect this tweak will win the arms race long-term, but it
21818 buys us time until we roll out a better solution.
21821 - Stop sending a CLOCK_SKEW controller status event whenever
21822 we fetch directory information from a relay that has a wrong clock.
21823 Instead, only inform the controller when it's a trusted authority
21824 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21825 the rest of bug 1074.
21826 - Fix a bounds-checking error that could allow an attacker to
21827 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21828 Found by "piebeer".
21829 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21830 Tor would ignore their RelayBandwidthBurst setting,
21831 potentially using more bandwidth than expected. Bugfix on
21832 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21833 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21834 hidserv" in her torrc. The 'hidserv' argument never controlled
21835 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21838 - Adjust our TLS Diffie-Hellman parameters to match those used by
21840 - Update to the February 1 2011 Maxmind GeoLite Country database.
21843 - Check for and reject overly long directory certificates and
21844 directory tokens before they have a chance to hit any assertions.
21845 Bugfix on 0.2.1.28. Found by "doorss".
21846 - Bring the logic that gathers routerinfos and assesses the
21847 acceptability of circuits into line. This prevents a Tor OP from
21848 getting locked in a cycle of choosing its local OR as an exit for a
21849 path (due to a .exit request) and then rejecting the circuit because
21850 its OR is not listed yet. It also prevents Tor clients from using an
21851 OR running in the same instance as an exit (due to a .exit request)
21852 if the OR does not meet the same requirements expected of an OR
21853 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21855 o Packaging changes:
21856 - Stop shipping the Tor specs files and development proposal documents
21857 in the tarball. They are now in a separate git repository at
21858 git://git.torproject.org/torspec.git
21859 - Do not include Git version tags as though they are SVN tags when
21860 generating a tarball from inside a repository that has switched
21861 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21864 Changes in version 0.2.1.29 - 2011-01-15
21865 Tor 0.2.1.29 continues our recent code security audit work. The main
21866 fix resolves a remote heap overflow vulnerability that can allow remote
21867 code execution. Other fixes address a variety of assert and crash bugs,
21868 most of which we think are hard to exploit remotely.
21870 o Major bugfixes (security):
21871 - Fix a heap overflow bug where an adversary could cause heap
21872 corruption. This bug probably allows remote code execution
21873 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21875 - Prevent a denial-of-service attack by disallowing any
21876 zlib-compressed data whose compression factor is implausibly
21877 high. Fixes part of bug 2324; reported by "doorss".
21878 - Zero out a few more keys in memory before freeing them. Fixes
21879 bug 2384 and part of bug 2385. These key instances found by
21880 "cypherpunks", based on Andrew Case's report about being able
21881 to find sensitive data in Tor's memory space if you have enough
21882 permissions. Bugfix on 0.0.2pre9.
21884 o Major bugfixes (crashes):
21885 - Prevent calls to Libevent from inside Libevent log handlers.
21886 This had potential to cause a nasty set of crashes, especially
21887 if running Libevent with debug logging enabled, and running
21888 Tor with a controller watching for low-severity log messages.
21889 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21890 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21891 underflow errors there too. Fixes the other part of bug 2324.
21892 - Fix a bug where we would assert if we ever had a
21893 cached-descriptors.new file (or another file read directly into
21894 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21895 on 0.2.1.25. Found by doorss.
21896 - Fix some potential asserts and parsing issues with grossly
21897 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21900 o Minor bugfixes (other):
21901 - Fix a bug with handling misformed replies to reverse DNS lookup
21902 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21903 bug reported by doorss.
21904 - Fix compilation on mingw when a pthreads compatibility library
21905 has been installed. (We don't want to use it, so we shouldn't
21906 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21907 - Fix a bug where we would declare that we had run out of virtual
21908 addresses when the address space was only half-exhausted. Bugfix
21910 - Correctly handle the case where AutomapHostsOnResolve is set but
21911 no virtual addresses are available. Fixes bug 2328; bugfix on
21912 0.1.2.1-alpha. Bug found by doorss.
21913 - Correctly handle wrapping around when we run out of virtual
21914 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
21917 - Update to the January 1 2011 Maxmind GeoLite Country database.
21918 - Introduce output size checks on all of our decryption functions.
21921 - Tor does not build packages correctly with Automake 1.6 and earlier;
21922 added a check to Makefile.am to make sure that we're building with
21923 Automake 1.7 or later.
21924 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21925 because we built it with a too-old version of automake. Thus that
21926 release broke ./configure --enable-openbsd-malloc, which is popular
21927 among really fast exit relays on Linux.
21930 Changes in version 0.2.1.28 - 2010-12-17
21931 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
21932 exploitable bugs. We also took this opportunity to change the IP address
21933 for one of our directory authorities, and to update the geoip database
21937 - Fix a remotely exploitable bug that could be used to crash instances
21938 of Tor remotely by overflowing on the heap. Remote-code execution
21939 hasn't been confirmed, but can't be ruled out. Everyone should
21940 upgrade. Bugfix on the 0.1.1 series and later.
21942 o Directory authority changes:
21943 - Change IP address and ports for gabelmoo (v3 directory authority).
21946 - Update to the December 1 2010 Maxmind GeoLite Country database.
21949 Changes in version 0.2.1.27 - 2010-11-23
21950 Yet another OpenSSL security patch broke its compatibility with Tor:
21951 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
21952 also took this opportunity to fix several crash bugs, integrate a new
21953 directory authority, and update the bundled GeoIP database.
21956 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21957 No longer set the tlsext_host_name extension on server SSL objects;
21958 but continue to set it on client SSL objects. Our goal in setting
21959 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21960 bugfix on 0.2.1.1-alpha.
21961 - Do not log messages to the controller while shrinking buffer
21962 freelists. Doing so would sometimes make the controller connection
21963 try to allocate a buffer chunk, which would mess up the internals
21964 of the freelist and cause an assertion failure. Fixes bug 1125;
21965 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21966 - Learn our external IP address when we're a relay or bridge, even if
21967 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21968 where we introduced bridge relays that don't need to publish to
21969 be useful. Fixes bug 2050.
21970 - Do even more to reject (and not just ignore) annotations on
21971 router descriptors received anywhere but from the cache. Previously
21972 we would ignore such annotations at first, but cache them to disk
21973 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21974 - When you're using bridges and your network goes away and your
21975 bridges get marked as down, recover when you attempt a new socks
21976 connection (if the network is back), rather than waiting up to an
21977 hour to try fetching new descriptors for your bridges. Bugfix on
21978 0.2.0.3-alpha; fixes bug 1981.
21981 - Move to the November 2010 Maxmind GeoLite country db (rather
21982 than the June 2009 ip-to-country GeoIP db) for our statistics that
21983 count how many users relays are seeing from each country. Now we'll
21984 have more accurate data, especially for many African countries.
21986 o New directory authorities:
21987 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
21991 - Fix an assertion failure that could occur in directory caches or
21992 bridge users when using a very short voting interval on a testing
21993 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
21995 - Enforce multiplicity rules when parsing annotations. Bugfix on
21996 0.2.0.8-alpha. Found by piebeer.
21997 - Allow handshaking OR connections to take a full KeepalivePeriod
21998 seconds to handshake. Previously, we would close them after
21999 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22000 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22002 - When building with --enable-gcc-warnings on OpenBSD, disable
22003 warnings in system headers. This makes --enable-gcc-warnings
22004 pass on OpenBSD 4.8.
22007 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22008 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22009 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22010 Servers can start sending this code when enough clients recognize
22011 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22012 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22013 Patch from mingw-san.
22016 - Remove the old debian/ directory from the main Tor distribution.
22017 The official Tor-for-debian git repository lives at the URL
22018 https://git.torproject.org/debian/tor.git
22019 - Stop shipping the old doc/website/ directory in the tarball. We
22020 changed the website format in late 2010, and what we shipped in
22021 0.2.1.26 really wasn't that useful anyway.
22024 Changes in version 0.2.1.26 - 2010-05-02
22025 Tor 0.2.1.26 addresses the recent connection and memory overload
22026 problems we've been seeing on relays, especially relays with their
22027 DirPort open. If your relay has been crashing, or you turned it off
22028 because it used too many resources, give this release a try.
22030 This release also fixes yet another instance of broken OpenSSL libraries
22031 that was causing some relays to drop out of the consensus.
22034 - Teach relays to defend themselves from connection overload. Relays
22035 now close idle circuits early if it looks like they were intended
22036 for directory fetches. Relays are also more aggressive about closing
22037 TLS connections that have no circuits on them. Such circuits are
22038 unlikely to be re-used, and tens of thousands of them were piling
22039 up at the fast relays, causing the relays to run out of sockets
22040 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22041 their directory fetches over TLS).
22042 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22043 that claim to be earlier than 0.9.8m, but which have in reality
22044 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22045 behavior. Possible fix for some cases of bug 1346.
22046 - Directory mirrors were fetching relay descriptors only from v2
22047 directory authorities, rather than v3 authorities like they should.
22048 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22049 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22052 - Finally get rid of the deprecated and now harmful notion of "clique
22053 mode", where directory authorities maintain TLS connections to
22057 - In the util/threads test, no longer free the test_mutex before all
22058 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22059 - The master thread could starve the worker threads quite badly on
22060 certain systems, causing them to run only partially in the allowed
22061 window. This resulted in test failures. Now the master thread sleeps
22062 occasionally for a few microseconds while the two worker-threads
22063 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22066 Changes in version 0.2.1.25 - 2010-03-16
22067 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
22068 prevent relays from guessing their IP address correctly. It also fixes
22069 several minor potential security bugs.
22072 - Fix a regression from our patch for bug 1244 that caused relays
22073 to guess their IP address incorrectly if they didn't set Address
22074 in their torrc and/or their address fails to resolve. Bugfix on
22075 0.2.1.23; fixes bug 1269.
22076 - When freeing a session key, zero it out completely. We only zeroed
22077 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
22078 patched by ekir. Fixes bug 1254.
22081 - Fix a dereference-then-NULL-check sequence when publishing
22082 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
22084 - Fix another dereference-then-NULL-check sequence. Bugfix on
22085 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
22086 - Make sure we treat potentially not NUL-terminated strings correctly.
22087 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
22090 Changes in version 0.2.1.24 - 2010-02-21
22091 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
22095 - Work correctly out-of-the-box with even more vendor-patched versions
22096 of OpenSSL. In particular, make it so Debian and OS X don't need
22097 customized patches to run/build.
22100 Changes in version 0.2.1.23 - 2010-02-13
22101 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
22102 again on the latest OS X, and updates the location of a directory
22105 o Major bugfixes (performance):
22106 - We were selecting our guards uniformly at random, and then weighting
22107 which of our guards we'd use uniformly at random. This imbalance
22108 meant that Tor clients were severely limited on throughput (and
22109 probably latency too) by the first hop in their circuit. Now we
22110 select guards weighted by currently advertised bandwidth. We also
22111 automatically discard guards picked using the old algorithm. Fixes
22112 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22115 - Make Tor work again on the latest OS X: when deciding whether to
22116 use strange flags to turn TLS renegotiation on, detect the OpenSSL
22117 version at run-time, not compile time. We need to do this because
22118 Apple doesn't update its dev-tools headers when it updates its
22119 libraries in a security patch.
22120 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
22121 that could happen on 32-bit platforms with 64-bit time_t. Also fix
22122 a memory leak when requesting a hidden service descriptor we've
22123 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
22127 - Refactor resolve_my_address() to not use gethostbyname() anymore.
22128 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
22131 - Avoid a mad rush at the beginning of each month when each client
22132 rotates half of its guards. Instead we spread the rotation out
22133 throughout the month, but we still avoid leaving a precise timestamp
22134 in the state file about when we first picked the guard. Improves
22135 over the behavior introduced in 0.1.2.17.
22138 Changes in version 0.2.1.22 - 2010-01-19
22139 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
22140 authorities -- it would tell you its whole history of bridge descriptors
22141 if you make the right directory request. This stable update also
22142 rotates two of the seven v3 directory authority keys and locations.
22144 o Directory authority changes:
22145 - Rotate keys (both v3 identity and relay identity) for moria1
22149 - Stop bridge directory authorities from answering dbg-stability.txt
22150 directory queries, which would let people fetch a list of all
22151 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22154 Changes in version 0.2.1.21 - 2009-12-21
22155 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
22156 library. If you use Tor on Linux / Unix and you're getting SSL
22157 renegotiation errors, upgrading should help. We also recommend an
22158 upgrade if you're an exit relay.
22161 - Work around a security feature in OpenSSL 0.9.8l that prevents our
22162 handshake from working unless we explicitly tell OpenSSL that we
22163 are using SSL renegotiation safely. We are, of course, but OpenSSL
22164 0.9.8l won't work unless we say we are.
22165 - Avoid crashing if the client is trying to upload many bytes and the
22166 circuit gets torn down at the same time, or if the flip side
22167 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
22170 - Do not refuse to learn about authority certs and v2 networkstatus
22171 documents that are older than the latest consensus. This bug might
22172 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
22173 Spotted and fixed by xmux.
22174 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
22175 trigger platform-specific option misparsing case found by Coverity
22177 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
22178 trigger assert. Fixes bug 1173.
22181 Changes in version 0.2.1.20 - 2009-10-15
22182 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
22183 services at once, prepares for more performance improvements, and
22184 fixes a bunch of smaller bugs.
22186 The Windows and OS X bundles also include a more recent Vidalia,
22187 and switch from Privoxy to Polipo.
22189 The OS X installers are now drag and drop. It's best to un-install
22190 Tor/Vidalia and then install this new bundle, rather than upgrade. If
22191 you want to upgrade, you'll need to update the paths for Tor and Polipo
22192 in the Vidalia Settings window.
22195 - Send circuit or stream sendme cells when our window has decreased
22196 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
22197 by Karsten when testing the "reduce circuit window" performance
22198 patch. Bugfix on the 54th commit on Tor -- from July 2002,
22199 before the release of Tor 0.0.0. This is the new winner of the
22201 - Fix a remotely triggerable memory leak when a consensus document
22202 contains more than one signature from the same voter. Bugfix on
22204 - Avoid segfault in rare cases when finishing an introduction circuit
22205 as a client and finding out that we don't have an introduction key
22206 for it. Fixes bug 1073. Reported by Aaron Swartz.
22209 - Tor now reads the "circwindow" parameter out of the consensus,
22210 and uses that value for its circuit package window rather than the
22211 default of 1000 cells. Begins the implementation of proposal 168.
22213 o New directory authorities:
22214 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
22216 - Move moria1 and tonga to alternate IP addresses.
22219 - Fix a signed/unsigned compile warning in 0.2.1.19.
22220 - Fix possible segmentation fault on directory authorities. Bugfix on
22222 - Fix an extremely rare infinite recursion bug that could occur if
22223 we tried to log a message after shutting down the log subsystem.
22224 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
22225 - Fix an obscure bug where hidden services on 64-bit big-endian
22226 systems might mis-read the timestamp in v3 introduce cells, and
22227 refuse to connect back to the client. Discovered by "rotor".
22228 Bugfix on 0.2.1.6-alpha.
22229 - We were triggering a CLOCK_SKEW controller status event whenever
22230 we connect via the v2 connection protocol to any relay that has
22231 a wrong clock. Instead, we should only inform the controller when
22232 it's a trusted authority that claims our clock is wrong. Bugfix
22233 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
22234 - We were telling the controller about CHECKING_REACHABILITY and
22235 REACHABILITY_FAILED status events whenever we launch a testing
22236 circuit or notice that one has failed. Instead, only tell the
22237 controller when we want to inform the user of overall success or
22238 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
22240 - Don't warn when we're using a circuit that ends with a node
22241 excluded in ExcludeExitNodes, but the circuit is not used to access
22242 the outside world. This should help fix bug 1090. Bugfix on
22244 - Work around a small memory leak in some versions of OpenSSL that
22245 stopped the memory used by the hostname TLS extension from being
22249 - Add a "getinfo status/accepted-server-descriptor" controller
22250 command, which is the recommended way for controllers to learn
22251 whether our server descriptor has been successfully received by at
22252 least on directory authority. Un-recommend good-server-descriptor
22253 getinfo and status events until we have a better design for them.
22256 Changes in version 0.2.1.19 - 2009-07-28
22257 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
22261 - Make accessing hidden services on 0.2.1.x work right again.
22262 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
22263 part of patch provided by "optimist".
22266 - When a relay/bridge is writing out its identity key fingerprint to
22267 the "fingerprint" file and to its logs, write it without spaces. Now
22268 it will look like the fingerprints in our bridges documentation,
22269 and confuse fewer users.
22272 - Relays no longer publish a new server descriptor if they change
22273 their MaxAdvertisedBandwidth config option but it doesn't end up
22274 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
22275 fixes bug 1026. Patch from Sebastian.
22276 - Avoid leaking memory every time we get a create cell but we have
22277 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
22278 fixes bug 1034. Reported by BarkerJr.
22281 Changes in version 0.2.1.18 - 2009-07-24
22282 Tor 0.2.1.18 lays the foundations for performance improvements,
22283 adds status events to help users diagnose bootstrap problems, adds
22284 optional authentication/authorization for hidden services, fixes a
22285 variety of potential anonymity problems, and includes a huge pile of
22286 other features and bug fixes.
22288 o Major features (clients):
22289 - Start sending "bootstrap phase" status events to the controller,
22290 so it can keep the user informed of progress fetching directory
22291 information and establishing circuits. Also inform the controller
22292 if we think we're stuck at a particular bootstrap phase. Implements
22294 - Clients replace entry guards that were chosen more than a few months
22295 ago. This change should significantly improve client performance,
22296 especially once more people upgrade, since relays that have been
22297 a guard for a long time are currently overloaded.
22298 - Network status consensus documents and votes now contain bandwidth
22299 information for each relay. Clients use the bandwidth values
22300 in the consensus, rather than the bandwidth values in each
22301 relay descriptor. This approach opens the door to more accurate
22302 bandwidth estimates once the directory authorities start doing
22303 active measurements. Implements part of proposal 141.
22305 o Major features (relays):
22306 - Disable and refactor some debugging checks that forced a linear scan
22307 over the whole server-side DNS cache. These accounted for over 50%
22308 of CPU time on a relatively busy exit node's gprof profile. Also,
22309 disable some debugging checks that appeared in exit node profile
22310 data. Found by Jacob.
22311 - New DirPortFrontPage option that takes an html file and publishes
22312 it as "/" on the DirPort. Now relay operators can provide a
22313 disclaimer without needing to set up a separate webserver. There's
22314 a sample disclaimer in contrib/tor-exit-notice.html.
22316 o Major features (hidden services):
22317 - Make it possible to build hidden services that only certain clients
22318 are allowed to connect to. This is enforced at several points,
22319 so that unauthorized clients are unable to send INTRODUCE cells
22320 to the service, or even (depending on the type of authentication)
22321 to learn introduction points. This feature raises the bar for
22322 certain kinds of active attacks against hidden services. Design
22323 and code by Karsten Loesing. Implements proposal 121.
22324 - Relays now store and serve v2 hidden service descriptors by default,
22325 i.e., the new default value for HidServDirectoryV2 is 1. This is
22326 the last step in proposal 114, which aims to make hidden service
22327 lookups more reliable.
22329 o Major features (path selection):
22330 - ExitNodes and Exclude*Nodes config options now allow you to restrict
22331 by country code ("{US}") or IP address or address pattern
22332 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
22333 refinement to decide what config options should take priority if
22334 you ask to both use a particular node and exclude it.
22336 o Major features (misc):
22337 - When building a consensus, do not include routers that are down.
22338 This cuts down 30% to 40% on consensus size. Implements proposal
22340 - New TestingTorNetwork config option to allow adjustment of
22341 previously constant values that could slow bootstrapping. Implements
22342 proposal 135. Patch from Karsten.
22343 - Convert many internal address representations to optionally hold
22344 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
22345 elements. Make resolver code handle nameservers located at IPv6
22347 - More work on making our TLS handshake blend in: modify the list
22348 of ciphers advertised by OpenSSL in client mode to even more
22349 closely resemble a common web browser. We cheat a little so that
22350 we can advertise ciphers that the locally installed OpenSSL doesn't
22352 - Use the TLS1 hostname extension to more closely resemble browser
22355 o Security fixes (anonymity/entropy):
22356 - Never use a connection with a mismatched address to extend a
22357 circuit, unless that connection is canonical. A canonical
22358 connection is one whose address is authenticated by the router's
22359 identity key, either in a NETINFO cell or in a router descriptor.
22360 - Implement most of proposal 110: The first K cells to be sent
22361 along a circuit are marked as special "early" cells; only K "early"
22362 cells will be allowed. Once this code is universal, we can block
22363 certain kinds of denial-of-service attack by requiring that EXTEND
22364 commands must be sent using an "early" cell.
22365 - Resume using OpenSSL's RAND_poll() for better (and more portable)
22366 cross-platform entropy collection again. We used to use it, then
22367 stopped using it because of a bug that could crash systems that
22368 called RAND_poll when they had a lot of fds open. It looks like the
22369 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
22370 at startup, and to call RAND_poll() when we reseed later only if
22371 we have a non-buggy OpenSSL version.
22372 - When the client is choosing entry guards, now it selects at most
22373 one guard from a given relay family. Otherwise we could end up with
22374 all of our entry points into the network run by the same operator.
22375 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
22376 - Do not use or believe expired v3 authority certificates. Patch
22377 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
22378 - Drop begin cells to a hidden service if they come from the middle
22379 of a circuit. Patch from lark.
22380 - When we erroneously receive two EXTEND cells for the same circuit
22381 ID on the same connection, drop the second. Patch from lark.
22382 - Authorities now vote for the Stable flag for any router whose
22383 weighted MTBF is at least 5 days, regardless of the mean MTBF.
22384 - Clients now never report any stream end reason except 'MISC'.
22385 Implements proposal 148.
22387 o Major bugfixes (crashes):
22388 - Parse dates and IPv4 addresses in a locale- and libc-independent
22389 manner, to avoid platform-dependent behavior on malformed input.
22390 - Fix a crash that occurs on exit nodes when a nameserver request
22391 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
22392 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
22394 - Do not assume that a stack-allocated character array will be
22395 64-bit aligned on platforms that demand that uint64_t access is
22396 aligned. Possible fix for bug 604.
22397 - Resolve a very rare crash bug that could occur when the user forced
22398 a nameserver reconfiguration during the middle of a nameserver
22399 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
22400 - Avoid a "0 divided by 0" calculation when calculating router uptime
22401 at directory authorities. Bugfix on 0.2.0.8-alpha.
22402 - Fix an assertion bug in parsing policy-related options; possible fix
22404 - Rate-limit too-many-sockets messages: when they happen, they happen
22405 a lot and end up filling up the disk. Resolves bug 748.
22406 - Fix a race condition that could cause crashes or memory corruption
22407 when running as a server with a controller listening for log
22409 - Avoid crashing when we have a policy specified in a DirPolicy or
22410 SocksPolicy or ReachableAddresses option with ports set on it,
22411 and we re-load the policy. May fix bug 996.
22412 - Fix an assertion failure on 64-bit platforms when we allocated
22413 memory right up to the end of a memarea, then realigned the memory
22414 one step beyond the end. Fixes a possible cause of bug 930.
22415 - Protect the count of open sockets with a mutex, so we can't
22416 corrupt it when two threads are closing or opening sockets at once.
22417 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
22419 o Major bugfixes (clients):
22420 - Discard router descriptors as we load them if they are more than
22421 five days old. Otherwise if Tor is off for a long time and then
22422 starts with cached descriptors, it will try to use the onion keys
22423 in those obsolete descriptors when building circuits. Fixes bug 887.
22424 - When we choose to abandon a new entry guard because we think our
22425 older ones might be better, close any circuits pending on that
22426 new entry guard connection. This fix should make us recover much
22427 faster when our network is down and then comes back. Bugfix on
22428 0.1.2.8-beta; found by lodger.
22429 - When Tor clients restart after 1-5 days, they discard all their
22430 cached descriptors as too old, but they still use the cached
22431 consensus document. This approach is good for robustness, but
22432 bad for performance: since they don't know any bandwidths, they
22433 end up choosing at random rather than weighting their choice by
22434 speed. Fixed by the above feature of putting bandwidths in the
22437 o Major bugfixes (relays):
22438 - Relays were falling out of the networkstatus consensus for
22439 part of a day if they changed their local config but the
22440 authorities discarded their new descriptor as "not sufficiently
22441 different". Now directory authorities accept a descriptor as changed
22442 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
22443 patch by Sebastian.
22444 - Ensure that two circuits can never exist on the same connection
22445 with the same circuit ID, even if one is marked for close. This
22446 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
22447 - Directory authorities were neglecting to mark relays down in their
22448 internal histories if the relays fall off the routerlist without
22449 ever being found unreachable. So there were relays in the histories
22450 that haven't been seen for eight months, and are listed as being
22451 up for eight months. This wreaked havoc on the "median wfu" and
22452 "median mtbf" calculations, in turn making Guard and Stable flags
22453 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
22456 o Major bugfixes (hidden services):
22457 - When establishing a hidden service, introduction points that
22458 originate from cannibalized circuits were completely ignored
22459 and not included in rendezvous service descriptors. This might
22460 have been another reason for delay in making a hidden service
22461 available. Bugfix from long ago (0.0.9.x?)
22463 o Major bugfixes (memory and resource management):
22464 - Fixed some memory leaks -- some quite frequent, some almost
22465 impossible to trigger -- based on results from Coverity.
22466 - Speed up parsing and cut down on memory fragmentation by using
22467 stack-style allocations for parsing directory objects. Previously,
22468 this accounted for over 40% of allocations from within Tor's code
22469 on a typical directory cache.
22470 - Use a Bloom filter rather than a digest-based set to track which
22471 descriptors we need to keep around when we're cleaning out old
22472 router descriptors. This speeds up the computation significantly,
22473 and may reduce fragmentation.
22475 o New/changed config options:
22476 - Now NodeFamily and MyFamily config options allow spaces in
22477 identity fingerprints, so it's easier to paste them in.
22478 Suggested by Lucky Green.
22479 - Allow ports 465 and 587 in the default exit policy again. We had
22480 rejected them in 0.1.0.15, because back in 2005 they were commonly
22481 misconfigured and ended up as spam targets. We hear they are better
22482 locked down these days.
22483 - Make TrackHostExit mappings expire a while after their last use, not
22484 after their creation. Patch from Robert Hogan.
22485 - Add an ExcludeExitNodes option so users can list a set of nodes
22486 that should be be excluded from the exit node position, but
22487 allowed elsewhere. Implements proposal 151.
22488 - New --hush command-line option similar to --quiet. While --quiet
22489 disables all logging to the console on startup, --hush limits the
22490 output to messages of warning and error severity.
22491 - New configure/torrc options (--enable-geoip-stats,
22492 DirRecordUsageByCountry) to record how many IPs we've served
22493 directory info to in each country code, how many status documents
22494 total we've sent to each country code, and what share of the total
22495 directory requests we should expect to see.
22496 - Make outbound DNS packets respect the OutboundBindAddress setting.
22497 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
22498 - Allow separate log levels to be configured for different logging
22499 domains. For example, this allows one to log all notices, warnings,
22500 or errors, plus all memory management messages of level debug or
22501 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
22502 - Update to the "June 3 2009" ip-to-country file.
22504 o Minor features (relays):
22505 - Raise the minimum rate limiting to be a relay from 20000 bytes
22506 to 20480 bytes (aka 20KB/s), to match our documentation. Also
22507 update directory authorities so they always assign the Fast flag
22508 to relays with 20KB/s of capacity. Now people running relays won't
22509 suddenly find themselves not seeing any use, if the network gets
22511 - If we're a relay and we change our IP address, be more verbose
22512 about the reason that made us change. Should help track down
22513 further bugs for relays on dynamic IP addresses.
22514 - Exit servers can now answer resolve requests for ip6.arpa addresses.
22515 - Implement most of Proposal 152: allow specialized servers to permit
22516 single-hop circuits, and clients to use those servers to build
22517 single-hop circuits when using a specialized controller. Patch
22518 from Josh Albrecht. Resolves feature request 768.
22519 - When relays do their initial bandwidth measurement, don't limit
22520 to just our entry guards for the test circuits. Otherwise we tend
22521 to have multiple test circuits going through a single entry guard,
22522 which makes our bandwidth test less accurate. Fixes part of bug 654;
22523 patch contributed by Josh Albrecht.
22525 o Minor features (directory authorities):
22526 - Try not to open more than one descriptor-downloading connection
22527 to an authority at once. This should reduce load on directory
22528 authorities. Fixes bug 366.
22529 - Add cross-certification to newly generated certificates, so that
22530 a signing key is enough information to look up a certificate. Start
22531 serving certificates by <identity digest, signing key digest>
22532 pairs. Implements proposal 157.
22533 - When a directory authority downloads a descriptor that it then
22534 immediately rejects, do not retry downloading it right away. Should
22535 save some bandwidth on authorities. Fix for bug 888. Patch by
22537 - Directory authorities now serve a /tor/dbg-stability.txt URL to
22538 help debug WFU and MTBF calculations.
22539 - In directory authorities' approved-routers files, allow
22540 fingerprints with or without space.
22542 o Minor features (directory mirrors):
22543 - When a download gets us zero good descriptors, do not notify
22544 Tor that new directory information has arrived.
22545 - Servers support a new URL scheme for consensus downloads that
22546 allows the client to specify which authorities are trusted.
22547 The server then only sends the consensus if the client will trust
22548 it. Otherwise a 404 error is sent back. Clients use this
22549 new scheme when the server supports it (meaning it's running
22550 0.2.1.1-alpha or later). Implements proposal 134.
22552 o Minor features (bridges):
22553 - If the bridge config line doesn't specify a port, assume 443.
22554 This makes bridge lines a bit smaller and easier for users to
22556 - If we're using bridges and our network goes away, be more willing
22557 to forgive our bridges and try again when we get an application
22560 o Minor features (hidden services):
22561 - When the client launches an introduction circuit, retry with a
22562 new circuit after 30 seconds rather than 60 seconds.
22563 - Launch a second client-side introduction circuit in parallel
22564 after a delay of 15 seconds (based on work by Christian Wilms).
22565 - Hidden services start out building five intro circuits rather
22566 than three, and when the first three finish they publish a service
22567 descriptor using those. Now we publish our service descriptor much
22568 faster after restart.
22569 - Drop the requirement to have an open dir port for storing and
22570 serving v2 hidden service descriptors.
22572 o Minor features (build and packaging):
22573 - On Linux, use the prctl call to re-enable core dumps when the User
22575 - Try to make sure that the version of Libevent we're running with
22576 is binary-compatible with the one we built with. May address bug
22578 - Add a new --enable-local-appdata configuration switch to change
22579 the default location of the datadir on win32 from APPDATA to
22580 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
22581 entirely. Patch from coderman.
22582 - Build correctly against versions of OpenSSL 0.9.8 or later that
22583 are built without support for deprecated functions.
22584 - On platforms with a maximum syslog string length, truncate syslog
22585 messages to that length ourselves, rather than relying on the
22586 system to do it for us.
22587 - Automatically detect MacOSX versions earlier than 10.4.0, and
22588 disable kqueue from inside Tor when running with these versions.
22589 We previously did this from the startup script, but that was no
22590 help to people who didn't use the startup script. Resolves bug 863.
22591 - Build correctly when configured to build outside the main source
22592 path. Patch from Michael Gold.
22593 - Disable GCC's strict alias optimization by default, to avoid the
22594 likelihood of its introducing subtle bugs whenever our code violates
22595 the letter of C99's alias rules.
22596 - Change the contrib/tor.logrotate script so it makes the new
22597 logs as "_tor:_tor" rather than the default, which is generally
22598 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
22599 - Change our header file guard macros to be less likely to conflict
22600 with system headers. Adam Langley noticed that we were conflicting
22601 with log.h on Android.
22602 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
22603 and stop using a warning that had become unfixably verbose under
22605 - Use a lockfile to make sure that two Tor processes are not
22606 simultaneously running with the same datadir.
22607 - Allow OpenSSL to use dynamic locks if it wants.
22608 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
22610 o Minor features (controllers):
22611 - When generating circuit events with verbose nicknames for
22612 controllers, try harder to look up nicknames for routers on a
22613 circuit. (Previously, we would look in the router descriptors we had
22614 for nicknames, but not in the consensus.) Partial fix for bug 941.
22615 - New controller event NEWCONSENSUS that lists the networkstatus
22616 lines for every recommended relay. Now controllers like Torflow
22617 can keep up-to-date on which relays they should be using.
22618 - New controller event "clients_seen" to report a geoip-based summary
22619 of which countries we've seen clients from recently. Now controllers
22620 like Vidalia can show bridge operators that they're actually making
22622 - Add a 'getinfo status/clients-seen' controller command, in case
22623 controllers want to hear clients_seen events but connect late.
22624 - New CONSENSUS_ARRIVED event to note when a new consensus has
22625 been fetched and validated.
22626 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
22627 controllers to prevent SIGHUP from reloading the configuration.
22629 - Return circuit purposes in response to GETINFO circuit-status.
22631 - Serve the latest v3 networkstatus consensus via the control
22632 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
22633 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
22634 controller can query our current bootstrap state in case it attaches
22635 partway through and wants to catch up.
22636 - Provide circuit purposes along with circuit events to the controller.
22638 o Minor features (tools):
22639 - Do not have tor-resolve automatically refuse all .onion addresses;
22640 if AutomapHostsOnResolve is set in your torrc, this will work fine.
22641 - Add a -p option to tor-resolve for specifying the SOCKS port: some
22642 people find host:port too confusing.
22643 - Print the SOCKS5 error message string as well as the error code
22644 when a tor-resolve request fails. Patch from Jacob.
22646 o Minor bugfixes (memory and resource management):
22647 - Clients no longer cache certificates for authorities they do not
22648 recognize. Bugfix on 0.2.0.9-alpha.
22649 - Do not use C's stdio library for writing to log files. This will
22650 improve logging performance by a minute amount, and will stop
22651 leaking fds when our disk is full. Fixes bug 861.
22652 - Stop erroneous use of O_APPEND in cases where we did not in fact
22653 want to re-seek to the end of a file before every last write().
22654 - Fix a small alignment and memory-wasting bug on buffer chunks.
22656 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
22657 to avoid unused RAM in buffer chunks and memory pools.
22658 - Reduce the default smartlist size from 32 to 16; it turns out that
22659 most smartlists hold around 8-12 elements tops.
22660 - Make dumpstats() log the fullness and size of openssl-internal
22662 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
22663 patch to their OpenSSL, turn it on to save memory on servers. This
22664 patch will (with any luck) get included in a mainline distribution
22666 - Fix a memory leak when v3 directory authorities load their keys
22667 and cert from disk. Bugfix on 0.2.0.1-alpha.
22668 - Stop using malloc_usable_size() to use more area than we had
22669 actually allocated: it was safe, but made valgrind really unhappy.
22670 - Make the assert_circuit_ok() function work correctly on circuits that
22671 have already been marked for close.
22672 - Fix uninitialized size field for memory area allocation: may improve
22673 memory performance during directory parsing.
22675 o Minor bugfixes (clients):
22676 - Stop reloading the router list from disk for no reason when we
22677 run out of reachable directory mirrors. Once upon a time reloading
22678 it would set the 'is_running' flag back to 1 for them. It hasn't
22679 done that for a long time.
22680 - When we had picked an exit node for a connection, but marked it as
22681 "optional", and it turned out we had no onion key for the exit,
22682 stop wanting that exit and try again. This situation may not
22683 be possible now, but will probably become feasible with proposal
22684 158. Spotted by rovv. Fixes another case of bug 752.
22685 - Fix a bug in address parsing that was preventing bridges or hidden
22686 service targets from being at IPv6 addresses.
22687 - Do not remove routers as too old if we do not have any consensus
22688 document. Bugfix on 0.2.0.7-alpha.
22689 - When an exit relay resolves a stream address to a local IP address,
22690 do not just keep retrying that same exit relay over and
22691 over. Instead, just close the stream. Addresses bug 872. Bugfix
22692 on 0.2.0.32. Patch from rovv.
22693 - Made Tor a little less aggressive about deleting expired
22694 certificates. Partial fix for bug 854.
22695 - Treat duplicate certificate fetches as failures, so that we do
22696 not try to re-fetch an expired certificate over and over and over.
22697 - Do not say we're fetching a certificate when we'll in fact skip it
22698 because of a pending download.
22699 - If we have correct permissions on $datadir, we complain to stdout
22700 and fail to start. But dangerous permissions on
22701 $datadir/cached-status/ would cause us to open a log and complain
22702 there. Now complain to stdout and fail to start in both cases. Fixes
22703 bug 820, reported by seeess.
22705 o Minor bugfixes (bridges):
22706 - When we made bridge authorities stop serving bridge descriptors over
22707 unencrypted links, we also broke DirPort reachability testing for
22708 bridges. So bridges with a non-zero DirPort were printing spurious
22709 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
22710 - Don't allow a bridge to publish its router descriptor to a
22711 non-bridge directory authority. Fixes part of bug 932.
22712 - When we change to or from being a bridge, reset our counts of
22713 client usage by country. Fixes bug 932.
22715 o Minor bugfixes (relays):
22716 - Log correct error messages for DNS-related network errors on
22718 - Actually return -1 in the error case for read_bandwidth_usage().
22719 Harmless bug, since we currently don't care about the return value
22720 anywhere. Bugfix on 0.2.0.9-alpha.
22721 - Provide a more useful log message if bug 977 (related to buffer
22722 freelists) ever reappears, and do not crash right away.
22723 - We were already rejecting relay begin cells with destination port
22724 of 0. Now also reject extend cells with destination port or address
22725 of 0. Suggested by lark.
22726 - When we can't transmit a DNS request due to a network error, retry
22727 it after a while, and eventually transmit a failing response to
22728 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
22729 - Solve a bug that kept hardware crypto acceleration from getting
22730 enabled when accounting was turned on. Fixes bug 907. Bugfix on
22732 - When a canonical connection appears later in our internal list
22733 than a noncanonical one for a given OR ID, always use the
22734 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
22736 - Avoid some nasty corner cases in the logic for marking connections
22737 as too old or obsolete or noncanonical for circuits. Partial
22739 - Fix another interesting corner-case of bug 891 spotted by rovv:
22740 Previously, if two hosts had different amounts of clock drift, and
22741 one of them created a new connection with just the wrong timing,
22742 the other might decide to deprecate the new connection erroneously.
22743 Bugfix on 0.1.1.13-alpha.
22744 - If one win32 nameserver fails to get added, continue adding the
22745 rest, and don't automatically fail.
22746 - Fix a bug where an unreachable relay would establish enough
22747 reachability testing circuits to do a bandwidth test -- if
22748 we already have a connection to the middle hop of the testing
22749 circuit, then it could establish the last hop by using the existing
22750 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
22751 circuits no longer use entry guards in 0.2.1.3-alpha.
22753 o Minor bugfixes (directory authorities):
22754 - Limit uploaded directory documents to be 16M rather than 500K.
22755 The directory authorities were refusing v3 consensus votes from
22756 other authorities, since the votes are now 504K. Fixes bug 959;
22757 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
22758 - Directory authorities should never send a 503 "busy" response to
22759 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
22761 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
22762 headers. Bugfix on 0.2.0.10-alpha.
22764 o Minor bugfixes (hidden services):
22765 - When we can't find an intro key for a v2 hidden service descriptor,
22766 fall back to the v0 hidden service descriptor and log a bug message.
22767 Workaround for bug 1024.
22768 - In very rare situations new hidden service descriptors were
22769 published earlier than 30 seconds after the last change to the
22770 service. (We currently think that a hidden service descriptor
22771 that's been stable for 30 seconds is worth publishing.)
22772 - If a hidden service sends us an END cell, do not consider
22773 retrying the connection; just close it. Patch from rovv.
22774 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
22775 service directories if they have no advertised dir port. Bugfix
22778 o Minor bugfixes (tools):
22779 - In the torify(1) manpage, mention that tsocks will leak your
22782 o Minor bugfixes (controllers):
22783 - If the controller claimed responsibility for a stream, but that
22784 stream never finished making its connection, it would live
22785 forever in circuit_wait state. Now we close it after SocksTimeout
22786 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
22787 - Make DNS resolved controller events into "CLOSED", not
22788 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
22790 - The control port would close the connection before flushing long
22791 replies, such as the network consensus, if a QUIT command was issued
22792 before the reply had completed. Now, the control port flushes all
22793 pending replies before closing the connection. Also fix a spurious
22794 warning when a QUIT command is issued after a malformed or rejected
22795 AUTHENTICATE command, but before the connection was closed. Patch
22796 by Marcus Griep. Fixes bugs 1015 and 1016.
22797 - Fix a bug that made stream bandwidth get misreported to the
22800 o Deprecated and removed features:
22801 - The old "tor --version --version" command, which would print out
22802 the subversion "Id" of most of the source files, is now removed. It
22803 turned out to be less useful than we'd expected, and harder to
22805 - RedirectExits has been removed. It was deprecated since
22807 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
22808 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
22809 - Cell pools are now always enabled; --disable-cell-pools is ignored.
22810 - Directory mirrors no longer fetch the v1 directory or
22811 running-routers files. They are obsolete, and nobody asks for them
22812 anymore. This is the first step to making v1 authorities obsolete.
22813 - Take out the TestVia config option, since it was a workaround for
22814 a bug that was fixed in Tor 0.1.1.21.
22815 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
22816 HiddenServiceExcludeNodes as obsolete: they never worked properly,
22817 and nobody seems to be using them. Fixes bug 754. Bugfix on
22818 0.1.0.1-rc. Patch from Christian Wilms.
22819 - Remove all backward-compatibility code for relays running
22820 versions of Tor so old that they no longer work at all on the
22823 o Code simplifications and refactoring:
22824 - Tool-assisted documentation cleanup. Nearly every function or
22825 static variable in Tor should have its own documentation now.
22826 - Rename the confusing or_is_obsolete field to the more appropriate
22827 is_bad_for_new_circs, and move it to or_connection_t where it
22829 - Move edge-only flags from connection_t to edge_connection_t: not
22830 only is this better coding, but on machines of plausible alignment,
22831 it should save 4-8 bytes per connection_t. "Every little bit helps."
22832 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
22833 for consistency; keep old option working for backward compatibility.
22834 - Simplify the code for finding connections to use for a circuit.
22835 - Revise the connection_new functions so that a more typesafe variant
22836 exists. This will work better with Coverity, and let us find any
22837 actual mistakes we're making here.
22838 - Refactor unit testing logic so that dmalloc can be used sensibly
22839 with unit tests to check for memory leaks.
22840 - Move all hidden-service related fields from connection and circuit
22841 structure to substructures: this way they won't eat so much memory.
22842 - Squeeze 2-5% out of client performance (according to oprofile) by
22843 improving the implementation of some policy-manipulation functions.
22844 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
22845 be more efficient. Formerly it was quadratic in the number of
22846 servers; now it should be linear. Fixes bug 509.
22847 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
22848 and n_conn_id_digest fields into a separate structure that's
22849 only needed when the circuit has not yet attached to an n_conn.
22850 - Optimize out calls to time(NULL) that occur for every IO operation,
22851 or for every cell. On systems like Windows where time() is a
22852 slow syscall, this fix will be slightly helpful.
22855 Changes in version 0.2.0.35 - 2009-06-24
22857 - Avoid crashing in the presence of certain malformed descriptors.
22858 Found by lark, and by automated fuzzing.
22859 - Fix an edge case where a malicious exit relay could convince a
22860 controller that the client's DNS question resolves to an internal IP
22861 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22864 - Finally fix the bug where dynamic-IP relays disappear when their
22865 IP address changes: directory mirrors were mistakenly telling
22866 them their old address if they asked via begin_dir, so they
22867 never got an accurate answer about their new address, so they
22868 just vanished after a day. For belt-and-suspenders, relays that
22869 don't set Address in their config now avoid using begin_dir for
22870 all direct connections. Should fix bugs 827, 883, and 900.
22871 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22872 that would occur on some exit nodes when DNS failures and timeouts
22873 occurred in certain patterns. Fix for bug 957.
22876 - When starting with a cache over a few days old, do not leak
22877 memory for the obsolete router descriptors in it. Bugfix on
22878 0.2.0.33; fixes bug 672.
22879 - Hidden service clients didn't use a cached service descriptor that
22880 was older than 15 minutes, but wouldn't fetch a new one either,
22881 because there was already one in the cache. Now, fetch a v2
22882 descriptor unless the same descriptor was added to the cache within
22883 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22886 Changes in version 0.2.0.34 - 2009-02-08
22887 Tor 0.2.0.34 features several more security-related fixes. You should
22888 upgrade, especially if you run an exit relay (remote crash) or a
22889 directory authority (remote infinite loop), or you're on an older
22890 (pre-XP) or not-recently-patched Windows (remote exploit).
22892 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
22893 have many known flaws, and nobody should be using them. You should
22894 upgrade. If you're using a Linux or BSD and its packages are obsolete,
22895 stop using those packages and upgrade anyway.
22898 - Fix an infinite-loop bug on handling corrupt votes under certain
22899 circumstances. Bugfix on 0.2.0.8-alpha.
22900 - Fix a temporary DoS vulnerability that could be performed by
22901 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22902 - Avoid a potential crash on exit nodes when processing malformed
22903 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
22904 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22905 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22908 - Fix compilation on systems where time_t is a 64-bit integer.
22909 Patch from Matthias Drochner.
22910 - Don't consider expiring already-closed client connections. Fixes
22911 bug 893. Bugfix on 0.0.2pre20.
22914 Changes in version 0.2.0.33 - 2009-01-21
22915 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
22916 useful to users. It also finally fixes a bug where a relay or client
22917 that's been off for many days would take a long time to bootstrap.
22919 This update also fixes an important security-related bug reported by
22920 Ilja van Sprundel. You should upgrade. (We'll send out more details
22921 about the bug once people have had some time to upgrade.)
22924 - Fix a heap-corruption bug that may be remotely triggerable on
22925 some platforms. Reported by Ilja van Sprundel.
22928 - When a stream at an exit relay is in state "resolving" or
22929 "connecting" and it receives an "end" relay cell, the exit relay
22930 would silently ignore the end cell and not close the stream. If
22931 the client never closes the circuit, then the exit relay never
22932 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
22933 reported by "wood".
22934 - When sending CREATED cells back for a given circuit, use a 64-bit
22935 connection ID to find the right connection, rather than an addr:port
22936 combination. Now that we can have multiple OR connections between
22937 the same ORs, it is no longer possible to use addr:port to uniquely
22938 identify a connection.
22939 - Bridge relays that had DirPort set to 0 would stop fetching
22940 descriptors shortly after startup, and then briefly resume
22941 after a new bandwidth test and/or after publishing a new bridge
22942 descriptor. Bridge users that try to bootstrap from them would
22943 get a recent networkstatus but would get descriptors from up to
22944 18 hours earlier, meaning most of the descriptors were obsolete
22945 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
22946 - Prevent bridge relays from serving their 'extrainfo' document
22947 to anybody who asks, now that extrainfo docs include potentially
22948 sensitive aggregated client geoip summaries. Bugfix on
22950 - If the cached networkstatus consensus is more than five days old,
22951 discard it rather than trying to use it. In theory it could be
22952 useful because it lists alternate directory mirrors, but in practice
22953 it just means we spend many minutes trying directory mirrors that
22954 are long gone from the network. Also discard router descriptors as
22955 we load them if they are more than five days old, since the onion
22956 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
22959 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
22960 could make gcc generate non-functional binary search code. Bugfix
22962 - Build correctly on platforms without socklen_t.
22963 - Compile without warnings on solaris.
22964 - Avoid potential crash on internal error during signature collection.
22965 Fixes bug 864. Patch from rovv.
22966 - Correct handling of possible malformed authority signing key
22967 certificates with internal signature types. Fixes bug 880.
22968 Bugfix on 0.2.0.3-alpha.
22969 - Fix a hard-to-trigger resource leak when logging credential status.
22971 - When we can't initialize DNS because the network is down, do not
22972 automatically stop Tor from starting. Instead, we retry failed
22973 dns_init() every 10 minutes, and change the exit policy to reject
22974 *:* until one succeeds. Fixes bug 691.
22975 - Use 64 bits instead of 32 bits for connection identifiers used with
22976 the controller protocol, to greatly reduce risk of identifier reuse.
22977 - When we're choosing an exit node for a circuit, and we have
22978 no pending streams, choose a good general exit rather than one that
22979 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
22980 - Fix another case of assuming, when a specific exit is requested,
22981 that we know more than the user about what hosts it allows.
22982 Fixes one case of bug 752. Patch from rovv.
22983 - Clip the MaxCircuitDirtiness config option to a minimum of 10
22984 seconds. Warn the user if lower values are given in the
22985 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
22986 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
22987 user if lower values are given in the configuration. Bugfix on
22988 0.1.1.17-rc. Patch by Sebastian.
22989 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
22990 the cache because we already had a v0 descriptor with the same ID.
22991 Bugfix on 0.2.0.18-alpha.
22992 - Fix a race condition when freeing keys shared between main thread
22993 and CPU workers that could result in a memory leak. Bugfix on
22994 0.1.0.1-rc. Fixes bug 889.
22995 - Send a valid END cell back when a client tries to connect to a
22996 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
22997 840. Patch from rovv.
22998 - Check which hops rendezvous stream cells are associated with to
22999 prevent possible guess-the-streamid injection attacks from
23000 intermediate hops. Fixes another case of bug 446. Based on patch
23002 - If a broken client asks a non-exit router to connect somewhere,
23003 do not even do the DNS lookup before rejecting the connection.
23004 Fixes another case of bug 619. Patch from rovv.
23005 - When a relay gets a create cell it can't decrypt (e.g. because it's
23006 using the wrong onion key), we were dropping it and letting the
23007 client time out. Now actually answer with a destroy cell. Fixes
23008 bug 904. Bugfix on 0.0.2pre8.
23010 o Minor bugfixes (hidden services):
23011 - Do not throw away existing introduction points on SIGHUP. Bugfix on
23012 0.0.6pre1. Patch by Karsten. Fixes bug 874.
23015 - Report the case where all signatures in a detached set are rejected
23016 differently than the case where there is an error handling the
23018 - When we realize that another process has modified our cached
23019 descriptors, print out a more useful error message rather than
23020 triggering an assertion. Fixes bug 885. Patch from Karsten.
23021 - Implement the 0x20 hack to better resist DNS poisoning: set the
23022 case on outgoing DNS requests randomly, and reject responses that do
23023 not match the case correctly. This logic can be disabled with the
23024 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
23025 of servers that do not reliably preserve case in replies. See
23026 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
23028 - Check DNS replies for more matching fields to better resist DNS
23030 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23031 compress cells, which are basically all encrypted, compressed, or
23035 Changes in version 0.2.0.32 - 2008-11-20
23036 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
23037 packages (and maybe other packages) noticed by Theo de Raadt, fixes
23038 a smaller security flaw that might allow an attacker to access local
23039 services, further improves hidden service performance, and fixes a
23040 variety of other issues.
23043 - The "User" and "Group" config options did not clear the
23044 supplementary group entries for the Tor process. The "User" option
23045 is now more robust, and we now set the groups to the specified
23046 user's primary group. The "Group" option is now ignored. For more
23047 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
23048 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
23049 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
23050 - The "ClientDNSRejectInternalAddresses" config option wasn't being
23051 consistently obeyed: if an exit relay refuses a stream because its
23052 exit policy doesn't allow it, we would remember what IP address
23053 the relay said the destination address resolves to, even if it's
23054 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
23057 - Fix a DOS opportunity during the voting signature collection process
23058 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
23060 o Major bugfixes (hidden services):
23061 - When fetching v0 and v2 rendezvous service descriptors in parallel,
23062 we were failing the whole hidden service request when the v0
23063 descriptor fetch fails, even if the v2 fetch is still pending and
23064 might succeed. Similarly, if the last v2 fetch fails, we were
23065 failing the whole hidden service request even if a v0 fetch is
23066 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
23067 - When extending a circuit to a hidden service directory to upload a
23068 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
23069 requests failed, because the router descriptor has not been
23070 downloaded yet. In these cases, do not attempt to upload the
23071 rendezvous descriptor, but wait until the router descriptor is
23072 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
23073 descriptor from a hidden service directory for which the router
23074 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
23078 - Fix several infrequent memory leaks spotted by Coverity.
23079 - When testing for libevent functions, set the LDFLAGS variable
23080 correctly. Found by Riastradh.
23081 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
23082 bootstrapping with tunneled directory connections. Bugfix on
23083 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
23084 - When asked to connect to A.B.exit:80, if we don't know the IP for A
23085 and we know that server B rejects most-but-not all connections to
23086 port 80, we would previously reject the connection. Now, we assume
23087 the user knows what they were asking for. Fixes bug 752. Bugfix
23088 on 0.0.9rc5. Diagnosed by BarkerJr.
23089 - If we overrun our per-second write limits a little, count this as
23090 having used up our write allocation for the second, and choke
23091 outgoing directory writes. Previously, we had only counted this when
23092 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
23093 Bugfix on 0.2.0.x (??).
23094 - Remove the old v2 directory authority 'lefkada' from the default
23095 list. It has been gone for many months.
23096 - Stop doing unaligned memory access that generated bus errors on
23097 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
23098 - Make USR2 log-level switch take effect immediately. Bugfix on
23101 o Minor bugfixes (controller):
23102 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
23103 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
23106 Changes in version 0.2.0.31 - 2008-09-03
23107 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
23108 a big bug we're seeing where in rare cases traffic from one Tor stream
23109 gets mixed into another stream, and fixes a variety of smaller issues.
23112 - Make sure that two circuits can never exist on the same connection
23113 with the same circuit ID, even if one is marked for close. This
23114 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
23115 - Relays now reject risky extend cells: if the extend cell includes
23116 a digest of all zeroes, or asks to extend back to the relay that
23117 sent the extend cell, tear down the circuit. Ideas suggested
23119 - If not enough of our entry guards are available so we add a new
23120 one, we might use the new one even if it overlapped with the
23121 current circuit's exit relay (or its family). Anonymity bugfix
23122 pointed out by rovv.
23125 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23126 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23127 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23128 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23129 - Pick size of default geoip filename string correctly on windows.
23130 Fixes bug 806. Bugfix on 0.2.0.30.
23131 - Make the autoconf script accept the obsolete --with-ssl-dir
23132 option as an alias for the actually-working --with-openssl-dir
23133 option. Fix the help documentation to recommend --with-openssl-dir.
23134 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23135 - When using the TransPort option on OpenBSD, and using the User
23136 option to change UID and drop privileges, make sure to open
23137 /dev/pf before dropping privileges. Fixes bug 782. Patch from
23138 Christopher Davis. Bugfix on 0.1.2.1-alpha.
23139 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23140 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23141 on the client side when connecting to a hidden service. Bugfix
23142 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23143 - When closing an application-side connection because its circuit is
23144 getting torn down, generate the stream event correctly. Bugfix on
23145 0.1.2.x. Anonymous patch.
23148 Changes in version 0.2.0.30 - 2008-07-15
23149 This new stable release switches to a more efficient directory
23150 distribution design, adds features to make connections to the Tor
23151 network harder to block, allows Tor to act as a DNS proxy, adds separate
23152 rate limiting for relayed traffic to make it easier for clients to
23153 become relays, fixes a variety of potential anonymity problems, and
23154 includes the usual huge pile of other features and bug fixes.
23156 o New v3 directory design:
23157 - Tor now uses a new way to learn about and distribute information
23158 about the network: the directory authorities vote on a common
23159 network status document rather than each publishing their own
23160 opinion. Now clients and caches download only one networkstatus
23161 document to bootstrap, rather than downloading one for each
23162 authority. Clients only download router descriptors listed in
23163 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
23165 - Set up moria1, tor26, and dizum as v3 directory authorities
23166 in addition to being v2 authorities. Also add three new ones:
23167 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
23168 dannenberg (run by CCC).
23169 - Switch to multi-level keys for directory authorities: now their
23170 long-term identity key can be kept offline, and they periodically
23171 generate a new signing key. Clients fetch the "key certificates"
23172 to keep up to date on the right keys. Add a standalone tool
23173 "tor-gencert" to generate key certificates. Implements proposal 103.
23174 - Add a new V3AuthUseLegacyKey config option to make it easier for
23175 v3 authorities to change their identity keys if another bug like
23176 Debian's OpenSSL RNG flaw appears.
23177 - Authorities and caches fetch the v2 networkstatus documents
23178 less often, now that v3 is recommended.
23180 o Make Tor connections stand out less on the wire:
23181 - Use an improved TLS handshake designed by Steven Murdoch in proposal
23182 124, as revised in proposal 130. The new handshake is meant to
23183 be harder for censors to fingerprint, and it adds the ability
23184 to detect certain kinds of man-in-the-middle traffic analysis
23185 attacks. The new handshake format includes version negotiation for
23186 OR connections as described in proposal 105, which will allow us
23187 to improve Tor's link protocol more safely in the future.
23188 - Enable encrypted directory connections by default for non-relays,
23189 so censor tools that block Tor directory connections based on their
23190 plaintext patterns will no longer work. This means Tor works in
23191 certain censored countries by default again.
23192 - Stop including recognizeable strings in the commonname part of
23193 Tor's x509 certificates.
23195 o Implement bridge relays:
23196 - Bridge relays (or "bridges" for short) are Tor relays that aren't
23197 listed in the main Tor directory. Since there is no complete public
23198 list of them, even an ISP that is filtering connections to all the
23199 known Tor relays probably won't be able to block all the bridges.
23200 See doc/design-paper/blocking.pdf and proposal 125 for details.
23201 - New config option BridgeRelay that specifies you want to be a
23202 bridge relay rather than a normal relay. When BridgeRelay is set
23203 to 1, then a) you cache dir info even if your DirPort ins't on,
23204 and b) the default for PublishServerDescriptor is now "bridge"
23205 rather than "v2,v3".
23206 - New config option "UseBridges 1" for clients that want to use bridge
23207 relays instead of ordinary entry guards. Clients then specify
23208 bridge relays by adding "Bridge" lines to their config file. Users
23209 can learn about a bridge relay either manually through word of
23210 mouth, or by one of our rate-limited mechanisms for giving out
23211 bridge addresses without letting an attacker easily enumerate them
23212 all. See https://www.torproject.org/bridges for details.
23213 - Bridge relays behave like clients with respect to time intervals
23214 for downloading new v3 consensus documents -- otherwise they
23215 stand out. Bridge users now wait until the end of the interval,
23216 so their bridge relay will be sure to have a new consensus document.
23218 o Implement bridge directory authorities:
23219 - Bridge authorities are like normal directory authorities, except
23220 they don't serve a list of known bridges. Therefore users that know
23221 a bridge's fingerprint can fetch a relay descriptor for that bridge,
23222 including fetching updates e.g. if the bridge changes IP address,
23223 yet an attacker can't just fetch a list of all the bridges.
23224 - Set up Tonga as the default bridge directory authority.
23225 - Bridge authorities refuse to serve bridge descriptors or other
23226 bridge information over unencrypted connections (that is, when
23227 responding to direct DirPort requests rather than begin_dir cells.)
23228 - Bridge directory authorities do reachability testing on the
23229 bridges they know. They provide router status summaries to the
23230 controller via "getinfo ns/purpose/bridge", and also dump summaries
23231 to a file periodically, so we can keep internal stats about which
23232 bridges are functioning.
23233 - If bridge users set the UpdateBridgesFromAuthority config option,
23234 but the digest they ask for is a 404 on the bridge authority,
23235 they fall back to contacting the bridge directly.
23236 - Bridges always use begin_dir to publish their server descriptor to
23237 the bridge authority using an anonymous encrypted tunnel.
23238 - Early work on a "bridge community" design: if bridge authorities set
23239 the BridgePassword config option, they will serve a snapshot of
23240 known bridge routerstatuses from their DirPort to anybody who
23241 knows that password. Unset by default.
23242 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
23243 report sanitized aggregated summaries in their extra-info documents
23244 privately to the bridge authority, listing which countries are
23245 able to reach them. We hope this mechanism will let us learn when
23246 certain countries start trying to block bridges.
23247 - Bridge authorities write bridge descriptors to disk, so they can
23248 reload them after a reboot. They can also export the descriptors
23249 to other programs, so we can distribute them to blocked users via
23250 the BridgeDB interface, e.g. via https://bridges.torproject.org/
23251 and bridges@torproject.org.
23253 o Tor can be a DNS proxy:
23254 - The new client-side DNS proxy feature replaces the need for
23255 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
23256 for DNS requests on port 9999, use the Tor network to resolve them
23257 anonymously, and send the reply back like a regular DNS server.
23258 The code still only implements a subset of DNS.
23259 - Add a new AutomapHostsOnResolve option: when it is enabled, any
23260 resolve request for hosts matching a given pattern causes Tor to
23261 generate an internal virtual address mapping for that host. This
23262 allows DNSPort to work sensibly with hidden service users. By
23263 default, .exit and .onion addresses are remapped; the list of
23264 patterns can be reconfigured with AutomapHostsSuffixes.
23265 - Add an "-F" option to tor-resolve to force a resolve for a .onion
23266 address. Thanks to the AutomapHostsOnResolve option, this is no
23267 longer a completely silly thing to do.
23269 o Major features (relay usability):
23270 - New config options RelayBandwidthRate and RelayBandwidthBurst:
23271 a separate set of token buckets for relayed traffic. Right now
23272 relayed traffic is defined as answers to directory requests, and
23273 OR connections that don't have any local circuits on them. See
23274 proposal 111 for details.
23275 - Create listener connections before we setuid to the configured
23276 User and Group. Now non-Windows users can choose port values
23277 under 1024, start Tor as root, and have Tor bind those ports
23278 before it changes to another UID. (Windows users could already
23280 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
23281 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
23282 on "vserver" accounts. Patch from coderman.
23284 o Major features (directory authorities):
23285 - Directory authorities track weighted fractional uptime and weighted
23286 mean-time-between failures for relays. WFU is suitable for deciding
23287 whether a node is "usually up", while MTBF is suitable for deciding
23288 whether a node is "likely to stay up." We need both, because
23289 "usually up" is a good requirement for guards, while "likely to
23290 stay up" is a good requirement for long-lived connections.
23291 - Directory authorities use a new formula for selecting which relays
23292 to advertise as Guards: they must be in the top 7/8 in terms of
23293 how long we have known about them, and above the median of those
23294 nodes in terms of weighted fractional uptime.
23295 - Directory authorities use a new formula for selecting which relays
23296 to advertise as Stable: when we have 4 or more days of data, use
23297 median measured MTBF rather than median declared uptime. Implements
23299 - Directory authorities accept and serve "extra info" documents for
23300 routers. Routers now publish their bandwidth-history lines in the
23301 extra-info docs rather than the main descriptor. This step saves
23302 60% (!) on compressed router descriptor downloads. Servers upload
23303 extra-info docs to any authority that accepts them; directory
23304 authorities now allow multiple router descriptors and/or extra
23305 info documents to be uploaded in a single go. Authorities, and
23306 caches that have been configured to download extra-info documents,
23307 download them as needed. Implements proposal 104.
23308 - Authorities now list relays who have the same nickname as
23309 a different named relay, but list them with a new flag:
23310 "Unnamed". Now we can make use of relays that happen to pick the
23311 same nickname as a server that registered two years ago and then
23312 disappeared. Implements proposal 122.
23313 - Store routers in a file called cached-descriptors instead of in
23314 cached-routers. Initialize cached-descriptors from cached-routers
23315 if the old format is around. The new format allows us to store
23316 annotations along with descriptors, to record the time we received
23317 each descriptor, its source, and its purpose: currently one of
23318 general, controller, or bridge.
23320 o Major features (other):
23321 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
23322 Tor can warn and/or refuse connections to ports commonly used with
23323 vulnerable-plaintext protocols. Currently we warn on ports 23,
23324 109, 110, and 143, but we don't reject any. Based on proposal 129
23325 by Kevin Bauer and Damon McCoy.
23326 - Integrate Karsten Loesing's Google Summer of Code project to publish
23327 hidden service descriptors on a set of redundant relays that are a
23328 function of the hidden service address. Now we don't have to rely
23329 on three central hidden service authorities for publishing and
23330 fetching every hidden service descriptor. Implements proposal 114.
23331 - Allow tunnelled directory connections to ask for an encrypted
23332 "begin_dir" connection or an anonymized "uses a full Tor circuit"
23333 connection independently. Now we can make anonymized begin_dir
23334 connections for (e.g.) more secure hidden service posting and
23337 o Major bugfixes (crashes and assert failures):
23338 - Stop imposing an arbitrary maximum on the number of file descriptors
23339 used for busy servers. Bug reported by Olaf Selke; patch from
23341 - Avoid possible failures when generating a directory with routers
23342 with over-long versions strings, or too many flags set.
23343 - Fix a rare assert error when we're closing one of our threads:
23344 use a mutex to protect the list of logs, so we never write to the
23345 list as it's being freed. Fixes the very rare bug 575, which is
23346 kind of the revenge of bug 222.
23347 - Avoid segfault in the case where a badly behaved v2 versioning
23348 directory sends a signed networkstatus with missing client-versions.
23349 - When we hit an EOF on a log (probably because we're shutting down),
23350 don't try to remove the log from the list: just mark it as
23351 unusable. (Bulletproofs against bug 222.)
23353 o Major bugfixes (code security fixes):
23354 - Detect size overflow in zlib code. Reported by Justin Ferguson and
23356 - Rewrite directory tokenization code to never run off the end of
23357 a string. Fixes bug 455. Patch from croup.
23358 - Be more paranoid about overwriting sensitive memory on free(),
23359 as a defensive programming tactic to ensure forward secrecy.
23361 o Major bugfixes (anonymity fixes):
23362 - Reject requests for reverse-dns lookup of names that are in
23363 a private address space. Patch from lodger.
23364 - Never report that we've used more bandwidth than we're willing to
23365 relay: it leaks how much non-relay traffic we're using. Resolves
23367 - As a client, do not believe any server that tells us that an
23368 address maps to an internal address space.
23369 - Warn about unsafe ControlPort configurations.
23370 - Directory authorities now call routers Fast if their bandwidth is
23371 at least 100KB/s, and consider their bandwidth adequate to be a
23372 Guard if it is at least 250KB/s, no matter the medians. This fix
23373 complements proposal 107.
23374 - Directory authorities now never mark more than 2 servers per IP as
23375 Valid and Running (or 5 on addresses shared by authorities).
23376 Implements proposal 109, by Kevin Bauer and Damon McCoy.
23377 - If we're a relay, avoid picking ourselves as an introduction point,
23378 a rendezvous point, or as the final hop for internal circuits. Bug
23379 reported by taranis and lodger.
23380 - Exit relays that are used as a client can now reach themselves
23381 using the .exit notation, rather than just launching an infinite
23382 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
23383 - Fix a bug where, when we were choosing the 'end stream reason' to
23384 put in our relay end cell that we send to the exit relay, Tor
23385 clients on Windows were sometimes sending the wrong 'reason'. The
23386 anonymity problem is that exit relays may be able to guess whether
23387 the client is running Windows, thus helping partition the anonymity
23388 set. Down the road we should stop sending reasons to exit relays,
23389 or otherwise prevent future versions of this bug.
23390 - Only update guard status (usable / not usable) once we have
23391 enough directory information. This was causing us to discard all our
23392 guards on startup if we hadn't been running for a few weeks. Fixes
23394 - When our directory information has been expired for a while, stop
23395 being willing to build circuits using it. Fixes bug 401.
23397 o Major bugfixes (peace of mind for relay operators)
23398 - Non-exit relays no longer answer "resolve" relay cells, so they
23399 can't be induced to do arbitrary DNS requests. (Tor clients already
23400 avoid using non-exit relays for resolve cells, but now servers
23401 enforce this too.) Fixes bug 619. Patch from lodger.
23402 - When we setconf ClientOnly to 1, close any current OR and Dir
23403 listeners. Reported by mwenge.
23405 o Major bugfixes (other):
23406 - If we only ever used Tor for hidden service lookups or posts, we
23407 would stop building circuits and start refusing connections after
23408 24 hours, since we falsely believed that Tor was dormant. Reported
23410 - Add a new __HashedControlSessionPassword option for controllers
23411 to use for one-off session password hashes that shouldn't get
23412 saved to disk by SAVECONF --- Vidalia users were accumulating a
23413 pile of HashedControlPassword lines in their torrc files, one for
23414 each time they had restarted Tor and then clicked Save. Make Tor
23415 automatically convert "HashedControlPassword" to this new option but
23416 only when it's given on the command line. Partial fix for bug 586.
23417 - Patch from "Andrew S. Lists" to catch when we contact a directory
23418 mirror at IP address X and he says we look like we're coming from
23419 IP address X. Otherwise this would screw up our address detection.
23420 - Reject uploaded descriptors and extrainfo documents if they're
23421 huge. Otherwise we'll cache them all over the network and it'll
23422 clog everything up. Suggested by Aljosha Judmayer.
23423 - When a hidden service was trying to establish an introduction point,
23424 and Tor *did* manage to reuse one of the preemptively built
23425 circuits, it didn't correctly remember which one it used,
23426 so it asked for another one soon after, until there were no
23427 more preemptive circuits, at which point it launched one from
23428 scratch. Bugfix on 0.0.9.x.
23430 o Rate limiting and load balancing improvements:
23431 - When we add data to a write buffer in response to the data on that
23432 write buffer getting low because of a flush, do not consider the
23433 newly added data as a candidate for immediate flushing, but rather
23434 make it wait until the next round of writing. Otherwise, we flush
23435 and refill recursively, and a single greedy TLS connection can
23436 eat all of our bandwidth.
23437 - When counting the number of bytes written on a TLS connection,
23438 look at the BIO actually used for writing to the network, not
23439 at the BIO used (sometimes) to buffer data for the network.
23440 Looking at different BIOs could result in write counts on the
23441 order of ULONG_MAX. Fixes bug 614.
23442 - If we change our MaxAdvertisedBandwidth and then reload torrc,
23443 Tor won't realize it should publish a new relay descriptor. Fixes
23444 bug 688, reported by mfr.
23445 - Avoid using too little bandwidth when our clock skips a few seconds.
23446 - Choose which bridge to use proportional to its advertised bandwidth,
23447 rather than uniformly at random. This should speed up Tor for
23448 bridge users. Also do this for people who set StrictEntryNodes.
23450 o Bootstrapping faster and building circuits more intelligently:
23451 - Fix bug 660 that was preventing us from knowing that we should
23452 preemptively build circuits to handle expected directory requests.
23453 - When we're checking if we have enough dir info for each relay
23454 to begin establishing circuits, make sure that we actually have
23455 the descriptor listed in the consensus, not just any descriptor.
23456 - Correctly notify one-hop connections when a circuit build has
23457 failed. Possible fix for bug 669. Found by lodger.
23458 - Clients now hold circuitless TLS connections open for 1.5 times
23459 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
23460 rebuild a new circuit over them within that timeframe. Previously,
23461 they held them open only for KeepalivePeriod (5 minutes).
23463 o Performance improvements (memory):
23464 - Add OpenBSD malloc code from "phk" as an optional malloc
23465 replacement on Linux: some glibc libraries do very poorly with
23466 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
23467 ./configure to get the replacement malloc code.
23468 - Switch our old ring buffer implementation for one more like that
23469 used by free Unix kernels. The wasted space in a buffer with 1mb
23470 of data will now be more like 8k than 1mb. The new implementation
23471 also avoids realloc();realloc(); patterns that can contribute to
23472 memory fragmentation.
23473 - Change the way that Tor buffers data that it is waiting to write.
23474 Instead of queueing data cells in an enormous ring buffer for each
23475 client->OR or OR->OR connection, we now queue cells on a separate
23476 queue for each circuit. This lets us use less slack memory, and
23477 will eventually let us be smarter about prioritizing different kinds
23479 - Reference-count and share copies of address policy entries; only 5%
23480 of them were actually distinct.
23481 - Tune parameters for cell pool allocation to minimize amount of
23483 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
23484 for every single inactive connection_t. Free items from the
23485 4k/16k-buffer free lists when they haven't been used for a while.
23486 - Make memory debugging information describe more about history
23487 of cell allocation, so we can help reduce our memory use.
23488 - Be even more aggressive about releasing RAM from small
23489 empty buffers. Thanks to our free-list code, this shouldn't be too
23490 performance-intensive.
23491 - Log malloc statistics from mallinfo() on platforms where it exists.
23492 - Use memory pools to allocate cells with better speed and memory
23493 efficiency, especially on platforms where malloc() is inefficient.
23494 - Add a --with-tcmalloc option to the configure script to link
23495 against tcmalloc (if present). Does not yet search for non-system
23498 o Performance improvements (socket management):
23499 - Count the number of open sockets separately from the number of
23500 active connection_t objects. This will let us avoid underusing
23501 our allocated connection limit.
23502 - We no longer use socket pairs to link an edge connection to an
23503 anonymous directory connection or a DirPort test connection.
23504 Instead, we track the link internally and transfer the data
23505 in-process. This saves two sockets per "linked" connection (at the
23506 client and at the server), and avoids the nasty Windows socketpair()
23508 - We were leaking a file descriptor if Tor started with a zero-length
23509 cached-descriptors file. Patch by "freddy77".
23511 o Performance improvements (CPU use):
23512 - Never walk through the list of logs if we know that no log target
23513 is interested in a given message.
23514 - Call routerlist_remove_old_routers() much less often. This should
23515 speed startup, especially on directory caches.
23516 - Base64 decoding was actually showing up on our profile when parsing
23517 the initial descriptor file; switch to an in-process all-at-once
23518 implementation that's about 3.5x times faster than calling out to
23520 - Use a slightly simpler string hashing algorithm (copying Python's
23521 instead of Java's) and optimize our digest hashing algorithm to take
23522 advantage of 64-bit platforms and to remove some possibly-costly
23524 - When implementing AES counter mode, update only the portions of the
23525 counter buffer that need to change, and don't keep separate
23526 network-order and host-order counters on big-endian hosts (where
23527 they are the same).
23528 - Add an in-place version of aes_crypt() so that we can avoid doing a
23529 needless memcpy() call on each cell payload.
23530 - Use Critical Sections rather than Mutexes for synchronizing threads
23531 on win32; Mutexes are heavier-weight, and designed for synchronizing
23534 o Performance improvements (bandwidth use):
23535 - Don't try to launch new descriptor downloads quite so often when we
23536 already have enough directory information to build circuits.
23537 - Version 1 directories are no longer generated in full. Instead,
23538 authorities generate and serve "stub" v1 directories that list
23539 no servers. This will stop Tor versions 0.1.0.x and earlier from
23540 working, but (for security reasons) nobody should be running those
23542 - Avoid going directly to the directory authorities even if you're a
23543 relay, if you haven't found yourself reachable yet or if you've
23544 decided not to advertise your dirport yet. Addresses bug 556.
23545 - If we've gone 12 hours since our last bandwidth check, and we
23546 estimate we have less than 50KB bandwidth capacity but we could
23547 handle more, do another bandwidth test.
23548 - Support "If-Modified-Since" when answering HTTP requests for
23549 directories, running-routers documents, and v2 and v3 networkstatus
23550 documents. (There's no need to support it for router descriptors,
23551 since those are downloaded by descriptor digest.)
23552 - Stop fetching directory info so aggressively if your DirPort is
23553 on but your ORPort is off; stop fetching v2 dir info entirely.
23554 You can override these choices with the new FetchDirInfoEarly
23557 o Changed config option behavior (features):
23558 - Configuration files now accept C-style strings as values. This
23559 helps encode characters not allowed in the current configuration
23560 file format, such as newline or #. Addresses bug 557.
23561 - Add hidden services and DNSPorts to the list of things that make
23562 Tor accept that it has running ports. Change starting Tor with no
23563 ports from a fatal error to a warning; we might change it back if
23564 this turns out to confuse anybody. Fixes bug 579.
23565 - Make PublishServerDescriptor default to 1, so the default doesn't
23566 have to change as we invent new directory protocol versions.
23567 - Allow people to say PreferTunnelledDirConns rather than
23568 PreferTunneledDirConns, for those alternate-spellers out there.
23569 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
23570 accommodate the growing number of servers that use the default
23571 and are reaching it.
23572 - Make it possible to enable HashedControlPassword and
23573 CookieAuthentication at the same time.
23574 - When a TrackHostExits-chosen exit fails too many times in a row,
23575 stop using it. Fixes bug 437.
23577 o Changed config option behavior (bugfixes):
23578 - Do not read the configuration file when we've only been told to
23579 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
23580 based on patch from Sebastian Hahn.
23581 - Actually validate the options passed to AuthDirReject,
23582 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
23583 - Make "ClientOnly 1" config option disable directory ports too.
23584 - Don't stop fetching descriptors when FetchUselessDescriptors is
23585 set, even if we stop asking for circuits. Bug reported by tup
23587 - Servers used to decline to publish their DirPort if their
23588 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
23589 they look only at BandwidthRate and RelayBandwidthRate.
23590 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
23591 minus 1 byte: the actual maximum declared bandwidth.
23592 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
23593 - Make the NodeFamilies config option work. (Reported by
23594 lodger -- it has never actually worked, even though we added it
23596 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
23597 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
23599 o New config options:
23600 - New configuration options AuthDirMaxServersPerAddr and
23601 AuthDirMaxServersperAuthAddr to override default maximum number
23602 of servers allowed on a single IP address. This is important for
23603 running a test network on a single host.
23604 - Three new config options (AlternateDirAuthority,
23605 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
23606 user selectively replace the default directory authorities by type,
23607 rather than the all-or-nothing replacement that DirServer offers.
23608 - New config options AuthDirBadDir and AuthDirListBadDirs for
23609 authorities to mark certain relays as "bad directories" in the
23610 networkstatus documents. Also supports the "!baddir" directive in
23611 the approved-routers file.
23612 - New config option V2AuthoritativeDirectory that all v2 directory
23613 authorities must set. This lets v3 authorities choose not to serve
23614 v2 directory information.
23616 o Minor features (other):
23617 - When we're not serving v2 directory information, there is no reason
23618 to actually keep any around. Remove the obsolete files and directory
23619 on startup if they are very old and we aren't going to serve them.
23620 - When we negotiate a v2 link-layer connection (not yet implemented),
23621 accept RELAY_EARLY cells and turn them into RELAY cells if we've
23622 negotiated a v1 connection for their next step. Initial steps for
23624 - When we have no consensus, check FallbackNetworkstatusFile (defaults
23625 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
23626 we can start out knowing some directory caches. We don't ship with
23627 a fallback consensus by default though, because it was making
23628 bootstrapping take too long while we tried many down relays.
23629 - Authorities send back an X-Descriptor-Not-New header in response to
23630 an accepted-but-discarded descriptor upload. Partially implements
23632 - If we find a cached-routers file that's been sitting around for more
23633 than 28 days unmodified, then most likely it's a leftover from
23634 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
23636 - When we (as a cache) download a descriptor because it was listed
23637 in a consensus, remember when the consensus was supposed to expire,
23638 and don't expire the descriptor until then.
23639 - Optionally (if built with -DEXPORTMALLINFO) export the output
23640 of mallinfo via http, as tor/mallinfo.txt. Only accessible
23642 - Tag every guard node in our state file with the version that
23643 we believe added it, or with our own version if we add it. This way,
23644 if a user temporarily runs an old version of Tor and then switches
23645 back to a new one, she doesn't automatically lose her guards.
23646 - When somebody requests a list of statuses or servers, and we have
23647 none of those, return a 404 rather than an empty 200.
23648 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
23650 - Add an HSAuthorityRecordStats option that hidden service authorities
23651 can use to track statistics of overall hidden service usage without
23652 logging information that would be as useful to an attacker.
23653 - Allow multiple HiddenServicePort directives with the same virtual
23654 port; when they occur, the user is sent round-robin to one
23655 of the target ports chosen at random. Partially fixes bug 393 by
23656 adding limited ad-hoc round-robining.
23657 - Revamp file-writing logic so we don't need to have the entire
23658 contents of a file in memory at once before we write to disk. Tor,
23661 o Minor bugfixes (other):
23662 - Alter the code that tries to recover from unhandled write
23663 errors, to not try to flush onto a socket that's given us
23665 - Directory mirrors no longer include a guess at the client's IP
23666 address if the connection appears to be coming from the same /24
23667 network; it was producing too many wrong guesses.
23668 - If we're trying to flush the last bytes on a connection (for
23669 example, when answering a directory request), reset the
23670 time-to-give-up timeout every time we manage to write something
23672 - Reject router descriptors with out-of-range bandwidthcapacity or
23673 bandwidthburst values.
23674 - If we can't expand our list of entry guards (e.g. because we're
23675 using bridges or we have StrictEntryNodes set), don't mark relays
23676 down when they fail a directory request. Otherwise we're too quick
23677 to mark all our entry points down.
23678 - Authorities no longer send back "400 you're unreachable please fix
23679 it" errors to Tor servers that aren't online all the time. We're
23680 supposed to tolerate these servers now.
23681 - Let directory authorities startup even when they can't generate
23682 a descriptor immediately, e.g. because they don't know their
23684 - Correctly enforce that elements of directory objects do not appear
23685 more often than they are allowed to appear.
23686 - Stop allowing hibernating servers to be "stable" or "fast".
23687 - On Windows, we were preventing other processes from reading
23688 cached-routers while Tor was running. (Reported by janbar)
23689 - Check return values from pthread_mutex functions.
23690 - When opening /dev/null in finish_daemonize(), do not pass the
23691 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
23692 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
23694 o Controller features:
23695 - The GETCONF command now escapes and quotes configuration values
23696 that don't otherwise fit into the torrc file.
23697 - The SETCONF command now handles quoted values correctly.
23698 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
23699 ask about source, timestamp of arrival, purpose, etc. We need
23700 something like this to help Vidalia not do GeoIP lookups on bridge
23702 - Allow multiple HashedControlPassword config lines, to support
23703 multiple controller passwords.
23704 - Accept LF instead of CRLF on controller, since some software has a
23705 hard time generating real Internet newlines.
23706 - Add GETINFO values for the server status events
23707 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
23709 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
23710 GETINFO for Torstat to use until it can switch to using extrainfos.
23711 - New config option CookieAuthFile to choose a new location for the
23712 cookie authentication file, and config option
23713 CookieAuthFileGroupReadable to make it group-readable.
23714 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
23715 match requests to applications. Patch from Robert Hogan.
23716 - Add a RESOLVE command to launch hostname lookups. Original patch
23718 - Add GETINFO status/enough-dir-info to let controllers tell whether
23719 Tor has downloaded sufficient directory information. Patch from Tup.
23720 - You can now use the ControlSocket option to tell Tor to listen for
23721 controller connections on Unix domain sockets on systems that
23722 support them. Patch from Peter Palfrader.
23723 - New "GETINFO address-mappings/*" command to get address mappings
23724 with expiry information. "addr-mappings/*" is now deprecated.
23726 - Add a new config option __DisablePredictedCircuits designed for
23727 use by the controller, when we don't want Tor to build any circuits
23729 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
23730 so we can exit from the middle of the circuit.
23731 - Implement "getinfo status/circuit-established".
23732 - Implement "getinfo status/version/..." so a controller can tell
23733 whether the current version is recommended, and whether any versions
23734 are good, and how many authorities agree. Patch from "shibz".
23735 - Controllers should now specify cache=no or cache=yes when using
23736 the +POSTDESCRIPTOR command.
23737 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
23738 Robert Hogan. Fixes the first part of bug 681.
23739 - When reporting clock skew, and we know that the clock is _at least
23740 as skewed_ as some value, but we don't know the actual value,
23741 report the value as a "minimum skew."
23743 o Controller bugfixes:
23744 - Generate "STATUS_SERVER" events rather than misspelled
23745 "STATUS_SEVER" events. Caught by mwenge.
23746 - Reject controller commands over 1MB in length, so rogue
23747 processes can't run us out of memory.
23748 - Change the behavior of "getinfo status/good-server-descriptor"
23749 so it doesn't return failure when any authority disappears.
23750 - Send NAMESERVER_STATUS messages for a single failed nameserver
23752 - When the DANGEROUS_VERSION controller status event told us we're
23753 running an obsolete version, it used the string "OLD" to describe
23754 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
23755 "OBSOLETE" in both cases.
23756 - Respond to INT and TERM SIGNAL commands before we execute the
23757 signal, in case the signal shuts us down. We had a patch in
23758 0.1.2.1-alpha that tried to do this by queueing the response on
23759 the connection's buffer before shutting down, but that really
23760 isn't the same thing at all. Bug located by Matt Edman.
23761 - Provide DNS expiry times in GMT, not in local time. For backward
23762 compatibility, ADDRMAP events only provide GMT expiry in an extended
23763 field. "GETINFO address-mappings" always does the right thing.
23764 - Use CRLF line endings properly in NS events.
23765 - Make 'getinfo fingerprint' return a 551 error if we're not a
23766 server, so we match what the control spec claims we do. Reported
23768 - Fix a typo in an error message when extendcircuit fails that
23769 caused us to not follow the \r\n-based delimiter protocol. Reported
23771 - When tunneling an encrypted directory connection, and its first
23772 circuit fails, do not leave it unattached and ask the controller
23773 to deal. Fixes the second part of bug 681.
23774 - Treat some 403 responses from directory servers as INFO rather than
23775 WARN-severity events.
23777 o Portability / building / compiling:
23778 - When building with --enable-gcc-warnings, check for whether Apple's
23779 warning "-Wshorten-64-to-32" is available.
23780 - Support compilation to target iPhone; patch from cjacker huang.
23781 To build for iPhone, pass the --enable-iphone option to configure.
23782 - Port Tor to build and run correctly on Windows CE systems, using
23783 the wcecompat library. Contributed by Valerio Lupi.
23784 - Detect non-ASCII platforms (if any still exist) and refuse to
23785 build there: some of our code assumes that 'A' is 65 and so on.
23786 - Clear up some MIPSPro compiler warnings.
23787 - Make autoconf search for libevent, openssl, and zlib consistently.
23788 - Update deprecated macros in configure.in.
23789 - When warning about missing headers, tell the user to let us
23790 know if the compile succeeds anyway, so we can downgrade the
23792 - Include the current subversion revision as part of the version
23793 string: either fetch it directly if we're in an SVN checkout, do
23794 some magic to guess it if we're in an SVK checkout, or use
23795 the last-detected version if we're building from a .tar.gz.
23796 Use this version consistently in log messages.
23797 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
23798 - Read resolv.conf files correctly on platforms where read() returns
23799 partial results on small file reads.
23800 - Build without verbose warnings even on gcc 4.2 and 4.3.
23801 - On Windows, correctly detect errors when listing the contents of
23802 a directory. Fix from lodger.
23803 - Run 'make test' as part of 'make dist', so we stop releasing so
23804 many development snapshots that fail their unit tests.
23805 - Add support to detect Libevent versions in the 1.4.x series
23807 - Add command-line arguments to unit-test executable so that we can
23808 invoke any chosen test from the command line rather than having
23809 to run the whole test suite at once; and so that we can turn on
23810 logging for the unit tests.
23811 - Do not automatically run configure from autogen.sh. This
23812 non-standard behavior tended to annoy people who have built other
23814 - Fix a macro/CPP interaction that was confusing some compilers:
23815 some GCCs don't like #if/#endif pairs inside macro arguments.
23817 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
23818 Fixes bug 704; fix from Steven Murdoch.
23819 - Correctly detect transparent proxy support on Linux hosts that
23820 require in.h to be included before netfilter_ipv4.h. Patch
23823 o Logging improvements:
23824 - When we haven't had any application requests lately, don't bother
23825 logging that we have expired a bunch of descriptors.
23826 - When attempting to open a logfile fails, tell us why.
23827 - Only log guard node status when guard node status has changed.
23828 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
23829 make "INFO" 75% less verbose.
23830 - When SafeLogging is disabled, log addresses along with all TLS
23832 - Report TLS "zero return" case as a "clean close" and "IO error"
23833 as a "close". Stop calling closes "unexpected closes": existing
23834 Tors don't use SSL_close(), so having a connection close without
23835 the TLS shutdown handshake is hardly unexpected.
23836 - When we receive a consensus from the future, warn about skew.
23837 - Make "not enough dir info yet" warnings describe *why* Tor feels
23838 it doesn't have enough directory info yet.
23839 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
23840 consumers. (We already do this on HUP.)
23841 - Give more descriptive well-formedness errors for out-of-range
23842 hidden service descriptor/protocol versions.
23843 - Stop recommending that every server operator send mail to tor-ops.
23844 Resolves bug 597. Bugfix on 0.1.2.x.
23845 - Improve skew reporting: try to give the user a better log message
23846 about how skewed they are, and how much this matters.
23847 - New --quiet command-line option to suppress the default console log.
23848 Good in combination with --hash-password.
23849 - Don't complain that "your server has not managed to confirm that its
23850 ports are reachable" if we haven't been able to build any circuits
23852 - Detect the reason for failing to mmap a descriptor file we just
23853 wrote, and give a more useful log message. Fixes bug 533.
23854 - Always prepend "Bug: " to any log message about a bug.
23855 - When dumping memory usage, list bytes used in buffer memory
23857 - When running with dmalloc, dump more stats on hup and on exit.
23858 - Put a platform string (e.g. "Linux i686") in the startup log
23859 message, so when people paste just their logs, we know if it's
23860 OpenBSD or Windows or what.
23861 - When logging memory usage, break down memory used in buffers by
23863 - When we are reporting the DirServer line we just parsed, we were
23864 logging the second stanza of the key fingerprint, not the first.
23865 - Even though Windows is equally happy with / and \ as path separators,
23866 try to use \ consistently on Windows and / consistently on Unix: it
23867 makes the log messages nicer.
23868 - On OSX, stop warning the user that kqueue support in libevent is
23869 "experimental", since it seems to have worked fine for ages.
23871 o Contributed scripts and tools:
23872 - Update linux-tor-prio.sh script to allow QoS based on the uid of
23873 the Tor process. Patch from Marco Bonetti with tweaks from Mike
23875 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
23876 Unix users an easy way to script their Tor process (e.g. by
23877 adjusting bandwidth based on the time of the day).
23878 - In the exitlist script, only consider the most recently published
23879 server descriptor for each server. Also, when the user requests
23880 a list of servers that _reject_ connections to a given address,
23881 explicitly exclude the IPs that also have servers that accept
23882 connections to that address. Resolves bug 405.
23883 - Include a new contrib/tor-exit-notice.html file that exit relay
23884 operators can put on their website to help reduce abuse queries.
23886 o Newly deprecated features:
23887 - The status/version/num-versioning and status/version/num-concurring
23888 GETINFO controller options are no longer useful in the v3 directory
23889 protocol: treat them as deprecated, and warn when they're used.
23890 - The RedirectExits config option is now deprecated.
23892 o Removed features:
23893 - Drop the old code to choke directory connections when the
23894 corresponding OR connections got full: thanks to the cell queue
23895 feature, OR conns don't get full any more.
23896 - Remove the old "dns worker" server DNS code: it hasn't been default
23897 since 0.1.2.2-alpha, and all the servers are using the new
23899 - Remove the code to generate the oldest (v1) directory format.
23900 - Remove support for the old bw_accounting file: we've been storing
23901 bandwidth accounting information in the state file since
23902 0.1.2.5-alpha. This may result in bandwidth accounting errors
23903 if you try to upgrade from 0.1.1.x or earlier, or if you try to
23904 downgrade to 0.1.1.x or earlier.
23905 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
23906 it, it had no AES, and it hasn't seen any security patches since
23908 - Stop overloading the circuit_t.onionskin field for both "onionskin
23909 from a CREATE cell that we are waiting for a cpuworker to be
23910 assigned" and "onionskin from an EXTEND cell that we are going to
23911 send to an OR as soon as we are connected". Might help with bug 600.
23912 - Remove the tor_strpartition() function: its logic was confused,
23913 and it was only used for one thing that could be implemented far
23915 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
23916 and TorControl.py, as they use the old v0 controller protocol,
23917 and are obsoleted by TorFlow anyway.
23918 - Drop support for v1 rendezvous descriptors, since we never used
23919 them anyway, and the code has probably rotted by now. Based on
23920 patch from Karsten Loesing.
23921 - Stop allowing address masks that do not correspond to bit prefixes.
23922 We have warned about these for a really long time; now it's time
23923 to reject them. (Patch from croup.)
23924 - Remove an optimization in the AES counter-mode code that assumed
23925 that the counter never exceeded 2^68. When the counter can be set
23926 arbitrarily as an IV (as it is by Karsten's new hidden services
23927 code), this assumption no longer holds.
23928 - Disable the SETROUTERPURPOSE controller command: it is now
23932 Changes in version 0.1.2.19 - 2008-01-17
23933 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
23934 exit policy a little bit more conservative so it's safer to run an
23935 exit relay on a home system, and fixes a variety of smaller issues.
23938 - Exit policies now reject connections that are addressed to a
23939 relay's public (external) IP address too, unless
23940 ExitPolicyRejectPrivate is turned off. We do this because too
23941 many relays are running nearby to services that trust them based
23942 on network address.
23945 - When the clock jumps forward a lot, do not allow the bandwidth
23946 buckets to become negative. Fixes bug 544.
23947 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
23948 on every successful resolve. Reported by Mike Perry.
23949 - Purge old entries from the "rephist" database and the hidden
23950 service descriptor database even when DirPort is zero.
23951 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
23952 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
23953 crashing or mis-answering these requests.
23954 - When we decide to send a 503 response to a request for servers, do
23955 not then also send the server descriptors: this defeats the whole
23956 purpose. Fixes bug 539.
23959 - Changing the ExitPolicyRejectPrivate setting should cause us to
23960 rebuild our server descriptor.
23961 - Fix handling of hex nicknames when answering controller requests for
23962 networkstatus by name, or when deciding whether to warn about
23963 unknown routers in a config option. (Patch from mwenge.)
23964 - Fix a couple of hard-to-trigger autoconf problems that could result
23965 in really weird results on platforms whose sys/types.h files define
23966 nonstandard integer types.
23967 - Don't try to create the datadir when running --verify-config or
23968 --hash-password. Resolves bug 540.
23969 - If we were having problems getting a particular descriptor from the
23970 directory caches, and then we learned about a new descriptor for
23971 that router, we weren't resetting our failure count. Reported
23973 - Although we fixed bug 539 (where servers would send HTTP status 503
23974 responses _and_ send a body too), there are still servers out there
23975 that haven't upgraded. Therefore, make clients parse such bodies
23976 when they receive them.
23977 - Run correctly on systems where rlim_t is larger than unsigned long.
23978 This includes some 64-bit systems.
23979 - Run correctly on platforms (like some versions of OS X 10.5) where
23980 the real limit for number of open files is OPEN_FILES, not rlim_max
23981 from getrlimit(RLIMIT_NOFILES).
23982 - Avoid a spurious free on base64 failure.
23983 - Avoid segfaults on certain complex invocations of
23984 router_get_by_hexdigest().
23985 - Fix rare bug on REDIRECTSTREAM control command when called with no
23986 port set: it could erroneously report an error when none had
23990 Changes in version 0.1.2.18 - 2007-10-28
23991 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
23992 hidden service introduction that were causing huge delays, and a big
23993 bug that was causing some servers to disappear from the network status
23994 lists for a few hours each day.
23996 o Major bugfixes (crashes):
23997 - If a connection is shut down abruptly because of something that
23998 happened inside connection_flushed_some(), do not call
23999 connection_finished_flushing(). Should fix bug 451:
24000 "connection_stop_writing: Assertion conn->write_event failed"
24001 Bugfix on 0.1.2.7-alpha.
24002 - Fix possible segfaults in functions called from
24003 rend_process_relay_cell().
24005 o Major bugfixes (hidden services):
24006 - Hidden services were choosing introduction points uniquely by
24007 hexdigest, but when constructing the hidden service descriptor
24008 they merely wrote the (potentially ambiguous) nickname.
24009 - Clients now use the v2 intro format for hidden service
24010 connections: they specify their chosen rendezvous point by identity
24011 digest rather than by (potentially ambiguous) nickname. These
24012 changes could speed up hidden service connections dramatically.
24014 o Major bugfixes (other):
24015 - Stop publishing a new server descriptor just because we get a
24016 HUP signal. This led (in a roundabout way) to some servers getting
24017 dropped from the networkstatus lists for a few hours each day.
24018 - When looking for a circuit to cannibalize, consider family as well
24019 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
24020 circuit cannibalization).
24021 - When a router wasn't listed in a new networkstatus, we were leaving
24022 the flags for that router alone -- meaning it remained Named,
24023 Running, etc -- even though absence from the networkstatus means
24024 that it shouldn't be considered to exist at all anymore. Now we
24025 clear all the flags for routers that fall out of the networkstatus
24026 consensus. Fixes bug 529.
24029 - Don't try to access (or alter) the state file when running
24030 --list-fingerprint or --verify-config or --hash-password. Resolves
24032 - When generating information telling us how to extend to a given
24033 router, do not try to include the nickname if it is
24034 absent. Resolves bug 467.
24035 - Fix a user-triggerable segfault in expand_filename(). (There isn't
24036 a way to trigger this remotely.)
24037 - When sending a status event to the controller telling it that an
24038 OR address is reachable, set the port correctly. (Previously we
24039 were reporting the dir port.)
24040 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
24041 command. Bugfix on 0.1.2.17.
24042 - When loading bandwidth history, do not believe any information in
24043 the future. Fixes bug 434.
24044 - When loading entry guard information, do not believe any information
24046 - When we have our clock set far in the future and generate an
24047 onion key, then re-set our clock to be correct, we should not stop
24048 the onion key from getting rotated.
24049 - On some platforms, accept() can return a broken address. Detect
24050 this more quietly, and deal accordingly. Fixes bug 483.
24051 - It's not actually an error to find a non-pending entry in the DNS
24052 cache when canceling a pending resolve. Don't log unless stuff
24053 is fishy. Resolves bug 463.
24054 - Don't reset trusted dir server list when we set a configuration
24055 option. Patch from Robert Hogan.
24058 Changes in version 0.1.2.17 - 2007-08-30
24059 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
24060 X bundles. Vidalia 0.0.14 makes authentication required for the
24061 ControlPort in the default configuration, which addresses important
24062 security risks. Everybody who uses Vidalia (or another controller)
24065 In addition, this Tor update fixes major load balancing problems with
24066 path selection, which should speed things up a lot once many people
24069 o Major bugfixes (security):
24070 - We removed support for the old (v0) control protocol. It has been
24071 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
24072 become more of a headache than it's worth.
24074 o Major bugfixes (load balancing):
24075 - When choosing nodes for non-guard positions, weight guards
24076 proportionally less, since they already have enough load. Patch
24078 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
24079 will allow fast Tor servers to get more attention.
24080 - When we're upgrading from an old Tor version, forget our current
24081 guards and pick new ones according to the new weightings. These
24082 three load balancing patches could raise effective network capacity
24083 by a factor of four. Thanks to Mike Perry for measurements.
24085 o Major bugfixes (stream expiration):
24086 - Expire not-yet-successful application streams in all cases if
24087 they've been around longer than SocksTimeout. Right now there are
24088 some cases where the stream will live forever, demanding a new
24089 circuit every 15 seconds. Fixes bug 454; reported by lodger.
24091 o Minor features (controller):
24092 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
24093 is valid before any authentication has been received. It tells
24094 a controller what kind of authentication is expected, and what
24095 protocol is spoken. Implements proposal 119.
24097 o Minor bugfixes (performance):
24098 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
24099 greatly speeding up loading cached-routers from disk on startup.
24100 - Disable sentinel-based debugging for buffer code: we squashed all
24101 the bugs that this was supposed to detect a long time ago, and now
24102 its only effect is to change our buffer sizes from nice powers of
24103 two (which platform mallocs tend to like) to values slightly over
24104 powers of two (which make some platform mallocs sad).
24106 o Minor bugfixes (misc):
24107 - If exit bandwidth ever exceeds one third of total bandwidth, then
24108 use the correct formula to weight exit nodes when choosing paths.
24109 Based on patch from Mike Perry.
24110 - Choose perfectly fairly among routers when choosing by bandwidth and
24111 weighting by fraction of bandwidth provided by exits. Previously, we
24112 would choose with only approximate fairness, and correct ourselves
24113 if we ran off the end of the list.
24114 - If we require CookieAuthentication but we fail to write the
24115 cookie file, we would warn but not exit, and end up in a state
24116 where no controller could authenticate. Now we exit.
24117 - If we require CookieAuthentication, stop generating a new cookie
24118 every time we change any piece of our config.
24119 - Refuse to start with certain directory authority keys, and
24120 encourage people using them to stop.
24121 - Terminate multi-line control events properly. Original patch
24123 - Fix a minor memory leak when we fail to find enough suitable
24124 servers to choose a circuit.
24125 - Stop leaking part of the descriptor when we run into a particularly
24126 unparseable piece of it.
24129 Changes in version 0.1.2.16 - 2007-08-01
24130 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
24131 remote attacker in certain situations to rewrite the user's torrc
24132 configuration file. This can completely compromise anonymity of users
24133 in most configurations, including those running the Vidalia bundles,
24134 TorK, etc. Or worse.
24136 o Major security fixes:
24137 - Close immediately after missing authentication on control port;
24138 do not allow multiple authentication attempts.
24141 Changes in version 0.1.2.15 - 2007-07-17
24142 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
24143 problems, fixes compilation on BSD, and fixes a variety of other
24144 bugs. Everybody should upgrade.
24146 o Major bugfixes (compilation):
24147 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
24149 o Major bugfixes (crashes):
24150 - Try even harder not to dereference the first character after
24151 an mmap(). Reported by lodger.
24152 - Fix a crash bug in directory authorities when we re-number the
24153 routerlist while inserting a new router.
24154 - When the cached-routers file is an even multiple of the page size,
24155 don't run off the end and crash. (Fixes bug 455; based on idea
24157 - Fix eventdns.c behavior on Solaris: It is critical to include
24158 orconfig.h _before_ sys/types.h, so that we can get the expected
24159 definition of _FILE_OFFSET_BITS.
24161 o Major bugfixes (security):
24162 - Fix a possible buffer overrun when using BSD natd support. Bug
24164 - When sending destroy cells from a circuit's origin, don't include
24165 the reason for tearing down the circuit. The spec says we didn't,
24166 and now we actually don't. Reported by lodger.
24167 - Keep streamids from different exits on a circuit separate. This
24168 bug may have allowed other routers on a given circuit to inject
24169 cells into streams. Reported by lodger; fixes bug 446.
24170 - If there's a never-before-connected-to guard node in our list,
24171 never choose any guards past it. This way we don't expand our
24172 guard list unless we need to.
24174 o Minor bugfixes (guard nodes):
24175 - Weight guard selection by bandwidth, so that low-bandwidth nodes
24176 don't get overused as guards.
24178 o Minor bugfixes (directory):
24179 - Correctly count the number of authorities that recommend each
24180 version. Previously, we were under-counting by 1.
24181 - Fix a potential crash bug when we load many server descriptors at
24182 once and some of them make others of them obsolete. Fixes bug 458.
24184 o Minor bugfixes (hidden services):
24185 - Stop tearing down the whole circuit when the user asks for a
24186 connection to a port that the hidden service didn't configure.
24189 o Minor bugfixes (misc):
24190 - On Windows, we were preventing other processes from reading
24191 cached-routers while Tor was running. Reported by janbar.
24192 - Fix a possible (but very unlikely) bug in picking routers by
24193 bandwidth. Add a log message to confirm that it is in fact
24194 unlikely. Patch from lodger.
24195 - Backport a couple of memory leak fixes.
24196 - Backport miscellaneous cosmetic bugfixes.
24199 Changes in version 0.1.2.14 - 2007-05-25
24200 Tor 0.1.2.14 changes the addresses of two directory authorities (this
24201 change especially affects those who serve or use hidden services),
24202 and fixes several other crash- and security-related bugs.
24204 o Directory authority changes:
24205 - Two directory authorities (moria1 and moria2) just moved to new
24206 IP addresses. This change will particularly affect those who serve
24207 or use hidden services.
24209 o Major bugfixes (crashes):
24210 - If a directory server runs out of space in the connection table
24211 as it's processing a begin_dir request, it will free the exit stream
24212 but leave it attached to the circuit, leading to unpredictable
24213 behavior. (Reported by seeess, fixes bug 425.)
24214 - Fix a bug in dirserv_remove_invalid() that would cause authorities
24215 to corrupt memory under some really unlikely scenarios.
24216 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
24217 - Avoid segfaults when reading from mmaped descriptor file. (Reported
24220 o Major bugfixes (security):
24221 - When choosing an entry guard for a circuit, avoid using guards
24222 that are in the same family as the chosen exit -- not just guards
24223 that are exactly the chosen exit. (Reported by lodger.)
24225 o Major bugfixes (resource management):
24226 - If a directory authority is down, skip it when deciding where to get
24227 networkstatus objects or descriptors. Otherwise we keep asking
24228 every 10 seconds forever. Fixes bug 384.
24229 - Count it as a failure if we fetch a valid network-status but we
24230 don't want to keep it. Otherwise we'll keep fetching it and keep
24231 not wanting to keep it. Fixes part of bug 422.
24232 - If all of our dirservers have given us bad or no networkstatuses
24233 lately, then stop hammering them once per minute even when we
24234 think they're failed. Fixes another part of bug 422.
24237 - Actually set the purpose correctly for descriptors inserted with
24238 purpose=controller.
24239 - When we have k non-v2 authorities in our DirServer config,
24240 we ignored the last k authorities in the list when updating our
24242 - Correctly back-off from requesting router descriptors that we are
24243 having a hard time downloading.
24244 - Read resolv.conf files correctly on platforms where read() returns
24245 partial results on small file reads.
24246 - Don't rebuild the entire router store every time we get 32K of
24247 routers: rebuild it when the journal gets very large, or when
24248 the gaps in the store get very large.
24251 - When routers publish SVN revisions in their router descriptors,
24252 authorities now include those versions correctly in networkstatus
24254 - Warn when using a version of libevent before 1.3b to run a server on
24255 OSX or BSD: these versions interact badly with userspace threads.
24258 Changes in version 0.1.2.13 - 2007-04-24
24259 This release features some major anonymity fixes, such as safer path
24260 selection; better client performance; faster bootstrapping, better
24261 address detection, and better DNS support for servers; write limiting as
24262 well as read limiting to make servers easier to run; and a huge pile of
24263 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
24265 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
24266 of the Freenode IRC network, remembering his patience and vision for
24267 free speech on the Internet.
24269 o Major features, client performance:
24270 - Weight directory requests by advertised bandwidth. Now we can
24271 let servers enable write limiting but still allow most clients to
24272 succeed at their directory requests. (We still ignore weights when
24273 choosing a directory authority; I hope this is a feature.)
24274 - Stop overloading exit nodes -- avoid choosing them for entry or
24275 middle hops when the total bandwidth available from non-exit nodes
24276 is much higher than the total bandwidth available from exit nodes.
24277 - Rather than waiting a fixed amount of time between retrying
24278 application connections, we wait only 10 seconds for the first,
24279 10 seconds for the second, and 15 seconds for each retry after
24280 that. Hopefully this will improve the expected user experience.
24281 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
24282 to open a stream fails; now we do in more cases. This should
24283 make clients able to find a good exit faster in some cases, since
24284 unhandleable requests will now get an error rather than timing out.
24286 o Major features, client functionality:
24287 - Implement BEGIN_DIR cells, so we can connect to a directory
24288 server via TLS to do encrypted directory requests rather than
24289 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
24290 config options if you like. For now, this feature only works if
24291 you already have a descriptor for the destination dirserver.
24292 - Add support for transparent application connections: this basically
24293 bundles the functionality of trans-proxy-tor into the Tor
24294 mainline. Now hosts with compliant pf/netfilter implementations
24295 can redirect TCP connections straight to Tor without diverting
24296 through SOCKS. (Based on patch from tup.)
24297 - Add support for using natd; this allows FreeBSDs earlier than
24298 5.1.2 to have ipfw send connections through Tor without using
24299 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
24301 o Major features, servers:
24302 - Setting up a dyndns name for your server is now optional: servers
24303 with no hostname or IP address will learn their IP address by
24304 asking the directory authorities. This code only kicks in when you
24305 would normally have exited with a "no address" error. Nothing's
24306 authenticated, so use with care.
24307 - Directory servers now spool server descriptors, v1 directories,
24308 and v2 networkstatus objects to buffers as needed rather than en
24309 masse. They also mmap the cached-routers files. These steps save
24311 - Stop requiring clients to have well-formed certificates, and stop
24312 checking nicknames in certificates. (Clients have certificates so
24313 that they can look like Tor servers, but in the future we might want
24314 to allow them to look like regular TLS clients instead. Nicknames
24315 in certificates serve no purpose other than making our protocol
24316 easier to recognize on the wire.) Implements proposal 106.
24318 o Improvements on DNS support:
24319 - Add "eventdns" asynchronous dns library originally based on code
24320 from Adam Langley. Now we can discard the old rickety dnsworker
24321 concept, and support a wider variety of DNS functions. Allows
24322 multithreaded builds on NetBSD and OpenBSD again.
24323 - Add server-side support for "reverse" DNS lookups (using PTR
24324 records so clients can determine the canonical hostname for a given
24325 IPv4 address). Only supported by servers using eventdns; servers
24326 now announce in their descriptors if they don't support eventdns.
24327 - Workaround for name servers (like Earthlink's) that hijack failing
24328 DNS requests and replace the no-such-server answer with a "helpful"
24329 redirect to an advertising-driven search portal. Also work around
24330 DNS hijackers who "helpfully" decline to hijack known-invalid
24331 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
24332 lets you turn it off.
24333 - Servers now check for the case when common DNS requests are going to
24334 wildcarded addresses (i.e. all getting the same answer), and change
24335 their exit policy to reject *:* if it's happening.
24336 - When asked to resolve a hostname, don't use non-exit servers unless
24337 requested to do so. This allows servers with broken DNS to be
24338 useful to the network.
24339 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
24340 useless IPv6 DNS resolves.
24341 - Specify and implement client-side SOCKS5 interface for reverse DNS
24342 lookups (see doc/socks-extensions.txt). Also cache them.
24343 - When we change nameservers or IP addresses, reset and re-launch
24344 our tests for DNS hijacking.
24346 o Improvements on reachability testing:
24347 - Servers send out a burst of long-range padding cells once they've
24348 established that they're reachable. Spread them over 4 circuits,
24349 so hopefully a few will be fast. This exercises bandwidth and
24350 bootstraps them into the directory more quickly.
24351 - When we find our DirPort to be reachable, publish a new descriptor
24352 so we'll tell the world (reported by pnx).
24353 - Directory authorities now only decide that routers are reachable
24354 if their identity keys are as expected.
24355 - Do DirPort reachability tests less often, since a single test
24356 chews through many circuits before giving up.
24357 - Avoid some false positives during reachability testing: don't try
24358 to test via a server that's on the same /24 network as us.
24359 - Start publishing one minute or so after we find our ORPort
24360 to be reachable. This will help reduce the number of descriptors
24361 we have for ourselves floating around, since it's quite likely
24362 other things (e.g. DirPort) will change during that minute too.
24363 - Routers no longer try to rebuild long-term connections to directory
24364 authorities, and directory authorities no longer try to rebuild
24365 long-term connections to all servers. We still don't hang up
24366 connections in these two cases though -- we need to look at it
24367 more carefully to avoid flapping, and we likely need to wait til
24368 0.1.1.x is obsolete.
24370 o Improvements on rate limiting:
24371 - Enable write limiting as well as read limiting. Now we sacrifice
24372 capacity if we're pushing out lots of directory traffic, rather
24373 than overrunning the user's intended bandwidth limits.
24374 - Include TLS overhead when counting bandwidth usage; previously, we
24375 would count only the bytes sent over TLS, but not the bytes used
24377 - Servers decline directory requests much more aggressively when
24378 they're low on bandwidth. Otherwise they end up queueing more and
24379 more directory responses, which can't be good for latency.
24380 - But never refuse directory requests from local addresses.
24381 - Be willing to read or write on local connections (e.g. controller
24382 connections) even when the global rate limiting buckets are empty.
24383 - Flush local controller connection buffers periodically as we're
24384 writing to them, so we avoid queueing 4+ megabytes of data before
24386 - Revise and clean up the torrc.sample that we ship with; add
24387 a section for BandwidthRate and BandwidthBurst.
24389 o Major features, NT services:
24390 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
24391 command-line flag so that admins can override the default by saying
24392 "tor --service install --user "SomeUser"". This will not affect
24393 existing installed services. Also, warn the user that the service
24394 will look for its configuration file in the service user's
24395 %appdata% directory. (We can't do the "hardwire the user's appdata
24396 directory" trick any more, since we may not have read access to that
24398 - Support running the Tor service with a torrc not in the same
24399 directory as tor.exe and default to using the torrc located in
24400 the %appdata%\Tor\ of the user who installed the service. Patch
24402 - Add an --ignore-missing-torrc command-line option so that we can
24403 get the "use sensible defaults if the configuration file doesn't
24404 exist" behavior even when specifying a torrc location on the
24406 - When stopping an NT service, wait up to 10 sec for it to actually
24407 stop. (Patch from Matt Edman; resolves bug 295.)
24409 o Directory authority improvements:
24410 - Stop letting hibernating or obsolete servers affect uptime and
24412 - Stop listing hibernating servers in the v1 directory.
24413 - Authorities no longer recommend exits as guards if this would shift
24414 too much load to the exit nodes.
24415 - Authorities now specify server versions in networkstatus. This adds
24416 about 2% to the size of compressed networkstatus docs, and allows
24417 clients to tell which servers support BEGIN_DIR and which don't.
24418 The implementation is forward-compatible with a proposed future
24419 protocol version scheme not tied to Tor versions.
24420 - DirServer configuration lines now have an orport= option so
24421 clients can open encrypted tunnels to the authorities without
24422 having downloaded their descriptors yet. Enabled for moria1,
24423 moria2, tor26, and lefkada now in the default configuration.
24424 - Add a BadDirectory flag to network status docs so that authorities
24425 can (eventually) tell clients about caches they believe to be
24426 broken. Not used yet.
24427 - Allow authorities to list nodes as bad exits in their
24428 approved-routers file by fingerprint or by address. If most
24429 authorities set a BadExit flag for a server, clients don't think
24430 of it as a general-purpose exit. Clients only consider authorities
24431 that advertise themselves as listing bad exits.
24432 - Patch from Steve Hildrey: Generate network status correctly on
24433 non-versioning dirservers.
24434 - Have directory authorities allow larger amounts of drift in uptime
24435 without replacing the server descriptor: previously, a server that
24436 restarted every 30 minutes could have 48 "interesting" descriptors
24438 - Reserve the nickname "Unnamed" for routers that can't pick
24439 a hostname: any router can call itself Unnamed; directory
24440 authorities will never allocate Unnamed to any particular router;
24441 clients won't believe that any router is the canonical Unnamed.
24443 o Directory mirrors and clients:
24444 - Discard any v1 directory info that's over 1 month old (for
24445 directories) or over 1 week old (for running-routers lists).
24446 - Clients track responses with status 503 from dirservers. After a
24447 dirserver has given us a 503, we try not to use it until an hour has
24448 gone by, or until we have no dirservers that haven't given us a 503.
24449 - When we get a 503 from a directory, and we're not a server, we no
24450 longer count the failure against the total number of failures
24451 allowed for the object we're trying to download.
24452 - Prepare for servers to publish descriptors less often: never
24453 discard a descriptor simply for being too old until either it is
24454 recommended by no authorities, or until we get a better one for
24455 the same router. Make caches consider retaining old recommended
24456 routers for even longer.
24457 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
24458 headers for content, so that we can work better in the presence of
24459 caching HTTP proxies.
24460 - Stop fetching descriptors if you're not a dir mirror and you
24461 haven't tried to establish any circuits lately. (This currently
24462 causes some dangerous behavior, because when you start up again
24463 you'll use your ancient server descriptors.)
24465 o Major fixes, crashes:
24466 - Stop crashing when the controller asks us to resetconf more than
24467 one config option at once. (Vidalia 0.0.11 does this.)
24468 - Fix a longstanding obscure crash bug that could occur when we run
24469 out of DNS worker processes, if we're not using eventdns. (Resolves
24471 - Fix an assert that could trigger if a controller quickly set then
24472 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
24473 - Avoid crash when telling controller about stream-status and a
24474 stream is detached.
24475 - Avoid sending junk to controllers or segfaulting when a controller
24476 uses EVENT_NEW_DESC with verbose nicknames.
24477 - Stop triggering asserts if the controller tries to extend hidden
24478 service circuits (reported by mwenge).
24479 - If we start a server with ClientOnly 1, then set ClientOnly to 0
24480 and hup, stop triggering an assert based on an empty onion_key.
24481 - Mask out all signals in sub-threads; only the libevent signal
24482 handler should be processing them. This should prevent some crashes
24483 on some machines using pthreads. (Patch from coderman.)
24484 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
24486 o Major fixes, anonymity/security:
24487 - Automatically avoid picking more than one node from the same
24488 /16 network when constructing a circuit. Add an
24489 "EnforceDistinctSubnets" option to let people disable it if they
24490 want to operate private test networks on a single subnet.
24491 - When generating bandwidth history, round down to the nearest
24492 1k. When storing accounting data, round up to the nearest 1k.
24493 - When we're running as a server, remember when we last rotated onion
24494 keys, so that we will rotate keys once they're a week old even if
24495 we never stay up for a week ourselves.
24496 - If a client asked for a server by name, and there's a named server
24497 in our network-status but we don't have its descriptor yet, we
24498 could return an unnamed server instead.
24499 - Reject (most) attempts to use Tor circuits with length one. (If
24500 many people start using Tor as a one-hop proxy, exit nodes become
24501 a more attractive target for compromise.)
24502 - Just because your DirPort is open doesn't mean people should be
24503 able to remotely teach you about hidden service descriptors. Now
24504 only accept rendezvous posts if you've got HSAuthoritativeDir set.
24505 - Fix a potential race condition in the rpm installer. Found by
24507 - Do not log IPs with TLS failures for incoming TLS
24508 connections. (Fixes bug 382.)
24510 o Major fixes, other:
24511 - If our system clock jumps back in time, don't publish a negative
24512 uptime in the descriptor.
24513 - When we start during an accounting interval before it's time to wake
24514 up, remember to wake up at the correct time. (May fix bug 342.)
24515 - Previously, we would cache up to 16 old networkstatus documents
24516 indefinitely, if they came from nontrusted authorities. Now we
24517 discard them if they are more than 10 days old.
24518 - When we have a state file we cannot parse, tell the user and
24519 move it aside. Now we avoid situations where the user starts
24520 Tor in 1904, Tor writes a state file with that timestamp in it,
24521 the user fixes her clock, and Tor refuses to start.
24522 - Publish a new descriptor after we hup/reload. This is important
24523 if our config has changed such that we'll want to start advertising
24524 our DirPort now, etc.
24525 - If we are using an exit enclave and we can't connect, e.g. because
24526 its webserver is misconfigured to not listen on localhost, then
24527 back off and try connecting from somewhere else before we fail.
24529 o New config options or behaviors:
24530 - When EntryNodes are configured, rebuild the guard list to contain,
24531 in order: the EntryNodes that were guards before; the rest of the
24532 EntryNodes; the nodes that were guards before.
24533 - Do not warn when individual nodes in the configuration's EntryNodes,
24534 ExitNodes, etc are down: warn only when all possible nodes
24535 are down. (Fixes bug 348.)
24536 - Put a lower-bound on MaxAdvertisedBandwidth.
24537 - Start using the state file to store bandwidth accounting data:
24538 the bw_accounting file is now obsolete. We'll keep generating it
24539 for a while for people who are still using 0.1.2.4-alpha.
24540 - Try to batch changes to the state file so that we do as few
24541 disk writes as possible while still storing important things in
24543 - The state file and the bw_accounting file get saved less often when
24544 the AvoidDiskWrites config option is set.
24545 - Make PIDFile work on Windows.
24546 - Add internal descriptions for a bunch of configuration options:
24547 accessible via controller interface and in comments in saved
24549 - Reject *:563 (NNTPS) in the default exit policy. We already reject
24550 NNTP by default, so this seems like a sensible addition.
24551 - Clients now reject hostnames with invalid characters. This should
24552 avoid some inadvertent info leaks. Add an option
24553 AllowNonRFC953Hostnames to disable this behavior, in case somebody
24554 is running a private network with hosts called @, !, and #.
24555 - Check for addresses with invalid characters at the exit as well,
24556 and warn less verbosely when they fail. You can override this by
24557 setting ServerDNSAllowNonRFC953Addresses to 1.
24558 - Remove some options that have been deprecated since at least
24559 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
24560 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
24561 to set log options. Mark PathlenCoinWeight as obsolete.
24562 - Stop accepting certain malformed ports in configured exit policies.
24563 - When the user uses bad syntax in the Log config line, stop
24564 suggesting other bad syntax as a replacement.
24565 - Add new config option "ResolvConf" to let the server operator
24566 choose an alternate resolve.conf file when using eventdns.
24567 - If one of our entry guards is on the ExcludeNodes list, or the
24568 directory authorities don't think it's a good guard, treat it as
24569 if it were unlisted: stop using it as a guard, and throw it off
24570 the guards list if it stays that way for a long time.
24571 - Allow directory authorities to be marked separately as authorities
24572 for the v1 directory protocol, the v2 directory protocol, and
24573 as hidden service directories, to make it easier to retire old
24574 authorities. V1 authorities should set "HSAuthoritativeDir 1"
24575 to continue being hidden service authorities too.
24576 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
24577 - Make TrackExitHosts case-insensitive, and fix the behavior of
24578 ".suffix" TrackExitHosts items to avoid matching in the middle of
24580 - New DirPort behavior: if you have your dirport set, you download
24581 descriptors aggressively like a directory mirror, whether or not
24582 your ORPort is set.
24585 - Create a new file ReleaseNotes which was the old ChangeLog. The
24586 new ChangeLog file now includes the notes for all development
24588 - Add a new address-spec.txt document to describe our special-case
24589 addresses: .exit, .onion, and .noconnnect.
24590 - Fork the v1 directory protocol into its own spec document,
24591 and mark dir-spec.txt as the currently correct (v2) spec.
24593 o Packaging, porting, and contrib
24594 - "tor --verify-config" now exits with -1(255) or 0 depending on
24595 whether the config options are bad or good.
24596 - The Debian package now uses --verify-config when (re)starting,
24597 to distinguish configuration errors from other errors.
24598 - Adapt a patch from goodell to let the contrib/exitlist script
24599 take arguments rather than require direct editing.
24600 - Prevent the contrib/exitlist script from printing the same
24601 result more than once.
24602 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
24603 - In the hidden service example in torrc.sample, stop recommending
24604 esoteric and discouraged hidden service options.
24605 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
24606 values before failing, and always enables eventdns.
24607 - Try to detect Windows correctly when cross-compiling.
24608 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
24609 Try to fix this in configure.in by checking for most functions
24610 before we check for libevent.
24611 - Update RPMs to require libevent 1.2.
24612 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
24613 or later. Log when we are doing this, so we can diagnose it when
24614 it fails. (Also, recommend libevent 1.1b for kqueue and
24615 win32 methods; deprecate libevent 1.0b harder; make libevent
24616 recommendation system saner.)
24617 - Build with recent (1.3+) libevents on platforms that do not
24618 define the nonstandard types "u_int8_t" and friends.
24619 - Remove architecture from OS X builds. The official builds are
24620 now universal binaries.
24621 - Run correctly on OS X platforms with case-sensitive filesystems.
24622 - Correctly set maximum connection limit on Cygwin. (This time
24624 - Start compiling on MinGW on Windows (patches from Mike Chiussi
24626 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
24627 - Finally fix the openssl warnings from newer gccs that believe that
24628 ignoring a return value is okay, but casting a return value and
24629 then ignoring it is a sign of madness.
24630 - On architectures where sizeof(int)>4, still clamp declarable
24631 bandwidth to INT32_MAX.
24633 o Minor features, controller:
24634 - Warn the user when an application uses the obsolete binary v0
24635 control protocol. We're planning to remove support for it during
24636 the next development series, so it's good to give people some
24638 - Add STREAM_BW events to report per-entry-stream bandwidth
24639 use. (Patch from Robert Hogan.)
24640 - Rate-limit SIGNEWNYM signals in response to controllers that
24641 impolitely generate them for every single stream. (Patch from
24642 mwenge; closes bug 394.)
24643 - Add a REMAP status to stream events to note that a stream's
24644 address has changed because of a cached address or a MapAddress
24646 - Make REMAP stream events have a SOURCE (cache or exit), and
24647 make them generated in every case where we get a successful
24648 connected or resolved cell.
24649 - Track reasons for OR connection failure; make these reasons
24650 available via the controller interface. (Patch from Mike Perry.)
24651 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
24652 can learn when clients are sending malformed hostnames to Tor.
24653 - Specify and implement some of the controller status events.
24654 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
24655 - Reimplement GETINFO so that info/names stays in sync with the
24657 - Implement "GETINFO fingerprint".
24658 - Implement "SETEVENTS GUARD" so controllers can get updates on
24659 entry guard status as it changes.
24660 - Make all connections to addresses of the form ".noconnect"
24661 immediately get closed. This lets application/controller combos
24662 successfully test whether they're talking to the same Tor by
24663 watching for STREAM events.
24664 - Add a REASON field to CIRC events; for backward compatibility, this
24665 field is sent only to controllers that have enabled the extended
24666 event format. Also, add additional reason codes to explain why
24667 a given circuit has been destroyed or truncated. (Patches from
24669 - Add a REMOTE_REASON field to extended CIRC events to tell the
24670 controller why a remote OR told us to close a circuit.
24671 - Stream events also now have REASON and REMOTE_REASON fields,
24672 working much like those for circuit events.
24673 - There's now a GETINFO ns/... field so that controllers can ask Tor
24674 about the current status of a router.
24675 - A new event type "NS" to inform a controller when our opinion of
24676 a router's status has changed.
24677 - Add a GETINFO events/names and GETINFO features/names so controllers
24678 can tell which events and features are supported.
24679 - A new CLEARDNSCACHE signal to allow controllers to clear the
24680 client-side DNS cache without expiring circuits.
24681 - Fix CIRC controller events so that controllers can learn the
24682 identity digests of non-Named servers used in circuit paths.
24683 - Let controllers ask for more useful identifiers for servers. Instead
24684 of learning identity digests for un-Named servers and nicknames
24685 for Named servers, the new identifiers include digest, nickname,
24686 and indication of Named status. Off by default; see control-spec.txt
24687 for more information.
24688 - Add a "getinfo address" controller command so it can display Tor's
24689 best guess to the user.
24690 - New controller event to alert the controller when our server
24691 descriptor has changed.
24692 - Give more meaningful errors on controller authentication failure.
24693 - Export the default exit policy via the control port, so controllers
24694 don't need to guess what it is / will be later.
24696 o Minor bugfixes, controller:
24697 - When creating a circuit via the controller, send a 'launched'
24698 event when we're done, so we follow the spec better.
24699 - Correct the control spec to match how the code actually responds
24700 to 'getinfo addr-mappings/*'. Reported by daejees.
24701 - The control spec described a GUARDS event, but the code
24702 implemented a GUARD event. Standardize on GUARD, but let people
24703 ask for GUARDS too. Reported by daejees.
24704 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
24705 clear the corresponding on_circuit variable, and remember later
24706 that we don't need to send a redundant CLOSED event. (Resolves part
24708 - Report events where a resolve succeeded or where we got a socks
24709 protocol error correctly, rather than calling both of them
24711 - Change reported stream target addresses to IP consistently when
24712 we finally get the IP from an exit node.
24713 - Send log messages to the controller even if they happen to be very
24715 - Flush ERR-level controller status events just like we currently
24716 flush ERR-level log events, so that a Tor shutdown doesn't prevent
24717 the controller from learning about current events.
24718 - Report the circuit number correctly in STREAM CLOSED events. Bug
24719 reported by Mike Perry.
24720 - Do not report bizarre values for results of accounting GETINFOs
24721 when the last second's write or read exceeds the allotted bandwidth.
24722 - Report "unrecognized key" rather than an empty string when the
24723 controller tries to fetch a networkstatus that doesn't exist.
24724 - When the controller does a "GETINFO network-status", tell it
24725 about even those routers whose descriptors are very old, and use
24726 long nicknames where appropriate.
24727 - Fix handling of verbose nicknames with ORCONN controller events:
24728 make them show up exactly when requested, rather than exactly when
24730 - Controller signals now work on non-Unix platforms that don't define
24731 SIGUSR1 and SIGUSR2 the way we expect.
24732 - Respond to SIGNAL command before we execute the signal, in case
24733 the signal shuts us down. Suggested by Karsten Loesing.
24734 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
24736 o Minor features, code performance:
24737 - Major performance improvement on inserting descriptors: change
24738 algorithm from O(n^2) to O(n).
24739 - Do not rotate onion key immediately after setting it for the first
24741 - Call router_have_min_dir_info half as often. (This is showing up in
24742 some profiles, but not others.)
24743 - When using GCC, make log_debug never get called at all, and its
24744 arguments never get evaluated, when no debug logs are configured.
24745 (This is showing up in some profiles, but not others.)
24746 - Statistics dumped by -USR2 now include a breakdown of public key
24747 operations, for profiling.
24748 - Make the common memory allocation path faster on machines where
24749 malloc(0) returns a pointer.
24750 - Split circuit_t into origin_circuit_t and or_circuit_t, and
24751 split connection_t into edge, or, dir, control, and base structs.
24752 These will save quite a bit of memory on busy servers, and they'll
24753 also help us track down bugs in the code and bugs in the spec.
24754 - Use OpenSSL's AES implementation on platforms where it's faster.
24755 This could save us as much as 10% CPU usage.
24757 o Minor features, descriptors and descriptor handling:
24758 - Avoid duplicate entries on MyFamily line in server descriptor.
24759 - When Tor receives a router descriptor that it asked for, but
24760 no longer wants (because it has received fresh networkstatuses
24761 in the meantime), do not warn the user. Cache the descriptor if
24762 we're a cache; drop it if we aren't.
24763 - Servers no longer ever list themselves in their "family" line,
24764 even if configured to do so. This makes it easier to configure
24765 family lists conveniently.
24767 o Minor fixes, confusing/misleading log messages:
24768 - Display correct results when reporting which versions are
24769 recommended, and how recommended they are. (Resolves bug 383.)
24770 - Inform the server operator when we decide not to advertise a
24771 DirPort due to AccountingMax enabled or a low BandwidthRate.
24772 - Only include function names in log messages for info/debug messages.
24773 For notice/warn/err, the content of the message should be clear on
24774 its own, and printing the function name only confuses users.
24775 - Remove even more protocol-related warnings from Tor server logs,
24776 such as bad TLS handshakes and malformed begin cells.
24777 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
24778 when the IP address is mapped through MapAddress to a hostname.
24779 - Fix misleading log messages: an entry guard that is "unlisted",
24780 as well as not known to be "down" (because we've never heard
24781 of it), is not therefore "up".
24783 o Minor fixes, old/obsolete behavior:
24784 - Start assuming we can use a create_fast cell if we don't know
24785 what version a router is running.
24786 - We no longer look for identity and onion keys in "identity.key" and
24787 "onion.key" -- these were replaced by secret_id_key and
24788 secret_onion_key in 0.0.8pre1.
24789 - We no longer require unrecognized directory entries to be
24791 - Drop compatibility with obsolete Tors that permit create cells
24792 to have the wrong circ_id_type.
24793 - Remove code to special-case "-cvs" ending, since it has not
24794 actually mattered since 0.0.9.
24795 - Don't re-write the fingerprint file every restart, unless it has
24798 o Minor fixes, misc client-side behavior:
24799 - Always remove expired routers and networkstatus docs before checking
24800 whether we have enough information to build circuits. (Fixes
24802 - When computing clock skew from directory HTTP headers, consider what
24803 time it was when we finished asking for the directory, not what
24805 - Make our socks5 handling more robust to broken socks clients:
24806 throw out everything waiting on the buffer in between socks
24807 handshake phases, since they can't possibly (so the theory
24808 goes) have predicted what we plan to respond to them.
24809 - Expire socks connections if they spend too long waiting for the
24810 handshake to finish. Previously we would let them sit around for
24811 days, if the connecting application didn't close them either.
24812 - And if the socks handshake hasn't started, don't send a
24813 "DNS resolve socks failed" handshake reply; just close it.
24814 - If the user asks to use invalid exit nodes, be willing to use
24816 - Track unreachable entry guards correctly: don't conflate
24817 'unreachable by us right now' with 'listed as down by the directory
24818 authorities'. With the old code, if a guard was unreachable by us
24819 but listed as running, it would clog our guard list forever.
24820 - Behave correctly in case we ever have a network with more than
24821 2GB/s total advertised capacity.
24822 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
24823 - Fix a memory leak when we ask for "all" networkstatuses and we
24824 get one we don't recognize.
24827 Changes in version 0.1.1.26 - 2006-12-14
24828 o Security bugfixes:
24829 - Stop sending the HttpProxyAuthenticator string to directory
24830 servers when directory connections are tunnelled through Tor.
24831 - Clients no longer store bandwidth history in the state file.
24832 - Do not log introduction points for hidden services if SafeLogging
24836 - Fix an assert failure when a directory authority sets
24837 AuthDirRejectUnlisted and then receives a descriptor from an
24838 unlisted router (reported by seeess).
24841 Changes in version 0.1.1.25 - 2006-11-04
24843 - When a client asks us to resolve (rather than connect to)
24844 an address, and we have a cached answer, give them the cached
24845 answer. Previously, we would give them no answer at all.
24846 - We were building exactly the wrong circuits when we predict
24847 hidden service requirements, meaning Tor would have to build all
24848 its circuits on demand.
24849 - If none of our live entry guards have a high uptime, but we
24850 require a guard with a high uptime, try adding a new guard before
24851 we give up on the requirement. This patch should make long-lived
24852 connections more stable on average.
24853 - When testing reachability of our DirPort, don't launch new
24854 tests when there's already one in progress -- unreachable
24855 servers were stacking up dozens of testing streams.
24857 o Security bugfixes:
24858 - When the user sends a NEWNYM signal, clear the client-side DNS
24859 cache too. Otherwise we continue to act on previous information.
24862 - Avoid a memory corruption bug when creating a hash table for
24864 - Avoid possibility of controller-triggered crash when misusing
24865 certain commands from a v0 controller on platforms that do not
24866 handle printf("%s",NULL) gracefully.
24867 - Avoid infinite loop on unexpected controller input.
24868 - Don't log spurious warnings when we see a circuit close reason we
24869 don't recognize; it's probably just from a newer version of Tor.
24870 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24871 Tor/Privoxy we also uninstall Vidalia.
24874 Changes in version 0.1.1.24 - 2006-09-29
24876 - Allow really slow clients to not hang up five minutes into their
24877 directory downloads (suggested by Adam J. Richter).
24878 - Fix major performance regression from 0.1.0.x: instead of checking
24879 whether we have enough directory information every time we want to
24880 do something, only check when the directory information has changed.
24881 This should improve client CPU usage by 25-50%.
24882 - Don't crash if, after a server has been running for a while,
24883 it can't resolve its hostname.
24884 - When a client asks us to resolve (not connect to) an address,
24885 and we have a cached answer, give them the cached answer.
24886 Previously, we would give them no answer at all.
24889 - Allow Tor to start when RunAsDaemon is set but no logs are set.
24890 - Don't crash when the controller receives a third argument to an
24891 "extendcircuit" request.
24892 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
24893 response; fix error code when "getinfo dir/status/" fails.
24894 - Fix configure.in to not produce broken configure files with
24895 more recent versions of autoconf. Thanks to Clint for his auto*
24897 - Fix security bug on NetBSD that could allow someone to force
24898 uninitialized RAM to be sent to a server's DNS resolver. This
24899 only affects NetBSD and other platforms that do not bounds-check
24901 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
24902 methods: these are known to be buggy.
24903 - If we're a directory mirror and we ask for "all" network status
24904 documents, we would discard status documents from authorities
24905 we don't recognize.
24908 Changes in version 0.1.1.23 - 2006-07-30
24910 - Fast Tor servers, especially exit nodes, were triggering asserts
24911 due to a bug in handling the list of pending DNS resolves. Some
24912 bugs still remain here; we're hunting them.
24913 - Entry guards could crash clients by sending unexpected input.
24914 - More fixes on reachability testing: if you find yourself reachable,
24915 then don't ever make any client requests (so you stop predicting
24916 circuits), then hup or have your clock jump, then later your IP
24917 changes, you won't think circuits are working, so you won't try to
24918 test reachability, so you won't publish.
24921 - Avoid a crash if the controller does a resetconf firewallports
24922 and then a setconf fascistfirewall=1.
24923 - Avoid an integer underflow when the dir authority decides whether
24924 a router is stable: we might wrongly label it stable, and compute
24925 a slightly wrong median stability, when a descriptor is published
24927 - Fix a place where we might trigger an assert if we can't build our
24928 own server descriptor yet.
24931 Changes in version 0.1.1.22 - 2006-07-05
24933 - Fix a big bug that was causing servers to not find themselves
24934 reachable if they changed IP addresses. Since only 0.1.1.22+
24935 servers can do reachability testing correctly, now we automatically
24936 make sure to test via one of these.
24937 - Fix to allow clients and mirrors to learn directory info from
24938 descriptor downloads that get cut off partway through.
24939 - Directory authorities had a bug in deciding if a newly published
24940 descriptor was novel enough to make everybody want a copy -- a few
24941 servers seem to be publishing new descriptors many times a minute.
24943 - Fix a rare bug that was causing some servers to complain about
24944 "closing wedged cpuworkers" and skip some circuit create requests.
24945 - Make the Exit flag in directory status documents actually work.
24948 Changes in version 0.1.1.21 - 2006-06-10
24949 o Crash and assert fixes from 0.1.1.20:
24950 - Fix a rare crash on Tor servers that have enabled hibernation.
24951 - Fix a seg fault on startup for Tor networks that use only one
24952 directory authority.
24953 - Fix an assert from a race condition that occurs on Tor servers
24954 while exiting, where various threads are trying to log that they're
24955 exiting, and delete the logs, at the same time.
24956 - Make our unit tests pass again on certain obscure platforms.
24959 - Add support for building SUSE RPM packages.
24960 - Speed up initial bootstrapping for clients: if we are making our
24961 first ever connection to any entry guard, then don't mark it down
24963 - When only one Tor server in the network is labelled as a guard,
24964 and we've already picked him, we would cycle endlessly picking him
24965 again, being unhappy about it, etc. Now we specifically exclude
24966 current guards when picking a new guard.
24967 - Servers send create cells more reliably after the TLS connection
24968 is established: we were sometimes forgetting to send half of them
24969 when we had more than one pending.
24970 - If we get a create cell that asks us to extend somewhere, but the
24971 Tor server there doesn't match the expected digest, we now send
24972 a destroy cell back, rather than silently doing nothing.
24973 - Make options->RedirectExit work again.
24974 - Make cookie authentication for the controller work again.
24975 - Stop being picky about unusual characters in the arguments to
24976 mapaddress. It's none of our business.
24977 - Add a new config option "TestVia" that lets you specify preferred
24978 middle hops to use for test circuits. Perhaps this will let me
24979 debug the reachability problems better.
24981 o Log / documentation fixes:
24982 - If we're a server and some peer has a broken TLS certificate, don't
24983 log about it unless ProtocolWarnings is set, i.e., we want to hear
24984 about protocol violations by others.
24985 - Fix spelling of VirtualAddrNetwork in man page.
24986 - Add a better explanation at the top of the autogenerated torrc file
24987 about what happened to our old torrc.
24990 Changes in version 0.1.1.20 - 2006-05-23
24991 o Crash and assert fixes from 0.1.0.17:
24992 - Fix assert bug in close_logs() on exit: when we close and delete
24993 logs, remove them all from the global "logfiles" list.
24994 - Fix an assert error when we're out of space in the connection_list
24995 and we try to post a hidden service descriptor (reported by Peter
24997 - Fix a rare assert error when we've tried all intro points for
24998 a hidden service and we try fetching the service descriptor again:
24999 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
25000 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
25001 out and refuse the setconf if it would fail.
25002 - If you specify a relative torrc path and you set RunAsDaemon in
25003 your torrc, then it chdir()'s to the new directory. If you then
25004 HUP, it tries to load the new torrc location, fails, and exits.
25005 The fix: no longer allow a relative path to torrc when using -f.
25006 - Check for integer overflows in more places, when adding elements
25007 to smartlists. This could possibly prevent a buffer overflow
25008 on malicious huge inputs.
25010 o Security fixes, major:
25011 - When we're printing strings from the network, don't try to print
25012 non-printable characters. Now we're safer against shell escape
25013 sequence exploits, and also against attacks to fool users into
25014 misreading their logs.
25015 - Implement entry guards: automatically choose a handful of entry
25016 nodes and stick with them for all circuits. Only pick new guards
25017 when the ones you have are unsuitable, and if the old guards
25018 become suitable again, switch back. This will increase security
25019 dramatically against certain end-point attacks. The EntryNodes
25020 config option now provides some hints about which entry guards you
25021 want to use most; and StrictEntryNodes means to only use those.
25022 Fixes CVE-2006-0414.
25023 - Implement exit enclaves: if we know an IP address for the
25024 destination, and there's a running Tor server at that address
25025 which allows exit to the destination, then extend the circuit to
25026 that exit first. This provides end-to-end encryption and end-to-end
25027 authentication. Also, if the user wants a .exit address or enclave,
25028 use 4 hops rather than 3, and cannibalize a general circ for it
25030 - Obey our firewall options more faithfully:
25031 . If we can't get to a dirserver directly, try going via Tor.
25032 . Don't ever try to connect (as a client) to a place our
25033 firewall options forbid.
25034 . If we specify a proxy and also firewall options, obey the
25035 firewall options even when we're using the proxy: some proxies
25036 can only proxy to certain destinations.
25037 - Make clients regenerate their keys when their IP address changes.
25038 - For the OS X package's modified privoxy config file, comment
25039 out the "logfile" line so we don't log everything passed
25041 - Our TLS handshakes were generating a single public/private
25042 keypair for the TLS context, rather than making a new one for
25043 each new connection. Oops. (But we were still rotating them
25044 periodically, so it's not so bad.)
25045 - When we were cannibalizing a circuit with a particular exit
25046 node in mind, we weren't checking to see if that exit node was
25047 already present earlier in the circuit. Now we are.
25048 - Require server descriptors to list IPv4 addresses -- hostnames
25049 are no longer allowed. This also fixes potential vulnerabilities
25050 to servers providing hostnames as their address and then
25051 preferentially resolving them so they can partition users.
25052 - Our logic to decide if the OR we connected to was the right guy
25053 was brittle and maybe open to a mitm for invalid routers.
25055 o Security fixes, minor:
25056 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
25057 Ian Goldberg can prove things about our handshake protocol more
25059 - Make directory authorities generate a separate "guard" flag to
25060 mean "would make a good entry guard". Clients now honor the
25061 is_guard flag rather than looking at is_fast or is_stable.
25062 - Try to list MyFamily elements by key, not by nickname, and warn
25063 if we've not heard of a server.
25064 - Start using RAND_bytes rather than RAND_pseudo_bytes from
25065 OpenSSL. Also, reseed our entropy every hour, not just at
25066 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
25067 - Refuse server descriptors where the fingerprint line doesn't match
25068 the included identity key. Tor doesn't care, but other apps (and
25069 humans) might actually be trusting the fingerprint line.
25070 - We used to kill the circuit when we receive a relay command we
25071 don't recognize. Now we just drop that cell.
25072 - Fix a bug found by Lasse Overlier: when we were making internal
25073 circuits (intended to be cannibalized later for rendezvous and
25074 introduction circuits), we were picking them so that they had
25075 useful exit nodes. There was no need for this, and it actually
25076 aids some statistical attacks.
25077 - Start treating internal circuits and exit circuits separately.
25078 It's important to keep them separate because internal circuits
25079 have their last hops picked like middle hops, rather than like
25080 exit hops. So exiting on them will break the user's expectations.
25081 - Fix a possible way to DoS dirservers.
25082 - When the client asked for a rendezvous port that the hidden
25083 service didn't want to provide, we were sending an IP address
25084 back along with the end cell. Fortunately, it was zero. But stop
25087 o Packaging improvements:
25088 - Implement --with-libevent-dir option to ./configure. Improve
25089 search techniques to find libevent, and use those for openssl too.
25090 - Fix a couple of bugs in OpenSSL detection. Deal better when
25091 there are multiple SSLs installed with different versions.
25092 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
25093 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
25095 - Make unit tests (and other invocations that aren't the real Tor)
25096 run without launching listeners, creating subdirectories, and so on.
25097 - The OS X installer was adding a symlink for tor_resolve but
25098 the binary was called tor-resolve (reported by Thomas Hardly).
25099 - Now we can target arch and OS in rpm builds (contributed by
25100 Phobos). Also make the resulting dist-rpm filename match the
25102 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
25103 if you log to syslog and want something other than LOG_DAEMON.
25104 - Fix the torify (tsocks) config file to not use Tor for localhost
25106 - Start shipping socks-extensions.txt, tor-doc-unix.html,
25107 tor-doc-server.html, and stylesheet.css in the tarball.
25108 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
25109 They are useless now.
25110 - Add Peter Palfrader's contributed check-tor script. It lets you
25111 easily check whether a given server (referenced by nickname)
25112 is reachable by you.
25113 - Add BSD-style contributed startup script "rc.subr" from Peter
25116 o Directory improvements -- new directory protocol:
25117 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
25118 - Authorities and caches publish individual descriptors (by
25119 digest, by fingerprint, by "all", and by "tell me yours").
25120 - Clients don't download or use the old directory anymore. Now they
25121 download network-statuses from the directory authorities, and
25122 fetch individual server descriptors as needed from mirrors.
25123 - Clients don't download descriptors of non-running servers.
25124 - Download descriptors by digest, not by fingerprint. Caches try to
25125 download all listed digests from authorities; clients try to
25126 download "best" digests from caches. This avoids partitioning
25127 and isolating attacks better.
25128 - Only upload a new server descriptor when options change, 18
25129 hours have passed, uptime is reset, or bandwidth changes a lot.
25130 - Directory authorities silently throw away new descriptors that
25131 haven't changed much if the timestamps are similar. We do this to
25132 tolerate older Tor servers that upload a new descriptor every 15
25133 minutes. (It seemed like a good idea at the time.)
25134 - Clients choose directory servers from the network status lists,
25135 not from their internal list of router descriptors. Now they can
25136 go to caches directly rather than needing to go to authorities
25137 to bootstrap the first set of descriptors.
25138 - When picking a random directory, prefer non-authorities if any
25140 - Add a new flag to network-status indicating whether the server
25141 can answer v2 directory requests too.
25142 - Directory mirrors now cache up to 16 unrecognized network-status
25143 docs, so new directory authorities will be cached too.
25144 - Stop parsing, storing, or using running-routers output (but
25145 mirrors still cache and serve it).
25146 - Clients consider a threshold of "versioning" directory authorities
25147 before deciding whether to warn the user that he's obsolete.
25148 - Authorities publish separate sorted lists of recommended versions
25149 for clients and for servers.
25150 - Change DirServers config line to note which dirs are v1 authorities.
25151 - Put nicknames on the DirServer line, so we can refer to them
25152 without requiring all our users to memorize their IP addresses.
25153 - Remove option when getting directory cache to see whether they
25154 support running-routers; they all do now. Replace it with one
25155 to see whether caches support v2 stuff.
25156 - Stop listing down or invalid nodes in the v1 directory. This
25157 reduces its bulk by about 1/3, and reduces load on mirrors.
25158 - Mirrors no longer cache the v1 directory as often.
25159 - If we as a directory mirror don't know of any v1 directory
25160 authorities, then don't try to cache any v1 directories.
25162 o Other directory improvements:
25163 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
25164 fifth authoritative directory servers.
25165 - Directory authorities no longer require an open connection from
25166 a server to consider him "reachable". We need this change because
25167 when we add new directory authorities, old servers won't know not
25168 to hang up on them.
25169 - Dir authorities now do their own external reachability testing
25170 of each server, and only list as running the ones they found to
25171 be reachable. We also send back warnings to the server's logs if
25172 it uploads a descriptor that we already believe is unreachable.
25173 - Spread the directory authorities' reachability testing over the
25174 entire testing interval, so we don't try to do 500 TLS's at once
25176 - Make the "stable" router flag in network-status be the median of
25177 the uptimes of running valid servers, and make clients pay
25178 attention to the network-status flags. Thus the cutoff adapts
25179 to the stability of the network as a whole, making IRC, IM, etc
25180 connections more reliable.
25181 - Make the v2 dir's "Fast" flag based on relative capacity, just
25182 like "Stable" is based on median uptime. Name everything in the
25183 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
25184 - Retry directory requests if we fail to get an answer we like
25185 from a given dirserver (we were retrying before, but only if
25186 we fail to connect).
25187 - Return a robots.txt on our dirport to discourage google indexing.
25189 o Controller protocol improvements:
25190 - Revised controller protocol (version 1) that uses ascii rather
25191 than binary: tor/doc/control-spec.txt. Add supporting libraries
25192 in python and java and c# so you can use the controller from your
25193 applications without caring how our protocol works.
25194 - Allow the DEBUG controller event to work again. Mark certain log
25195 entries as "don't tell this to controllers", so we avoid cycles.
25196 - New controller function "getinfo accounting", to ask how
25197 many bytes we've used in this time period.
25198 - Add a "resetconf" command so you can set config options like
25199 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
25200 a config option in the torrc with no value, then it clears it
25201 entirely (rather than setting it to its default).
25202 - Add a "getinfo config-file" to tell us where torrc is. Also
25203 expose guard nodes, config options/names.
25204 - Add a "quit" command (when when using the controller manually).
25205 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
25206 stop using any currently-dirty circuits for new streams, so we
25207 don't link new actions to old actions. This also occurs on HUP
25208 or "signal reload".
25209 - If we would close a stream early (e.g. it asks for a .exit that
25210 we know would refuse it) but the LeaveStreamsUnattached config
25211 option is set by the controller, then don't close it.
25212 - Add a new controller event type "authdir_newdescs" that allows
25213 controllers to get all server descriptors that were uploaded to
25214 a router in its role as directory authority.
25215 - New controller option "getinfo desc/all-recent" to fetch the
25216 latest server descriptor for every router that Tor knows about.
25217 - Fix the controller's "attachstream 0" command to treat conn like
25218 it just connected, doing address remapping, handling .exit and
25219 .onion idioms, and so on. Now we're more uniform in making sure
25220 that the controller hears about new and closing connections.
25221 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
25222 the controller. Also, rotate dns and cpu workers if the controller
25223 changes options that will affect them; and initialize the dns
25224 worker cache tree whether or not we start out as a server.
25225 - Add a new circuit purpose 'controller' to let the controller ask
25226 for a circuit that Tor won't try to use. Extend the "extendcircuit"
25227 controller command to let you specify the purpose if you're starting
25228 a new circuit. Add a new "setcircuitpurpose" controller command to
25229 let you change a circuit's purpose after it's been created.
25230 - Let the controller ask for "getinfo dir/server/foo" so it can ask
25231 directly rather than connecting to the dir port. "getinfo
25232 dir/status/foo" also works, but currently only if your DirPort
25234 - Let the controller tell us about certain router descriptors
25235 that it doesn't want Tor to use in circuits. Implement
25236 "setrouterpurpose" and modify "+postdescriptor" to do this.
25237 - If the controller's *setconf commands fail, collect an error
25238 message in a string and hand it back to the controller -- don't
25239 just tell them to go read their logs.
25241 o Scalability, resource management, and performance:
25242 - Fix a major load balance bug: we were round-robin reading in 16 KB
25243 chunks, and servers with bandwidthrate of 20 KB, while downloading
25244 a 600 KB directory, would starve their other connections. Now we
25245 try to be a bit more fair.
25246 - Be more conservative about whether to advertise our DirPort.
25247 The main change is to not advertise if we're running at capacity
25248 and either a) we could hibernate ever or b) our capacity is low
25249 and we're using a default DirPort.
25250 - We weren't cannibalizing circuits correctly for
25251 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
25252 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
25253 build those from scratch. This should make hidden services faster.
25254 - Predict required circuits better, with an eye toward making hidden
25255 services faster on the service end.
25256 - Compress exit policies even more: look for duplicate lines and
25258 - Generate 18.0.0.0/8 address policy format in descs when we can;
25259 warn when the mask is not reducible to a bit-prefix.
25260 - There used to be two ways to specify your listening ports in a
25261 server descriptor: on the "router" line and with a separate "ports"
25262 line. Remove support for the "ports" line.
25263 - Reduce memory requirements in our structs by changing the order
25264 of fields. Replace balanced trees with hash tables. Inline
25265 bottleneck smartlist functions. Add a "Map from digest to void*"
25266 abstraction so we can do less hex encoding/decoding, and use it
25267 in router_get_by_digest(). Many other CPU and memory improvements.
25268 - Allow tor_gzip_uncompress to extract as much as possible from
25269 truncated compressed data. Try to extract as many
25270 descriptors as possible from truncated http responses (when
25271 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
25272 - Make circ->onionskin a pointer, not a static array. moria2 was using
25273 125000 circuit_t's after it had been up for a few weeks, which
25274 translates to 20+ megs of wasted space.
25275 - The private half of our EDH handshake keys are now chosen out
25276 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
25277 - Stop doing the complex voodoo overkill checking for insecure
25278 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
25279 - Do round-robin writes for TLS of at most 16 kB per write. This
25280 might be more fair on loaded Tor servers.
25281 - Do not use unaligned memory access on alpha, mips, or mipsel.
25282 It *works*, but is very slow, so we treat them as if it doesn't.
25284 o Other bugfixes and improvements:
25285 - Start storing useful information to $DATADIR/state, so we can
25286 remember things across invocations of Tor. Retain unrecognized
25287 lines so we can be forward-compatible, and write a TorVersion line
25288 so we can be backward-compatible.
25289 - If ORPort is set, Address is not explicitly set, and our hostname
25290 resolves to a private IP address, try to use an interface address
25291 if it has a public address. Now Windows machines that think of
25292 themselves as localhost can guess their address.
25293 - Regenerate our local descriptor if it's dirty and we try to use
25294 it locally (e.g. if it changes during reachability detection).
25295 This was causing some Tor servers to keep publishing the same
25296 initial descriptor forever.
25297 - Tor servers with dynamic IP addresses were needing to wait 18
25298 hours before they could start doing reachability testing using
25299 the new IP address and ports. This is because they were using
25300 the internal descriptor to learn what to test, yet they were only
25301 rebuilding the descriptor once they decided they were reachable.
25302 - It turns out we couldn't bootstrap a network since we added
25303 reachability detection in 0.1.0.1-rc. Good thing the Tor network
25304 has never gone down. Add an AssumeReachable config option to let
25305 servers and authorities bootstrap. When we're trying to build a
25306 high-uptime or high-bandwidth circuit but there aren't enough
25307 suitable servers, try being less picky rather than simply failing.
25308 - Newly bootstrapped Tor networks couldn't establish hidden service
25309 circuits until they had nodes with high uptime. Be more tolerant.
25310 - Really busy servers were keeping enough circuits open on stable
25311 connections that they were wrapping around the circuit_id
25312 space. (It's only two bytes.) This exposed a bug where we would
25313 feel free to reuse a circuit_id even if it still exists but has
25314 been marked for close. Try to fix this bug. Some bug remains.
25315 - When we fail to bind or listen on an incoming or outgoing
25316 socket, we now close it before refusing, rather than just
25317 leaking it. (Thanks to Peter Palfrader for finding.)
25318 - Fix a file descriptor leak in start_daemon().
25319 - On Windows, you can't always reopen a port right after you've
25320 closed it. So change retry_listeners() to only close and re-open
25321 ports that have changed.
25322 - Workaround a problem with some http proxies that refuse GET
25323 requests that specify "Content-Length: 0". Reported by Adrian.
25324 - Recover better from TCP connections to Tor servers that are
25325 broken but don't tell you (it happens!); and rotate TLS
25326 connections once a week.
25327 - Fix a scary-looking but apparently harmless bug where circuits
25328 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
25329 servers, and never switch to state CIRCUIT_STATE_OPEN.
25330 - Check for even more Windows version flags when writing the platform
25331 string in server descriptors, and note any we don't recognize.
25332 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
25333 get a better idea of why their circuits failed. Not used yet.
25334 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
25335 We don't use them yet, but maybe one day our DNS resolver will be
25336 able to discover them.
25337 - Let people type "tor --install" as well as "tor -install" when they
25338 want to make it an NT service.
25339 - Looks like we were never delivering deflated (i.e. compressed)
25340 running-routers lists, even when asked. Oops.
25341 - We were leaking some memory every time the client changed IPs.
25342 - Clean up more of the OpenSSL memory when exiting, so we can detect
25343 memory leaks better.
25344 - Never call free() on tor_malloc()d memory. This will help us
25345 use dmalloc to detect memory leaks.
25346 - Some Tor servers process billions of cells per day. These
25347 statistics are now uint64_t's.
25348 - Check [X-]Forwarded-For headers in HTTP requests when generating
25349 log messages. This lets people run dirservers (and caches) behind
25350 Apache but still know which IP addresses are causing warnings.
25351 - Fix minor integer overflow in calculating when we expect to use up
25352 our bandwidth allocation before hibernating.
25353 - Lower the minimum required number of file descriptors to 1000,
25354 so we can have some overhead for Valgrind on Linux, where the
25355 default ulimit -n is 1024.
25356 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
25357 and its existence is confusing some users.
25359 o Config option fixes:
25360 - Add a new config option ExitPolicyRejectPrivate which defaults
25361 to on. Now all exit policies will begin with rejecting private
25362 addresses, unless the server operator explicitly turns it off.
25363 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
25364 - Add new ReachableORAddresses and ReachableDirAddresses options
25365 that understand address policies. FascistFirewall is now a synonym
25366 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
25367 - Start calling it FooListenAddress rather than FooBindAddress,
25368 since few of our users know what it means to bind an address
25370 - If the user gave Tor an odd number of command-line arguments,
25371 we were silently ignoring the last one. Now we complain and fail.
25372 This wins the oldest-bug prize -- this bug has been present since
25373 November 2002, as released in Tor 0.0.0.
25374 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
25375 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
25376 it would silently ignore the 6668.
25377 - If we get a linelist or linelist_s config option from the torrc,
25378 e.g. ExitPolicy, and it has no value, warn and skip rather than
25379 silently resetting it to its default.
25380 - Setconf was appending items to linelists, not clearing them.
25381 - Add MyFamily to torrc.sample in the server section, so operators
25382 will be more likely to learn that it exists.
25383 - Make ContactInfo mandatory for authoritative directory servers.
25384 - MaxConn has been obsolete for a while now. Document the ConnLimit
25385 config option, which is a *minimum* number of file descriptors
25386 that must be available else Tor refuses to start.
25387 - Get rid of IgnoreVersion undocumented config option, and make us
25388 only warn, never exit, when we're running an obsolete version.
25389 - Make MonthlyAccountingStart config option truly obsolete now.
25390 - Correct the man page entry on TrackHostExitsExpire.
25391 - Let directory authorities start even if they don't specify an
25392 Address config option.
25393 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
25394 reflect the updated flags in our v2 dir protocol.
25396 o Config option features:
25397 - Add a new config option FastFirstHopPK (on by default) so clients
25398 do a trivial crypto handshake for their first hop, since TLS has
25399 already taken care of confidentiality and authentication.
25400 - Let the user set ControlListenAddress in the torrc. This can be
25401 dangerous, but there are some cases (like a secured LAN) where it
25403 - New config options to help controllers: FetchServerDescriptors
25404 and FetchHidServDescriptors for whether to fetch server
25405 info and hidserv info or let the controller do it, and
25406 PublishServerDescriptor and PublishHidServDescriptors.
25407 - Also let the controller set the __AllDirActionsPrivate config
25408 option if you want all directory fetches/publishes to happen via
25409 Tor (it assumes your controller bootstraps your circuits).
25410 - Add "HardwareAccel" config option: support for crypto hardware
25411 accelerators via OpenSSL. Off by default, until we find somebody
25412 smart who can test it for us. (It appears to produce seg faults
25413 in at least some cases.)
25414 - New config option "AuthDirRejectUnlisted" for directory authorities
25415 as a panic button: if we get flooded with unusable servers we can
25416 revert to only listing servers in the approved-routers file.
25417 - Directory authorities can now reject/invalidate by key and IP,
25418 with the config options "AuthDirInvalid" and "AuthDirReject", or
25419 by marking a fingerprint as "!reject" or "!invalid" (as its
25420 nickname) in the approved-routers file. This is useful since
25421 currently we automatically list servers as running and usable
25422 even if we know they're jerks.
25423 - Add a new config option TestSocks so people can see whether their
25424 applications are using socks4, socks4a, socks5-with-ip, or
25425 socks5-with-fqdn. This way they don't have to keep mucking
25426 with tcpdump and wondering if something got cached somewhere.
25427 - Add "private:*" as an alias in configuration for policies. Now
25428 you can simplify your exit policy rather than needing to list
25429 every single internal or nonroutable network space.
25430 - Accept "private:*" in routerdesc exit policies; not generated yet
25431 because older Tors do not understand it.
25432 - Add configuration option "V1AuthoritativeDirectory 1" which
25433 moria1, moria2, and tor26 have set.
25434 - Implement an option, VirtualAddrMask, to set which addresses
25435 get handed out in response to mapaddress requests. This works
25436 around a bug in tsocks where 127.0.0.0/8 is never socksified.
25437 - Add a new config option FetchUselessDescriptors, off by default,
25438 for when you plan to run "exitlist" on your client and you want
25439 to know about even the non-running descriptors.
25440 - SocksTimeout: How long do we let a socks connection wait
25441 unattached before we fail it?
25442 - CircuitBuildTimeout: Cull non-open circuits that were born
25443 at least this many seconds ago.
25444 - CircuitIdleTimeout: Cull open clean circuits that were born
25445 at least this many seconds ago.
25446 - New config option SafeSocks to reject all application connections
25447 using unsafe socks protocols. Defaults to off.
25449 o Improved and clearer log messages:
25450 - Reduce clutter in server logs. We're going to try to make
25451 them actually usable now. New config option ProtocolWarnings that
25452 lets you hear about how _other Tors_ are breaking the protocol. Off
25454 - Divide log messages into logging domains. Once we put some sort
25455 of interface on this, it will let people looking at more verbose
25456 log levels specify the topics they want to hear more about.
25457 - Log server fingerprint on startup, so new server operators don't
25458 have to go hunting around their filesystem for it.
25459 - Provide dire warnings to any users who set DirServer manually;
25460 move it out of torrc.sample and into torrc.complete.
25461 - Make the log message less scary when all the dirservers are
25462 temporarily unreachable.
25463 - When tor_socketpair() fails in Windows, give a reasonable
25464 Windows-style errno back.
25465 - Improve tor_gettimeofday() granularity on windows.
25466 - We were printing the number of idle dns workers incorrectly when
25468 - Handle duplicate lines in approved-routers files without warning.
25469 - We were whining about using socks4 or socks5-with-local-lookup
25470 even when it's an IP address in the "virtual" range we designed
25471 exactly for this case.
25472 - Check for named servers when looking them up by nickname;
25473 warn when we're calling a non-named server by its nickname;
25474 don't warn twice about the same name.
25475 - Downgrade the dirserver log messages when whining about
25477 - Correct "your server is reachable" log entries to indicate that
25478 it was self-testing that told us so.
25479 - If we're trying to be a Tor server and running Windows 95/98/ME
25480 as a server, explain that we'll likely crash.
25481 - Provide a more useful warn message when our onion queue gets full:
25482 the CPU is too slow or the exit policy is too liberal.
25483 - Don't warn when we receive a 503 from a dirserver/cache -- this
25484 will pave the way for them being able to refuse if they're busy.
25485 - When we fail to bind a listener, try to provide a more useful
25486 log message: e.g., "Is Tor already running?"
25487 - Only start testing reachability once we've established a
25488 circuit. This will make startup on dir authorities less noisy.
25489 - Don't try to upload hidden service descriptors until we have
25490 established a circuit.
25491 - Tor didn't warn when it failed to open a log file.
25492 - Warn when listening on a public address for socks. We suspect a
25493 lot of people are setting themselves up as open socks proxies,
25494 and they have no idea that jerks on the Internet are using them,
25495 since they simply proxy the traffic into the Tor network.
25496 - Give a useful message when people run Tor as the wrong user,
25497 rather than telling them to start chowning random directories.
25498 - Fix a harmless bug that was causing Tor servers to log
25499 "Got an end because of misc error, but we're not an AP. Closing."
25500 - Fix wrong log message when you add a "HiddenServiceNodes" config
25501 line without any HiddenServiceDir line (reported by Chris Thomas).
25502 - Directory authorities now stop whining so loudly about bad
25503 descriptors that they fetch from other dirservers. So when there's
25504 a log complaint, it's for sure from a freshly uploaded descriptor.
25505 - When logging via syslog, include the pid whenever we provide
25506 a log entry. Suggested by Todd Fries.
25507 - When we're shutting down and we do something like try to post a
25508 server descriptor or rendezvous descriptor, don't complain that
25509 we seem to be unreachable. Of course we are, we're shutting down.
25510 - Change log line for unreachability to explicitly suggest /etc/hosts
25511 as the culprit. Also make it clearer what IP address and ports we're
25512 testing for reachability.
25513 - Put quotes around user-supplied strings when logging so users are
25514 more likely to realize if they add bad characters (like quotes)
25516 - NT service patch from Matt Edman to improve error messages on Win32.
25519 Changes in version 0.1.0.17 - 2006-02-17
25520 o Crash bugfixes on 0.1.0.x:
25521 - When servers with a non-zero DirPort came out of hibernation,
25522 sometimes they would trigger an assert.
25524 o Other important bugfixes:
25525 - On platforms that don't have getrlimit (like Windows), we were
25526 artificially constraining ourselves to a max of 1024
25527 connections. Now just assume that we can handle as many as 15000
25528 connections. Hopefully this won't cause other problems.
25530 o Backported features:
25531 - When we're a server, a client asks for an old-style directory,
25532 and our write bucket is empty, don't give it to him. This way
25533 small servers can continue to serve the directory *sometimes*,
25534 without getting overloaded.
25535 - Whenever you get a 503 in response to a directory fetch, try
25536 once more. This will become important once servers start sending
25537 503's whenever they feel busy.
25538 - Fetch a new directory every 120 minutes, not every 40 minutes.
25539 Now that we have hundreds of thousands of users running the old
25540 directory algorithm, it's starting to hurt a lot.
25541 - Bump up the period for forcing a hidden service descriptor upload
25542 from 20 minutes to 1 hour.
25545 Changes in version 0.1.0.16 - 2006-01-02
25546 o Crash bugfixes on 0.1.0.x:
25547 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25548 corrupting the heap, losing FDs, or crashing when we need to resize
25549 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25550 - It turns out sparc64 platforms crash on unaligned memory access
25551 too -- so detect and avoid this.
25552 - Handle truncated compressed data correctly (by detecting it and
25554 - Fix possible-but-unlikely free(NULL) in control.c.
25555 - When we were closing connections, there was a rare case that
25556 stomped on memory, triggering seg faults and asserts.
25557 - Avoid potential infinite recursion when building a descriptor. (We
25558 don't know that it ever happened, but better to fix it anyway.)
25559 - We were neglecting to unlink marked circuits from soon-to-close OR
25560 connections, which caused some rare scribbling on freed memory.
25561 - Fix a memory stomping race bug when closing the joining point of two
25562 rendezvous circuits.
25563 - Fix an assert in time parsing found by Steven Murdoch.
25565 o Other bugfixes on 0.1.0.x:
25566 - When we're doing reachability testing, provide more useful log
25567 messages so the operator knows what to expect.
25568 - Do not check whether DirPort is reachable when we are suppressing
25569 advertising it because of hibernation.
25570 - When building with -static or on Solaris, we sometimes needed -ldl.
25571 - One of the dirservers (tor26) changed its IP address.
25572 - When we're deciding whether a stream has enough circuits around
25573 that can handle it, count the freshly dirty ones and not the ones
25574 that are so dirty they won't be able to handle it.
25575 - When we're expiring old circuits, we had a logic error that caused
25576 us to close new rendezvous circuits rather than old ones.
25577 - Give a more helpful log message when you try to change ORPort via
25578 the controller: you should upgrade Tor if you want that to work.
25579 - We were failing to parse Tor versions that start with "Tor ".
25580 - Tolerate faulty streams better: when a stream fails for reason
25581 exitpolicy, stop assuming that the router is lying about his exit
25582 policy. When a stream fails for reason misc, allow it to retry just
25583 as if it was resolvefailed. When a stream has failed three times,
25584 reset its failure count so we can try again and get all three tries.
25587 Changes in version 0.1.0.15 - 2005-09-23
25588 o Bugfixes on 0.1.0.x:
25589 - Reject ports 465 and 587 (spam targets) in default exit policy.
25590 - Don't crash when we don't have any spare file descriptors and we
25591 try to spawn a dns or cpu worker.
25592 - Get rid of IgnoreVersion undocumented config option, and make us
25593 only warn, never exit, when we're running an obsolete version.
25594 - Don't try to print a null string when your server finds itself to
25595 be unreachable and the Address config option is empty.
25596 - Make the numbers in read-history and write-history into uint64s,
25597 so they don't overflow and publish negatives in the descriptor.
25598 - Fix a minor memory leak in smartlist_string_remove().
25599 - We were only allowing ourselves to upload a server descriptor at
25600 most every 20 minutes, even if it changed earlier than that.
25601 - Clean up log entries that pointed to old URLs.
25604 Changes in version 0.1.0.14 - 2005-08-08
25605 o Bugfixes on 0.1.0.x:
25606 - Fix the other half of the bug with crypto handshakes
25608 - Fix an assert trigger if you send a 'signal term' via the
25609 controller when it's listening for 'event info' messages.
25612 Changes in version 0.1.0.13 - 2005-08-04
25613 o Bugfixes on 0.1.0.x:
25614 - Fix a critical bug in the security of our crypto handshakes.
25615 - Fix a size_t underflow in smartlist_join_strings2() that made
25616 it do bad things when you hand it an empty smartlist.
25617 - Fix Windows installer to ship Tor license (thanks to Aphex for
25618 pointing out this oversight) and put a link to the doc directory
25620 - Explicitly set no-unaligned-access for sparc: it turns out the
25621 new gcc's let you compile broken code, but that doesn't make it
25625 Changes in version 0.1.0.12 - 2005-07-18
25626 o New directory servers:
25627 - tor26 has changed IP address.
25629 o Bugfixes on 0.1.0.x:
25630 - Fix a possible double-free in tor_gzip_uncompress().
25631 - When --disable-threads is set, do not search for or link against
25632 pthreads libraries.
25633 - Don't trigger an assert if an authoritative directory server
25634 claims its dirport is 0.
25635 - Fix bug with removing Tor as an NT service: some people were
25636 getting "The service did not return an error." Thanks to Matt
25640 Changes in version 0.1.0.11 - 2005-06-30
25641 o Bugfixes on 0.1.0.x:
25642 - Fix major security bug: servers were disregarding their
25643 exit policies if clients behaved unexpectedly.
25644 - Make OS X init script check for missing argument, so we don't
25645 confuse users who invoke it incorrectly.
25646 - Fix a seg fault in "tor --hash-password foo".
25647 - The MAPADDRESS control command was broken.
25650 Changes in version 0.1.0.10 - 2005-06-14
25652 - Make NT services work and start on startup on Win32 (based on
25653 patch by Matt Edman). See the FAQ entry for details.
25654 - Make 'platform' string in descriptor more accurate for Win32
25655 servers, so it's not just "unknown platform".
25656 - REUSEADDR on normal platforms means you can rebind to the port
25657 right after somebody else has let it go. But REUSEADDR on Win32
25658 means you can bind to the port _even when somebody else already
25659 has it bound_! So, don't do that on Win32.
25660 - Clean up the log messages when starting on Win32 with no config
25662 - Allow seeding the RNG on Win32 even when you're not running as
25663 Administrator. If seeding the RNG on Win32 fails, quit.
25665 o Assert / crash bugs:
25666 - Refuse relay cells that claim to have a length larger than the
25667 maximum allowed. This prevents a potential attack that could read
25668 arbitrary memory (e.g. keys) from an exit server's process
25670 - If unofficial Tor clients connect and send weird TLS certs, our
25671 Tor server triggers an assert. Stop asserting, and start handling
25672 TLS errors better in other situations too.
25673 - Fix a race condition that can trigger an assert when we have a
25674 pending create cell and an OR connection attempt fails.
25677 - Use pthreads for worker processes rather than forking. This was
25678 forced because when we forked, we ended up wasting a lot of
25679 duplicate ram over time.
25680 - Also switch to foo_r versions of some library calls to allow
25681 reentry and threadsafeness.
25682 - Implement --disable-threads configure option. Disable threads on
25683 netbsd and openbsd by default, because they have no reentrant
25684 resolver functions (!), and on solaris since it has other
25686 - Fix possible bug on threading platforms (e.g. win32) which was
25687 leaking a file descriptor whenever a cpuworker or dnsworker died.
25688 - Fix a minor memory leak when somebody establishes an introduction
25689 point at your Tor server.
25690 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
25692 - Add ./configure --with-dmalloc option, to track memory leaks.
25693 - And try to free all memory on closing, so we can detect what
25696 o Protocol correctness:
25697 - When we've connected to an OR and handshaked but didn't like
25698 the result, we were closing the conn without sending destroy
25699 cells back for pending circuits. Now send those destroys.
25700 - Start sending 'truncated' cells back rather than destroy cells
25701 if the circuit closes in front of you. This means we won't have
25702 to abandon partially built circuits.
25703 - Handle changed router status correctly when dirserver reloads
25704 fingerprint file. We used to be dropping all unverified descriptors
25705 right then. The bug was hidden because we would immediately
25706 fetch a directory from another dirserver, which would include the
25707 descriptors we just dropped.
25708 - Revise tor-spec to add more/better stream end reasons.
25709 - Revise all calls to connection_edge_end to avoid sending 'misc',
25710 and to take errno into account where possible.
25711 - Client now retries when streams end early for 'hibernating' or
25712 'resource limit' reasons, rather than failing them.
25713 - Try to be more zealous about calling connection_edge_end when
25714 things go bad with edge conns in connection.c.
25716 o Robustness improvements:
25717 - Better handling for heterogeneous / unreliable nodes:
25718 - Annotate circuits with whether they aim to contain high uptime
25719 nodes and/or high capacity nodes. When building circuits, choose
25721 - This means that every single node in an intro rend circuit,
25722 not just the last one, will have a minimum uptime.
25723 - New config option LongLivedPorts to indicate application streams
25724 that will want high uptime circuits.
25725 - Servers reset uptime when a dir fetch entirely fails. This
25726 hopefully reflects stability of the server's network connectivity.
25727 - If somebody starts his tor server in Jan 2004 and then fixes his
25728 clock, don't make his published uptime be a year.
25729 - Reset published uptime when we wake up from hibernation.
25730 - Introduce a notion of 'internal' circs, which are chosen without
25731 regard to the exit policy of the last hop. Intro and rendezvous
25732 circs must be internal circs, to avoid leaking information. Resolve
25733 and connect streams can use internal circs if they want.
25734 - New circuit pooling algorithm: keep track of what destination ports
25735 we've used recently (start out assuming we'll want to use 80), and
25736 make sure to have enough circs around to satisfy these ports. Also
25737 make sure to have 2 internal circs around if we've required internal
25738 circs lately (and with high uptime if we've seen that lately too).
25739 - Turn addr_policy_compare from a tristate to a quadstate; this should
25740 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
25741 for google.com" problem.
25742 - When a client asks us for a dir mirror and we don't have one,
25743 launch an attempt to get a fresh one.
25744 - First cut at support for "create-fast" cells. Clients can use
25745 these when extending to their first hop, since the TLS already
25746 provides forward secrecy and authentication. Not enabled on
25749 o Reachability testing.
25750 - Your Tor server will automatically try to see if its ORPort and
25751 DirPort are reachable from the outside, and it won't upload its
25752 descriptor until it decides at least ORPort is reachable (when
25753 DirPort is not yet found reachable, publish it as zero).
25754 - When building testing circs for ORPort testing, use only
25755 high-bandwidth nodes, so fewer circuits fail.
25756 - Notice when our IP changes, and reset stats/uptime/reachability.
25757 - Authdirservers don't do ORPort reachability detection, since
25758 they're in clique mode, so it will be rare to find a server not
25759 already connected to them.
25760 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
25764 - Now we allow two unverified servers with the same nickname
25765 but different keys. But if a nickname is verified, only that
25766 nickname+key are allowed.
25767 - If you're an authdirserver connecting to an address:port,
25768 and it's not the OR you were expecting, forget about that
25769 descriptor. If he *was* the one you were expecting, then forget
25770 about all other descriptors for that address:port.
25771 - Allow servers to publish descriptors from 12 hours in the future.
25772 Corollary: only whine about clock skew from the dirserver if
25773 he's a trusted dirserver (since now even verified servers could
25774 have quite wrong clocks).
25775 - Require servers that use the default dirservers to have public IP
25776 addresses. We have too many servers that are configured with private
25777 IPs and their admins never notice the log entries complaining that
25778 their descriptors are being rejected.
25780 o Efficiency improvements:
25781 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
25782 and /dev/poll), and hopefully work better on Windows too.
25783 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
25784 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
25785 - Find libevent even if it's hiding in /usr/local/ and your
25786 CFLAGS and LDFLAGS don't tell you to look there.
25787 - Be able to link with libevent as a shared library (the default
25788 after 1.0d), even if it's hiding in /usr/local/lib and even
25789 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
25790 assuming you're running gcc. Otherwise fail and give a useful
25792 - Switch to a new buffer management algorithm, which tries to avoid
25793 reallocing and copying quite as much. In first tests it looks like
25794 it uses *more* memory on average, but less cpu.
25795 - Switch our internal buffers implementation to use a ring buffer,
25796 to hopefully improve performance for fast servers a lot.
25797 - Reenable the part of the code that tries to flush as soon as an
25798 OR outbuf has a full TLS record available. Perhaps this will make
25799 OR outbufs not grow as huge except in rare cases, thus saving lots
25800 of CPU time plus memory.
25801 - Improve performance for dirservers: stop re-parsing the whole
25802 directory every time you regenerate it.
25803 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
25804 it much faster to look up a circuit for each relay cell.
25805 - Remove most calls to assert_all_pending_dns_resolves_ok(),
25806 since they're eating our cpu on exit nodes.
25807 - Stop wasting time doing a case insensitive comparison for every
25808 dns name every time we do any lookup. Canonicalize the names to
25809 lowercase when you first see them.
25812 - Handle unavailable hidden services better. Handle slow or busy
25813 hidden services better.
25814 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
25815 circ as necessary, if there are any completed ones lying around
25816 when we try to launch one.
25817 - Make hidden services try to establish a rendezvous for 30 seconds
25818 after fetching the descriptor, rather than for n (where n=3)
25819 attempts to build a circuit.
25820 - Adjust maximum skew and age for rendezvous descriptors: let skew
25821 be 48 hours rather than 90 minutes.
25822 - Reject malformed .onion addresses rather then passing them on as
25823 normal web requests.
25826 - More Tor controller support. See
25827 http://tor.eff.org/doc/control-spec.txt for all the new features,
25828 including signals to emulate unix signals from any platform;
25829 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
25830 closestream; closecircuit; etc.
25831 - Encode hashed controller passwords in hex instead of base64,
25832 to make it easier to write controllers.
25833 - Revise control spec and implementation to allow all log messages to
25834 be sent to controller with their severities intact (suggested by
25835 Matt Edman). Disable debug-level logs while delivering a debug-level
25836 log to the controller, to prevent loop. Update TorControl to handle
25837 new log event types.
25839 o New config options/defaults:
25840 - Begin scrubbing sensitive strings from logs by default. Turn off
25841 the config option SafeLogging if you need to do debugging.
25842 - New exit policy: accept most low-numbered ports, rather than
25843 rejecting most low-numbered ports.
25844 - Put a note in the torrc about abuse potential with the default
25846 - Add support for CONNECTing through https proxies, with "HttpsProxy"
25848 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
25849 based on patch from Adam Langley (basic auth only).
25850 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
25851 the fast servers that have been joining lately. (Clients are now
25852 willing to load balance over up to 2 MB of advertised bandwidth
25854 - New config option MaxAdvertisedBandwidth which lets you advertise
25855 a low bandwidthrate (to not attract as many circuits) while still
25856 allowing a higher bandwidthrate in reality.
25857 - Require BandwidthRate to be at least 20kB/s for servers.
25858 - Add a NoPublish config option, so you can be a server (e.g. for
25859 testing running Tor servers in other Tor networks) without
25860 publishing your descriptor to the primary dirservers.
25861 - Add a new AddressMap config directive to rewrite incoming socks
25862 addresses. This lets you, for example, declare an implicit
25863 required exit node for certain sites.
25864 - Add a new TrackHostExits config directive to trigger addressmaps
25865 for certain incoming socks addresses -- for sites that break when
25866 your exit keeps changing (based on patch from Mike Perry).
25867 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
25868 which describes how often we retry making new circuits if current
25869 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
25870 how long we're willing to make use of an already-dirty circuit.
25871 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
25872 a config option "ShutdownWaitLength" (when using kill -INT on
25874 - Fix an edge case in parsing config options: if they say "--"
25875 on the commandline, it's not a config option (thanks weasel).
25876 - New config option DirAllowPrivateAddresses for authdirservers.
25877 Now by default they refuse router descriptors that have non-IP or
25878 private-IP addresses.
25879 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
25880 smart" default value: low for servers and high for clients.
25881 - Some people were putting "Address " in their torrc, and they had
25882 a buggy resolver that resolved " " to 0.0.0.0. Oops.
25883 - If DataDir is ~/.tor, and that expands to /.tor, then default to
25884 LOCALSTATEDIR/tor instead.
25885 - Implement --verify-config command-line option to check if your torrc
25886 is valid without actually launching Tor.
25888 o Logging improvements:
25889 - When dirservers refuse a server descriptor, we now log its
25890 contactinfo, platform, and the poster's IP address.
25891 - Only warn once per nickname from add_nickname_list_to_smartlist()
25892 per failure, so an entrynode or exitnode choice that's down won't
25894 - When we're connecting to an OR and he's got a different nickname/key
25895 than we were expecting, only complain loudly if we're an OP or a
25896 dirserver. Complaining loudly to the OR admins just confuses them.
25897 - Whine at you if you're a server and you don't set your contactinfo.
25898 - Warn when exit policy implicitly allows local addresses.
25899 - Give a better warning when some other server advertises an
25900 ORPort that is actually an apache running ssl.
25901 - If we get an incredibly skewed timestamp from a dirserver mirror
25902 that isn't a verified OR, don't warn -- it's probably him that's
25904 - When a dirserver causes you to give a warn, mention which dirserver
25906 - Initialize libevent later in the startup process, so the logs are
25907 already established by the time we start logging libevent warns.
25908 - Use correct errno on win32 if libevent fails.
25909 - Check and warn about known-bad/slow libevent versions.
25910 - Stop warning about sigpipes in the logs. We're going to
25911 pretend that getting these occasionally is normal and fine.
25913 o New contrib scripts:
25914 - New experimental script tor/contrib/exitlist: a simple python
25915 script to parse directories and find Tor nodes that exit to listed
25917 - New experimental script tor/contrib/ExerciseServer.py (needs more
25918 work) that uses the controller interface to build circuits and
25919 fetch pages over them. This will help us bootstrap servers that
25920 have lots of capacity but haven't noticed it yet.
25921 - New experimental script tor/contrib/PathDemo.py (needs more work)
25922 that uses the controller interface to let you choose whole paths
25924 "<hostname>.<path,separated by dots>.<length of path>.path"
25925 - New contributed script "privoxy-tor-toggle" to toggle whether
25926 Privoxy uses Tor. Seems to be configured for Debian by default.
25927 - Have torctl.in/tor.sh.in check for location of su binary (needed
25931 - chdir() to your datadirectory at the *end* of the daemonize process,
25932 not the beginning. This was a problem because the first time you
25933 run tor, if your datadir isn't there, and you have runasdaemon set
25934 to 1, it will try to chdir to it before it tries to create it. Oops.
25935 - Fix several double-mark-for-close bugs, e.g. where we were finding
25936 a conn for a cell even if that conn is already marked for close.
25937 - Stop most cases of hanging up on a socks connection without sending
25939 - Fix a bug in the RPM package: set home directory for _tor to
25940 something more reasonable when first installing.
25941 - Stop putting nodename in the Platform string in server descriptors.
25942 It doesn't actually help, and it is confusing/upsetting some people.
25943 - When using preferred entry or exit nodes, ignore whether the
25944 circuit wants uptime or capacity. They asked for the nodes, they
25946 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
25947 artificially capped at 500kB.
25948 - Cache local dns resolves correctly even when they're .exit
25950 - If we're hibernating and we get a SIGINT, exit immediately.
25951 - tor-resolve requests were ignoring .exit if there was a working circuit
25952 they could use instead.
25953 - Pay more attention to the ClientOnly config option.
25954 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
25955 installer screens; and don't put stuff into StartupItems unless
25956 the user asks you to.
25959 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
25960 rather than just rejecting it.
25961 - If our clock jumps forward by 100 seconds or more, assume something
25962 has gone wrong with our network and abandon all not-yet-used circs.
25963 - When an application is using socks5, give him the whole variety of
25964 potential socks5 responses (connect refused, host unreachable, etc),
25965 rather than just "success" or "failure".
25966 - A more sane version numbering system. See
25967 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
25968 - Change version parsing logic: a version is "obsolete" if it is not
25969 recommended and (1) there is a newer recommended version in the
25970 same series, or (2) there are no recommended versions in the same
25971 series, but there are some recommended versions in a newer series.
25972 A version is "new" if it is newer than any recommended version in
25974 - Report HTTP reasons to client when getting a response from directory
25975 servers -- so you can actually know what went wrong.
25976 - Reject odd-looking addresses at the client (e.g. addresses that
25977 contain a colon), rather than having the server drop them because
25979 - Stop publishing socksport in the directory, since it's not
25980 actually meant to be public. For compatibility, publish a 0 there
25982 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
25983 cookies to disk and doesn't log each web request to disk. (Thanks
25984 to Brett Carrington for pointing this out.)
25985 - Add OSX uninstall instructions. An actual uninstall script will
25987 - Add "opt hibernating 1" to server descriptor to make it clearer
25988 whether the server is hibernating.
25991 Changes in version 0.0.9.10 - 2005-06-16
25992 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
25993 - Refuse relay cells that claim to have a length larger than the
25994 maximum allowed. This prevents a potential attack that could read
25995 arbitrary memory (e.g. keys) from an exit server's process
25999 Changes in version 0.0.9.9 - 2005-04-23
26000 o Bugfixes on 0.0.9.x:
26001 - If unofficial Tor clients connect and send weird TLS certs, our
26002 Tor server triggers an assert. This release contains a minimal
26003 backport from the broader fix that we put into 0.1.0.4-rc.
26006 Changes in version 0.0.9.8 - 2005-04-07
26007 o Bugfixes on 0.0.9.x:
26008 - We have a bug that I haven't found yet. Sometimes, very rarely,
26009 cpuworkers get stuck in the 'busy' state, even though the cpuworker
26010 thinks of itself as idle. This meant that no new circuits ever got
26011 established. Here's a workaround to kill any cpuworker that's been
26012 busy for more than 100 seconds.
26015 Changes in version 0.0.9.7 - 2005-04-01
26016 o Bugfixes on 0.0.9.x:
26017 - Fix another race crash bug (thanks to Glenn Fink for reporting).
26018 - Compare identity to identity, not to nickname, when extending to
26019 a router not already in the directory. This was preventing us from
26020 extending to unknown routers. Oops.
26021 - Make sure to create OS X Tor user in <500 range, so we aren't
26022 creating actual system users.
26023 - Note where connection-that-hasn't-sent-end was marked, and fix
26024 a few really loud instances of this harmless bug (it's fixed more
26028 Changes in version 0.0.9.6 - 2005-03-24
26029 o Bugfixes on 0.0.9.x (crashes and asserts):
26030 - Add new end stream reasons to maintenance branch. Fix bug where
26031 reason (8) could trigger an assert. Prevent bug from recurring.
26032 - Apparently win32 stat wants paths to not end with a slash.
26033 - Fix assert triggers in assert_cpath_layer_ok(), where we were
26034 blowing away the circuit that conn->cpath_layer points to, then
26035 checking to see if the circ is well-formed. Backport check to make
26036 sure we dont use the cpath on a closed connection.
26037 - Prevent circuit_resume_edge_reading_helper() from trying to package
26038 inbufs for marked-for-close streams.
26039 - Don't crash on hup if your options->address has become unresolvable.
26040 - Some systems (like OS X) sometimes accept() a connection and tell
26041 you the remote host is 0.0.0.0:0. If this happens, due to some
26042 other mis-features, we get confused; so refuse the conn for now.
26044 o Bugfixes on 0.0.9.x (other):
26045 - Fix harmless but scary "Unrecognized content encoding" warn message.
26046 - Add new stream error reason: TORPROTOCOL reason means "you are not
26047 speaking a version of Tor I understand; say bye-bye to your stream."
26048 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
26049 into the future, now that we are more tolerant of skew. This
26050 resolves a bug where a Tor server would refuse to cache a directory
26051 because all the directories it gets are too far in the future;
26052 yet the Tor server never logs any complaints about clock skew.
26053 - Mac packaging magic: make man pages useable, and do not overwrite
26054 existing torrc files.
26055 - Make OS X log happily to /var/log/tor/tor.log
26058 Changes in version 0.0.9.5 - 2005-02-22
26059 o Bugfixes on 0.0.9.x:
26060 - Fix an assert race at exit nodes when resolve requests fail.
26061 - Stop picking unverified dir mirrors--it only leads to misery.
26062 - Patch from Matt Edman to make NT services work better. Service
26063 support is still not compiled into the executable by default.
26064 - Patch from Dmitri Bely so the Tor service runs better under
26065 the win32 SYSTEM account.
26066 - Make tor-resolve actually work (?) on Win32.
26067 - Fix a sign bug when getrlimit claims to have 4+ billion
26068 file descriptors available.
26069 - Stop refusing to start when bandwidthburst == bandwidthrate.
26070 - When create cells have been on the onion queue more than five
26071 seconds, just send back a destroy and take them off the list.
26074 Changes in version 0.0.9.4 - 2005-02-03
26075 o Bugfixes on 0.0.9:
26076 - Fix an assert bug that took down most of our servers: when
26077 a server claims to have 1 GB of bandwidthburst, don't
26079 - Don't crash as badly if we have spawned the max allowed number
26080 of dnsworkers, or we're out of file descriptors.
26081 - Block more file-sharing ports in the default exit policy.
26082 - MaxConn is now automatically set to the hard limit of max
26083 file descriptors we're allowed (ulimit -n), minus a few for
26085 - Give a clearer message when servers need to raise their
26086 ulimit -n when they start running out of file descriptors.
26087 - SGI Compatibility patches from Jan Schaumann.
26088 - Tolerate a corrupt cached directory better.
26089 - When a dirserver hasn't approved your server, list which one.
26090 - Go into soft hibernation after 95% of the bandwidth is used,
26091 not 99%. This is especially important for daily hibernators who
26092 have a small accounting max. Hopefully it will result in fewer
26093 cut connections when the hard hibernation starts.
26094 - Load-balance better when using servers that claim more than
26095 800kB/s of capacity.
26096 - Make NT services work (experimental, only used if compiled in).
26099 Changes in version 0.0.9.3 - 2005-01-21
26100 o Bugfixes on 0.0.9:
26101 - Backport the cpu use fixes from main branch, so busy servers won't
26102 need as much processor time.
26103 - Work better when we go offline and then come back, or when we
26104 run Tor at boot before the network is up. We do this by
26105 optimistically trying to fetch a new directory whenever an
26106 application request comes in and we think we're offline -- the
26107 human is hopefully a good measure of when the network is back.
26108 - Backport some minimal hidserv bugfixes: keep rend circuits open as
26109 long as you keep using them; actually publish hidserv descriptors
26110 shortly after they change, rather than waiting 20-40 minutes.
26111 - Enable Mac startup script by default.
26112 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
26113 - When you update AllowUnverifiedNodes or FirewallPorts via the
26114 controller's setconf feature, we were always appending, never
26116 - When you update HiddenServiceDir via setconf, it was screwing up
26117 the order of reading the lines, making it fail.
26118 - Do not rewrite a cached directory back to the cache; otherwise we
26119 will think it is recent and not fetch a newer one on startup.
26120 - Workaround for webservers that lie about Content-Encoding: Tor
26121 now tries to autodetect compressed directories and compression
26122 itself. This lets us Proxypass dir fetches through apache.
26125 Changes in version 0.0.9.2 - 2005-01-04
26126 o Bugfixes on 0.0.9 (crashes and asserts):
26127 - Fix an assert on startup when the disk is full and you're logging
26129 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
26130 style address, then we'd crash.
26131 - Fix an assert trigger when the running-routers string we get from
26132 a dirserver is broken.
26133 - Make worker threads start and run on win32. Now win32 servers
26135 - Bandaid (not actually fix, but now it doesn't crash) an assert
26136 where the dns worker dies mysteriously and the main Tor process
26137 doesn't remember anything about the address it was resolving.
26139 o Bugfixes on 0.0.9 (Win32):
26140 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
26141 name out of the warning/assert messages.
26142 - Fix a superficial "unhandled error on read" bug on win32.
26143 - The win32 installer no longer requires a click-through for our
26144 license, since our Free Software license grants rights but does not
26146 - Win32: When connecting to a dirserver fails, try another one
26147 immediately. (This was already working for non-win32 Tors.)
26148 - Stop trying to parse $HOME on win32 when hunting for default
26150 - Make tor-resolve.c work on win32 by calling network_init().
26152 o Bugfixes on 0.0.9 (other):
26153 - Make 0.0.9.x build on Solaris again.
26154 - Due to a fencepost error, we were blowing away the \n when reporting
26155 confvalue items in the controller. So asking for multiple config
26156 values at once couldn't work.
26157 - When listing circuits that are pending on an opening OR connection,
26158 if we're an OR we were listing circuits that *end* at us as
26159 being pending on every listener, dns/cpu worker, etc. Stop that.
26160 - Dirservers were failing to create 'running-routers' or 'directory'
26161 strings if we had more than some threshold of routers. Fix them so
26162 they can handle any number of routers.
26163 - Fix a superficial "Duplicate mark for close" bug.
26164 - Stop checking for clock skew for OR connections, even for servers.
26165 - Fix a fencepost error that was chopping off the last letter of any
26166 nickname that is the maximum allowed nickname length.
26167 - Update URLs in log messages so they point to the new website.
26168 - Fix a potential problem in mangling server private keys while
26169 writing to disk (not triggered yet, as far as we know).
26170 - Include the licenses for other free software we include in Tor,
26171 now that we're shipping binary distributions more regularly.
26174 Changes in version 0.0.9.1 - 2004-12-15
26175 o Bugfixes on 0.0.9:
26176 - Make hibernation actually work.
26177 - Make HashedControlPassword config option work.
26178 - When we're reporting event circuit status to a controller,
26179 don't use the stream status code.
26182 Changes in version 0.0.9 - 2004-12-12
26183 o Bugfixes on 0.0.8.1 (Crashes and asserts):
26184 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
26185 write() call will fail and we handle it there.
26186 - When we run out of disk space, or other log writing error, don't
26187 crash. Just stop logging to that log and continue.
26188 - Fix isspace() and friends so they still make Solaris happy
26189 but also so they don't trigger asserts on win32.
26190 - Fix assert failure on malformed socks4a requests.
26191 - Fix an assert bug where a hidden service provider would fail if
26192 the first hop of his rendezvous circuit was down.
26193 - Better handling of size_t vs int, so we're more robust on 64
26196 o Bugfixes on 0.0.8.1 (Win32):
26197 - Make windows sockets actually non-blocking (oops), and handle
26198 win32 socket errors better.
26199 - Fix parse_iso_time on platforms without strptime (eg win32).
26200 - win32: when being multithreaded, leave parent fdarray open.
26201 - Better handling of winsock includes on non-MSV win32 compilers.
26202 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
26204 - Make unit tests work on win32.
26206 o Bugfixes on 0.0.8.1 (Path selection and streams):
26207 - Calculate timeout for waiting for a connected cell from the time
26208 we sent the begin cell, not from the time the stream started. If
26209 it took a long time to establish the circuit, we would time out
26210 right after sending the begin cell.
26211 - Fix router_compare_addr_to_addr_policy: it was not treating a port
26212 of * as always matching, so we were picking reject *:* nodes as
26213 exit nodes too. Oops.
26214 - When read() failed on a stream, we would close it without sending
26215 back an end. So 'connection refused' would simply be ignored and
26216 the user would get no response.
26217 - Stop a sigpipe: when an 'end' cell races with eof from the app,
26218 we shouldn't hold-open-until-flush if the eof arrived first.
26219 - Let resolve conns retry/expire also, rather than sticking around
26221 - Fix more dns related bugs: send back resolve_failed and end cells
26222 more reliably when the resolve fails, rather than closing the
26223 circuit and then trying to send the cell. Also attach dummy resolve
26224 connections to a circuit *before* calling dns_resolve(), to fix
26225 a bug where cached answers would never be sent in RESOLVED cells.
26227 o Bugfixes on 0.0.8.1 (Circuits):
26228 - Finally fix a bug that's been plaguing us for a year:
26229 With high load, circuit package window was reaching 0. Whenever
26230 we got a circuit-level sendme, we were reading a lot on each
26231 socket, but only writing out a bit. So we would eventually reach
26232 eof. This would be noticed and acted on even when there were still
26233 bytes sitting in the inbuf.
26234 - Use identity comparison, not nickname comparison, to choose which
26235 half of circuit-ID-space each side gets to use. This is needed
26236 because sometimes we think of a router as a nickname, and sometimes
26237 as a hex ID, and we can't predict what the other side will do.
26239 o Bugfixes on 0.0.8.1 (Other):
26240 - Fix a whole slew of memory leaks.
26241 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
26242 - If we are using select, make sure we stay within FD_SETSIZE.
26243 - When poll() is interrupted, we shouldn't believe the revents values.
26244 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
26245 and smartlist_len, which are two major profiling offenders.
26246 - If do_hup fails, actually notice.
26247 - Flush the log file descriptor after we print "Tor opening log file",
26248 so we don't see those messages days later.
26249 - Hidden service operators now correctly handle version 1 style
26250 INTRODUCE1 cells (nobody generates them still, so not a critical
26252 - Handle more errnos from accept() without closing the listener.
26253 Some OpenBSD machines were closing their listeners because
26254 they ran out of file descriptors.
26255 - Some people had wrapped their tor client/server in a script
26256 that would restart it whenever it died. This did not play well
26257 with our "shut down if your version is obsolete" code. Now people
26258 don't fetch a new directory if their local cached version is
26260 - Make our autogen.sh work on ksh as well as bash.
26261 - Better torrc example lines for dirbindaddress and orbindaddress.
26262 - Improved bounds checking on parsed ints (e.g. config options and
26263 the ones we find in directories.)
26264 - Stop using separate defaults for no-config-file and
26265 empty-config-file. Now you have to explicitly turn off SocksPort,
26266 if you don't want it open.
26267 - We were starting to daemonize before we opened our logs, so if
26268 there were any problems opening logs, we would complain to stderr,
26269 which wouldn't work, and then mysteriously exit.
26270 - If a verified OR connects to us before he's uploaded his descriptor,
26271 or we verify him and hup but he still has the original TLS
26272 connection, then conn->nickname is still set like he's unverified.
26274 o Code security improvements, inspired by Ilja:
26275 - tor_snprintf wrapper over snprintf with consistent (though not C99)
26277 - Replace sprintf with tor_snprintf. (I think they were all safe, but
26279 - Replace strcpy/strncpy with strlcpy in more places.
26280 - Avoid strcat; use tor_snprintf or strlcat instead.
26282 o Features (circuits and streams):
26283 - New circuit building strategy: keep a list of ports that we've
26284 used in the past 6 hours, and always try to have 2 circuits open
26285 or on the way that will handle each such port. Seed us with port
26286 80 so web users won't complain that Tor is "slow to start up".
26287 - Make kill -USR1 dump more useful stats about circuits.
26288 - When warning about retrying or giving up, print the address, so
26289 the user knows which one it's talking about.
26290 - If you haven't used a clean circuit in an hour, throw it away,
26291 just to be on the safe side. (This means after 6 hours a totally
26292 unused Tor client will have no circuits open.)
26293 - Support "foo.nickname.exit" addresses, to let Alice request the
26294 address "foo" as viewed by exit node "nickname". Based on a patch
26295 from Geoff Goodell.
26296 - If your requested entry or exit node has advertised bandwidth 0,
26298 - Be more greedy about filling up relay cells -- we try reading again
26299 once we've processed the stuff we read, in case enough has arrived
26300 to fill the last cell completely.
26301 - Refuse application socks connections to port 0.
26302 - Use only 0.0.9pre1 and later servers for resolve cells.
26304 o Features (bandwidth):
26305 - Hibernation: New config option "AccountingMax" lets you
26306 set how many bytes per month (in each direction) you want to
26307 allow your server to consume. Rather than spreading those
26308 bytes out evenly over the month, we instead hibernate for some
26309 of the month and pop up at a deterministic time, work until
26310 the bytes are consumed, then hibernate again. Config option
26311 "MonthlyAccountingStart" lets you specify which day of the month
26312 your billing cycle starts on.
26313 - Implement weekly/monthly/daily accounting: now you specify your
26314 hibernation properties by
26315 AccountingMax N bytes|KB|MB|GB|TB
26316 AccountingStart day|week|month [day] HH:MM
26317 Defaults to "month 1 0:00".
26318 - Let bandwidth and interval config options be specified as 5 bytes,
26319 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
26321 o Features (directories):
26322 - New "router-status" line in directory, to better bind each verified
26323 nickname to its identity key.
26324 - Clients can ask dirservers for /dir.z to get a compressed version
26325 of the directory. Only works for servers running 0.0.9, of course.
26326 - Make clients cache directories and use them to seed their router
26327 lists at startup. This means clients have a datadir again.
26328 - Respond to content-encoding headers by trying to uncompress as
26330 - Clients and servers now fetch running-routers; cache
26331 running-routers; compress running-routers; serve compressed
26333 - Make moria2 advertise a dirport of 80, so people behind firewalls
26334 will be able to get a directory.
26335 - Http proxy support
26336 - Dirservers translate requests for http://%s:%d/x to /x
26337 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
26338 be routed through this host.
26339 - Clients ask for /tor/x rather than /x for new enough dirservers.
26340 This way we can one day coexist peacefully with apache.
26341 - Clients specify a "Host: %s%d" http header, to be compatible
26342 with more proxies, and so running squid on an exit node can work.
26343 - Protect dirservers from overzealous descriptor uploading -- wait
26344 10 seconds after directory gets dirty, before regenerating.
26346 o Features (packages and install):
26347 - Add NSI installer contributed by J Doe.
26348 - Apply NT service patch from Osamu Fujino. Still needs more work.
26349 - Commit VC6 and VC7 workspace/project files.
26350 - Commit a tor.spec for making RPM files, with help from jbash.
26351 - Add contrib/torctl.in contributed by Glenn Fink.
26352 - Make expand_filename handle ~ and ~username.
26353 - Use autoconf to enable largefile support where necessary. Use
26354 ftello where available, since ftell can fail at 2GB.
26355 - Ship src/win32/ in the tarball, so people can use it to build.
26356 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
26359 o Features (ui controller):
26360 - Control interface: a separate program can now talk to your
26361 client/server over a socket, and get/set config options, receive
26362 notifications of circuits and streams starting/finishing/dying,
26363 bandwidth used, etc. The next step is to get some GUIs working.
26364 Let us know if you want to help out. See doc/control-spec.txt .
26365 - Ship a contrib/tor-control.py as an example script to interact
26366 with the control port.
26367 - "tor --hash-password zzyxz" will output a salted password for
26368 use in authenticating to the control interface.
26369 - Implement the control-spec's SAVECONF command, to write your
26370 configuration to torrc.
26371 - Get cookie authentication for the controller closer to working.
26372 - When set_conf changes our server descriptor, upload a new copy.
26373 But don't upload it too often if there are frequent changes.
26375 o Features (config and command-line):
26376 - Deprecate unofficial config option abbreviations, and abbreviations
26377 not on the command line.
26378 - Configuration infrastructure support for warning on obsolete
26380 - Give a slightly more useful output for "tor -h".
26381 - Break DirFetchPostPeriod into:
26382 - DirFetchPeriod for fetching full directory,
26383 - StatusFetchPeriod for fetching running-routers,
26384 - DirPostPeriod for posting server descriptor,
26385 - RendPostPeriod for posting hidden service descriptors.
26386 - New log format in config:
26387 "Log minsev[-maxsev] stdout|stderr|syslog" or
26388 "Log minsev[-maxsev] file /var/foo"
26389 - DirPolicy config option, to let people reject incoming addresses
26390 from their dirserver.
26391 - "tor --list-fingerprint" will list your identity key fingerprint
26393 - Make tor --version --version dump the cvs Id of every file.
26394 - New 'MyFamily nick1,...' config option for a server to
26395 specify other servers that shouldn't be used in the same circuit
26396 with it. Only believed if nick1 also specifies us.
26397 - New 'NodeFamily nick1,nick2,...' config option for a client to
26398 specify nodes that it doesn't want to use in the same circuit.
26399 - New 'Redirectexit pattern address:port' config option for a
26400 server to redirect exit connections, e.g. to a local squid.
26401 - Add "pass" target for RedirectExit, to make it easier to break
26402 out of a sequence of RedirectExit rules.
26403 - Make the dirservers file obsolete.
26404 - Include a dir-signing-key token in directories to tell the
26405 parsing entity which key is being used to sign.
26406 - Remove the built-in bulky default dirservers string.
26407 - New config option "Dirserver %s:%d [fingerprint]", which can be
26408 repeated as many times as needed. If no dirservers specified,
26409 default to moria1,moria2,tor26.
26410 - Make 'Routerfile' config option obsolete.
26411 - Discourage people from setting their dirfetchpostperiod more often
26412 than once per minute.
26414 o Features (other):
26415 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
26416 get back to normal.)
26417 - Accept *:706 (silc) in default exit policy.
26418 - Implement new versioning format for post 0.1.
26419 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
26420 log more informatively.
26421 - Check clock skew for verified servers, but allow unverified
26422 servers and clients to have any clock skew.
26423 - Make sure the hidden service descriptors are at a random offset
26424 from each other, to hinder linkability.
26425 - Clients now generate a TLS cert too, in preparation for having
26426 them act more like real nodes.
26427 - Add a pure-C tor-resolve implementation.
26428 - Use getrlimit and friends to ensure we can reach MaxConn (currently
26429 1024) file descriptors.
26430 - Raise the max dns workers from 50 to 100.
26433 Changes in version 0.0.8.1 - 2004-10-13
26435 - Fix a seg fault that can be triggered remotely for Tor
26436 clients/servers with an open dirport.
26437 - Fix a rare assert trigger, where routerinfos for entries in
26438 our cpath would expire while we're building the path.
26439 - Fix a bug in OutboundBindAddress so it (hopefully) works.
26440 - Fix a rare seg fault for people running hidden services on
26441 intermittent connections.
26442 - Fix a bug in parsing opt keywords with objects.
26443 - Fix a stale pointer assert bug when a stream detaches and
26445 - Fix a string format vulnerability (probably not exploitable)
26446 in reporting stats locally.
26447 - Fix an assert trigger: sometimes launching circuits can fail
26448 immediately, e.g. because too many circuits have failed recently.
26449 - Fix a compile warning on 64 bit platforms.
26452 Changes in version 0.0.8 - 2004-08-25
26454 - Made our unit tests compile again on OpenBSD 3.5, and tor
26455 itself compile again on OpenBSD on a sparc64.
26456 - We were neglecting milliseconds when logging on win32, so
26457 everything appeared to happen at the beginning of each second.
26458 - Check directory signature _before_ you decide whether you're
26459 you're running an obsolete version and should exit.
26460 - Check directory signature _before_ you parse the running-routers
26461 list to decide who's running.
26462 - Check return value of fclose while writing to disk, so we don't
26463 end up with broken files when servers run out of disk space.
26464 - Port it to SunOS 5.9 / Athena
26465 - Fix two bugs in saving onion keys to disk when rotating, so
26466 hopefully we'll get fewer people using old onion keys.
26467 - Remove our mostly unused -- and broken -- hex_encode()
26468 function. Use base16_encode() instead. (Thanks to Timo Lindfors
26469 for pointing out this bug.)
26470 - Only pick and establish intro points after we've gotten a
26472 - Fix assert triggers: if the other side returns an address 0.0.0.0,
26473 don't put it into the client dns cache.
26474 - If a begin failed due to exit policy, but we believe the IP
26475 address should have been allowed, switch that router to exitpolicy
26476 reject *:* until we get our next directory.
26478 o Protocol changes:
26479 - 'Extend' relay cell payloads now include the digest of the
26480 intended next hop's identity key. Now we can verify that we're
26481 extending to the right router, and also extend to routers we
26482 hadn't heard of before.
26485 - Tor nodes can now act as relays (with an advertised ORPort)
26486 without being manually verified by the dirserver operators.
26487 - Uploaded descriptors of unverified routers are now accepted
26488 by the dirservers, and included in the directory.
26489 - Verified routers are listed by nickname in the running-routers
26490 list; unverified routers are listed as "$<fingerprint>".
26491 - We now use hash-of-identity-key in most places rather than
26492 nickname or addr:port, for improved security/flexibility.
26493 - AllowUnverifiedNodes config option to let circuits choose no-name
26494 routers in entry,middle,exit,introduction,rendezvous positions.
26495 Allow middle and rendezvous positions by default.
26496 - When picking unverified routers, skip those with low uptime and/or
26497 low bandwidth, depending on what properties you care about.
26498 - ClientOnly option for nodes that never want to become servers.
26499 - Directory caching.
26500 - "AuthoritativeDir 1" option for the official dirservers.
26501 - Now other nodes (clients and servers) will cache the latest
26502 directory they've pulled down.
26503 - They can enable their DirPort to serve it to others.
26504 - Clients will pull down a directory from any node with an open
26505 DirPort, and check the signature/timestamp correctly.
26506 - Authoritative dirservers now fetch directories from other
26507 authdirservers, to stay better synced.
26508 - Running-routers list tells who's down also, along with noting
26509 if they're verified (listed by nickname) or unverified (listed
26511 - Allow dirservers to serve running-router list separately.
26512 This isn't used yet.
26513 - You can now fetch $DIRURL/running-routers to get just the
26514 running-routers line, not the whole descriptor list. (But
26515 clients don't use this yet.)
26516 - Clients choose nodes proportional to advertised bandwidth.
26517 - Clients avoid using nodes with low uptime as introduction points.
26518 - Handle servers with dynamic IP addresses: don't just replace
26519 options->Address with the resolved one at startup, and
26520 detect our address right before we make a routerinfo each time.
26521 - 'FascistFirewall' option to pick dirservers and ORs on specific
26522 ports; plus 'FirewallPorts' config option to tell FascistFirewall
26523 which ports are open. (Defaults to 80,443)
26524 - Try other dirservers immediately if the one you try is down. This
26525 should tolerate down dirservers better now.
26526 - ORs connect-on-demand to other ORs
26527 - If you get an extend cell to an OR you're not connected to,
26528 connect, handshake, and forward the create cell.
26529 - The authoritative dirservers stay connected to everybody,
26530 and everybody stays connected to 0.0.7 servers, but otherwise
26531 clients/servers expire unused connections after 5 minutes.
26532 - When servers get a sigint, they delay 30 seconds (refusing new
26533 connections) then exit. A second sigint causes immediate exit.
26534 - File and name management:
26535 - Look for .torrc if no CONFDIR "torrc" is found.
26536 - If no datadir is defined, then choose, make, and secure ~/.tor
26538 - If torrc not found, exitpolicy reject *:*.
26539 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
26540 - If no nickname is defined, derive default from hostname.
26541 - Rename secret key files, e.g. identity.key -> secret_id_key,
26542 to discourage people from mailing their identity key to tor-ops.
26543 - Refuse to build a circuit before the directory has arrived --
26544 it won't work anyway, since you won't know the right onion keys
26546 - Parse tor version numbers so we can do an is-newer-than check
26547 rather than an is-in-the-list check.
26548 - New socks command 'resolve', to let us shim gethostbyname()
26550 - A 'tor_resolve' script to access the socks resolve functionality.
26551 - A new socks-extensions.txt doc file to describe our
26552 interpretation and extensions to the socks protocols.
26553 - Add a ContactInfo option, which gets published in descriptor.
26554 - Write tor version at the top of each log file
26555 - New docs in the tarball:
26557 - Document that you should proxy your SSL traffic too.
26558 - Log a warning if the user uses an unsafe socks variant, so people
26559 are more likely to learn about privoxy or socat.
26560 - Log a warning if you're running an unverified server, to let you
26561 know you might want to get it verified.
26562 - Change the default exit policy to reject the default edonkey,
26563 kazaa, gnutella ports.
26564 - Add replace_file() to util.[ch] to handle win32's rename().
26565 - Publish OR uptime in descriptor (and thus in directory) too.
26566 - Remember used bandwidth (both in and out), and publish 15-minute
26567 snapshots for the past day into our descriptor.
26568 - Be more aggressive about trying to make circuits when the network
26569 has changed (e.g. when you unsuspend your laptop).
26570 - Check for time skew on http headers; report date in response to
26572 - If the entrynode config line has only one node, don't pick it as
26574 - Add strict{entry|exit}nodes config options. If set to 1, then
26575 we refuse to build circuits that don't include the specified entry
26577 - OutboundBindAddress config option, to bind to a specific
26578 IP address for outgoing connect()s.
26579 - End truncated log entries (e.g. directories) with "[truncated]".
26582 Changes in version 0.0.7.3 - 2004-08-12
26583 o Stop dnsworkers from triggering an assert failure when you
26584 ask them to resolve the host "".
26587 Changes in version 0.0.7.2 - 2004-07-07
26588 o A better fix for the 0.0.0.0 problem, that will hopefully
26589 eliminate the remaining related assertion failures.
26592 Changes in version 0.0.7.1 - 2004-07-04
26593 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
26594 since internally we use 0.0.0.0 to signify "not yet resolved".
26597 Changes in version 0.0.7 - 2004-06-07
26598 o Fixes for crashes and other obnoxious bugs:
26599 - Fix an epipe bug: sometimes when directory connections failed
26600 to connect, we would give them a chance to flush before closing
26602 - When we detached from a circuit because of resolvefailed, we
26603 would immediately try the same circuit twice more, and then
26604 give up on the resolve thinking we'd tried three different
26606 - Limit the number of intro circuits we'll attempt to build for a
26607 hidden service per 15-minute period.
26608 - Check recommended-software string *early*, before actually parsing
26609 the directory. Thus we can detect an obsolete version and exit,
26610 even if the new directory format doesn't parse.
26611 o Fixes for security bugs:
26612 - Remember which nodes are dirservers when you startup, and if a
26613 random OR enables his dirport, don't automatically assume he's
26614 a trusted dirserver.
26616 - Directory connections were asking the wrong poll socket to
26617 start writing, and not asking themselves to start writing.
26618 - When we detached from a circuit because we sent a begin but
26619 didn't get a connected, we would use it again the first time;
26620 but after that we would correctly switch to a different one.
26621 - Stop warning when the first onion decrypt attempt fails; they
26622 will sometimes legitimately fail now that we rotate keys.
26623 - Override unaligned-access-ok check when $host_cpu is ia64 or
26624 arm. Apparently they allow it but the kernel whines.
26625 - Dirservers try to reconnect periodically too, in case connections
26627 - Fix some memory leaks in directory servers.
26628 - Allow backslash in Win32 filenames.
26629 - Made Tor build complain-free on FreeBSD, hopefully without
26630 breaking other BSD builds. We'll see.
26631 - Check directory signatures based on name of signer, not on whom
26632 we got the directory from. This will let us cache directories more
26634 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
26637 - Doxygen markup on all functions and global variables.
26638 - Make directory functions update routerlist, not replace it. So
26639 now directory disagreements are not so critical a problem.
26640 - Remove the upper limit on number of descriptors in a dirserver's
26641 directory (not that we were anywhere close).
26642 - Allow multiple logfiles at different severity ranges.
26643 - Allow *BindAddress to specify ":port" rather than setting *Port
26644 separately. Allow multiple instances of each BindAddress config
26645 option, so you can bind to multiple interfaces if you want.
26646 - Allow multiple exit policy lines, which are processed in order.
26647 Now we don't need that huge line with all the commas in it.
26648 - Enable accept/reject policies on SOCKS connections, so you can bind
26649 to 0.0.0.0 but still control who can use your OP.
26650 - Updated the man page to reflect these features.
26653 Changes in version 0.0.6.2 - 2004-05-16
26654 o Our integrity-checking digest was checking only the most recent cell,
26655 not the previous cells like we'd thought.
26656 Thanks to Stefan Mark for finding the flaw!
26659 Changes in version 0.0.6.1 - 2004-05-06
26660 o Fix two bugs in our AES counter-mode implementation (this affected
26661 onion-level stream encryption, but not TLS-level). It turns
26662 out we were doing something much more akin to a 16-character
26663 polyalphabetic cipher. Oops.
26664 Thanks to Stefan Mark for finding the flaw!
26665 o Retire moria3 as a directory server, and add tor26 as a directory
26669 Changes in version 0.0.6 - 2004-05-02
26671 - Hidden services and rendezvous points are implemented. Go to
26672 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
26673 hidden services. (This only works via a socks4a proxy such as
26674 Privoxy, and currently it's quite slow.)
26675 - We now rotate link (tls context) keys and onion keys.
26676 - CREATE cells now include oaep padding, so you can tell
26677 if you decrypted them correctly.
26678 - Retry stream correctly when we fail to connect because of
26679 exit-policy-reject (should try another) or can't-resolve-address.
26680 - When we hup a dirserver and we've *removed* a server from the
26681 approved-routers list, now we remove that server from the
26682 in-memory directories too.
26683 - Add bandwidthburst to server descriptor.
26684 - Directories now say which dirserver signed them.
26685 - Use a tor_assert macro that logs failed assertions too.
26686 - Since we don't support truncateds much, don't bother sending them;
26687 just close the circ.
26688 - Fetch randomness from /dev/urandom better (not via fopen/fread)
26689 - Better debugging for tls errors
26690 - Set Content-Type on the directory and hidserv descriptor.
26691 - Remove IVs from cipher code, since AES-ctr has none.
26693 - Fix an assert trigger for exit nodes that's been plaguing us since
26694 the days of 0.0.2prexx (thanks weasel!)
26695 - Fix a bug where we were closing tls connections intermittently.
26696 It turns out openssl keeps its errors around -- so if an error
26697 happens, and you don't ask about it, and then another openssl
26698 operation happens and succeeds, and you ask if there was an error,
26699 it tells you about the first error.
26700 - Fix a bug that's been lurking since 27 may 03 (!)
26701 When passing back a destroy cell, we would use the wrong circ id.
26702 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
26703 - Some versions of openssl have an SSL_pending function that erroneously
26704 returns bytes when there is a non-application record pending.
26705 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
26706 o We were using an array of length zero in a few places.
26707 o Win32's gethostbyname can't resolve an IP to an IP.
26708 o Win32's close can't close a socket.
26709 o Handle windows socket errors correctly.
26711 - check for <sys/limits.h> so we build on FreeBSD again, and
26712 <machine/limits.h> for NetBSD.
26715 Changes in version 0.0.5 - 2004-03-30
26716 o Install torrc as torrc.sample -- we no longer clobber your
26718 o Fix mangled-state bug in directory fetching (was causing sigpipes).
26719 o Only build circuits after we've fetched the directory: clients were
26720 using only the directory servers before they'd fetched a directory.
26721 This also means longer startup time; so it goes.
26722 o Fix an assert trigger where an OP would fail to handshake, and we'd
26723 expect it to have a nickname.
26724 o Work around a tsocks bug: do a socks reject when AP connection dies
26725 early, else tsocks goes into an infinite loop.
26726 o Hold socks connection open until reply is flushed (if possible)
26727 o Make exit nodes resolve IPs to IPs immediately, rather than asking
26728 the dns farm to do it.
26729 o Fix c99 aliasing warnings in rephist.c
26730 o Don't include server descriptors that are older than 24 hours in the
26732 o Give socks 'reject' replies their whole 15s to attempt to flush,
26733 rather than seeing the 60s timeout and assuming the flush had failed.
26734 o Clean automake droppings from the cvs repository
26735 o Add in a 'notice' log level for things the operator should hear
26736 but that aren't warnings
26739 Changes in version 0.0.4 - 2004-03-26
26740 o When connecting to a dirserver or OR and the network is down,
26744 Changes in version 0.0.3 - 2004-03-26
26745 o Warn and fail if server chose a nickname with illegal characters
26746 o Port to Solaris and Sparc:
26747 - include missing header fcntl.h
26748 - have autoconf find -lsocket -lnsl automatically
26749 - deal with hardware word alignment
26750 - make uname() work (solaris has a different return convention)
26751 - switch from using signal() to sigaction()
26752 o Preliminary work on reputation system:
26753 - Keep statistics on success/fail of connect attempts; they're published
26754 by kill -USR1 currently.
26755 - Add a RunTesting option to try to learn link state by creating test
26756 circuits, even when SocksPort is off.
26757 - Remove unused open circuits when there are too many.
26760 Changes in version 0.0.2 - 2004-03-19
26761 - Include strlcpy and strlcat for safer string ops
26762 - define INADDR_NONE so we compile (but still not run) on solaris
26765 Changes in version 0.0.2pre27 - 2004-03-14
26767 - Allow internal tor networks (we were rejecting internal IPs,
26768 now we allow them if they're set explicitly).
26769 - And fix a few endian issues.
26772 Changes in version 0.0.2pre26 - 2004-03-14
26774 - If a stream times out after 15s without a connected cell, don't
26775 try that circuit again: try a new one.
26776 - Retry streams at most 4 times. Then give up.
26777 - When a dirserver gets a descriptor from an unknown router, it
26778 logs its fingerprint (so the dirserver operator can choose to
26779 accept it even without mail from the server operator).
26780 - Inform unapproved servers when we reject their descriptors.
26781 - Make tor build on Windows again. It works as a client, who knows
26783 - Clearer instructions in the torrc for how to set up a server.
26784 - Be more efficient about reading fd's when our global token bucket
26785 (used for rate limiting) becomes empty.
26787 - Stop asserting that computers always go forward in time. It's
26789 - When we sent a cell (e.g. destroy) and then marked an OR connection
26790 expired, we might close it before finishing a flush if the other
26791 side isn't reading right then.
26792 - Don't allow dirservers to start if they haven't defined
26793 RecommendedVersions
26794 - We were caching transient dns failures. Oops.
26795 - Prevent servers from publishing an internal IP as their address.
26796 - Address a strcat vulnerability in circuit.c
26799 Changes in version 0.0.2pre25 - 2004-03-04
26801 - Put the OR's IP in its router descriptor, not its fqdn. That way
26802 we'll stop being stalled by gethostbyname for nodes with flaky dns,
26805 - If the user typed in an address that didn't resolve, the server
26809 Changes in version 0.0.2pre24 - 2004-03-03
26811 - Fix an assertion failure in dns.c, where we were trying to dequeue
26812 a pending dns resolve even if it wasn't pending
26813 - Fix a spurious socks5 warning about still trying to write after the
26814 connection is finished.
26815 - Hold certain marked_for_close connections open until they're finished
26816 flushing, rather than losing bytes by closing them too early.
26817 - Correctly report the reason for ending a stream
26818 - Remove some duplicate calls to connection_mark_for_close
26819 - Put switch_id and start_daemon earlier in the boot sequence, so it
26820 will actually try to chdir() to options.DataDirectory
26821 - Make 'make test' exit(1) if a test fails; fix some unit tests
26822 - Make tor fail when you use a config option it doesn't know about,
26823 rather than warn and continue.
26824 - Make --version work
26825 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
26828 Changes in version 0.0.2pre23 - 2004-02-29
26830 - Print a statement when the first circ is finished, so the user
26831 knows it's working.
26832 - If a relay cell is unrecognized at the end of the circuit,
26833 send back a destroy. (So attacks to mutate cells are more
26835 - New config option 'excludenodes' to avoid certain nodes for circuits.
26836 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
26837 so you can collect coredumps there.
26839 - Fix a bug in tls flushing where sometimes data got wedged and
26840 didn't flush until more data got sent. Hopefully this bug was
26841 a big factor in the random delays we were seeing.
26842 - Make 'connected' cells include the resolved IP, so the client
26843 dns cache actually gets populated.
26844 - Disallow changing from ORPort=0 to ORPort>0 on hup.
26845 - When we time-out on a stream and detach from the circuit, send an
26846 end cell down it first.
26847 - Only warn about an unknown router (in exitnodes, entrynodes,
26848 excludenodes) after we've fetched a directory.
26851 Changes in version 0.0.2pre22 - 2004-02-26
26853 - Servers publish less revealing uname information in descriptors.
26854 - More memory tracking and assertions, to crash more usefully when
26856 - If the default torrc isn't there, just use some default defaults.
26857 Plus provide an internal dirservers file if they don't have one.
26858 - When the user tries to use Tor as an http proxy, give them an http
26859 501 failure explaining that we're a socks proxy.
26860 - Dump a new router.desc on hup, to help confused people who change
26861 their exit policies and then wonder why router.desc doesn't reflect
26863 - Clean up the generic tor.sh init script that we ship with.
26865 - If the exit stream is pending on the resolve, and a destroy arrives,
26866 then the stream wasn't getting removed from the pending list. I
26867 think this was the one causing recent server crashes.
26868 - Use a more robust poll on OSX 10.3, since their poll is flaky.
26869 - When it couldn't resolve any dirservers, it was useless from then on.
26870 Now it reloads the RouterFile (or default dirservers) if it has no
26872 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
26873 many users don't even *have* a /usr/local/sbin/.
26876 Changes in version 0.0.2pre21 - 2004-02-18
26878 - There's a ChangeLog file that actually reflects the changelog.
26879 - There's a 'torify' wrapper script, with an accompanying
26880 tor-tsocks.conf, that simplifies the process of using tsocks for
26881 tor. It even has a man page.
26882 - The tor binary gets installed to sbin rather than bin now.
26883 - Retry streams where the connected cell hasn't arrived in 15 seconds
26884 - Clean up exit policy handling -- get the default out of the torrc,
26885 so we can update it without forcing each server operator to fix
26887 - Allow imaps and pop3s in default exit policy
26889 - Prevent picking middleman nodes as the last node in the circuit
26892 Changes in version 0.0.2pre20 - 2004-01-30
26894 - We now have a deb package, and it's in debian unstable. Go to
26895 it, apt-getters. :)
26896 - I've split the TotalBandwidth option into BandwidthRate (how many
26897 bytes per second you want to allow, long-term) and
26898 BandwidthBurst (how many bytes you will allow at once before the cap
26899 kicks in). This better token bucket approach lets you, say, set
26900 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
26901 performance while not exceeding your monthly bandwidth quota.
26902 - Push out a tls record's worth of data once you've got it, rather
26903 than waiting until you've read everything waiting to be read. This
26904 may improve performance by pipelining better. We'll see.
26905 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
26906 from failed circuits (if they haven't been connected yet) and attach
26908 - Expire old streams that haven't managed to connect. Some day we'll
26909 have them reattach to new circuits instead.
26912 - Fix several memory leaks that were causing servers to become bloated
26914 - Fix a few very rare assert triggers. A few more remain.
26915 - Setuid to User _before_ complaining about running as root.
26918 Changes in version 0.0.2pre19 - 2004-01-07
26920 - Fix deadlock condition in dns farm. We were telling a child to die by
26921 closing the parent's file descriptor to him. But newer children were
26922 inheriting the open file descriptor from the parent, and since they
26923 weren't closing it, the socket never closed, so the child never read
26924 eof, so he never knew to exit. Similarly, dns workers were holding
26925 open other sockets, leading to all sorts of chaos.
26926 - New cleaner daemon() code for forking and backgrounding.
26927 - If you log to a file, it now prints an entry at the top of the
26928 logfile so you know it's working.
26929 - The onionskin challenge length was 30 bytes longer than necessary.
26930 - Started to patch up the spec so it's not quite so out of date.
26933 Changes in version 0.0.2pre18 - 2004-01-02
26935 - Fix endian issues with the 'integrity' field in the relay header.
26936 - Fix a potential bug where connections in state
26937 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
26940 Changes in version 0.0.2pre17 - 2003-12-30
26942 - Made --debuglogfile (or any second log file, actually) work.
26943 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
26944 adversary could force us into an infinite loop.
26947 - Each onionskin handshake now includes a hash of the computed key,
26948 to prove the server's identity and help perfect forward secrecy.
26949 - Changed cell size from 256 to 512 bytes (working toward compatibility
26951 - Changed cell length to 2 bytes, and moved it to the relay header.
26952 - Implemented end-to-end integrity checking for the payloads of
26954 - Separated streamid from 'recognized' (otherwise circuits will get
26955 messed up when we try to have streams exit from the middle). We
26956 use the integrity-checking to confirm that a cell is addressed to
26958 - Randomize the initial circid and streamid values, so an adversary who
26959 breaks into a node can't learn how many circuits or streams have
26963 Changes in version 0.0.2pre16 - 2003-12-14
26965 - Fixed a bug that made HUP trigger an assert
26966 - Fixed a bug where a circuit that immediately failed wasn't being
26967 counted as a failed circuit in counting retries.
26970 - Now we close the circuit when we get a truncated cell: otherwise we're
26971 open to an anonymity attack where a bad node in the path truncates
26972 the circuit and then we open streams at him.
26973 - Add port ranges to exit policies
26974 - Add a conservative default exit policy
26975 - Warn if you're running tor as root
26976 - on HUP, retry OR connections and close/rebind listeners
26977 - options.EntryNodes: try these nodes first when picking the first node
26978 - options.ExitNodes: if your best choices happen to include any of
26979 your preferred exit nodes, you choose among just those preferred
26981 - options.ExcludedNodes: nodes that are never picked in path building
26984 Changes in version 0.0.2pre15 - 2003-12-03
26985 o Robustness and bugfixes:
26986 - Sometimes clients would cache incorrect DNS resolves, which would
26987 really screw things up.
26988 - An OP that goes offline would slowly leak all its sockets and stop
26990 - A wide variety of bugfixes in exit node selection, exit policy
26991 handling, and processing pending streams when a new circuit is
26993 - Pick nodes for a path only from those the directory says are up
26994 - Choose randomly from all running dirservers, not always the first one
26995 - Increase allowed http header size for directory fetch.
26996 - Stop writing to stderr (if we're daemonized it will be closed).
26997 - Enable -g always, so cores will be more useful to me.
26998 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
27001 - Wrote a man page. It lists commonly used options.
27004 - Change default loglevel to warn.
27005 - Make PidFile default to null rather than littering in your CWD.
27006 - OnionRouter config option is now obsolete. Instead it just checks
27008 - Moved to a single unified torrc file for both clients and servers.
27011 Changes in version 0.0.2pre14 - 2003-11-29
27012 o Robustness and bugfixes:
27013 - Force the admin to make the DataDirectory himself
27014 - to get ownership/permissions right
27015 - so clients no longer make a DataDirectory and then never use it
27016 - fix bug where a client who was offline for 45 minutes would never
27017 pull down a directory again
27018 - fix (or at least hide really well) the dns assert bug that was
27019 causing server crashes
27020 - warnings and improved robustness wrt clockskew for certs
27021 - use the native daemon(3) to daemonize, when available
27022 - exit if bind() fails
27023 - exit if neither socksport nor orport is defined
27024 - include our own tor_timegm (Win32 doesn't have its own)
27025 - bugfix for win32 with lots of connections
27026 - fix minor bias in PRNG
27027 - make dirserver more robust to corrupt cached directory
27030 - Wrote the design document (woo)
27032 o Circuit building and exit policies:
27033 - Circuits no longer try to use nodes that the directory has told them
27035 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
27036 bitcounts (18.0.0.0/8).
27037 - Make AP connections standby for a circuit if no suitable circuit
27038 exists, rather than failing
27039 - Circuits choose exit node based on addr/port, exit policies, and
27040 which AP connections are standing by
27041 - Bump min pathlen from 2 to 3
27042 - Relay end cells have a payload to describe why the stream ended.
27043 - If the stream failed because of exit policy, try again with a new
27045 - Clients have a dns cache to remember resolved addresses.
27046 - Notice more quickly when we have no working circuits
27049 - APPort is now called SocksPort
27050 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
27052 - RecommendedVersions is now a config variable rather than
27053 hardcoded (for dirservers)
27054 - Reloads config on HUP
27055 - Usage info on -h or --help
27056 - If you set User and Group config vars, it'll setu/gid to them.
27058 Changes in version 0.0.2pre13 - 2003-10-19
27059 o General stability:
27060 - SSL_write no longer fails when it returns WANTWRITE and the number
27061 of bytes in the buf has changed by the next SSL_write call.
27062 - Fix segfault fetching directory when network is down
27063 - Fix a variety of minor memory leaks
27064 - Dirservers reload the fingerprints file on HUP, so I don't have
27065 to take down the network when I approve a new router
27066 - Default server config file has explicit Address line to specify fqdn
27069 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
27070 - Make listener connections not ever alloc bufs
27072 o Autoconf improvements:
27073 - don't clobber an external CFLAGS in ./configure
27074 - Make install now works
27075 - create var/lib/tor on make install
27076 - autocreate a tor.sh initscript to help distribs
27077 - autocreate the torrc and sample-server-torrc with correct paths
27079 o Log files and Daemonizing now work:
27080 - If --DebugLogFile is specified, log to it at -l debug
27081 - If --LogFile is specified, use it instead of commandline
27082 - If --RunAsDaemon is set, tor forks and backgrounds on startup