1 Changes in version 0.3.3.4-alpha - 2018-03-29
2 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
3 the alpha testing of earlier releases in its series. We are
4 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
6 o New system requirements:
7 - When built with Rust, Tor now depends on version 0.2.39 of the
8 libc crate. Closes tickets 25310 and 25664.
10 o Major bugfixes (relay, connection):
11 - If we have failed to connect to a relay and received a connection
12 refused, timeout, or similar error (at the TCP level), do not try
13 that same address/port again for 60 seconds after the failure has
14 occurred. Fixes bug 24767; bugfix on 0.0.6.
16 o Minor features (geoip):
17 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
18 Country database. Closes ticket 25469.
20 o Minor features (log messages):
21 - Improve log message in the out-of-memory handler to include
22 information about memory usage from the different compression
23 backends. Closes ticket 25372.
25 o Minor features (sandbox):
26 - Explicitly permit the poll() system call when the Linux
27 seccomp2-based sandbox is enabled: apparently, some versions of
28 libc use poll() when calling getpwnam(). Closes ticket 25313.
30 o Minor bugfixes (C correctness):
31 - Fix a very unlikely (impossible, we believe) null pointer
32 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
33 Coverity; this is CID 1430932.
35 o Minor bugfixes (channel, client):
36 - Better identify client connection when reporting to the geoip
37 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
39 o Minor bugfixes (compilation):
40 - Fix a C99 compliance issue in our configuration script that caused
41 compilation issues when compiling Tor with certain versions of
42 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
44 o Minor bugfixes (controller, reliability):
45 - Avoid a (nonfatal) assertion failure when extending a one-hop
46 circuit from the controller to become a multihop circuit. Fixes
47 bug 24903; bugfix on 0.2.5.2-alpha.
49 o Minor bugfixes (networking):
50 - Tor will no longer reject IPv6 address strings from TorBrowser
51 when they are passed as hostnames in SOCKS5 requests. Fixes bug
52 25036, bugfix on Tor 0.3.1.2.
53 - string_is_valid_hostname() will not consider IP strings to be
54 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
56 o Minor bugfixes (onion service v3):
57 - Avoid an assertion failure when the next the next onion service
58 descriptor rotation type is out of sync with the consensus's
59 valid-after time. Instead, log a warning message with extra
60 information, so we can better hunt down the cause of this
61 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
63 o Minor bugfixes (testing):
64 - Avoid intermittent test failures due to a test that had relied on
65 onion service introduction point creation finishing within 5
66 seconds of real clock time. Fixes bug 25450; bugfix
68 - Rust crates are now automatically detected and tested. Previously,
69 some crates were not tested by `make test-rust` due to a static
70 string in the `src/test/test_rust.sh` script specifying which
71 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
73 o Minor bugfixes (testing, benchmarks):
74 - Fix a crash when running benchmark tests on win32 systems. The
75 crash was due to a mutex that wasn't initialized before logging
76 and options were initialized. Fixes bug 25479; bugfix
79 o Minor bugfixes (warnings, ipv6):
80 - Avoid a bug warning that could occur when trying to connect to a
81 relay over IPv6. This warning would occur on a Tor instance that
82 downloads router descriptors, but prefers to use microdescriptors.
83 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
85 o Code simplification and refactoring:
86 - Remove the old (deterministic) directory retry logic entirely:
87 We've used exponential backoff exclusively for some time. Closes
91 - Improved the documentation of AccountingStart parameter. Closes
93 - Update the documentation for "Log" to include the current list of
94 logging domains. Closes ticket 25378.
97 Changes in version 0.3.3.3-alpha - 2018-03-03
98 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
99 It includes an important security fix for a remote crash attack
100 against directory authorities tracked as TROVE-2018-001.
102 Additionally, with this release, we are upgrading the severity of a
103 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
104 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
105 a use-after-free pattern. As such, we are now tracking that bug as
106 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
107 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
109 This release also fixes several minor bugs and annoyances from
112 Relays running 0.3.2.x should upgrade to one of the versions released
113 today, for the fix to TROVE-2018-002. Directory authorities should
114 also upgrade. (Relays on earlier versions might want to update too for
115 the DoS mitigations.)
117 o Major bugfixes (denial-of-service, directory authority):
118 - Fix a protocol-list handling bug that could be used to remotely crash
119 directory authorities with a null-pointer exception. Fixes bug 25074;
120 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
123 o Minor features (compatibility, OpenSSL):
124 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
125 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
126 since they neither disabled TLS 1.3 nor enabled any of the
127 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
130 o Minor features (logging):
131 - Clarify the log messages produced when getrandom() or a related
132 entropy-generation mechanism gives an error. Closes ticket 25120.
134 o Minor features (testing):
135 - Add a "make test-rust" target to run the rust tests only. Closes
138 o Minor bugfixes (denial-of-service):
139 - Fix a possible crash on malformed consensus. If a consensus had
140 contained an unparseable protocol line, it could have made clients
141 and relays crash with a null-pointer exception. To exploit this
142 issue, however, an attacker would need to be able to subvert the
143 directory authority system. Fixes bug 25251; bugfix on
144 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
146 o Minor bugfixes (DoS mitigation):
147 - Add extra safety checks when refilling the circuit creation bucket
148 to ensure we never set a value above the allowed maximum burst.
149 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
150 - When a new consensus arrives, don't update our DoS-mitigation
151 parameters if we aren't a public relay. Fixes bug 25223; bugfix
154 o Minor bugfixes (man page, SocksPort):
155 - Remove dead code from the old "SocksSocket" option, and rename
156 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
157 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
159 o Minor bugfixes (performance):
160 - Reduce the number of circuits that will be opened at once during
161 the circuit build timeout phase. This is done by increasing the
162 idle timeout to 3 minutes, and lowering the maximum number of
163 concurrent learning circuits to 10. Fixes bug 24769; bugfix
166 o Minor bugfixes (spec conformance):
167 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
169 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
170 bugfix on 0.2.9.4-alpha.
172 o Minor bugfixes (spec conformance, rust):
173 - Resolve a denial-of-service issue caused by an infinite loop in
174 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
175 Also tracked as TROVE-2018-003.
177 o Code simplification and refactoring:
178 - Update the "rust dependencies" submodule to be a project-level
179 repository, rather than a user repository. Closes ticket 25323.
182 Changes in version 0.3.3.2-alpha - 2018-02-10
183 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
184 introduces a mechanism to handle the high loads that many relay
185 operators have been reporting recently. It also fixes several bugs in
186 older releases. If this new code proves reliable, we plan to backport
187 it to older supported release series.
189 o Major features (denial-of-service mitigation):
190 - Give relays some defenses against the recent network overload. We
191 start with three defenses (default parameters in parentheses).
192 First: if a single client address makes too many concurrent
193 connections (>100), hang up on further connections. Second: if a
194 single client address makes circuits too quickly (more than 3 per
195 second, with an allowed burst of 90) while also having too many
196 connections open (3), refuse new create cells for the next while
197 (1-2 hours). Third: if a client asks to establish a rendezvous
198 point to you directly, ignore the request. These defenses can be
199 manually controlled by new torrc options, but relays will also
200 take guidance from consensus parameters, so there's no need to
201 configure anything manually. Implements ticket 24902.
203 o Major bugfixes (netflow padding):
204 - Stop adding unneeded channel padding right after we finish
205 flushing to a connection that has been trying to flush for many
206 seconds. Instead, treat all partial or complete flushes as
207 activity on the channel, which will defer the time until we need
208 to add padding. This fix should resolve confusing and scary log
209 messages like "Channel padding timeout scheduled 221453ms in the
210 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
212 o Major bugfixes (protocol versions):
213 - Add Link protocol version 5 to the supported protocols list. Fixes
214 bug 25070; bugfix on 0.3.1.1-alpha.
216 o Major bugfixes (scheduler, consensus):
217 - The scheduler subsystem was failing to promptly notice changes in
218 consensus parameters, making it harder to switch schedulers
219 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
221 o Minor features (denial-of-service avoidance):
222 - Make our OOM handler aware of the geoip client history cache so it
223 doesn't fill up the memory. This check is important for IPv6 and
224 our DoS mitigation subsystem. Closes ticket 25122.
226 o Minor features (directory authority):
227 - When directory authorities are unable to add signatures to a
228 pending consensus, log the reason why. Closes ticket 24849.
230 o Minor features (geoip):
231 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
234 o Minor features (logging, diagnostic):
235 - When logging a failure to create an onion service's descriptor,
236 also log what the problem with the descriptor was. Diagnostic for
239 o Minor bugfix (channel connection):
240 - Use the actual observed address of an incoming relay connection,
241 not the canonical address of the relay from its descriptor, when
242 making decisions about how to handle the incoming connection.
243 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
245 o Minor bugfix (directory authority):
246 - Directory authorities, when refusing a descriptor from a rejected
247 relay, now explicitly tell the relay (in its logs) to set a valid
248 ContactInfo address and contact the bad-relays@ mailing list.
249 Fixes bug 25170; bugfix on 0.2.9.1.
251 o Minor bugfixes (all versions of Tor):
252 - Use the "misspell" tool to detect and fix typos throughout the
253 source code. Fixes bug 23650; bugfix on various versions of Tor.
254 Patch from Deepesh Pathak.
256 o Minor bugfixes (circuit, cannibalization):
257 - Don't cannibalize preemptively-built circuits if we no longer
258 recognize their first hop. This situation can happen if our Guard
259 relay went off the consensus after the circuit was created. Fixes
260 bug 24469; bugfix on 0.0.6.
262 o Minor bugfixes (correctness):
263 - Remove a nonworking, unnecessary check to see whether a circuit
264 hop's identity digest was set when the circuit failed. Fixes bug
265 24927; bugfix on 0.2.4.4-alpha.
267 o Minor bugfixes (logging):
268 - Don't treat inability to store a cached consensus object as a bug:
269 it can happen normally when we are out of disk space. Fixes bug
270 24859; bugfix on 0.3.1.1-alpha.
271 - Fix a (mostly harmless) race condition when invoking
272 LOG_PROTOCOL_WARN message from a subthread while the torrc options
273 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
275 o Minor bugfixes (onion services):
276 - Remove a BUG() statement when a client fetches an onion descriptor
277 that has a lower revision counter than the one in its cache. This
278 can happen in normal circumstances due to HSDir desync. Fixes bug
279 24976; bugfix on 0.3.2.1-alpha.
280 - If we are configured to offer a single onion service, don't log
281 long-term established one hop rendezvous points in the heartbeat.
282 Fixes bug 25116; bugfix on 0.2.9.6-rc.
284 o Minor bugfixes (performance):
285 - Avoid calling protocol_list_supports_protocol() from inside tight
286 loops when running with cached routerinfo_t objects. Instead,
287 summarize the relevant protocols as flags in the routerinfo_t, as
288 we do for routerstatus_t objects. This change simplifies our code
289 a little, and saves a large amount of short-term memory allocation
290 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
292 o Minor bugfixes (Rust FFI):
293 - Fix a minor memory leak which would happen whenever the C code
294 would call the Rust implementation of
295 protover_get_supported_protocols(). This was due to the C version
296 returning a static string, whereas the Rust version newly allocated
297 a CString to pass accross the FFI boundary. Consequently, the C
298 code was not expecting to need to free() what it was given. Fixes
299 bug 25127; bugfix on 0.3.2.1-alpha.
301 o Minor bugfixes (scheduler, KIST):
302 - Avoid adding the same channel twice in the KIST scheduler pending
303 list, which would waste CPU cycles. Fixes bug 24700; bugfix
306 o Minor bugfixes (unit test, monotonic time):
307 - Increase a constant (1msec to 10msec) in the monotonic time test
308 that makes sure the nsec/usec/msec times read are synchronized.
309 This change was needed to accommodate slow systems like armel or
310 when the clock_gettime() is not a VDSO on the running kernel.
311 Fixes bug 25113; bugfix on 0.2.9.1.
313 o Minor bugfixes (v3 onion services):
314 - Look at the "HSRend" protocol version, not the "HSDir" protocol
315 version, when deciding whether a consensus entry can support the
316 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
317 bugfix on 0.3.2.1-alpha.
319 o Code simplification and refactoring:
320 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
322 - Remove a series of counters used to track circuit extend attempts
323 and connection status but that in reality we aren't using for
324 anything other than stats logged by a SIGUSR1 signal. Closes
327 o Documentation (man page):
328 - The HiddenServiceVersion torrc option accepts only one number:
329 either version 2 or 3. Closes ticket 25026; bugfix
333 Changes in version 0.3.3.1-alpha - 2018-01-25
334 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
335 several new features to Tor, including several improvements to
336 bootstrapping, and support for an experimental "vanguards" feature to
337 resist guard discovery attacks. This series also includes better
338 support for applications that need to embed Tor or manage v3
341 o Major features (embedding):
342 - There is now a documented stable API for programs that need to
343 embed Tor. See tor_api.h for full documentation and known bugs.
345 - Tor now has support for restarting in the same process.
346 Controllers that run Tor using the "tor_api.h" interface can now
347 restart Tor after Tor has exited. This support is incomplete,
348 however: we fixed crash bugs that prevented it from working at
349 all, but many bugs probably remain, including a possibility of
350 security issues. Implements ticket 24581.
352 o Major features (IPv6, directory documents):
353 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
354 consensus. This information makes it easier for IPv6 clients to
355 bootstrap and choose reachable entry guards. Implements 23826.
356 - Add consensus method 28, which removes IPv6 ORPorts from
357 microdescriptors. Now that the consensus contains IPv6 ORPorts,
358 they are redundant in microdescs. This change will be used by Tor
359 clients on 0.2.8.x and later. (That is to say, with all Tor
360 clients having IPv6 bootstrap and guard support.) Implements 23828.
361 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
362 set by different numbers of authorities. Fixes 23870
365 o Major features (onion service v3, control port):
366 - The control port now supports commands and events for v3 onion
367 services. It is now possible to create ephemeral v3 services using
368 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
369 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
370 DEL_ONION) have been extended to support v3 onion services. Closes
371 ticket 20699; implements proposal 284.
373 o Major features (onion services):
374 - Provide torrc options to pin the second and third hops of onion
375 service circuits to a list of nodes. The option HSLayer2Guards
376 pins the second hop, and the option HSLayer3Guards pins the third
377 hop. These options are for use in conjunction with experiments
378 with "vanguards" for preventing guard enumeration attacks. Closes
381 o Major features (rust, portability, experimental):
382 - Tor now ships with an optional implementation of one of its
383 smaller modules (protover.c) in the Rust programming language. To
384 try it out, install a Rust build environment, and configure Tor
385 with "--enable-rust --enable-cargo-online-mode". This should not
386 cause any user-visible changes, but should help us gain more
387 experience with Rust, and plan future Rust integration work.
388 Implementation by Chelsea Komlo. Closes ticket 22840.
390 o Major features (storage, configuration):
391 - Users can store cached directory documents somewhere other than
392 the DataDirectory by using the CacheDirectory option. Similarly,
393 the storage location for relay's keys can be overridden with the
394 KeyDirectory option. Closes ticket 22703.
396 o Major features (v3 onion services, ipv6):
397 - When v3 onion service clients send introduce cells, they now
398 include the IPv6 address of the rendezvous point, if it has one.
399 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
400 in future Tor versions, IPv6-only v3 single onion services will be
401 able to use IPv6 addresses to connect directly to the rendezvous
402 point. Closes ticket 23577. Patch by Neel Chauhan.
404 o Major bugfixes (onion services, retry behavior):
405 - Fix an "off by 2" error in counting rendezvous failures on the
406 onion service side. While we thought we would stop the rendezvous
407 attempt after one failed circuit, we were actually making three
408 circuit attempts before giving up. Now switch to a default of 2,
409 and allow the consensus parameter "hs_service_max_rdv_failures" to
410 override. Fixes bug 24895; bugfix on 0.0.6.
411 - New-style (v3) onion services now obey the "max rendezvous circuit
412 attempts" logic. Previously they would make as many rendezvous
413 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
414 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
416 o Major bugfixes (relays):
417 - Fix a set of false positives where relays would consider
418 connections to other relays as being client-only connections (and
419 thus e.g. deserving different link padding schemes) if those
420 relays fell out of the consensus briefly. Now we look only at the
421 initial handshake and whether the connection authenticated as a
422 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
424 o Minor feature (IPv6):
425 - Make IPv6-only clients wait for microdescs for relays, even if we
426 were previously using descriptors (or were using them as a bridge)
427 and have a cached descriptor for them. Implements 23827.
428 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
429 them, rather than waiting to download microdescriptors.
432 o Minor features (cleanup):
433 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
434 when it stops. Closes ticket 23271.
436 o Minor features (defensive programming):
437 - Most of the functions in Tor that free objects have been replaced
438 with macros that free the objects and set the corresponding
439 pointers to NULL. This change should help prevent a large class of
440 dangling pointer bugs. Closes ticket 24337.
441 - Where possible, the tor_free() macro now only evaluates its input
442 once. Part of ticket 24337.
443 - Check that microdesc ed25519 ids are non-zero in
444 node_get_ed25519_id() before returning them. Implements 24001,
445 patch by "aruna1234".
447 o Minor features (directory authority):
448 - Make the "Exit" flag assignment only depend on whether the exit
449 policy allows connections to ports 80 and 443. Previously relays
450 would get the Exit flag if they allowed connections to one of
451 these ports and also port 6667. Resolves ticket 23637.
453 o Minor features (embedding):
454 - Tor can now start with a preauthenticated control connection
455 created by the process that launched it. This feature is meant for
456 use by programs that want to launch and manage a Tor process
457 without allowing other programs to manage it as well. For more
458 information, see the __OwningControllerFD option documented in
459 control-spec.txt. Closes ticket 23900.
460 - On most errors that would cause Tor to exit, it now tries to
461 return from the tor_main() function, rather than calling the
462 system exit() function. Most users won't notice a difference here,
463 but it should make a significant for programs that run Tor inside
464 a separate thread: they should now be able to survive Tor's exit
465 conditions rather than having Tor shut down the entire process.
467 - Applications that want to embed Tor can now tell Tor not to
468 register any of its own POSIX signal handlers, using the
469 __DisableSignalHandlers option. Closes ticket 24588.
471 o Minor features (fallback directory list):
472 - Avoid selecting fallbacks that change their IP addresses too
473 often. Select more fallbacks by ignoring the Guard flag, and
474 allowing lower cutoffs for the Running and V2Dir flags. Also allow
475 a lower bandwidth, and a higher number of fallbacks per operator
476 (5% of the list). Implements ticket 24785.
477 - Update the fallback whitelist and blacklist based on opt-ins and
478 relay changes. Closes tickets 22321, 24678, 22527, 24135,
481 o Minor features (fallback directory mirror configuration):
482 - Add a nickname to each fallback in a C comment. This makes it
483 easier for operators to find their relays, and allows stem to use
484 nicknames to identify fallbacks. Implements ticket 24600.
485 - Add a type and version header to the fallback directory mirror
486 file. Also add a delimiter to the end of each fallback entry. This
487 helps external parsers like stem and Relay Search. Implements
489 - Add an extrainfo cache flag for each fallback in a C comment. This
490 allows stem to use fallbacks to fetch extra-info documents, rather
491 than using authorities. Implements ticket 22759.
492 - Add the generateFallbackDirLine.py script for automatically
493 generating fallback directory mirror lines from relay fingerprints.
494 No more typos! Add the lookupFallbackDirContact.py script for
495 automatically looking up operator contact info from relay
496 fingerprints. Implements ticket 24706, patch by teor and atagar.
497 - Reject any fallback directory mirror that serves an expired
498 consensus. Implements ticket 20942, patch by "minik".
499 - Remove commas and equals signs from external string inputs to the
500 fallback list. This avoids format confusion attacks. Implements
502 - Remove the "weight=10" line from fallback directory mirror
503 entries. Ticket 24681 will maintain the current fallback weights
504 by changing Tor's default fallback weight to 10. Implements
506 - Stop logging excessive information about fallback netblocks.
507 Implements ticket 24791.
509 o Minor features (forward-compatibility):
510 - If a relay supports some link authentication protocol that we do
511 not recognize, then include that relay's ed25519 key when telling
512 other relays to extend to it. Previously, we treated future
513 versions as if they were too old to support ed25519 link
514 authentication. Closes ticket 20895.
516 o Minor features (heartbeat):
517 - Add onion service information to our heartbeat logs, displaying
518 stats about the activity of configured onion services. Closes
521 o Minor features (instrumentation, development):
522 - Add the MainloopStats option to allow developers to get
523 instrumentation information from the main event loop via the
524 heartbeat messages. We hope to use this to improve Tor's behavior
525 when it's trying to sleep. Closes ticket 24605.
527 o Minor features (log messages):
528 - Improve a warning message that happens when we fail to re-parse an
529 old router because of an expired certificate. Closes ticket 20020.
530 - Make the log more quantitative when we hit MaxMemInQueues
531 threshold exposing some values. Closes ticket 24501.
533 o Minor features (logging, android):
534 - Added support for the Android logging subsystem. Closes
537 o Minor features (performance):
538 - Support predictive circuit building for onion service circuits
539 with multiple layers of guards. Closes ticket 23101.
540 - Use stdatomic.h where available, rather than mutexes, to implement
541 atomic_counter_t. Closes ticket 23953.
543 o Minor features (performance, 32-bit):
544 - Improve performance on 32-bit systems by avoiding 64-bit division
545 when calculating the timestamp in milliseconds for channel padding
546 computations. Implements ticket 24613.
547 - Improve performance on 32-bit systems by avoiding 64-bit division
548 when timestamping cells and buffer chunks for OOM calculations.
549 Implements ticket 24374.
551 o Minor features (performance, OSX, iOS):
552 - Use the mach_approximate_time() function (when available) to
553 implement coarse monotonic time. Having a coarse time function
554 should avoid a large number of system calls, and improve
555 performance slightly, especially under load. Closes ticket 24427.
557 o Minor features (performance, windows):
558 - Improve performance on Windows Vista and Windows 7 by adjusting
559 TCP send window size according to the recommendation from
560 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
563 o Minor features (relay):
564 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
565 operator to use a more reasonable ("reduced") exit policy, rather
566 than the default one. If you want to run an exit node without
567 thinking too hard about which ports to allow, this one is for you.
568 Closes ticket 13605. Patch from Neel Chauhan.
570 o Minor features (testing, debugging, embedding):
571 - For development purposes, Tor now has a mode in which it runs for
572 a few seconds, then stops, and starts again without exiting the
573 process. This mode is meant to help us debug various issues with
574 ticket 23847. To use this feature, compile with
575 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
576 environment variable. This is expected to crash a lot, and is
577 really meant for developers only. It will likely be removed in a
578 future release. Implements ticket 24583.
580 o Minor bugfix (network IPv6 test):
581 - Tor's test scripts now check if "ping -6 ::1" works when the user
582 runs "make test-network-all". Fixes bug 24677; bugfix on
583 0.2.9.3-alpha. Patch by "ffmancera".
585 o Minor bugfixes (build, rust):
586 - Fix output of autoconf checks to display success messages for Rust
587 dependencies and a suitable rustc compiler version. Fixes bug
588 24612; bugfix on 0.3.1.3-alpha.
589 - When building with Rust on OSX, link against libresolv, to work
590 around the issue at https://github.com/rust-lang/rust/issues/46797.
591 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
592 - Don't pass the --quiet option to cargo: it seems to suppress some
593 errors, which is not what we want to do when building. Fixes bug
594 24518; bugfix on 0.3.1.7.
595 - Build correctly when building from outside Tor's source tree with
596 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
599 o Minor bugfixes (directory authorities, IPv6):
600 - When creating a routerstatus (vote) from a routerinfo (descriptor),
601 set the IPv6 address to the unspecified IPv6 address, and
602 explicitly initialize the port to zero. Fixes bug 24488; bugfix
605 o Minor bugfixes (fallback directory mirrors):
606 - Make updateFallbackDirs.py search harder for python. (Some OSs
607 don't put it in /usr/bin.) Fixes bug 24708; bugfix
610 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
611 - When hibernating, close connections normally and allow them to
612 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
614 - Do not attempt to launch self-reachability tests when entering
615 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
616 - Resolve several bugs related to descriptor fetching on bridge
617 clients with bandwidth accounting enabled. (This combination is
618 not recommended!) Fixes a case of bug 12062; bugfix
620 - When hibernating, do not attempt to launch DNS checks. Fixes a
621 case of bug 12062; bugfix on 0.1.2.2-alpha.
622 - When hibernating, do not try to upload or download descriptors.
623 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
625 o Minor bugfixes (IPv6, bridges):
626 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
627 bugfix on 0.2.8.2-alpha.
628 - Tor now sets IPv6 address in the routerstatus as well as in the
629 router descriptors when updating addresses for a bridge. Closes
630 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
632 o Minor bugfixes (linux seccomp2 sandbox):
633 - When running with the sandbox enabled, reload configuration files
634 correctly even when %include was used. Previously we would crash.
635 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
637 o Minor bugfixes (memory leaks):
638 - Avoid possible at-exit memory leaks related to use of Libevent's
639 event_base_once() function. (This function tends to leak memory if
640 the event_base is closed before the event fires.) Fixes bug 24584;
641 bugfix on 0.2.8.1-alpha.
642 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
645 o Minor bugfixes (OSX):
646 - Don't exit the Tor process if setrlimit() fails to change the file
647 limit (which can happen sometimes on some versions of OSX). Fixes
648 bug 21074; bugfix on 0.0.9pre5.
650 o Minor bugfixes (performance, fragile-hardening):
651 - Improve the performance of our consensus-diff application code
652 when Tor is built with the --enable-fragile-hardening option set.
653 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
655 o Minor bugfixes (performance, timeouts):
656 - Consider circuits for timeout as soon as they complete a hop. This
657 is more accurate than applying the timeout in
658 circuit_expire_building() because that function is only called
659 once per second, which is now too slow for typical timeouts on the
660 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
661 - Use onion service circuits (and other circuits longer than 3 hops)
662 to calculate a circuit build timeout. Previously, Tor only
663 calculated its build timeout based on circuits that planned to be
664 exactly 3 hops long. With this change, we include measurements
665 from all circuits at the point where they complete their third
666 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
668 o Minor bugfixes (testing):
669 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
670 bugfix on 0.2.3.1-alpha.
671 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
672 25005; bugfix on 0.3.2.7-rc.
674 o Code simplification and refactoring:
675 - Remove /usr/athena from search path in configure.ac. Closes
677 - Remove duplicate code in node_has_curve25519_onion_key() and
678 node_get_curve25519_onion_key(), and add a check for a zero
679 microdesc curve25519 onion key. Closes ticket 23966, patch by
680 "aruna1234" and teor.
681 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
682 memory allocations with large numbers of OR connections (e.g.
683 relays). Closes ticket 24119.
684 - Separate the function that deletes ephemeral files when Tor
686 - Small changes to Tor's buf_t API to make it suitable for use as a
687 general-purpose safe string constructor. Closes ticket 22342.
688 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
689 avoid source code identifier confusion. Closes ticket 24467.
690 - The tor_git_revision[] constant no longer needs to be redeclared
691 by everything that links against the rest of Tor. Done as part of
692 ticket 23845, to simplify our external API.
693 - We make extend_info_from_node() use node_get_curve25519_onion_key()
694 introduced in ticket 23577 to access the curve25519 public keys
695 rather than accessing it directly. Closes ticket 23760. Patch by
697 - Add a function to log channels' scheduler state changes to aid
698 debugging efforts. Closes ticket 24531.
701 - Add documentation on how to build tor with Rust dependencies
702 without having to be online. Closes ticket 22907; bugfix
704 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
705 traffic. Closes ticket 24318.
706 - Document that OutboundBindAddress doesn't apply to DNS requests.
707 Closes ticket 22145. Patch from Aruna Maurya.
708 - Document that operators who run more than one relay or bridge are
709 expected to set MyFamily and ContactInfo correctly. Closes
712 o Code simplification and refactoring (channels):
713 - Remove the incoming and outgoing channel queues. These were never
714 used, but still took up a step in our fast path.
715 - The majority of the channel unit tests have been rewritten and the
716 code coverage has now been raised to 83.6% for channel.c. Closes
718 - Remove other dead code from the channel subsystem: All together,
719 this cleanup has removed more than 1500 lines of code overall and
720 adding very little except for unit test.
722 o Code simplification and refactoring (circuit rendezvous):
723 - Split the client-size rendezvous circuit lookup into two
724 functions: one that returns only established circuits and another
725 that returns all kinds of circuits. Closes ticket 23459.
727 o Code simplification and refactoring (controller):
728 - Make most of the variables in networkstatus_getinfo_by_purpose()
729 const. Implements ticket 24489.
732 Changes in version 0.3.2.9 - 2018-01-09
733 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
735 The 0.3.2 series includes our long-anticipated new onion service
736 design, with numerous security features. (For more information, see
737 our blog post at https://blog.torproject.org/fall-harvest.) We also
738 have a new circuit scheduler algorithm for improved performance on
739 relays everywhere (see https://blog.torproject.org/kist-and-tell),
740 along with many smaller features and bugfixes.
742 Per our stable release policy, we plan to support each stable release
743 series for at least the next nine months, or for three months after
744 the first stable release of the next series: whichever is longer. If
745 you need a release with long-term support, we recommend that you stay
746 with the 0.2.9 series.
748 Below is a list of the changes since 0.3.2.8-rc. For a list of all
749 changes since 0.3.1, see the ReleaseNotes file.
751 o Minor features (fallback directory mirrors):
752 - The fallback directory list has been re-generated based on the
753 current status of the network. Tor uses fallback directories to
754 bootstrap when it doesn't yet have up-to-date directory
755 information. Closes ticket 24801.
756 - Make the default DirAuthorityFallbackRate 0.1, so that clients
757 prefer to bootstrap from fallback directory mirrors. This is a
758 follow-up to 24679, which removed weights from the default
759 fallbacks. Implements ticket 24681.
761 o Minor features (geoip):
762 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
765 o Minor bugfixes (address selection):
766 - When the fascist_firewall_choose_address_ functions don't find a
767 reachable address, set the returned address to the null address
768 and port. This is a precautionary measure, because some callers do
769 not check the return value. Fixes bug 24736; bugfix
772 o Minor bugfixes (compilation):
773 - Resolve a few shadowed-variable warnings in the onion service
774 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
776 o Minor bugfixes (portability, msvc):
777 - Fix a bug in the bit-counting parts of our timing-wheel code on
778 MSVC. (Note that MSVC is still not a supported build platform, due
779 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
783 Changes in version 0.3.2.8-rc - 2017-12-21
784 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
785 schedulers that had led servers under heavy load to overload their
786 outgoing connections. All relay operators running earlier 0.3.2.x
787 versions should upgrade. This version also includes a mitigation for
788 over-full DESTROY queues leading to out-of-memory conditions: if it
789 works, we will soon backport it to earlier release series.
791 This is the second release candidate in the 0.3.2 series. If we find
792 no new bugs or regression here, then the first stable 0.3.2 release
793 will be nearly identical to this.
795 o Major bugfixes (KIST, scheduler):
796 - The KIST scheduler did not correctly account for data already
797 enqueued in each connection's send socket buffer, particularly in
798 cases when the TCP/IP congestion window was reduced between
799 scheduler calls. This situation lead to excessive per-connection
800 buffering in the kernel, and a potential memory DoS. Fixes bug
801 24665; bugfix on 0.3.2.1-alpha.
803 o Minor features (geoip):
804 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
807 o Minor bugfixes (hidden service v3):
808 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
809 the probability of reaching a service for a client missing
810 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
812 o Minor bugfixes (memory usage):
813 - When queuing DESTROY cells on a channel, only queue the circuit-id
814 and reason fields: not the entire 514-byte cell. This fix should
815 help mitigate any bugs or attacks that fill up these queues, and
816 free more RAM for other uses. Fixes bug 24666; bugfix
819 o Minor bugfixes (scheduler, KIST):
820 - Use a sane write limit for KISTLite when writing onto a connection
821 buffer instead of using INT_MAX and shoving as much as it can.
822 Because the OOM handler cleans up circuit queues, we are better
823 off at keeping them in that queue instead of the connection's
824 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
827 Changes in version 0.3.2.7-rc - 2017-12-14
828 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
829 including some that could affect reliability or correctness.
831 This is the first release candidate in the 0.3.2 series. If we find no
832 new bugs or regression here, then the first stable 0.3.2. release will
833 be nearly identical to this.
835 o Major bugfixes (circuit prediction):
836 - Fix circuit prediction logic so that a client doesn't treat a port
837 as being "handled" by a circuit if that circuit already has
838 isolation settings on it. This change should make Tor clients more
839 responsive by improving their chances of having a pre-created
840 circuit ready for use when a request arrives. Fixes bug 18859;
841 bugfix on 0.2.3.3-alpha.
843 o Minor features (logging):
844 - Provide better warnings when the getrandom() syscall fails. Closes
847 o Minor features (portability):
848 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
849 (It doesn't yet work with the sandbox enabled.) Closes
852 o Minor bugfixes (bridge clients, bootstrap):
853 - Retry directory downloads when we get our first bridge descriptor
854 during bootstrap or while reconnecting to the network. Keep
855 retrying every time we get a bridge descriptor, until we have a
856 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
857 - Stop delaying bridge descriptor fetches when we have cached bridge
858 descriptors. Instead, only delay bridge descriptor fetches when we
859 have at least one reachable bridge. Fixes part of bug 24367;
860 bugfix on 0.2.0.3-alpha.
861 - Stop delaying directory fetches when we have cached bridge
862 descriptors. Instead, only delay bridge descriptor fetches when
863 all our bridges are definitely unreachable. Fixes part of bug
864 24367; bugfix on 0.2.0.3-alpha.
866 o Minor bugfixes (compilation):
867 - Fix a signed/unsigned comparison warning introduced by our fix to
868 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
870 o Minor bugfixes (correctness):
871 - Fix several places in our codebase where a C compiler would be
872 likely to eliminate a check, based on assuming that undefined
873 behavior had not happened elsewhere in the code. These cases are
874 usually a sign of redundant checking or dubious arithmetic. Found
875 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
876 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
879 o Minor bugfixes (onion service v3):
880 - Fix a race where an onion service would launch a new intro circuit
881 after closing an old one, but fail to register it before freeing
882 the previously closed circuit. This bug was making the service
883 unable to find the established intro circuit and thus not upload
884 its descriptor, thus making a service unavailable for up to 24
885 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
887 o Minor bugfixes (scheduler, KIST):
888 - Properly set the scheduler state of an unopened channel in the
889 KIST scheduler main loop. This prevents a harmless but annoying
890 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
891 - Avoid a possible integer overflow when computing the available
892 space on the TCP buffer of a channel. This had no security
893 implications; but could make KIST allow too many cells on a
894 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
895 - Downgrade to "info" a harmless warning about the monotonic time
896 moving backwards: This can happen on platform not supporting
897 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
900 Changes in version 0.3.2.6-alpha - 2017-12-01
901 This version of Tor is the latest in the 0.3.2 alpha series. It
902 includes fixes for several important security issues. All Tor users
903 should upgrade to this release, or to one of the other releases coming
906 o Major bugfixes (security):
907 - Fix a denial of service bug where an attacker could use a
908 malformed directory object to cause a Tor instance to pause while
909 OpenSSL would try to read a passphrase from the terminal. (Tor
910 instances run without a terminal, which is the case for most Tor
911 packages, are not impacted.) Fixes bug 24246; bugfix on every
912 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
913 Found by OSS-Fuzz as testcase 6360145429790720.
914 - Fix a denial of service issue where an attacker could crash a
915 directory authority using a malformed router descriptor. Fixes bug
916 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
918 - When checking for replays in the INTRODUCE1 cell data for a
919 (legacy) onion service, correctly detect replays in the RSA-
920 encrypted part of the cell. We were previously checking for
921 replays on the entire cell, but those can be circumvented due to
922 the malleability of Tor's legacy hybrid encryption. This fix helps
923 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
924 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
927 o Major bugfixes (security, onion service v2):
928 - Fix a use-after-free error that could crash v2 Tor onion services
929 when they failed to open circuits while expiring introduction
930 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
931 also tracked as TROVE-2017-013 and CVE-2017-8823.
933 o Major bugfixes (security, relay):
934 - When running as a relay, make sure that we never build a path
935 through ourselves, even in the case where we have somehow lost the
936 version of our descriptor appearing in the consensus. Fixes part
937 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
938 as TROVE-2017-012 and CVE-2017-8822.
939 - When running as a relay, make sure that we never choose ourselves
940 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
941 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
943 o Minor feature (relay statistics):
944 - Change relay bandwidth reporting stats interval from 4 hours to 24
945 hours in order to reduce the efficiency of guard discovery
946 attacks. Fixes ticket 23856.
948 o Minor features (directory authority):
949 - Add an IPv6 address for the "bastet" directory authority. Closes
952 o Minor bugfixes (client):
953 - By default, do not enable storage of client-side DNS values. These
954 values were unused by default previously, but they should not have
955 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
958 Changes in version 0.3.1.9 - 2017-12-01:
959 Tor 0.3.1.9 backports important security and stability fixes from the
960 0.3.2 development series. All Tor users should upgrade to this
961 release, or to another of the releases coming out today.
963 o Major bugfixes (security, backport from 0.3.2.6-alpha):
964 - Fix a denial of service bug where an attacker could use a
965 malformed directory object to cause a Tor instance to pause while
966 OpenSSL would try to read a passphrase from the terminal. (Tor
967 instances run without a terminal, which is the case for most Tor
968 packages, are not impacted.) Fixes bug 24246; bugfix on every
969 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
970 Found by OSS-Fuzz as testcase 6360145429790720.
971 - Fix a denial of service issue where an attacker could crash a
972 directory authority using a malformed router descriptor. Fixes bug
973 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
975 - When checking for replays in the INTRODUCE1 cell data for a
976 (legacy) onion service, correctly detect replays in the RSA-
977 encrypted part of the cell. We were previously checking for
978 replays on the entire cell, but those can be circumvented due to
979 the malleability of Tor's legacy hybrid encryption. This fix helps
980 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
981 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
984 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
985 - Fix a use-after-free error that could crash v2 Tor onion services
986 when they failed to open circuits while expiring introduction
987 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
988 also tracked as TROVE-2017-013 and CVE-2017-8823.
990 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
991 - When running as a relay, make sure that we never build a path
992 through ourselves, even in the case where we have somehow lost the
993 version of our descriptor appearing in the consensus. Fixes part
994 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
995 as TROVE-2017-012 and CVE-2017-8822.
996 - When running as a relay, make sure that we never choose ourselves
997 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
998 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1000 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1001 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1002 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1003 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1004 identifying and finding a workaround to this bug and to Moritz,
1005 Arthur Edelstein, and Roger for helping to track it down and
1008 o Minor features (bridge):
1009 - Bridges now include notice in their descriptors that they are
1010 bridges, and notice of their distribution status, based on their
1011 publication settings. Implements ticket 18329. For more fine-
1012 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1015 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1016 - Add an IPv6 address for the "bastet" directory authority. Closes
1019 o Minor features (geoip):
1020 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1023 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1024 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1025 relays, to prevent spurious address resolutions and descriptor
1026 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1027 bugfix on in 0.2.8.1-alpha.
1029 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1030 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1031 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1033 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1034 - When a circuit is marked for close, do not attempt to package any
1035 cells for channels on that circuit. Previously, we would detect
1036 this condition lower in the call stack, when we noticed that the
1037 circuit had no attached channel, and log an annoying message.
1038 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1040 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
1041 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1042 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1045 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1046 - Avoid a crash when transitioning from client mode to bridge mode.
1047 Previously, we would launch the worker threads whenever our
1048 "public server" mode changed, but not when our "server" mode
1049 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1052 Changes in version 0.3.0.13 - 2017-12-01
1053 Tor 0.3.0.13 backports important security and stability bugfixes from
1054 later Tor releases. All Tor users should upgrade to this release, or
1055 to another of the releases coming out today.
1057 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1058 2018. If you need a release with long-term support, please stick with
1059 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1061 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1062 - Fix a denial of service bug where an attacker could use a
1063 malformed directory object to cause a Tor instance to pause while
1064 OpenSSL would try to read a passphrase from the terminal. (Tor
1065 instances run without a terminal, which is the case for most Tor
1066 packages, are not impacted.) Fixes bug 24246; bugfix on every
1067 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1068 Found by OSS-Fuzz as testcase 6360145429790720.
1069 - Fix a denial of service issue where an attacker could crash a
1070 directory authority using a malformed router descriptor. Fixes bug
1071 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1073 - When checking for replays in the INTRODUCE1 cell data for a
1074 (legacy) onion service, correctly detect replays in the RSA-
1075 encrypted part of the cell. We were previously checking for
1076 replays on the entire cell, but those can be circumvented due to
1077 the malleability of Tor's legacy hybrid encryption. This fix helps
1078 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1079 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1082 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1083 - Fix a use-after-free error that could crash v2 Tor onion services
1084 when they failed to open circuits while expiring introduction
1085 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1086 also tracked as TROVE-2017-013 and CVE-2017-8823.
1088 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1089 - When running as a relay, make sure that we never build a path
1090 through ourselves, even in the case where we have somehow lost the
1091 version of our descriptor appearing in the consensus. Fixes part
1092 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1093 as TROVE-2017-012 and CVE-2017-8822.
1094 - When running as a relay, make sure that we never choose ourselves
1095 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1096 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1098 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1099 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1100 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1101 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1102 identifying and finding a workaround to this bug and to Moritz,
1103 Arthur Edelstein, and Roger for helping to track it down and
1106 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1107 - Enable a couple of pieces of Windows hardening: one
1108 (HeapEnableTerminationOnCorruption) that has been on-by-default
1109 since Windows 8, and unavailable before Windows 7; and one
1110 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1111 affect us, but shouldn't do any harm. Closes ticket 21953.
1113 o Minor features (bridge, backport from 0.3.1.9):
1114 - Bridges now include notice in their descriptors that they are
1115 bridges, and notice of their distribution status, based on their
1116 publication settings. Implements ticket 18329. For more fine-
1117 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1120 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1121 - Add an IPv6 address for the "bastet" directory authority. Closes
1124 o Minor features (geoip):
1125 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1128 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1129 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1130 relays, to prevent spurious address resolutions and descriptor
1131 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1132 bugfix on in 0.2.8.1-alpha.
1134 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1135 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1136 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1138 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1139 - When a circuit is marked for close, do not attempt to package any
1140 cells for channels on that circuit. Previously, we would detect
1141 this condition lower in the call stack, when we noticed that the
1142 circuit had no attached channel, and log an annoying message.
1143 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1145 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1146 - Avoid a crash when transitioning from client mode to bridge mode.
1147 Previously, we would launch the worker threads whenever our
1148 "public server" mode changed, but not when our "server" mode
1149 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1151 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1152 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1153 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1156 Changes in version 0.2.9.14 - 2017-12-01
1157 Tor 0.3.0.13 backports important security and stability bugfixes from
1158 later Tor releases. All Tor users should upgrade to this release, or
1159 to another of the releases coming out today.
1161 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1162 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1163 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1164 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1165 identifying and finding a workaround to this bug and to Moritz,
1166 Arthur Edelstein, and Roger for helping to track it down and
1169 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1170 - Fix a denial of service bug where an attacker could use a
1171 malformed directory object to cause a Tor instance to pause while
1172 OpenSSL would try to read a passphrase from the terminal. (Tor
1173 instances run without a terminal, which is the case for most Tor
1174 packages, are not impacted.) Fixes bug 24246; bugfix on every
1175 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1176 Found by OSS-Fuzz as testcase 6360145429790720.
1177 - Fix a denial of service issue where an attacker could crash a
1178 directory authority using a malformed router descriptor. Fixes bug
1179 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1181 - When checking for replays in the INTRODUCE1 cell data for a
1182 (legacy) onion service, correctly detect replays in the RSA-
1183 encrypted part of the cell. We were previously checking for
1184 replays on the entire cell, but those can be circumvented due to
1185 the malleability of Tor's legacy hybrid encryption. This fix helps
1186 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1187 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1190 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1191 - Fix a use-after-free error that could crash v2 Tor onion services
1192 when they failed to open circuits while expiring introduction
1193 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1194 also tracked as TROVE-2017-013 and CVE-2017-8823.
1196 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1197 - When running as a relay, make sure that we never build a path
1198 through ourselves, even in the case where we have somehow lost the
1199 version of our descriptor appearing in the consensus. Fixes part
1200 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1201 as TROVE-2017-012 and CVE-2017-8822.
1203 o Minor features (bridge, backport from 0.3.1.9):
1204 - Bridges now include notice in their descriptors that they are
1205 bridges, and notice of their distribution status, based on their
1206 publication settings. Implements ticket 18329. For more fine-
1207 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1210 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1211 - Add an IPv6 address for the "bastet" directory authority. Closes
1214 o Minor features (geoip):
1215 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1218 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1219 - Enable a couple of pieces of Windows hardening: one
1220 (HeapEnableTerminationOnCorruption) that has been on-by-default
1221 since Windows 8, and unavailable before Windows 7; and one
1222 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1223 affect us, but shouldn't do any harm. Closes ticket 21953.
1225 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1226 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1227 relays, to prevent spurious address resolutions and descriptor
1228 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1229 bugfix on in 0.2.8.1-alpha.
1231 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1232 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1233 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1235 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1236 - When a circuit is marked for close, do not attempt to package any
1237 cells for channels on that circuit. Previously, we would detect
1238 this condition lower in the call stack, when we noticed that the
1239 circuit had no attached channel, and log an annoying message.
1240 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1242 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1243 - Avoid a crash when transitioning from client mode to bridge mode.
1244 Previously, we would launch the worker threads whenever our
1245 "public server" mode changed, but not when our "server" mode
1246 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1248 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1249 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1250 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1253 Changes in version 0.2.8.17 - 2017-12-01
1254 Tor 0.2.8.17 backports important security and stability bugfixes from
1255 later Tor releases. All Tor users should upgrade to this release, or
1256 to another of the releases coming out today.
1258 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1259 2018. If you need a release with long-term support, please upgrade with
1260 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1262 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1263 - Fix a denial of service bug where an attacker could use a
1264 malformed directory object to cause a Tor instance to pause while
1265 OpenSSL would try to read a passphrase from the terminal. (Tor
1266 instances run without a terminal, which is the case for most Tor
1267 packages, are not impacted.) Fixes bug 24246; bugfix on every
1268 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1269 Found by OSS-Fuzz as testcase 6360145429790720.
1270 - When checking for replays in the INTRODUCE1 cell data for a
1271 (legacy) onion service, correctly detect replays in the RSA-
1272 encrypted part of the cell. We were previously checking for
1273 replays on the entire cell, but those can be circumvented due to
1274 the malleability of Tor's legacy hybrid encryption. This fix helps
1275 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1276 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1279 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1280 - Fix a use-after-free error that could crash v2 Tor onion services
1281 when they failed to open circuits while expiring introduction
1282 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1283 also tracked as TROVE-2017-013 and CVE-2017-8823.
1285 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1286 - When running as a relay, make sure that we never build a path through
1287 ourselves, even in the case where we have somehow lost the version of
1288 our descriptor appearing in the consensus. Fixes part of bug 21534;
1289 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
1292 o Minor features (bridge, backport from 0.3.1.9):
1293 - Bridges now include notice in their descriptors that they are
1294 bridges, and notice of their distribution status, based on their
1295 publication settings. Implements ticket 18329. For more fine-
1296 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1299 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1300 - Add an IPv6 address for the "bastet" directory authority. Closes
1303 o Minor features (geoip):
1304 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1307 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1308 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1309 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1312 Changes in version 0.2.5.16 - 2017-12-01
1313 Tor 0.2.5.13 backports important security and stability bugfixes from
1314 later Tor releases. All Tor users should upgrade to this release, or
1315 to another of the releases coming out today.
1317 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1318 2018. If you need a release with long-term support, please upgrade to
1319 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1321 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1322 - Fix a denial of service bug where an attacker could use a
1323 malformed directory object to cause a Tor instance to pause while
1324 OpenSSL would try to read a passphrase from the terminal. (Tor
1325 instances run without a terminal, which is the case for most Tor
1326 packages, are not impacted.) Fixes bug 24246; bugfix on every
1327 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1328 Found by OSS-Fuzz as testcase 6360145429790720.
1329 - When checking for replays in the INTRODUCE1 cell data for a
1330 (legacy) onion service, correctly detect replays in the RSA-
1331 encrypted part of the cell. We were previously checking for
1332 replays on the entire cell, but those can be circumvented due to
1333 the malleability of Tor's legacy hybrid encryption. This fix helps
1334 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1335 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1338 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1339 - When running as a relay, make sure that we never build a path
1340 through ourselves, even in the case where we have somehow lost the
1341 version of our descriptor appearing in the consensus. Fixes part
1342 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1343 as TROVE-2017-012 and CVE-2017-8822.
1345 o Minor features (bridge, backport from 0.3.1.9):
1346 - Bridges now include notice in their descriptors that they are
1347 bridges, and notice of their distribution status, based on their
1348 publication settings. Implements ticket 18329. For more fine-
1349 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1352 o Minor features (geoip):
1353 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1357 Changes in version 0.3.2.5-alpha - 2017-11-22
1358 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
1359 fixes several stability and reliability bugs, including a fix for
1360 intermittent bootstrapping failures that some people have been seeing
1361 since the 0.3.0.x series.
1363 Please test this alpha out -- many of these fixes will soon be
1364 backported to stable Tor versions if no additional bugs are found
1367 o Major bugfixes (bootstrapping):
1368 - Fetch descriptors aggressively whenever we lack enough to build
1369 circuits, regardless of how many descriptors we are missing.
1370 Previously, we would delay launching the fetch when we had fewer
1371 than 15 missing descriptors, even if some of those descriptors
1372 were blocking circuits from building. Fixes bug 23985; bugfix on
1373 0.1.1.11-alpha. The effects of this bug became worse in
1374 0.3.0.3-alpha, when we began treating missing descriptors from our
1375 primary guards as a reason to delay circuits.
1376 - Don't try fetching microdescriptors from relays that have failed
1377 to deliver them in the past. Fixes bug 23817; bugfix
1380 o Minor features (directory authority):
1381 - Make the "Exit" flag assignment only depend on whether the exit
1382 policy allows connections to ports 80 and 443. Previously relays
1383 would get the Exit flag if they allowed connections to one of
1384 these ports and also port 6667. Resolves ticket 23637.
1386 o Minor features (geoip):
1387 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1390 o Minor features (linux seccomp2 sandbox):
1391 - Update the sandbox rules so that they should now work correctly
1392 with Glibc 2.26. Closes ticket 24315.
1394 o Minor features (logging):
1395 - Downgrade a pair of log messages that could occur when an exit's
1396 resolver gave us an unusual (but not forbidden) response. Closes
1398 - Improve the message we log when re-enabling circuit build timeouts
1399 after having received a consensus. Closes ticket 20963.
1401 o Minor bugfixes (compilation):
1402 - Fix a memory leak warning in one of the libevent-related
1403 configuration tests that could occur when manually specifying
1404 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
1405 Found and patched by Alex Xu.
1406 - When detecting OpenSSL on Windows from our configure script, make
1407 sure to try linking with the ws2_32 library. Fixes bug 23783;
1408 bugfix on 0.3.2.2-alpha.
1410 o Minor bugfixes (control port, linux seccomp2 sandbox):
1411 - Avoid a crash when attempting to use the seccomp2 sandbox together
1412 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1415 o Minor bugfixes (control port, onion services):
1416 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
1417 HS_DESC event when a service is not able to upload a descriptor.
1418 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
1420 o Minor bugfixes (directory cache):
1421 - Recover better from empty or corrupt files in the consensus cache
1422 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1423 - When a consensus diff calculation is only partially successful,
1424 only record the successful parts as having succeeded. Partial
1425 success can happen if (for example) one compression method fails
1426 but the others succeed. Previously we misrecorded all the
1427 calculations as having succeeded, which would later cause a
1428 nonfatal assertion failure. Fixes bug 24086; bugfix
1431 o Minor bugfixes (logging):
1432 - Only log once if we notice that KIST support is gone. Fixes bug
1433 24158; bugfix on 0.3.2.1-alpha.
1434 - Suppress a log notice when relay descriptors arrive. We already
1435 have a bootstrap progress for this so no need to log notice
1436 everytime tor receives relay descriptors. Microdescriptors behave
1437 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
1439 o Minor bugfixes (network layer):
1440 - When closing a connection via close_connection_immediately(), we
1441 mark it as "not blocked on bandwidth", to prevent later calls from
1442 trying to unblock it, and give it permission to read. This fixes a
1443 backtrace warning that can happen on relays under various
1444 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1446 o Minor bugfixes (onion services):
1447 - The introduction circuit was being timed out too quickly while
1448 waiting for the rendezvous circuit to complete. Keep the intro
1449 circuit around longer instead of timing out and reopening new ones
1450 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
1451 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1452 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1454 - Silence a warning about failed v3 onion descriptor uploads that
1455 can happen naturally under certain edge cases. Fixes part of bug
1456 23662; bugfix on 0.3.2.1-alpha.
1458 o Minor bugfixes (tests):
1459 - Fix a memory leak in one of the bridge-distribution test cases.
1460 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
1461 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
1462 to correctly handle cases where a caller gives it an RSA key of
1463 under 160 bits. (This is not actually a bug in Tor itself, but
1464 rather in our fuzzing code.) Fixes bug 24247; bugfix on
1465 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
1468 - Add notes in man page regarding OS support for the various
1469 scheduler types. Attempt to use less jargon in the scheduler
1470 section. Closes ticket 24254.
1473 Changes in version 0.3.2.4-alpha - 2017-11-08
1474 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
1475 It fixes several stability and reliability bugs, especially including
1476 a major reliability issue that has been plaguing fast exit relays in
1479 o Major bugfixes (exit relays, DNS):
1480 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1481 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1482 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1483 identifying and finding a workaround to this bug and to Moritz,
1484 Arthur Edelstein, and Roger for helping to track it down and
1487 o Major bugfixes (scheduler, channel):
1488 - Stop processing scheduled channels if they closed while flushing
1489 cells. This can happen if the write on the connection fails
1490 leading to the channel being closed while in the scheduler loop.
1491 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
1493 o Minor features (logging, scheduler):
1494 - Introduce a SCHED_BUG() function to log extra information about
1495 the scheduler state if we ever catch a bug in the scheduler.
1496 Closes ticket 23753.
1498 o Minor features (removed deprecations):
1499 - The ClientDNSRejectInternalAddresses flag can once again be set in
1500 non-testing Tor networks, so long as they do not use the default
1501 directory authorities. This change also removes the deprecation of
1502 this flag from 0.2.9.2-alpha. Closes ticket 21031.
1504 o Minor features (testing):
1505 - Our fuzzing tests now test the encrypted portions of v3 onion
1506 service descriptors. Implements more of 21509.
1508 o Minor bugfixes (directory client):
1509 - On failure to download directory information, delay retry attempts
1510 by a random amount based on the "decorrelated jitter" algorithm.
1511 Our previous delay algorithm tended to produce extra-long delays
1512 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
1514 o Minor bugfixes (IPv6, v3 single onion services):
1515 - Remove buggy code for IPv6-only v3 single onion services, and
1516 reject attempts to configure them. This release supports IPv4,
1517 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
1518 stack v3 single onion services. Fixes bug 23820; bugfix
1521 o Minor bugfixes (logging, relay):
1522 - Give only a protocol warning when the ed25519 key is not
1523 consistent between the descriptor and microdescriptor of a relay.
1524 This can happen, for instance, if the relay has been flagged
1525 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
1527 o Minor bugfixes (manpage, onion service):
1528 - Document that the HiddenServiceNumIntroductionPoints option is
1529 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
1530 bugfix on 0.3.2.1-alpha.
1532 o Minor bugfixes (memory leaks):
1533 - Fix a minor memory leak at exit in the KIST scheduler. This bug
1534 should have no user-visible impact. Fixes bug 23774; bugfix
1536 - Fix a memory leak when decrypting a badly formatted v3 onion
1537 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
1538 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
1540 o Minor bugfixes (onion services):
1541 - Cache some needed onion service client information instead of
1542 constantly computing it over and over again. Fixes bug 23623;
1543 bugfix on 0.3.2.1-alpha.
1544 - Properly retry HSv3 descriptor fetches when missing required
1545 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
1547 o Minor bugfixes (path selection):
1548 - When selecting relays by bandwidth, avoid a rounding error that
1549 could sometimes cause load to be imbalanced incorrectly.
1550 Previously, we would always round upwards; now, we round towards
1551 the nearest integer. This had the biggest effect when a relay's
1552 weight adjustments should have given it weight 0, but it got
1553 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1554 - When calculating the fraction of nodes that have descriptors, and
1555 all nodes in the network have zero bandwidths, count the number of
1556 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1557 - Actually log the total bandwidth in compute_weighted_bandwidths().
1558 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1560 o Minor bugfixes (relay, crash):
1561 - Avoid a crash when transitioning from client mode to bridge mode.
1562 Previously, we would launch the worker threads whenever our
1563 "public server" mode changed, but not when our "server" mode
1564 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1566 o Minor bugfixes (testing):
1567 - Fix a spurious fuzzing-only use of an uninitialized value. Found
1568 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
1569 - Test that IPv6-only clients can use microdescriptors when running
1570 "make test-network-all". Requires chutney master 61c28b9 or later.
1571 Closes ticket 24109.
1574 Changes in version 0.3.2.3-alpha - 2017-10-27
1575 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
1576 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
1577 directory authority, Bastet.
1579 o Directory authority changes:
1580 - Add "Bastet" as a ninth directory authority to the default list.
1581 Closes ticket 23910.
1582 - The directory authority "Longclaw" has changed its IP address.
1583 Closes ticket 23592.
1585 o Minor features (bridge):
1586 - Bridge relays can now set the BridgeDistribution config option to
1587 add a "bridge-distribution-request" line to their bridge
1588 descriptor, which tells BridgeDB how they'd like their bridge
1589 address to be given out. (Note that as of Oct 2017, BridgeDB does
1590 not yet implement this feature.) As a side benefit, this feature
1591 provides a way to distinguish bridge descriptors from non-bridge
1592 descriptors. Implements tickets 18329.
1594 o Minor features (client, entry guards):
1595 - Improve log messages when missing descriptors for primary guards.
1596 Resolves ticket 23670.
1598 o Minor features (geoip):
1599 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1602 o Minor bugfixes (bridge):
1603 - Overwrite the bridge address earlier in the process of retrieving
1604 its descriptor, to make sure we reach it on the configured
1605 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
1607 o Minor bugfixes (documentation):
1608 - Document better how to read gcov, and what our gcov postprocessing
1609 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
1611 o Minor bugfixes (entry guards):
1612 - Tor now updates its guard state when it reads a consensus
1613 regardless of whether it's missing descriptors. That makes tor use
1614 its primary guards to fetch descriptors in some edge cases where
1615 it would previously have used fallback directories. Fixes bug
1616 23862; bugfix on 0.3.0.1-alpha.
1618 o Minor bugfixes (hidden service client):
1619 - When handling multiple SOCKS request for the same .onion address,
1620 only fetch the service descriptor once.
1621 - When a descriptor fetch fails with a non-recoverable error, close
1622 all pending SOCKS requests for that .onion. Fixes bug 23653;
1623 bugfix on 0.3.2.1-alpha.
1625 o Minor bugfixes (hidden service):
1626 - Always regenerate missing hidden service public key files. Prior
1627 to this, if the public key was deleted from disk, it wouldn't get
1628 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
1630 - Make sure that we have a usable ed25519 key when the intro point
1631 relay supports ed25519 link authentication. Fixes bug 24002;
1632 bugfix on 0.3.2.1-alpha.
1634 o Minor bugfixes (hidden service, v2):
1635 - When reloading configured hidden services, copy all information
1636 from the old service object. Previously, some data was omitted,
1637 causing delays in descriptor upload, and other bugs. Fixes bug
1638 23790; bugfix on 0.2.1.9-alpha.
1640 o Minor bugfixes (memory safety, defensive programming):
1641 - Clear the target address when node_get_prim_orport() returns
1642 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1644 o Minor bugfixes (relay):
1645 - Avoid a BUG warning when receiving a dubious CREATE cell while an
1646 option transition is in progress. Fixes bug 23952; bugfix
1649 o Minor bugfixes (testing):
1650 - Adjust the GitLab CI configuration to more closely match that of
1651 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
1652 - Prevent scripts/test/coverage from attempting to move gcov output
1653 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
1654 - When running unit tests as root, skip a test that would fail
1655 because it expects a permissions error. This affects some
1656 continuous integration setups. Fixes bug 23758; bugfix
1658 - Stop unconditionally mirroring the tor repository in GitLab CI.
1659 This prevented developers from enabling GitLab CI on master. Fixes
1660 bug 23755; bugfix on 0.3.2.2-alpha.
1661 - Fix the hidden service v3 descriptor decoding fuzzing to use the
1662 latest decoding API correctly. Fixes bug 21509; bugfix
1665 o Minor bugfixes (warnings):
1666 - When we get an HTTP request on a SOCKS port, tell the user about
1667 the new HTTPTunnelPort option. Previously, we would give a "Tor is
1668 not an HTTP Proxy" message, which stopped being true when
1669 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
1673 Changes in version 0.2.5.15 - 2017-10-25
1674 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
1675 series. It also adds a new directory authority, Bastet.
1677 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1678 2018. If you need a release with long-term support, please upgrade to
1679 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1681 o Directory authority changes:
1682 - Add "Bastet" as a ninth directory authority to the default list.
1683 Closes ticket 23910.
1684 - The directory authority "Longclaw" has changed its IP address.
1685 Closes ticket 23592.
1687 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1688 - Avoid an assertion failure bug affecting our implementation of
1689 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1690 handling of "0xx" differs from what we had expected. Fixes bug
1691 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1693 o Minor features (geoip):
1694 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1697 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1698 - Fix a memset() off the end of an array when packing cells. This
1699 bug should be harmless in practice, since the corrupted bytes are
1700 still in the same structure, and are always padding bytes,
1701 ignored, or immediately overwritten, depending on compiler
1702 behavior. Nevertheless, because the memset()'s purpose is to make
1703 sure that any other cell-handling bugs can't expose bytes to the
1704 network, we need to fix it. Fixes bug 22737; bugfix on
1705 0.2.4.11-alpha. Fixes CID 1401591.
1707 o Build features (backport from 0.3.1.5-alpha):
1708 - Tor's repository now includes a Travis Continuous Integration (CI)
1709 configuration file (.travis.yml). This is meant to help new
1710 developers and contributors who fork Tor to a Github repository be
1711 better able to test their changes, and understand what we expect
1712 to pass. To use this new build feature, you must fork Tor to your
1713 Github account, then go into the "Integrations" menu in the
1714 repository settings for your fork and enable Travis, then push
1715 your changes. Closes ticket 22636.
1718 Changes in version 0.2.8.16 - 2017-10-25
1719 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
1720 series, including a bugfix for a crash issue that had affected relays
1721 under memory pressure. It also adds a new directory authority, Bastet.
1723 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1724 2018. If you need a release with long-term support, please stick with
1725 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1727 o Directory authority changes:
1728 - Add "Bastet" as a ninth directory authority to the default list.
1729 Closes ticket 23910.
1730 - The directory authority "Longclaw" has changed its IP address.
1731 Closes ticket 23592.
1733 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1734 - Fix a timing-based assertion failure that could occur when the
1735 circuit out-of-memory handler freed a connection's output buffer.
1736 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1738 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1739 - Remove longclaw's IPv6 address, as it will soon change. Authority
1740 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1741 3/8 directory authorities with IPv6 addresses, but there are also
1742 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1744 o Minor features (geoip):
1745 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1749 Changes in version 0.2.9.13 - 2017-10-25
1750 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
1751 series, including a bugfix for a crash issue that had affected relays
1752 under memory pressure. It also adds a new directory authority, Bastet.
1754 o Directory authority changes:
1755 - Add "Bastet" as a ninth directory authority to the default list.
1756 Closes ticket 23910.
1757 - The directory authority "Longclaw" has changed its IP address.
1758 Closes ticket 23592.
1760 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1761 - Fix a timing-based assertion failure that could occur when the
1762 circuit out-of-memory handler freed a connection's output buffer.
1763 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1765 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1766 - Remove longclaw's IPv6 address, as it will soon change. Authority
1767 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1768 3/8 directory authorities with IPv6 addresses, but there are also
1769 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1771 o Minor features (geoip):
1772 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1775 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1776 - When a directory authority rejects a descriptor or extrainfo with
1777 a given digest, mark that digest as undownloadable, so that we do
1778 not attempt to download it again over and over. We previously
1779 tried to avoid downloading such descriptors by other means, but we
1780 didn't notice if we accidentally downloaded one anyway. This
1781 behavior became problematic in 0.2.7.2-alpha, when authorities
1782 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1785 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1786 - Clear the address when node_get_prim_orport() returns early.
1787 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1789 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1790 - When running as a Windows service, set the ID of the main thread
1791 correctly. Failure to do so made us fail to send log messages to
1792 the controller in 0.2.1.16-rc, slowed down controller event
1793 delivery in 0.2.7.3-rc and later, and crash with an assertion
1794 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1795 Patch and diagnosis from "Vort".
1798 Changes in version 0.3.0.12 - 2017-10-25
1799 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
1800 series, including a bugfix for a crash issue that had affected relays
1801 under memory pressure. It also adds a new directory authority, Bastet.
1803 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1804 2018. If you need a release with long-term support, please stick with
1805 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1807 o Directory authority changes:
1808 - Add "Bastet" as a ninth directory authority to the default list.
1809 Closes ticket 23910.
1810 - The directory authority "Longclaw" has changed its IP address.
1811 Closes ticket 23592.
1813 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1814 - Fix a timing-based assertion failure that could occur when the
1815 circuit out-of-memory handler freed a connection's output buffer.
1816 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1818 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1819 - Remove longclaw's IPv6 address, as it will soon change. Authority
1820 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1821 3/8 directory authorities with IPv6 addresses, but there are also
1822 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1824 o Minor features (geoip):
1825 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1828 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1829 - When a directory authority rejects a descriptor or extrainfo with
1830 a given digest, mark that digest as undownloadable, so that we do
1831 not attempt to download it again over and over. We previously
1832 tried to avoid downloading such descriptors by other means, but we
1833 didn't notice if we accidentally downloaded one anyway. This
1834 behavior became problematic in 0.2.7.2-alpha, when authorities
1835 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1838 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1839 - Avoid a possible double close of a circuit by the intro point on
1840 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1841 bugfix on 0.3.0.1-alpha.
1843 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1844 - Clear the address when node_get_prim_orport() returns early.
1845 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1847 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1848 - When running as a Windows service, set the ID of the main thread
1849 correctly. Failure to do so made us fail to send log messages to
1850 the controller in 0.2.1.16-rc, slowed down controller event
1851 delivery in 0.2.7.3-rc and later, and crash with an assertion
1852 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1853 Patch and diagnosis from "Vort".
1856 Changes in version 0.3.1.8 - 2017-10-25
1857 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
1858 It includes several bugfixes, including a bugfix for a crash issue
1859 that had affected relays under memory pressure. It also adds
1860 a new directory authority, Bastet.
1862 o Directory authority changes:
1863 - Add "Bastet" as a ninth directory authority to the default list.
1864 Closes ticket 23910.
1865 - The directory authority "Longclaw" has changed its IP address.
1866 Closes ticket 23592.
1868 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1869 - Fix a timing-based assertion failure that could occur when the
1870 circuit out-of-memory handler freed a connection's output buffer.
1871 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1873 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1874 - Remove longclaw's IPv6 address, as it will soon change. Authority
1875 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1876 3/8 directory authorities with IPv6 addresses, but there are also
1877 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1879 o Minor features (geoip):
1880 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1883 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
1884 - Fix a compilation warning when building with zstd support on
1885 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1886 and fixed by Andreas Stieger.
1888 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
1889 - Handle a pathological case when decompressing Zstandard data when
1890 the output buffer size is zero. Fixes bug 23551; bugfix
1893 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
1894 - Remove the length limit on HTTP status lines that authorities can
1895 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
1897 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1898 - Avoid a possible double close of a circuit by the intro point on
1899 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1900 bugfix on 0.3.0.1-alpha.
1902 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1903 - Clear the address when node_get_prim_orport() returns early.
1904 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1906 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
1907 - Fix additional channelpadding unit test failures by using mocked
1908 time instead of actual time for all tests. Fixes bug 23608; bugfix
1912 Changes in version 0.3.2.2-alpha - 2017-09-29
1913 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
1914 release fixes several minor bugs in the new scheduler and next-
1915 generation onion services; both features were newly added in the 0.3.2
1916 series. Other fixes in this alpha include several fixes for non-fatal
1917 tracebacks which would appear in logs.
1919 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
1920 alpha does not contain any substantial new features. Minor features
1921 include better testing and logging.
1923 The following comprises the complete list of changes included
1924 in tor-0.3.2.2-alpha:
1926 o Major bugfixes (relay, crash, assertion failure):
1927 - Fix a timing-based assertion failure that could occur when the
1928 circuit out-of-memory handler freed a connection's output buffer.
1929 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1931 o Major bugfixes (scheduler):
1932 - If a channel is put into the scheduler's pending list, then it
1933 starts closing, and then if the scheduler runs before it finishes
1934 closing, the scheduler will get stuck trying to flush its cells
1935 while the lower layers refuse to cooperate. Fix that race
1936 condition by giving the scheduler an escape method. Fixes bug
1937 23676; bugfix on 0.3.2.1-alpha.
1939 o Minor features (build, compilation):
1940 - The "check-changes" feature is now part of the "make check" tests;
1941 we'll use it to try to prevent misformed changes files from
1942 accumulating. Closes ticket 23564.
1943 - Tor builds should now fail if there are any mismatches between the
1944 C type representing a configuration variable and the C type the
1945 data-driven parser uses to store a value there. Previously, we
1946 needed to check these by hand, which sometimes led to mistakes.
1947 Closes ticket 23643.
1949 o Minor features (directory authorities):
1950 - Remove longclaw's IPv6 address, as it will soon change. Authority
1951 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1952 3/8 directory authorities with IPv6 addresses, but there are also
1953 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1955 o Minor features (hidden service, circuit, logging):
1956 - Improve logging of many callsite in the circuit subsystem to print
1957 the circuit identifier(s).
1958 - Log when we cleanup an intro point from a service so we know when
1959 and for what reason it happened. Closes ticket 23604.
1961 o Minor features (logging):
1962 - Log more circuit information whenever we are about to try to
1963 package a relay cell on a circuit with a nonexistent n_chan.
1964 Attempt to diagnose ticket 8185.
1965 - Improve info-level log identification of particular circuits, to
1966 help with debugging. Closes ticket 23645.
1968 o Minor features (relay):
1969 - When choosing which circuits can be expired as unused, consider
1970 circuits from clients even if those clients used regular CREATE
1971 cells to make them; and do not consider circuits from relays even
1972 if they were made with CREATE_FAST. Part of ticket 22805.
1974 o Minor features (robustness):
1975 - Change several fatal assertions when flushing buffers into non-
1976 fatal assertions, to prevent any recurrence of 23690.
1978 o Minor features (spec conformance, bridge, diagnostic):
1979 - When handling the USERADDR command on an ExtOrPort, warn when the
1980 transports provides a USERADDR with no port. In a future version,
1981 USERADDR commands of this format may be rejected. Detects problems
1982 related to ticket 23080.
1984 o Minor features (testing):
1985 - Add a unit test to make sure that our own generated platform
1986 string will be accepted by directory authorities. Closes
1989 o Minor bugfixes (bootstrapping):
1990 - When warning about state file clock skew, report the correct
1991 direction for the detected skew. Fixes bug 23606; bugfix
1993 - Avoid an assertion failure when logging a state file clock skew
1994 very early in bootstrapping. Fixes bug 23607; bugfix
1997 o Minor bugfixes (build, compilation):
1998 - Fix a compilation warning when building with zstd support on
1999 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2000 and fixed by Andreas Stieger.
2001 - When searching for OpenSSL, don't accept any OpenSSL library that
2002 lacks TLSv1_1_method(): Tor doesn't build with those versions.
2003 Additionally, look in /usr/local/opt/openssl, if it's present.
2004 These changes together repair the default build on OSX systems
2005 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
2007 o Minor bugfixes (compression):
2008 - Handle a pathological case when decompressing Zstandard data when
2009 the output buffer size is zero. Fixes bug 23551; bugfix
2012 o Minor bugfixes (documentation):
2013 - Fix manpage to not refer to the obsolete (and misspelled)
2014 UseEntryGuardsAsDirectoryGuards parameter in the description of
2015 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
2017 o Minor bugfixes (hidden service v3):
2018 - Don't log an assertion failure when we can't find the right
2019 information to extend to an introduction point. In rare cases,
2020 this could happen, causing a warning, even though tor would
2021 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
2022 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
2023 much bigger so the rendezvous point can't distinguish which hidden
2024 service protocol is being used. Fixes bug 23420; bugfix
2027 o Minor bugfixes (hidden service, relay):
2028 - Avoid a possible double close of a circuit by the intro point on
2029 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2030 bugfix on 0.3.0.1-alpha.
2032 o Minor bugfixes (logging, relay shutdown, annoyance):
2033 - When a circuit is marked for close, do not attempt to package any
2034 cells for channels on that circuit. Previously, we would detect
2035 this condition lower in the call stack, when we noticed that the
2036 circuit had no attached channel, and log an annoying message.
2037 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2039 o Minor bugfixes (scheduler):
2040 - When switching schedulers due to a consensus change, we didn't
2041 give the new scheduler a chance to react to the consensus. Fix
2042 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
2043 - Make the KISTSchedRunInterval option a non negative value. With
2044 this, the way to disable KIST through the consensus is to set it
2045 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
2046 - Only notice log the selected scheduler when we switch scheduler
2047 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
2048 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
2049 by a different tv_usec data type. Fixes bug 23575; bugfix
2051 - Make a hard exit if tor is unable to pick a scheduler which can
2052 happen if the user specifies a scheduler type that is not
2053 supported and not other types in Schedulers. Fixes bug 23581;
2054 bugfix on 0.3.2.1-alpha.
2055 - Properly initialize the scheduler last run time counter so it is
2056 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
2058 o Minor bugfixes (testing):
2059 - Capture and detect several "Result does not fit" warnings in unit
2060 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
2062 - Fix additional channelpadding unit test failures by using mocked
2063 time instead of actual time for all tests. Fixes bug 23608; bugfix
2065 - The removal of some old scheduler options caused some tests to
2066 fail on BSD systems. Assume current behavior is correct and make
2067 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
2069 o Code simplification and refactoring:
2070 - Remove various ways of testing circuits and connections for
2071 "clientness"; instead, favor channel_is_client(). Part of
2074 o Deprecated features:
2075 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
2076 now deprecated; they do not apply to relays, and they have had no
2077 effect on clients since 0.2.8.x. Closes ticket 19704.
2080 - HiddenServiceVersion man page entry wasn't mentioning the now
2081 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
2082 - Clarify that the Address option is entirely about setting an
2083 advertised IPv4 address. Closes ticket 18891.
2084 - Clarify the manpage's use of the term "address" to clarify what
2085 kind of address is intended. Closes ticket 21405.
2086 - Document that onion service subdomains are allowed, and ignored.
2087 Closes ticket 18736.
2090 Changes in version 0.3.2.1-alpha - 2017-09-18
2091 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
2092 includes support for our next-generation ("v3") onion service
2093 protocol, and adds a new circuit scheduler for more responsive
2094 forwarding decisions from relays. There are also numerous other small
2095 features and bugfixes here.
2097 Below are the changes since Tor 0.3.1.7.
2099 o Major feature (scheduler, channel):
2100 - Tor now uses new schedulers to decide which circuits should
2101 deliver cells first, in order to improve congestion at relays. The
2102 first type is called "KIST" ("Kernel Informed Socket Transport"),
2103 and is only available on Linux-like systems: it uses feedback from
2104 the kernel to prevent the kernel's TCP buffers from growing too
2105 full. The second new scheduler type is called "KISTLite": it
2106 behaves the same as KIST, but runs on systems without kernel
2107 support for inspecting TCP implementation details. The old
2108 scheduler is still available, under the name "Vanilla". To change
2109 the default scheduler preference order, use the new "Schedulers"
2110 option. (The default preference order is "KIST,KISTLite,Vanilla".)
2112 Matt Traudt implemented KIST, based on research by Rob Jansen,
2113 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
2114 more information, see the design paper at
2115 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
2116 followup implementation paper at https://arxiv.org/abs/1709.01044.
2117 Closes ticket 12541.
2119 o Major features (next-generation onion services):
2120 - Tor now supports the next-generation onion services protocol for
2121 clients and services! As part of this release, the core of
2122 proposal 224 has been implemented and is available for
2123 experimentation and testing by our users. This newer version of
2124 onion services ("v3") features many improvements over the legacy
2127 a) Better crypto (replaced SHA1/DH/RSA1024
2128 with SHA3/ed25519/curve25519)
2130 b) Improved directory protocol, leaking much less information to
2133 c) Improved directory protocol, with smaller surface for
2136 d) Better onion address security against impersonation.
2138 e) More extensible introduction/rendezvous protocol.
2140 f) A cleaner and more modular codebase.
2142 You can identify a next-generation onion address by its length:
2143 they are 56 characters long, as in
2144 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
2146 In the future, we will release more options and features for v3
2147 onion services, but we first need a testing period, so that the
2148 current codebase matures and becomes more robust. Planned features
2149 include: offline keys, advanced client authorization, improved
2150 guard algorithms, and statistics. For full details, see
2153 Legacy ("v2") onion services will still work for the foreseeable
2154 future, and will remain the default until this new codebase gets
2155 tested and hardened. Service operators who want to experiment with
2156 the new system can use the 'HiddenServiceVersion 3' torrc
2157 directive along with the regular onion service configuration
2158 options. We will publish a blog post about this new feature
2161 o Major bugfixes (usability, control port):
2162 - Report trusted clock skew indications as bootstrap errors, so
2163 controllers can more easily alert users when their clocks are
2164 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
2166 o Minor features (bug detection):
2167 - Log a warning message with a stack trace for any attempt to call
2168 get_options() during option validation. This pattern has caused
2169 subtle bugs in the past. Closes ticket 22281.
2171 o Minor features (client):
2172 - You can now use Tor as a tunneled HTTP proxy: use the new
2173 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
2174 requests. Closes ticket 22407.
2175 - Add an extra check to make sure that we always use the newer guard
2176 selection code for picking our guards. Closes ticket 22779.
2177 - When downloading (micro)descriptors, don't split the list into
2178 multiple requests unless we want at least 32 descriptors.
2179 Previously, we split at 4, not 32, which led to significant
2180 overhead in HTTP request size and degradation in compression
2181 performance. Closes ticket 23220.
2183 o Minor features (command line):
2184 - Add a new commandline option, --key-expiration, which prints when
2185 the current signing key is going to expire. Implements ticket
2186 17639; patch by Isis Lovecruft.
2188 o Minor features (control port):
2189 - If an application tries to use the control port as an HTTP proxy,
2190 respond with a meaningful "This is the Tor control port" message,
2191 and log the event. Closes ticket 1667. Patch from Ravi
2193 - Provide better error message for GETINFO desc/(id|name) when not
2194 fetching router descriptors. Closes ticket 5847. Patch by
2196 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
2197 whether Tor will try to download router descriptors and
2198 microdescriptors respectively. Closes ticket 22684.
2199 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
2200 so controllers can tell whether the geoip databases are loaded.
2201 Closes ticket 23237.
2202 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
2203 events. Closes ticket 19254. Patch by "DonnchaC".
2205 o Minor features (development support):
2206 - Developers can now generate a call-graph for Tor using the
2207 "calltool" python program, which post-processes object dumps. It
2208 should work okay on many Linux and OSX platforms, and might work
2209 elsewhere too. To run it, install calltool from
2210 https://gitweb.torproject.org/user/nickm/calltool.git and run
2211 "make callgraph". Closes ticket 19307.
2213 o Minor features (ed25519):
2214 - Add validation function to checks for torsion components in
2215 ed25519 public keys, used by prop224 client-side code. Closes
2216 ticket 22006. Math help by Ian Goldberg.
2218 o Minor features (exit relay, DNS):
2219 - Improve the clarity and safety of the log message from evdns when
2220 receiving an apparently spoofed DNS reply. Closes ticket 3056.
2222 o Minor features (integration, hardening):
2223 - Add a new NoExec option to prevent Tor from running other
2224 programs. When this option is set to 1, Tor will never try to run
2225 another program, regardless of the settings of
2226 PortForwardingHelper, ClientTransportPlugin, or
2227 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
2228 without restarting Tor. Closes ticket 22976.
2230 o Minor features (logging):
2231 - Improve the warning message for specifying a relay by nickname.
2232 The previous message implied that nickname registration was still
2233 part of the Tor network design, which it isn't. Closes
2235 - If the sandbox filter fails to load, suggest to the user that
2236 their kernel might not support seccomp2. Closes ticket 23090.
2238 o Minor features (portability):
2239 - Check at configure time whether uint8_t is the same type as
2240 unsigned char. Lots of existing code already makes this
2241 assumption, and there could be strict aliasing issues if the
2242 assumption is violated. Closes ticket 22410.
2244 o Minor features (relay, configuration):
2245 - Reject attempts to use relative file paths when RunAsDaemon is
2246 set. Previously, Tor would accept these, but the directory-
2247 changing step of RunAsDaemon would give strange and/or confusing
2248 results. Closes ticket 22731.
2250 o Minor features (startup, safety):
2251 - When configured to write a PID file, Tor now exits if it is unable
2252 to do so. Previously, it would warn and continue. Closes
2255 o Minor features (static analysis):
2256 - The BUG() macro has been changed slightly so that Coverity no
2257 longer complains about dead code if the bug is impossible. Closes
2260 o Minor features (testing):
2261 - The default chutney network tests now include tests for the v3
2262 hidden service design. Make sure you have the latest version of
2263 chutney if you want to run these. Closes ticket 22437.
2264 - Add a unit test to verify that we can parse a hardcoded v2 hidden
2265 service descriptor. Closes ticket 15554.
2267 o Minor bugfixes (certificate handling):
2268 - Fix a time handling bug in Tor certificates set to expire after
2269 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
2270 Coverity as CID 1415728.
2272 o Minor bugfixes (client, usability):
2273 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
2274 SOCKS4a requests that contain IP address strings, even when
2275 SafeSocks in enabled, as this prevents user from connecting to
2276 known IP addresses without relying on DNS for resolving. SafeSocks
2277 still rejects SOCKS connections that connect to IP addresses when
2278 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
2279 bugfix on Tor 0.2.6.2-alpha.
2281 o Minor bugfixes (code correctness):
2282 - Call htons() in extend_cell_format() for encoding a 16-bit value.
2283 Previously we used ntohs(), which happens to behave the same on
2284 all the platforms we support, but which isn't really correct.
2285 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
2286 - For defense-in-depth, make the controller's write_escaped_data()
2287 function robust to extremely long inputs. Fixes bug 19281; bugfix
2288 on 0.1.1.1-alpha. Reported by Guido Vranken.
2290 o Minor bugfixes (compilation):
2291 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
2292 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2294 o Minor bugfixes (consensus expiry):
2295 - Check for adequate directory information correctly. Previously, Tor
2296 would reconsider whether it had sufficient directory information
2297 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
2299 o Minor bugfixes (directory protocol):
2300 - Directory servers now include a "Date:" http header for response
2301 codes other than 200. Clients starting with a skewed clock and a
2302 recent consensus were getting "304 Not modified" responses from
2303 directory authorities, so without the Date header, the client
2304 would never hear about a wrong clock. Fixes bug 23499; bugfix
2306 - Make clients wait for 6 seconds before trying to download a
2307 consensus from an authority. Fixes bug 17750; bugfix
2310 o Minor bugfixes (DoS-resistance):
2311 - If future code asks if there are any running bridges, without
2312 checking if bridges are enabled, log a BUG warning rather than
2313 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
2315 o Minor bugfixes (format strictness):
2316 - Restrict several data formats to decimal. Previously, the
2317 BuildTimeHistogram entries in the state file, the "bw=" entries in
2318 the bandwidth authority file, and the process IDs passed to the
2319 __OwningControllerProcess option could all be specified in hex or
2320 octal as well as in decimal. This was not an intentional feature.
2321 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
2324 o Minor bugfixes (heartbeat):
2325 - If we fail to write a heartbeat message, schedule a retry for the
2326 minimum heartbeat interval number of seconds in the future. Fixes
2327 bug 19476; bugfix on 0.2.3.1-alpha.
2329 o Minor bugfixes (linux seccomp2 sandbox, logging):
2330 - Fix some messages on unexpected errors from the seccomp2 library.
2331 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
2333 o Minor bugfixes (logging):
2334 - Remove duplicate log messages regarding opening non-local
2335 SocksPorts upon parsing config and opening listeners at startup.
2336 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
2337 - Use a more comprehensible log message when telling the user
2338 they've excluded every running exit node. Fixes bug 7890; bugfix
2340 - When logging the number of descriptors we intend to download per
2341 directory request, do not log a number higher than then the number
2342 of descriptors we're fetching in total. Fixes bug 19648; bugfix
2344 - When warning about a directory owned by the wrong user, log the
2345 actual name of the user owning the directory. Previously, we'd log
2346 the name of the process owner twice. Fixes bug 23487; bugfix
2348 - The tor specification says hop counts are 1-based, so fix two log
2349 messages that mistakenly logged 0-based hop counts. Fixes bug
2350 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
2351 Credit to Xiaofan Li for reporting this issue.
2353 o Minor bugfixes (portability):
2354 - Stop using the PATH_MAX variable, which is not defined on GNU
2355 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
2357 o Minor bugfixes (relay):
2358 - When uploading our descriptor for the first time after startup,
2359 report the reason for uploading as "Tor just started" rather than
2360 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
2361 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2362 relays, to prevent spurious address resolutions and descriptor
2363 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2364 bugfix on in 0.2.8.1-alpha.
2366 o Minor bugfixes (tests):
2367 - Fix a broken unit test for the OutboundAddress option: the parsing
2368 function was never returning an error on failure. Fixes bug 23366;
2369 bugfix on 0.3.0.3-alpha.
2370 - Fix a signed-integer overflow in the unit tests for
2371 dir/download_status_random_backoff, which was untriggered until we
2372 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
2374 o Minor bugfixes (usability, control port):
2375 - Stop making an unnecessary routerlist check in NETINFO clock skew
2376 detection; this was preventing clients from reporting NETINFO clock
2377 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
2379 o Code simplification and refactoring:
2380 - Extract the code for handling newly-open channels into a separate
2381 function from the general code to handle channel state
2382 transitions. This change simplifies our callgraph, reducing the
2383 size of the largest strongly connected component by roughly a
2384 factor of two. Closes ticket 22608.
2385 - Remove dead code for largely unused statistics on the number of
2386 times we've attempted various public key operations. Fixes bug
2387 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
2388 - Remove several now-obsolete functions for asking about old
2389 variants directory authority status. Closes ticket 22311; patch
2391 - Remove some of the code that once supported "Named" and "Unnamed"
2392 routers. Authorities no longer vote for these flags. Closes
2394 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
2395 and old hidden services, to indicate that they aren't suitable for
2396 new protocols or formats. Closes ticket 23026.
2397 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
2398 22521. Patch from Neel Chauhan.
2399 - Split the enormous circuit_send_next_onion_skin() function into
2400 multiple subfunctions. Closes ticket 22804.
2401 - Split the portions of the buffer.c module that handle particular
2402 protocols into separate modules. Part of ticket 23149.
2403 - Use our test macros more consistently, to produce more useful
2404 error messages when our unit tests fail. Add coccinelle patches to
2405 allow us to re-check for test macro uses. Closes ticket 22497.
2407 o Deprecated features:
2408 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
2409 only applies to direct unencrypted HTTP connections to your
2410 directory server, which your Tor probably isn't using. Closes
2414 - Clarify in the manual that "Sandbox 1" is only supported on Linux
2415 kernels. Closes ticket 22677.
2416 - Document all values of PublishServerDescriptor in the manpage.
2417 Closes ticket 15645.
2418 - Improve the documentation for the directory port part of the
2419 DirAuthority line. Closes ticket 20152.
2420 - Restore documentation for the authorities' "approved-routers"
2421 file. Closes ticket 21148.
2424 - The AllowDotExit option has been removed as unsafe. It has been
2425 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
2426 - The ClientDNSRejectInternalAddresses flag can no longer be set on
2427 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
2428 Closes ticket 21031.
2429 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
2430 nobody was using it any longer. Closes ticket 22377.
2433 Changes in version 0.2.8.15 - 2017-09-18
2434 Tor 0.2.8.15 backports a collection of bugfixes from later
2437 Most significantly, it includes a fix for TROVE-2017-008, a
2438 security bug that affects hidden services running with the
2439 SafeLogging option disabled. For more information, see
2440 https://trac.torproject.org/projects/tor/ticket/23490
2442 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
2443 2018. We suggest that you upgrade to the latest stable release if
2444 possible. If you can't, we recommend that you upgrade at least to
2445 0.2.9, which will be supported until 2020.
2447 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2448 - Avoid an assertion failure bug affecting our implementation of
2449 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2450 handling of "0xx" differs from what we had expected. Fixes bug
2451 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2454 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2457 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2458 - Backport a fix for an "unused variable" warning that appeared
2459 in some versions of mingw. Fixes bug 22838; bugfix on
2462 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2463 - Fix a memset() off the end of an array when packing cells. This
2464 bug should be harmless in practice, since the corrupted bytes are
2465 still in the same structure, and are always padding bytes,
2466 ignored, or immediately overwritten, depending on compiler
2467 behavior. Nevertheless, because the memset()'s purpose is to make
2468 sure that any other cell-handling bugs can't expose bytes to the
2469 network, we need to fix it. Fixes bug 22737; bugfix on
2470 0.2.4.11-alpha. Fixes CID 1401591.
2472 o Build features (backport from 0.3.1.5-alpha):
2473 - Tor's repository now includes a Travis Continuous Integration (CI)
2474 configuration file (.travis.yml). This is meant to help new
2475 developers and contributors who fork Tor to a Github repository be
2476 better able to test their changes, and understand what we expect
2477 to pass. To use this new build feature, you must fork Tor to your
2478 Github account, then go into the "Integrations" menu in the
2479 repository settings for your fork and enable Travis, then push
2480 your changes. Closes ticket 22636.
2483 Changes in version 0.2.9.12 - 2017-09-18
2484 Tor 0.2.9.12 backports a collection of bugfixes from later
2487 Most significantly, it includes a fix for TROVE-2017-008, a
2488 security bug that affects hidden services running with the
2489 SafeLogging option disabled. For more information, see
2490 https://trac.torproject.org/projects/tor/ticket/23490
2492 o Major features (security, backport from 0.3.0.2-alpha):
2493 - Change the algorithm used to decide DNS TTLs on client and server
2494 side, to better resist DNS-based correlation attacks like the
2495 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2496 Feamster. Now relays only return one of two possible DNS TTL
2497 values, and clients are willing to believe DNS TTL values up to 3
2498 hours long. Closes ticket 19769.
2500 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
2501 - Fix a rare crash when sending a begin cell on a circuit whose
2502 linked directory connection had already been closed. Fixes bug
2503 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
2505 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
2506 - Fix a bug that prevented exit nodes from caching DNS records for
2507 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2509 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2510 - Fix a typo that had prevented TPROXY-based transparent proxying
2511 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2512 Patch from "d4fq0fQAgoJ".
2514 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2515 - Avoid an assertion failure bug affecting our implementation of
2516 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2517 handling of "0xx" differs from what we had expected. Fixes bug
2518 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2520 o Minor features (code style, backport from 0.3.1.3-alpha):
2521 - Add "Falls through" comments to our codebase, in order to silence
2522 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2523 Stieger. Closes ticket 22446.
2525 o Minor features (geoip):
2526 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2529 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
2530 - Roll over monthly accounting at the configured hour and minute,
2531 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2532 Found by Andrey Karpov with PVS-Studio.
2534 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
2535 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2536 bugfix on 0.2.8.1-alpha.
2537 - Fix warnings when building with libscrypt and openssl scrypt support
2538 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2539 - When building with certain versions the mingw C header files, avoid
2540 float-conversion warnings when calling the C functions isfinite(),
2541 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
2543 o Minor bugfixes (compilation, backport from 0.3.1.7):
2544 - Avoid compiler warnings in the unit tests for running tor_sscanf()
2545 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2547 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2548 - Backport a fix for an "unused variable" warning that appeared
2549 in some versions of mingw. Fixes bug 22838; bugfix on
2552 o Minor bugfixes (controller, backport from 0.3.1.7):
2553 - Do not crash when receiving a HSPOST command with an empty body.
2554 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2555 - Do not crash when receiving a POSTDESCRIPTOR command with an
2556 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2558 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2559 - Avoid Coverity build warnings related to our BUG() macro. By
2560 default, Coverity treats BUG() as the Linux kernel does: an
2561 instant abort(). We need to override that so our BUG() macro
2562 doesn't prevent Coverity from analyzing functions that use it.
2563 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2565 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2566 - Fix a memset() off the end of an array when packing cells. This
2567 bug should be harmless in practice, since the corrupted bytes are
2568 still in the same structure, and are always padding bytes,
2569 ignored, or immediately overwritten, depending on compiler
2570 behavior. Nevertheless, because the memset()'s purpose is to make
2571 sure that any other cell-handling bugs can't expose bytes to the
2572 network, we need to fix it. Fixes bug 22737; bugfix on
2573 0.2.4.11-alpha. Fixes CID 1401591.
2575 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2576 - When setting the maximum number of connections allowed by the OS,
2577 always allow some extra file descriptors for other files. Fixes
2578 bug 22797; bugfix on 0.2.0.10-alpha.
2580 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2581 - Avoid a sandbox failure when trying to re-bind to a socket and
2582 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2584 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2585 - Permit the fchmod system call, to avoid crashing on startup when
2586 starting with the seccomp2 sandbox and an unexpected set of
2587 permissions on the data directory or its contents. Fixes bug
2588 22516; bugfix on 0.2.5.4-alpha.
2590 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
2591 - Avoid a double-marked-circuit warning that could happen when we
2592 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
2595 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2596 - Reject version numbers with non-numeric prefixes (such as +, -, or
2597 whitespace). Disallowing whitespace prevents differential version
2598 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2599 and part of 21508; bugfix on 0.0.8pre1.
2601 o Build features (backport from 0.3.1.5-alpha):
2602 - Tor's repository now includes a Travis Continuous Integration (CI)
2603 configuration file (.travis.yml). This is meant to help new
2604 developers and contributors who fork Tor to a Github repository be
2605 better able to test their changes, and understand what we expect
2606 to pass. To use this new build feature, you must fork Tor to your
2607 Github account, then go into the "Integrations" menu in the
2608 repository settings for your fork and enable Travis, then push
2609 your changes. Closes ticket 22636.
2612 Changes in version 0.3.0.11 - 2017-09-18
2613 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
2616 Most significantly, it includes a fix for TROVE-2017-008, a
2617 security bug that affects hidden services running with the
2618 SafeLogging option disabled. For more information, see
2619 https://trac.torproject.org/projects/tor/ticket/23490
2621 o Minor features (code style, backport from 0.3.1.7):
2622 - Add "Falls through" comments to our codebase, in order to silence
2623 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2624 Stieger. Closes ticket 22446.
2627 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2630 o Minor bugfixes (compilation, backport from 0.3.1.7):
2631 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2632 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2634 o Minor bugfixes (controller, backport from 0.3.1.7):
2635 - Do not crash when receiving a HSPOST command with an empty body.
2636 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2637 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2638 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2640 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2641 - When setting the maximum number of connections allowed by the OS,
2642 always allow some extra file descriptors for other files. Fixes
2643 bug 22797; bugfix on 0.2.0.10-alpha.
2645 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
2646 - Remove a forgotten debugging message when an introduction point
2647 successfully establishes a hidden service prop224 circuit with
2649 - Change three other log_warn() for an introduction point to
2650 protocol warnings, because they can be failure from the network
2651 and are not relevant to the operator. Fixes bug 23078; bugfix on
2652 0.3.0.1-alpha and 0.3.0.2-alpha.
2655 Changes in version 0.3.1.7 - 2017-09-18
2656 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
2658 With the 0.3.1 series, Tor now serves and downloads directory
2659 information in more compact formats, to save on bandwidth overhead. It
2660 also contains a new padding system to resist netflow-based traffic
2661 analysis, and experimental support for building parts of Tor in Rust
2662 (though no parts of Tor are in Rust yet). There are also numerous
2663 small features, bugfixes on earlier release series, and groundwork for
2664 the hidden services revamp of 0.3.2.
2666 This release also includes a fix for TROVE-2017-008, a security bug
2667 that affects hidden services running with the SafeLogging option
2668 disabled. For more information, see
2669 https://trac.torproject.org/projects/tor/ticket/23490
2671 Per our stable release policy, we plan to support each stable release
2672 series for at least the next nine months, or for three months after
2673 the first stable release of the next series: whichever is longer. If
2674 you need a release with long-term support, we recommend that you stay
2675 with the 0.2.9 series.
2677 Below is a list of the changes since 0.3.1.6-rc. For a list of all
2678 changes since 0.3.0, see the ReleaseNotes file.
2680 o Major bugfixes (security, hidden services, loggging):
2681 - Fix a bug where we could log uninitialized stack when a certain
2682 hidden service error occurred while SafeLogging was disabled.
2683 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
2684 TROVE-2017-008 and CVE-2017-0380.
2686 o Minor features (defensive programming):
2687 - Create a pair of consensus parameters, nf_pad_tor2web and
2688 nf_pad_single_onion, to disable netflow padding in the consensus
2689 for non-anonymous connections in case the overhead is high. Closes
2692 o Minor features (diagnostic):
2693 - Add a stack trace to the bug warnings that can be logged when
2694 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
2695 attempt for bug 23105.
2697 o Minor features (geoip):
2698 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2701 o Minor bugfixes (compilation):
2702 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2703 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2705 o Minor bugfixes (controller):
2706 - Do not crash when receiving a HSPOST command with an empty body.
2707 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2708 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2709 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2711 o Minor bugfixes (relay):
2712 - Inform the geoip and rephist modules about all requests, even on
2713 relays that are only fetching microdescriptors. Fixes a bug
2714 related to 21585; bugfix on 0.3.0.1-alpha.
2716 o Minor bugfixes (unit tests):
2717 - Fix a channelpadding unit test failure on slow systems by using
2718 mocked time instead of actual time. Fixes bug 23077; bugfix
2722 Changes in version 0.3.1.6-rc - 2017-09-05
2723 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
2724 release series, including a bug that produced weird behavior on
2725 Windows directory caches.
2727 This is the first release candidate in the Tor 0.3.1 series. If we
2728 find no new bugs or regressions here, the first stable 0.3.1 release
2729 will be nearly identical to it.
2731 o Major bugfixes (windows, directory cache):
2732 - On Windows, do not try to delete cached consensus documents and
2733 diffs before they are unmapped from memory--Windows won't allow
2734 that. Instead, allow the consensus cache directory to grow larger,
2735 to hold files that might need to stay around longer. Fixes bug
2736 22752; bugfix on 0.3.1.1-alpha.
2738 o Minor features (directory authority):
2739 - Improve the message that authorities report to relays that present
2740 RSA/Ed25519 keypairs that conflict with previously pinned keys.
2741 Closes ticket 22348.
2743 o Minor features (geoip):
2744 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
2747 o Minor features (testing):
2748 - Add more tests for compression backend initialization. Closes
2751 o Minor bugfixes (directory cache):
2752 - Fix a memory leak when recovering space in the consensus cache.
2753 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
2755 o Minor bugfixes (hidden service):
2756 - Increase the number of circuits that a service is allowed to
2757 open over a specific period of time. The value was lower than it
2758 should be (8 vs 12) in the normal case of 3 introduction points.
2759 Fixes bug 22159; bugfix on 0.3.0.5-rc.
2760 - Fix a BUG warning during HSv3 descriptor decoding that could be
2761 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
2762 on 0.3.0.1-alpha. Bug found by "haxxpop".
2763 - Rate-limit the log messages if we exceed the maximum number of
2764 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
2766 o Minor bugfixes (logging, relay):
2767 - Remove a forgotten debugging message when an introduction point
2768 successfully establishes a hidden service prop224 circuit with
2770 - Change three other log_warn() for an introduction point to
2771 protocol warnings, because they can be failure from the network
2772 and are not relevant to the operator. Fixes bug 23078; bugfix on
2773 0.3.0.1-alpha and 0.3.0.2-alpha.
2775 o Minor bugfixes (relay):
2776 - When a relay is not running as a directory cache, it will no
2777 longer generate compressed consensuses and consensus diff
2778 information. Previously, this was a waste of disk and CPU. Fixes
2779 bug 23275; bugfix on 0.3.1.1-alpha.
2781 o Minor bugfixes (robustness, error handling):
2782 - Improve our handling of the cases where OpenSSL encounters a
2783 memory error while encoding keys and certificates. We haven't
2784 observed these errors in the wild, but if they do happen, we now
2785 detect and respond better. Fixes bug 19418; bugfix on all versions
2786 of Tor. Reported by Guido Vranken.
2788 o Minor bugfixes (stability):
2789 - Avoid crashing on a double-free when unable to load or process an
2790 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
2791 with the clang static analyzer.
2793 o Minor bugfixes (testing):
2794 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2795 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2796 - Port the hs_ntor handshake test to work correctly with recent
2797 versions of the pysha3 module. Fixes bug 23071; bugfix
2800 o Minor bugfixes (Windows service):
2801 - When running as a Windows service, set the ID of the main thread
2802 correctly. Failure to do so made us fail to send log messages to
2803 the controller in 0.2.1.16-rc, slowed down controller event
2804 delivery in 0.2.7.3-rc and later, and crash with an assertion
2805 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2806 Patch and diagnosis from "Vort".
2809 Changes in version 0.3.0.10 - 2017-08-02
2810 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
2811 from the current Tor alpha series. OpenBSD users and TPROXY users
2812 should upgrade; others are probably okay sticking with 0.3.0.9.
2814 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
2815 - Tor's repository now includes a Travis Continuous Integration (CI)
2816 configuration file (.travis.yml). This is meant to help new
2817 developers and contributors who fork Tor to a Github repository be
2818 better able to test their changes, and understand what we expect
2819 to pass. To use this new build feature, you must fork Tor to your
2820 Github account, then go into the "Integrations" menu in the
2821 repository settings for your fork and enable Travis, then push
2822 your changes. Closes ticket 22636.
2824 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2825 - Fix a typo that had prevented TPROXY-based transparent proxying
2826 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2827 Patch from "d4fq0fQAgoJ".
2829 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2830 - Avoid an assertion failure bug affecting our implementation of
2831 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2832 handling of "0xbar" differs from what we had expected. Fixes bug
2833 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2835 o Minor features (backport from 0.3.1.5-alpha):
2836 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2839 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
2840 - Roll over monthly accounting at the configured hour and minute,
2841 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2842 Found by Andrey Karpov with PVS-Studio.
2844 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
2845 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2846 bugfix on 0.2.8.1-alpha.
2847 - Fix warnings when building with libscrypt and openssl scrypt
2848 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2849 - When building with certain versions of the mingw C header files,
2850 avoid float-conversion warnings when calling the C functions
2851 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2854 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2855 - Backport a fix for an "unused variable" warning that appeared
2856 in some versions of mingw. Fixes bug 22838; bugfix on
2859 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2860 - Avoid Coverity build warnings related to our BUG() macro. By
2861 default, Coverity treats BUG() as the Linux kernel does: an
2862 instant abort(). We need to override that so our BUG() macro
2863 doesn't prevent Coverity from analyzing functions that use it.
2864 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2866 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
2867 - When rejecting a router descriptor for running an obsolete version
2868 of Tor without ntor support, warn about the obsolete tor version,
2869 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2871 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2872 - Avoid a sandbox failure when trying to re-bind to a socket and
2873 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2875 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
2876 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2877 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2880 Changes in version 0.3.1.5-alpha - 2017-08-01
2881 Tor 0.3.1.5-alpha improves the performance of consensus diff
2882 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
2883 several other bugs. If no serious bugs are found in this version, the
2884 next version will be a release candidate.
2886 This release also marks the end of support for the Tor 0.2.4.x,
2887 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
2888 further bug or security fixes. Anyone still running or distributing
2889 one of those versions should upgrade.
2891 o Major features (build system, continuous integration):
2892 - Tor's repository now includes a Travis Continuous Integration (CI)
2893 configuration file (.travis.yml). This is meant to help new
2894 developers and contributors who fork Tor to a Github repository be
2895 better able to test their changes, and understand what we expect
2896 to pass. To use this new build feature, you must fork Tor to your
2897 Github account, then go into the "Integrations" menu in the
2898 repository settings for your fork and enable Travis, then push
2899 your changes. Closes ticket 22636.
2901 o Major bugfixes (openbsd, denial-of-service):
2902 - Avoid an assertion failure bug affecting our implementation of
2903 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2904 handling of "0xbar" differs from what we had expected. Fixes bug
2905 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2907 o Major bugfixes (relay, performance):
2908 - Perform circuit handshake operations at a higher priority than we
2909 use for consensus diff creation and compression. This should
2910 prevent circuits from starving when a relay or bridge receives a
2911 new consensus, especially on lower-powered machines. Fixes bug
2912 22883; bugfix on 0.3.1.1-alpha.
2914 o Minor features (bridge authority):
2915 - Add "fingerprint" lines to the networkstatus-bridges file produced
2916 by bridge authorities. Closes ticket 22207.
2918 o Minor features (directory cache, consensus diff):
2919 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
2920 operators with low-resource environments to adjust the number of
2921 consensuses they'll store and generate diffs from. Most cache
2922 operators should leave it unchanged. Helps to work around
2925 o Minor features (geoip):
2926 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2929 o Minor features (relay, performance):
2930 - Always start relays with at least two worker threads, to prevent
2931 priority inversion on slow tasks. Part of the fix for bug 22883.
2932 - Allow background work to be queued with different priorities, so
2933 that a big pile of slow low-priority jobs will not starve out
2934 higher priority jobs. This lays the groundwork for a fix for
2937 o Minor bugfixes (build system, rust):
2938 - Fix a problem where Rust toolchains were not being found when
2939 building without --enable-cargo-online-mode, due to setting the
2940 $HOME environment variable instead of $CARGO_HOME. Fixes bug
2941 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
2943 o Minor bugfixes (compatibility, zstd):
2944 - Write zstd epilogues correctly when the epilogue requires
2945 reallocation of the output buffer, even with zstd 1.3.0.
2946 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
2947 22927; bugfix on 0.3.1.1-alpha.
2949 o Minor bugfixes (compilation warnings):
2950 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
2951 22915; bugfix on 0.2.8.1-alpha.
2952 - Fix warnings when building with libscrypt and openssl scrypt
2953 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2954 - Compile correctly when both openssl 1.1.0 and libscrypt are
2955 detected. Previously this would cause an error. Fixes bug 22892;
2956 bugfix on 0.3.1.1-alpha.
2957 - When building with certain versions of the mingw C header files,
2958 avoid float-conversion warnings when calling the C functions
2959 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2962 o Minor bugfixes (coverity build support):
2963 - Avoid Coverity build warnings related to our BUG() macro. By
2964 default, Coverity treats BUG() as the Linux kernel does: an
2965 instant abort(). We need to override that so our BUG() macro
2966 doesn't prevent Coverity from analyzing functions that use it.
2967 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2969 o Minor bugfixes (directory authority):
2970 - When a directory authority rejects a descriptor or extrainfo with
2971 a given digest, mark that digest as undownloadable, so that we do
2972 not attempt to download it again over and over. We previously
2973 tried to avoid downloading such descriptors by other means, but we
2974 didn't notice if we accidentally downloaded one anyway. This
2975 behavior became problematic in 0.2.7.2-alpha, when authorities
2976 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2979 o Minor bugfixes (error reporting, windows):
2980 - When formatting Windows error messages, use the English format to
2981 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2984 o Minor bugfixes (file limits, osx):
2985 - When setting the maximum number of connections allowed by the OS,
2986 always allow some extra file descriptors for other files. Fixes
2987 bug 22797; bugfix on 0.2.0.10-alpha.
2989 o Minor bugfixes (linux seccomp2 sandbox):
2990 - Avoid a sandbox failure when trying to re-bind to a socket and
2991 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2993 o Minor bugfixes (memory leaks):
2994 - Fix a small memory leak when validating a configuration that uses
2995 two or more AF_UNIX sockets for the same port type. Fixes bug
2996 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2998 o Minor bugfixes (unit tests):
2999 - test_consdiff_base64cmp would fail on OS X because while OS X
3000 follows the standard of (less than zero/zero/greater than zero),
3001 it doesn't follow the convention of (-1/0/+1). Make the test
3002 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
3003 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3004 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3007 Changes in version 0.3.1.4-alpha - 2017-06-29
3008 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
3009 to use a guard that was in the same network family as a chosen exit
3010 relay. This is a security regression; all clients running earlier
3011 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
3014 This release also fixes several other bugs introduced in 0.3.0.x
3015 and 0.3.1.x, including others that can affect bandwidth usage
3019 - To build with zstd and lzma support, Tor now requires the
3020 pkg-config tool at build time. (This requirement was new in
3021 0.3.1.1-alpha, but was not noted at the time. Noting it here to
3022 close ticket 22623.)
3024 o Major bugfixes (path selection, security):
3025 - When choosing which guard to use for a circuit, avoid the exit's
3026 family along with the exit itself. Previously, the new guard
3027 selection logic avoided the exit, but did not consider its family.
3028 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3029 006 and CVE-2017-0377.
3031 o Major bugfixes (compression, zstd):
3032 - Correctly detect a full buffer when decompressing a large zstd-
3033 compressed input. Previously, we would sometimes treat a full
3034 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
3036 o Major bugfixes (directory protocol):
3037 - Ensure that we send "304 Not modified" as HTTP status code when a
3038 client is attempting to fetch a consensus or consensus diff, and
3039 the best one we can send them is one they already have. Fixes bug
3040 22702; bugfix on 0.3.1.1-alpha.
3042 o Major bugfixes (entry guards):
3043 - When starting with an old consensus, do not add new entry guards
3044 unless the consensus is "reasonably live" (under 1 day old). Fixes
3045 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3047 o Minor features (bug mitigation, diagnostics, logging):
3048 - Avoid an assertion failure, and log a better error message, when
3049 unable to remove a file from the consensus cache on Windows.
3050 Attempts to mitigate and diagnose bug 22752.
3052 o Minor features (geoip):
3053 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3056 o Minor bugfixes (compression):
3057 - When compressing or decompressing a buffer, check for a failure to
3058 create a compression object. Fixes bug 22626; bugfix
3060 - When decompressing a buffer, check for extra data after the end of
3061 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
3062 - When decompressing an object received over an anonymous directory
3063 connection, if we have already decompressed it using an acceptable
3064 compression method, do not reject it for looking like an
3065 unacceptable compression method. Fixes part of bug 22670; bugfix
3067 - When serving directory votes compressed with zlib, do not claim to
3068 have compressed them with zstd. Fixes bug 22669; bugfix
3070 - When spooling compressed data to an output buffer, don't try to
3071 spool more data when there is no more data to spool and we are not
3072 trying to flush the input. Previously, we would sometimes launch
3073 compression requests with nothing to do, which interferes with our
3074 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
3076 o Minor bugfixes (defensive programming):
3077 - Detect and break out of infinite loops in our compression code. We
3078 don't think that any such loops exist now, but it's best to be
3079 safe. Closes ticket 22672.
3080 - Fix a memset() off the end of an array when packing cells. This
3081 bug should be harmless in practice, since the corrupted bytes are
3082 still in the same structure, and are always padding bytes,
3083 ignored, or immediately overwritten, depending on compiler
3084 behavior. Nevertheless, because the memset()'s purpose is to make
3085 sure that any other cell-handling bugs can't expose bytes to the
3086 network, we need to fix it. Fixes bug 22737; bugfix on
3087 0.2.4.11-alpha. Fixes CID 1401591.
3089 o Minor bugfixes (linux seccomp2 sandbox):
3090 - Permit the fchmod system call, to avoid crashing on startup when
3091 starting with the seccomp2 sandbox and an unexpected set of
3092 permissions on the data directory or its contents. Fixes bug
3093 22516; bugfix on 0.2.5.4-alpha.
3094 - Fix a crash in the LZMA module, when the sandbox was enabled, and
3095 liblzma would allocate more than 16 MB of memory. We solve this by
3096 bumping the mprotect() limit in the sandbox module from 16 MB to
3097 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
3099 o Minor bugfixes (logging):
3100 - When decompressing, do not warn if we fail to decompress using a
3101 compression method that we merely guessed. Fixes part of bug
3102 22670; bugfix on 0.1.1.14-alpha.
3103 - When decompressing, treat mismatch between content-encoding and
3104 actual compression type as a protocol warning. Fixes part of bug
3105 22670; bugfix on 0.1.1.9-alpha.
3106 - Downgrade "assigned_to_cpuworker failed" message to info-level
3107 severity. In every case that can reach it, either a better warning
3108 has already been logged, or no warning is warranted. Fixes bug
3109 22356; bugfix on 0.2.6.3-alpha.
3110 - Demote a warn that was caused by libevent delays to info if
3111 netflow padding is less than 4.5 seconds late, or to notice
3112 if it is more (4.5 seconds is the amount of time that a netflow
3113 record might be emitted after, if we chose the maximum timeout).
3114 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
3116 o Minor bugfixes (process behavior):
3117 - When exiting because of an error, always exit with a nonzero exit
3118 status. Previously, we would fail to report an error in our exit
3119 status in cases related to __OwningControllerProcess failure,
3120 lockfile contention, and Ed25519 key initialization. Fixes bug
3121 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
3122 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
3126 - Add a manpage description for the key-pinning-journal file. Closes
3128 - Correctly note that bandwidth accounting values are stored in the
3129 state file, and the bw_accounting file is now obsolete. Closes
3131 - Document more of the files in the Tor data directory, including
3132 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
3133 approved-routers, sr-random, and diff-cache. Found while fixing
3137 Changes in version 0.3.0.9 - 2017-06-29
3138 Tor 0.3.0.9 fixes a path selection bug that would allow a client
3139 to use a guard that was in the same network family as a chosen exit
3140 relay. This is a security regression; all clients running earlier
3141 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
3144 This release also backports several other bugfixes from the 0.3.1.x
3147 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
3148 - When choosing which guard to use for a circuit, avoid the exit's
3149 family along with the exit itself. Previously, the new guard
3150 selection logic avoided the exit, but did not consider its family.
3151 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3152 006 and CVE-2017-0377.
3154 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
3155 - Don't block bootstrapping when a primary bridge is offline and we
3156 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3157 21969; bugfix on 0.3.0.3-alpha.
3159 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
3160 - When starting with an old consensus, do not add new entry guards
3161 unless the consensus is "reasonably live" (under 1 day old). Fixes
3162 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3164 o Minor features (geoip):
3165 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3168 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3169 - Reject version numbers with non-numeric prefixes (such as +, -, or
3170 whitespace). Disallowing whitespace prevents differential version
3171 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3172 and part of 21508; bugfix on 0.0.8pre1.
3174 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3175 - Permit the fchmod system call, to avoid crashing on startup when
3176 starting with the seccomp2 sandbox and an unexpected set of
3177 permissions on the data directory or its contents. Fixes bug
3178 22516; bugfix on 0.2.5.4-alpha.
3180 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
3181 - Fix a memset() off the end of an array when packing cells. This
3182 bug should be harmless in practice, since the corrupted bytes are
3183 still in the same structure, and are always padding bytes,
3184 ignored, or immediately overwritten, depending on compiler
3185 behavior. Nevertheless, because the memset()'s purpose is to make
3186 sure that any other cell-handling bugs can't expose bytes to the
3187 network, we need to fix it. Fixes bug 22737; bugfix on
3188 0.2.4.11-alpha. Fixes CID 1401591.
3191 Changes in version 0.3.1.3-alpha - 2017-06-08
3192 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
3193 remotely crash a hidden service with an assertion failure. Anyone
3194 running a hidden service should upgrade to this version, or to some
3195 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3197 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
3198 that sometimes made relays unreliable, as well as several other
3199 bugfixes described below.
3201 o Major bugfixes (hidden service, relay, security):
3202 - Fix a remotely triggerable assertion failure when a hidden service
3203 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3204 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3205 - Fix a remotely triggerable assertion failure caused by receiving a
3206 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3207 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3210 o Major bugfixes (relay, link handshake):
3211 - When performing the v3 link handshake on a TLS connection, report
3212 that we have the x509 certificate that we actually used on that
3213 connection, even if we have changed certificates since that
3214 connection was first opened. Previously, we would claim to have
3215 used our most recent x509 link certificate, which would sometimes
3216 make the link handshake fail. Fixes one case of bug 22460; bugfix
3219 o Major bugfixes (relays, key management):
3220 - Regenerate link and authentication certificates whenever the key
3221 that signs them changes; also, regenerate link certificates
3222 whenever the signed key changes. Previously, these processes were
3223 only weakly coupled, and we relays could (for minutes to hours)
3224 wind up with an inconsistent set of keys and certificates, which
3225 other relays would not accept. Fixes two cases of bug 22460;
3226 bugfix on 0.3.0.1-alpha.
3227 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3228 send the certificate that matches the x509 certificate that we
3229 used on the TLS connection. Previously, there was a race condition
3230 if the TLS context rotated after we began the TLS handshake but
3231 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3234 o Major bugfixes (torrc, crash):
3235 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
3236 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
3238 o Minor features (code style):
3239 - Add "Falls through" comments to our codebase, in order to silence
3240 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3241 Stieger. Closes ticket 22446.
3243 o Minor features (diagnostic):
3244 - Add logging messages to try to diagnose a rare bug that seems to
3245 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
3246 think this is happening because of incorrect system clocks, but
3247 we'd like to know for certain. Diagnostic for bug 22466.
3249 o Minor bugfixes (correctness):
3250 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3251 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3253 o Minor bugfixes (directory protocol):
3254 - Check for libzstd >= 1.1, because older versions lack the
3255 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
3257 o Minor bugfixes (link handshake):
3258 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3259 months, and regenerate it when it is within one month of expiring.
3260 Previously, we had generated this certificate at startup with a
3261 ten-year lifetime, but that could lead to weird behavior when Tor
3262 was started with a grossly inaccurate clock. Mitigates bug 22466;
3263 mitigation on 0.3.0.1-alpha.
3265 o Minor bugfixes (storage directories):
3266 - Always check for underflows in the cached storage directory usage.
3267 If the usage does underflow, re-calculate it. Also, avoid a
3268 separate underflow when the usage is not known. Fixes bug 22424;
3269 bugfix on 0.3.1.1-alpha.
3271 o Minor bugfixes (unit tests):
3272 - The unit tests now pass on systems where localhost is misconfigured
3273 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
3277 - Clarify the manpage for the (deprecated) torify script. Closes
3280 Changes in version 0.3.0.8 - 2017-06-08
3281 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
3282 remotely crash a hidden service with an assertion failure. Anyone
3283 running a hidden service should upgrade to this version, or to some
3284 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3286 Tor 0.3.0.8 also includes fixes for several key management bugs
3287 that sometimes made relays unreliable, as well as several other
3288 bugfixes described below.
3290 o Major bugfixes (hidden service, relay, security, backport
3291 from 0.3.1.3-alpha):
3292 - Fix a remotely triggerable assertion failure when a hidden service
3293 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3294 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3295 - Fix a remotely triggerable assertion failure caused by receiving a
3296 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3297 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3300 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3301 - When performing the v3 link handshake on a TLS connection, report
3302 that we have the x509 certificate that we actually used on that
3303 connection, even if we have changed certificates since that
3304 connection was first opened. Previously, we would claim to have
3305 used our most recent x509 link certificate, which would sometimes
3306 make the link handshake fail. Fixes one case of bug 22460; bugfix
3309 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
3310 - Regenerate link and authentication certificates whenever the key
3311 that signs them changes; also, regenerate link certificates
3312 whenever the signed key changes. Previously, these processes were
3313 only weakly coupled, and we relays could (for minutes to hours)
3314 wind up with an inconsistent set of keys and certificates, which
3315 other relays would not accept. Fixes two cases of bug 22460;
3316 bugfix on 0.3.0.1-alpha.
3317 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3318 send the certificate that matches the x509 certificate that we
3319 used on the TLS connection. Previously, there was a race condition
3320 if the TLS context rotated after we began the TLS handshake but
3321 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3324 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
3325 - Stop rejecting v3 hidden service descriptors because their size
3326 did not match an old padding rule. Fixes bug 22447; bugfix on
3329 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3330 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3331 December 2016 (of which ~126 were still functional) with a list of
3332 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3333 2017. Resolves ticket 21564.
3335 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
3336 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3337 bug 22252; bugfix on 0.2.9.3-alpha.
3339 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3340 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3341 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3343 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
3344 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3345 months, and regenerate it when it is within one month of expiring.
3346 Previously, we had generated this certificate at startup with a
3347 ten-year lifetime, but that could lead to weird behavior when Tor
3348 was started with a grossly inaccurate clock. Mitigates bug 22466;
3349 mitigation on 0.3.0.1-alpha.
3351 o Minor bugfixes (memory leak, directory authority, backport from
3353 - When directory authorities reject a router descriptor due to
3354 keypinning, free the router descriptor rather than leaking the
3355 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3358 Changes in version 0.2.9.11 - 2017-06-08
3359 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
3360 remotely crash a hidden service with an assertion failure. Anyone
3361 running a hidden service should upgrade to this version, or to some
3362 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3363 are not affected by TROVE-2017-004.)
3365 Tor 0.2.9.11 also backports fixes for several key management bugs
3366 that sometimes made relays unreliable, as well as several other
3367 bugfixes described below.
3369 o Major bugfixes (hidden service, relay, security, backport
3370 from 0.3.1.3-alpha):
3371 - Fix a remotely triggerable assertion failure caused by receiving a
3372 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3373 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3376 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3377 - When performing the v3 link handshake on a TLS connection, report
3378 that we have the x509 certificate that we actually used on that
3379 connection, even if we have changed certificates since that
3380 connection was first opened. Previously, we would claim to have
3381 used our most recent x509 link certificate, which would sometimes
3382 make the link handshake fail. Fixes one case of bug 22460; bugfix
3385 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3386 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3387 December 2016 (of which ~126 were still functional) with a list of
3388 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3389 2017. Resolves ticket 21564.
3391 o Minor features (future-proofing, backport from 0.3.0.7):
3392 - Tor no longer refuses to download microdescriptors or descriptors if
3393 they are listed as "published in the future". This change will
3394 eventually allow us to stop listing meaningful "published" dates
3395 in microdescriptor consensuses, and thereby allow us to reduce the
3396 resources required to download consensus diffs by over 50%.
3397 Implements part of ticket 21642; implements part of proposal 275.
3399 o Minor features (directory authorities, backport from 0.3.0.4-rc)
3400 - Directory authorities now reject relays running versions
3401 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3402 suffer from bug 20499 and don't keep their consensus cache
3403 up-to-date. Resolves ticket 20509.
3405 o Minor features (geoip):
3406 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3409 o Minor bugfixes (control port, backport from 0.3.0.6):
3410 - The GETINFO extra-info/digest/<digest> command was broken because
3411 of a wrong base16 decode return value check, introduced when
3412 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3414 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3415 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3416 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3418 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
3419 - The getpid() system call is now permitted under the Linux seccomp2
3420 sandbox, to avoid crashing with versions of OpenSSL (and other
3421 libraries) that attempt to learn the process's PID by using the
3422 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3425 o Minor bugfixes (memory leak, directory authority, backport
3426 from 0.3.1.2-alpha):
3427 - When directory authorities reject a router descriptor due to
3428 keypinning, free the router descriptor rather than leaking the
3429 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3431 Changes in version 0.2.8.14 - 2017-06-08
3432 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3433 remotely crash a hidden service with an assertion failure. Anyone
3434 running a hidden service should upgrade to this version, or to some
3435 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3436 are not affected by TROVE-2017-004.)
3438 o Major bugfixes (hidden service, relay, security):
3439 - Fix a remotely triggerable assertion failure caused by receiving a
3440 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3441 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3444 o Minor features (geoip):
3445 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3448 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3449 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3450 December 2016 (of which ~126 were still functional) with a list of
3451 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3452 2017. Resolves ticket 21564.
3454 o Minor bugfixes (correctness):
3455 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3456 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3458 Changes in version 0.2.7.8 - 2017-06-08
3459 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3460 remotely crash a hidden service with an assertion failure. Anyone
3461 running a hidden service should upgrade to this version, or to some
3462 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3463 are not affected by TROVE-2017-004.)
3465 o Major bugfixes (hidden service, relay, security):
3466 - Fix a remotely triggerable assertion failure caused by receiving a
3467 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3468 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3471 o Minor features (geoip):
3472 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3475 o Minor bugfixes (correctness):
3476 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3477 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3480 Changes in version 0.2.6.12 - 2017-06-08
3481 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
3482 remotely crash a hidden service with an assertion failure. Anyone
3483 running a hidden service should upgrade to this version, or to some
3484 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3485 are not affected by TROVE-2017-004.)
3487 o Major bugfixes (hidden service, relay, security):
3488 - Fix a remotely triggerable assertion failure caused by receiving a
3489 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3490 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3493 o Minor features (geoip):
3494 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3497 o Minor bugfixes (correctness):
3498 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3499 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3501 Changes in version 0.2.5.14 - 2017-06-08
3502 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
3503 remotely crash a hidden service with an assertion failure. Anyone
3504 running a hidden service should upgrade to this version, or to some
3505 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3506 are not affected by TROVE-2017-004.)
3508 o Major bugfixes (hidden service, relay, security):
3509 - Fix a remotely triggerable assertion failure caused by receiving a
3510 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3511 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3514 o Minor features (geoip):
3515 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3518 o Minor bugfixes (correctness):
3519 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3520 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3522 Changes in version 0.2.4.29 - 2017-06-08
3523 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
3524 remotely crash a hidden service with an assertion failure. Anyone
3525 running a hidden service should upgrade to this version, or to some
3526 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3527 are not affected by TROVE-2017-004.)
3529 o Major bugfixes (hidden service, relay, security):
3530 - Fix a remotely triggerable assertion failure caused by receiving a
3531 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3532 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3535 o Minor features (geoip):
3536 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3539 o Minor bugfixes (correctness):
3540 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3541 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3544 Changes in version 0.3.1.2-alpha - 2017-05-26
3545 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
3546 fixes a few bugs found while testing 0.3.1.1-alpha, including a
3547 memory corruption bug that affected relay stability.
3549 o Major bugfixes (crash, relay):
3550 - Fix a memory-corruption bug in relays that set MyFamily.
3551 Previously, they would double-free MyFamily elements when making
3552 the next descriptor or when changing their configuration. Fixes
3553 bug 22368; bugfix on 0.3.1.1-alpha.
3555 o Minor bugfixes (logging):
3556 - Log a better message when a directory authority replies to an
3557 upload with an unexpected status code. Fixes bug 11121; bugfix
3560 o Minor bugfixes (memory leak, directory authority):
3561 - When directory authorities reject a router descriptor due to
3562 keypinning, free the router descriptor rather than leaking the
3563 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3566 Changes in version 0.3.1.1-alpha - 2017-05-22
3567 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
3568 reduces the bandwidth usage for Tor's directory protocol, adds some
3569 basic padding to resist netflow-based traffic analysis and to serve as
3570 the basis of other padding in the future, and adds rust support to the
3573 It also contains numerous other small features and improvements to
3574 security, correctness, and performance.
3576 Below are the changes since 0.3.0.7.
3578 o Major features (directory protocol):
3579 - Tor relays and authorities can now serve clients an abbreviated
3580 version of the consensus document, containing only the changes
3581 since an older consensus document that the client holds. Clients
3582 now request these documents when available. When both client and
3583 server use this new protocol, they will use far less bandwidth (up
3584 to 94% less) to keep the client's consensus up-to-date. Implements
3585 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
3586 - Tor can now compress directory traffic with lzma or with zstd
3587 compression algorithms, which can deliver better bandwidth
3588 performance. Because lzma is computationally expensive, it's only
3589 used for documents that can be compressed once and served many
3590 times. Support for these algorithms requires that tor is built
3591 with the libzstd and/or liblzma libraries available. Implements
3592 proposal 278; closes ticket 21662.
3593 - Relays now perform the more expensive compression operations, and
3594 consensus diff generation, in worker threads. This separation
3595 avoids delaying the main thread when a new consensus arrives.
3597 o Major features (experimental):
3598 - Tor can now build modules written in Rust. To turn this on, pass
3599 the "--enable-rust" flag to the configure script. It's not time to
3600 get excited yet: currently, there is no actual Rust functionality
3601 beyond some simple glue code, and a notice at startup to tell you
3602 that Rust is running. Still, we hope that programmers and
3603 packagers will try building Tor with Rust support, so that we can
3604 find issues and solve portability problems. Closes ticket 22106.
3606 o Major features (traffic analysis resistance):
3607 - Connections between clients and relays now send a padding cell in
3608 each direction every 1.5 to 9.5 seconds (tunable via consensus
3609 parameters). This padding will not resist specialized
3610 eavesdroppers, but it should be enough to make many ISPs' routine
3611 network flow logging less useful in traffic analysis against
3614 Padding is negotiated using Tor's link protocol, so both relays
3615 and clients must upgrade for this to take effect. Clients may
3616 still send padding despite the relay's version by setting
3617 ConnectionPadding 1 in torrc, and may disable padding by setting
3618 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
3619 users with the torrc option ReducedConnectionPadding. Implements
3620 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
3621 - Relays will publish 24 hour totals of padding and non-padding cell
3622 counts to their extra-info descriptors, unless PaddingStatistics 0
3623 is set in torrc. These 24 hour totals are also rounded to
3626 o Major bugfixes (connection usage):
3627 - We use NETINFO cells to try to determine if both relays involved
3628 in a connection will agree on the canonical status of that
3629 connection. We prefer the connections where this is the case for
3630 extend cells, and try to close connections where relays disagree
3631 on their canonical status early. Also, we now prefer the oldest
3632 valid connection for extend cells. These two changes should reduce
3633 the number of long-term connections that are kept open between
3634 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
3635 - Relays now log hourly statistics (look for
3636 "channel_check_for_duplicates" lines) on the total number of
3637 connections to other relays. If the number of connections per
3638 relay is unexpectedly large, this log message is at notice level.
3639 Otherwise it is at info.
3641 o Major bugfixes (entry guards):
3642 - Don't block bootstrapping when a primary bridge is offline and we
3643 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3644 21969; bugfix on 0.3.0.3-alpha.
3646 o Major bugfixes (linux TPROXY support):
3647 - Fix a typo that had prevented TPROXY-based transparent proxying
3648 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3649 Patch from "d4fq0fQAgoJ".
3651 o Minor features (security, windows):
3652 - Enable a couple of pieces of Windows hardening: one
3653 (HeapEnableTerminationOnCorruption) that has been on-by-default
3654 since Windows 8, and unavailable before Windows 7; and one
3655 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3656 affect us, but shouldn't do any harm. Closes ticket 21953.
3658 o Minor features (config options):
3659 - Allow "%include" directives in torrc configuration files. These
3660 directives import the settings from other files, or from all the
3661 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
3662 - Make SAVECONF return an error when overwriting a torrc that has
3663 includes. Using SAVECONF with the FORCE option will allow it to
3664 overwrite torrc even if includes are used. Related to ticket 1922.
3665 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
3666 will work without the FORCE option. Related to ticket 1922.
3668 o Minor features (controller):
3669 - Warn the first time that a controller requests data in the long-
3670 deprecated 'GETINFO network-status' format. Closes ticket 21703.
3672 o Minor features (defaults):
3673 - The default value for UseCreateFast is now 0: clients which
3674 haven't yet received a consensus document will now use a proper
3675 ntor handshake to talk to their directory servers whenever they
3676 can. Closes ticket 21407.
3677 - Onion key rotation and expiry intervals are now defined as a
3678 network consensus parameter, per proposal 274. The default
3679 lifetime of an onion key is increased from 7 to 28 days. Old onion
3680 keys will expire after 7 days by default. This change will make
3681 consensus diffs much smaller, and save significant bandwidth.
3682 Closes ticket 21641.
3684 o Minor features (fallback directory list):
3685 - Update the fallback directory mirror whitelist and blacklist based
3686 on operator emails. Closes task 21121.
3687 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3688 December 2016 (of which ~126 were still functional) with a list of
3689 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3690 2017. Resolves ticket 21564.
3692 o Minor features (hidden services, logging):
3693 - Log a message when a hidden service descriptor has fewer
3694 introduction points than specified in
3695 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
3696 - Log a message when a hidden service reaches its introduction point
3697 circuit limit, and when that limit is reset. Follow up to ticket
3698 21594; closes ticket 21622.
3699 - Warn user if multiple entries in EntryNodes and at least one
3700 HiddenService are used together. Pinning EntryNodes along with a
3701 hidden service can be possibly harmful; for instance see ticket
3702 14917 or 21155. Closes ticket 21155.
3704 o Minor features (linux seccomp2 sandbox):
3705 - We now have a document storage backend compatible with the Linux
3706 seccomp2 sandbox. This backend is used for consensus documents and
3707 diffs between them; in the long term, we'd like to use it for
3708 unparseable directory material too. Closes ticket 21645
3709 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
3710 from 1MB to 16MB. This was necessary with the glibc allocator in
3711 order to allow worker threads to allocate more memory -- which in
3712 turn is necessary because of our new use of worker threads for
3713 compression. Closes ticket 22096.
3715 o Minor features (logging):
3716 - Log files are no longer created world-readable by default.
3717 (Previously, most distributors would store the logs in a non-
3718 world-readable location to prevent inappropriate access. This
3719 change is an extra precaution.) Closes ticket 21729; patch
3722 o Minor features (performance):
3723 - Our Keccak (SHA-3) implementation now accesses memory more
3724 efficiently, especially on little-endian systems. Closes
3726 - Add an O(1) implementation of channel_find_by_global_id(), to
3727 speed some controller functions.
3729 o Minor features (relay, configuration):
3730 - The MyFamily option may now be repeated as many times as desired,
3731 for relays that want to configure large families. Closes ticket
3732 4998; patch by Daniel Pinto.
3734 o Minor features (safety):
3735 - Add an explicit check to extrainfo_parse_entry_from_string() for
3736 NULL inputs. We don't believe this can actually happen, but it may
3737 help silence a warning from the Clang analyzer. Closes
3740 o Minor features (testing):
3741 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
3742 When Tor is compiled with this option, we disable a number of
3743 redundant memory-safety failsafes that are intended to stop bugs
3744 from becoming security issues. This makes it easier to hunt for
3745 bugs that would be security issues without the failsafes turned
3746 on. Closes ticket 21439.
3747 - Add a general event-tracing instrumentation support to Tor. This
3748 subsystem will enable developers and researchers to add fine-
3749 grained instrumentation to their Tor instances, for use when
3750 examining Tor network performance issues. There are no trace
3751 events yet, and event-tracing is off by default unless enabled at
3752 compile time. Implements ticket 13802.
3753 - Improve our version parsing tests: add tests for typical version
3754 components, add tests for invalid versions, including numeric
3755 range and non-numeric prefixes. Unit tests 21278, 21450, and
3756 21507. Partially implements 21470.
3758 o Minor bugfixes (bandwidth accounting):
3759 - Roll over monthly accounting at the configured hour and minute,
3760 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3761 Found by Andrey Karpov with PVS-Studio.
3763 o Minor bugfixes (code correctness):
3764 - Accurately identify client connections by their lack of peer
3765 authentication. This means that we bail out earlier if asked to
3766 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
3769 o Minor bugfixes (configuration):
3770 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3771 bug 22252; bugfix on 0.2.9.3-alpha.
3773 o Minor bugfixes (connection lifespan):
3774 - Allow more control over how long TLS connections are kept open:
3775 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
3776 single option called CircuitsAvailableTimeout. Also, allow the
3777 consensus to control the default values for both this preference
3778 and the lifespan of relay-to-relay connections. Fixes bug 17592;
3779 bugfix on 0.2.5.5-alpha.
3780 - Increase the initial circuit build timeout testing frequency, to
3781 help ensure that ReducedConnectionPadding clients finish learning
3782 a timeout before their orconn would expire. The initial testing
3783 rate was set back in the days of TAP and before the Tor Browser
3784 updater, when we had to be much more careful about new clients
3785 making lots of circuits. With this change, a circuit build timeout
3786 is learned in about 15-20 minutes, instead of 100-120 minutes.
3788 o Minor bugfixes (controller):
3789 - GETINFO onions/current and onions/detached no longer respond with
3790 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
3791 - Trigger HS descriptor events on the control port when the client
3792 fails to pick a hidden service directory for a hidden service.
3793 This can happen if all the hidden service directories are in
3794 ExcludeNodes, or they have all been queried within the last 15
3795 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
3797 o Minor bugfixes (directory authority):
3798 - When rejecting a router descriptor for running an obsolete version
3799 of Tor without ntor support, warn about the obsolete tor version,
3800 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3801 - Prevent the shared randomness subsystem from asserting when
3802 initialized by a bridge authority with an incomplete configuration
3803 file. Fixes bug 21586; bugfix on 0.2.9.8.
3805 o Minor bugfixes (exit-side DNS):
3806 - Fix an untriggerable assertion that checked the output of a
3807 libevent DNS error, so that the assertion actually behaves as
3808 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
3809 Karpov using PVS-Studio.
3811 o Minor bugfixes (fallback directories):
3812 - Make the usage example in updateFallbackDirs.py actually work, and
3813 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
3814 - Decrease the guard flag average required to be a fallback. This
3815 allows us to keep relays that have their guard flag removed when
3816 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3817 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
3818 bugfix on 0.2.8.1-alpha.
3819 - Make sure fallback directory mirrors have the same address, port,
3820 and relay identity key for at least 30 days before they are
3821 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3823 o Minor bugfixes (hidden services):
3824 - Stop printing a cryptic warning when a hidden service gets a
3825 request to connect to a virtual port that it hasn't configured.
3826 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
3827 - Simplify hidden service descriptor creation by using an existing
3828 flag to check if an introduction point is established. Fixes bug
3829 21599; bugfix on 0.2.7.2-alpha.
3831 o Minor bugfixes (memory leak):
3832 - Fix a small memory leak at exit from the backtrace handler code.
3833 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
3835 o Minor bugfixes (protocol, logging):
3836 - Downgrade a log statement about unexpected relay cells from "bug"
3837 to "protocol warning", because there is at least one use case
3838 where it can be triggered by a buggy tor implementation. Fixes bug
3839 21293; bugfix on 0.1.1.14-alpha.
3841 o Minor bugfixes (testing):
3842 - Use unbuffered I/O for utility functions around the
3843 process_handle_t type. This fixes unit test failures reported on
3844 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
3845 - Make display of captured unit test log messages consistent. Fixes
3846 bug 21510; bugfix on 0.2.9.3-alpha.
3847 - Make test-network.sh always call chutney's test-network.sh.
3848 Previously, this only worked on systems which had bash installed,
3849 due to some bash-specific code in the script. Fixes bug 19699;
3850 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
3852 o Minor bugfixes (voting consistency):
3853 - Reject version numbers with non-numeric prefixes (such as +, -, or
3854 whitespace). Disallowing whitespace prevents differential version
3855 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3856 and part of 21508; bugfix on 0.0.8pre1.
3858 o Minor bugfixes (windows, relay):
3859 - Resolve "Failure from drain_fd: No error" warnings on Windows
3860 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
3862 o Code simplification and refactoring:
3863 - Break up the 630-line function connection_dir_client_reached_eof()
3864 into a dozen smaller functions. This change should help
3865 maintainability and readability of the client directory code.
3866 - Isolate our use of the openssl headers so that they are only
3867 included from our crypto wrapper modules, and from tests that
3868 examine those modules' internals. Closes ticket 21841.
3869 - Simplify our API to launch directory requests, making it more
3870 extensible and less error-prone. Now it's easier to add extra
3871 headers to directory requests. Closes ticket 21646.
3872 - Our base64 decoding functions no longer overestimate the output
3873 space that they need when parsing unpadded inputs. Closes
3875 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
3876 Resolves ticket 22213.
3877 - The logic that directory caches use to spool request to clients,
3878 serving them one part at a time so as not to allocate too much
3879 memory, has been refactored for consistency. Previously there was
3880 a separate spooling implementation per type of spoolable data. Now
3881 there is one common spooling implementation, with extensible data
3882 types. Closes ticket 21651.
3883 - Tor's compression module now supports multiple backends. Part of
3884 the implementation for proposal 278; closes ticket 21663.
3887 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
3888 Closes ticket 21873.
3889 - Correct documentation about the default DataDirectory value.
3890 Closes ticket 21151.
3891 - Document the default behavior of NumEntryGuards and
3892 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
3894 - Document key=value pluggable transport arguments for Bridge lines
3895 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
3896 - Note that bandwidth-limiting options don't affect TCP headers or
3897 DNS. Closes ticket 17170.
3899 o Removed features (configuration options, all in ticket 22060):
3900 - These configuration options are now marked Obsolete, and no longer
3901 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3902 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3903 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3904 in 0.2.9.2-alpha and have now been removed. The previous default
3905 behavior is now always chosen; the previous (less secure) non-
3906 default behavior is now unavailable.
3907 - CloseHSClientCircuitsImmediatelyOnTimeout and
3908 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3909 0.2.9.2-alpha and now have been removed. HS circuits never close
3910 on circuit build timeout; they have a longer timeout period.
3911 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3912 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3913 (and others) to configure listen-only and advertise-only addresses.
3915 o Removed features (tools):
3916 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3917 used it to help people detect RSA keys that were generated by
3918 versions of Debian affected by CVE-2008-0166. But those keys have
3919 been out of circulation for ages, and this tool is no longer
3920 required. Closes ticket 21842.
3923 Changes in version 0.3.0.7 - 2017-05-15
3924 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3925 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3926 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3927 clients are not affected.
3929 o Major bugfixes (hidden service directory, security):
3930 - Fix an assertion failure in the hidden service directory code, which
3931 could be used by an attacker to remotely cause a Tor relay process to
3932 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3933 should upgrade. This security issue is tracked as TROVE-2017-002.
3934 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3937 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3940 o Minor features (future-proofing):
3941 - Tor no longer refuses to download microdescriptors or descriptors
3942 if they are listed as "published in the future". This change will
3943 eventually allow us to stop listing meaningful "published" dates
3944 in microdescriptor consensuses, and thereby allow us to reduce the
3945 resources required to download consensus diffs by over 50%.
3946 Implements part of ticket 21642; implements part of proposal 275.
3948 o Minor bugfixes (Linux seccomp2 sandbox):
3949 - The getpid() system call is now permitted under the Linux seccomp2
3950 sandbox, to avoid crashing with versions of OpenSSL (and other
3951 libraries) that attempt to learn the process's PID by using the
3952 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3956 Changes in version 0.3.0.6 - 2017-04-26
3957 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3959 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3960 authenticate their link connections to relays, rather than the old
3961 RSA1024 keys that they used before. (Circuit crypto has been
3962 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3963 the guard selection and replacement algorithm to behave more robustly
3964 in the presence of unreliable networks, and to resist guard-
3967 This series also includes numerous other small features and bugfixes,
3968 along with more groundwork for the upcoming hidden-services revamp.
3970 Per our stable release policy, we plan to support the Tor 0.3.0
3971 release series for at least the next nine months, or for three months
3972 after the first stable release of the 0.3.1 series: whichever is
3973 longer. If you need a release with long-term support, we recommend
3974 that you stay with the 0.2.9 series.
3976 Below are the changes since 0.3.0.5-rc. For a list of all changes
3977 since 0.2.9, see the ReleaseNotes file.
3979 o Minor features (geoip):
3980 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
3983 o Minor bugfixes (control port):
3984 - The GETINFO extra-info/digest/<digest> command was broken because
3985 of a wrong base16 decode return value check, introduced when
3986 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3988 o Minor bugfixes (crash prevention):
3989 - Fix a (currently untriggerable, but potentially dangerous) crash
3990 bug when base32-encoding inputs whose sizes are not a multiple of
3991 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3994 Changes in version 0.3.0.5-rc - 2017-04-05
3995 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
3996 0.3.0 release series.
3998 This is the second release candidate in the Tor 0.3.0 series, and has
3999 much fewer changes than the first. If we find no new bugs or
4000 regressions here, the first stable 0.3.0 release will be nearly
4003 o Major bugfixes (crash, directory connections):
4004 - Fix a rare crash when sending a begin cell on a circuit whose
4005 linked directory connection had already been closed. Fixes bug
4006 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
4008 o Major bugfixes (guard selection):
4009 - Fix a guard selection bug where Tor would refuse to bootstrap in
4010 some cases if the user swapped a bridge for another bridge in
4011 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
4012 Reported by "torvlnt33r".
4014 o Minor features (geoip):
4015 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
4018 o Minor bugfix (compilation):
4019 - Fix a warning when compiling hs_service.c. Previously, it had no
4020 exported symbols when compiled for libor.a, resulting in a
4021 compilation warning from clang. Fixes bug 21825; bugfix
4024 o Minor bugfixes (hidden services):
4025 - Make hidden services check for failed intro point connections,
4026 even when they have exceeded their intro point creation limit.
4027 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
4028 - Make hidden services with 8 to 10 introduction points check for
4029 failed circuits immediately after startup. Previously, they would
4030 wait for 5 minutes before performing their first checks. Fixes bug
4031 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
4033 o Minor bugfixes (memory leaks):
4034 - Fix a memory leak when using GETCONF on a port option. Fixes bug
4035 21682; bugfix on 0.3.0.3-alpha.
4037 o Minor bugfixes (relay):
4038 - Avoid a double-marked-circuit warning that could happen when we
4039 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
4042 o Minor bugfixes (tests):
4043 - Run the entry_guard_parse_from_state_full() test with the time set
4044 to a specific date. (The guard state that this test was parsing
4045 contained guards that had expired since the test was first
4046 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
4049 - Update the description of the directory server options in the
4050 manual page, to clarify that a relay no longer needs to set
4051 DirPort in order to be a directory cache. Closes ticket 21720.
4055 Changes in version 0.2.8.13 - 2017-03-03
4056 Tor 0.2.8.13 backports a security fix from later Tor
4057 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
4058 this release, if for some reason they cannot upgrade to a later
4059 release series, and if they build Tor with the --enable-expensive-hardening
4062 Note that support for Tor 0.2.8.x is ending next year: we will not issue
4063 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
4064 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4066 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4067 - Fix an integer underflow bug when comparing malformed Tor
4068 versions. This bug could crash Tor when built with
4069 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4070 0.2.9.8, which were built with -ftrapv by default. In other cases
4071 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4072 on 0.0.8pre1. Found by OSS-Fuzz.
4074 o Minor features (geoip):
4075 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4079 Changes in version 0.2.7.7 - 2017-03-03
4080 Tor 0.2.7.7 backports a number of security fixes from later Tor
4081 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
4082 this release, if for some reason they cannot upgrade to a later
4085 Note that support for Tor 0.2.7.x is ending this year: we will not issue
4086 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
4087 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4089 o Directory authority changes (backport from 0.2.8.5-rc):
4090 - Urras is no longer a directory authority. Closes ticket 19271.
4092 o Directory authority changes (backport from 0.2.9.2-alpha):
4093 - The "Tonga" bridge authority has been retired; the new bridge
4094 authority is "Bifroest". Closes tickets 19728 and 19690.
4096 o Directory authority key updates (backport from 0.2.8.1-alpha):
4097 - Update the V3 identity key for the dannenberg directory authority:
4098 it was changed on 18 November 2015. Closes task 17906. Patch
4101 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4102 - Fix a bug in parsing that could cause clients to read a single
4103 byte past the end of an allocated region. This bug could be used
4104 to cause hardened clients (built with --enable-expensive-hardening)
4105 to crash if they tried to visit a hostile hidden service. Non-
4106 hardened clients are only affected depending on the details of
4107 their platform's memory allocator. Fixes bug 21018; bugfix on
4108 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4109 2016-12-002 and as CVE-2016-1254.
4111 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4112 - Stop a crash that could occur when a client running with DNSPort
4113 received a query with multiple address types, and the first
4114 address type was not supported. Found and fixed by Scott Dial.
4115 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4116 - Prevent a class of security bugs caused by treating the contents
4117 of a buffer chunk as if they were a NUL-terminated string. At
4118 least one such bug seems to be present in all currently used
4119 versions of Tor, and would allow an attacker to remotely crash
4120 most Tor instances, especially those compiled with extra compiler
4121 hardening. With this defense in place, such bugs can't crash Tor,
4122 though we should still fix them as they occur. Closes ticket
4123 20384 (TROVE-2016-10-001).
4125 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4126 - Avoid a difficult-to-trigger heap corruption attack when extending
4127 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4128 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4129 Reported by Guido Vranken.
4131 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4132 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4133 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4135 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4136 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4137 pointer to the previous (uninitialized) key value. The impact here
4138 should be limited to a difficult-to-trigger crash, if OpenSSL is
4139 running an engine that makes key generation failures possible, or
4140 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4141 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4144 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4145 - Fix an integer underflow bug when comparing malformed Tor
4146 versions. This bug could crash Tor when built with
4147 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4148 0.2.9.8, which were built with -ftrapv by default. In other cases
4149 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4150 on 0.0.8pre1. Found by OSS-Fuzz.
4152 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4153 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4154 zero size. Check size argument to memwipe() for underflow. Fixes
4155 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4158 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4159 - Make Tor survive errors involving connections without a
4160 corresponding event object. Previously we'd fail with an
4161 assertion; now we produce a log message. Related to bug 16248.
4163 o Minor features (geoip):
4164 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4168 Changes in version 0.2.6.11 - 2017-03-03
4169 Tor 0.2.6.11 backports a number of security fixes from later Tor
4170 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
4171 this release, if for some reason they cannot upgrade to a later
4174 Note that support for Tor 0.2.6.x is ending this year: we will not issue
4175 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
4176 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4178 o Directory authority changes (backport from 0.2.8.5-rc):
4179 - Urras is no longer a directory authority. Closes ticket 19271.
4181 o Directory authority changes (backport from 0.2.9.2-alpha):
4182 - The "Tonga" bridge authority has been retired; the new bridge
4183 authority is "Bifroest". Closes tickets 19728 and 19690.
4185 o Directory authority key updates (backport from 0.2.8.1-alpha):
4186 - Update the V3 identity key for the dannenberg directory authority:
4187 it was changed on 18 November 2015. Closes task 17906. Patch
4190 o Major features (security fixes, backport from 0.2.9.4-alpha):
4191 - Prevent a class of security bugs caused by treating the contents
4192 of a buffer chunk as if they were a NUL-terminated string. At
4193 least one such bug seems to be present in all currently used
4194 versions of Tor, and would allow an attacker to remotely crash
4195 most Tor instances, especially those compiled with extra compiler
4196 hardening. With this defense in place, such bugs can't crash Tor,
4197 though we should still fix them as they occur. Closes ticket
4198 20384 (TROVE-2016-10-001).
4200 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4201 - Fix a bug in parsing that could cause clients to read a single
4202 byte past the end of an allocated region. This bug could be used
4203 to cause hardened clients (built with --enable-expensive-hardening)
4204 to crash if they tried to visit a hostile hidden service. Non-
4205 hardened clients are only affected depending on the details of
4206 their platform's memory allocator. Fixes bug 21018; bugfix on
4207 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4208 2016-12-002 and as CVE-2016-1254.
4210 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4211 - Stop a crash that could occur when a client running with DNSPort
4212 received a query with multiple address types, and the first
4213 address type was not supported. Found and fixed by Scott Dial.
4214 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4216 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4217 - Fix an error that could cause us to read 4 bytes before the
4218 beginning of an openssl string. This bug could be used to cause
4219 Tor to crash on systems with unusual malloc implementations, or
4220 systems with unusual hardening installed. Fixes bug 17404; bugfix
4223 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4224 - Avoid a difficult-to-trigger heap corruption attack when extending
4225 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4226 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4227 Reported by Guido Vranken.
4229 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4230 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4231 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4233 o Major bugfixes (guard selection, backport from 0.2.7.6):
4234 - Actually look at the Guard flag when selecting a new directory
4235 guard. When we implemented the directory guard design, we
4236 accidentally started treating all relays as if they have the Guard
4237 flag during guard selection, leading to weaker anonymity and worse
4238 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4241 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4242 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4243 pointer to the previous (uninitialized) key value. The impact here
4244 should be limited to a difficult-to-trigger crash, if OpenSSL is
4245 running an engine that makes key generation failures possible, or
4246 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4247 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4250 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4251 - Fix an integer underflow bug when comparing malformed Tor
4252 versions. This bug could crash Tor when built with
4253 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4254 0.2.9.8, which were built with -ftrapv by default. In other cases
4255 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4256 on 0.0.8pre1. Found by OSS-Fuzz.
4258 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4259 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4260 zero size. Check size argument to memwipe() for underflow. Fixes
4261 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4264 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4265 - Make Tor survive errors involving connections without a
4266 corresponding event object. Previously we'd fail with an
4267 assertion; now we produce a log message. Related to bug 16248.
4269 o Minor features (geoip):
4270 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4273 o Minor bugfixes (compilation, backport from 0.2.7.6):
4274 - Fix a compilation warning with Clang 3.6: Do not check the
4275 presence of an address which can never be NULL. Fixes bug 17781.
4278 Changes in version 0.2.5.13 - 2017-03-03
4279 Tor 0.2.5.13 backports a number of security fixes from later Tor
4280 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
4281 this release, if for some reason they cannot upgrade to a later
4284 Note that support for Tor 0.2.5.x is ending next year: we will not issue
4285 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
4286 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4288 o Directory authority changes (backport from 0.2.8.5-rc):
4289 - Urras is no longer a directory authority. Closes ticket 19271.
4291 o Directory authority changes (backport from 0.2.9.2-alpha):
4292 - The "Tonga" bridge authority has been retired; the new bridge
4293 authority is "Bifroest". Closes tickets 19728 and 19690.
4295 o Directory authority key updates (backport from 0.2.8.1-alpha):
4296 - Update the V3 identity key for the dannenberg directory authority:
4297 it was changed on 18 November 2015. Closes task 17906. Patch
4300 o Major features (security fixes, backport from 0.2.9.4-alpha):
4301 - Prevent a class of security bugs caused by treating the contents
4302 of a buffer chunk as if they were a NUL-terminated string. At
4303 least one such bug seems to be present in all currently used
4304 versions of Tor, and would allow an attacker to remotely crash
4305 most Tor instances, especially those compiled with extra compiler
4306 hardening. With this defense in place, such bugs can't crash Tor,
4307 though we should still fix them as they occur. Closes ticket
4308 20384 (TROVE-2016-10-001).
4310 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4311 - Fix a bug in parsing that could cause clients to read a single
4312 byte past the end of an allocated region. This bug could be used
4313 to cause hardened clients (built with --enable-expensive-hardening)
4314 to crash if they tried to visit a hostile hidden service. Non-
4315 hardened clients are only affected depending on the details of
4316 their platform's memory allocator. Fixes bug 21018; bugfix on
4317 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4318 2016-12-002 and as CVE-2016-1254.
4320 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4321 - Stop a crash that could occur when a client running with DNSPort
4322 received a query with multiple address types, and the first
4323 address type was not supported. Found and fixed by Scott Dial.
4324 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4326 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4327 - Fix an error that could cause us to read 4 bytes before the
4328 beginning of an openssl string. This bug could be used to cause
4329 Tor to crash on systems with unusual malloc implementations, or
4330 systems with unusual hardening installed. Fixes bug 17404; bugfix
4333 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4334 - Avoid a difficult-to-trigger heap corruption attack when extending
4335 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4336 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4337 Reported by Guido Vranken.
4339 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4340 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4341 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4343 o Major bugfixes (guard selection, backport from 0.2.7.6):
4344 - Actually look at the Guard flag when selecting a new directory
4345 guard. When we implemented the directory guard design, we
4346 accidentally started treating all relays as if they have the Guard
4347 flag during guard selection, leading to weaker anonymity and worse
4348 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4351 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4352 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4353 pointer to the previous (uninitialized) key value. The impact here
4354 should be limited to a difficult-to-trigger crash, if OpenSSL is
4355 running an engine that makes key generation failures possible, or
4356 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4357 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4360 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4361 - Fix an integer underflow bug when comparing malformed Tor
4362 versions. This bug could crash Tor when built with
4363 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4364 0.2.9.8, which were built with -ftrapv by default. In other cases
4365 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4366 on 0.0.8pre1. Found by OSS-Fuzz.
4368 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4369 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4370 zero size. Check size argument to memwipe() for underflow. Fixes
4371 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4374 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4375 - Make Tor survive errors involving connections without a
4376 corresponding event object. Previously we'd fail with an
4377 assertion; now we produce a log message. Related to bug 16248.
4379 o Minor features (geoip):
4380 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4383 o Minor bugfixes (compilation, backport from 0.2.7.6):
4384 - Fix a compilation warning with Clang 3.6: Do not check the
4385 presence of an address which can never be NULL. Fixes bug 17781.
4387 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
4388 - Check for failures from crypto_early_init, and refuse to continue.
4389 A previous typo meant that we could keep going with an
4390 uninitialized crypto library, and would have OpenSSL initialize
4391 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4392 when implementing ticket 4900. Patch by "teor".
4394 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4395 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4396 a client authorized hidden service. Fixes bug 15823; bugfix
4400 Changes in version 0.2.4.28 - 2017-03-03
4401 Tor 0.2.4.28 backports a number of security fixes from later Tor
4402 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
4403 this release, if for some reason they cannot upgrade to a later
4406 Note that support for Tor 0.2.4.x is ending soon: we will not issue
4407 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
4408 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
4410 o Directory authority changes (backport from 0.2.8.5-rc):
4411 - Urras is no longer a directory authority. Closes ticket 19271.
4413 o Directory authority changes (backport from 0.2.9.2-alpha):
4414 - The "Tonga" bridge authority has been retired; the new bridge
4415 authority is "Bifroest". Closes tickets 19728 and 19690.
4417 o Directory authority key updates (backport from 0.2.8.1-alpha):
4418 - Update the V3 identity key for the dannenberg directory authority:
4419 it was changed on 18 November 2015. Closes task 17906. Patch
4422 o Major features (security fixes, backport from 0.2.9.4-alpha):
4423 - Prevent a class of security bugs caused by treating the contents
4424 of a buffer chunk as if they were a NUL-terminated string. At
4425 least one such bug seems to be present in all currently used
4426 versions of Tor, and would allow an attacker to remotely crash
4427 most Tor instances, especially those compiled with extra compiler
4428 hardening. With this defense in place, such bugs can't crash Tor,
4429 though we should still fix them as they occur. Closes ticket
4430 20384 (TROVE-2016-10-001).
4432 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4433 - Fix a bug in parsing that could cause clients to read a single
4434 byte past the end of an allocated region. This bug could be used
4435 to cause hardened clients (built with --enable-expensive-hardening)
4436 to crash if they tried to visit a hostile hidden service. Non-
4437 hardened clients are only affected depending on the details of
4438 their platform's memory allocator. Fixes bug 21018; bugfix on
4439 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4440 2016-12-002 and as CVE-2016-1254.
4442 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4443 - Fix an error that could cause us to read 4 bytes before the
4444 beginning of an openssl string. This bug could be used to cause
4445 Tor to crash on systems with unusual malloc implementations, or
4446 systems with unusual hardening installed. Fixes bug 17404; bugfix
4449 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4450 - Avoid a difficult-to-trigger heap corruption attack when extending
4451 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4452 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4453 Reported by Guido Vranken.
4455 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4456 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4457 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4459 o Major bugfixes (guard selection, backport from 0.2.7.6):
4460 - Actually look at the Guard flag when selecting a new directory
4461 guard. When we implemented the directory guard design, we
4462 accidentally started treating all relays as if they have the Guard
4463 flag during guard selection, leading to weaker anonymity and worse
4464 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4467 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4468 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4469 pointer to the previous (uninitialized) key value. The impact here
4470 should be limited to a difficult-to-trigger crash, if OpenSSL is
4471 running an engine that makes key generation failures possible, or
4472 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4473 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4476 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4477 - Fix an integer underflow bug when comparing malformed Tor
4478 versions. This bug could crash Tor when built with
4479 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4480 0.2.9.8, which were built with -ftrapv by default. In other cases
4481 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4482 on 0.0.8pre1. Found by OSS-Fuzz.
4484 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4485 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4486 zero size. Check size argument to memwipe() for underflow. Fixes
4487 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4490 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4491 - Make Tor survive errors involving connections without a
4492 corresponding event object. Previously we'd fail with an
4493 assertion; now we produce a log message. Related to bug 16248.
4495 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
4496 - Make it harder for attackers to overload hidden services with
4497 introductions, by blocking multiple introduction requests on the
4498 same circuit. Resolves ticket 15515.
4500 o Minor features (geoip):
4501 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4504 o Minor bugfixes (compilation, backport from 0.2.7.6):
4505 - Fix a compilation warning with Clang 3.6: Do not check the
4506 presence of an address which can never be NULL. Fixes bug 17781.
4508 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4509 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4510 a client authorized hidden service. Fixes bug 15823; bugfix
4514 Changes in version 0.3.0.4-rc - 2017-03-01
4515 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
4516 0.3.0 release series, and introduces a few reliability features to
4517 keep them from coming back.
4519 This is the first release candidate in the Tor 0.3.0 series. If we
4520 find no new bugs or regressions here, the first stable 0.3.0 release
4521 will be nearly identical to it.
4523 o Major bugfixes (bridges):
4524 - When the same bridge is configured multiple times with the same
4525 identity, but at different address:port combinations, treat those
4526 bridge instances as separate guards. This fix restores the ability
4527 of clients to configure the same bridge with multiple pluggable
4528 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
4530 o Major bugfixes (hidden service directory v3):
4531 - Stop crashing on a failed v3 hidden service descriptor lookup
4532 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
4534 o Major bugfixes (parsing):
4535 - When parsing a malformed content-length field from an HTTP
4536 message, do not read off the end of the buffer. This bug was a
4537 potential remote denial-of-service attack against Tor clients and
4538 relays. A workaround was released in October 2016, to prevent this
4539 bug from crashing Tor. This is a fix for the underlying issue,
4540 which should no longer matter (if you applied the earlier patch).
4541 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
4542 using AFL (http://lcamtuf.coredump.cx/afl/).
4543 - Fix an integer underflow bug when comparing malformed Tor
4544 versions. This bug could crash Tor when built with
4545 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4546 0.2.9.8, which were built with -ftrapv by default. In other cases
4547 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4548 on 0.0.8pre1. Found by OSS-Fuzz.
4550 o Minor feature (protocol versioning):
4551 - Add new protocol version for proposal 224. HSIntro now advertises
4552 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
4554 o Minor features (directory authorities):
4555 - Directory authorities now reject descriptors that claim to be
4556 malformed versions of Tor. Helps prevent exploitation of
4558 - Reject version numbers with components that exceed INT32_MAX.
4559 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
4560 Fixes bug 21450; bugfix on 0.0.8pre1.
4561 - Directory authorities now reject relays running versions
4562 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
4563 suffer from bug 20499 and don't keep their consensus cache
4564 up-to-date. Resolves ticket 20509.
4566 o Minor features (geoip):
4567 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4570 o Minor features (reliability, crash):
4571 - Try better to detect problems in buffers where they might grow (or
4572 think they have grown) over 2 GB in size. Diagnostic for
4575 o Minor features (testing):
4576 - During 'make test-network-all', if tor logs any warnings, ask
4577 chutney to output them. Requires a recent version of chutney with
4578 the 21572 patch. Implements 21570.
4580 o Minor bugfixes (certificate expiration time):
4581 - Avoid using link certificates that don't become valid till some
4582 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
4584 o Minor bugfixes (code correctness):
4585 - Repair a couple of (unreachable or harmless) cases of the risky
4586 comparison-by-subtraction pattern that caused bug 21278.
4587 - Remove a redundant check for the UseEntryGuards option from the
4588 options_transition_affects_guards() function. Fixes bug 21492;
4589 bugfix on 0.3.0.1-alpha.
4591 o Minor bugfixes (directory mirrors):
4592 - Allow relays to use directory mirrors without a DirPort: these
4593 relays need to be contacted over their ORPorts using a begindir
4594 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
4595 - Clarify the message logged when a remote relay is unexpectedly
4596 missing an ORPort or DirPort: users were confusing this with a
4597 local port. Fixes another case of bug 20711; bugfix
4600 o Minor bugfixes (guards):
4601 - Don't warn about a missing guard state on timeout-measurement
4602 circuits: they aren't supposed to be using guards. Fixes an
4603 instance of bug 21007; bugfix on 0.3.0.1-alpha.
4604 - Silence a BUG() warning when attempting to use a guard whose
4605 descriptor we don't know, and make this scenario less likely to
4606 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
4608 o Minor bugfixes (hidden service):
4609 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
4610 cells. Previously, we were using sizeof() on a pointer, instead of
4611 the real destination buffer. Fortunately, that value was only used
4612 to double-check that there was enough room--which was already
4613 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
4615 o Minor bugfixes (testing):
4616 - Fix Raspbian build issues related to missing socket errno in
4617 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
4619 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
4620 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
4621 - Use bash in src/test/test-network.sh. This ensures we reliably
4622 call chutney's newer tools/test-network.sh when available. Fixes
4623 bug 21562; bugfix on 0.2.9.1-alpha.
4626 - Small fixes to the fuzzing documentation. Closes ticket 21472.
4629 Changes in version 0.2.9.10 - 2017-03-01
4630 Tor 0.2.9.10 backports a security fix from later Tor release. It also
4631 includes fixes for some major issues affecting directory authorities,
4632 LibreSSL compatibility, and IPv6 correctness.
4634 The Tor 0.2.9.x release series is now marked as a long-term-support
4635 series. We intend to backport security fixes to 0.2.9.x until at
4636 least January of 2020.
4638 o Major bugfixes (directory authority, 0.3.0.3-alpha):
4639 - During voting, when marking a relay as a probable sybil, do not
4640 clear its BadExit flag: sybils can still be bad in other ways
4641 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4644 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
4645 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4646 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4647 exit policy rejects that port on more than an IPv6 /16 of
4648 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4649 which rejected a relay's own IPv6 address by default. Fixes bug
4650 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4652 o Major bugfixes (parsing, also in 0.3.0.4-rc):
4653 - Fix an integer underflow bug when comparing malformed Tor
4654 versions. This bug could crash Tor when built with
4655 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4656 0.2.9.8, which were built with -ftrapv by default. In other cases
4657 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4658 on 0.0.8pre1. Found by OSS-Fuzz.
4660 o Minor features (directory authorities, also in 0.3.0.4-rc):
4661 - Directory authorities now reject descriptors that claim to be
4662 malformed versions of Tor. Helps prevent exploitation of
4664 - Reject version numbers with components that exceed INT32_MAX.
4665 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
4666 Fixes bug 21450; bugfix on 0.0.8pre1.
4668 o Minor features (geoip):
4669 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4672 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
4673 - Autoconf now checks to determine if OpenSSL structures are opaque,
4674 instead of explicitly checking for OpenSSL version numbers. Part
4676 - Support building with recent LibreSSL code that uses opaque
4677 structures. Closes ticket 21359.
4679 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
4680 - Repair a couple of (unreachable or harmless) cases of the risky
4681 comparison-by-subtraction pattern that caused bug 21278.
4683 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
4684 - The tor-resolve command line tool now rejects hostnames over 255
4685 characters in length. Previously, it would silently truncate them,
4686 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4687 Patch by "junglefowl".
4690 Changes in version 0.3.0.3-alpha - 2017-02-03
4691 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
4692 0.3.0.x development series, including some that could cause
4693 authorities to behave badly. There is also a fix for a longstanding
4694 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
4695 includes some smaller features and bugfixes.
4697 The Tor 0.3.0.x release series is now in patch-freeze: no additional
4698 features will be considered for inclusion in 0.3.0.x. We suspect that
4699 some bugs will probably remain, however, and we encourage people to
4702 o Major bugfixes (directory authority):
4703 - During voting, when marking a relay as a probable sybil, do not
4704 clear its BadExit flag: sybils can still be bad in other ways
4705 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4707 - When deciding whether we have just found a router to be reachable,
4708 do not penalize it for not having performed an Ed25519 link
4709 handshake if it does not claim to support an Ed25519 handshake.
4710 Previously, we would treat such relays as non-running. Fixes bug
4711 21107; bugfix on 0.3.0.1-alpha.
4713 o Major bugfixes (entry guards):
4714 - Stop trying to build circuits through entry guards for which we
4715 have no descriptor. Also, stop crashing in the case that we *do*
4716 accidentally try to build a circuit in such a state. Fixes bug
4717 21242; bugfix on 0.3.0.1-alpha.
4719 o Major bugfixes (IPv6 Exits):
4720 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4721 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4722 exit policy rejects that port on more than an IPv6 /16 of
4723 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4724 which rejected a relay's own IPv6 address by default. Fixes bug
4725 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4727 o Minor feature (client):
4728 - Enable IPv6 traffic on the SocksPort by default. To disable this,
4729 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
4731 o Minor feature (fallback scripts):
4732 - Add a check_existing mode to updateFallbackDirs.py, which checks
4733 if fallbacks in the hard-coded list are working. Closes ticket
4734 20174. Patch by haxxpop.
4736 o Minor features (ciphersuite selection):
4737 - Clients now advertise a list of ciphersuites closer to the ones
4738 preferred by Firefox. Closes part of ticket 15426.
4739 - Allow relays to accept a wider range of ciphersuites, including
4740 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
4742 o Minor features (controller, configuration):
4743 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
4744 and so on, now comes with a __*Port variant that will not be saved
4745 to the torrc file by the controller's SAVECONF command. This
4746 change allows TorBrowser to set up a single-use domain socket for
4747 each time it launches Tor. Closes ticket 20956.
4748 - The GETCONF command can now query options that may only be
4749 meaningful in context-sensitive lists. This allows the controller
4750 to query the mixed SocksPort/__SocksPort style options introduced
4751 in feature 20956. Implements ticket 21300.
4753 o Minor features (portability, compilation):
4754 - Autoconf now checks to determine if OpenSSL structures are opaque,
4755 instead of explicitly checking for OpenSSL version numbers. Part
4757 - Support building with recent LibreSSL code that uses opaque
4758 structures. Closes ticket 21359.
4760 o Minor features (relay):
4761 - We now allow separation of exit and relay traffic to different
4762 source IP addresses, using the OutboundBindAddressExit and
4763 OutboundBindAddressOR options respectively. Closes ticket 17975.
4764 Written by Michael Sonntag.
4766 o Minor bugfix (logging):
4767 - Don't recommend the use of Tor2web in non-anonymous mode.
4768 Recommending Tor2web is a bad idea because the client loses all
4769 anonymity. Tor2web should only be used in specific cases by users
4770 who *know* and understand the issues. Fixes bug 21294; bugfix
4773 o Minor bugfixes (client):
4774 - Always recover from failures in extend_info_from_node(), in an
4775 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
4776 bugfix on 0.2.3.1-alpha.
4778 o Minor bugfixes (client, entry guards):
4779 - Fix a bug warning (with backtrace) when we fail a channel that
4780 circuits to fallback directories on it. Fixes bug 21128; bugfix
4782 - Fix a spurious bug warning (with backtrace) when removing an
4783 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
4784 - Fix a bug of the new guard algorithm where tor could stall for up
4785 to 10 minutes before retrying a guard after a long period of no
4786 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
4787 - Do not try to build circuits until we have descriptors for our
4788 primary entry guards. Related to fix for bug 21242.
4790 o Minor bugfixes (configure, autoconf):
4791 - Rename the configure option --enable-expensive-hardening to
4792 --enable-fragile-hardening. Expensive hardening makes the tor
4793 daemon abort when some kinds of issues are detected. Thus, it
4794 makes tor more at risk of remote crashes but safer against RCE or
4795 heartbleed bug category. We now try to explain this issue in a
4796 message from the configure script. Fixes bug 21290; bugfix
4799 o Minor bugfixes (controller):
4800 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
4801 20824; bugfix on 0.3.0.1-alpha.
4803 o Minor bugfixes (hidden service):
4804 - Clean up the code for expiring intro points with no associated
4805 circuits. It was causing, rarely, a service with some expiring
4806 introduction points to not open enough additional introduction
4807 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
4808 - Stop setting the torrc option HiddenServiceStatistics to "0" just
4809 because we're not a bridge or relay. Instead, we preserve whatever
4810 value the user set (or didn't set). Fixes bug 21150; bugfix
4812 - Resolve two possible underflows which could lead to creating and
4813 closing a lot of introduction point circuits in a non-stop loop.
4814 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
4816 o Minor bugfixes (portability):
4817 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
4818 It is supported by OpenBSD itself, and also by most OpenBSD
4819 variants (such as Bitrig). Fixes bug 20980; bugfix
4821 - When mapping a file of length greater than SIZE_MAX, do not
4822 silently truncate its contents. This issue could occur on 32 bit
4823 systems with large file support and files which are larger than 4
4824 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
4826 o Minor bugfixes (tor-resolve):
4827 - The tor-resolve command line tool now rejects hostnames over 255
4828 characters in length. Previously, it would silently truncate them,
4829 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4830 Patch by "junglefowl".
4832 o Minor bugfixes (Windows services):
4833 - Be sure to initialize the monotonic time subsystem before using
4834 it, even when running as an NT service. Fixes bug 21356; bugfix
4838 Changes in version 0.3.0.2-alpha - 2017-01-23
4839 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
4840 cause relays and clients to crash, even if they were not built with
4841 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4842 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4843 version should upgrade.
4845 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
4846 time-to-live values, makes directory authorities enforce the 1-to-1
4847 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
4848 client-side onion service reachability bug, does better at selecting
4849 the set of fallback directories, and more.
4851 o Major bugfixes (security, also in 0.2.9.9):
4852 - Downgrade the "-ftrapv" option from "always on" to "only on when
4853 --enable-expensive-hardening is provided." This hardening option, like
4854 others, can turn survivable bugs into crashes--and having it on by
4855 default made a (relatively harmless) integer overflow bug into a
4856 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
4859 o Major features (security):
4860 - Change the algorithm used to decide DNS TTLs on client and server
4861 side, to better resist DNS-based correlation attacks like the
4862 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4863 Feamster. Now relays only return one of two possible DNS TTL
4864 values, and clients are willing to believe DNS TTL values up to 3
4865 hours long. Closes ticket 19769.
4867 o Major features (directory authority, security):
4868 - The default for AuthDirPinKeys is now 1: directory authorities
4869 will reject relays where the RSA identity key matches a previously
4870 seen value, but the Ed25519 key has changed. Closes ticket 18319.
4872 o Major bugfixes (client, guard, crash):
4873 - In circuit_get_global_origin_list(), return the actual list of
4874 origin circuits. The previous version of this code returned the
4875 list of all the circuits, and could have caused strange bugs,
4876 including possible crashes. Fixes bug 21118; bugfix
4879 o Major bugfixes (client, onion service, also in 0.2.9.9):
4880 - Fix a client-side onion service reachability bug, where multiple
4881 socks requests to an onion service (or a single slow request)
4882 could cause us to mistakenly mark some of the service's
4883 introduction points as failed, and we cache that failure so
4884 eventually we run out and can't reach the service. Also resolves a
4885 mysterious "Remote server sent bogus reason code 65021" log
4886 warning. The bug was introduced in ticket 17218, where we tried to
4887 remember the circuit end reason as a uint16_t, which mangled
4888 negative values. Partially fixes bug 21056 and fixes bug 20307;
4889 bugfix on 0.2.8.1-alpha.
4891 o Major bugfixes (DNS):
4892 - Fix a bug that prevented exit nodes from caching DNS records for
4893 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4895 o Minor features (controller):
4896 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
4897 shared-random values to the controller. Closes ticket 19925.
4899 o Minor features (entry guards):
4900 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
4901 break regression tests.
4902 - Require UseEntryGuards when UseBridges is set, in order to make
4903 sure bridges aren't bypassed. Resolves ticket 20502.
4905 o Minor features (fallback directories):
4906 - Select 200 fallback directories for each release. Closes
4908 - Allow 3 fallback relays per operator, which is safe now that we
4909 are choosing 200 fallback relays. Closes ticket 20912.
4910 - Exclude relays affected by bug 20499 from the fallback list.
4911 Exclude relays from the fallback list if they are running versions
4912 known to be affected by bug 20499, or if in our tests they deliver
4913 a stale consensus (i.e. one that expired more than 24 hours ago).
4914 Closes ticket 20539.
4915 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
4917 - Require fallback directories to have the same address and port for
4918 7 days (now that we have enough relays with this stability).
4919 Relays whose OnionOO stability timer is reset on restart by bug
4920 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
4921 this issue. Closes ticket 20880; maintains short-term fix
4923 - Require fallbacks to have flags for 90% of the time (weighted
4924 decaying average), rather than 95%. This allows at least 73% of
4925 clients to bootstrap in the first 5 seconds without contacting an
4926 authority. Part of ticket 18828.
4927 - Annotate updateFallbackDirs.py with the bandwidth and consensus
4928 weight for each candidate fallback. Closes ticket 20878.
4929 - Make it easier to change the output sort order of fallbacks.
4930 Closes ticket 20822.
4931 - Display the relay fingerprint when downloading consensuses from
4932 fallbacks. Closes ticket 20908.
4934 o Minor features (geoip, also in 0.2.9.9):
4935 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4938 o Minor features (next-gen onion service directories):
4939 - Remove the "EnableOnionServicesV3" consensus parameter that we
4940 introduced in 0.3.0.1-alpha: relays are now always willing to act
4941 as v3 onion service directories. Resolves ticket 19899.
4943 o Minor features (linting):
4944 - Enhance the changes file linter to warn on Tor versions that are
4945 prefixed with "tor-". Closes ticket 21096.
4947 o Minor features (logging):
4948 - In several places, describe unset ed25519 keys as "<unset>",
4949 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
4951 o Minor bugfix (control protocol):
4952 - The reply to a "GETINFO config/names" request via the control
4953 protocol now spells the type "Dependent" correctly. This is a
4954 breaking change in the control protocol. (The field seems to be
4955 ignored by the most common known controllers.) Fixes bug 18146;
4956 bugfix on 0.1.1.4-alpha.
4958 o Minor bugfixes (bug resilience):
4959 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
4960 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
4961 Hans Jerry Illikainen.
4963 o Minor bugfixes (build):
4964 - Replace obsolete Autoconf macros with their modern equivalent and
4965 prevent similar issues in the future. Fixes bug 20990; bugfix
4968 o Minor bugfixes (client, guards):
4969 - Fix bug where Tor would think that there are circuits waiting for
4970 better guards even though those circuits have been freed. Fixes
4971 bug 21142; bugfix on 0.3.0.1-alpha.
4973 o Minor bugfixes (config):
4974 - Don't assert on startup when trying to get the options list and
4975 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
4976 options so of course they aren't ready yet. Fixes bug 21062;
4977 bugfix on 0.2.9.3-alpha.
4979 o Minor bugfixes (controller):
4980 - Make the GETINFO interface for inquiring about entry guards
4981 support the new guards backend. Fixes bug 20823; bugfix
4984 o Minor bugfixes (dead code):
4985 - Remove a redundant check for PidFile changes at runtime in
4986 options_transition_allowed(): this check is already performed
4987 regardless of whether the sandbox is active. Fixes bug 21123;
4988 bugfix on 0.2.5.4-alpha.
4990 o Minor bugfixes (documentation):
4991 - Update the tor manual page to document every option that can not
4992 be changed while tor is running. Fixes bug 21122.
4994 o Minor bugfixes (fallback directories):
4995 - Stop failing when a relay has no uptime data in
4996 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
4997 - Avoid checking fallback candidates' DirPorts if they are down in
4998 OnionOO. When a relay operator has multiple relays, this
4999 prioritizes relays that are up over relays that are down. Fixes
5000 bug 20926; bugfix on 0.2.8.3-alpha.
5001 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
5002 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
5004 o Minor bugfixes (guards, bootstrapping):
5005 - When connecting to a directory guard during bootstrap, do not mark
5006 the guard as successful until we receive a good-looking directory
5007 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
5009 o Minor bugfixes (onion services):
5010 - Fix the config reload pruning of old vs new services so it
5011 actually works when both ephemeral and non-ephemeral services are
5012 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
5013 - Allow the number of introduction points to be as low as 0, rather
5014 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
5016 o Minor bugfixes (IPv6):
5017 - Make IPv6-using clients try harder to find an IPv6 directory
5018 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
5019 - When IPv6 addresses have not been downloaded yet (microdesc
5020 consensus documents don't list relay IPv6 addresses), use hard-
5021 coded addresses for authorities, fallbacks, and configured
5022 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
5023 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
5025 o Minor bugfixes (memory leaks):
5026 - Fix a memory leak when configuring hidden services. Fixes bug
5027 20987; bugfix on 0.3.0.1-alpha.
5029 o Minor bugfixes (portability, also in 0.2.9.9):
5030 - Avoid crashing when Tor is built using headers that contain
5031 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5032 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5034 - Fix Libevent detection on platforms without Libevent 1 headers
5035 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5037 o Minor bugfixes (relay):
5038 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
5039 initializing the keys would reset the DataDirectory to 0700
5040 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
5041 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
5043 o Minor bugfixes (testing):
5044 - Remove undefined behavior from the backtrace generator by removing
5045 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
5047 o Minor bugfixes (unit tests):
5048 - Allow the unit tests to pass even when DNS lookups of bogus
5049 addresses do not fail as expected. Fixes bug 20862 and 20863;
5050 bugfix on unit tests introduced in 0.2.8.1-alpha
5051 through 0.2.9.4-alpha.
5053 o Code simplification and refactoring:
5054 - Refactor code to manipulate global_origin_circuit_list into
5055 separate functions. Closes ticket 20921.
5057 o Documentation (formatting):
5058 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
5059 blocks were incorrectly appearing. Closes ticket 20885.
5061 o Documentation (man page):
5062 - Clarify many options in tor.1 and add some min/max values for
5063 HiddenService options. Closes ticket 21058.
5066 Changes in version 0.2.9.9 - 2017-01-23
5067 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
5068 cause relays and clients to crash, even if they were not built with
5069 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5070 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5071 version should upgrade.
5073 This release also resolves a client-side onion service reachability
5074 bug, and resolves a pair of small portability issues.
5076 o Major bugfixes (security):
5077 - Downgrade the "-ftrapv" option from "always on" to "only on when
5078 --enable-expensive-hardening is provided." This hardening option,
5079 like others, can turn survivable bugs into crashes -- and having
5080 it on by default made a (relatively harmless) integer overflow bug
5081 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
5082 bugfix on 0.2.9.1-alpha.
5084 o Major bugfixes (client, onion service):
5085 - Fix a client-side onion service reachability bug, where multiple
5086 socks requests to an onion service (or a single slow request)
5087 could cause us to mistakenly mark some of the service's
5088 introduction points as failed, and we cache that failure so
5089 eventually we run out and can't reach the service. Also resolves a
5090 mysterious "Remote server sent bogus reason code 65021" log
5091 warning. The bug was introduced in ticket 17218, where we tried to
5092 remember the circuit end reason as a uint16_t, which mangled
5093 negative values. Partially fixes bug 21056 and fixes bug 20307;
5094 bugfix on 0.2.8.1-alpha.
5096 o Minor features (geoip):
5097 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5100 o Minor bugfixes (portability):
5101 - Avoid crashing when Tor is built using headers that contain
5102 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5103 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5105 - Fix Libevent detection on platforms without Libevent 1 headers
5106 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5109 Changes in version 0.3.0.1-alpha - 2016-12-19
5110 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
5111 series. It strengthens Tor's link and circuit handshakes by
5112 identifying relays by their Ed25519 keys, improves the algorithm that
5113 clients use to choose and maintain their list of guards, and includes
5114 additional backend support for the next-generation hidden service
5115 design. It also contains numerous other small features and
5116 improvements to security, correctness, and performance.
5118 Below are the changes since 0.2.9.8.
5120 o Major features (guard selection algorithm):
5121 - Tor's guard selection algorithm has been redesigned from the
5122 ground up, to better support unreliable networks and restrictive
5123 sets of entry nodes, and to better resist guard-capture attacks by
5124 hostile local networks. Implements proposal 271; closes
5127 o Major features (next-generation hidden services):
5128 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
5129 prop224 aka "Next Generation Hidden Services". Service and clients
5130 don't use this functionality yet. Closes ticket 19043. Based on
5131 initial code by Alec Heifetz.
5132 - Relays now support the HSDir version 3 protocol, so that they can
5133 can store and serve v3 descriptors. This is part of the next-
5134 generation onion service work detailed in proposal 224. Closes
5137 o Major features (protocol, ed25519 identity keys):
5138 - Relays now use Ed25519 to prove their Ed25519 identities and to
5139 one another, and to clients. This algorithm is faster and more
5140 secure than the RSA-based handshake we've been doing until now.
5141 Implements the second big part of proposal 220; Closes
5143 - Clients now support including Ed25519 identity keys in the EXTEND2
5144 cells they generate. By default, this is controlled by a consensus
5145 parameter, currently disabled. You can turn this feature on for
5146 testing by setting ExtendByEd25519ID in your configuration. This
5147 might make your traffic appear different than the traffic
5148 generated by other users, however. Implements part of ticket
5149 15056; part of proposal 220.
5150 - Relays now understand requests to extend to other relays by their
5151 Ed25519 identity keys. When an Ed25519 identity key is included in
5152 an EXTEND2 cell, the relay will only extend the circuit if the
5153 other relay can prove ownership of that identity. Implements part
5154 of ticket 15056; part of proposal 220.
5156 o Major bugfixes (scheduler):
5157 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
5158 caused the channel scheduler to behave more or less randomly,
5159 rather than preferring channels with higher-priority circuits.
5160 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
5162 o Minor features (controller):
5163 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
5164 rather than "unrecognized." Closes ticket 20389; patch from
5167 o Minor features (diagnostic, directory client):
5168 - Warn when we find an unexpected inconsistency in directory
5169 download status objects. Prevents some negative consequences of
5172 o Minor features (directory authority):
5173 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
5174 default) to control whether authorities should try to probe relays
5175 by their Ed25519 link keys. This option will go away in a few
5176 releases--unless we encounter major trouble in our ed25519 link
5177 protocol rollout, in which case it will serve as a safety option.
5179 o Minor features (directory cache):
5180 - Relays and bridges will now refuse to serve the consensus they
5181 have if they know it is too old for a client to use. Closes
5184 o Minor features (ed25519 link handshake):
5185 - Advertise support for the ed25519 link handshake using the
5186 subprotocol-versions mechanism, so that clients can tell which
5187 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
5189 o Minor features (fingerprinting resistance, authentication):
5190 - Extend the length of RSA keys used for TLS link authentication to
5191 2048 bits. (These weren't used for forward secrecy; for forward
5192 secrecy, we used P256.) Closes ticket 13752.
5194 o Minor features (infrastructure):
5195 - Implement smartlist_add_strdup() function. Replaces the use of
5196 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
5198 o Minor bugfixes (client):
5199 - When clients that use bridges start up with a cached consensus on
5200 disk, they were ignoring it and downloading a new one. Now they
5201 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
5203 o Minor bugfixes (configuration):
5204 - Accept non-space whitespace characters after the severity level in
5205 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
5206 - Support "TByte" and "TBytes" units in options given in bytes.
5207 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
5208 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
5210 o Minor bugfixes (consensus weight):
5211 - Add new consensus method that initializes bw weights to 1 instead
5212 of 0. This prevents a zero weight from making it all the way to
5213 the end (happens in small testing networks) and causing an error.
5214 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
5216 o Minor bugfixes (descriptors):
5217 - Correctly recognise downloaded full descriptors as valid, even
5218 when using microdescriptors as circuits. This affects clients with
5219 FetchUselessDescriptors set, and may affect directory authorities.
5220 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
5222 o Minor bugfixes (directory system):
5223 - Download all consensus flavors, descriptors, and authority
5224 certificates when FetchUselessDescriptors is set, regardless of
5225 whether tor is a directory cache or not. Fixes bug 20667; bugfix
5226 on all recent tor versions.
5227 - Bridges and relays now use microdescriptors (like clients do)
5228 rather than old-style router descriptors. Now bridges will blend
5229 in with clients in terms of the circuits they build. Fixes bug
5230 6769; bugfix on 0.2.3.2-alpha.
5232 o Minor bugfixes (ed25519 certificates):
5233 - Correctly interpret ed25519 certificates that would expire some
5234 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
5236 o Minor bugfixes (hidden services):
5237 - Stop ignoring misconfigured hidden services. Instead, refuse to
5238 start tor until the misconfigurations have been corrected. Fixes
5239 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
5242 o Minor bugfixes (memory leak at exit):
5243 - Fix a small harmless memory leak at exit of the previously unused
5244 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
5247 o Minor bugfixes (util):
5248 - When finishing writing a file to disk, if we were about to replace
5249 the file with the temporary file created before and we fail to
5250 replace it, remove the temporary file so it doesn't stay on disk.
5251 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
5253 o Minor bugfixes (Windows):
5254 - Check for getpagesize before using it to mmap files. This fixes
5255 compilation in some MinGW environments. Fixes bug 20530; bugfix on
5256 0.1.2.1-alpha. Reported by "ice".
5258 o Code simplification and refactoring:
5259 - Abolish all global guard context in entrynodes.c; replace with new
5260 guard_selection_t structure as preparation for proposal 271.
5261 Closes ticket 19858.
5262 - Introduce rend_service_is_ephemeral() that tells if given onion
5263 service is ephemeral. Replace unclear NULL-checkings for service
5264 directory with this function. Closes ticket 20526.
5265 - Extract magic numbers in circuituse.c into defined variables.
5266 - Refactor circuit_is_available_for_use to remove unnecessary check.
5267 - Refactor circuit_predict_and_launch_new for readability and
5268 testability. Closes ticket 18873.
5269 - Refactor large if statement in purpose_needs_anonymity to use
5270 switch statement instead. Closes part of ticket 20077.
5271 - Refactor the hashing API to return negative values for errors, as
5272 is done as throughout the codebase. Closes ticket 20717.
5273 - Remove data structures that were used to index or_connection
5274 objects by their RSA identity digests. These structures are fully
5275 redundant with the similar structures used in the
5276 channel abstraction.
5277 - Remove duplicate code in the channel_write_*cell() functions.
5278 Closes ticket 13827; patch from Pingl.
5279 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
5280 use only purpose_needs_anonymity. Closes part of ticket 20077.
5281 - The code to generate and parse EXTEND and EXTEND2 cells has been
5282 replaced with code automatically generated by the
5286 - Include the "TBits" unit in Tor's man page. Fixes part of bug
5287 20622; bugfix on tor-0.2.5.1-alpha.
5288 - Change '1' to 'weight_scale' in consensus bw weights calculation
5289 comments, as that is reality. Closes ticket 20273. Patch
5291 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
5292 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
5293 on tor-0.2.5.6-alpha.
5294 - Stop the man page from incorrectly stating that HiddenServiceDir
5295 must already exist. Fixes 20486.
5296 - Clarify that when ClientRejectInternalAddresses is enabled (which
5297 is the default), multicast DNS hostnames for machines on the local
5298 network (of the form *.local) are also rejected. Closes
5302 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
5303 limit for relays running on a single IP applies to authority IP
5304 addresses as well as to non-authority IP addresses. Closes
5306 - The UseDirectoryGuards torrc option no longer exists: all users
5307 that use entry guards will also use directory guards. Related to
5308 proposal 271; implements part of ticket 20831.
5311 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
5312 from "overcaffeinated".
5313 - Perform the coding style checks when running the tests and fail
5314 when coding style violations are found. Closes ticket 5500.
5315 - Add tests for networkstatus_compute_bw_weights_v10.
5316 - Add unit tests circuit_predict_and_launch_new.
5317 - Extract dummy_origin_circuit_new so it can be used by other
5321 Changes in version 0.2.8.12 - 2016-12-19
5322 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
5323 below) where Tor clients could crash when attempting to visit a
5324 hostile hidden service. Clients are recommended to upgrade as packages
5325 become available for their systems.
5327 It also includes an updated list of fallback directories, backported
5330 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
5331 backported to 0.2.8 in the future.
5333 o Major bugfixes (parsing, security, backported from 0.2.9.8):
5334 - Fix a bug in parsing that could cause clients to read a single
5335 byte past the end of an allocated region. This bug could be used
5336 to cause hardened clients (built with --enable-expensive-hardening)
5337 to crash if they tried to visit a hostile hidden service. Non-
5338 hardened clients are only affected depending on the details of
5339 their platform's memory allocator. Fixes bug 21018; bugfix on
5340 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5341 2016-12-002 and as CVE-2016-1254.
5343 o Minor features (fallback directory list, backported from 0.2.9.8):
5344 - Replace the 81 remaining fallbacks of the 100 originally
5345 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5346 fallbacks (123 new, 54 existing, 27 removed) generated in December
5347 2016. Resolves ticket 20170.
5349 o Minor features (geoip, backported from 0.2.9.7-rc):
5350 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
5354 Changes in version 0.2.9.8 - 2016-12-19
5355 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
5357 The Tor 0.2.9 series makes mandatory a number of security features
5358 that were formerly optional. It includes support for a new shared-
5359 randomness protocol that will form the basis for next generation
5360 hidden services, includes a single-hop hidden service mode for
5361 optimizing .onion services that don't actually want to be hidden,
5362 tries harder not to overload the directory authorities with excessive
5363 downloads, and supports a better protocol versioning scheme for
5364 improved compatibility with other implementations of the Tor protocol.
5366 And of course, there are numerous other bugfixes and improvements.
5368 This release also includes a fix for a medium-severity issue (bug
5369 21018 below) where Tor clients could crash when attempting to visit a
5370 hostile hidden service. Clients are recommended to upgrade as packages
5371 become available for their systems.
5373 Below are the changes since 0.2.9.7-rc. For a list of all changes
5374 since 0.2.8, see the ReleaseNotes file.
5376 o Major bugfixes (parsing, security):
5377 - Fix a bug in parsing that could cause clients to read a single
5378 byte past the end of an allocated region. This bug could be used
5379 to cause hardened clients (built with --enable-expensive-hardening)
5380 to crash if they tried to visit a hostile hidden service. Non-
5381 hardened clients are only affected depending on the details of
5382 their platform's memory allocator. Fixes bug 21018; bugfix on
5383 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5384 2016-12-002 and as CVE-2016-1254.
5386 o Minor features (fallback directory list):
5387 - Replace the 81 remaining fallbacks of the 100 originally
5388 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5389 fallbacks (123 new, 54 existing, 27 removed) generated in December
5390 2016. Resolves ticket 20170.
5393 Changes in version 0.2.9.7-rc - 2016-12-12
5394 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
5395 including a few that had prevented tests from passing on
5398 o Minor features (geoip):
5399 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
5402 o Minor bugfix (build):
5403 - The current Git revision when building from a local repository is
5404 now detected correctly when using git worktrees. Fixes bug 20492;
5405 bugfix on 0.2.3.9-alpha.
5407 o Minor bugfixes (directory authority):
5408 - When computing old Tor protocol line version in protover, we were
5409 looking at 0.2.7.5 twice instead of a specific case for
5410 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
5412 o Minor bugfixes (download scheduling):
5413 - Resolve a "bug" warning when considering a download schedule whose
5414 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
5416 o Minor bugfixes (logging):
5417 - Downgrade a harmless log message about the
5418 pending_entry_connections list from "warn" to "info". Mitigates
5421 o Minor bugfixes (memory leak):
5422 - Fix a small memory leak when receiving AF_UNIX connections on a
5423 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
5424 - When moving a signed descriptor object from a source to an
5425 existing destination, free the allocated memory inside that
5426 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
5428 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
5429 - Fix a memory leak and use-after-free error when removing entries
5430 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
5431 0.2.5.5-alpha. Patch from "cypherpunks".
5433 o Minor bugfixes (portability):
5434 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
5435 Fixes bug 20935; bugfix on 0.2.9.6-rc.
5437 o Minor bugfixes (unit tests):
5438 - Stop expecting NetBSD unit tests to report success for ipfw. Part
5439 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
5440 - Fix tolerances in unit tests for monotonic time comparisons
5441 between nanoseconds and microseconds. Previously, we accepted a 10
5442 us difference only, which is not realistic on every platform's
5443 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
5444 - Remove a double-free in the single onion service unit test. Stop
5445 ignoring a return value. Make future changes less error-prone.
5446 Fixes bug 20864; bugfix on 0.2.9.6-rc.
5449 Changes in version 0.2.8.11 - 2016-12-08
5450 Tor 0.2.8.11 backports fixes for additional portability issues that
5451 could prevent Tor from building correctly on OSX Sierra, or with
5452 OpenSSL 1.1. Affected users should upgrade; others can safely stay
5455 o Minor bugfixes (portability):
5456 - Avoid compilation errors when building on OSX Sierra. Sierra began
5457 to support the getentropy() and clock_gettime() APIs, but created
5458 a few problems in doing so. Tor 0.2.9 has a more thorough set of
5459 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
5460 monotonic time interfaces. Fixes bug 20865. Bugfix
5463 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5464 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
5465 architectures. Closes ticket 20588.
5468 Changes in version 0.2.8.10 - 2016-12-02
5469 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
5470 unusable after they left standby mode. It also backports fixes for
5471 a few portability issues and a small but problematic memory leak.
5473 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
5474 - When Tor leaves standby because of a new application request, open
5475 circuits as needed to serve that request. Previously, we would
5476 potentially wait a very long time. Fixes part of bug 19969; bugfix
5479 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
5480 - Clients now respond to new application stream requests immediately
5481 when they arrive, rather than waiting up to one second before
5482 starting to handle them. Fixes part of bug 19969; bugfix
5485 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
5486 - Work around a bug in the OSX 10.12 SDK that would prevent us from
5487 successfully targeting earlier versions of OSX. Resolves
5490 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5491 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
5492 20551; bugfix on 0.2.1.1-alpha.
5494 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
5495 - Work around a memory leak in OpenSSL 1.1 when encoding public
5496 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
5498 o Minor features (geoip):
5499 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
5502 Changes in version 0.2.9.6-rc - 2016-12-02
5503 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
5504 version. We hope that it will be ready to become stable soon, and we
5505 encourage everyone to test this release. If no showstopper bugs are
5506 found here, the next 0.2.9 release will be stable.
5508 o Major bugfixes (relay, resolver, logging):
5509 - For relays that don't know their own address, avoid attempting a
5510 local hostname resolve for each descriptor we download. This
5511 will cut down on the number of "Success: chose address 'x.x.x.x'"
5512 log lines, and also avoid confusing clock jumps if the resolver
5513 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
5515 o Minor bugfixes (client, fascistfirewall):
5516 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
5517 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
5519 o Minor bugfixes (hidden services):
5520 - Stop ignoring the anonymity status of saved keys for hidden
5521 services and single onion services when first starting tor.
5522 Instead, refuse to start tor if any hidden service key has been
5523 used in a different hidden service anonymity mode. Fixes bug
5524 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
5526 o Minor bugfixes (portability):
5527 - Work around a bug in the OSX 10.12 SDK that would prevent us from
5528 successfully targeting earlier versions of OSX. Resolves
5530 - Run correctly when built on Windows build environments that
5531 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
5533 o Minor bugfixes (single onion services, Tor2web):
5534 - Stop complaining about long-term one-hop circuits deliberately
5535 created by single onion services and Tor2web. These log messages
5536 are intended to diagnose issue 8387, which relates to circuits
5537 hanging around forever for no reason. Fixes bug 20613; bugfix on
5538 0.2.9.1-alpha. Reported by "pastly".
5540 o Minor bugfixes (unit tests):
5541 - Stop spurious failures in the local interface address discovery
5542 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
5546 - Correct the minimum bandwidth value in torrc.sample, and queue a
5547 corresponding change for torrc.minimal. Closes ticket 20085.
5550 Changes in version 0.2.9.5-alpha - 2016-11-08
5551 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
5552 version. We believe one or two probably remain, and we encourage
5553 everyone to test this release.
5555 o Major bugfixes (client performance):
5556 - Clients now respond to new application stream requests immediately
5557 when they arrive, rather than waiting up to one second before
5558 starting to handle them. Fixes part of bug 19969; bugfix
5561 o Major bugfixes (client reliability):
5562 - When Tor leaves standby because of a new application request, open
5563 circuits as needed to serve that request. Previously, we would
5564 potentially wait a very long time. Fixes part of bug 19969; bugfix
5567 o Major bugfixes (download scheduling):
5568 - When using an exponential backoff schedule, do not give up on
5569 downloading just because we have failed a bunch of times. Since
5570 each delay is longer than the last, retrying indefinitely won't
5571 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
5572 - If a consensus expires while we are waiting for certificates to
5573 download, stop waiting for certificates.
5574 - If we stop waiting for certificates less than a minute after we
5575 started downloading them, do not consider the certificate download
5576 failure a separate failure. Fixes bug 20533; bugfix
5578 - Remove the maximum delay on exponential-backoff scheduling. Since
5579 we now allow an infinite number of failures (see ticket 20536), we
5580 must now allow the time to grow longer on each failure. Fixes part
5581 of bug 20534; bugfix on 0.2.9.1-alpha.
5582 - Make our initial download delays closer to those from 0.2.8. Fixes
5583 another part of bug 20534; bugfix on 0.2.9.1-alpha.
5584 - When determining when to download a directory object, handle times
5585 after 2038 if the operating system supports them. (Someday this
5586 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
5587 - When using exponential backoff in test networks, use a lower
5588 exponent, so the delays do not vary as much. This helps test
5589 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
5591 o Minor features (geoip):
5592 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
5595 o Minor bugfixes (client directory scheduling):
5596 - Treat "relay too busy to answer request" as a failed request and a
5597 reason to back off on our retry frequency. This is safe now that
5598 exponential backoffs retry indefinitely, and avoids a bug where we
5599 would reset our download schedule erroneously. Fixes bug 20593;
5600 bugfix on 0.2.9.1-alpha.
5602 o Minor bugfixes (client, logging):
5603 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
5604 assume all nodes support EXTEND2. Use ntor whenever a key is
5605 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
5606 - On DNSPort, stop logging a BUG warning on a failed hostname
5607 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
5609 o Minor bugfixes (hidden services):
5610 - When configuring hidden services, check every hidden service
5611 directory's permissions. Previously, we only checked the last
5612 hidden service. Fixes bug 20529; bugfix the work to fix 13942
5615 o Minor bugfixes (portability):
5616 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
5617 architectures. Closes ticket 20588.
5618 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
5619 removed the ECDH ciphers which caused the tests to fail on
5620 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
5621 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
5622 20551; bugfix on 0.2.1.1-alpha.
5624 o Minor bugfixes (relay bootstrap):
5625 - Ensure relays don't make multiple connections during bootstrap.
5626 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
5628 o Minor bugfixes (relay):
5629 - Work around a memory leak in OpenSSL 1.1 when encoding public
5630 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
5631 - Avoid a small memory leak when informing worker threads about
5632 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
5633 - Do not try to parallelize workers more than 16x without the user
5634 explicitly configuring us to do so, even if we do detect more than
5635 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5637 o Minor bugfixes (single onion services):
5638 - Start correctly when creating a single onion service in a
5639 directory that did not previously exist. Fixes bug 20484; bugfix
5642 o Minor bugfixes (testing):
5643 - Avoid a unit test failure on systems with over 16 detectable CPU
5644 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5647 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
5648 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
5649 - Module-level documentation for several more modules. Closes
5650 tickets 19287 and 19290.
5653 Changes in version 0.2.8.9 - 2016-10-17
5654 Tor 0.2.8.9 backports a fix for a security hole in previous versions
5655 of Tor that would allow a remote attacker to crash a Tor client,
5656 hidden service, relay, or authority. All Tor users should upgrade to
5657 this version, or to 0.2.9.4-alpha. Patches will be released for older
5660 o Major features (security fixes, also in 0.2.9.4-alpha):
5661 - Prevent a class of security bugs caused by treating the contents
5662 of a buffer chunk as if they were a NUL-terminated string. At
5663 least one such bug seems to be present in all currently used
5664 versions of Tor, and would allow an attacker to remotely crash
5665 most Tor instances, especially those compiled with extra compiler
5666 hardening. With this defense in place, such bugs can't crash Tor,
5667 though we should still fix them as they occur. Closes ticket
5668 20384 (TROVE-2016-10-001).
5670 o Minor features (geoip):
5671 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
5675 Changes in version 0.2.9.4-alpha - 2016-10-17
5676 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
5677 that would allow a remote attacker to crash a Tor client, hidden
5678 service, relay, or authority. All Tor users should upgrade to this
5679 version, or to 0.2.8.9. Patches will be released for older versions
5682 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
5683 previous versions of Tor, including the implementation of a feature to
5684 future- proof the Tor ecosystem against protocol changes, some bug
5685 fixes necessary for Tor Browser to use unix domain sockets correctly,
5686 and several portability improvements. We anticipate that this will be
5687 the last alpha in the Tor 0.2.9 series, and that the next release will
5688 be a release candidate.
5690 o Major features (security fixes):
5691 - Prevent a class of security bugs caused by treating the contents
5692 of a buffer chunk as if they were a NUL-terminated string. At
5693 least one such bug seems to be present in all currently used
5694 versions of Tor, and would allow an attacker to remotely crash
5695 most Tor instances, especially those compiled with extra compiler
5696 hardening. With this defense in place, such bugs can't crash Tor,
5697 though we should still fix them as they occur. Closes ticket
5698 20384 (TROVE-2016-10-001).
5700 o Major features (subprotocol versions):
5701 - Tor directory authorities now vote on a set of recommended
5702 subprotocol versions, and on a set of required subprotocol
5703 versions. Clients and relays that lack support for a _required_
5704 subprotocol version will not start; those that lack support for a
5705 _recommended_ subprotocol version will warn the user to upgrade.
5706 Closes ticket 19958; implements part of proposal 264.
5707 - Tor now uses "subprotocol versions" to indicate compatibility.
5708 Previously, versions of Tor looked at the declared Tor version of
5709 a relay to tell whether they could use a given feature. Now, they
5710 should be able to rely on its declared subprotocol versions. This
5711 change allows compatible implementations of the Tor protocol(s) to
5712 exist without pretending to be 100% bug-compatible with particular
5713 releases of Tor itself. Closes ticket 19958; implements part of
5716 o Minor feature (fallback directories):
5717 - Remove broken fallbacks from the hard-coded fallback directory
5718 list. Closes ticket 20190; patch by teor.
5720 o Minor features (client, directory):
5721 - Since authorities now omit all routers that lack the Running and
5722 Valid flags, we assume that any relay listed in the consensus must
5723 have those flags. Closes ticket 20001; implements part of
5726 o Minor features (compilation, portability):
5727 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
5730 o Minor features (development tools, etags):
5731 - Teach the "make tags" Makefile target how to correctly find
5732 "MOCK_IMPL" function definitions. Patch from nherring; closes
5735 o Minor features (geoip):
5736 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
5739 o Minor features (unix domain sockets):
5740 - When configuring a unix domain socket for a SocksPort,
5741 ControlPort, or Hidden service, you can now wrap the address in
5742 quotes, using C-style escapes inside the quotes. This allows unix
5743 domain socket paths to contain spaces.
5745 o Minor features (virtual addresses):
5746 - Increase the maximum number of bits for the IPv6 virtual network
5747 prefix from 16 to 104. In this way, the condition for address
5748 allocation is less restrictive. Closes ticket 20151; feature
5751 o Minor bugfixes (address discovery):
5752 - Stop reordering IP addresses returned by the OS. This makes it
5753 more likely that Tor will guess the same relay IP address every
5754 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
5755 Reported by René Mayrhofer, patch by "cypherpunks".
5757 o Minor bugfixes (client, unix domain sockets):
5758 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
5759 the client address is meaningless. Fixes bug 20261; bugfix
5762 o Minor bugfixes (compilation, OpenBSD):
5763 - Detect Libevent2 functions correctly on systems that provide
5764 libevent2, but where libevent1 is linked with -levent. Fixes bug
5765 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
5767 o Minor bugfixes (configuration):
5768 - When parsing quoted configuration values from the torrc file,
5769 handle windows line endings correctly. Fixes bug 19167; bugfix on
5770 0.2.0.16-alpha. Patch from "Pingl".
5772 o Minor bugfixes (getpass):
5773 - Defensively fix a non-triggerable heap corruption at do_getpass()
5774 to protect ourselves from mistakes in the future. Fixes bug
5775 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
5778 o Minor bugfixes (hidden service):
5779 - Allow hidden services to run on IPv6 addresses even when the
5780 IPv6Exit option is not set. Fixes bug 18357; bugfix
5784 - Add module-level internal documentation for 36 C files that
5785 previously didn't have a high-level overview. Closes ticket #20385.
5787 o Required libraries:
5788 - When building with OpenSSL, Tor now requires version 1.0.1 or
5789 later. OpenSSL 1.0.0 and earlier are no longer supported by the
5790 OpenSSL team, and should not be used. Closes ticket 20303.
5793 Changes in version 0.2.9.3-alpha - 2016-09-23
5794 Tor 0.2.9.3-alpha adds improved support for entities that want to make
5795 high-performance services available through the Tor .onion mechanism
5796 without themselves receiving anonymity as they host those services. It
5797 also tries harder to ensure that all steps on a circuit are using the
5798 strongest crypto possible, strengthens some TLS properties, and
5799 resolves several bugs -- including a pair of crash bugs from the 0.2.8
5800 series. Anybody running an earlier version of 0.2.9.x should upgrade.
5802 o Major bugfixes (crash, also in 0.2.8.8):
5803 - Fix a complicated crash bug that could affect Tor clients
5804 configured to use bridges when replacing a networkstatus consensus
5805 in which one of their bridges was mentioned. OpenBSD users saw
5806 more crashes here, but all platforms were potentially affected.
5807 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5809 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
5810 - Fix a timing-dependent assertion failure that could occur when we
5811 tried to flush from a circuit after having freed its cells because
5812 of an out-of-memory condition. Fixes bug 20203; bugfix on
5813 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5816 o Major features (circuit building, security):
5817 - Authorities, relays and clients now require ntor keys in all
5818 descriptors, for all hops (except for rare hidden service protocol
5819 cases), for all circuits, and for all other roles. Part of
5821 - Tor authorities, relays, and clients only use ntor, except for
5822 rare cases in the hidden service protocol. Part of ticket 19163.
5824 o Major features (single-hop "hidden" services):
5825 - Add experimental HiddenServiceSingleHopMode and
5826 HiddenServiceNonAnonymousMode options. When both are set to 1,
5827 every hidden service on a Tor instance becomes a non-anonymous
5828 Single Onion Service. Single Onions make one-hop (direct)
5829 connections to their introduction and renzedvous points. One-hop
5830 circuits make Single Onion servers easily locatable, but clients
5831 remain location-anonymous. This is compatible with the existing
5832 hidden service implementation, and works on the current tor
5833 network without any changes to older relays or clients. Implements
5834 proposal 260, completes ticket 17178. Patch by teor and asn.
5836 o Major features (resource management):
5837 - Tor can now notice it is about to run out of sockets, and
5838 preemptively close connections of lower priority. (This feature is
5839 off by default for now, since the current prioritizing method is
5840 yet not mature enough. You can enable it by setting
5841 "DisableOOSCheck 0", but watch out: it might close some sockets
5842 you would rather have it keep.) Closes ticket 18640.
5844 o Major bugfixes (circuit building):
5845 - Hidden service client-to-intro-point and service-to-rendezvous-
5846 point circuits use the TAP key supplied by the protocol, to avoid
5847 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
5849 o Major bugfixes (compilation, OpenBSD):
5850 - Fix a Libevent-detection bug in our autoconf script that would
5851 prevent Tor from linking successfully on OpenBSD. Patch from
5852 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
5854 o Major bugfixes (hidden services):
5855 - Clients now require hidden services to include the TAP keys for
5856 their intro points in the hidden service descriptor. This prevents
5857 an inadvertent upgrade to ntor, which a malicious hidden service
5858 could use to distinguish clients by consensus version. Fixes bug
5859 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
5861 o Minor features (security, TLS):
5862 - Servers no longer support clients that without AES ciphersuites.
5863 (3DES is no longer considered an acceptable cipher.) We believe
5864 that no such Tor clients currently exist, since Tor has required
5865 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
5867 o Minor feature (fallback directories):
5868 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
5869 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
5870 2016. Closes ticket 20190; patch by teor.
5872 o Minor features (geoip, also in 0.2.8.8):
5873 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5876 o Minor feature (port flags):
5877 - Add new flags to the *Port options to finer control over which
5878 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
5879 and the synthetic flag OnionTrafficOnly, which is equivalent to
5880 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
5881 18693; patch by "teor".
5883 o Minor features (directory authority):
5884 - After voting, if the authorities decide that a relay is not
5885 "Valid", they no longer include it in the consensus at all. Closes
5886 ticket 20002; implements part of proposal 272.
5888 o Minor features (testing):
5889 - Disable memory protections on OpenBSD when performing our unit
5890 tests for memwipe(). The test deliberately invokes undefined
5891 behavior, and the OpenBSD protections interfere with this. Patch
5892 from "rubiate". Closes ticket 20066.
5894 o Minor features (testing, ipv6):
5895 - Add the single-onion and single-onion-ipv6 chutney targets to
5896 "make test-network-all". This requires a recent chutney version
5897 with the single onion network flavours (git c72a652 or later).
5898 Closes ticket 20072; patch by teor.
5899 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5900 tests. Remove bridges+hs, as it's somewhat redundant. This
5901 requires a recent chutney version that supports IPv6 clients,
5902 relays, and authorities. Closes ticket 20069; patch by teor.
5904 o Minor features (Tor2web):
5905 - Make Tor2web clients respect ReachableAddresses. This feature was
5906 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5907 0.2.8.7. Implements feature 20034. Patch by teor.
5909 o Minor features (unit tests):
5910 - We've done significant work to make the unit tests run faster.
5911 - Our link-handshake unit tests now check that when invalid
5912 handshakes fail, they fail with the error messages we expected.
5913 - Our unit testing code that captures log messages no longer
5914 prevents them from being written out if the user asked for them
5915 (by passing --debug or --info or or --notice --warn to the "test"
5916 binary). This change prevents us from missing unexpected log
5917 messages simply because we were looking for others. Related to
5919 - The unit tests now log all warning messages with the "BUG" flag.
5920 Previously, they only logged errors by default. This change will
5921 help us make our testing code more correct, and make sure that we
5922 only hit this code when we mean to. In the meantime, however,
5923 there will be more warnings in the unit test logs than before.
5924 This is preparatory work for ticket 19999.
5925 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5926 assertion as a test failure.
5928 o Minor bug fixes (circuits):
5929 - Use the CircuitBuildTimeout option whenever
5930 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5931 the option when a user disabled it, but not when it was disabled
5932 because some other option was set. Fixes bug 20073; bugfix on
5933 0.2.4.12-alpha. Patch by teor.
5935 o Minor bugfixes (allocation):
5936 - Change how we allocate memory for large chunks on buffers, to
5937 avoid a (currently impossible) integer overflow, and to waste less
5938 space when allocating unusually large chunks. Fixes bug 20081;
5939 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5940 - Always include orconfig.h before including any other C headers.
5941 Sometimes, it includes macros that affect the behavior of the
5942 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
5943 first version to use AC_USE_SYSTEM_EXTENSIONS).
5944 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
5945 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
5946 Patch from Gisle Vanem.
5947 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
5948 They apparently require a set of annotations that we aren't
5949 currently using, and they create false positives in our pthreads
5950 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
5952 o Minor bugfixes (directory authority):
5953 - Die with a more useful error when the operator forgets to place
5954 the authority_signing_key file into the keys directory. This
5955 avoids an uninformative assert & traceback about having an invalid
5956 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5957 - When allowing private addresses, mark Exits that only exit to
5958 private locations as such. Fixes bug 20064; bugfix
5961 o Minor bugfixes (documentation):
5962 - Document the default PathsNeededToBuildCircuits value that's used
5963 by clients when the directory authorities don't set
5964 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
5965 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
5966 - Fix manual for the User option: it takes a username, not a UID.
5967 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5970 o Minor bugfixes (hidden services):
5971 - Stop logging intro point details to the client log on certain
5972 error conditions. Fixed as part of bug 20012; bugfix on
5973 0.2.4.8-alpha. Patch by teor.
5975 o Minor bugfixes (IPv6, testing):
5976 - Check for IPv6 correctly on Linux when running test networks.
5977 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5979 o Minor bugfixes (Linux seccomp2 sandbox):
5980 - Add permission to run the sched_yield() and sigaltstack() system
5981 calls, in order to support versions of Tor compiled with asan or
5982 ubsan code that use these calls. Now "sandbox 1" and
5983 "--enable-expensive-hardening" should be compatible on more
5984 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5986 o Minor bugfixes (logging):
5987 - When logging a message from the BUG() macro, be explicit about
5988 what we were asserting. Previously we were confusing what we were
5989 asserting with what the bug was. Fixes bug 20093; bugfix
5991 - When we are unable to remove the bw_accounting file, do not warn
5992 if the reason we couldn't remove it was that it didn't exist.
5993 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
5995 o Minor bugfixes (option parsing):
5996 - Count unix sockets when counting client listeners (SOCKS, Trans,
5997 NATD, and DNS). This has no user-visible behaviour changes: these
5998 options are set once, and never read. Required for correct
5999 behaviour in ticket 17178. Fixes bug 19677; bugfix on
6000 0.2.6.3-alpha. Patch by teor.
6002 o Minor bugfixes (options):
6003 - Check the consistency of UseEntryGuards and EntryNodes more
6004 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
6006 - Stop changing the configured value of UseEntryGuards on
6007 authorities and Tor2web clients. Fixes bug 20074; bugfix on
6008 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
6011 o Minor bugfixes (Tor2web):
6012 - Prevent Tor2web clients running hidden services, these services
6013 are not anonymous due to the one-hop client paths. Fixes bug
6014 19678. Patch by teor.
6016 o Minor bugfixes (unit tests):
6017 - Fix a shared-random unit test that was failing on big endian
6018 architectures due to internal representation of a integer copied
6019 to a buffer. The test is changed to take a full 32 bytes of data
6020 and use the output of a python script that make the COMMIT and
6021 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
6023 - The tor_tls_server_info_callback unit test no longer crashes when
6024 debug-level logging is turned on. Fixes bug 20041; bugfix
6028 Changes in version 0.2.8.8 - 2016-09-23
6029 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
6030 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
6031 who select public relays as their bridges.
6033 o Major bugfixes (crash):
6034 - Fix a complicated crash bug that could affect Tor clients
6035 configured to use bridges when replacing a networkstatus consensus
6036 in which one of their bridges was mentioned. OpenBSD users saw
6037 more crashes here, but all platforms were potentially affected.
6038 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
6040 o Major bugfixes (relay, OOM handler):
6041 - Fix a timing-dependent assertion failure that could occur when we
6042 tried to flush from a circuit after having freed its cells because
6043 of an out-of-memory condition. Fixes bug 20203; bugfix on
6044 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
6047 o Minor feature (fallback directories):
6048 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
6049 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
6050 2016. Closes ticket 20190; patch by teor.
6052 o Minor features (geoip):
6053 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
6057 Changes in version 0.2.9.2-alpha - 2016-08-24
6058 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
6059 several new features and bugfixes. It also includes an important
6060 authority update and an important bugfix from 0.2.8.7. Everyone who
6061 sets the ReachableAddresses option, and all bridges, are strongly
6062 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
6064 o Directory authority changes (also in 0.2.8.7):
6065 - The "Tonga" bridge authority has been retired; the new bridge
6066 authority is "Bifroest". Closes tickets 19728 and 19690.
6068 o Major bugfixes (client, security, also in 0.2.8.7):
6069 - Only use the ReachableAddresses option to restrict the first hop
6070 in a path. In earlier versions of 0.2.8.x, it would apply to
6071 every hop in the path, with a possible degradation in anonymity
6072 for anyone using an uncommon ReachableAddress setting. Fixes bug
6073 19973; bugfix on 0.2.8.2-alpha.
6075 o Major features (user interface):
6076 - Tor now supports the ability to declare options deprecated, so
6077 that we can recommend that people stop using them. Previously,
6078 this was done in an ad-hoc way. Closes ticket 19820.
6080 o Major bugfixes (directory downloads):
6081 - Avoid resetting download status for consensuses hourly, since we
6082 already have another, smarter retry mechanism. Fixes bug 8625;
6083 bugfix on 0.2.0.9-alpha.
6085 o Minor features (config):
6086 - Warn users when descriptor and port addresses are inconsistent.
6087 Mitigates bug 13953; patch by teor.
6089 o Minor features (geoip):
6090 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
6093 o Minor features (user interface):
6094 - There is a new --list-deprecated-options command-line option to
6095 list all of the deprecated options. Implemented as part of
6098 o Minor bugfixes (code style):
6099 - Fix an integer signedness conversion issue in the case conversion
6100 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
6102 o Minor bugfixes (compilation):
6103 - Build correctly on versions of libevent2 without support for
6104 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
6106 - Fix a compilation warning on GCC versions before 4.6. Our
6107 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
6108 when it is also required as an argument to the compiler pragma.
6109 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
6111 o Minor bugfixes (compilation, also in 0.2.8.7):
6112 - Remove an inappropriate "inline" in tortls.c that was causing
6113 warnings on older versions of GCC. Fixes bug 19903; bugfix
6116 o Minor bugfixes (fallback directories, also in 0.2.8.7):
6117 - Avoid logging a NULL string pointer when loading fallback
6118 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
6119 and 0.2.8.1-alpha. Report and patch by "rubiate".
6121 o Minor bugfixes (logging):
6122 - Log a more accurate message when we fail to dump a microdescriptor.
6123 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
6125 o Minor bugfixes (memory leak):
6126 - Fix a series of slow memory leaks related to parsing torrc files
6127 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
6129 o Deprecated features:
6130 - A number of DNS-cache-related sub-options for client ports are now
6131 deprecated for security reasons, and may be removed in a future
6132 version of Tor. (We believe that client-side DNS caching is a bad
6133 idea for anonymity, and you should not turn it on.) The options
6134 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
6135 UseIPv4Cache, and UseIPv6Cache.
6136 - A number of options are deprecated for security reasons, and may
6137 be removed in a future version of Tor. The options are:
6138 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
6139 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
6140 CloseHSClientCircuitsImmediatelyOnTimeout,
6141 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
6142 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
6143 UseNTorHandshake, and WarnUnsafeSocks.
6144 - The *ListenAddress options are now deprecated as unnecessary: the
6145 corresponding *Port options should be used instead. These options
6146 may someday be removed. The affected options are:
6147 ControlListenAddress, DNSListenAddress, DirListenAddress,
6148 NATDListenAddress, ORListenAddress, SocksListenAddress,
6149 and TransListenAddress.
6152 - Correct the IPv6 syntax in our documentation for the
6153 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
6156 - We no longer include the (dead, deprecated) bufferevent code in
6157 Tor. Closes ticket 19450. Based on a patch from U+039b.
6160 Changes in version 0.2.8.7 - 2016-08-24
6161 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
6162 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
6163 who sets the ReachableAddresses option, and all bridges, are strongly
6164 encouraged to upgrade.
6166 o Directory authority changes:
6167 - The "Tonga" bridge authority has been retired; the new bridge
6168 authority is "Bifroest". Closes tickets 19728 and 19690.
6170 o Major bugfixes (client, security):
6171 - Only use the ReachableAddresses option to restrict the first hop
6172 in a path. In earlier versions of 0.2.8.x, it would apply to
6173 every hop in the path, with a possible degradation in anonymity
6174 for anyone using an uncommon ReachableAddress setting. Fixes bug
6175 19973; bugfix on 0.2.8.2-alpha.
6177 o Minor features (geoip):
6178 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
6181 o Minor bugfixes (compilation):
6182 - Remove an inappropriate "inline" in tortls.c that was causing
6183 warnings on older versions of GCC. Fixes bug 19903; bugfix
6186 o Minor bugfixes (fallback directories):
6187 - Avoid logging a NULL string pointer when loading fallback
6188 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
6189 and 0.2.8.1-alpha. Report and patch by "rubiate".
6192 Changes in version 0.2.9.1-alpha - 2016-08-08
6193 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
6194 series. It improves our support for hardened builds and compiler
6195 warnings, deploys some critical infrastructure for improvements to
6196 hidden services, includes a new timing backend that we hope to use for
6197 better support for traffic padding, makes it easier for programmers to
6198 log unexpected events, and contains other small improvements to
6199 security, correctness, and performance.
6201 Below are the changes since 0.2.8.6.
6203 o New system requirements:
6204 - Tor now requires Libevent version 2.0.10-stable or later. Older
6205 versions of Libevent have less efficient backends for several
6206 platforms, and lack the DNS code that we use for our server-side
6207 DNS support. This implements ticket 19554.
6208 - Tor now requires zlib version 1.2 or later, for security,
6209 efficiency, and (eventually) gzip support. (Back when we started,
6210 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
6211 released in 2003. We recommend the latest version.)
6213 o Major features (build, hardening):
6214 - Tor now builds with -ftrapv by default on compilers that support
6215 it. This option detects signed integer overflow (which C forbids),
6216 and turns it into a hard-failure. We do not apply this option to
6217 code that needs to run in constant time to avoid side-channels;
6218 instead, we use -fwrapv in that code. Closes ticket 17983.
6219 - When --enable-expensive-hardening is selected, stop applying the
6220 clang/gcc sanitizers to code that needs to run in constant time.
6221 Although we are aware of no introduced side-channels, we are not
6222 able to prove that there are none. Related to ticket 17983.
6224 o Major features (compilation):
6225 - Our big list of extra GCC warnings is now enabled by default when
6226 building with GCC (or with anything like Clang that claims to be
6227 GCC-compatible). To make all warnings into fatal compilation
6228 errors, pass --enable-fatal-warnings to configure. Closes
6230 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
6231 turn on C and POSIX extensions. (Previously, we attempted to do
6232 this on an ad hoc basis.) Closes ticket 19139.
6234 o Major features (directory authorities, hidden services):
6235 - Directory authorities can now perform the shared randomness
6236 protocol specified by proposal 250. Using this protocol, directory
6237 authorities generate a global fresh random value every day. In the
6238 future, this value will be used by hidden services to select
6239 HSDirs. This release implements the directory authority feature;
6240 the hidden service side will be implemented in the future as part
6241 of proposal 224. Resolves ticket 16943; implements proposal 250.
6243 o Major features (downloading, random exponential backoff):
6244 - When we fail to download an object from a directory service, wait
6245 for an (exponentially increasing) randomized amount of time before
6246 retrying, rather than a fixed interval as we did before. This
6247 prevents a group of Tor instances from becoming too synchronized,
6248 or a single Tor instance from becoming too predictable, in its
6249 download schedule. Closes ticket 15942.
6251 o Major bugfixes (exit policies):
6252 - Avoid disclosing exit outbound bind addresses, configured port
6253 bind addresses, and local interface addresses in relay descriptors
6254 by default under ExitPolicyRejectPrivate. Instead, only reject
6255 these (otherwise unlisted) addresses if
6256 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
6257 0.2.7.2-alpha. Patch by teor.
6259 o Major bugfixes (hidden service client):
6260 - Allow Tor clients with appropriate controllers to work with
6261 FetchHidServDescriptors set to 0. Previously, this option also
6262 disabled descriptor cache lookup, thus breaking hidden services
6263 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
6265 o Minor features (build, hardening):
6266 - Detect and work around a libclang_rt problem that would prevent
6267 clang from finding __mulodi4() on some 32-bit platforms, and thus
6268 keep -ftrapv from linking on those systems. Closes ticket 19079.
6269 - When building on a system without runtime support for the runtime
6270 hardening options, try to log a useful warning at configuration
6271 time, rather than an incomprehensible warning at link time. If
6272 expensive hardening was requested, this warning becomes an error.
6273 Closes ticket 18895.
6275 o Minor features (code safety):
6276 - In our integer-parsing functions, ensure that maxiumum value we
6277 give is no smaller than the minimum value. Closes ticket 19063;
6280 o Minor features (controller):
6281 - Implement new GETINFO queries for all downloads that use
6282 download_status_t to schedule retries. This allows controllers to
6283 examine the schedule for pending downloads. Closes ticket 19323.
6284 - Allow controllers to configure basic client authorization on
6285 hidden services when they create them with the ADD_ONION control
6286 command. Implements ticket 15588. Patch by "special".
6287 - Fire a STATUS_SERVER controller event whenever the hibernation
6288 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
6290 o Minor features (directory authority):
6291 - Directory authorities now only give the Guard flag to a relay if
6292 they are also giving it the Stable flag. This change allows us to
6293 simplify path selection for clients. It should have minimal effect
6294 in practice, since >99% of Guards already have the Stable flag.
6295 Implements ticket 18624.
6296 - Directory authorities now write their v3-status-votes file out to
6297 disk earlier in the consensus process, so we have a record of the
6298 votes even if we abort the consensus process. Resolves
6301 o Minor features (hidden service):
6302 - Stop being so strict about the payload length of "rendezvous1"
6303 cells. We used to be locked in to the "TAP" handshake length, and
6304 now we can handle better handshakes like "ntor". Resolves
6307 o Minor features (infrastructure, time):
6308 - Tor now uses the operating system's monotonic timers (where
6309 available) for internal fine-grained timing. Previously we would
6310 look at the system clock, and then attempt to compensate for the
6311 clock running backwards. Closes ticket 18908.
6312 - Tor now includes an improved timer backend, so that we can
6313 efficiently support tens or hundreds of thousands of concurrent
6314 timers, as will be needed for some of our planned anti-traffic-
6315 analysis work. This code is based on William Ahern's "timeout.c"
6316 project, which implements a "tickless hierarchical timing wheel".
6317 Closes ticket 18365.
6319 o Minor features (logging):
6320 - Provide a more useful warning message when configured with an
6321 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
6322 - When dumping unparseable router descriptors, optionally store them
6323 in separate files, named by digest, up to a configurable size
6324 limit. You can change the size limit by setting the
6325 MaxUnparseableDescSizeToLog option, and disable this feature by
6326 setting that option to 0. Closes ticket 18322.
6327 - Add a set of macros to check nonfatal assertions, for internal
6328 use. Migrating more of our checks to these should help us avoid
6329 needless crash bugs. Closes ticket 18613.
6331 o Minor features (performance):
6332 - Changer the "optimistic data" extension from "off by default" to
6333 "on by default". The default was ordinarily overridden by a
6334 consensus option, but when clients were bootstrapping for the
6335 first time, they would not have a consensus to get the option
6336 from. Changing this default When fetching a consensus for the
6337 first time, use optimistic data. This saves a round-trip during
6338 startup. Closes ticket 18815.
6340 o Minor features (relay, usability):
6341 - When the directory authorities refuse a bad relay's descriptor,
6342 encourage the relay operator to contact us. Many relay operators
6343 won't notice this line in their logs, but it's a win if even a few
6344 learn why we don't like what their relay was doing. Resolves
6347 o Minor features (testing):
6348 - Let backtrace tests work correctly under AddressSanitizer. Fixes
6349 part of bug 18934; bugfix on 0.2.5.2-alpha.
6350 - Move the test-network.sh script to chutney, and modify tor's test-
6351 network.sh to call the (newer) chutney version when available.
6352 Resolves ticket 19116. Patch by teor.
6353 - Use the lcov convention for marking lines as unreachable, so that
6354 we don't count them when we're generating test coverage data.
6355 Update our coverage tools to understand this convention. Closes
6358 o Minor bugfixes (bootstrap):
6359 - Remember the directory we fetched the consensus or previous
6360 certificates from, and use it to fetch future authority
6361 certificates. This change improves bootstrapping performance.
6362 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
6364 o Minor bugfixes (build):
6365 - The test-stem and test-network makefile targets now depend only on
6366 the tor binary that they are testing. Previously, they depended on
6367 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
6368 patch from "cypherpunks".
6370 o Minor bugfixes (circuits):
6371 - Make sure extend_info_from_router() is only called on servers.
6372 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
6374 o Minor bugfixes (compilation):
6375 - When building with Clang, use a full set of GCC warnings.
6376 (Previously, we included only a subset, because of the way we
6377 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
6379 o Minor bugfixes (directory authority):
6380 - Authorities now sort the "package" lines in their votes, for ease
6381 of debugging. (They are already sorted in consensus documents.)
6382 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
6383 - When parsing a detached signature, make sure we use the length of
6384 the digest algorithm instead of an hardcoded DIGEST256_LEN in
6385 order to avoid comparing bytes out-of-bounds with a smaller digest
6386 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
6388 o Minor bugfixes (documentation):
6389 - Document the --passphrase-fd option in the tor manpage. Fixes bug
6390 19504; bugfix on 0.2.7.3-rc.
6391 - Fix the description of the --passphrase-fd option in the
6392 tor-gencert manpage. The option is used to pass the number of a
6393 file descriptor to read the passphrase from, not to read the file
6394 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
6396 o Minor bugfixes (ephemeral hidden service):
6397 - When deleting an ephemeral hidden service, close its intro points
6398 even if they are not completely open. Fixes bug 18604; bugfix
6401 o Minor bugfixes (guard selection):
6402 - Use a single entry guard even if the NumEntryGuards consensus
6403 parameter is not provided. Fixes bug 17688; bugfix
6405 - Don't mark guards as unreachable if connection_connect() fails.
6406 That function fails for local reasons, so it shouldn't reveal
6407 anything about the status of the guard. Fixes bug 14334; bugfix
6410 o Minor bugfixes (hidden service client):
6411 - Increase the minimum number of internal circuits we preemptively
6412 build from 2 to 3, so a circuit is available when a client
6413 connects to another onion service. Fixes bug 13239; bugfix
6416 o Minor bugfixes (logging):
6417 - When logging a directory ownership mismatch, log the owning
6418 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
6420 o Minor bugfixes (memory leaks):
6421 - Fix a small, uncommon memory leak that could occur when reading a
6422 truncated ed25519 key file. Fixes bug 18956; bugfix
6425 o Minor bugfixes (testing):
6426 - Allow clients to retry HSDirs much faster in test networks. Fixes
6427 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
6428 - Disable ASAN's detection of segmentation faults while running
6429 test_bt.sh, so that we can make sure that our own backtrace
6430 generation code works. Fixes another aspect of bug 18934; bugfix
6431 on 0.2.5.2-alpha. Patch from "cypherpunks".
6432 - Fix the test-network-all target on out-of-tree builds by using the
6433 correct path to the test driver script. Fixes bug 19421; bugfix
6436 o Minor bugfixes (time):
6437 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
6438 bugfix on all released tor versions.
6439 - When computing the difference between two times in milliseconds,
6440 we now round to the nearest millisecond correctly. Previously, we
6441 could sometimes round in the wrong direction. Fixes bug 19428;
6442 bugfix on 0.2.2.2-alpha.
6444 o Minor bugfixes (user interface):
6445 - Display a more accurate number of suppressed messages in the log
6446 rate-limiter. Previously, there was a potential integer overflow
6447 in the counter. Now, if the number of messages hits a maximum, the
6448 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
6450 - Fix a typo in the passphrase prompt for the ed25519 identity key.
6451 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
6453 o Code simplification and refactoring:
6454 - Remove redundant declarations of the MIN macro. Closes
6456 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
6457 Closes ticket 18462; patch from "icanhasaccount".
6458 - Split the 600-line directory_handle_command_get function into
6459 separate functions for different URL types. Closes ticket 16698.
6462 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
6463 ticket 19153. Patch from "U+039b".
6466 - Remove support for "GET /tor/bytes.txt" DirPort request, and
6467 "GETINFO dir-usage" controller request, which were only available
6468 via a compile-time option in Tor anyway. Feature was added in
6469 0.2.2.1-alpha. Resolves ticket 19035.
6470 - There is no longer a compile-time option to disable support for
6471 TransPort. (If you don't want TransPort; just don't use it.) Patch
6472 from "U+039b". Closes ticket 19449.
6475 - Run more workqueue tests as part of "make check". These had
6476 previously been implemented, but you needed to know special
6477 command-line options to enable them.
6478 - We now have unit tests for our code to reject zlib "compression
6479 bombs". (Fortunately, the code works fine.)
6482 Changes in version 0.2.8.6 - 2016-08-02
6484 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
6486 The Tor 0.2.8 series improves client bootstrapping performance,
6487 completes the authority-side implementation of improved identity
6488 keys for relays, and includes numerous bugfixes and performance
6489 improvements throughout the program. This release continues to
6490 improve the coverage of Tor's test suite. For a full list of
6491 changes since Tor 0.2.7, see the ReleaseNotes file.
6493 Changes since 0.2.8.5-rc:
6495 o Minor features (geoip):
6496 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
6499 o Minor bugfixes (compilation):
6500 - Fix a compilation warning in the unit tests on systems where char
6501 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
6503 o Minor bugfixes (fallback directories):
6504 - Remove 1 fallback that was on the hardcoded list, then opted-out,
6505 leaving 89 of the 100 fallbacks originally introduced in Tor
6506 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
6508 o Minor bugfixes (Linux seccomp2 sandbox):
6509 - Allow more syscalls when running with "Sandbox 1" enabled:
6510 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
6511 some systems, these are required for Tor to start. Fixes bug
6512 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
6513 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
6514 so that get_interface_address6_via_udp_socket_hack() can work.
6515 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
6518 Changes in version 0.2.8.5-rc - 2016-07-07
6519 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
6520 series. If we find no new bugs or regressions here, the first stable
6521 0.2.8 release will be identical to it. It has a few small bugfixes
6522 against previous versions.
6524 o Directory authority changes:
6525 - Urras is no longer a directory authority. Closes ticket 19271.
6527 o Major bugfixes (heartbeat):
6528 - Fix a regression that would crash Tor when the periodic
6529 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
6530 0.2.8.1-alpha. Reported by "kubaku".
6532 o Minor features (build):
6533 - Tor now again builds with the recent OpenSSL 1.1 development
6534 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
6535 - When building manual pages, set the timezone to "UTC", so that the
6536 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
6537 Patch from intrigeri.
6539 o Minor bugfixes (fallback directory selection):
6540 - Avoid errors during fallback selection if there are no eligible
6541 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
6544 o Minor bugfixes (IPv6, microdescriptors):
6545 - Don't check node addresses when we only have a routerstatus. This
6546 allows IPv6-only clients to bootstrap by fetching microdescriptors
6547 from fallback directory mirrors. (The microdescriptor consensus
6548 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
6551 o Minor bugfixes (logging):
6552 - Reduce pointlessly verbose log messages when directory servers
6553 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
6554 0.2.8.1-alpha. Patch by teor.
6555 - When a fallback directory changes its fingerprint from the hard-
6556 coded fingerprint, log a less severe, more explanatory log
6557 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
6559 o Minor bugfixes (Linux seccomp2 sandboxing):
6560 - Allow statistics to be written to disk when "Sandbox 1" is
6561 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
6562 0.2.6.1-alpha respectively.
6564 o Minor bugfixes (user interface):
6565 - Remove a warning message "Service [scrubbed] not found after
6566 descriptor upload". This message appears when one uses HSPOST
6567 control command to upload a service descriptor. Since there is
6568 only a descriptor and no service, showing this message is
6569 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
6571 o Fallback directory list:
6572 - Add a comment to the generated fallback directory list that
6573 explains how to comment out unsuitable fallbacks in a way that's
6574 compatible with the stem fallback parser.
6575 - Update fallback whitelist and blacklist based on relay operator
6576 emails. Blacklist unsuitable (non-working, over-volatile)
6577 fallbacks. Resolves ticket 19071. Patch by teor.
6578 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
6579 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
6580 ticket 19071; patch by teor.
6583 Changes in version 0.2.8.4-rc - 2016-06-15
6584 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
6585 If we find no new bugs or regressions here, the first stable 0.2.8
6586 release will be identical to it. It has a few small bugfixes against
6589 o Major bugfixes (user interface):
6590 - Correctly give a warning in the cases where a relay is specified
6591 by nickname, and one such relay is found, but it is not officially
6592 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
6594 o Minor features (build):
6595 - Tor now builds once again with the recent OpenSSL 1.1 development
6596 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
6598 o Minor features (geoip):
6599 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
6602 o Minor bugfixes (compilation):
6603 - Cause the unit tests to compile correctly on mingw64 versions that
6604 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
6606 o Minor bugfixes (downloading):
6607 - Predict more correctly whether we'll be downloading over HTTP when
6608 we determine the maximum length of a URL. This should avoid a
6609 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
6613 Changes in version 0.2.8.3-alpha - 2016-05-26
6614 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
6615 the course of the 0.2.8 development cycle. It improves the behavior of
6616 directory clients, fixes several crash bugs, fixes a gap in compiler
6617 hardening, and allows the full integration test suite to run on
6620 o Major bugfixes (security, client, DNS proxy):
6621 - Stop a crash that could occur when a client running with DNSPort
6622 received a query with multiple address types, and the first
6623 address type was not supported. Found and fixed by Scott Dial.
6624 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
6626 o Major bugfixes (security, compilation):
6627 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
6628 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
6629 cause a compiler warning, thereby making other checks fail, and
6630 needlessly disabling compiler-hardening support. Fixes one case of
6631 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
6633 o Major bugfixes (security, directory authorities):
6634 - Fix a crash and out-of-bounds write during authority voting, when
6635 the list of relays includes duplicate ed25519 identity keys. Fixes
6636 bug 19032; bugfix on 0.2.8.2-alpha.
6638 o Major bugfixes (client, bootstrapping):
6639 - Check if bootstrap consensus downloads are still needed when the
6640 linked connection attaches. This prevents tor making unnecessary
6641 begindir-style connections, which are the only directory
6642 connections tor clients make since the fix for 18483 was merged.
6643 - Fix some edge cases where consensus download connections may not
6644 have been closed, even though they were not needed. Related to fix
6646 - Make relays retry consensus downloads the correct number of times,
6647 rather than the more aggressive client retry count. Fixes part of
6649 - Stop downloading consensuses when we have a consensus, even if we
6650 don't have all the certificates for it yet. Fixes bug 18809;
6651 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
6653 o Major bugfixes (directory mirrors):
6654 - Decide whether to advertise begindir support in the the same way
6655 we decide whether to advertise our DirPort. Allowing these
6656 decisions to become out-of-sync led to surprising behavior like
6657 advertising begindir support when hibernation made us not
6658 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
6661 o Major bugfixes (IPv6 bridges, client):
6662 - Actually use IPv6 addresses when selecting directory addresses for
6663 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
6666 o Major bugfixes (key management):
6667 - If OpenSSL fails to generate an RSA key, do not retain a dangling
6668 pointer to the previous (uninitialized) key value. The impact here
6669 should be limited to a difficult-to-trigger crash, if OpenSSL is
6670 running an engine that makes key generation failures possible, or
6671 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
6672 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
6675 o Major bugfixes (testing):
6676 - Fix a bug that would block 'make test-network-all' on systems where
6677 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
6678 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
6679 bugfix on 0.2.8.1-alpha.
6681 o Minor features (clients):
6682 - Make clients, onion services, and bridge relays always use an
6683 encrypted begindir connection for directory requests. Resolves
6684 ticket 18483. Patch by "teor".
6686 o Minor features (fallback directory mirrors):
6687 - Give each fallback the same weight for client selection; restrict
6688 fallbacks to one per operator; report fallback directory detail
6689 changes when rebuilding list; add new fallback directory mirrors
6690 to the whitelist; and many other minor simplifications and fixes.
6691 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
6692 0.2.8.1-alpha; patch by "teor".
6693 - Replace the 21 fallbacks generated in January 2016 and included in
6694 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
6695 2016. Closes task 17158; patch by "teor".
6697 o Minor features (geoip):
6698 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
6701 o Minor bugfixes (assert, portability):
6702 - Fix an assertion failure in memarea.c on systems where "long" is
6703 shorter than the size of a pointer. Fixes bug 18716; bugfix
6706 o Minor bugfixes (bootstrap):
6707 - Consistently use the consensus download schedule for authority
6708 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
6710 o Minor bugfixes (build):
6711 - Remove a pair of redundant AM_CONDITIONAL declarations from
6712 configure.ac. Fixes one final case of bug 17744; bugfix
6714 - Resolve warnings when building on systems that are concerned with
6715 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
6717 - When libscrypt.h is found, but no libscrypt library can be linked,
6718 treat libscrypt as absent. Fixes bug 19161; bugfix
6721 o Minor bugfixes (client):
6722 - Turn all TestingClientBootstrap* into non-testing torrc options.
6723 This changes simply renames them by removing "Testing" in front of
6724 them and they do not require TestingTorNetwork to be enabled
6725 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
6726 - Make directory node selection more reliable, mainly for IPv6-only
6727 clients and clients with few reachable addresses. Fixes bug 18929;
6728 bugfix on 0.2.8.1-alpha. Patch by "teor".
6730 o Minor bugfixes (controller, microdescriptors):
6731 - Make GETINFO dir/status-vote/current/consensus conform to the
6732 control specification by returning "551 Could not open cached
6733 consensus..." when not caching consensuses. Fixes bug 18920;
6734 bugfix on 0.2.2.6-alpha.
6736 o Minor bugfixes (crypto, portability):
6737 - The SHA3 and SHAKE routines now produce the correct output on Big
6738 Endian systems. No code calls either algorithm yet, so this is
6739 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
6740 - Tor now builds again with the recent OpenSSL 1.1 development
6741 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
6744 o Minor bugfixes (directories):
6745 - When fetching extrainfo documents, compare their SHA256 digests
6746 and Ed25519 signing key certificates with the routerinfo that led
6747 us to fetch them, rather than with the most recent routerinfo.
6748 Otherwise we generate many spurious warnings about mismatches.
6749 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
6751 o Minor bugfixes (logging):
6752 - When we can't generate a signing key because OfflineMasterKey is
6753 set, do not imply that we should have been able to load it. Fixes
6754 bug 18133; bugfix on 0.2.7.2-alpha.
6755 - Stop periodic_event_dispatch() from blasting twelve lines per
6756 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
6757 - When rejecting a misformed INTRODUCE2 cell, only log at
6758 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
6760 o Minor bugfixes (pluggable transports):
6761 - Avoid reporting a spurious error when we decide that we don't need
6762 to terminate a pluggable transport because it has already exited.
6763 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
6765 o Minor bugfixes (pointer arithmetic):
6766 - Fix a bug in memarea_alloc() that could have resulted in remote
6767 heap write access, if Tor had ever passed an unchecked size to
6768 memarea_alloc(). Fortunately, all the sizes we pass to
6769 memarea_alloc() are pre-checked to be less than 128 kilobytes.
6770 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
6773 o Minor bugfixes (relays):
6774 - Consider more config options when relays decide whether to
6775 regenerate their descriptor. Fixes more of bug 12538; bugfix
6777 - Resolve some edge cases where we might launch an ORPort
6778 reachability check even when DisableNetwork is set. Noticed while
6779 fixing bug 18616; bugfix on 0.2.3.9-alpha.
6781 o Minor bugfixes (statistics):
6782 - We now include consensus downloads via IPv6 in our directory-
6783 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
6785 o Minor bugfixes (testing):
6786 - Allow directories in small networks to bootstrap by skipping
6787 DirPort checks when the consensus has no exits. Fixes bug 19003;
6788 bugfix on 0.2.8.1-alpha. Patch by teor.
6789 - Fix a small memory leak that would occur when the
6790 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
6791 bugfix on 0.2.5.2-alpha.
6793 o Minor bugfixes (time handling):
6794 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
6795 field. Otherwise, our unit tests crash on Windows. Fixes bug
6796 18977; bugfix on 0.2.2.25-alpha.
6799 - Document the contents of the 'datadir/keys' subdirectory in the
6800 manual page. Closes ticket 17621.
6801 - Stop recommending use of nicknames to identify relays in our
6802 MapAddress documentation. Closes ticket 18312.
6805 Changes in version 0.2.8.2-alpha - 2016-03-28
6806 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
6807 bugs in earlier versions of Tor, including some that prevented
6808 authorities using Tor 0.2.7.x from running correctly. IPv6 and
6809 directory support should also be much improved.
6811 o New system requirements:
6812 - Tor no longer supports versions of OpenSSL with a broken
6813 implementation of counter mode. (This bug was present in OpenSSL
6814 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
6815 longer runs with, these versions.
6816 - Tor no longer attempts to support platforms where the "time_t"
6817 type is unsigned. (To the best of our knowledge, only OpenVMS does
6818 this, and Tor has never actually built on OpenVMS.) Closes
6820 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
6821 later (released in 2008 and 2009 respectively). If you are
6822 building Tor from the git repository instead of from the source
6823 distribution, and your tools are older than this, you will need to
6824 upgrade. Closes ticket 17732.
6826 o Major bugfixes (security, pointers):
6827 - Avoid a difficult-to-trigger heap corruption attack when extending
6828 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6829 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6830 Reported by Guido Vranken.
6832 o Major bugfixes (bridges, pluggable transports):
6833 - Modify the check for OR connections to private addresses. Allow
6834 bridges on private addresses, including pluggable transports that
6835 ignore the (potentially private) address in the bridge line. Fixes
6836 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
6838 o Major bugfixes (compilation):
6839 - Repair hardened builds under the clang compiler. Previously, our
6840 use of _FORTIFY_SOURCE would conflict with clang's address
6841 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
6843 o Major bugfixes (crash on shutdown):
6844 - Correctly handle detaching circuits from muxes when shutting down.
6845 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
6846 - Fix an assert-on-exit bug related to counting memory usage in
6847 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
6849 o Major bugfixes (crash on startup):
6850 - Fix a segfault during startup: If a Unix domain socket was
6851 configured as listener (such as a ControlSocket or a SocksPort
6852 "unix:" socket), and tor was started as root but not configured to
6853 switch to another user, tor would segfault while trying to string
6854 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
6857 o Major bugfixes (dns proxy mode, crash):
6858 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
6859 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
6861 o Major bugfixes (relays, bridge clients):
6862 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
6863 bridge clients use the address configured in the bridge line.
6864 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
6867 o Major bugfixes (voting):
6868 - Actually enable support for authorities to match routers by their
6869 Ed25519 identities. Previously, the code had been written, but
6870 some debugging code that had accidentally been left in the
6871 codebase made it stay turned off. Fixes bug 17702; bugfix
6873 - When collating votes by Ed25519 identities, authorities now
6874 include a "NoEdConsensus" flag if the ed25519 value (or lack
6875 thereof) for a server does not reflect the majority consensus.
6876 Related to bug 17668; bugfix on 0.2.7.2-alpha.
6877 - When generating a vote with keypinning disabled, never include two
6878 entries for the same ed25519 identity. This bug was causing
6879 authorities to generate votes that they could not parse when a
6880 router violated key pinning by changing its RSA identity but
6881 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
6882 18318. Bugfix on 0.2.7.2-alpha.
6884 o Minor features (security, win32):
6885 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
6886 attack. Fixes bug 18123; bugfix on all tor versions. Patch
6889 o Minor features (bug-resistance):
6890 - Make Tor survive errors involving connections without a
6891 corresponding event object. Previously we'd fail with an
6892 assertion; now we produce a log message. Related to bug 16248.
6894 o Minor features (build):
6895 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
6896 as having possible IPFW support. Closes ticket 18448. Patch from
6899 o Minor features (code hardening):
6900 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6901 level code, to harden against accidental failures to NUL-
6902 terminate. Part of ticket 17852. Patch from jsturgix. Found
6905 o Minor features (crypto):
6906 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6907 p is a safe prime, and g is a suitable generator. Closes
6910 o Minor features (geoip):
6911 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
6914 o Minor features (hidden service directory):
6915 - Streamline relay-side hsdir handling: when relays consider whether
6916 to accept an uploaded hidden service descriptor, they no longer
6917 check whether they are one of the relays in the network that is
6918 "supposed" to handle that descriptor. Implements ticket 18332.
6920 o Minor features (IPv6):
6921 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
6922 to 1, tor prefers IPv6 directory addresses.
6923 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
6924 avoids using IPv4 for client OR and directory connections.
6925 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
6926 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
6927 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
6929 o Minor features (linux seccomp2 sandbox):
6930 - Reject attempts to change our Address with "Sandbox 1" enabled.
6931 Changing Address with Sandbox turned on would never actually work,
6932 but previously it would fail in strange and confusing ways. Found
6935 o Minor features (robustness):
6936 - Exit immediately with an error message if the code attempts to use
6937 Libevent without having initialized it. This should resolve some
6938 frequently-made mistakes in our unit tests. Closes ticket 18241.
6940 o Minor features (unix domain sockets):
6941 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
6942 Unix domain sockets without checking the permissions on the parent
6943 directory. (Tor checks permissions by default because some
6944 operating systems only check permissions on the parent directory.
6945 However, some operating systems do look at permissions on the
6946 socket, and tor's default check is unneeded.) Closes ticket 18458.
6949 o Minor bugfixes (exit policies, security):
6950 - Refresh an exit relay's exit policy when interface addresses
6951 change. Previously, tor only refreshed the exit policy when the
6952 configured external address changed. Fixes bug 18208; bugfix on
6953 0.2.7.3-rc. Patch by teor.
6955 o Minor bugfixes (security, hidden services):
6956 - Prevent hidden services connecting to client-supplied rendezvous
6957 addresses that are reserved as internal or multicast. Fixes bug
6958 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6960 o Minor bugfixes (build):
6961 - Do not link the unit tests against both the testing and non-
6962 testing versions of the static libraries. Fixes bug 18490; bugfix
6964 - Avoid spurious failures from configure files related to calling
6965 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
6966 0.2.0.1-alpha. Patch from "cypherpunks".
6967 - Silence spurious clang-scan warnings in the ed25519_donna code by
6968 explicitly initializing some objects. Fixes bug 18384; bugfix on
6969 0.2.7.2-alpha. Patch by teor.
6971 o Minor bugfixes (client, bootstrap):
6972 - Count receipt of new microdescriptors as progress towards
6973 bootstrapping. Previously, with EntryNodes set, Tor might not
6974 successfully repopulate the guard set on bootstrapping. Fixes bug
6975 16825; bugfix on 0.2.3.1-alpha.
6977 o Minor bugfixes (code correctness):
6978 - Update to the latest version of Trunnel, which tries harder to
6979 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
6980 by clang address sanitizer. Fixes bug 18373; bugfix
6983 o Minor bugfixes (configuration):
6984 - Fix a tiny memory leak when parsing a port configuration ending in
6985 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
6987 o Minor bugfixes (containers):
6988 - If we somehow attempt to construct a heap with more than
6989 1073741822 elements, avoid an integer overflow when maintaining
6990 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
6992 o Minor bugfixes (correctness):
6993 - Fix a bad memory handling bug that would occur if we had queued a
6994 cell on a channel's incoming queue. Fortunately, we can't actually
6995 queue a cell like that as our code is constructed today, but it's
6996 best to avoid this kind of error, even if there isn't any code
6997 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
6999 o Minor bugfixes (directory):
7000 - When generating a URL for a directory server on an IPv6 address,
7001 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
7002 on 0.2.3.9-alpha. Patch from Malek.
7004 o Minor bugfixes (fallback directory mirrors):
7005 - When requesting extrainfo descriptors from a trusted directory
7006 server, check whether it is an authority or a fallback directory
7007 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
7008 0.2.4.7-alpha. Reported by atagar, patch by teor.
7010 o Minor bugfixes (hidden service, client):
7011 - Handle the case where the user makes several fast consecutive
7012 requests to the same .onion address. Previously, the first six
7013 requests would each trigger a descriptor fetch, each picking a
7014 directory (there are 6 overall) and the seventh one would fail
7015 because no directories were left, thereby triggering a close on
7016 all current directory connections asking for the hidden service.
7017 The solution here is to not close the connections if we have
7018 pending directory fetches. Fixes bug 15937; bugfix
7021 o Minor bugfixes (hidden service, control port):
7022 - Add the onion address to the HS_DESC event for the UPLOADED action
7023 both on success or failure. It was previously hardcoded with
7024 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
7026 o Minor bugfixes (hidden service, directory):
7027 - Bridges now refuse "rendezvous2" (hidden service descriptor)
7028 publish attempts. Suggested by ticket 18332.
7030 o Minor bugfixes (linux seccomp2 sandbox):
7031 - Allow the setrlimit syscall, and the prlimit and prlimit64
7032 syscalls, which some libc implementations use under the hood.
7033 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
7034 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
7035 enabled and no DNS resolvers configured. This should help TAILS
7036 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
7037 - Fix the sandbox's interoperability with unix domain sockets under
7038 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
7040 o Minor bugfixes (logging):
7041 - When logging information about an unparsable networkstatus vote or
7042 consensus, do not say "vote" when we mean consensus. Fixes bug
7043 18368; bugfix on 0.2.0.8-alpha.
7044 - Scrub service name in "unrecognized service ID" log messages.
7045 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
7046 - Downgrade logs and backtraces about IP versions to info-level.
7047 Only log backtraces once each time tor runs. Assists in diagnosing
7048 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
7049 Christian, patch by teor.
7051 o Minor bugfixes (memory safety):
7052 - Avoid freeing an uninitialized pointer when opening a socket fails
7053 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
7054 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
7056 - Correctly duplicate addresses in get_interface_address6_list().
7057 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
7058 patch by "cypherpunks".
7059 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
7061 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
7062 18672; bugfix on 0.2.5.1-alpha.
7064 o Minor bugfixes (private directory):
7065 - Prevent a race condition when creating private directories. Fixes
7066 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
7067 Patch from jsturgix. Found with Flawfinder.
7069 o Minor bugfixes (test networks, IPv6):
7070 - Allow internal IPv6 addresses in descriptors in test networks.
7071 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
7074 o Minor bugfixes (testing):
7075 - We no longer disable assertions in the unit tests when coverage is
7076 enabled. Instead, we require you to say --disable-asserts-in-tests
7077 to the configure script if you need assertions disabled in the
7078 unit tests (for example, if you want to perform branch coverage).
7079 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
7081 o Minor bugfixes (time parsing):
7082 - Avoid overflow in tor_timegm when parsing dates in and after 2038
7083 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
7084 0.0.2pre14. Patch by teor.
7086 o Minor bugfixes (tor-gencert):
7087 - Correctly handle the case where an authority operator enters a
7088 passphrase but sends an EOF before sending a newline. Fixes bug
7089 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
7091 o Code simplification and refactoring:
7092 - Quote all the string interpolations in configure.ac -- even those
7093 which we are pretty sure can't contain spaces. Closes ticket
7094 17744. Patch from zerosion.
7095 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
7096 inplace, so there's no need to have a separate implementation for
7097 the non-inplace code. Closes ticket 18258. Patch from Malek.
7098 - Simplify return types for some crypto functions that can't
7099 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
7102 - Change build messages to refer to "Fedora" instead of "Fedora
7103 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
7104 Patches from "icanhasaccount" and "cypherpunks".
7107 - We no longer maintain an internal freelist in memarea.c.
7108 Allocators should be good enough to make this code unnecessary,
7109 and it's doubtful that it ever had any performance benefit.
7112 - Fix several warnings from clang's address sanitizer produced in
7114 - Treat backtrace test failures as expected on FreeBSD until we
7115 solve bug 17808. Closes ticket 18204.
7118 Changes in version 0.2.8.1-alpha - 2016-02-04
7119 Tor 0.2.8.1-alpha is the first alpha release in its series. It
7120 includes numerous small features and bugfixes against previous Tor
7121 versions, and numerous small infrastructure improvements. The most
7122 notable features are a set of improvements to the directory subsystem.
7124 o Major features (security, Linux):
7125 - When Tor starts as root on Linux and is told to switch user ID, it
7126 can now retain the capability to bind to low ports. By default,
7127 Tor will do this only when it's switching user ID and some low
7128 ports have been configured. You can change this behavior with the
7129 new option KeepBindCapabilities. Closes ticket 8195.
7131 o Major features (directory system):
7132 - When bootstrapping multiple consensus downloads at a time, use the
7133 first one that starts downloading, and close the rest. This
7134 reduces failures when authorities or fallback directories are slow
7135 or down. Together with the code for feature 15775, this feature
7136 should reduces failures due to fallback churn. Implements ticket
7137 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
7138 "mikeperry" and "teor".
7139 - Include a trial list of 21 default fallback directories, generated
7140 in January 2016, based on an opt-in survey of suitable relays.
7141 Doing this should make clients bootstrap more quickly and reliably,
7142 and reduce the load on the directory authorities. Closes ticket
7143 15775. Patch by "teor".
7144 Candidates identified using an OnionOO script by "weasel", "teor",
7145 "gsathya", and "karsten".
7146 - Previously only relays that explicitly opened a directory port
7147 (DirPort) accepted directory requests from clients. Now all
7148 relays, with and without a DirPort, accept and serve tunneled
7149 directory requests that they receive through their ORPort. You can
7150 disable this behavior using the new DirCache option. Closes
7153 o Major key updates:
7154 - Update the V3 identity key for the dannenberg directory authority:
7155 it was changed on 18 November 2015. Closes task 17906. Patch
7158 o Minor features (security, clock):
7159 - Warn when the system clock appears to move back in time (when the
7160 state file was last written in the future). Tor doesn't know that
7161 consensuses have expired if the clock is in the past. Patch by
7162 "teor". Implements ticket 17188.
7164 o Minor features (security, exit policies):
7165 - ExitPolicyRejectPrivate now rejects more private addresses by
7166 default. Specifically, it now rejects the relay's outbound bind
7167 addresses (if configured), and the relay's configured port
7168 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
7169 0.2.0.11-alpha. Patch by "teor".
7171 o Minor features (security, memory erasure):
7172 - Set the unused entries in a smartlist to NULL. This helped catch
7173 a (harmless) bug, and shouldn't affect performance too much.
7174 Implements ticket 17026.
7175 - Use SecureMemoryWipe() function to securely clean memory on
7176 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
7177 Implements feature 17986.
7178 - Use explicit_bzero or memset_s when present. Previously, we'd use
7179 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
7180 from <logan@hackers.mu> and <selven@hackers.mu>.
7181 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7182 zero size. Check size argument to memwipe() for underflow. Fixes
7183 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7186 o Minor features (security, RNG):
7187 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
7188 positively are not allowed to fail. Previously we depended on
7189 internal details of OpenSSL's behavior. Closes ticket 17686.
7190 - Never use the system entropy output directly for anything besides
7191 seeding the PRNG. When we want to generate important keys, instead
7192 of using system entropy directly, we now hash it with the PRNG
7193 stream. This may help resist certain attacks based on broken OS
7194 entropy implementations. Closes part of ticket 17694.
7195 - Use modern system calls (like getentropy() or getrandom()) to
7196 generate strong entropy on platforms that have them. Closes
7199 o Minor features (accounting):
7200 - Added two modes to the AccountingRule option: One for limiting
7201 only the number of bytes sent ("AccountingRule out"), and one for
7202 limiting only the number of bytes received ("AccountingRule in").
7203 Closes ticket 15989; patch from "unixninja92".
7205 o Minor features (build):
7206 - Since our build process now uses "make distcheck", we no longer
7207 force "make dist" to depend on "make check". Closes ticket 17893;
7208 patch from "cypherpunks."
7209 - Tor now builds successfully with the recent OpenSSL 1.1
7210 development branch, and with the latest LibreSSL. Closes tickets
7211 17549, 17921, and 17984.
7213 o Minor features (controller):
7214 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
7215 tickets 16774 and 17817. Patch by George Tankersley.
7216 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
7217 service descriptor from a service's local hidden service
7218 descriptor cache. Closes ticket 14846.
7219 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
7220 controllers can examine the the reject rules added by
7221 ExitPolicyRejectPrivate. This makes it easier for stem to display
7224 o Minor features (crypto):
7225 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
7227 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
7228 - When allocating a digest state object, allocate no more space than
7229 we actually need. Previously, we would allocate as much space as
7230 the state for the largest algorithm would need. This change saves
7231 up to 672 bytes per circuit. Closes ticket 17796.
7232 - Improve performance when hashing non-multiple of 8 sized buffers,
7233 based on Andrew Moon's public domain SipHash-2-4 implementation.
7234 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
7236 o Minor features (directory downloads):
7237 - Wait for busy authorities and fallback directories to become non-
7238 busy when bootstrapping. (A similar change was made in 6c443e987d
7239 for directory caches chosen from the consensus.) Closes ticket
7240 17864; patch by "teor".
7241 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
7242 directory mirrors. The default is 1; set it to 0 to disable
7243 fallbacks. Implements ticket 17576. Patch by "teor".
7245 o Minor features (geoip):
7246 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
7249 o Minor features (IPv6):
7250 - Add an argument 'ipv6=address:orport' to the DirAuthority and
7251 FallbackDir torrc options, to specify an IPv6 address for an
7252 authority or fallback directory. Add hard-coded ipv6 addresses for
7253 directory authorities that have them. Closes ticket 17327; patch
7254 from Nick Mathewson and "teor".
7255 - Add address policy assume_action support for IPv6 addresses.
7256 - Limit IPv6 mask bits to 128.
7257 - Warn when comparing against an AF_UNSPEC address in a policy, it's
7258 almost always a bug. Closes ticket 17863; patch by "teor".
7259 - Allow users to configure directory authorities and fallback
7260 directory servers with IPv6 addresses and ORPorts. Resolves
7262 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
7263 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
7264 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
7265 17638; bugfix on 0.0.2pre8. Patch by "teor".
7267 o Minor features (logging):
7268 - When logging to syslog, allow a tag to be added to the syslog
7269 identity (the string prepended to every log message). The tag can
7270 be configured with SyslogIdentityTag and defaults to none. Setting
7271 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
7274 o Minor features (portability):
7275 - Use timingsafe_memcmp() where available. Closes ticket 17944;
7276 patch from <logan@hackers.mu>.
7278 o Minor features (relay, address discovery):
7279 - Add a family argument to get_interface_addresses_raw() and
7280 subfunctions to make network interface address interogation more
7281 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
7282 types of interfaces from the operating system. Resolves
7284 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
7285 fails to enumerate interface addresses using the platform-specific
7286 API, have it rely on the UDP socket fallback technique to try and
7287 find out what IP addresses (both IPv4 and IPv6) our machine has.
7288 Resolves ticket 17951.
7290 o Minor features (replay cache):
7291 - The replay cache now uses SHA256 instead of SHA1. Implements
7292 feature 8961. Patch by "teor", issue reported by "rransom".
7294 o Minor features (unix file permissions):
7295 - Defer creation of Unix sockets until after setuid. This avoids
7296 needing CAP_CHOWN and CAP_FOWNER when using systemd's
7297 CapabilityBoundingSet, or chown and fowner when using SELinux.
7298 Implements part of ticket 17562. Patch from Jamie Nguyen.
7299 - If any directory created by Tor is marked as group readable, the
7300 filesystem group is allowed to be either the default GID or the
7301 root user. Allowing root to read the DataDirectory prevents the
7302 need for CAP_READ_SEARCH when using systemd's
7303 CapabilityBoundingSet, or dac_read_search when using SELinux.
7304 Implements part of ticket 17562. Patch from Jamie Nguyen.
7305 - Introduce a new DataDirectoryGroupReadable option. If it is set to
7306 1, the DataDirectory will be made readable by the default GID.
7307 Implements part of ticket 17562. Patch from Jamie Nguyen.
7309 o Minor bugfixes (accounting):
7310 - The max bandwidth when using 'AccountRule sum' is now correctly
7311 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
7314 o Minor bugfixes (code correctness):
7315 - When closing an entry connection, generate a warning if we should
7316 have sent an end cell for it but we haven't. Fixes bug 17876;
7317 bugfix on 0.2.3.2-alpha.
7318 - Assert that allocated memory held by the reputation code is freed
7319 according to its internal counters. Fixes bug 17753; bugfix
7321 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
7324 o Minor bugfixes (compilation):
7325 - Mark all object files that include micro-revision.i as depending
7326 on it, so as to make parallel builds more reliable. Fixes bug
7327 17826; bugfix on 0.2.5.1-alpha.
7328 - Don't try to use the pthread_condattr_setclock() function unless
7329 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
7330 17819; bugfix on 0.2.6.3-alpha.
7331 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
7333 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
7334 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
7335 - Fix search for libevent libraries on OpenBSD (and other systems
7336 that install libevent 1 and libevent 2 in parallel). Fixes bug
7337 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
7338 - Isolate environment variables meant for tests from the rest of the
7339 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
7340 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
7342 - Remove config.log only from make distclean, not from make clean.
7343 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
7345 o Minor bugfixes (crypto):
7346 - Check the return value of HMAC() and assert on failure. Fixes bug
7347 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
7349 o Minor bugfixes (fallback directories):
7350 - Mark fallbacks as "too busy" when they return a 503 response,
7351 rather than just marking authorities. Fixes bug 17572; bugfix on
7352 0.2.4.7-alpha. Patch by "teor".
7354 o Minor bugfixes (IPv6):
7355 - Update the limits in max_dl_per_request for IPv6 address length.
7356 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
7358 o Minor bugfixes (linux seccomp2 sandbox):
7359 - Fix a crash when using offline master ed25519 keys with the Linux
7360 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
7362 o Minor bugfixes (logging):
7363 - In log messages that include a function name, use __FUNCTION__
7364 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
7365 with clang __PRETTY_FUNCTION__ has extra information we don't
7366 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
7368 - Remove needless quotes from a log message about unparseable
7369 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
7371 o Minor bugfixes (portability):
7372 - Remove an #endif from configure.ac so that we correctly detect the
7373 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
7376 o Minor bugfixes (relays):
7377 - Check that both the ORPort and DirPort (if present) are reachable
7378 before publishing a relay descriptor. Otherwise, relays publish a
7379 descriptor with DirPort 0 when the DirPort reachability test takes
7380 longer than the ORPort reachability test. Fixes bug 18050; bugfix
7381 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
7383 o Minor bugfixes (relays, hidden services):
7384 - Refuse connection requests to private OR addresses unless
7385 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
7386 then refuse to send any cells to a private address. Fixes bugs
7387 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
7389 o Minor bugfixes (safe logging):
7390 - When logging a malformed hostname received through socks4, scrub
7391 it if SafeLogging says we should. Fixes bug 17419; bugfix
7394 o Minor bugfixes (statistics code):
7395 - Consistently check for overflow in round_*_to_next_multiple_of
7396 functions, and add unit tests with additional and maximal values.
7397 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
7398 - Handle edge cases in the laplace functions: avoid division by
7399 zero, avoid taking the log of zero, and silence clang type
7400 conversion warnings using round and trunc. Add unit tests for edge
7401 cases with maximal values. Fixes part of bug 13192; bugfix
7404 o Minor bugfixes (testing):
7405 - The test for log_heartbeat was incorrectly failing in timezones
7406 with non-integer offsets. Instead of comparing the end of the time
7407 string against a constant, compare it to the output of
7408 format_local_iso_time when given the correct input. Fixes bug
7409 18039; bugfix on 0.2.5.4-alpha.
7410 - Make unit tests pass on IPv6-only systems, and systems without
7411 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
7412 bugfix on 0.2.7.3-rc. Patch by "teor".
7413 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
7415 - Check the full results of SHA256 and SHA512 digests in the unit
7416 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
7418 o Code simplification and refactoring:
7419 - Move logging of redundant policy entries in
7420 policies_parse_exit_policy_internal into its own function. Closes
7421 ticket 17608; patch from "juce".
7422 - Extract the more complicated parts of circuit_mark_for_close()
7423 into a new function that we run periodically before circuits are
7424 freed. This change removes more than half of the functions
7425 currently in the "blob". Closes ticket 17218.
7426 - Clean up a little duplicated code in
7427 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
7429 - Decouple the list of streams waiting to be attached to circuits
7430 from the overall connection list. This change makes it possible to
7431 attach streams quickly while simplifying Tor's callgraph and
7432 avoiding O(N) scans of the entire connection list. Closes
7434 - When a direct directory request fails immediately on launch,
7435 instead of relaunching that request from inside the code that
7436 launches it, instead mark the connection for teardown. This change
7437 simplifies Tor's callback and prevents the directory-request
7438 launching code from invoking itself recursively. Closes
7440 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
7441 use them. Closes ticket 17926.
7444 - Add a description of the correct use of the '--keygen' command-
7445 line option. Closes ticket 17583; based on text by 's7r'.
7446 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
7447 - Explain actual minima for BandwidthRate. Closes ticket 16382.
7448 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
7449 - Mention torspec URL in the manpage and point the reader to it
7450 whenever we mention a document that belongs in torspce. Fixes
7454 - Remove client-side support for connecting to Tor relays running
7455 versions of Tor before 0.2.3.6-alpha. These relays didn't support
7456 the v3 TLS handshake protocol, and are no longer allowed on the
7457 Tor network. Implements the client side of ticket 11150. Based on
7458 patches by Tom van der Woerdt.
7461 - Add unit tests to check for common RNG failure modes, such as
7462 returning all zeroes, identical values, or incrementing values
7463 (OpenSSL's rand_predictable feature). Patch by "teor".
7464 - Log more information when the backtrace tests fail. Closes ticket
7465 17892. Patch from "cypherpunks."
7466 - Always test both ed25519 backends, so that we can be sure that our
7467 batch-open replacement code works. Part of ticket 16794.
7468 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
7469 portion of ticket 16831.
7470 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
7471 util_format.c, directory.c, and options_validate.c. Closes tickets
7472 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
7474 - Unit tests for directory_handle_command_get. Closes ticket 17004.
7475 Patch from Reinaldo de Souza Jr.
7478 Changes in version 0.2.7.6 - 2015-12-10
7479 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
7480 well as a minor bug in hidden service reliability.
7482 o Major bugfixes (guard selection):
7483 - Actually look at the Guard flag when selecting a new directory
7484 guard. When we implemented the directory guard design, we
7485 accidentally started treating all relays as if they have the Guard
7486 flag during guard selection, leading to weaker anonymity and worse
7487 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7490 o Minor features (geoip):
7491 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
7494 o Minor bugfixes (compilation):
7495 - When checking for net/pfvar.h, include netinet/in.h if possible.
7496 This fixes transparent proxy detection on OpenBSD. Fixes bug
7497 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
7498 - Fix a compilation warning with Clang 3.6: Do not check the
7499 presence of an address which can never be NULL. Fixes bug 17781.
7501 o Minor bugfixes (correctness):
7502 - When displaying an IPv6 exit policy, include the mask bits
7503 correctly even when the number is greater than 31. Fixes bug
7504 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
7505 - The wrong list was used when looking up expired intro points in a
7506 rend service object, causing what we think could be reachability
7507 issues for hidden services, and triggering a BUG log. Fixes bug
7508 16702; bugfix on 0.2.7.2-alpha.
7509 - Fix undefined behavior in the tor_cert_checksig function. Fixes
7510 bug 17722; bugfix on 0.2.7.2-alpha.
7513 Changes in version 0.2.7.5 - 2015-11-20
7514 The Tor 0.2.7 release series is dedicated to the memory of Tor user
7515 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
7516 tirelessly to advocate human rights regardless of national borders,
7517 and oppose the encroachments of mass surveillance. He opposed national
7518 exceptionalism, he brought clarity to legal and policy debates, he
7519 understood and predicted the impact of mass surveillance on the world,
7520 and he laid the groundwork for resisting it. While serving on the Tor
7521 Project's board of directors, he brought us his uncompromising focus
7522 on technical excellence in the service of humankind. Caspar was an
7523 inimitable force for good and a wonderful friend. He was kind,
7524 humorous, generous, gallant, and believed we should protect one
7525 another without exception. We honor him here for his ideals, his
7526 efforts, and his accomplishments. Please honor his memory with works
7527 that would make him proud.
7529 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
7531 The 0.2.7 series adds a more secure identity key type for relays,
7532 improves cryptography performance, resolves several longstanding
7533 hidden-service performance issues, improves controller support for
7534 hidden services, and includes small bugfixes and performance
7535 improvements throughout the program. This release series also includes
7536 more tests than before, and significant simplifications to which parts
7537 of Tor invoke which others.
7539 (This release contains no code changes since 0.2.7.4-rc.)
7542 Changes in version 0.2.7.4-rc - 2015-10-21
7543 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
7544 fixes some important memory leaks, and a scary-looking (but mostly
7545 harmless in practice) invalid-read bug. It also has a few small
7546 bugfixes, notably fixes for compilation and portability on different
7547 platforms. If no further significant bounds are found, the next
7548 release will the the official stable release.
7550 o Major bugfixes (security, correctness):
7551 - Fix an error that could cause us to read 4 bytes before the
7552 beginning of an openssl string. This bug could be used to cause
7553 Tor to crash on systems with unusual malloc implementations, or
7554 systems with unusual hardening installed. Fixes bug 17404; bugfix
7557 o Major bugfixes (correctness):
7558 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
7559 bug 17401; bugfix on 0.2.7.3-rc.
7561 o Major bugfixes (memory leaks):
7562 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
7563 17398; bugfix on 0.2.6.1-alpha.
7564 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
7565 17402; bugfix on 0.2.7.3-rc.
7566 - Fix a memory leak when reading an expired signing key from disk.
7567 Fixes bug 17403; bugfix on 0.2.7.2-rc.
7569 o Minor features (geoIP):
7570 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
7573 o Minor bugfixes (compilation):
7574 - Repair compilation with the most recent (unreleased, alpha)
7575 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
7576 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
7577 17251; bugfix on 0.2.7.2-alpha.
7578 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
7579 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
7581 o Minor bugfixes (portability):
7582 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
7583 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
7586 o Minor bugfixes (sandbox):
7587 - Add the "hidserv-stats" filename to our sandbox filter for the
7588 HiddenServiceStatistics option to work properly. Fixes bug 17354;
7589 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
7591 o Minor bugfixes (testing):
7592 - Add unit tests for get_interface_address* failure cases. Fixes bug
7593 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
7594 - Fix breakage when running 'make check' with BSD make. Fixes bug
7595 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
7596 - Make the get_ifaddrs_* unit tests more tolerant of different
7597 network configurations. (Don't assume every test box has an IPv4
7598 address, and don't assume every test box has a non-localhost
7599 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
7600 - Skip backtrace tests when backtrace support is not compiled in.
7601 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
7605 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
7606 - Note that HiddenServicePorts can take a unix domain socket. Closes
7610 Changes in version 0.2.7.3-rc - 2015-09-25
7611 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
7612 contains numerous usability fixes for Ed25519 keys, safeguards against
7613 several misconfiguration problems, significant simplifications to
7614 Tor's callgraph, and numerous bugfixes and small features.
7616 This is the most tested release of Tor to date. The unit tests cover
7617 39.40% of the code, and the integration tests (accessible with "make
7618 test-full-online", requiring stem and chutney and a network
7619 connection) raise the coverage to 64.49%.
7621 o Major features (security, hidden services):
7622 - Hidden services, if using the EntryNodes option, are required to
7623 use more than one EntryNode, in order to avoid a guard discovery
7624 attack. (This would only affect people who had configured hidden
7625 services and manually specified the EntryNodes option with a
7626 single entry-node. The impact was that it would be easy to
7627 remotely identify the guard node used by such a hidden service.
7628 See ticket for more information.) Fixes ticket 14917.
7630 o Major features (Ed25519 keys, keypinning):
7631 - The key-pinning option on directory authorities is now advisory-
7632 only by default. In a future version, or when the AuthDirPinKeys
7633 option is set, pins are enforced again. Disabling key-pinning
7634 seemed like a good idea so that we can survive the fallout of any
7635 usability problems associated with Ed25519 keys. Closes
7638 o Major features (Ed25519 performance):
7639 - Improve the speed of Ed25519 operations and Curve25519 keypair
7640 generation when built targeting 32 bit x86 platforms with SSE2
7641 available. Implements ticket 16535.
7642 - Improve the runtime speed of Ed25519 signature verification by
7643 using Ed25519-donna's batch verification support. Implements
7646 o Major features (performance testing):
7647 - The test-network.sh script now supports performance testing.
7648 Requires corresponding chutney performance testing changes. Patch
7649 by "teor". Closes ticket 14175.
7651 o Major features (relay, Ed25519):
7652 - Significant usability improvements for Ed25519 key management. Log
7653 messages are better, and the code can recover from far more
7654 failure conditions. Thanks to "s7r" for reporting and diagnosing
7656 - Add a new OfflineMasterKey option to tell Tor never to try loading
7657 or generating a secret Ed25519 identity key. You can use this in
7658 combination with tor --keygen to manage offline and/or encrypted
7659 Ed25519 keys. Implements ticket 16944.
7660 - Add a --newpass option to allow changing or removing the
7661 passphrase of an encrypted key with tor --keygen. Implements part
7663 - On receiving a HUP signal, check to see whether the Ed25519
7664 signing key has changed, and reload it if so. Closes ticket 16790.
7666 o Major bugfixes (relay, Ed25519):
7667 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
7668 0.2.7.2-alpha. Reported by "s7r".
7669 - Improve handling of expired signing keys with offline master keys.
7670 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
7672 o Minor features (client-side privacy):
7673 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
7674 lifespan when IsolateSOCKSAuth and streams with SOCKS
7675 authentication are attached to the circuit. This allows
7676 applications like TorBrowser to manage circuit lifetime on their
7677 own. Implements feature 15482.
7678 - When logging malformed hostnames from SOCKS5 requests, respect
7679 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
7681 o Minor features (compilation):
7682 - Give a warning as early as possible when trying to build with an
7683 unsupported OpenSSL version. Closes ticket 16901.
7684 - Fail during configure if we're trying to build against an OpenSSL
7685 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
7686 which started requiring ECC.
7688 o Minor features (geoip):
7689 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
7692 o Minor features (hidden services):
7693 - Relays need to have the Fast flag to get the HSDir flag. As this
7694 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
7695 drop. This change should make some attacks against the hidden
7696 service directory system harder. Fixes ticket 15963.
7697 - Turn on hidden service statistics collection by setting the torrc
7698 option HiddenServiceStatistics to "1" by default. (This keeps
7699 track only of the fraction of traffic used by hidden services, and
7700 the total number of hidden services in existence.) Closes
7702 - Client now uses an introduction point failure cache to know when
7703 to fetch or keep a descriptor in their cache. Previously, failures
7704 were recorded implicitly, but not explicitly remembered. Closes
7707 o Minor features (testing, authorities, documentation):
7708 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
7709 explicitly manage consensus flags in testing networks. Patch by
7710 "robgjansen", modified by "teor". Implements part of ticket 14882.
7712 o Minor bugfixes (security, exit policies):
7713 - ExitPolicyRejectPrivate now also rejects the relay's published
7714 IPv6 address (if any), and any publicly routable IPv4 or IPv6
7715 addresses on any local interfaces. ticket 17027. Patch by "teor".
7716 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
7718 o Minor bug fixes (torrc exit policies):
7719 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
7720 produce IPv6 wildcard addresses. Previously they would produce
7721 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
7722 of bug 16069; bugfix on 0.2.4.7-alpha.
7723 - When parsing torrc ExitPolicies, we now warn for a number of cases
7724 where the user's intent is likely to differ from Tor's actual
7725 behavior. These include: using an IPv4 address with an accept6 or
7726 reject6 line; using "private" on an accept6 or reject6 line; and
7727 including any ExitPolicy lines after accept *:* or reject *:*.
7728 Related to ticket 16069.
7729 - When parsing torrc ExitPolicies, we now issue an info-level
7730 message when expanding an "accept/reject *" line to include both
7731 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
7732 - In each instance above, usage advice is provided to avoid the
7733 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
7734 16069; bugfix on 0.2.4.7-alpha.
7736 o Minor bugfixes (authority):
7737 - Don't assign "HSDir" to a router if it isn't Valid and Running.
7738 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
7739 - Downgrade log messages about Ed25519 key issues if they are in old
7740 cached router descriptors. Fixes part of bug 16286; bugfix
7742 - When we find an Ed25519 key issue in a cached descriptor, stop
7743 saying the descriptor was just "uploaded". Fixes another part of
7744 bug 16286; bugfix on 0.2.7.2-alpha.
7746 o Minor bugfixes (control port):
7747 - Repair a warning and a spurious result when getting the maximum
7748 number of file descriptors from the controller. Fixes bug 16697;
7749 bugfix on 0.2.7.2-alpha.
7751 o Minor bugfixes (correctness):
7752 - When calling channel_free_list(), avoid calling smartlist_remove()
7753 while inside a FOREACH loop. This partially reverts commit
7754 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
7755 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
7757 o Minor bugfixes (documentation):
7758 - Advise users on how to configure separate IPv4 and IPv6 exit
7759 policies in the manpage and sample torrcs. Related to ticket 16069.
7760 - Fix the usage message of tor-resolve(1) so that it no longer lists
7761 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
7762 - Fix an error in the manual page and comments for
7763 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
7764 required "ORPort connectivity". While this is true, it is in no
7765 way unique to the HSDir flag. Of all the flags, only HSDirs need a
7766 DirPort configured in order for the authorities to assign that
7767 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
7770 o Minor bugfixes (Ed25519):
7771 - Fix a memory leak when reading router descriptors with expired
7772 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
7774 o Minor bugfixes (linux seccomp2 sandbox):
7775 - Allow bridge authorities to run correctly under the seccomp2
7776 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
7777 - Allow routers with ed25519 keys to run correctly under the
7778 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
7780 o Minor bugfixes (open file limit):
7781 - Fix set_max_file_descriptors() to set by default the max open file
7782 limit to the current limit when setrlimit() fails. Fixes bug
7783 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
7785 o Minor bugfixes (portability):
7786 - Try harder to normalize the exit status of the Tor process to the
7787 standard-provided range. Fixes bug 16975; bugfix on every version
7789 - Check correctly for Windows socket errors in the workqueue
7790 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
7791 - Fix the behavior of crypto_rand_time_range() when told to consider
7792 times before 1970. (These times were possible when running in a
7793 simulated network environment where time()'s output starts at
7794 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
7795 - Restore correct operation of TLS client-cipher detection on
7796 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
7798 o Minor bugfixes (relay):
7799 - Ensure that worker threads actually exit when a fatal error or
7800 shutdown is indicated. This fix doesn't currently affect the
7801 behavior of Tor, because Tor workers never indicates fatal error
7802 or shutdown except in the unit tests. Fixes bug 16868; bugfix
7804 - Unblock threads before releasing the work queue mutex to ensure
7805 predictable scheduling behavior. Fixes bug 16644; bugfix
7808 o Code simplification and refactoring:
7809 - Change the function that's called when we need to retry all
7810 downloads so that it only reschedules the downloads to happen
7811 immediately, rather than launching them all at once itself. This
7812 further simplifies Tor's callgraph.
7813 - Move some format-parsing functions out of crypto.c and
7814 crypto_curve25519.c into crypto_format.c and/or util_format.c.
7815 - Move the client-only parts of init_keys() into a separate
7816 function. Closes ticket 16763.
7817 - Simplify the microdesc_free() implementation so that it no longer
7818 appears (to code analysis tools) to potentially invoke a huge
7819 suite of other microdesc functions.
7820 - Simply the control graph further by deferring the inner body of
7821 directory_all_unreachable() into a callback. Closes ticket 16762.
7822 - Treat the loss of an owning controller as equivalent to a SIGTERM
7823 signal. This removes a tiny amount of duplicated code, and
7824 simplifies our callgraph. Closes ticket 16788.
7825 - When generating an event to send to the controller, we no longer
7826 put the event over the network immediately. Instead, we queue
7827 these events, and use a Libevent callback to deliver them. This
7828 change simplifies Tor's callgraph by reducing the number of
7829 functions from which all other Tor functions are reachable. Closes
7831 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
7832 that try to scan or compile every file on Unix won't decide that
7834 - Remove the unused "nulterminate" argument from buf_pullup().
7837 - Recommend a 40 GB example AccountingMax in torrc.sample rather
7838 than a 4 GB max. Closes ticket 16742.
7839 - Include the TUNING document in our source tarball. It is referred
7840 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
7844 - The internal pure-C tor-fw-helper tool is now removed from the Tor
7845 distribution, in favor of the pure-Go clone available from
7846 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
7847 used by the C tor-fw-helper are not, in our opinion, very
7848 confidence- inspiring in their secure-programming techniques.
7849 Closes ticket 13338.
7850 - Remove the code that would try to aggressively flush controller
7851 connections while writing to them. This code was introduced in
7852 0.1.2.7-alpha, in order to keep output buffers from exceeding
7853 their limits. But there is no longer a maximum output buffer size,
7854 and flushing data in this way caused some undesirable recursions
7855 in our call graph. Closes ticket 16480.
7858 - Make "bridges+hs" the default test network. This tests almost all
7859 tor functionality during make test-network, while allowing tests
7860 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
7861 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
7862 (chutney). Patches by "teor".
7863 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
7864 by-side in the same parent directory. Closes ticket 16903. Patch
7866 - Use environment variables rather than autoconf substitutions to
7867 send variables from the build system to the test scripts. This
7868 change should be easier to maintain, and cause 'make distcheck' to
7869 work better than before. Fixes bug 17148.
7870 - Add a new set of callgraph analysis scripts that use clang to
7871 produce a list of which Tor functions are reachable from which
7872 other Tor functions. We're planning to use these to help simplify
7873 our code structure by identifying illogical dependencies.
7874 - Add new 'test-full' and 'test-full-online' targets to run all
7875 tests, including integration tests with stem and chutney.
7876 - Make the test-workqueue test work on Windows by initializing the
7877 network before we begin.
7878 - New make target (make test-network-all) to run multiple applicable
7879 chutney test cases. Patch from Teor; closes 16953.
7880 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
7881 functions in dns.c. Implements a portion of ticket 16831.
7882 - When building Tor with testing coverage enabled, run Chutney tests
7883 (if any) using the 'tor-cov' coverage binary.
7884 - When running test-network or test-stem, check for the absence of
7885 stem/chutney before doing any build operations.
7888 Changes in version 0.2.7.2-alpha - 2015-07-27
7889 This, the second alpha in the Tor 0.2.7 series, has a number of new
7890 features, including a way to manually pick the number of introduction
7891 points for hidden services, and the much stronger Ed25519 signing key
7892 algorithm for regular Tor relays (including support for encrypted
7893 offline identity keys in the new algorithm).
7895 Support for Ed25519 on relays is currently limited to signing router
7896 descriptors; later alphas in this series will extend Ed25519 key
7897 support to more parts of the Tor protocol.
7899 o Major features (Ed25519 identity keys, Proposal 220):
7900 - All relays now maintain a stronger identity key, using the Ed25519
7901 elliptic curve signature format. This master key is designed so
7902 that it can be kept offline. Relays also generate an online
7903 signing key, and a set of other Ed25519 keys and certificates.
7904 These are all automatically regenerated and rotated as needed.
7905 Implements part of ticket 12498.
7906 - Directory authorities now vote on Ed25519 identity keys along with
7907 RSA1024 keys. Implements part of ticket 12498.
7908 - Directory authorities track which Ed25519 identity keys have been
7909 used with which RSA1024 identity keys, and do not allow them to
7910 vary freely. Implements part of ticket 12498.
7911 - Microdescriptors now include Ed25519 identity keys. Implements
7912 part of ticket 12498.
7913 - Add support for offline encrypted Ed25519 master keys. To use this
7914 feature on your tor relay, run "tor --keygen" to make a new master
7915 key (or to make a new signing key if you already have a master
7916 key). Closes ticket 13642.
7918 o Major features (Hidden services):
7919 - Add the torrc option HiddenServiceNumIntroductionPoints, to
7920 specify a fixed number of introduction points. Its maximum value
7921 is 10 and default is 3. Using this option can increase a hidden
7922 service's reliability under load, at the cost of making it more
7923 visible that the hidden service is facing extra load. Closes
7925 - Remove the adaptive algorithm for choosing the number of
7926 introduction points, which used to change the number of
7927 introduction points (poorly) depending on the number of
7928 connections the HS sees. Closes ticket 4862.
7930 o Major features (onion key cross-certification):
7931 - Relay descriptors now include signatures of their own identity
7932 keys, made using the TAP and ntor onion keys. These signatures
7933 allow relays to prove ownership of their own onion keys. Because
7934 of this change, microdescriptors will no longer need to include
7935 RSA identity keys. Implements proposal 228; closes ticket 12499.
7937 o Major features (performance):
7938 - Improve the runtime speed of Ed25519 operations by using the
7939 public-domain Ed25519-donna by Andrew M. ("floodyberry").
7940 Implements ticket 16467.
7941 - Improve the runtime speed of the ntor handshake by using an
7942 optimized curve25519 basepoint scalarmult implementation from the
7943 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
7944 ideas by Adam Langley. Implements ticket 9663.
7946 o Major bugfixes (client-side privacy, also in 0.2.6.9):
7947 - Properly separate out each SOCKSPort when applying stream
7948 isolation. The error occurred because each port's session group
7949 was being overwritten by a default value when the listener
7950 connection was initialized. Fixes bug 16247; bugfix on
7951 0.2.6.3-alpha. Patch by "jojelino".
7953 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
7954 - Stop refusing to store updated hidden service descriptors on a
7955 client. This reverts commit 9407040c59218 (which indeed fixed bug
7956 14219, but introduced a major hidden service reachability
7957 regression detailed in bug 16381). This is a temporary fix since
7958 we can live with the minor issue in bug 14219 (it just results in
7959 some load on the network) but the regression of 16381 is too much
7960 of a setback. First-round fix for bug 16381; bugfix
7963 o Major bugfixes (hidden services):
7964 - When cannibalizing a circuit for an introduction point, always
7965 extend to the chosen exit node (creating a 4 hop circuit).
7966 Previously Tor would use the current circuit exit node, which
7967 changed the original choice of introduction point, and could cause
7968 the hidden service to skip excluded introduction points or
7969 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
7972 o Major bugfixes (open file limit):
7973 - The open file limit wasn't checked before calling
7974 tor_accept_socket_nonblocking(), which would make Tor exceed the
7975 limit. Now, before opening a new socket, Tor validates the open
7976 file limit just before, and if the max has been reached, return an
7977 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
7979 o Major bugfixes (stability, also in 0.2.6.10):
7980 - Stop crashing with an assertion failure when parsing certain kinds
7981 of malformed or truncated microdescriptors. Fixes bug 16400;
7982 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7983 by "cypherpunks_backup".
7984 - Stop random client-side assertion failures that could occur when
7985 connecting to a busy hidden service, or connecting to a hidden
7986 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7989 o Minor features (directory authorities, security, also in 0.2.6.9):
7990 - The HSDir flag given by authorities now requires the Stable flag.
7991 For the current network, this results in going from 2887 to 2806
7992 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7993 attack by raising the effort for a relay to become Stable to
7994 require at the very least 7 days, while maintaining the 96 hours
7995 uptime requirement for HSDir. Implements ticket 8243.
7997 o Minor features (client):
7998 - Relax the validation of hostnames in SOCKS5 requests, allowing the
7999 character '_' to appear, in order to cope with domains observed in
8000 the wild that are serving non-RFC compliant records. Resolves
8002 - Relax the validation done to hostnames in SOCKS5 requests, and
8003 allow a single trailing '.' to cope with clients that pass FQDNs
8004 using that syntax to explicitly indicate that the domain name is
8005 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
8006 - Add GroupWritable and WorldWritable options to unix-socket based
8007 SocksPort and ControlPort options. These options apply to a single
8008 socket, and override {Control,Socks}SocketsGroupWritable. Closes
8011 o Minor features (control protocol):
8012 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
8013 the control protocol. Resolves ticket 15358.
8015 o Minor features (directory authorities):
8016 - Directory authorities no longer vote against the "Fast", "Stable",
8017 and "HSDir" flags just because they were going to vote against
8018 "Running": if the consensus turns out to be that the router was
8019 running, then the authority's vote should count. Patch from Peter
8020 Retzlaff; closes issue 8712.
8022 o Minor features (geoip, also in 0.2.6.10):
8023 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
8024 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
8026 o Minor features (hidden services):
8027 - Add the new options "HiddenServiceMaxStreams" and
8028 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
8029 limit the maximum number of simultaneous streams per circuit, and
8030 optionally tear down the circuit when the limit is exceeded. Part
8033 o Minor features (portability):
8034 - Use C99 variadic macros when the compiler is not GCC. This avoids
8035 failing compilations on MSVC, and fixes a log-file-based race
8036 condition in our old workarounds. Original patch from Gisle Vanem.
8038 o Minor bugfixes (compilation, also in 0.2.6.9):
8039 - Build with --enable-systemd correctly when libsystemd is
8040 installed, but systemd is not. Fixes bug 16164; bugfix on
8041 0.2.6.3-alpha. Patch from Peter Palfrader.
8043 o Minor bugfixes (controller):
8044 - Add the descriptor ID in each HS_DESC control event. It was
8045 missing, but specified in control-spec.txt. Fixes bug 15881;
8046 bugfix on 0.2.5.2-alpha.
8048 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
8049 - Check for failures from crypto_early_init, and refuse to continue.
8050 A previous typo meant that we could keep going with an
8051 uninitialized crypto library, and would have OpenSSL initialize
8052 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8053 when implementing ticket 4900. Patch by "teor".
8055 o Minor bugfixes (hidden services):
8056 - Fix a crash when reloading configuration while at least one
8057 configured and one ephemeral hidden service exists. Fixes bug
8058 16060; bugfix on 0.2.7.1-alpha.
8059 - Avoid crashing with a double-free bug when we create an ephemeral
8060 hidden service but adding it fails for some reason. Fixes bug
8061 16228; bugfix on 0.2.7.1-alpha.
8063 o Minor bugfixes (Linux seccomp2 sandbox):
8064 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
8065 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
8067 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
8068 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
8069 these when eventfd2() support is missing. Fixes bug 16363; bugfix
8070 on 0.2.6.3-alpha. Patch from "teor".
8072 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
8073 - Fix sandboxing to work when running as a relay, by allowing the
8074 renaming of secret_id_key, and allowing the eventfd2 and futex
8075 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
8077 - Allow systemd connections to work with the Linux seccomp2 sandbox
8078 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
8081 o Minor bugfixes (relay):
8082 - Fix a rarely-encountered memory leak when failing to initialize
8083 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
8086 o Minor bugfixes (systemd):
8087 - Fix an accidental formatting error that broke the systemd
8088 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
8089 - Tor's systemd unit file no longer contains extraneous spaces.
8090 These spaces would sometimes confuse tools like deb-systemd-
8091 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
8093 o Minor bugfixes (tests):
8094 - Use the configured Python executable when running test-stem-full.
8095 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
8097 o Minor bugfixes (tests, also in 0.2.6.9):
8098 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
8099 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
8101 o Minor bugfixes (threads, comments):
8102 - Always initialize return value in compute_desc_id in rendcommon.c
8103 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
8104 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
8105 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
8106 - Remove undefined directive-in-macro in test_util_writepid clang
8107 3.7 complains that using a preprocessor directive inside a macro
8108 invocation in test_util_writepid in test_util.c is undefined.
8109 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
8111 o Code simplification and refactoring:
8112 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
8113 to ensure they remain consistent and visible everywhere.
8114 - Remove some vestigial workarounds for the MSVC6 compiler. We
8115 haven't supported that in ages.
8116 - The link authentication code has been refactored for better
8117 testability and reliability. It now uses code generated with the
8118 "trunnel" binary encoding generator, to reduce the risk of bugs
8119 due to programmer error. Done as part of ticket 12498.
8122 - Include a specific and (hopefully) accurate documentation of the
8123 torrc file's meta-format in doc/torrc_format.txt. This is mainly
8124 of interest to people writing programs to parse or generate torrc
8125 files. This document is not a commitment to long-term
8126 compatibility; some aspects of the current format are a bit
8127 ridiculous. Closes ticket 2325.
8130 - Tor no longer supports copies of OpenSSL that are missing support
8131 for Elliptic Curve Cryptography. (We began using ECC when
8132 available in 0.2.4.8-alpha, for more safe and efficient key
8133 negotiation.) In particular, support for at least one of P256 or
8134 P224 is now required, with manual configuration needed if only
8135 P224 is available. Resolves ticket 16140.
8136 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
8137 on an operating system that has not upgraded to OpenSSL 1.0 or
8138 later, and you compile Tor from source, you will need to install a
8139 more recent OpenSSL to link Tor against.) These versions of
8140 OpenSSL are still supported by the OpenSSL, but the numerous
8141 cryptographic improvements in later OpenSSL releases makes them a
8142 clear choice. Resolves ticket 16034.
8143 - Remove the HidServDirectoryV2 option. Now all relays offer to
8144 store hidden service descriptors. Related to 16543.
8145 - Remove the VoteOnHidServDirectoriesV2 option, since all
8146 authorities have long set it to 1. Closes ticket 16543.
8149 - Document use of coverity, clang static analyzer, and clang dynamic
8150 undefined behavior and address sanitizers in doc/HACKING. Include
8151 detailed usage instructions in the blacklist. Patch by "teor".
8152 Closes ticket 15817.
8153 - The link authentication protocol code now has extensive tests.
8154 - The relay descriptor signature testing code now has
8156 - The test_workqueue program now runs faster, and is enabled by
8157 default as a part of "make check".
8158 - Now that OpenSSL has its own scrypt implementation, add an unit
8159 test that checks for interoperability between libscrypt_scrypt()
8160 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
8161 and rely on EVP_PBE_scrypt() whenever possible. Resolves
8165 Changes in version 0.2.6.10 - 2015-07-12
8166 Tor version 0.2.6.10 fixes some significant stability and hidden
8167 service client bugs, bulletproofs the cryptography init process, and
8168 fixes a bug when using the sandbox code with some older versions of
8169 Linux. Everyone running an older version, especially an older version
8170 of 0.2.6, should upgrade.
8172 o Major bugfixes (hidden service clients, stability):
8173 - Stop refusing to store updated hidden service descriptors on a
8174 client. This reverts commit 9407040c59218 (which indeed fixed bug
8175 14219, but introduced a major hidden service reachability
8176 regression detailed in bug 16381). This is a temporary fix since
8177 we can live with the minor issue in bug 14219 (it just results in
8178 some load on the network) but the regression of 16381 is too much
8179 of a setback. First-round fix for bug 16381; bugfix
8182 o Major bugfixes (stability):
8183 - Stop crashing with an assertion failure when parsing certain kinds
8184 of malformed or truncated microdescriptors. Fixes bug 16400;
8185 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
8186 by "cypherpunks_backup".
8187 - Stop random client-side assertion failures that could occur when
8188 connecting to a busy hidden service, or connecting to a hidden
8189 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
8192 o Minor features (geoip):
8193 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
8194 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
8196 o Minor bugfixes (crypto error-handling):
8197 - Check for failures from crypto_early_init, and refuse to continue.
8198 A previous typo meant that we could keep going with an
8199 uninitialized crypto library, and would have OpenSSL initialize
8200 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8201 when implementing ticket 4900. Patch by "teor".
8203 o Minor bugfixes (Linux seccomp2 sandbox):
8204 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
8205 these when eventfd2() support is missing. Fixes bug 16363; bugfix
8206 on 0.2.6.3-alpha. Patch from "teor".
8209 Changes in version 0.2.6.9 - 2015-06-11
8210 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
8211 requirements for receiving an HSDir flag, and addresses some other small
8212 bugs in the systemd and sandbox code. Clients using circuit isolation
8213 should upgrade; all directory authorities should upgrade.
8215 o Major bugfixes (client-side privacy):
8216 - Properly separate out each SOCKSPort when applying stream
8217 isolation. The error occurred because each port's session group was
8218 being overwritten by a default value when the listener connection
8219 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
8222 o Minor feature (directory authorities, security):
8223 - The HSDir flag given by authorities now requires the Stable flag.
8224 For the current network, this results in going from 2887 to 2806
8225 HSDirs. Also, it makes it harder for an attacker to launch a sybil
8226 attack by raising the effort for a relay to become Stable which
8227 takes at the very least 7 days to do so and by keeping the 96
8228 hours uptime requirement for HSDir. Implements ticket 8243.
8230 o Minor bugfixes (compilation):
8231 - Build with --enable-systemd correctly when libsystemd is
8232 installed, but systemd is not. Fixes bug 16164; bugfix on
8233 0.2.6.3-alpha. Patch from Peter Palfrader.
8235 o Minor bugfixes (Linux seccomp2 sandbox):
8236 - Fix sandboxing to work when running as a relaymby renaming of
8237 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
8238 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
8239 - Allow systemd connections to work with the Linux seccomp2 sandbox
8240 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
8243 o Minor bugfixes (tests):
8244 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
8245 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
8248 Changes in version 0.2.6.8 - 2015-05-21
8249 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
8250 fixes an authority-side bug in assigning the HSDir flag. All directory
8251 authorities should upgrade.
8253 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
8254 - Revert commit that made directory authorities assign the HSDir
8255 flag to relays without a DirPort; this was bad because such relays
8256 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
8259 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8260 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8261 a client authorized hidden service. Fixes bug 15823; bugfix
8264 o Minor features (geoip):
8265 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
8266 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
8270 Changes in version 0.2.7.1-alpha - 2015-05-12
8271 Tor 0.2.7.1-alpha is the first alpha release in its series. It
8272 includes numerous small features and bugfixes against previous Tor
8273 versions, and numerous small infrastructure improvements. The most
8274 notable features are several new ways for controllers to interact with
8275 the hidden services subsystem.
8277 o New system requirements:
8278 - Tor no longer includes workarounds to support Libevent versions
8279 before 1.3e. Libevent 2.0 or later is recommended. Closes
8282 o Major features (controller):
8283 - Add the ADD_ONION and DEL_ONION commands that allow the creation
8284 and management of hidden services via the controller. Closes
8286 - New "GETINFO onions/current" and "GETINFO onions/detached"
8287 commands to get information about hidden services created via the
8288 controller. Part of ticket 6411.
8289 - New HSFETCH command to launch a request for a hidden service
8290 descriptor. Closes ticket 14847.
8291 - New HSPOST command to upload a hidden service descriptor. Closes
8292 ticket 3523. Patch by "DonnchaC".
8294 o Major bugfixes (hidden services):
8295 - Revert commit that made directory authorities assign the HSDir
8296 flag to relays without a DirPort; this was bad because such relays
8297 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
8300 o Minor features (clock-jump tolerance):
8301 - Recover better when our clock jumps back many hours, like might
8302 happen for Tails or Whonix users who start with a very wrong
8303 hardware clock, use Tor to discover a more accurate time, and then
8304 fix their clock. Resolves part of ticket 8766.
8306 o Minor features (command-line interface):
8307 - Make --hash-password imply --hush to prevent unnecessary noise.
8308 Closes ticket 15542. Patch from "cypherpunks".
8309 - Print a warning whenever we find a relative file path being used
8310 as torrc option. Resolves issue 14018.
8312 o Minor features (controller):
8313 - Add DirAuthority lines for default directory authorities to the
8314 output of the "GETINFO config/defaults" command if not already
8315 present. Implements ticket 14840.
8316 - Controllers can now use "GETINFO hs/client/desc/id/..." to
8317 retrieve items from the client's hidden service descriptor cache.
8318 Closes ticket 14845.
8319 - Implement a new controller command "GETINFO status/fresh-relay-
8320 descs" to fetch a descriptor/extrainfo pair that was generated on
8321 demand just for the controller's use. Implements ticket 14784.
8323 o Minor features (DoS-resistance):
8324 - Make it harder for attackers to overload hidden services with
8325 introductions, by blocking multiple introduction requests on the
8326 same circuit. Resolves ticket 15515.
8328 o Minor features (geoip):
8329 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
8330 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
8333 o Minor features (HS popularity countermeasure):
8334 - To avoid leaking HS popularity, don't cycle the introduction point
8335 when we've handled a fixed number of INTRODUCE2 cells but instead
8336 cycle it when a random number of introductions is reached, thus
8337 making it more difficult for an attacker to find out the amount of
8338 clients that have used the introduction point for a specific HS.
8339 Closes ticket 15745.
8341 o Minor features (logging):
8342 - Include the Tor version in all LD_BUG log messages, since people
8343 tend to cut and paste those into the bugtracker. Implements
8346 o Minor features (pluggable transports):
8347 - When launching managed pluggable transports on Linux systems,
8348 attempt to have the kernel deliver a SIGTERM on tor exit if the
8349 pluggable transport process is still running. Resolves
8351 - When launching managed pluggable transports, setup a valid open
8352 stdin in the child process that can be used to detect if tor has
8353 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
8354 can be used by implementations to detect this new behavior.
8355 Resolves ticket 15435.
8357 o Minor features (testing):
8358 - Add a test to verify that the compiler does not eliminate our
8359 memwipe() implementation. Closes ticket 15377.
8360 - Add make rule `check-changes` to verify the format of changes
8361 files. Closes ticket 15180.
8362 - Add unit tests for control_event_is_interesting(). Add a compile-
8363 time check that the number of events doesn't exceed the capacity
8364 of control_event_t.event_mask. Closes ticket 15431, checks for
8365 bugs similar to 13085. Patch by "teor".
8366 - Command-line argument tests moved to Stem. Resolves ticket 14806.
8367 - Integrate the ntor, backtrace, and zero-length keys tests into the
8368 automake test suite. Closes ticket 15344.
8369 - Remove assertions during builds to determine Tor's test coverage.
8370 We don't want to trigger these even in assertions, so including
8371 them artificially makes our branch coverage look worse than it is.
8372 This patch provides the new test-stem-full and coverage-html-full
8373 configure options. Implements ticket 15400.
8375 o Minor bugfixes (build):
8376 - Improve out-of-tree builds by making non-standard rules work and
8377 clean up additional files and directories. Fixes bug 15053; bugfix
8380 o Minor bugfixes (command-line interface):
8381 - When "--quiet" is provided along with "--validate-config", do not
8382 write anything to stdout on success. Fixes bug 14994; bugfix
8384 - When complaining about bad arguments to "--dump-config", use
8387 o Minor bugfixes (configuration, unit tests):
8388 - Only add the default fallback directories when the DirAuthorities,
8389 AlternateDirAuthority, and FallbackDir directory config options
8390 are set to their defaults. The default fallback directory list is
8391 currently empty, this fix will only change tor's behavior when it
8392 has default fallback directories. Includes unit tests for
8393 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
8394 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
8396 o Minor bugfixes (correctness):
8397 - For correctness, avoid modifying a constant string in
8398 handle_control_postdescriptor. Fixes bug 15546; bugfix
8400 - Remove side-effects from tor_assert() calls. This was harmless,
8401 because we never disable assertions, but it is bad style and
8402 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
8405 o Minor bugfixes (hidden service):
8406 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8407 a client authorized hidden service. Fixes bug 15823; bugfix
8409 - Remove an extraneous newline character from the end of hidden
8410 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
8412 o Minor bugfixes (interface):
8413 - Print usage information for --dump-config when it is used without
8414 an argument. Also, fix the error message to use different wording
8415 and add newline at the end. Fixes bug 15541; bugfix
8418 o Minor bugfixes (logs):
8419 - When building Tor under Clang, do not include an extra set of
8420 parentheses in log messages that include function names. Fixes bug
8421 15269; bugfix on every released version of Tor when compiled with
8422 recent enough Clang.
8424 o Minor bugfixes (network):
8425 - When attempting to use fallback technique for network interface
8426 lookup, disregard loopback and multicast addresses since they are
8427 unsuitable for public communications.
8429 o Minor bugfixes (statistics):
8430 - Disregard the ConnDirectionStatistics torrc options when Tor is
8431 not a relay since in that mode of operation no sensible data is
8432 being collected and because Tor might run into measurement hiccups
8433 when running as a client for some time, then becoming a relay.
8434 Fixes bug 15604; bugfix on 0.2.2.35.
8436 o Minor bugfixes (test networks):
8437 - When self-testing reachability, use ExtendAllowPrivateAddresses to
8438 determine if local/private addresses imply reachability. The
8439 previous fix used TestingTorNetwork, which implies
8440 ExtendAllowPrivateAddresses, but this excluded rare configurations
8441 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
8442 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
8443 issue discovered by CJ Ess.
8445 o Minor bugfixes (testing):
8446 - Check for matching value in server response in ntor_ref.py. Fixes
8447 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
8449 - Set the severity correctly when testing
8450 get_interface_addresses_ifaddrs() and
8451 get_interface_addresses_win32(), so that the tests fail gracefully
8452 instead of triggering an assertion. Fixes bug 15759; bugfix on
8453 0.2.6.3-alpha. Reported by Nicolas Derive.
8455 o Code simplification and refactoring:
8456 - Move the hacky fallback code out of get_interface_address6() into
8457 separate function and get it covered with unit-tests. Resolves
8459 - Refactor hidden service client-side cache lookup to intelligently
8460 report its various failure cases, and disentangle failure cases
8461 involving a lack of introduction points. Closes ticket 14391.
8462 - Use our own Base64 encoder instead of OpenSSL's, to allow more
8463 control over the output. Part of ticket 15652.
8466 - Improve the descriptions of statistics-related torrc options in
8467 the manpage to describe rationale and possible uses cases. Fixes
8469 - Improve the layout and formatting of ./configure --help messages.
8470 Closes ticket 15024. Patch from "cypherpunks".
8471 - Standardize on the term "server descriptor" in the manual page.
8472 Previously, we had used "router descriptor", "server descriptor",
8473 and "relay descriptor" interchangeably. Part of ticket 14987.
8476 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
8477 and always use the internal Base64 decoder. The internal decoder
8478 has been part of tor since 0.2.0.10-alpha, and no one should
8479 be using the OpenSSL one. Part of ticket 15652.
8480 - Remove the 'tor_strclear()' function; use memwipe() instead.
8481 Closes ticket 14922.
8484 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
8485 fingerprinting we now recommend pluggable transports; for forward-
8486 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
8487 - Remove the undocumented "--digests" command-line option. It
8488 complicated our build process, caused subtle build issues on
8489 multiple platforms, and is now redundant since we started
8490 including git version identifiers. Closes ticket 14742.
8491 - Tor no longer contains checks for ancient directory cache versions
8492 that didn't know about microdescriptors.
8493 - Tor no longer contains workarounds for stat files generated by
8494 super-old versions of Tor that didn't choose guards sensibly.
8497 Changes in version 0.2.4.27 - 2015-04-06
8498 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
8499 could be used by an attacker to crash hidden services, or crash clients
8500 visiting hidden services. Hidden services should upgrade as soon as
8501 possible; clients should upgrade whenever packages become available.
8503 This release also backports a simple improvement to make hidden
8504 services a bit less vulnerable to denial-of-service attacks.
8506 o Major bugfixes (security, hidden service):
8507 - Fix an issue that would allow a malicious client to trigger an
8508 assertion failure and halt a hidden service. Fixes bug 15600;
8509 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
8510 - Fix a bug that could cause a client to crash with an assertion
8511 failure when parsing a malformed hidden service descriptor. Fixes
8512 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
8514 o Minor features (DoS-resistance, hidden service):
8515 - Introduction points no longer allow multiple INTRODUCE1 cells to
8516 arrive on the same circuit. This should make it more expensive for
8517 attackers to overwhelm hidden services with introductions.
8518 Resolves ticket 15515.
8521 Changes in version 0.2.5.12 - 2015-04-06
8522 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
8523 could be used by an attacker to crash hidden services, or crash clients
8524 visiting hidden services. Hidden services should upgrade as soon as
8525 possible; clients should upgrade whenever packages become available.
8527 This release also backports a simple improvement to make hidden
8528 services a bit less vulnerable to denial-of-service attacks.
8530 o Major bugfixes (security, hidden service):
8531 - Fix an issue that would allow a malicious client to trigger an
8532 assertion failure and halt a hidden service. Fixes bug 15600;
8533 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
8534 - Fix a bug that could cause a client to crash with an assertion
8535 failure when parsing a malformed hidden service descriptor. Fixes
8536 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
8538 o Minor features (DoS-resistance, hidden service):
8539 - Introduction points no longer allow multiple INTRODUCE1 cells to
8540 arrive on the same circuit. This should make it more expensive for
8541 attackers to overwhelm hidden services with introductions.
8542 Resolves ticket 15515.
8545 Changes in version 0.2.6.7 - 2015-04-06
8546 Tor 0.2.6.7 fixes two security issues that could be used by an
8547 attacker to crash hidden services, or crash clients visiting hidden
8548 services. Hidden services should upgrade as soon as possible; clients
8549 should upgrade whenever packages become available.
8551 This release also contains two simple improvements to make hidden
8552 services a bit less vulnerable to denial-of-service attacks.
8554 o Major bugfixes (security, hidden service):
8555 - Fix an issue that would allow a malicious client to trigger an
8556 assertion failure and halt a hidden service. Fixes bug 15600;
8557 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
8558 - Fix a bug that could cause a client to crash with an assertion
8559 failure when parsing a malformed hidden service descriptor. Fixes
8560 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
8562 o Minor features (DoS-resistance, hidden service):
8563 - Introduction points no longer allow multiple INTRODUCE1 cells to
8564 arrive on the same circuit. This should make it more expensive for
8565 attackers to overwhelm hidden services with introductions.
8566 Resolves ticket 15515.
8567 - Decrease the amount of reattempts that a hidden service performs
8568 when its rendezvous circuits fail. This reduces the computational
8569 cost for running a hidden service under heavy load. Resolves
8573 Changes in version 0.2.6.6 - 2015-03-24
8574 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
8576 It adds numerous safety, security, correctness, and performance
8577 improvements. Client programs can be configured to use more kinds of
8578 sockets, AutomapHosts works better, the multithreading backend is
8579 improved, cell transmission is refactored, test coverage is much
8580 higher, more denial-of-service attacks are handled, guard selection is
8581 improved to handle long-term guards better, pluggable transports
8582 should work a bit better, and some annoying hidden service performance
8583 bugs should be addressed.
8585 o Minor bugfixes (portability):
8586 - Use the correct datatype in the SipHash-2-4 function to prevent
8587 compilers from assuming any sort of alignment. Fixes bug 15436;
8588 bugfix on 0.2.5.3-alpha.
8590 Changes in version 0.2.6.5-rc - 2015-03-18
8591 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
8592 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
8594 o Major bugfixes (client):
8595 - Avoid crashing when making certain configuration option changes on
8596 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
8599 o Major bugfixes (pluggable transports):
8600 - Initialize the extended OR Port authentication cookie before
8601 launching pluggable transports. This prevents a race condition
8602 that occurred when server-side pluggable transports would cache the
8603 authentication cookie before it has been (re)generated. Fixes bug
8604 15240; bugfix on 0.2.5.1-alpha.
8606 o Major bugfixes (portability):
8607 - Do not crash on startup when running on Solaris. Fixes a bug
8608 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
8611 o Minor features (heartbeat):
8612 - On relays, report how many connections we negotiated using each
8613 version of the Tor link protocols. This information will let us
8614 know if removing support for very old versions of the Tor
8615 protocols is harming the network. Closes ticket 15212.
8617 o Code simplification and refactoring:
8618 - Refactor main loop to extract the 'loop' part. This makes it
8619 easier to run Tor under Shadow. Closes ticket 15176.
8622 Changes in version 0.2.5.11 - 2015-03-17
8623 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
8625 It backports several bugfixes from the 0.2.6 branch, including a
8626 couple of medium-level security fixes for relays and exit nodes.
8627 It also updates the list of directory authorities.
8629 o Directory authority changes:
8630 - Remove turtles as a directory authority.
8631 - Add longclaw as a new (v3) directory authority. This implements
8632 ticket 13296. This keeps the directory authority count at 9.
8633 - The directory authority Faravahar has a new IP address. This
8634 closes ticket 14487.
8636 o Major bugfixes (crash, OSX, security):
8637 - Fix a remote denial-of-service opportunity caused by a bug in
8638 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8641 o Major bugfixes (relay, stability, possible security):
8642 - Fix a bug that could lead to a relay crashing with an assertion
8643 failure if a buffer of exactly the wrong layout was passed to
8644 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8645 0.2.0.10-alpha. Patch from 'cypherpunks'.
8646 - Do not assert if the 'data' pointer on a buffer is advanced to the
8647 very end of the buffer; log a BUG message instead. Only assert if
8648 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8650 o Major bugfixes (exit node stability):
8651 - Fix an assertion failure that could occur under high DNS load.
8652 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8653 diagnosed and fixed by "cypherpunks".
8655 o Major bugfixes (Linux seccomp2 sandbox):
8656 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8657 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8658 0.2.5.1-alpha. Patch from "sanic".
8660 o Minor features (controller):
8661 - New "GETINFO bw-event-cache" to get information about recent
8662 bandwidth events. Closes ticket 14128. Useful for controllers to
8663 get recent bandwidth history after the fix for ticket 13988.
8665 o Minor features (geoip):
8666 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8667 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8670 o Minor bugfixes (client, automapping):
8671 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8672 no value follows the option. Fixes bug 14142; bugfix on
8673 0.2.4.7-alpha. Patch by "teor".
8674 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8675 14195; bugfix on 0.1.0.1-rc.
8677 o Minor bugfixes (compilation):
8678 - Build without warnings with the stock OpenSSL srtp.h header, which
8679 has a duplicate declaration of SSL_get_selected_srtp_profile().
8680 Fixes bug 14220; this is OpenSSL's bug, not ours.
8682 o Minor bugfixes (directory authority):
8683 - Allow directory authorities to fetch more data from one another if
8684 they find themselves missing lots of votes. Previously, they had
8685 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8686 bugfix on 0.1.2.5-alpha.
8687 - Enlarge the buffer to read bwauth generated files to avoid an
8688 issue when parsing the file in dirserv_read_measured_bandwidths().
8689 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8691 o Minor bugfixes (statistics):
8692 - Increase period over which bandwidth observations are aggregated
8693 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8695 o Minor bugfixes (preventative security, C safety):
8696 - When reading a hexadecimal, base-32, or base-64 encoded value from
8697 a string, always overwrite the whole output buffer. This prevents
8698 some bugs where we would look at (but fortunately, not reveal)
8699 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8703 Changes in version 0.2.4.26 - 2015-03-17
8704 Tor 0.2.4.26 includes an updated list of directory authorities. It
8705 also backports a couple of stability and security bugfixes from 0.2.5
8708 o Directory authority changes:
8709 - Remove turtles as a directory authority.
8710 - Add longclaw as a new (v3) directory authority. This implements
8711 ticket 13296. This keeps the directory authority count at 9.
8712 - The directory authority Faravahar has a new IP address. This
8713 closes ticket 14487.
8715 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
8716 - Fix an assertion failure that could occur under high DNS load.
8717 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8718 diagnosed and fixed by "cypherpunks".
8720 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
8721 - Fix a bug that could lead to a relay crashing with an assertion
8722 failure if a buffer of exactly the wrong layout was passed to
8723 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8724 0.2.0.10-alpha. Patch from 'cypherpunks'.
8725 - Do not assert if the 'data' pointer on a buffer is advanced to the
8726 very end of the buffer; log a BUG message instead. Only assert if
8727 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8729 o Minor features (geoip):
8730 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8731 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8734 Changes in version 0.2.6.4-rc - 2015-03-09
8735 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
8736 attacker might be able to use in order to crash certain Tor
8737 directories. It also resolves some minor issues left over from, or
8738 introduced in, Tor 0.2.6.3-alpha or earlier.
8740 o Major bugfixes (crash, OSX, security):
8741 - Fix a remote denial-of-service opportunity caused by a bug in
8742 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8745 o Major bugfixes (relay, stability, possible security):
8746 - Fix a bug that could lead to a relay crashing with an assertion
8747 failure if a buffer of exactly the wrong layout is passed to
8748 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8749 0.2.0.10-alpha. Patch from "cypherpunks".
8750 - Do not assert if the 'data' pointer on a buffer is advanced to the
8751 very end of the buffer; log a BUG message instead. Only assert if
8752 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8754 o Major bugfixes (FreeBSD IPFW transparent proxy):
8755 - Fix address detection with FreeBSD transparent proxies, when
8756 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
8759 o Major bugfixes (Linux seccomp2 sandbox):
8760 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
8761 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
8763 - Allow AF_UNIX hidden services to be used with the seccomp2
8764 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
8765 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8766 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8767 0.2.5.1-alpha. Patch from "sanic".
8769 o Minor features (controller):
8770 - Messages about problems in the bootstrap process now include
8771 information about the server we were trying to connect to when we
8772 noticed the problem. Closes ticket 15006.
8774 o Minor features (geoip):
8775 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8776 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8779 o Minor features (logs):
8780 - Quiet some log messages in the heartbeat and at startup. Closes
8783 o Minor bugfixes (certificate handling):
8784 - If an authority operator accidentally makes a signing certificate
8785 with a future publication time, do not discard its real signing
8786 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
8787 - Remove any old authority certificates that have been superseded
8788 for at least two days. Previously, we would keep superseded
8789 certificates until they expired, if they were published close in
8790 time to the certificate that superseded them. Fixes bug 11454;
8791 bugfix on 0.2.1.8-alpha.
8793 o Minor bugfixes (compilation):
8794 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
8796 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
8799 o Minor bugfixes (testing):
8800 - Fix endianness issues in unit test for resolve_my_address() to
8801 have it pass on big endian systems. Fixes bug 14980; bugfix on
8803 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
8804 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
8805 - When running the new 'make test-stem' target, use the configured
8806 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
8808 - When running the zero-length-keys tests, do not use the default
8809 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
8812 o Directory authority IP change:
8813 - The directory authority Faravahar has a new IP address. This
8814 closes ticket 14487.
8817 - Remove some lingering dead code that once supported mempools.
8818 Mempools were disabled by default in 0.2.5, and removed entirely
8819 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
8823 Changes in version 0.2.6.3-alpha - 2015-02-19
8824 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
8825 the 0.2.6.x series. It introduces support for more kinds of sockets,
8826 makes it harder to accidentally run an exit, improves our
8827 multithreading backend, incorporates several fixes for the
8828 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
8830 If no major regressions or security holes are found in this version,
8831 the next version will be a release candidate.
8833 o Deprecated versions:
8834 - Tor relays older than 0.2.4.18-rc are no longer allowed to
8835 advertise themselves on the network. Closes ticket 13555.
8837 o Major features (security, unix domain sockets):
8838 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
8839 applications can reach Tor without having to create AF_INET or
8840 AF_INET6 sockets, meaning they can completely disable their
8841 ability to make non-Tor network connections. To create a socket of
8842 this type, use "SocksPort unix:/path/to/socket". Implements
8844 - Support mapping hidden service virtual ports to AF_UNIX sockets.
8845 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
8846 Implements ticket 11485.
8848 o Major features (changed defaults):
8849 - Prevent relay operators from unintentionally running exits: When a
8850 relay is configured as an exit node, we now warn the user unless
8851 the "ExitRelay" option is set to 1. We warn even more loudly if
8852 the relay is configured with the default exit policy, since this
8853 can indicate accidental misconfiguration. Setting "ExitRelay 0"
8854 stops Tor from running as an exit relay. Closes ticket 10067.
8856 o Major features (directory system):
8857 - When downloading server- or microdescriptors from a directory
8858 server, we no longer launch multiple simultaneous requests to the
8859 same server. This reduces load on the directory servers,
8860 especially when directory guards are in use. Closes ticket 9969.
8861 - When downloading server- or microdescriptors over a tunneled
8862 connection, do not limit the length of our requests to what the
8863 Squid proxy is willing to handle. Part of ticket 9969.
8864 - Authorities can now vote on the correct digests and latest
8865 versions for different software packages. This allows packages
8866 that include Tor to use the Tor authority system as a way to get
8867 notified of updates and their correct digests. Implements proposal
8868 227. Closes ticket 10395.
8870 o Major features (guards):
8871 - Introduce the Guardfraction feature to improves load balancing on
8872 guard nodes. Specifically, it aims to reduce the traffic gap that
8873 guard nodes experience when they first get the Guard flag. This is
8874 a required step if we want to increase the guard lifetime to 9
8875 months or greater. Closes ticket 9321.
8877 o Major features (performance):
8878 - Make the CPU worker implementation more efficient by avoiding the
8879 kernel and lengthening pipelines. The original implementation used
8880 sockets to transfer data from the main thread to the workers, and
8881 didn't allow any thread to be assigned more than a single piece of
8882 work at once. The new implementation avoids communications
8883 overhead by making requests in shared memory, avoiding kernel IO
8884 where possible, and keeping more requests in flight at once.
8885 Implements ticket 9682.
8887 o Major features (relay):
8888 - Raise the minimum acceptable configured bandwidth rate for bridges
8889 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
8890 20 KiB/sec.) Closes ticket 13822.
8892 o Major bugfixes (exit node stability):
8893 - Fix an assertion failure that could occur under high DNS load.
8894 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8895 diagnosed and fixed by "cypherpunks".
8897 o Major bugfixes (mixed relay-client operation):
8898 - When running as a relay and client at the same time (not
8899 recommended), if we decide not to use a new guard because we want
8900 to retry older guards, only close the locally-originating circuits
8901 passing through that guard. Previously we would close all the
8902 circuits through that guard. Fixes bug 9819; bugfix on
8903 0.2.1.1-alpha. Reported by "skruffy".
8905 o Minor features (build):
8906 - New --disable-system-torrc compile-time option to prevent Tor from
8907 looking for the system-wide torrc or torrc-defaults files.
8908 Resolves ticket 13037.
8910 o Minor features (controller):
8911 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
8912 events so controllers can observe circuit isolation inputs. Closes
8914 - ControlPort now supports the unix:/path/to/socket syntax as an
8915 alternative to the ControlSocket option, for consistency with
8916 SocksPort and HiddenServicePort. Closes ticket 14451.
8917 - New "GETINFO bw-event-cache" to get information about recent
8918 bandwidth events. Closes ticket 14128. Useful for controllers to
8919 get recent bandwidth history after the fix for ticket 13988.
8921 o Minor features (Denial of service resistance):
8922 - Count the total number of bytes used storing hidden service
8923 descriptors against the value of MaxMemInQueues. If we're low on
8924 memory, and more than 20% of our memory is used holding hidden
8925 service descriptors, free them until no more than 10% of our
8926 memory holds hidden service descriptors. Free the least recently
8927 fetched descriptors first. Resolves ticket 13806.
8928 - When we have recently been under memory pressure (over 3/4 of
8929 MaxMemInQueues is allocated), then allocate smaller zlib objects
8930 for small requests. Closes ticket 11791.
8932 o Minor features (geoip):
8933 - Update geoip and geoip6 files to the January 7 2015 Maxmind
8934 GeoLite2 Country database.
8936 o Minor features (guard nodes):
8937 - Reduce the time delay before saving guard status to disk from 10
8938 minutes to 30 seconds (or from one hour to 10 minutes if
8939 AvoidDiskWrites is set). Closes ticket 12485.
8941 o Minor features (hidden service):
8942 - Make Sybil attacks against hidden services harder by changing the
8943 minimum time required to get the HSDir flag from 25 hours up to 96
8944 hours. Addresses ticket 14149.
8945 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
8946 services to disable the anti-scanning feature introduced in
8947 0.2.6.2-alpha. With this option not set, a connection to an
8948 unlisted port closes the circuit. With this option set, only a
8949 RELAY_DONE cell is sent. Closes ticket 14084.
8951 o Minor features (interface):
8952 - Implement "-f -" command-line option to read torrc configuration
8953 from standard input, if you don't want to store the torrc file in
8954 the file system. Implements feature 13865.
8956 o Minor features (logging):
8957 - Add a count of unique clients to the bridge heartbeat message.
8958 Resolves ticket 6852.
8959 - Suppress "router info incompatible with extra info" message when
8960 reading extrainfo documents from cache. (This message got loud
8961 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
8963 - Elevate hidden service authorized-client message from DEBUG to
8964 INFO. Closes ticket 14015.
8966 o Minor features (stability):
8967 - Add assertions in our hash-table iteration code to check for
8968 corrupted values that could cause infinite loops. Closes
8971 o Minor features (systemd):
8972 - Various improvements and modernizations in systemd hardening
8973 support. Closes ticket 13805. Patch from Craig Andrews.
8975 o Minor features (testing networks):
8976 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
8977 and the default on a testing network to 2 minutes. Drop the
8978 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
8979 keep the default on a testing network at 30 seconds. This reduces
8980 HS bootstrap time to around 25 seconds. Also, change the default
8981 time in test-network.sh to match. Closes ticket 13401. Patch
8983 - Create TestingDirAuthVoteHSDir to correspond to
8984 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
8985 HSDir flag for the listed relays regardless of uptime or ORPort
8986 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
8987 Partial implementation for ticket 14067. Patch by "teor".
8989 o Minor features (tor2web mode):
8990 - Introduce the config option Tor2webRendezvousPoints, which allows
8991 clients in Tor2webMode to select a specific Rendezvous Point to be
8992 used in HS circuits. This might allow better performance for
8993 Tor2Web nodes. Implements ticket 12844.
8995 o Minor bugfixes (client DNS):
8996 - Report the correct cached DNS expiration times on SOCKS port or in
8997 DNS replies. Previously, we would report everything as "never
8998 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8999 - Avoid a small memory leak when we find a cached answer for a
9000 reverse DNS lookup in a client-side DNS cache. (Remember, client-
9001 side DNS caching is off by default, and is not recommended.) Fixes
9002 bug 14259; bugfix on 0.2.0.1-alpha.
9004 o Minor bugfixes (client, automapping):
9005 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
9006 no value follows the option. Fixes bug 14142; bugfix on
9007 0.2.4.7-alpha. Patch by "teor".
9008 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
9009 14195; bugfix on 0.1.0.1-rc.
9010 - Prevent changes to other options from removing the wildcard value
9011 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
9013 - Allow MapAddress and AutomapHostsOnResolve to work together when
9014 an address is mapped into another address type (like .onion) that
9015 must be automapped at resolve time. Fixes bug 7555; bugfix
9018 o Minor bugfixes (client, bridges):
9019 - When we are using bridges and we had a network connectivity
9020 problem, only retry connecting to our currently configured
9021 bridges, not all bridges we know about and remember using. Fixes
9022 bug 14216; bugfix on 0.2.2.17-alpha.
9024 o Minor bugfixes (client, IPv6):
9025 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
9026 flag is not set; and not because the NoIPv4Traffic flag was set.
9027 Previously we'd looked at the NoIPv4Traffic flag for both types of
9028 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
9030 o Minor bugfixes (compilation):
9031 - The address of an array in the middle of a structure will always
9032 be non-NULL. clang recognises this and complains. Disable the
9033 tautologous and redundant check to silence this warning. Fixes bug
9034 14001; bugfix on 0.2.1.2-alpha.
9035 - Avoid warnings when building with systemd 209 or later. Fixes bug
9036 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
9037 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
9038 Addresses ticket 14188.
9039 - Build without warnings with the stock OpenSSL srtp.h header, which
9040 has a duplicate declaration of SSL_get_selected_srtp_profile().
9041 Fixes bug 14220; this is OpenSSL's bug, not ours.
9042 - Do not compile any code related to Tor2Web mode when Tor2Web mode
9043 is not enabled at compile time. Previously, this code was included
9044 in a disabled state. See discussion on ticket 12844.
9045 - Remove the --disable-threads configure option again. It was
9046 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
9047 14819; bugfix on 0.2.6.2-alpha.
9049 o Minor bugfixes (controller):
9050 - Report "down" in response to the "GETINFO entry-guards" command
9051 when relays are down with an unreachable_since value. Previously,
9052 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
9053 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
9054 14116; bugfix on 0.2.2.9-alpha.
9055 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
9056 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
9058 o Minor bugfixes (directory authority):
9059 - Allow directory authorities to fetch more data from one another if
9060 they find themselves missing lots of votes. Previously, they had
9061 been bumping against the 10 MB queued data limit. Fixes bug 14261;
9062 bugfix on 0.1.2.5-alpha.
9063 - Do not attempt to download extrainfo documents which we will be
9064 unable to validate with a matching server descriptor. Fixes bug
9065 13762; bugfix on 0.2.0.1-alpha.
9066 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
9067 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
9068 - Enlarge the buffer to read bwauth generated files to avoid an
9069 issue when parsing the file in dirserv_read_measured_bandwidths().
9070 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
9072 o Minor bugfixes (file handling):
9073 - Stop failing when key files are zero-length. Instead, generate new
9074 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
9075 on all versions of Tor. Patch by "teor".
9076 - Stop generating a fresh .old RSA onion key file when the .old file
9077 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
9078 - Avoid overwriting .old key files with empty key files.
9079 - Skip loading zero-length extrainfo store, router store, stats,
9080 state, and key files.
9081 - Avoid crashing when trying to reload a torrc specified as a
9082 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
9085 o Minor bugfixes (hidden services):
9086 - Close the introduction circuit when we have no more usable intro
9087 points, instead of waiting for it to time out. This also ensures
9088 that no follow-up HS descriptor fetch is triggered when the
9089 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
9090 - When fetching a hidden service descriptor for a down service that
9091 was recently up, do not keep refetching until we try the same
9092 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
9093 - Successfully launch Tor with a nonexistent hidden service
9094 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
9095 14106; bugfix on 0.2.6.2-alpha.
9097 o Minor bugfixes (logging):
9098 - Avoid crashing when there are more log domains than entries in
9099 domain_list. Bugfix on 0.2.3.1-alpha.
9100 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
9102 - Don't log messages to stdout twice when starting up. Fixes bug
9103 13993; bugfix on 0.2.6.1-alpha.
9105 o Minor bugfixes (parsing):
9106 - Stop accepting milliseconds (or other junk) at the end of
9107 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
9108 - Support two-number and three-number version numbers correctly, in
9109 case we change the Tor versioning system in the future. Fixes bug
9110 13661; bugfix on 0.0.8pre1.
9112 o Minor bugfixes (path counting):
9113 - When deciding whether the consensus lists any exit nodes, count
9114 the number listed in the consensus, not the number we have
9115 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
9116 - When deciding whether we have any exit nodes, only examine
9117 ExitNodes when the ExitNodes option is actually set. Fixes part of
9118 bug 14918; bugfix on 0.2.6.2-alpha.
9119 - Get rid of redundant and possibly scary warnings that we are
9120 missing directory information while we bootstrap. Fixes part of
9121 bug 14918; bugfix on 0.2.6.2-alpha.
9123 o Minor bugfixes (portability):
9124 - Fix the ioctl()-based network interface lookup code so that it
9125 will work on systems that have variable-length struct ifreq, for
9127 - Fix scheduler compilation on targets where char is unsigned. Fixes
9128 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
9130 o Minor bugfixes (sandbox):
9131 - Allow glibc fatal errors to be sent to stderr before Tor exits.
9132 Previously, glibc would try to write them to /dev/tty, and the
9133 sandbox would trap the call and make Tor exit prematurely. Fixes
9134 bug 14759; bugfix on 0.2.5.1-alpha.
9136 o Minor bugfixes (shutdown):
9137 - When shutting down, always call event_del() on lingering read or
9138 write events before freeing them. Otherwise, we risk double-frees
9139 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
9142 o Minor bugfixes (small memory leaks):
9143 - Avoid leaking memory when using IPv6 virtual address mappings.
9144 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
9147 o Minor bugfixes (statistics):
9148 - Increase period over which bandwidth observations are aggregated
9149 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9151 o Minor bugfixes (systemd support):
9152 - Fix detection and operation of systemd watchdog. Fixes part of bug
9153 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
9154 - Run correctly under systemd with the RunAsDaemon option set. Fixes
9155 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
9156 - Inform the systemd supervisor about more changes in the Tor
9157 process status. Implements part of ticket 14141. Patch from
9159 - Cause the "--disable-systemd" option to actually disable systemd
9160 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
9163 o Minor bugfixes (TLS):
9164 - Check more thoroughly throughout the TLS code for possible
9165 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
9167 o Minor bugfixes (transparent proxy):
9168 - Use getsockname, not getsockopt, to retrieve the address for a
9169 TPROXY-redirected connection. Fixes bug 13796; bugfix
9172 o Code simplification and refactoring:
9173 - Move fields related to isolating and configuring client ports into
9174 a shared structure. Previously, they were duplicated across
9175 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
9176 to copy them correctly had been the cause of at least one bug in
9177 the past. Closes ticket 8546.
9178 - Refactor the get_interface_addresses_raw() doom-function into
9179 multiple smaller and simpler subfunctions. Cover the resulting
9180 subfunctions with unit-tests. Fixes a significant portion of
9182 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
9183 only for version <= 0.2.2.24 which is now deprecated. Closes
9185 - Remove a test for a long-defunct broken version-one
9189 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
9190 for writing the OpenBSD-specific tips. Resolves ticket 13702.
9191 - Make the tor-resolve documentation match its help string and its
9192 options. Resolves part of ticket 14325.
9193 - Log a more useful error message from tor-resolve when failing to
9194 look up a hidden service address. Resolves part of ticket 14325.
9196 o Downgraded warnings:
9197 - Don't warn when we've attempted to contact a relay using the wrong
9198 ntor onion key. Closes ticket 9635.
9201 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
9202 longer silently accepted as an alias for "ExitNodes".
9203 - The --enable-mempool and --enable-buf-freelists options, which
9204 were originally created to work around bad malloc implementations,
9205 no longer exist. They were off-by-default in 0.2.5. Closes
9209 - Make the checkdir/perms test complete successfully even if the
9210 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
9211 - Test that tor does not fail when key files are zero-length. Check
9212 that tor generates new keys, and overwrites the empty key files.
9213 - Test that tor generates new keys when keys are missing
9214 (existing behavior).
9215 - Test that tor does not overwrite key files that already contain
9216 data (existing behavior). Tests bug 13111. Patch by "teor".
9217 - New "make test-stem" target to run stem integration tests.
9218 Requires that the "STEM_SOURCE_DIR" environment variable be set.
9219 Closes ticket 14107.
9220 - Make the test_cmdline_args.py script work correctly on Windows.
9221 Patch from Gisle Vanem.
9222 - Move the slower unit tests into a new "./src/test/test-slow"
9223 binary that can be run independently of the other tests. Closes
9225 - Avoid undefined behavior when sampling huge values from the
9226 Laplace distribution. This made unittests fail on Raspberry Pi.
9227 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
9230 Changes in version 0.2.6.2-alpha - 2014-12-31
9231 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
9232 It introduces a major new backend for deciding when to send cells on
9233 channels, which should lead down the road to big performance
9234 increases. It contains security and statistics features for better
9235 work on hidden services, and numerous bugfixes.
9237 This release contains many new unit tests, along with major
9238 performance improvements for running testing networks using Chutney.
9239 Thanks to a series of patches contributed by "teor", testing networks
9240 should now bootstrap in seconds, rather than minutes.
9242 o Major features (relay, infrastructure):
9243 - Complete revision of the code that relays use to decide which cell
9244 to send next. Formerly, we selected the best circuit to write on
9245 each channel, but we didn't select among channels in any
9246 sophisticated way. Now, we choose the best circuits globally from
9247 among those whose channels are ready to deliver traffic.
9249 This patch implements a new inter-cmux comparison API, a global
9250 high/low watermark mechanism and a global scheduler loop for
9251 transmission prioritization across all channels as well as among
9252 circuits on one channel. This schedule is currently tuned to
9253 (tolerantly) avoid making changes in network performance, but it
9254 should form the basis for major circuit performance increases in
9255 the future. Code by Andrea; tuning by Rob Jansen; implements
9258 o Major features (hidden services):
9259 - Make HS port scanning more difficult by immediately closing the
9260 circuit when a user attempts to connect to a nonexistent port.
9261 Closes ticket 13667.
9262 - Add a HiddenServiceStatistics option that allows Tor relays to
9263 gather and publish statistics about the overall size and volume of
9264 hidden service usage. Specifically, when this option is turned on,
9265 an HSDir will publish an approximate number of hidden services
9266 that have published descriptors to it the past 24 hours. Also, if
9267 a relay has acted as a hidden service rendezvous point, it will
9268 publish the approximate amount of rendezvous cells it has relayed
9269 the past 24 hours. The statistics themselves are obfuscated so
9270 that the exact values cannot be derived. For more details see
9271 proposal 238, "Better hidden service stats from Tor relays". This
9272 feature is currently disabled by default. Implements feature 13192.
9274 o Major bugfixes (client, automap):
9275 - Repair automapping with IPv6 addresses. This automapping should
9276 have worked previously, but one piece of debugging code that we
9277 inserted to detect a regression actually caused the regression to
9278 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
9279 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
9282 o Major bugfixes (hidden services):
9283 - When closing an introduction circuit that was opened in parallel
9284 with others, don't mark the introduction point as unreachable.
9285 Previously, the first successful connection to an introduction
9286 point would make the other introduction points get marked as
9287 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
9289 o Directory authority changes:
9290 - Remove turtles as a directory authority.
9291 - Add longclaw as a new (v3) directory authority. This implements
9292 ticket 13296. This keeps the directory authority count at 9.
9294 o Major removed features:
9295 - Tor clients no longer support connecting to hidden services
9296 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
9297 option has been removed. (There shouldn't be any hidden services
9298 running these versions on the network.) Closes ticket 7803.
9300 o Minor features (client):
9301 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
9302 is enabled, reject requests with IP addresses as hostnames.
9303 Resolves ticket 13315.
9305 o Minor features (controller):
9306 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
9307 write an unscheduled heartbeat message to the log. Implements
9310 o Minor features (geoip):
9311 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
9314 o Minor features (hidden services):
9315 - When re-enabling the network, don't try to build introduction
9316 circuits until we have successfully built a circuit. This makes
9317 hidden services come up faster when the network is re-enabled.
9318 Patch from "akwizgran". Closes ticket 13447.
9319 - When we fail to retrieve a hidden service descriptor, send the
9320 controller an "HS_DESC FAILED" controller event. Implements
9322 - New HiddenServiceDirGroupReadable option to cause hidden service
9323 directories and hostname files to be created group-readable. Patch
9324 from "anon", David Stainton, and "meejah". Closes ticket 11291.
9326 o Minor features (systemd):
9327 - Where supported, when running with systemd, report successful
9328 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
9329 - When running with systemd, support systemd watchdog messages. Part
9330 of ticket 11016. Patch by Michael Scherer.
9332 o Minor features (transparent proxy):
9333 - Update the transparent proxy option checks to allow for both ipfw
9334 and pf on OS X. Closes ticket 14002.
9335 - Use the correct option when using IPv6 with transparent proxy
9336 support on Linux. Resolves 13808. Patch by Francisco Blas
9339 o Minor bugfixes (preventative security, C safety):
9340 - When reading a hexadecimal, base-32, or base-64 encoded value from
9341 a string, always overwrite the whole output buffer. This prevents
9342 some bugs where we would look at (but fortunately, not reveal)
9343 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
9345 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
9346 just the part that's used. This makes it harder for data leak bugs
9347 to occur in the event of other programming failures. Resolves
9350 o Minor bugfixes (client, microdescriptors):
9351 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
9352 computing which microdescriptors to download. This keeps us from
9353 erroneous download behavior if two microdescriptor digests ever
9354 have the same first 160 bits. Fixes part of bug 13399; bugfix
9356 - Reset a router's status if its microdescriptor digest changes,
9357 even if the first 160 bits remain the same. Fixes part of bug
9358 13399; bugfix on 0.2.3.1-alpha.
9360 o Minor bugfixes (compilation):
9361 - Silence clang warnings under --enable-expensive-hardening,
9362 including implicit truncation of 64 bit values to 32 bit, const
9363 char assignment to self, tautological compare, and additional
9364 parentheses around equality tests. Fixes bug 13577; bugfix
9366 - Fix a clang warning about checking whether an address in the
9367 middle of a structure is NULL. Fixes bug 14001; bugfix
9370 o Minor bugfixes (hidden services):
9371 - Correctly send a controller event when we find that a rendezvous
9372 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
9373 - Pre-check directory permissions for new hidden-services to avoid
9374 at least one case of "Bug: Acting on config options left us in a
9375 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
9376 - When adding a new hidden service (for example, via SETCONF), Tor
9377 no longer congratulates the user for running a relay. Fixes bug
9378 13941; bugfix on 0.2.6.1-alpha.
9379 - When fetching hidden service descriptors, we now check not only
9380 for whether we got the hidden service we had in mind, but also
9381 whether we got the particular descriptors we wanted. This prevents
9382 a class of inefficient but annoying DoS attacks by hidden service
9383 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
9386 o Minor bugfixes (Linux seccomp2 sandbox):
9387 - Make transparent proxy support work along with the seccomp2
9388 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
9389 by Francisco Blas Izquierdo Riera.
9390 - Fix a memory leak in tor-resolve when running with the sandbox
9391 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
9393 o Minor bugfixes (logging):
9394 - Downgrade warnings about RSA signature failures to info log level.
9395 Emit a warning when an extra info document is found incompatible
9396 with a corresponding router descriptor. Fixes bug 9812; bugfix
9398 - Make connection_ap_handshake_attach_circuit() log the circuit ID
9399 correctly. Fixes bug 13701; bugfix on 0.0.6.
9401 o Minor bugfixes (misc):
9402 - Stop allowing invalid address patterns like "*/24" that contain
9403 both a wildcard address and a bit prefix length. This affects all
9404 our address-range parsing code. Fixes bug 7484; bugfix
9407 o Minor bugfixes (testing networks, fast startup):
9408 - Allow Tor to build circuits using a consensus with no exits. If
9409 the consensus has no exits (typical of a bootstrapping test
9410 network), allow Tor to build circuits once enough descriptors have
9411 been downloaded. This assists in bootstrapping a testing Tor
9412 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
9414 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
9415 header to directory servers. This allows us to obtain consensuses
9416 promptly when the consensus interval is very short. This assists
9417 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
9418 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
9419 - Stop assuming that private addresses are local when checking
9420 reachability in a TestingTorNetwork. Instead, when testing, assume
9421 all OR connections are remote. (This is necessary due to many test
9422 scenarios running all relays on localhost.) This assists in
9423 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
9424 0.1.0.1-rc. Patch by "teor".
9425 - Avoid building exit circuits from a consensus with no exits. Now
9426 thanks to our fix for 13718, we accept a no-exit network as not
9427 wholly lost, but we need to remember not to try to build exit
9428 circuits on it. Closes ticket 13814; patch by "teor".
9429 - Stop requiring exits to have non-zero bandwithcapacity in a
9430 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
9431 ignore exit bandwidthcapacity. This assists in bootstrapping a
9432 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
9433 on 0.2.0.3-alpha. Patch by "teor".
9434 - Add "internal" to some bootstrap statuses when no exits are
9435 available. If the consensus does not contain Exits, Tor will only
9436 build internal circuits. In this case, relevant statuses will
9437 contain the word "internal" as indicated in the Tor control-
9438 spec.txt. When bootstrap completes, Tor will be ready to build
9439 internal circuits. If a future consensus contains Exits, exit
9440 circuits may become available. Fixes part of bug 13718; bugfix on
9441 0.2.4.10-alpha. Patch by "teor".
9442 - Decrease minimum consensus interval to 10 seconds when
9443 TestingTorNetwork is set, or 5 seconds for the first consensus.
9444 Fix assumptions throughout the code that assume larger intervals.
9445 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
9447 - Avoid excluding guards from path building in minimal test
9448 networks, when we're in a test network and excluding guards would
9449 exclude all relays. This typically occurs in incredibly small tor
9450 networks, and those using "TestingAuthVoteGuard *". Fixes part of
9451 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
9453 o Code simplification and refactoring:
9454 - Stop using can_complete_circuits as a global variable; access it
9455 with a function instead.
9456 - Avoid using operators directly as macro arguments: this lets us
9457 apply coccinelle transformations to our codebase more directly.
9458 Closes ticket 13172.
9459 - Combine the functions used to parse ClientTransportPlugin and
9460 ServerTransportPlugin into a single function. Closes ticket 6456.
9461 - Add inline functions and convenience macros for inspecting channel
9462 state. Refactor the code to use convenience macros instead of
9463 checking channel state directly. Fixes issue 7356.
9464 - Document all members of was_router_added_t and rename
9465 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
9466 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
9467 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
9468 constant instead of hardcoded value. Fixes issue 13840.
9469 - Refactor our generic strmap and digestmap types into a single
9470 implementation, so that we can add a new digest256map
9474 - Document the bridge-authority-only 'networkstatus-bridges' file.
9475 Closes ticket 13713; patch from "tom".
9476 - Fix typo in PredictedPortsRelevanceTime option description in
9477 manpage. Resolves issue 13707.
9478 - Stop suggesting that users specify relays by nickname: it isn't a
9479 good idea. Also, properly cross-reference how to specify relays in
9480 all parts of manual documenting options that take a list of
9481 relays. Closes ticket 13381.
9482 - Clarify the HiddenServiceDir option description in manpage to make
9483 it clear that relative paths are taken with respect to the current
9484 working directory. Also clarify that this behavior is not
9485 guaranteed to remain indefinitely. Fixes issue 13913.
9488 - New tests for many parts of channel, relay, and circuitmux
9489 functionality. Code by Andrea; part of 9262.
9490 - New tests for parse_transport_line(). Part of ticket 6456.
9491 - In the unit tests, use chgrp() to change the group of the unit
9492 test temporary directory to the current user, so that the sticky
9493 bit doesn't interfere with tests that check directory groups.
9495 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
9499 Changes in version 0.2.6.1-alpha - 2014-10-30
9500 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
9501 includes numerous code cleanups and new tests, and fixes a large
9502 number of annoying bugs. Out-of-memory conditions are handled better
9503 than in 0.2.5, pluggable transports have improved proxy support, and
9504 clients now use optimistic data for contacting hidden services. Also,
9505 we are now more robust to changes in what we consider a parseable
9506 directory object, so that tightening restrictions does not have a risk
9507 of introducing infinite download loops.
9509 This is the first alpha release in a new series, so expect there to be
9510 bugs. Users who would rather test out a more stable branch should stay
9511 with 0.2.5.x for now.
9513 o New compiler and system requirements:
9514 - Tor 0.2.6.x requires that your compiler support more of the C99
9515 language standard than before. The 'configure' script now detects
9516 whether your compiler supports C99 mid-block declarations and
9517 designated initializers. If it does not, Tor will not compile.
9519 We may revisit this requirement if it turns out that a significant
9520 number of people need to build Tor with compilers that don't
9521 bother implementing a 15-year-old standard. Closes ticket 13233.
9522 - Tor no longer supports systems without threading support. When we
9523 began working on Tor, there were several systems that didn't have
9524 threads, or where the thread support wasn't able to run the
9525 threads of a single process on multiple CPUs. That no longer
9526 holds: every system where Tor needs to run well now has threading
9527 support. Resolves ticket 12439.
9529 o Removed platform support:
9530 - We no longer include special code to build on Windows CE; as far
9531 as we know, nobody has used Tor on Windows CE in a very long time.
9532 Closes ticket 11446.
9534 o Major features (bridges):
9535 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
9536 transports if they are configured via the "TOR_PT_PROXY"
9537 environment variable. Implements proposal 232. Resolves
9540 o Major features (client performance, hidden services):
9541 - Allow clients to use optimistic data when connecting to a hidden
9542 service, which should remove a round-trip from hidden service
9543 initialization. See proposal 181 for details. Implements
9546 o Major features (directory system):
9547 - Upon receiving an unparseable directory object, if its digest
9548 matches what we expected, then don't try to download it again.
9549 Previously, when we got a descriptor we didn't like, we would keep
9550 trying to download it over and over. Closes ticket 11243.
9552 o Major features (sample torrc):
9553 - Add a new, infrequently-changed "torrc.minimal". This file is
9554 similar to torrc.sample, but it will change as infrequently as
9555 possible, for the benefit of users whose systems prompt them for
9556 intervention whenever a default configuration file is changed.
9557 Making this change allows us to update torrc.sample to be a more
9558 generally useful "sample torrc".
9560 o Major bugfixes (directory authorities):
9561 - Do not assign the HSDir flag to relays if they are not Valid, or
9562 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
9564 o Major bugfixes (directory bandwidth performance):
9565 - Don't flush the zlib buffer aggressively when compressing
9566 directory information for clients. This should save about 7% of
9567 the bandwidth currently used for compressed descriptors and
9568 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
9570 o Minor features (security, memory wiping):
9571 - Ensure we securely wipe keys from memory after
9572 crypto_digest_get_digest and init_curve25519_keypair_from_file
9573 have finished using them. Resolves ticket 13477.
9575 o Minor features (security, out-of-memory handling):
9576 - When handling an out-of-memory condition, allocate less memory for
9577 temporary data structures. Fixes issue 10115.
9578 - When handling an out-of-memory condition, consider more types of
9579 buffers, including those on directory connections, and zlib
9580 buffers. Resolves ticket 11792.
9583 - When identity keypair is generated for first time, log a
9584 congratulatory message that links to the new relay lifecycle
9585 document. Implements feature 10427.
9587 o Minor features (client):
9588 - Clients are now willing to send optimistic data (before they
9589 receive a 'connected' cell) to relays of any version. (Relays
9590 without support for optimistic data are no longer supported on the
9591 Tor network.) Resolves ticket 13153.
9593 o Minor features (directory authorities):
9594 - Don't list relays with a bandwidth estimate of 0 in the consensus.
9595 Implements a feature proposed during discussion of bug 13000.
9596 - In tor-gencert, report an error if the user provides the same
9597 argument more than once.
9598 - If a directory authority can't find a best consensus method in the
9599 votes that it holds, it now falls back to its favorite consensus
9600 method. Previously, it fell back to method 1. Neither of these is
9601 likely to get enough signatures, but "fall back to favorite"
9602 doesn't require us to maintain support an obsolete consensus
9603 method. Implements part of proposal 215.
9605 o Minor features (logging):
9606 - On Unix-like systems, you can now use named pipes as the target of
9607 the Log option, and other options that try to append to files.
9608 Closes ticket 12061. Patch from "carlo von lynX".
9609 - When opening a log file at startup, send it every log message that
9610 we generated between startup and opening it. Previously, log
9611 messages that were generated before opening the log file were only
9612 logged to stdout. Closes ticket 6938.
9613 - Add a TruncateLogFile option to overwrite logs instead of
9614 appending to them. Closes ticket 5583.
9616 o Minor features (portability, Solaris):
9617 - Threads are no longer disabled by default on Solaris; we believe
9618 that the versions of Solaris with broken threading support are all
9619 obsolete by now. Resolves ticket 9495.
9621 o Minor features (relay):
9622 - Re-check our address after we detect a changed IP address from
9623 getsockname(). This ensures that the controller command "GETINFO
9624 address" will report the correct value. Resolves ticket 11582.
9626 - A new AccountingRule option lets Relays set whether they'd like
9627 AccountingMax to be applied separately to inbound and outbound
9628 traffic, or applied to the sum of inbound and outbound traffic.
9629 Resolves ticket 961. Patch by "chobe".
9631 o Minor features (testing networks):
9632 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
9633 the "Exit" flag regardless of their uptime, bandwidth, or exit
9634 policy. TestingTorNetwork must be set for this option to have any
9635 effect. Previously, authorities would take up to 35 minutes to
9636 give nodes the Exit flag in a test network. Partially implements
9639 o Minor features (validation):
9640 - Check all date/time values passed to tor_timegm and
9641 parse_rfc1123_time for validity, taking leap years into account.
9642 Improves HTTP header validation. Implemented with bug 13476.
9643 - In correct_tm(), limit the range of values returned by system
9644 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
9645 This means we don't have to deal with negative or too large dates,
9646 even if a clock is wrong. Otherwise we might fail to read a file
9647 written by us which includes such a date. Fixes bug 13476.
9649 o Minor bugfixes (bridge clients):
9650 - When configured to use a bridge without an identity digest (not
9651 recommended), avoid launching an extra channel to it when
9652 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
9654 o Minor bugfixes (bridges):
9655 - When DisableNetwork is set, do not launch pluggable transport
9656 plugins, and if any are running, terminate them. Fixes bug 13213;
9657 bugfix on 0.2.3.6-alpha.
9659 o Minor bugfixes (C correctness):
9660 - Fix several instances of possible integer overflow/underflow/NaN.
9661 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
9663 - In circuit_build_times_calculate_timeout() in circuitstats.c,
9664 avoid dividing by zero in the pareto calculations. This traps
9665 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
9667 - Fix an integer overflow in format_time_interval(). Fixes bug
9668 13393; bugfix on 0.2.0.10-alpha.
9669 - Set the correct day of year value when the system's localtime(_r)
9670 or gmtime(_r) functions fail to set struct tm. Not externally
9671 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
9672 - Avoid unlikely signed integer overflow in tor_timegm on systems
9673 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
9675 o Minor bugfixes (client):
9676 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
9677 BadExit flag are not considered worthy candidates. Fixes bug
9678 13066; bugfix on 0.1.2.3-alpha.
9679 - Use the consensus schedule for downloading consensuses, and not
9680 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
9681 - Handle unsupported or malformed SOCKS5 requests properly by
9682 responding with the appropriate error message before closing the
9683 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
9685 o Minor bugfixes (client, torrc):
9686 - Stop modifying the value of our DirReqStatistics torrc option just
9687 because we're not a bridge or relay. This bug was causing Tor
9688 Browser users to write "DirReqStatistics 0" in their torrc files
9689 as if they had chosen to change the config. Fixes bug 4244; bugfix
9691 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
9692 that our options have changed every time we SIGHUP. Fixes bug
9693 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
9695 o Minor bugfixes (controller):
9696 - Return an error when the second or later arguments of the
9697 "setevents" controller command are invalid events. Previously we
9698 would return success while silently skipping invalid events. Fixes
9699 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
9701 o Minor bugfixes (directory system):
9702 - Always believe that v3 directory authorities serve extra-info
9703 documents, whether they advertise "caches-extra-info" or not.
9704 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
9705 - When running as a v3 directory authority, advertise that you serve
9706 extra-info documents so that clients who want them can find them
9707 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
9708 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
9709 Previously, directories offering BRIDGE_DIRINFO and some other
9710 flag (i.e. microdescriptors or extrainfo) would be ignored when
9711 looking for bridges. Partially fixes bug 13163; bugfix
9714 o Minor bugfixes (networking):
9715 - Check for orconns and use connection_or_close_for_error() rather
9716 than connection_mark_for_close() directly in the getsockopt()
9717 failure case of connection_handle_write_impl(). Fixes bug 11302;
9718 bugfix on 0.2.4.4-alpha.
9720 o Minor bugfixes (relay):
9721 - When generating our family list, remove spaces from around the
9722 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
9723 - If our previous bandwidth estimate was 0 bytes, allow publishing a
9724 new relay descriptor immediately. Fixes bug 13000; bugfix
9727 o Minor bugfixes (testing networks):
9728 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
9729 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
9730 - Stop using the default authorities in networks which provide both
9731 AlternateDirAuthority and AlternateBridgeAuthority. Partially
9732 fixes bug 13163; bugfix on 0.2.0.13-alpha.
9734 o Minor bugfixes (testing):
9735 - Stop spawn test failures due to a race condition between the
9736 SIGCHLD handler updating the process status, and the test reading
9737 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
9739 o Minor bugfixes (testing, Windows):
9740 - Avoid passing an extra backslash when creating a temporary
9741 directory for running the unit tests on Windows. Fixes bug 12392;
9742 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
9744 o Minor bugfixes (windows):
9745 - Remove code to special-case handling of NTE_BAD_KEYSET when
9746 acquiring windows CryptoAPI context. This error can't actually
9747 occur for the parameters we're providing. Fixes bug 10816; bugfix
9750 o Minor bugfixes (zlib):
9751 - Avoid truncating a zlib stream when trying to finalize it with an
9752 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
9755 - Allow our configure script to build correctly with autoconf 2.62
9756 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
9757 - Improve the error message from ./configure to make it clear that
9758 when asciidoc has not been found, the user will have to either add
9759 --disable-asciidoc argument or install asciidoc. Resolves
9762 o Code simplification and refactoring:
9763 - Change the entry_is_live() function to take named bitfield
9764 elements instead of an unnamed list of booleans. Closes
9766 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
9767 Resolves ticket 12205.
9768 - Use calloc and reallocarray functions instead of multiply-
9769 then-malloc. This makes it less likely for us to fall victim to an
9770 integer overflow attack when allocating. Resolves ticket 12855.
9771 - Use the standard macro name SIZE_MAX, instead of our
9773 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
9774 functions which take them as arguments. Replace 0 with NO_DIRINFO
9775 in a function call for clarity. Seeks to prevent future issues
9777 - Avoid 4 null pointer errors under clang static analysis by using
9778 tor_assert() to prove that the pointers aren't null. Fixes
9780 - Rework the API of policies_parse_exit_policy() to use a bitmask to
9781 represent parsing options, instead of a confusing mess of
9782 booleans. Resolves ticket 8197.
9783 - Introduce a helper function to parse ExitPolicy in
9784 or_options_t structure.
9787 - Add a doc/TUNING document with tips for handling large numbers of
9788 TCP connections when running busy Tor relay. Update the warning
9789 message to point to this file when running out of sockets
9790 operating system is allowing to use simultaneously. Resolves
9794 - We no longer remind the user about configuration options that have
9795 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
9796 - Remove our old, non-weighted bandwidth-based node selection code.
9797 Previously, we used it as a fallback when we couldn't perform
9798 weighted bandwidth-based node selection. But that would only
9799 happen in the cases where we had no consensus, or when we had a
9800 consensus generated by buggy or ancient directory authorities. In
9801 either case, it's better to use the more modern, better maintained
9802 algorithm, with reasonable defaults for the weights. Closes
9804 - Remove the --disable-curve25519 configure option. Relays and
9805 clients now are required to support curve25519 and the
9807 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
9808 used to be deprecated synonyms for "StrictNodes", are now marked
9809 obsolete. Resolves ticket 12226.
9810 - Clients don't understand the BadDirectory flag in the consensus
9811 anymore, and ignore it.
9814 - Refactor the function that chooses guard nodes so that it can more
9815 easily be tested; write some tests for it.
9816 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
9817 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
9818 - Create unit tests for format_time_interval(). With bug 13393.
9819 - Add unit tests for tor_timegm signed overflow, tor_timegm and
9820 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
9821 tests (visible) fixes in bug 13476.
9822 - Add a "coverage-html" make target to generate HTML-visualized
9823 coverage results when building with --enable-coverage. (Requires
9824 lcov.) Patch from Kevin Murray.
9825 - Enable the backtrace handler (where supported) when running the
9827 - Revise all unit tests that used the legacy test_* macros to
9828 instead use the recommended tt_* macros. This patch was generated
9829 with coccinelle, to avoid manual errors. Closes ticket 13119.
9831 o Distribution (systemd):
9832 - systemd unit file: only allow tor to write to /var/lib/tor and
9833 /var/log/tor. The rest of the filesystem is accessible for reading
9834 only. Patch by intrigeri; resolves ticket 12751.
9835 - systemd unit file: ensure that the process and all its children
9836 can never gain new privileges. Patch by intrigeri; resolves
9838 - systemd unit file: set up /var/run/tor as writable for the Tor
9839 service. Patch by intrigeri; resolves ticket 13196.
9841 o Removed features (directory authorities):
9842 - Remove code that prevented authorities from listing Tor relays
9843 affected by CVE-2011-2769 as guards. These relays are already
9844 rejected altogether due to the minimum version requirement of
9845 0.2.3.16-alpha. Closes ticket 13152.
9846 - The "AuthDirRejectUnlisted" option no longer has any effect, as
9847 the fingerprints file (approved-routers) has been deprecated.
9848 - Directory authorities do not support being Naming dirauths anymore.
9849 The "NamingAuthoritativeDir" config option is now obsolete.
9850 - Directory authorities do not support giving out the BadDirectory
9852 - Directory authorities no longer advertise or support consensus
9853 methods 1 through 12 inclusive. These consensus methods were
9854 obsolete and/or insecure: maintaining the ability to support them
9855 served no good purpose. Implements part of proposal 215; closes
9858 o Testing (test-network.sh):
9859 - Stop using "echo -n", as some shells' built-in echo doesn't
9860 support "-n". Instead, use "/bin/echo -n". Partially fixes
9862 - Stop an apparent test-network hang when used with make -j2. Fixes
9864 - Add a --delay option to test-network.sh, which configures the
9865 delay before the chutney network tests for data transmission.
9866 Partially implements ticket 13161.
9869 Changes in version 0.2.5.10 - 2014-10-24
9870 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
9872 It adds several new security features, including improved
9873 denial-of-service resistance for relays, new compiler hardening
9874 options, and a system-call sandbox for hardened installations on Linux
9875 (requires seccomp2). The controller protocol has several new features,
9876 resolving IPv6 addresses should work better than before, and relays
9877 should be a little more CPU-efficient. We've added support for more
9878 OpenBSD and FreeBSD transparent proxy types. We've improved the build
9879 system and testing infrastructure to allow unit testing of more parts
9880 of the Tor codebase. Finally, we've addressed several nagging pluggable
9881 transport usability issues, and included numerous other small bugfixes
9882 and features mentioned below.
9884 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
9885 have accumulated many known flaws; everyone should upgrade.
9887 o Deprecated versions:
9888 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
9889 attention for some while.
9892 Changes in version 0.2.5.9-rc - 2014-10-20
9893 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
9894 series. It disables SSL3 in response to the recent "POODLE" attack
9895 (even though POODLE does not affect Tor). It also works around a crash
9896 bug caused by some operating systems' response to the "POODLE" attack
9897 (which does affect Tor). It also contains a few miscellaneous fixes.
9899 o Major security fixes:
9900 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9901 today support TLS 1.0 or later, so we can safely turn off support
9902 for this old (and insecure) protocol. Fixes bug 13426.
9904 o Major bugfixes (openssl bug workaround):
9905 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9906 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9907 13471. This is a workaround for an OpenSSL bug.
9910 - Disable the sandbox name resolver cache when running tor-resolve:
9911 tor-resolve doesn't use the sandbox code, and turning it on was
9912 breaking attempts to do tor-resolve on a non-default server on
9913 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
9915 o Compilation fixes:
9916 - Build and run correctly on systems like OpenBSD-current that have
9917 patched OpenSSL to remove get_cipher_by_char and/or its
9918 implementations. Fixes issue 13325.
9920 o Downgraded warnings:
9921 - Downgrade the severity of the 'unexpected sendme cell from client'
9922 from 'warn' to 'protocol warning'. Closes ticket 8093.
9925 Changes in version 0.2.4.25 - 2014-10-20
9926 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9927 (even though POODLE does not affect Tor). It also works around a crash
9928 bug caused by some operating systems' response to the "POODLE" attack
9929 (which does affect Tor).
9931 o Major security fixes (also in 0.2.5.9-rc):
9932 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9933 today support TLS 1.0 or later, so we can safely turn off support
9934 for this old (and insecure) protocol. Fixes bug 13426.
9936 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9937 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9938 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9939 13471. This is a workaround for an OpenSSL bug.
9942 Changes in version 0.2.5.8-rc - 2014-09-22
9943 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
9944 series. It fixes a bug that affects consistency and speed when
9945 connecting to hidden services, and it updates the location of one of
9946 the directory authorities.
9949 - Clients now send the correct address for their chosen rendezvous
9950 point when trying to access a hidden service. They used to send
9951 the wrong address, which would still work some of the time because
9952 they also sent the identity digest of the rendezvous point, and if
9953 the hidden service happened to try connecting to the rendezvous
9954 point from a relay that already had a connection open to it,
9955 the relay would reuse that connection. Now connections to hidden
9956 services should be more robust and faster. Also, this bug meant
9957 that clients were leaking to the hidden service whether they were
9958 on a little-endian (common) or big-endian (rare) system, which for
9959 some users might have reduced their anonymity. Fixes bug 13151;
9960 bugfix on 0.2.1.5-alpha.
9962 o Directory authority changes:
9963 - Change IP address for gabelmoo (v3 directory authority).
9966 Changes in version 0.2.4.24 - 2014-09-22
9967 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9968 connecting to hidden services, and it updates the location of one of
9969 the directory authorities.
9972 - Clients now send the correct address for their chosen rendezvous
9973 point when trying to access a hidden service. They used to send
9974 the wrong address, which would still work some of the time because
9975 they also sent the identity digest of the rendezvous point, and if
9976 the hidden service happened to try connecting to the rendezvous
9977 point from a relay that already had a connection open to it,
9978 the relay would reuse that connection. Now connections to hidden
9979 services should be more robust and faster. Also, this bug meant
9980 that clients were leaking to the hidden service whether they were
9981 on a little-endian (common) or big-endian (rare) system, which for
9982 some users might have reduced their anonymity. Fixes bug 13151;
9983 bugfix on 0.2.1.5-alpha.
9985 o Directory authority changes:
9986 - Change IP address for gabelmoo (v3 directory authority).
9988 o Minor features (geoip):
9989 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9993 Changes in version 0.2.5.7-rc - 2014-09-11
9994 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
9995 release series, and some long-standing bugs related to ORPort reachability
9996 testing and failure to send CREATE cells. It is the first release
9997 candidate for the Tor 0.2.5.x series.
9999 o Major bugfixes (client, startup):
10000 - Start making circuits as soon as DisabledNetwork is turned off.
10001 When Tor started with DisabledNetwork set, it would correctly
10002 conclude that it shouldn't build circuits, but it would mistakenly
10003 cache this conclusion, and continue believing it even when
10004 DisableNetwork is set to 0. Fixes the bug introduced by the fix
10005 for bug 11200; bugfix on 0.2.5.4-alpha.
10006 - Resume expanding abbreviations for command-line options. The fix
10007 for bug 4647 accidentally removed our hack from bug 586 that
10008 rewrote HashedControlPassword to __HashedControlSessionPassword
10009 when it appears on the commandline (which allowed the user to set
10010 her own HashedControlPassword in the torrc file while the
10011 controller generates a fresh session password for each run). Fixes
10012 bug 12948; bugfix on 0.2.5.1-alpha.
10013 - Warn about attempts to run hidden services and relays in the same
10014 process: that's probably not a good idea. Closes ticket 12908.
10016 o Major bugfixes (relay):
10017 - Avoid queuing or sending destroy cells for circuit ID zero when we
10018 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
10019 Found and fixed by "cypherpunks".
10020 - Fix ORPort reachability detection on relays running behind a
10021 proxy, by correctly updating the "local" mark on the controlling
10022 channel when changing the address of an or_connection_t after the
10023 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
10025 o Minor features (bridge):
10026 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
10027 cookie file for the ExtORPort g+r by default.
10029 o Minor features (geoip):
10030 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
10033 o Minor bugfixes (logging):
10034 - Reduce the log severity of the "Pluggable transport proxy does not
10035 provide any needed transports and will not be launched." message,
10036 since Tor Browser includes several ClientTransportPlugin lines in
10037 its torrc-defaults file, leading every Tor Browser user who looks
10038 at her logs to see these notices and wonder if they're dangerous.
10039 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
10040 - Downgrade "Unexpected onionskin length after decryption" warning
10041 to a protocol-warn, since there's nothing relay operators can do
10042 about a client that sends them a malformed create cell. Resolves
10043 bug 12996; bugfix on 0.0.6rc1.
10044 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
10045 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
10046 - When logging information about an EXTEND2 or EXTENDED2 cell, log
10047 their names correctly. Fixes part of bug 12700; bugfix
10049 - When logging information about a relay cell whose command we don't
10050 recognize, log its command as an integer. Fixes part of bug 12700;
10051 bugfix on 0.2.1.10-alpha.
10052 - Escape all strings from the directory connection before logging
10053 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
10055 o Minor bugfixes (controller):
10056 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
10057 bug 12864; bugfix on 0.2.5.1-alpha.
10058 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
10059 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
10062 o Minor bugfixes (compilation):
10063 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
10064 bugfix on 0.2.5.5-alpha.
10065 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
10066 0.2.5.1-alpha. Patch from "NewEraCracker".
10067 - In routerlist_assert_ok(), don't take the address of a
10068 routerinfo's cache_info member unless that routerinfo is non-NULL.
10069 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
10070 - Fix a large number of false positive warnings from the clang
10071 analyzer static analysis tool. This should make real warnings
10072 easier for clang analyzer to find. Patch from "teor". Closes
10075 o Distribution (systemd):
10076 - Verify configuration file via ExecStartPre in the systemd unit
10077 file. Patch from intrigeri; resolves ticket 12730.
10078 - Explicitly disable RunAsDaemon in the systemd unit file. Our
10079 current systemd unit uses "Type = simple", so systemd does not
10080 expect tor to fork. If the user has "RunAsDaemon 1" in their
10081 torrc, then things won't work as expected. This is e.g. the case
10082 on Debian (and derivatives), since there we pass "--defaults-torrc
10083 /usr/share/tor/tor-service-defaults-torrc" (that contains
10084 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
10088 - Adjust the URLs in the README to refer to the new locations of
10089 several documents on the website. Fixes bug 12830. Patch from
10091 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
10095 Changes in version 0.2.5.6-alpha - 2014-07-28
10096 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
10097 risk from guard rotation, and fixes a variety of other issues to get
10098 us closer to a release candidate.
10100 o Major features (also in 0.2.4.23):
10101 - Make the number of entry guards configurable via a new
10102 NumEntryGuards consensus parameter, and the number of directory
10103 guards configurable via a new NumDirectoryGuards consensus
10104 parameter. Implements ticket 12688.
10106 o Major bugfixes (also in 0.2.4.23):
10107 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
10108 implementation that caused incorrect results on 32-bit
10109 implementations when certain malformed inputs were used along with
10110 a small class of private ntor keys. This bug does not currently
10111 appear to allow an attacker to learn private keys or impersonate a
10112 Tor server, but it could provide a means to distinguish 32-bit Tor
10113 implementations from 64-bit Tor implementations. Fixes bug 12694;
10114 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
10118 - Perform circuit cleanup operations even when circuit
10119 construction operations are disabled (because the network is
10120 disabled, or because there isn't enough directory information).
10121 Previously, when we were not building predictive circuits, we
10122 were not closing expired circuits either. Fixes bug 8387; bugfix on
10123 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
10124 became more strict about when we have "enough directory information
10125 to build circuits".
10128 - Authorities now assign the Guard flag to the fastest 25% of the
10129 network (it used to be the fastest 50%). Also raise the consensus
10130 weight that guarantees the Guard flag from 250 to 2000. For the
10131 current network, this results in about 1100 guards, down from 2500.
10132 This step paves the way for moving the number of entry guards
10133 down to 1 (proposal 236) while still providing reasonable expected
10134 performance for most users. Implements ticket 12690.
10135 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
10137 - Slightly enhance the diagnostic message for bug 12184.
10139 o Minor bugfixes (also in 0.2.4.23):
10140 - Warn and drop the circuit if we receive an inbound 'relay early'
10141 cell. Those used to be normal to receive on hidden service circuits
10142 due to bug 1038, but the buggy Tor versions are long gone from
10143 the network so we can afford to resume watching for them. Resolves
10144 the rest of bug 1038; bugfix on 0.2.1.19.
10145 - Correct a confusing error message when trying to extend a circuit
10146 via the control protocol but we don't know a descriptor or
10147 microdescriptor for one of the specified relays. Fixes bug 12718;
10148 bugfix on 0.2.3.1-alpha.
10151 - Fix compilation when building with bufferevents enabled. (This
10152 configuration is still not expected to work, however.)
10153 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
10154 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
10156 - Compile correctly with builds and forks of OpenSSL (such as
10157 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
10158 0.2.1.1-alpha. Patch from "dhill".
10161 Changes in version 0.2.4.23 - 2014-07-28
10162 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
10163 guard rotation, and also backports several important fixes from the
10164 Tor 0.2.5 alpha release series.
10167 - Clients now look at the "usecreatefast" consensus parameter to
10168 decide whether to use CREATE_FAST or CREATE cells for the first hop
10169 of their circuit. This approach can improve security on connections
10170 where Tor's circuit handshake is stronger than the available TLS
10171 connection security levels, but the tradeoff is more computational
10172 load on guard relays. Implements proposal 221. Resolves ticket 9386.
10173 - Make the number of entry guards configurable via a new
10174 NumEntryGuards consensus parameter, and the number of directory
10175 guards configurable via a new NumDirectoryGuards consensus
10176 parameter. Implements ticket 12688.
10179 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
10180 implementation that caused incorrect results on 32-bit
10181 implementations when certain malformed inputs were used along with
10182 a small class of private ntor keys. This bug does not currently
10183 appear to allow an attacker to learn private keys or impersonate a
10184 Tor server, but it could provide a means to distinguish 32-bit Tor
10185 implementations from 64-bit Tor implementations. Fixes bug 12694;
10186 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
10190 - Warn and drop the circuit if we receive an inbound 'relay early'
10191 cell. Those used to be normal to receive on hidden service circuits
10192 due to bug 1038, but the buggy Tor versions are long gone from
10193 the network so we can afford to resume watching for them. Resolves
10194 the rest of bug 1038; bugfix on 0.2.1.19.
10195 - Correct a confusing error message when trying to extend a circuit
10196 via the control protocol but we don't know a descriptor or
10197 microdescriptor for one of the specified relays. Fixes bug 12718;
10198 bugfix on 0.2.3.1-alpha.
10199 - Avoid an illegal read from stack when initializing the TLS
10200 module using a version of OpenSSL without all of the ciphers
10201 used by the v2 link handshake. Fixes bug 12227; bugfix on
10202 0.2.4.8-alpha. Found by "starlight".
10205 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
10209 Changes in version 0.2.5.5-alpha - 2014-06-18
10210 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
10211 0.2.5.x release series, including a couple of DoS issues, some
10212 performance regressions, a large number of bugs affecting the Linux
10213 seccomp2 sandbox code, and various other bugfixes. It also adds
10214 diagnostic bugfixes for a few tricky issues that we're trying to
10217 o Major features (security, traffic analysis resistance):
10218 - Several major improvements to the algorithm used to decide when to
10219 close TLS connections. Previous versions of Tor closed connections
10220 at a fixed interval after the last time a non-padding cell was
10221 sent over the connection, regardless of the target of the
10222 connection. Now, we randomize the intervals by adding up to 50% of
10223 their base value, we measure the length of time since connection
10224 last had at least one circuit, and we allow connections to known
10225 ORs to remain open a little longer (15 minutes instead of 3
10226 minutes minimum). These changes should improve Tor's resistance
10227 against some kinds of traffic analysis, and lower some overhead
10228 from needlessly closed connections. Fixes ticket 6799.
10229 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
10231 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
10232 - Fix a memory leak that could occur if a microdescriptor parse
10233 fails during the tokenizing step. This bug could enable a memory
10234 exhaustion attack by directory servers. Fixes bug 11649; bugfix
10237 o Major bugfixes (security, directory authorities):
10238 - Directory authorities now include a digest of each relay's
10239 identity key as a part of its microdescriptor.
10241 This is a workaround for bug 11743 (reported by "cypherpunks"),
10242 where Tor clients do not support receiving multiple
10243 microdescriptors with the same SHA256 digest in the same
10244 consensus. When clients receive a consensus like this, they only
10245 use one of the relays. Without this fix, a hostile relay could
10246 selectively disable some client use of target relays by
10247 constructing a router descriptor with a different identity and the
10248 same microdescriptor parameters and getting the authorities to
10249 list it in a microdescriptor consensus. This fix prevents an
10250 attacker from causing a microdescriptor collision, because the
10251 router's identity is not forgeable.
10253 o Major bugfixes (relay):
10254 - Use a direct dirport connection when uploading non-anonymous
10255 descriptors to the directory authorities. Previously, relays would
10256 incorrectly use tunnel connections under a fairly wide variety of
10257 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
10258 - When a circuit accidentally has the same circuit ID for its
10259 forward and reverse direction, correctly detect the direction of
10260 cells using that circuit. Previously, this bug made roughly one
10261 circuit in a million non-functional. Fixes bug 12195; this is a
10262 bugfix on every version of Tor.
10264 o Major bugfixes (client, pluggable transports):
10265 - When managing pluggable transports, use OS notification facilities
10266 to learn if they have crashed, and don't attempt to kill any
10267 process that has already exited. Fixes bug 8746; bugfix
10270 o Minor features (diagnostic):
10271 - When logging a warning because of bug 7164, additionally check the
10272 hash table for consistency (as proposed on ticket 11737). This may
10273 help diagnose bug 7164.
10274 - When we log a heartbeat, log how many one-hop circuits we have
10275 that are at least 30 minutes old, and log status information about
10276 a few of them. This is an attempt to track down bug 8387.
10277 - When encountering an unexpected CR while writing text to a file on
10278 Windows, log the name of the file. Should help diagnosing
10280 - Give more specific warnings when a client notices that an onion
10281 handshake has failed. Fixes ticket 9635.
10282 - Add significant new logging code to attempt to diagnose bug 12184,
10283 where relays seem to run out of available circuit IDs.
10284 - Improve the diagnostic log message for bug 8387 even further to
10285 try to improve our odds of figuring out why one-hop directory
10286 circuits sometimes do not get closed.
10288 o Minor features (security, memory management):
10289 - Memory allocation tricks (mempools and buffer freelists) are now
10290 disabled by default. You can turn them back on with
10291 --enable-mempools and --enable-buf-freelists respectively. We're
10292 disabling these features because malloc performance is good enough
10293 on most platforms, and a similar feature in OpenSSL exacerbated
10294 exploitation of the Heartbleed attack. Resolves ticket 11476.
10296 o Minor features (security):
10297 - Apply the secure SipHash-2-4 function to the hash table mapping
10298 circuit IDs and channels to circuits. We missed this one when we
10299 were converting all the other hash functions to use SipHash back
10300 in 0.2.5.3-alpha. Resolves ticket 11750.
10302 o Minor features (build):
10303 - The configure script has a --disable-seccomp option to turn off
10304 support for libseccomp on systems that have it, in case it (or
10305 Tor's use of it) is broken. Resolves ticket 11628.
10307 o Minor features (other):
10308 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
10311 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
10312 - When running a hidden service, do not allow TunneledDirConns 0;
10313 this will keep the hidden service from running, and also
10314 make it publish its descriptors directly over HTTP. Fixes bug 10849;
10315 bugfix on 0.2.1.1-alpha.
10317 o Minor bugfixes (performance):
10318 - Avoid a bug where every successful connection made us recompute
10319 the flag telling us whether we have sufficient information to
10320 build circuits. Previously, we would forget our cached value
10321 whenever we successfully opened a channel (or marked a router as
10322 running or not running for any other reason), regardless of
10323 whether we had previously believed the router to be running. This
10324 forced us to run an expensive update operation far too often.
10325 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
10326 - Avoid using tor_memeq() for checking relay cell integrity. This
10327 removes a possible performance bottleneck. Fixes part of bug
10328 12169; bugfix on 0.2.1.31.
10330 o Minor bugfixes (compilation):
10331 - Fix compilation of test_status.c when building with MVSC. Bugfix
10332 on 0.2.5.4-alpha. Patch from Gisle Vanem.
10333 - Resolve GCC complaints on OpenBSD about discarding constness in
10334 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
10335 on 0.1.1.23. Patch from Dana Koch.
10336 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
10337 treatment of long and time_t as comparable types. Fixes part of
10338 bug 11633. Patch from Dana Koch.
10339 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
10340 11623; bugfix on 0.2.5.3-alpha.
10341 - When deciding whether to build the 64-bit curve25519
10342 implementation, detect platforms where we can compile 128-bit
10343 arithmetic but cannot link it. Fixes bug 11729; bugfix on
10344 0.2.4.8-alpha. Patch from "conradev".
10345 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
10346 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
10347 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
10350 o Minor bugfixes (Directory server):
10351 - When sending a compressed set of descriptors or microdescriptors,
10352 make sure to finalize the zlib stream. Previously, we would write
10353 all the compressed data, but if the last descriptor we wanted to
10354 send was missing or too old, we would not mark the stream as
10355 finished. This caused problems for decompression tools. Fixes bug
10356 11648; bugfix on 0.1.1.23.
10358 o Minor bugfixes (Linux seccomp sandbox):
10359 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
10360 11622; bugfix on 0.2.5.1-alpha.
10361 - Avoid crashing when re-opening listener ports with the seccomp
10362 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
10363 - Avoid crashing with the seccomp sandbox enabled along with
10364 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
10365 - When we receive a SIGHUP with the sandbox enabled, correctly
10366 support rotating our log files. Fixes bug 12032; bugfix
10368 - Avoid crash when running with sandboxing enabled and
10369 DirReqStatistics not disabled. Fixes bug 12035; bugfix
10371 - Fix a "BUG" warning when trying to write bridge-stats files with
10372 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
10374 - Prevent the sandbox from crashing on startup when run with the
10375 --enable-expensive-hardening configuration option. Fixes bug
10376 11477; bugfix on 0.2.5.4-alpha.
10377 - When running with DirPortFrontPage and sandboxing both enabled,
10378 reload the DirPortFrontPage correctly when restarting. Fixes bug
10379 12028; bugfix on 0.2.5.1-alpha.
10380 - Don't try to enable the sandbox when using the Tor binary to check
10381 its configuration, hash a passphrase, or so on. Doing so was
10382 crashing on startup for some users. Fixes bug 11609; bugfix
10384 - Avoid warnings when running with sandboxing and node statistics
10385 enabled at the same time. Fixes part of 12064; bugfix on
10386 0.2.5.1-alpha. Patch from Michael Wolf.
10387 - Avoid warnings when running with sandboxing enabled at the same
10388 time as cookie authentication, hidden services, or directory
10389 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
10390 - Do not allow options that require calls to exec to be enabled
10391 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
10392 bug 12043; bugfix on 0.2.5.1-alpha.
10393 - Handle failures in getpwnam()/getpwuid() when running with the
10394 User option set and the Linux syscall sandbox enabled. Fixes bug
10395 11946; bugfix on 0.2.5.1-alpha.
10396 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
10397 to avoid calling getaddrinfo() after installing the sandbox
10398 filters. Previously, it preloaded a cache with the IPv4 address
10399 for our hostname, and nothing else. Now, it loads the cache with
10400 every address that it used to initialize the Tor process. Fixes
10401 bug 11970; bugfix on 0.2.5.1-alpha.
10403 o Minor bugfixes (pluggable transports):
10404 - Enable the ExtORPortCookieAuthFile option, to allow changing the
10405 default location of the authentication token for the extended OR
10406 Port as used by sever-side pluggable transports. We had
10407 implemented this option before, but the code to make it settable
10408 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
10409 - Avoid another 60-second delay when starting Tor in a pluggable-
10410 transport-using configuration when we already have cached
10411 descriptors for our bridges. Fixes bug 11965; bugfix
10414 o Minor bugfixes (client):
10415 - Avoid "Tried to open a socket with DisableNetwork set" warnings
10416 when starting a client with bridges configured and DisableNetwork
10417 set. (Tor launcher starts Tor with DisableNetwork set the first
10418 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
10420 o Minor bugfixes (testing):
10421 - The Python parts of the test scripts now work on Python 3 as well
10422 as Python 2, so systems where '/usr/bin/python' is Python 3 will
10423 no longer have the tests break. Fixes bug 11608; bugfix
10425 - When looking for versions of python that we could run the tests
10426 with, check for "python2.7" and "python3.3"; previously we were
10427 only looking for "python", "python2", and "python3". Patch from
10428 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
10429 - Fix all valgrind warnings produced by the unit tests. There were
10430 over a thousand memory leak warnings previously, mostly produced
10431 by forgetting to free things in the unit test code. Fixes bug
10432 11618, bugfixes on many versions of Tor.
10434 o Minor bugfixes (tor-fw-helper):
10435 - Give a correct log message when tor-fw-helper fails to launch.
10436 (Previously, we would say something like "tor-fw-helper sent us a
10437 string we could not parse".) Fixes bug 9781; bugfix
10440 o Minor bugfixes (relay, threading):
10441 - Check return code on spawn_func() in cpuworker code, so that we
10442 don't think we've spawned a nonworking cpuworker and write junk to
10443 it forever. Fix related to bug 4345; bugfix on all released Tor
10444 versions. Found by "skruffy".
10445 - Use a pthread_attr to make sure that spawn_func() cannot return an
10446 error while at the same time launching a thread. Fix related to
10447 bug 4345; bugfix on all released Tor versions. Reported
10450 o Minor bugfixes (relay, oom prevention):
10451 - Correctly detect the total available system memory. We tried to do
10452 this in 0.2.5.4-alpha, but the code was set up to always return an
10453 error value, even on success. Fixes bug 11805; bugfix
10456 o Minor bugfixes (relay, other):
10457 - We now drop CREATE cells for already-existent circuit IDs and for
10458 zero-valued circuit IDs, regardless of other factors that might
10459 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
10461 - Avoid an illegal read from stack when initializing the TLS module
10462 using a version of OpenSSL without all of the ciphers used by the
10463 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
10465 - When rejecting DATA cells for stream_id zero, still count them
10466 against the circuit's deliver window so that we don't fail to send
10467 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
10469 o Minor bugfixes (logging):
10470 - Fix a misformatted log message about delayed directory fetches.
10471 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
10472 - Squelch a spurious LD_BUG message "No origin circuit for
10473 successful SOCKS stream" in certain hidden service failure cases;
10477 - Include a tor.service file in contrib/dist for use with systemd.
10478 Some distributions will be able to use this file unmodified;
10479 others will need to tweak it, or write their own. Patch from Jamie
10480 Nguyen; resolves ticket 8368.
10483 - Clean up several option names in the manpage to match their real
10484 names, add the missing documentation for a couple of testing and
10485 directory authority options, remove the documentation for a
10486 V2-directory fetching option that no longer exists. Resolves
10488 - Correct the documentation so that it lists the correct directory
10489 for the stats files. (They are in a subdirectory called "stats",
10491 - In the manpage, move more authority-only options into the
10492 directory authority section so that operators of regular directory
10493 caches don't get confused.
10496 - The contrib directory has been sorted and tidied. Before, it was
10497 an unsorted dumping ground for useful and not-so-useful things.
10498 Now, it is divided based on functionality, and the items which
10499 seemed to be nonfunctional or useless have been removed. Resolves
10500 ticket 8966; based on patches from "rl1987".
10503 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
10504 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
10505 - The TunnelDirConns and PreferTunnelledDirConns options no longer
10506 exist; tunneled directory connections have been available since
10507 0.1.2.5-alpha, and turning them off is not a good idea. This is a
10508 brute-force fix for 10849, where "TunnelDirConns 0" would break
10512 Changes in version 0.2.4.22 - 2014-05-16
10513 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
10514 alpha release series. These include blocking all authority signing
10515 keys that may have been affected by the OpenSSL "heartbleed" bug,
10516 choosing a far more secure set of TLS ciphersuites by default, closing
10517 a couple of memory leaks that could be used to run a target relay out
10518 of RAM, and several others.
10520 o Major features (security, backport from 0.2.5.4-alpha):
10521 - Block authority signing keys that were used on authorities
10522 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
10523 don't have any evidence that these keys _were_ compromised; we're
10524 doing this to be prudent.) Resolves ticket 11464.
10526 o Major bugfixes (security, OOM):
10527 - Fix a memory leak that could occur if a microdescriptor parse
10528 fails during the tokenizing step. This bug could enable a memory
10529 exhaustion attack by directory servers. Fixes bug 11649; bugfix
10532 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
10533 - The relay ciphersuite list is now generated automatically based on
10534 uniform criteria, and includes all OpenSSL ciphersuites with
10535 acceptable strength and forward secrecy. Previously, we had left
10536 some perfectly fine ciphersuites unsupported due to omission or
10537 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
10538 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
10539 - Relays now trust themselves to have a better view than clients of
10540 which TLS ciphersuites are better than others. (Thanks to bug
10541 11513, the relay list is now well-considered, whereas the client
10542 list has been chosen mainly for anti-fingerprinting purposes.)
10543 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
10544 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
10545 AES128. Resolves ticket 11528.
10546 - Clients now try to advertise the same list of ciphersuites as
10547 Firefox 28. This change enables selection of (fast) GCM
10548 ciphersuites, disables some strange old ciphers, and stops
10549 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
10550 Resolves ticket 11438.
10552 o Minor bugfixes (configuration, security):
10553 - When running a hidden service, do not allow TunneledDirConns 0:
10554 trying to set that option together with a hidden service would
10555 otherwise prevent the hidden service from running, and also make
10556 it publish its descriptors directly over HTTP. Fixes bug 10849;
10557 bugfix on 0.2.1.1-alpha.
10559 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
10560 - Avoid sending a garbage value to the controller when a circuit is
10561 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
10563 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
10564 - Stop leaking memory when we successfully resolve a PTR record.
10565 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
10567 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
10568 - Avoid 60-second delays in the bootstrapping process when Tor is
10569 launching for a second time while using bridges. Fixes bug 9229;
10570 bugfix on 0.2.0.3-alpha.
10572 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
10573 - Give the correct URL in the warning message when trying to run a
10574 relay on an ancient version of Windows. Fixes bug 9393.
10576 o Minor bugfixes (compilation):
10577 - Fix a compilation error when compiling with --disable-curve25519.
10578 Fixes bug 9700; bugfix on 0.2.4.17-rc.
10581 - Downgrade the warning severity for the the "md was still
10582 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
10583 for trying to diagnose this bug, and the current warning in
10584 earlier versions of tor achieves nothing useful. Addresses warning
10587 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
10588 - When we run out of usable circuit IDs on a channel, log only one
10589 warning for the whole channel, and describe how many circuits
10590 there were on the channel. Fixes part of ticket 11553.
10592 o Minor features (security, backport from 0.2.5.4-alpha):
10593 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
10594 leave the default at 8GBytes), to better support Raspberry Pi
10595 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
10597 o Documentation (backport from 0.2.5.4-alpha):
10598 - Correctly document that we search for a system torrc file before
10599 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
10603 Changes in version 0.2.5.4-alpha - 2014-04-25
10604 Tor 0.2.5.4-alpha includes several security and performance
10605 improvements for clients and relays, including blacklisting authority
10606 signing keys that were used while susceptible to the OpenSSL
10607 "heartbleed" bug, fixing two expensive functions on busy relays,
10608 improved TLS ciphersuite preference lists, support for run-time
10609 hardening on compilers that support AddressSanitizer, and more work on
10610 the Linux sandbox code.
10612 There are also several usability fixes for clients (especially clients
10613 that use bridges), two new TransPort protocols supported (one on
10614 OpenBSD, one on FreeBSD), and various other bugfixes.
10616 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
10617 have accumulated many known flaws; everyone should upgrade.
10619 o Major features (security):
10620 - If you don't specify MaxMemInQueues yourself, Tor now tries to
10621 pick a good value based on your total system memory. Previously,
10622 the default was always 8 GB. You can still override the default by
10623 setting MaxMemInQueues yourself. Resolves ticket 11396.
10624 - Block authority signing keys that were used on authorities
10625 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
10626 don't have any evidence that these keys _were_ compromised; we're
10627 doing this to be prudent.) Resolves ticket 11464.
10629 o Major features (relay performance):
10630 - Speed up server-side lookups of rendezvous and introduction point
10631 circuits by using hashtables instead of linear searches. These
10632 functions previously accounted between 3 and 7% of CPU usage on
10633 some busy relays. Resolves ticket 9841.
10634 - Avoid wasting CPU when extending a circuit over a channel that is
10635 nearly out of circuit IDs. Previously, we would do a linear scan
10636 over possible circuit IDs before finding one or deciding that we
10637 had exhausted our possibilities. Now, we try at most 64 random
10638 circuit IDs before deciding that we probably won't succeed. Fixes
10639 a possible root cause of ticket 11553.
10641 o Major features (seccomp2 sandbox, Linux only):
10642 - The seccomp2 sandbox can now run a test network for multiple hours
10643 without crashing. The sandbox is still experimental, and more bugs
10644 will probably turn up. To try it, enable "Sandbox 1" on a Linux
10645 host. Resolves ticket 11351.
10646 - Strengthen sandbox code: the sandbox can now test the arguments
10647 for rename(), and blocks _sysctl() entirely. Resolves another part
10649 - When the sandbox blocks a system call, it now tries to log a stack
10650 trace before exiting. Resolves ticket 11465.
10652 o Major bugfixes (TLS cipher selection):
10653 - The relay ciphersuite list is now generated automatically based on
10654 uniform criteria, and includes all OpenSSL ciphersuites with
10655 acceptable strength and forward secrecy. Previously, we had left
10656 some perfectly fine ciphersuites unsupported due to omission or
10657 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
10658 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
10659 - Relays now trust themselves to have a better view than clients of
10660 which TLS ciphersuites are better than others. (Thanks to bug
10661 11513, the relay list is now well-considered, whereas the client
10662 list has been chosen mainly for anti-fingerprinting purposes.)
10663 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
10664 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
10665 AES128. Resolves ticket 11528.
10666 - Clients now try to advertise the same list of ciphersuites as
10667 Firefox 28. This change enables selection of (fast) GCM
10668 ciphersuites, disables some strange old ciphers, and stops
10669 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
10670 Resolves ticket 11438.
10672 o Major bugfixes (bridge client):
10673 - Avoid 60-second delays in the bootstrapping process when Tor is
10674 launching for a second time while using bridges. Fixes bug 9229;
10675 bugfix on 0.2.0.3-alpha.
10677 o Minor features (transparent proxy, *BSD):
10678 - Support FreeBSD's ipfw firewall interface for TransPort ports on
10679 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
10680 10267; patch from "yurivict".
10681 - Support OpenBSD's divert-to rules with the pf firewall for
10682 transparent proxy ports. To enable it, set "TransProxyType
10683 pf-divert". This allows Tor to run a TransPort transparent proxy
10684 port on OpenBSD 4.4 or later without root privileges. See the
10685 pf.conf(5) manual page for information on configuring pf to use
10686 divert-to rules. Closes ticket 10896; patch from Dana Koch.
10688 o Minor features (security):
10689 - New --enable-expensive-hardening option to enable security
10690 hardening options that consume nontrivial amounts of CPU and
10691 memory. Right now, this includes AddressSanitizer and UbSan, which
10692 are supported in newer versions of GCC and Clang. Closes ticket
10695 o Minor features (log verbosity):
10696 - Demote the message that we give when a flushing connection times
10697 out for too long from NOTICE to INFO. It was usually meaningless.
10698 Resolves ticket 5286.
10699 - Don't log so many notice-level bootstrapping messages at startup
10700 about downloading descriptors. Previously, we'd log a notice
10701 whenever we learned about more routers. Now, we only log a notice
10702 at every 5% of progress. Fixes bug 9963.
10703 - Warn less verbosely when receiving a malformed
10704 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
10705 - When we run out of usable circuit IDs on a channel, log only one
10706 warning for the whole channel, and describe how many circuits
10707 there were on the channel. Fixes part of ticket 11553.
10709 o Minor features (relay):
10710 - If a circuit timed out for at least 3 minutes, check if we have a
10711 new external IP address, and publish a new descriptor with the new
10712 IP address if it changed. Resolves ticket 2454.
10714 o Minor features (controller):
10715 - Make the entire exit policy available from the control port via
10716 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
10718 - Because of the fix for ticket 11396, the real limit for memory
10719 usage may no longer match the configured MaxMemInQueues value. The
10720 real limit is now exposed via GETINFO limits/max-mem-in-queues.
10722 o Minor features (bridge client):
10723 - Report a more useful failure message when we can't connect to a
10724 bridge because we don't have the right pluggable transport
10725 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
10727 o Minor features (diagnostic):
10728 - Add more log messages to diagnose bug 7164, which causes
10729 intermittent "microdesc_free() called but md was still referenced"
10730 warnings. We now include more information, to figure out why we
10731 might be cleaning a microdescriptor for being too old if it's
10732 still referenced by a live node_t object.
10734 o Minor bugfixes (client, DNSPort):
10735 - When using DNSPort, try to respond to AAAA requests with AAAA
10736 answers. Previously, we hadn't looked at the request type when
10737 deciding which answer type to prefer. Fixes bug 10468; bugfix on
10739 - When receiving a DNS query for an unsupported record type, reply
10740 with no answer rather than with a NOTIMPL error. This behavior
10741 isn't correct either, but it will break fewer client programs, we
10742 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
10745 o Minor bugfixes (exit relay):
10746 - Stop leaking memory when we successfully resolve a PTR record.
10747 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
10749 o Minor bugfixes (bridge client):
10750 - Stop accepting bridge lines containing hostnames. Doing so would
10751 cause clients to perform DNS requests on the hostnames, which was
10752 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
10753 - Avoid a 60-second delay in the bootstrapping process when a Tor
10754 client with pluggable transports re-reads its configuration at
10755 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
10757 o Minor bugfixes (client, logging during bootstrap):
10758 - Warn only once if we start logging in an unsafe way. Previously,
10759 we complain as many times as we had problems. Fixes bug 9870;
10760 bugfix on 0.2.5.1-alpha.
10761 - Only report the first fatal bootstrap error on a given OR
10762 connection. This stops us from telling the controller bogus error
10763 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
10764 - Be more helpful when trying to run sandboxed on Linux without
10765 libseccomp. Instead of saying "Sandbox is not implemented on this
10766 platform", we now explain that we need to be built with
10767 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
10768 - Avoid generating spurious warnings when starting with
10769 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
10772 o Minor bugfixes (closing OR connections):
10773 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
10774 check if it's an or_connection_t and correctly call
10775 connection_or_close_for_error() rather than
10776 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
10778 - When closing all connections on setting DisableNetwork to 1, use
10779 connection_or_close_normally() rather than closing OR connections
10780 out from under the channel layer. Fixes bug 11306; bugfix on
10783 o Minor bugfixes (controller):
10784 - Avoid sending a garbage value to the controller when a circuit is
10785 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
10787 o Minor bugfixes (tor-fw-helper):
10788 - Allow tor-fw-helper to build again by adding src/ext to its
10789 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
10791 o Minor bugfixes (bridges):
10792 - Avoid potential crashes or bad behavior when launching a
10793 server-side managed proxy with ORPort or ExtORPort temporarily
10794 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
10796 o Minor bugfixes (platform-specific):
10797 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
10798 bug 11426; bugfix on 0.2.5.3-alpha.
10799 - When dumping a malformed directory object to disk, save it in
10800 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
10802 - Don't report failures from make_socket_reuseable() on incoming
10803 sockets on OSX: this can happen when incoming connections close
10804 early. Fixes bug 10081.
10806 o Minor bugfixes (trivial memory leaks):
10807 - Fix a small memory leak when signing a directory object. Fixes bug
10808 11275; bugfix on 0.2.4.13-alpha.
10809 - Free placeholder entries in our circuit table at exit; fixes a
10810 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
10811 - Don't re-initialize a second set of OpenSSL mutexes when starting
10812 up. Previously, we'd make one set of mutexes, and then immediately
10813 replace them with another. Fixes bug 11726; bugfix on
10815 - Resolve some memory leaks found by coverity in the unit tests, on
10816 exit in tor-gencert, and on a failure to compute digests for our
10817 own keys when generating a v3 networkstatus vote. These leaks
10818 should never have affected anyone in practice.
10820 o Minor bugfixes (hidden service):
10821 - Only retry attempts to connect to a chosen rendezvous point 8
10822 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
10824 o Minor bugfixes (misc code correctness):
10825 - Fix various instances of undefined behavior in channeltls.c,
10826 tor_memmem(), and eventdns.c that would cause us to construct
10827 pointers to memory outside an allocated object. (These invalid
10828 pointers were not accessed, but C does not even allow them to
10829 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
10830 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
10831 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
10832 fix some miscellaneous errors in our tests and codebase. Fixes bug
10833 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
10834 - Always check return values for unlink, munmap, UnmapViewOfFile;
10835 check strftime return values more often. In some cases all we can
10836 do is report a warning, but this may help prevent deeper bugs from
10837 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
10839 - Fix numerous warnings from the clang "scan-build" static analyzer.
10840 Some of these are programming style issues; some of them are false
10841 positives that indicated awkward code; some are undefined behavior
10842 cases related to constructing (but not using) invalid pointers;
10843 some are assumptions about API behavior; some are (harmlessly)
10844 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
10845 correct; and one or two are genuine bugs that weren't reachable
10846 from the rest of the program. Fixes bug 8793; bugfixes on many,
10850 - Build the torify.1 manpage again. Previously, we were only trying
10851 to build it when also building tor-fw-helper. That's why we didn't
10852 notice that we'd broken the ability to build it. Fixes bug 11321;
10853 bugfix on 0.2.5.1-alpha.
10854 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
10855 11061; bugfix on 0.2.4.7-alpha.
10856 - Correctly document that we search for a system torrc file before
10857 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
10859 - Resolve warnings from Doxygen.
10861 o Code simplifications and refactoring:
10862 - Remove is_internal_IP() function. Resolves ticket 4645.
10863 - Remove unused function circuit_dump_by_chan from circuitlist.c.
10864 Closes issue 9107; patch from "marek".
10865 - Change our use of the ENUM_BF macro to avoid declarations that
10868 o Deprecated versions:
10869 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
10870 attention for some while. Directory authorities no longer accept
10871 descriptors from relays running any version of Tor prior to Tor
10872 0.2.3.16-alpha. Resolves ticket 11149.
10875 - New macros in test.h to simplify writing mock-functions for unit
10876 tests. Part of ticket 11507. Patch from Dana Koch.
10877 - Complete tests for the status.c module. Resolves ticket 11507.
10878 Patch from Dana Koch.
10881 - Remove all code for the long unused v1 directory protocol.
10882 Resolves ticket 11070.
10885 Changes in version 0.2.5.3-alpha - 2014-03-22
10886 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
10887 two new anti-DoS features for Tor relays, resolves a bug that kept
10888 SOCKS5 support for IPv6 from working, fixes several annoying usability
10889 issues for bridge users, and removes more old code for unused
10892 The Tor 0.2.5.x release series is now in patch-freeze: no feature
10893 patches not already written will be considered for inclusion in 0.2.5.x.
10895 o Major features (relay security, DoS-resistance):
10896 - When deciding whether we have run out of memory and we need to
10897 close circuits, also consider memory allocated in buffers for
10898 streams attached to each circuit.
10900 This change, which extends an anti-DoS feature introduced in
10901 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
10902 better resist more memory-based DoS attacks than before. Since the
10903 MaxMemInCellQueues option now applies to all queues, it is renamed
10904 to MaxMemInQueues. This feature fixes bug 10169.
10905 - Avoid hash-flooding denial-of-service attacks by using the secure
10906 SipHash-2-4 hash function for our hashtables. Without this
10907 feature, an attacker could degrade performance of a targeted
10908 client or server by flooding their data structures with a large
10909 number of entries to be stored at the same hash table position,
10910 thereby slowing down the Tor instance. With this feature, hash
10911 table positions are derived from a randomized cryptographic key,
10912 and an attacker cannot predict which entries will collide. Closes
10914 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
10915 the default at 8GBytes), to better support Raspberry Pi users. Fixes
10916 bug 9686; bugfix on 0.2.4.14-alpha.
10918 o Minor features (bridges, pluggable transports):
10919 - Bridges now write the SHA1 digest of their identity key
10920 fingerprint (that is, a hash of a hash of their public key) to
10921 notice-level logs, and to a new hashed-fingerprint file. This
10922 information will help bridge operators look up their bridge in
10923 Globe and similar tools. Resolves ticket 10884.
10924 - Improve the message that Tor displays when running as a bridge
10925 using pluggable transports without an Extended ORPort listener.
10926 Also, log the message in the log file too. Resolves ticket 11043.
10928 o Minor features (other):
10929 - Add a new option, PredictedPortsRelevanceTime, to control how long
10930 after having received a request to connect to a given port Tor
10931 will try to keep circuits ready in anticipation of future requests
10932 for that port. Patch from "unixninja92"; implements ticket 9176.
10933 - Generate a warning if any ports are listed in the SocksPolicy,
10934 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
10935 AuthDirBadExit options. (These options only support address
10936 ranges.) Fixes part of ticket 11108.
10937 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
10940 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
10941 - Build without warnings under clang 3.4. (We have some macros that
10942 define static functions only some of which will get used later in
10943 the module. Starting with clang 3.4, these give a warning unless the
10944 unused attribute is set on them.) Resolves ticket 10904.
10945 - Fix build warnings about missing "a2x" comment when building the
10946 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10947 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10949 o Minor bugfixes (client):
10950 - Improve the log message when we can't connect to a hidden service
10951 because all of the hidden service directory nodes hosting its
10952 descriptor are excluded. Improves on our fix for bug 10722, which
10953 was a bugfix on 0.2.0.10-alpha.
10954 - Raise a control port warning when we fail to connect to all of
10955 our bridges. Previously, we didn't inform the controller, and
10956 the bootstrap process would stall. Fixes bug 11069; bugfix on
10958 - Exit immediately when a process-owning controller exits.
10959 Previously, tor relays would wait for a little while after their
10960 controller exited, as if they had gotten an INT signal -- but this
10961 was problematic, since there was no feedback for the user. To do a
10962 clean shutdown, controllers should send an INT signal and give Tor
10963 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
10964 - Stop attempting to connect to bridges before our pluggable
10965 transports are configured (harmless but resulted in some erroneous
10966 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
10967 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
10968 generating incorrect SOCKS5 responses, and confusing client
10969 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
10971 o Minor bugfixes (relays and bridges):
10972 - Avoid crashing on a malformed resolv.conf file when running a
10973 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
10974 - Non-exit relays no longer launch mock DNS requests to check for
10975 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
10976 non-exit relays stopped servicing DNS requests. Fixes bug 965;
10977 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
10978 - Bridges now report complete directory request statistics. Related
10979 to bug 5824; bugfix on 0.2.2.1-alpha.
10980 - Bridges now never collect statistics that were designed for
10981 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
10982 - Stop giving annoying warning messages when we decide not to launch
10983 a pluggable transport proxy that we don't need (because there are
10984 no bridges configured to use it). Resolves ticket 5018; bugfix
10986 - Give the correct URL in the warning message when trying to run a
10987 relay on an ancient version of Windows. Fixes bug 9393.
10989 o Minor bugfixes (backtrace support):
10990 - Support automatic backtraces on more platforms by using the
10991 "-fasynchronous-unwind-tables" compiler option. This option is
10992 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
10993 is on by default and table generation is not. This doesn't yet
10994 add Windows support; only Linux, OSX, and some BSDs are affected.
10995 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
10996 - Avoid strange behavior if two threads hit failed assertions at the
10997 same time and both try to log backtraces at once. (Previously, if
10998 this had happened, both threads would have stored their intermediate
10999 results in the same buffer, and generated junk outputs.) Reported by
11000 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
11001 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
11002 0.2.5.2-alpha; patch from Nick Hopper.
11004 o Minor bugfixes (unit tests):
11005 - Fix a small bug in the unit tests that might have made the tests
11006 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
11007 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
11010 - Remove all remaining code related to version-0 hidden service
11011 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
11012 the rest of bug 10841.
11015 - Document in the manpage that "KBytes" may also be written as
11016 "kilobytes" or "KB", that "Kbits" may also be written as
11017 "kilobits", and so forth. Closes ticket 9222.
11018 - Document that the ClientOnly config option overrides ORPort.
11019 Our old explanation made ClientOnly sound as though it did
11020 nothing at all. Resolves bug 9059.
11021 - Explain that SocksPolicy, DirPolicy, and similar options don't
11022 take port arguments. Fixes the other part of ticket 11108.
11023 - Fix a comment about the rend_server_descriptor_t.protocols field
11024 to more accurately describe its range. Also, make that field
11025 unsigned, to more accurately reflect its usage. Fixes bug 9099;
11026 bugfix on 0.2.1.5-alpha.
11027 - Fix the manpage's description of HiddenServiceAuthorizeClient:
11028 the maximum client name length is 16, not 19. Fixes bug 11118;
11029 bugfix on 0.2.1.6-alpha.
11031 o Code simplifications and refactoring:
11032 - Get rid of router->address, since in all cases it was just the
11033 string representation of router->addr. Resolves ticket 5528.
11035 o Test infrastructure:
11036 - Update to the latest version of tinytest.
11037 - Improve the tinytest implementation of string operation tests so
11038 that comparisons with NULL strings no longer crash the tests; they
11039 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
11042 Changes in version 0.2.4.21 - 2014-02-28
11043 Tor 0.2.4.21 further improves security against potential adversaries who
11044 find breaking 1024-bit crypto doable, and backports several stability
11045 and robustness patches from the 0.2.5 branch.
11047 o Major features (client security):
11048 - When we choose a path for a 3-hop circuit, make sure it contains
11049 at least one relay that supports the NTor circuit extension
11050 handshake. Otherwise, there is a chance that we're building
11051 a circuit that's worth attacking by an adversary who finds
11052 breaking 1024-bit crypto doable, and that chance changes the game
11053 theory. Implements ticket 9777.
11056 - Do not treat streams that fail with reason
11057 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
11058 since it could also indicate an ENETUNREACH connection error. Fixes
11059 part of bug 10777; bugfix on 0.2.4.8-alpha.
11061 o Code simplification and refactoring:
11062 - Remove data structures which were introduced to implement the
11063 CellStatistics option: they are now redundant with the new timestamp
11064 field in the regular packed_cell_t data structure, which we did
11065 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
11068 - Always clear OpenSSL bignums before freeing them -- even bignums
11069 that don't contain secrets. Resolves ticket 10793. Patch by
11071 - Build without warnings under clang 3.4. (We have some macros that
11072 define static functions only some of which will get used later in
11073 the module. Starting with clang 3.4, these give a warning unless the
11074 unused attribute is set on them.) Resolves ticket 10904.
11075 - Update geoip and geoip6 files to the February 7 2014 Maxmind
11076 GeoLite2 Country database.
11079 - Set the listen() backlog limit to the largest actually supported
11080 on the system, not to the value in a header file. Fixes bug 9716;
11081 bugfix on every released Tor.
11082 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
11083 exit node as a NOROUTE error, not an INTERNAL error, since they
11084 can apparently happen when trying to connect to the wrong sort
11085 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
11086 - Fix build warnings about missing "a2x" comment when building the
11087 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
11088 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
11089 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
11090 not entirely remove it from the connection lists. Fixes bug 9602;
11091 bugfix on 0.2.4.4-alpha.
11092 - Fix a segmentation fault in our benchmark code when running with
11093 Fedora's OpenSSL package, or any other OpenSSL that provides
11094 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
11095 - Turn "circuit handshake stats since last time" log messages into a
11096 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
11098 o Documentation fixes:
11099 - Document that all but one DirPort entry must have the NoAdvertise
11100 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
11103 Changes in version 0.2.5.2-alpha - 2014-02-13
11104 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
11105 like the "poor random number generation" fix and the "building too many
11106 circuits" fix. It also further improves security against potential
11107 adversaries who find breaking 1024-bit crypto doable, and launches
11108 pluggable transports on demand (which gets us closer to integrating
11109 pluggable transport support by default -- not to be confused with Tor
11110 bundles enabling pluggable transports and bridges by default).
11112 o Major features (client security):
11113 - When we choose a path for a 3-hop circuit, make sure it contains
11114 at least one relay that supports the NTor circuit extension
11115 handshake. Otherwise, there is a chance that we're building
11116 a circuit that's worth attacking by an adversary who finds
11117 breaking 1024-bit crypto doable, and that chance changes the game
11118 theory. Implements ticket 9777.
11119 - Clients now look at the "usecreatefast" consensus parameter to
11120 decide whether to use CREATE_FAST or CREATE cells for the first hop
11121 of their circuit. This approach can improve security on connections
11122 where Tor's circuit handshake is stronger than the available TLS
11123 connection security levels, but the tradeoff is more computational
11124 load on guard relays. Implements proposal 221. Resolves ticket 9386.
11126 o Major features (bridges):
11127 - Don't launch pluggable transport proxies if we don't have any
11128 bridges configured that would use them. Now we can list many
11129 pluggable transports, and Tor will dynamically start one when it
11130 hears a bridge address that needs it. Resolves ticket 5018.
11131 - The bridge directory authority now assigns status flags (Stable,
11132 Guard, etc) to bridges based on thresholds calculated over all
11133 Running bridges. Now bridgedb can finally make use of its features
11134 to e.g. include at least one Stable bridge in its answers. Fixes
11137 o Major features (other):
11138 - Extend ORCONN controller event to include an "ID" parameter,
11139 and add four new controller event types CONN_BW, CIRC_BW,
11140 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
11141 The new events are emitted in private Tor networks only, with the
11142 goal of being able to better track performance and load during
11143 full-network simulations. Implements proposal 218 and ticket 7359.
11144 - On some platforms (currently: recent OSX versions, glibc-based
11145 platforms that support the ELF format, and a few other
11146 Unix-like operating systems), Tor can now dump stack traces
11147 when a crash occurs or an assertion fails. By default, traces
11148 are dumped to stderr (if possible) and to any logs that are
11149 reporting errors. Implements ticket 9299.
11152 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
11153 not entirely remove it from the connection lists. Fixes bug 9602;
11154 bugfix on 0.2.4.4-alpha.
11155 - Do not treat streams that fail with reason
11156 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
11157 since it could also indicate an ENETUNREACH connection error. Fixes
11158 part of bug 10777; bugfix on 0.2.4.8-alpha.
11160 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
11161 - Do not allow OpenSSL engines to replace the PRNG, even when
11162 HardwareAccel is set. The only default builtin PRNG engine uses
11163 the Intel RDRAND instruction to replace the entire PRNG, and
11164 ignores all attempts to seed it with more entropy. That's
11165 cryptographically stupid: the right response to a new alleged
11166 entropy source is never to discard all previously used entropy
11167 sources. Fixes bug 10402; works around behavior introduced in
11168 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
11170 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
11171 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
11172 - Avoid launching spurious extra circuits when a stream is pending.
11173 This fixes a bug where any circuit that _wasn't_ unusable for new
11174 streams would be treated as if it were, causing extra circuits to
11175 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
11177 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11178 - No longer stop reading or writing on cpuworker connections when
11179 our rate limiting buckets go empty. Now we should handle circuit
11180 handshake requests more promptly. Resolves bug 9731.
11181 - Stop trying to bootstrap all our directory information from
11182 only our first guard. Discovered while fixing bug 9946; bugfix
11185 o Minor features (bridges, pluggable transports):
11186 - Add threshold cutoffs to the networkstatus document created by
11187 the Bridge Authority. Fixes bug 1117.
11188 - On Windows, spawn background processes using the CREATE_NO_WINDOW
11189 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
11190 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
11191 Vidalia set this option for us.) Implements ticket 10297.
11193 o Minor features (security):
11194 - Always clear OpenSSL bignums before freeing them -- even bignums
11195 that don't contain secrets. Resolves ticket 10793. Patch by
11196 Florent Daignière.
11198 o Minor features (config options and command line):
11199 - Add an --allow-missing-torrc commandline option that tells Tor to
11200 run even if the configuration file specified by -f is not available.
11201 Implements ticket 10060.
11202 - Add support for the TPROXY transparent proxying facility on Linux.
11203 See documentation for the new TransProxyType option for more
11204 details. Implementation by "thomo". Closes ticket 10582.
11206 o Minor features (controller):
11207 - Add a new "HS_DESC" controller event that reports activities
11208 related to hidden service descriptors. Resolves ticket 8510.
11209 - New "DROPGUARDS" controller command to forget all current entry
11210 guards. Not recommended for ordinary use, since replacing guards
11211 too frequently makes several attacks easier. Resolves ticket 9934;
11214 o Minor features (build):
11215 - Assume that a user using ./configure --host wants to cross-compile,
11216 and give an error if we cannot find a properly named
11217 tool-chain. Add a --disable-tool-name-check option to proceed
11218 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
11219 - If we run ./configure and the compiler recognizes -fstack-protector
11220 but the linker rejects it, warn the user about a potentially missing
11221 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
11223 o Minor features (testing):
11224 - If Python is installed, "make check" now runs extra tests beyond
11225 the unit test scripts.
11226 - When bootstrapping a test network, sometimes very few relays get
11227 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
11228 specify a set of relays which should be voted Guard regardless of
11229 their uptime or bandwidth. Addresses ticket 9206.
11231 o Minor features (log messages):
11232 - When ServerTransportPlugin is set on a bridge, Tor can write more
11233 useful statistics about bridge use in its extrainfo descriptors,
11234 but only if the Extended ORPort ("ExtORPort") is set too. Add a
11235 log message to inform the user in this case. Resolves ticket 9651.
11236 - When receiving a new controller connection, log the origin address.
11237 Resolves ticket 9698; patch from "sigpipe".
11238 - When logging OpenSSL engine status at startup, log the status of
11239 more engines. Fixes ticket 10043; patch from Joshua Datko.
11240 - Turn "circuit handshake stats since last time" log messages into a
11241 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
11243 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11244 - Improve the circuit queue out-of-memory handler. Previously, when
11245 we ran low on memory, we'd close whichever circuits had the most
11246 queued cells. Now, we close those that have the *oldest* queued
11247 cells, on the theory that those are most responsible for us
11248 running low on memory. Based on analysis from a forthcoming paper
11249 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
11250 - Generate bootstrapping status update events correctly when fetching
11251 microdescriptors. Fixes bug 9927.
11252 - Update to the October 2 2013 Maxmind GeoLite Country database.
11254 o Minor bugfixes (clients):
11255 - When closing a channel that has already been open, do not close
11256 pending circuits that were waiting to connect to the same relay.
11257 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
11260 o Minor bugfixes (relays):
11261 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
11262 exit node as a NOROUTE error, not an INTERNAL error, since they
11263 can apparently happen when trying to connect to the wrong sort
11264 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
11266 o Minor bugfixes (bridges):
11267 - Fix a bug where the first connection works to a bridge that uses a
11268 pluggable transport with client-side parameters, but we don't send
11269 the client-side parameters on subsequent connections. (We don't
11270 use any pluggable transports with client-side parameters yet,
11271 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
11272 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
11274 o Minor bugfixes (node selection):
11275 - If ExcludeNodes is set, consider non-excluded hidden service
11276 directory servers before excluded ones. Do not consider excluded
11277 hidden service directory servers at all if StrictNodes is
11278 set. (Previously, we would sometimes decide to connect to those
11279 servers, and then realize before we initiated a connection that
11280 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
11281 Reported by "mr-4".
11282 - If we set the ExitNodes option but it doesn't include any nodes
11283 that have the Exit flag, we would choose not to bootstrap. Now we
11284 bootstrap so long as ExitNodes includes nodes which can exit to
11285 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
11287 o Minor bugfixes (controller and command-line):
11288 - If changing a config option via "setconf" fails in a recoverable
11289 way, we used to nonetheless write our new control ports to the
11290 file described by the "ControlPortWriteToFile" option. Now we only
11291 write out that file if we successfully switch to the new config
11292 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
11293 - When a command-line option such as --version or --help that
11294 ordinarily implies --hush appears on the command line along with
11295 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
11296 only if it appeared later on the command line. Fixes bug 9578;
11297 bugfix on 0.2.5.1-alpha.
11299 o Minor bugfixes (code correctness):
11300 - Previously we used two temporary files when writing descriptors to
11301 disk; now we only use one. Fixes bug 1376.
11302 - Remove an erroneous (but impossible and thus harmless) pointer
11303 comparison that would have allowed compilers to skip a bounds
11304 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
11305 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
11306 - Fix an always-true assertion in pluggable transports code so it
11307 actually checks what it was trying to check. Fixes bug 10046;
11308 bugfix on 0.2.3.9-alpha. Found by "dcb".
11310 o Minor bugfixes (protocol correctness):
11311 - When receiving a VERSIONS cell with an odd number of bytes, close
11312 the connection immediately since the cell is malformed. Fixes bug
11313 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
11316 o Minor bugfixes (build):
11317 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
11318 turned off (that is, without support for v2 link handshakes). Fixes
11319 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
11320 - Fix compilation warnings and startup issues when running with
11321 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
11323 - Fix compilation on Solaris 9, which didn't like us having an
11324 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
11326 o Minor bugfixes (testing):
11327 - Fix a segmentation fault in our benchmark code when running with
11328 Fedora's OpenSSL package, or any other OpenSSL that provides
11329 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
11331 o Minor bugfixes (log messages):
11332 - Fix a bug where clients using bridges would report themselves
11333 as 50% bootstrapped even without a live consensus document.
11334 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
11335 - Suppress a warning where, if there's only one directory authority
11336 in the network, we would complain that votes and signatures cannot
11337 be uploaded to other directory authorities. Fixes bug 10842;
11338 bugfix on 0.2.2.26-beta.
11339 - Report bootstrapping progress correctly when we're downloading
11340 microdescriptors. We had updated our "do we have enough microdescs
11341 to begin building circuits?" logic most recently in 0.2.4.10-alpha
11342 (see bug 5956), but we left the bootstrap status event logic at
11343 "how far through getting 1/4 of them are we?" Fixes bug 9958;
11344 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
11346 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
11347 - Avoid a crash bug when starting with a corrupted microdescriptor
11348 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
11349 - If we fail to dump a previously cached microdescriptor to disk, avoid
11350 freeing duplicate data later on. Fixes bug 10423; bugfix on
11351 0.2.4.13-alpha. Spotted by "bobnomnom".
11353 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11354 - Correctly log long IPv6 exit policies, instead of truncating them
11355 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
11356 - Our default TLS ecdhe groups were backwards: we meant to be using
11357 P224 for relays (for performance win) and P256 for bridges (since
11358 it is more common in the wild). Instead we had it backwards. After
11359 reconsideration, we decided that the default should be P256 on all
11360 hosts, since its security is probably better, and since P224 is
11361 reportedly used quite little in the wild. Found by "skruffy" on
11362 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
11363 - Free directory authority certificate download statuses on exit
11364 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
11366 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11367 - If the guard we choose first doesn't answer, we would try the
11368 second guard, but once we connected to the second guard we would
11369 abandon it and retry the first one, slowing down bootstrapping.
11370 The fix is to treat all our initially chosen guards as acceptable
11371 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
11372 - Fix an assertion failure that would occur when disabling the
11373 ORPort setting on a running Tor process while accounting was
11374 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
11375 - When examining the list of network interfaces to find our address,
11376 do not consider non-running or disabled network interfaces. Fixes
11377 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
11378 - Avoid an off-by-one error when checking buffer boundaries when
11379 formatting the exit status of a pluggable transport helper.
11380 This is probably not an exploitable bug, but better safe than
11381 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
11384 o Removed code and features:
11385 - Clients now reject any directory authority certificates lacking
11386 a dir-key-crosscert element. These have been included since
11387 0.2.1.9-alpha, so there's no real reason for them to be optional
11388 any longer. Completes proposal 157. Resolves ticket 10162.
11389 - Remove all code that existed to support the v2 directory system,
11390 since there are no longer any v2 directory authorities. Resolves
11392 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
11393 options, which were used for designating authorities as "Hidden
11394 service authorities". There has been no use of hidden service
11395 authorities since 0.2.2.1-alpha, when we stopped uploading or
11396 downloading v0 hidden service descriptors. Fixes bug 10881; also
11397 part of a fix for bug 10841.
11399 o Code simplification and refactoring:
11400 - Remove some old fallback code designed to keep Tor clients working
11401 in a network with only two working relays. Elsewhere in the code we
11402 have long since stopped supporting such networks, so there wasn't
11403 much point in keeping it around. Addresses ticket 9926.
11404 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
11405 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
11406 - Remove data structures which were introduced to implement the
11407 CellStatistics option: they are now redundant with the addition
11408 of a timestamp to the regular packed_cell_t data structure, which
11409 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
11412 o Documentation (man page) fixes:
11413 - Update manpage to describe some of the files you can expect to
11414 find in Tor's DataDirectory. Addresses ticket 9839.
11415 - Document that all but one DirPort entry must have the NoAdvertise
11416 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
11418 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
11419 - Clarify the usage and risks of setting the ContactInfo torrc line
11420 for your relay or bridge. Resolves ticket 9854.
11421 - Add anchors to the manpage so we can link to the html version of
11422 the documentation for specific options. Resolves ticket 9866.
11423 - Replace remaining references to DirServer in man page and
11424 log entries. Resolves ticket 10124.
11427 - Make the "tor-gencert" tool used by directory authority operators
11428 create 2048-bit signing keys by default (rather than 1024-bit, since
11429 1024-bit is uncomfortably small these days). Addresses ticket 10324.
11432 Changes in version 0.2.4.20 - 2013-12-22
11433 Tor 0.2.4.20 fixes potentially poor random number generation for users
11434 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
11435 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
11436 and 4) have no state file in their DataDirectory (as would happen on
11437 first start). Users who generated relay or hidden service identity
11438 keys in such a situation should discard them and generate new ones.
11440 This release also fixes a logic error that caused Tor clients to build
11441 many more preemptive circuits than they actually need.
11444 - Do not allow OpenSSL engines to replace the PRNG, even when
11445 HardwareAccel is set. The only default builtin PRNG engine uses
11446 the Intel RDRAND instruction to replace the entire PRNG, and
11447 ignores all attempts to seed it with more entropy. That's
11448 cryptographically stupid: the right response to a new alleged
11449 entropy source is never to discard all previously used entropy
11450 sources. Fixes bug 10402; works around behavior introduced in
11451 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
11453 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
11454 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
11455 - Avoid launching spurious extra circuits when a stream is pending.
11456 This fixes a bug where any circuit that _wasn't_ unusable for new
11457 streams would be treated as if it were, causing extra circuits to
11458 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
11461 - Avoid a crash bug when starting with a corrupted microdescriptor
11462 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
11463 - If we fail to dump a previously cached microdescriptor to disk, avoid
11464 freeing duplicate data later on. Fixes bug 10423; bugfix on
11465 0.2.4.13-alpha. Spotted by "bobnomnom".
11468 Changes in version 0.2.4.19 - 2013-12-11
11469 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
11470 (1986-2013). Aaron worked on diverse projects including helping to guide
11471 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
11472 transparency to the U.S government's PACER documents, and contributing
11473 design and development for Tor and Tor2Web. Aaron was one of the latest
11474 martyrs in our collective fight for civil liberties and human rights,
11475 and his death is all the more painful because he was one of us.
11477 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
11478 a new circuit handshake and link encryption that use ECC to provide
11479 better security and efficiency; makes relays better manage circuit
11480 creation requests; uses "directory guards" to reduce client enumeration
11481 risks; makes bridges collect and report statistics about the pluggable
11482 transports they support; cleans up and improves our geoip database;
11483 gets much closer to IPv6 support for clients, bridges, and relays; makes
11484 directory authorities use measured bandwidths rather than advertised
11485 ones when computing flags and thresholds; disables client-side DNS
11486 caching to reduce tracking risks; and fixes a big bug in bridge
11487 reachability testing. This release introduces two new design
11488 abstractions in the code: a new "channel" abstraction between circuits
11489 and or_connections to allow for implementing alternate relay-to-relay
11490 transports, and a new "circuitmux" abstraction storing the queue of
11491 circuits for a channel. The release also includes many stability,
11492 security, and privacy fixes.
11495 Changes in version 0.2.4.18-rc - 2013-11-16
11496 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
11497 series. It takes a variety of fixes from the 0.2.5.x branch to improve
11498 stability, performance, and better handling of edge cases.
11501 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
11502 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
11503 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
11504 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
11505 them to solve bug 6033.)
11508 - No longer stop reading or writing on cpuworker connections when
11509 our rate limiting buckets go empty. Now we should handle circuit
11510 handshake requests more promptly. Resolves bug 9731.
11511 - If we are unable to save a microdescriptor to the journal, do not
11512 drop it from memory and then reattempt downloading it. Fixes bug
11513 9645; bugfix on 0.2.2.6-alpha.
11514 - Stop trying to bootstrap all our directory information from
11515 only our first guard. Discovered while fixing bug 9946; bugfix
11517 - The new channel code sometimes lost track of in-progress circuits,
11518 causing long-running clients to stop building new circuits. The
11519 fix is to always call circuit_n_chan_done(chan, 0) from
11520 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
11522 o Minor bugfixes (on 0.2.4.x):
11523 - Correctly log long IPv6 exit policies, instead of truncating them
11524 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
11525 - Our default TLS ecdhe groups were backwards: we meant to be using
11526 P224 for relays (for performance win) and P256 for bridges (since
11527 it is more common in the wild). Instead we had it backwards. After
11528 reconsideration, we decided that the default should be P256 on all
11529 hosts, since its security is probably better, and since P224 is
11530 reportedly used quite little in the wild. Found by "skruffy" on
11531 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
11532 - Free directory authority certificate download statuses on exit
11533 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
11535 o Minor bugfixes (on 0.2.3.x and earlier):
11536 - If the guard we choose first doesn't answer, we would try the
11537 second guard, but once we connected to the second guard we would
11538 abandon it and retry the first one, slowing down bootstrapping.
11539 The fix is to treat all our initially chosen guards as acceptable
11540 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
11541 - Fix an assertion failure that would occur when disabling the
11542 ORPort setting on a running Tor process while accounting was
11543 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
11544 - When examining the list of network interfaces to find our address,
11545 do not consider non-running or disabled network interfaces. Fixes
11546 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
11547 - Avoid an off-by-one error when checking buffer boundaries when
11548 formatting the exit status of a pluggable transport helper.
11549 This is probably not an exploitable bug, but better safe than
11550 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
11553 o Minor features (protecting client timestamps):
11554 - Clients no longer send timestamps in their NETINFO cells. These were
11555 not used for anything, and they provided one small way for clients
11556 to be distinguished from each other as they moved from network to
11557 network or behind NAT. Implements part of proposal 222.
11558 - Clients now round timestamps in INTRODUCE cells down to the nearest
11559 10 minutes. If a new Support022HiddenServices option is set to 0, or
11560 if it's set to "auto" and the feature is disabled in the consensus,
11561 the timestamp is sent as 0 instead. Implements part of proposal 222.
11562 - Stop sending timestamps in AUTHENTICATE cells. This is not such
11563 a big deal from a security point of view, but it achieves no actual
11564 good purpose, and isn't needed. Implements part of proposal 222.
11565 - Reduce down accuracy of timestamps in hidden service descriptors.
11566 Implements part of proposal 222.
11568 o Minor features (other):
11569 - Improve the circuit queue out-of-memory handler. Previously, when
11570 we ran low on memory, we'd close whichever circuits had the most
11571 queued cells. Now, we close those that have the *oldest* queued
11572 cells, on the theory that those are most responsible for us
11573 running low on memory. Based on analysis from a forthcoming paper
11574 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
11575 - Generate bootstrapping status update events correctly when fetching
11576 microdescriptors. Fixes bug 9927.
11577 - Update to the October 2 2013 Maxmind GeoLite Country database.
11579 o Documentation fixes:
11580 - Clarify the usage and risks of setting the ContactInfo torrc line
11581 for your relay or bridge. Resolves ticket 9854.
11582 - Add anchors to the manpage so we can link to the html version of
11583 the documentation for specific options. Resolves ticket 9866.
11584 - Replace remaining references to DirServer in man page and
11585 log entries. Resolves ticket 10124.
11588 Changes in version 0.2.5.1-alpha - 2013-10-02
11589 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
11590 on Linux, allows bridges that offer pluggable transports to report usage
11591 statistics, fixes many issues to make testing easier, and provides
11592 a pile of minor features and bugfixes that have been waiting for a
11593 release of the new branch.
11595 This is the first alpha release in a new series, so expect there to
11596 be bugs. Users who would rather test out a more stable branch should
11597 stay with 0.2.4.x for now.
11599 o Major features (security):
11600 - Use the seccomp2 syscall filtering facility on Linux to limit
11601 which system calls Tor can invoke. This is an experimental,
11602 Linux-only feature to provide defense-in-depth against unknown
11603 attacks. To try turning it on, set "Sandbox 1" in your torrc
11604 file. Please be ready to report bugs. We hope to add support
11605 for better sandboxing in the future, including more fine-grained
11606 filters, better division of responsibility, and support for more
11607 platforms. This work has been done by Cristian-Matei Toader for
11608 Google Summer of Code.
11609 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
11610 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
11611 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
11612 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
11613 them to solve bug 6033.)
11615 o Major features (other):
11616 - Add support for passing arguments to managed pluggable transport
11617 proxies. Implements ticket 3594.
11618 - Bridges now track GeoIP information and the number of their users
11619 even when pluggable transports are in use, and report usage
11620 statistics in their extra-info descriptors. Resolves tickets 4773
11622 - Make testing Tor networks bootstrap better: lower directory fetch
11623 retry schedules and maximum interval without directory requests,
11624 and raise maximum download tries. Implements ticket 6752.
11625 - Add make target 'test-network' to run tests on a Chutney network.
11626 Implements ticket 8530.
11627 - The ntor handshake is now on-by-default, no matter what the
11628 directory authorities recommend. Implements ticket 8561.
11631 - Instead of writing destroy cells directly to outgoing connection
11632 buffers, queue them and intersperse them with other outgoing cells.
11633 This can prevent a set of resource starvation conditions where too
11634 many pending destroy cells prevent data cells from actually getting
11635 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
11636 bugfix on 0.2.0.1-alpha.
11637 - If we are unable to save a microdescriptor to the journal, do not
11638 drop it from memory and then reattempt downloading it. Fixes bug
11639 9645; bugfix on 0.2.2.6-alpha.
11640 - The new channel code sometimes lost track of in-progress circuits,
11641 causing long-running clients to stop building new circuits. The
11642 fix is to always call circuit_n_chan_done(chan, 0) from
11643 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
11646 - Tor now builds each source file in two modes: a mode that avoids
11647 exposing identifiers needlessly, and another mode that exposes
11648 more identifiers for testing. This lets the compiler do better at
11649 optimizing the production code, while enabling us to take more
11650 radical measures to let the unit tests test things.
11651 - The production builds no longer include functions used only in
11652 the unit tests; all functions exposed from a module only for
11653 unit-testing are now static in production builds.
11654 - Add an --enable-coverage configuration option to make the unit
11655 tests (and a new src/or/tor-cov target) to build with gcov test
11659 - We now have rudimentary function mocking support that our unit
11660 tests can use to test functions in isolation. Function mocking
11661 lets the tests temporarily replace a function's dependencies with
11662 stub functions, so that the tests can check the function without
11663 invoking the other functions it calls.
11664 - Add more unit tests for the <circid,channel>->circuit map, and
11665 the destroy-cell-tracking code to fix bug 7912.
11666 - Unit tests for failing cases of the TAP onion handshake.
11667 - More unit tests for address-manipulation functions.
11669 o Minor features (protecting client timestamps):
11670 - Clients no longer send timestamps in their NETINFO cells. These were
11671 not used for anything, and they provided one small way for clients
11672 to be distinguished from each other as they moved from network to
11673 network or behind NAT. Implements part of proposal 222.
11674 - Clients now round timestamps in INTRODUCE cells down to the nearest
11675 10 minutes. If a new Support022HiddenServices option is set to 0, or
11676 if it's set to "auto" and the feature is disabled in the consensus,
11677 the timestamp is sent as 0 instead. Implements part of proposal 222.
11678 - Stop sending timestamps in AUTHENTICATE cells. This is not such
11679 a big deal from a security point of view, but it achieves no actual
11680 good purpose, and isn't needed. Implements part of proposal 222.
11681 - Reduce down accuracy of timestamps in hidden service descriptors.
11682 Implements part of proposal 222.
11684 o Minor features (config options):
11685 - Config (torrc) lines now handle fingerprints which are missing
11686 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
11687 - Support a --dump-config option to print some or all of the
11688 configured options. Mainly useful for debugging the command-line
11689 option parsing code. Helps resolve ticket 4647.
11690 - Raise awareness of safer logging: notify user of potentially
11691 unsafe config options, like logging more verbosely than severity
11692 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
11693 - Add a new configuration option TestingV3AuthVotingStartOffset
11694 that bootstraps a network faster by changing the timing for
11695 consensus votes. Addresses ticket 8532.
11696 - Add a new torrc option "ServerTransportOptions" that allows
11697 bridge operators to pass configuration parameters to their
11698 pluggable transports. Resolves ticket 8929.
11699 - The config (torrc) file now accepts bandwidth and space limits in
11700 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
11701 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
11704 o Minor features (build):
11705 - Add support for `--library-versions` flag. Implements ticket 6384.
11706 - Return the "unexpected sendme" warnings to a warn severity, but make
11707 them rate limited, to help diagnose ticket 8093.
11708 - Detect a missing asciidoc, and warn the user about it, during
11709 configure rather than at build time. Fixes issue 6506. Patch from
11712 o Minor features (other):
11713 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
11714 sockets in a single system call. Implements ticket 5129.
11715 - Log current accounting state (bytes sent and received + remaining
11716 time for the current accounting period) in the relay's heartbeat
11717 message. Implements ticket 5526; patch from Peter Retzlaff.
11718 - Implement the TRANSPORT_LAUNCHED control port event that
11719 notifies controllers about new launched pluggable
11720 transports. Resolves ticket 5609.
11721 - If we're using the pure-C 32-bit curve25519_donna implementation
11722 of curve25519, build it with the -fomit-frame-pointer option to
11723 make it go faster on register-starved hosts. This improves our
11724 handshake performance by about 6% on i386 hosts without nacl.
11725 Closes ticket 8109.
11726 - Update to the September 4 2013 Maxmind GeoLite Country database.
11729 - Set the listen() backlog limit to the largest actually supported
11730 on the system, not to the value in a header file. Fixes bug 9716;
11731 bugfix on every released Tor.
11732 - No longer accept malformed http headers when parsing urls from
11733 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
11734 bugfix on 0.0.6pre1.
11735 - In munge_extrainfo_into_routerinfo(), check the return value of
11736 memchr(). This would have been a serious issue if we ever passed
11737 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
11739 - On the chance that somebody manages to build Tor on a
11740 platform where time_t is unsigned, correct the way that
11741 microdesc_add_to_cache() handles negative time arguments.
11742 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
11743 - Reject relative control socket paths and emit a warning. Previously,
11744 single-component control socket paths would be rejected, but Tor
11745 would not log why it could not validate the config. Fixes bug 9258;
11746 bugfix on 0.2.3.16-alpha.
11748 o Minor bugfixes (command line):
11749 - Use a single command-line parser for parsing torrc options on the
11750 command line and for finding special command-line options to avoid
11751 inconsistent behavior for torrc option arguments that have the same
11752 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
11754 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
11755 9573; bugfix on 0.0.9pre5.
11757 o Minor fixes (build, auxiliary programs):
11758 - Stop preprocessing the "torify" script with autoconf, since
11759 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
11761 - The tor-fw-helper program now follows the standard convention and
11762 exits with status code "0" on success. Fixes bug 9030; bugfix on
11763 0.2.3.1-alpha. Patch by Arlo Breault.
11764 - Corrected ./configure advice for what openssl dev package you should
11765 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
11767 o Minor code improvements:
11768 - Remove constants and tests for PKCS1 padding; it's insecure and
11769 shouldn't be used for anything new. Fixes bug 8792; patch
11771 - Remove instances of strcpy() from the unit tests. They weren't
11772 hurting anything, since they were only in the unit tests, but it's
11773 embarrassing to have strcpy() in the code at all, and some analysis
11774 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
11775 0.2.3.8-alpha. Patch from Arlo Breault.
11777 o Removed features:
11778 - Remove migration code from when we renamed the "cached-routers"
11779 file to "cached-descriptors" back in 0.2.0.8-alpha. This
11780 incidentally resolves ticket 6502 by cleaning up the related code
11781 a bit. Patch from Akshay Hebbar.
11783 o Code simplification and refactoring:
11784 - Extract the common duplicated code for creating a subdirectory
11785 of the data directory and writing to a file in it. Fixes ticket
11786 4282; patch from Peter Retzlaff.
11787 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
11788 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
11789 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
11790 - Add a set of accessor functions for the circuit timeout data
11791 structure. Fixes ticket 6153; patch from "piet".
11792 - Clean up exit paths from connection_listener_new(). Closes ticket
11793 8789. Patch from Arlo Breault.
11794 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
11795 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
11796 - Use a doubly-linked list to implement the global circuit list.
11797 Resolves ticket 9108. Patch from Marek Majkowski.
11798 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
11801 Changes in version 0.2.4.17-rc - 2013-09-05
11802 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
11803 series. It adds an emergency step to help us tolerate the massive
11804 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
11805 circuit-level handshakes now effectively jump the queue compared to
11806 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
11807 big bug hindering bridge reachability tests.
11810 - Relays now process the new "NTor" circuit-level handshake requests
11811 with higher priority than the old "TAP" circuit-level handshake
11812 requests. We still process some TAP requests to not totally starve
11813 0.2.3 clients when NTor becomes popular. A new consensus parameter
11814 "NumNTorsPerTAP" lets us tune the balance later if we need to.
11815 Implements ticket 9574.
11818 - If the circuit build timeout logic is disabled (via the consensus,
11819 or because we are an authority), then don't build testing circuits.
11820 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
11821 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
11822 previously they did not, which prevented them from receiving
11823 successful connections from relays for self-test or bandwidth
11824 testing. Also, when a relay is extending a circuit to a bridge,
11825 it needs to send a NETINFO cell, even when the bridge hasn't sent
11826 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
11827 - If the time to download the next old-style networkstatus is in
11828 the future, do not decline to consider whether to download the
11829 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
11833 - Avoid double-closing the listener socket in our socketpair()
11834 replacement (used on Windows) in the case where the addresses on
11835 our opened sockets don't match what we expected. Fixes bug 9400;
11836 bugfix on 0.0.2pre7. Found by Coverity.
11838 o Minor fixes (config options):
11839 - Avoid overflows when the user sets MaxCircuitDirtiness to a
11840 ridiculously high value, by imposing a (ridiculously high) 30-day
11841 maximum on MaxCircuitDirtiness.
11842 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
11843 message is logged at notice, not at info.
11844 - Warn and fail if a server is configured not to advertise any
11845 ORPorts at all. (We need *something* to put in our descriptor,
11846 or we just won't work.)
11849 - Track how many "TAP" and "NTor" circuit handshake requests we get,
11850 and how many we complete, and log it every hour to help relay
11851 operators follow trends in network load. Addresses ticket 9658.
11852 - Update to the August 7 2013 Maxmind GeoLite Country database.
11855 Changes in version 0.2.4.16-rc - 2013-08-10
11856 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
11857 series. It fixes several crash bugs in the 0.2.4 branch.
11860 - Fix a bug in the voting algorithm that could yield incorrect results
11861 when a non-naming authority declared too many flags. Fixes bug 9200;
11862 bugfix on 0.2.0.3-alpha.
11863 - Fix an uninitialized read that could in some cases lead to a remote
11864 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
11865 Anybody running a hidden service on the experimental 0.2.4.x
11866 branch should upgrade. (This is, so far as we know, unrelated to
11868 - Avoid an assertion failure when processing DNS replies without the
11869 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
11870 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
11871 0.2.4.15-rc. Found by stem integration tests.
11874 - Fix an invalid memory read that occurred when a pluggable
11875 transport proxy failed its configuration protocol.
11876 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
11877 - When evaluating whether to use a connection that we haven't
11878 decided is canonical using a recent link protocol version,
11879 decide that it's canonical only if it used address _does_
11880 match the desired address. Fixes bug 9309; bugfix on
11881 0.2.4.4-alpha. Reported by skruffy.
11882 - Make the default behavior of NumDirectoryGuards be to track
11883 NumEntryGuards. Now a user who changes only NumEntryGuards will get
11884 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
11885 - Fix a spurious compilation warning with some older versions of
11886 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
11889 - Update to the July 3 2013 Maxmind GeoLite Country database.
11892 Changes in version 0.2.4.15-rc - 2013-07-01
11893 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
11894 series. It fixes a few smaller bugs, but generally appears stable.
11895 Please test it and let us know whether it is!
11898 - When receiving a new configuration file via the control port's
11899 LOADCONF command, do not treat the defaults file as absent.
11900 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
11903 - Issue a warning when running with the bufferevents backend enabled.
11904 It's still not stable, and people should know that they're likely
11905 to hit unexpected problems. Closes ticket 9147.
11908 Changes in version 0.2.4.14-alpha - 2013-06-18
11909 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
11910 present in 0.2.4.13-alpha.
11913 - When we have too much memory queued in circuits (according to a new
11914 MaxMemInCellQueues option), close the circuits consuming the most
11915 memory. This prevents us from running out of memory as a relay if
11916 circuits fill up faster than they can be drained. Fixes bug 9063;
11917 bugfix on the 54th commit of Tor. This bug is a further fix beyond
11918 bug 6252, whose fix was merged into 0.2.3.21-rc.
11920 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
11921 where we tried to solve this issue simply by imposing an upper limit
11922 on the number of queued cells for a single circuit. That approach
11923 proved to be problematic, since there are ways to provoke clients to
11924 send a number of cells in excess of any such reasonable limit. Fixes
11925 bug 9072; bugfix on 0.2.4.13-alpha.
11927 - Limit hidden service descriptors to at most ten introduction
11928 points, to slow one kind of guard enumeration. Fixes bug 9002;
11929 bugfix on 0.1.1.11-alpha.
11932 Changes in version 0.2.4.13-alpha - 2013-06-14
11933 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
11934 vulnerabilities, makes socks5 username/password circuit isolation
11935 actually actually work (this time for sure!), and cleans up a bunch
11936 of other issues in preparation for a release candidate.
11938 o Major bugfixes (robustness):
11939 - Close any circuit that has too many cells queued on it. Fixes
11940 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
11941 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
11942 - Prevent the get_freelists() function from running off the end of
11943 the list of freelists if it somehow gets an unrecognized
11944 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
11946 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
11947 when an exit connection with optimistic data succeeds immediately
11948 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
11950 - Fix a directory authority crash bug when building a consensus
11951 using an older consensus as its basis. Fixes bug 8833. Bugfix
11955 - Avoid a memory leak where we would leak a consensus body when we
11956 find that a consensus which we couldn't previously verify due to
11957 missing certificates is now verifiable. Fixes bug 8719; bugfix
11959 - We used to always request authority certificates by identity digest,
11960 meaning we'd get the newest one even when we wanted one with a
11961 different signing key. Then we would complain about being given
11962 a certificate we already had, and never get the one we really
11963 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
11964 resource to request the one we want. Fixes bug 5595; bugfix on
11966 - Follow the socks5 protocol when offering username/password
11967 authentication. The fix for bug 8117 exposed this bug, and it
11968 turns out real-world applications like Pidgin do care. Bugfix on
11969 0.2.3.2-alpha; fixes bug 8879.
11970 - Prevent failures on Windows Vista and later when rebuilding the
11971 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
11972 bugfix on 0.2.4.12-alpha.
11975 - Fix an impossible buffer overrun in the AES unit tests. Fixes
11976 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
11977 - If for some reason we fail to write a microdescriptor while
11978 rebuilding the cache, do not let the annotations from that
11979 microdescriptor linger in the cache file, and do not let the
11980 microdescriptor stay recorded as present in its old location.
11981 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
11982 - Fix a memory leak that would occur whenever a configuration
11983 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
11984 - Paste the description for PathBias parameters from the man
11985 page into or.h, so the code documents them too. Fixes bug 7982;
11986 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
11987 - Relays now treat a changed IPv6 ORPort as sufficient reason to
11988 publish an updated descriptor. Fixes bug 6026; bugfix on
11990 - When launching a resolve request on behalf of an AF_UNIX control
11991 socket, omit the address field of the new entry connection, used in
11992 subsequent controller events, rather than letting tor_dup_addr()
11993 set it to "<unknown address type>". Fixes bug 8639; bugfix on
11996 o Minor bugfixes (log messages):
11997 - Fix a scaling issue in the path bias accounting code that
11998 resulted in "Bug:" log messages from either
11999 pathbias_scale_close_rates() or pathbias_count_build_success().
12000 This represents a bugfix on a previous bugfix: the original fix
12001 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
12003 - Give a less useless error message when the user asks for an IPv4
12004 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
12008 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
12009 to tolerate bug 8093 for now.
12010 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
12011 in directory authority votes to describe whether they have enough
12012 measured bandwidths to ignore advertised (relay descriptor)
12013 bandwidth claims. Resolves ticket 8711.
12014 - Update to the June 5 2013 Maxmind GeoLite Country database.
12016 o Removed documentation:
12017 - Remove some of the older contents of doc/ as obsolete; move others
12018 to torspec.git. Fixes bug 8965.
12020 o Code simplification and refactoring:
12021 - Avoid using character buffers when constructing most directory
12022 objects: this approach was unwieldy and error-prone. Instead,
12023 build smartlists of strings, and concatenate them when done.
12026 Changes in version 0.2.4.12-alpha - 2013-04-18
12027 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
12028 process for lengthening the guard rotation period, makes directory
12029 authority opinions in the consensus a bit less gameable, makes socks5
12030 username/password circuit isolation actually work, and fixes a wide
12031 variety of other issues.
12034 - Raise the default time that a client keeps an entry guard from
12035 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
12036 2012 paper. (We would make it even longer, but we need better client
12037 load balancing first.) Also, make the guard lifetime controllable
12038 via a new GuardLifetime torrc option and a GuardLifetime consensus
12039 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
12040 - Directory authorities now prefer using measured bandwidths to
12041 advertised ones when computing flags and thresholds. Resolves
12043 - Directory authorities that have more than a threshold number
12044 of relays with measured bandwidths now treat relays with unmeasured
12045 bandwidths as having bandwidth 0. Resolves ticket 8435.
12047 o Major bugfixes (assert / resource use):
12048 - Avoid a bug where our response to TLS renegotiation under certain
12049 network conditions could lead to a busy-loop, with 100% CPU
12050 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
12051 - Avoid an assertion when we discover that we'd like to write a cell
12052 onto a closing connection: just discard the cell. Fixes another
12053 case of bug 7350; bugfix on 0.2.4.4-alpha.
12055 o Major bugfixes (client-side privacy):
12056 - When we mark a circuit as unusable for new circuits, have it
12057 continue to be unusable for new circuits even if MaxCircuitDirtiness
12058 is increased too much at the wrong time, or the system clock jumps
12059 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
12060 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
12061 which have resolved to internal addresses") is set, apply that
12062 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
12063 - When an exit relay rejects a stream with reason "exit policy", but
12064 we only know an exit policy summary (e.g. from the microdesc
12065 consensus) for it, do not mark the relay as useless for all exiting.
12066 Instead, mark just the circuit as unsuitable for that particular
12067 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
12068 - Allow applications to get proper stream isolation with
12069 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
12070 username/password authentication also offer "no authentication". Tor
12071 had previously preferred "no authentication", so the applications
12072 never actually sent Tor their auth details. Now Tor selects
12073 username/password authentication if it's offered. You can disable
12074 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
12075 bug 8117; bugfix on 0.2.3.3-alpha.
12077 o Major bugfixes (other):
12078 - When unable to find any working directory nodes to use as a
12079 directory guard, give up rather than adding the same non-working
12080 nodes to the directory guard list over and over. Fixes bug 8231;
12081 bugfix on 0.2.4.8-alpha.
12084 - Reject as invalid most directory objects containing a NUL.
12085 Belt-and-suspender fix for bug 8037.
12086 - In our testsuite, create temporary directories with a bit more
12087 entropy in their name to make name collisions less likely. Fixes
12089 - Add CACHED keyword to ADDRMAP events in the control protocol
12090 to indicate whether a DNS result will be cached or not. Resolves
12092 - Update to the April 3 2013 Maxmind GeoLite Country database.
12094 o Minor features (build):
12095 - Detect and reject attempts to build Tor with threading support
12096 when OpenSSL has been compiled without threading support.
12098 - Clarify that when autoconf is checking for nacl, it is checking
12099 specifically for nacl with a fast curve25519 implementation.
12101 - Warn if building on a platform with an unsigned time_t: there
12102 are too many places where Tor currently assumes that time_t can
12103 hold negative values. We'd like to fix them all, but probably
12106 o Minor bugfixes (build):
12107 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
12108 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
12109 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
12110 - Add the old src/or/micro-revision.i filename to CLEANFILES.
12111 On the off chance that somebody has one, it will go away as soon
12112 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
12113 - Build Tor correctly on 32-bit platforms where the compiler can build
12114 but not run code using the "uint128_t" construction. Fixes bug 8587;
12115 bugfix on 0.2.4.8-alpha.
12116 - Fix compilation warning with some versions of clang that would
12117 prefer the -Wswitch-enum compiler flag to warn about switch
12118 statements with missing enum values, even if those switch
12119 statements have a "default:" statement. Fixes bug 8598; bugfix
12122 o Minor bugfixes (protocol):
12123 - Fix the handling of a TRUNCATE cell when it arrives while the
12124 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
12125 - Fix a misframing issue when reading the version numbers in a
12126 VERSIONS cell. Previously we would recognize [00 01 00 02] as
12127 'version 1, version 2, and version 0x100', when it should have
12128 only included versions 1 and 2. Fixes bug 8059; bugfix on
12129 0.2.0.10-alpha. Reported pseudonymously.
12130 - Make the format and order of STREAM events for DNS lookups
12131 consistent among the various ways to launch DNS lookups. Fixes
12132 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
12133 - Correct our check for which versions of Tor support the EXTEND2
12134 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
12135 later, when support was really added in version 0.2.4.8-alpha.
12136 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
12138 o Minor bugfixes (other):
12139 - Correctly store microdescriptors and extrainfo descriptors with
12140 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
12141 Bug reported by "cypherpunks".
12142 - Increase the width of the field used to remember a connection's
12143 link protocol version to two bytes. Harmless for now, since the
12144 only currently recognized versions are one byte long. Reported
12145 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
12146 - If the state file's path bias counts are invalid (presumably from a
12147 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
12148 additional checks and log messages to the scaling of Path Bias
12149 counts, in case there still are remaining issues with scaling.
12150 Should help resolve bug 8235.
12151 - Eliminate several instances where we use "Nickname=ID" to refer to
12152 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
12153 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
12154 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
12156 o Minor bugfixes (syscalls):
12157 - Always check the return values of functions fcntl() and
12158 setsockopt(). We don't believe these are ever actually failing in
12159 practice, but better safe than sorry. Also, checking these return
12160 values should please analysis tools like Coverity. Patch from
12161 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
12162 - Use direct writes rather than stdio when building microdescriptor
12163 caches, in an attempt to mitigate bug 8031, or at least make it
12166 o Minor bugfixes (config):
12167 - When rejecting a configuration because we were unable to parse a
12168 quoted string, log an actual error message. Fixes bug 7950; bugfix
12170 - Behave correctly when the user disables LearnCircuitBuildTimeout
12171 but doesn't tell us what they would like the timeout to be. Fixes
12172 bug 6304; bugfix on 0.2.2.14-alpha.
12173 - When autodetecting the number of CPUs, use the number of available
12174 CPUs in preference to the number of configured CPUs. Inform the
12175 user if this reduces the number of available CPUs. Fixes bug 8002;
12176 bugfix on 0.2.3.1-alpha.
12177 - Make it an error when you set EntryNodes but disable UseGuardNodes,
12178 since it will (surprisingly to some users) ignore EntryNodes. Fixes
12179 bug 8180; bugfix on 0.2.3.11-alpha.
12180 - Allow TestingTorNetworks to override the 4096-byte minimum for
12181 the Fast threshold. Otherwise they can't bootstrap until they've
12182 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
12183 - Fix some logic errors when the user manually overrides the
12184 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
12187 o Minor bugfixes (log messages to help diagnose bugs):
12188 - If we fail to free a microdescriptor because of bug 7164, log
12189 the filename and line number from which we tried to free it.
12190 - Add another diagnostic to the heartbeat message: track and log
12191 overhead that TLS is adding to the data we write. If this is
12192 high, we are sending too little data to SSL_write at a time.
12193 Diagnostic for bug 7707.
12194 - Add more detail to a log message about relaxed timeouts, to help
12196 - Warn more aggressively when flushing microdescriptors to a
12197 microdescriptor cache fails, in an attempt to mitigate bug 8031,
12198 or at least make it more diagnosable.
12199 - Improve debugging output to help track down bug 8185 ("Bug:
12200 outgoing relay cell has n_chan==NULL. Dropping.")
12201 - Log the purpose of a path-bias testing circuit correctly.
12202 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
12204 o Minor bugfixes (0.2.4.x log messages that were too noisy):
12205 - Don't attempt to relax the timeout of already opened 1-hop circuits.
12206 They might never timeout. This should eliminate some/all cases of
12207 the relaxed timeout log message.
12208 - Use circuit creation time for network liveness evaluation. This
12209 should eliminate warning log messages about liveness caused
12210 by changes in timeout evaluation. Fixes bug 6572; bugfix on
12212 - Reduce a path bias length check from notice to info. The message
12213 is triggered when creating controller circuits. Fixes bug 8196;
12214 bugfix on 0.2.4.8-alpha.
12215 - Fix a path state issue that triggered a notice during relay startup.
12216 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
12217 - Reduce occurrences of warns about circuit purpose in
12218 connection_ap_expire_building(). Fixes bug 8477; bugfix on
12221 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
12222 - If we encounter a write failure on a SOCKS connection before we
12223 finish our SOCKS handshake, don't warn that we closed the
12224 connection before we could send a SOCKS reply. Fixes bug 8427;
12225 bugfix on 0.1.0.1-rc.
12226 - Correctly recognize that [::1] is a loopback address. Fixes
12227 bug 8377; bugfix on 0.2.1.3-alpha.
12228 - Fix a directory authority warn caused when we have a large amount
12229 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
12230 - Don't log inappropriate heartbeat messages when hibernating: a
12231 hibernating node is _expected_ to drop out of the consensus,
12232 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
12233 bugfix on 0.2.3.1-alpha.
12234 - Don't complain about bootstrapping problems while hibernating.
12235 These complaints reflect a general code problem, but not one
12236 with any problematic effects (no connections are actually
12237 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
12239 o Documentation fixes:
12240 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
12241 names match. Fixes bug 7768.
12242 - Make the torify manpage no longer refer to tsocks; torify hasn't
12243 supported tsocks since 0.2.3.14-alpha.
12244 - Make the tor manpage no longer reference tsocks.
12245 - Fix the GeoIPExcludeUnknown documentation to refer to
12246 ExcludeExitNodes rather than the currently nonexistent
12247 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
12250 - The tor-tsocks.conf is no longer distributed or installed. We
12251 recommend that tsocks users use torsocks instead. Resolves
12255 Changes in version 0.2.4.11-alpha - 2013-03-11
12256 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
12257 more robust, makes hidden service authentication work again, and
12258 resolves a DPI fingerprint for Tor's SSL transport.
12260 o Major features (directory authorities):
12261 - Directory authorities now support a new consensus method (17)
12262 where they cap the published bandwidth of servers for which
12263 insufficient bandwidth measurements exist. Fixes part of bug 2286.
12264 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
12265 serve any v2 directory information. Now we can test disabling the
12266 old deprecated v2 directory format, and see whether doing so has
12267 any effect on network load. Begins to fix bug 6783.
12268 - Directory authorities now include inside each vote a statement of
12269 the performance thresholds they used when assigning flags.
12270 Implements ticket 8151.
12272 o Major bugfixes (directory authorities):
12273 - Stop marking every relay as having been down for one hour every
12274 time we restart a directory authority. These artificial downtimes
12275 were messing with our Stable and Guard flag calculations. Fixes
12276 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
12278 o Major bugfixes (hidden services):
12279 - Allow hidden service authentication to succeed again. When we
12280 refactored the hidden service introduction code back
12281 in 0.2.4.1-alpha, we didn't update the code that checks
12282 whether authentication information is present, causing all
12283 authentication checks to return "false". Fix for bug 8207; bugfix
12284 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
12286 o Minor features (relays, bridges):
12287 - Make bridge relays check once a minute for whether their IP
12288 address has changed, rather than only every 15 minutes. Resolves
12289 bugs 1913 and 1992.
12290 - Refactor resolve_my_address() so it returns the method by which we
12291 decided our public IP address (explicitly configured, resolved from
12292 explicit hostname, guessed from interfaces, learned by gethostname).
12293 Now we can provide more helpful log messages when a relay guesses
12294 its IP address incorrectly (e.g. due to unexpected lines in
12295 /etc/hosts). Resolves ticket 2267.
12296 - Teach bridge-using clients to avoid 0.2.2 bridges when making
12297 microdescriptor-related dir requests, and only fall back to normal
12298 descriptors if none of their bridges can handle microdescriptors
12299 (as opposed to the fix in ticket 4013, which caused them to fall
12300 back to normal descriptors if *any* of their bridges preferred
12301 them). Resolves ticket 4994.
12302 - Randomize the lifetime of our SSL link certificate, so censors can't
12303 use the static value for filtering Tor flows. Resolves ticket 8443;
12304 related to ticket 4014 which was included in 0.2.2.33.
12305 - Support a new version of the link protocol that allows 4-byte circuit
12306 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
12307 a possible resource exhaustion issue. Closes ticket 7351; implements
12310 o Minor features (portability):
12311 - Tweak the curve25519-donna*.c implementations to tolerate systems
12312 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
12313 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
12314 the signs of types during autoconf. This is better than our old
12315 approach, which didn't work when cross-compiling.
12316 - Detect the sign of enum values, rather than assuming that MSC is the
12317 only compiler where enum types are all signed. Fixes bug 7727;
12318 bugfix on 0.2.4.10-alpha.
12320 o Minor features (other):
12321 - Say "KBytes" rather than "KB" in the man page (for various values
12322 of K), to further reduce confusion about whether Tor counts in
12323 units of memory or fractions of units of memory. Resolves ticket 7054.
12324 - Clear the high bit on curve25519 public keys before passing them to
12325 our backend, in case we ever wind up using a backend that doesn't do
12326 so itself. If we used such a backend, and *didn't* clear the high bit,
12327 we could wind up in a situation where users with such backends would
12328 be distinguishable from users without. Fixes bug 8121; bugfix on
12330 - Update to the March 6 2013 Maxmind GeoLite Country database.
12332 o Minor bugfixes (clients):
12333 - When we receive a RELAY_END cell with the reason DONE, or with no
12334 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
12335 status as "connection refused". Previously we reported these cases
12336 as success but then immediately closed the connection. Fixes bug
12337 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
12338 - Downgrade an assertion in connection_ap_expire_beginning to an
12339 LD_BUG message. The fix for bug 8024 should prevent this message
12340 from displaying, but just in case, a warn that we can diagnose
12341 is better than more assert crashes. Fixes bug 8065; bugfix on
12343 - Lower path use bias thresholds to .80 for notice and .60 for warn.
12344 Also make the rate limiting flags for the path use bias log messages
12345 independent from the original path bias flags. Fixes bug 8161;
12346 bugfix on 0.2.4.10-alpha.
12348 o Minor bugfixes (relays):
12349 - Stop trying to resolve our hostname so often (e.g. every time we
12350 think about doing a directory fetch). Now we reuse the cached
12351 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
12352 and 2410 (bugfix on 0.1.2.2-alpha).
12353 - Stop sending a stray "(null)" in some cases for the server status
12354 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
12356 - When choosing which stream on a formerly stalled circuit to wake
12357 first, make better use of the platform's weak RNG. Previously,
12358 we had been using the % ("modulo") operator to try to generate a
12359 1/N chance of picking each stream, but this behaves badly with
12360 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
12362 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
12363 Irix's random() only return 15 bits; Solaris's random() returns more
12364 bits but its RAND_MAX says it only returns 15, and so on. Motivated
12365 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
12367 o Minor bugfixes (directory authorities):
12368 - Directory authorities now use less space when formatting identical
12369 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
12372 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
12373 - Avoid leaking memory if we fail to compute a consensus signature
12374 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
12375 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
12377 - Fix a memory leak during safe-cookie controller authentication.
12378 Bugfix on 0.2.3.13-alpha.
12379 - Avoid memory leak of IPv6 policy content if we fail to format it into
12380 a router descriptor. Bugfix on 0.2.4.7-alpha.
12382 o Minor bugfixes (other code correctness issues):
12383 - Avoid a crash if we fail to generate an extrainfo descriptor.
12384 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
12385 this is CID 718634.
12386 - When detecting the largest possible file descriptor (in order to
12387 close all file descriptors when launching a new program), actually
12388 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
12389 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
12391 - Fix a copy-and-paste error when adding a missing A1 to a routerset
12392 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
12393 Bugfix on 0.2.4.10-alpha.
12394 - Fix an impossible-to-trigger integer overflow when estimating how
12395 long our onionskin queue would take. (This overflow would require us
12396 to accept 4 million onionskins before processing 100 of them.) Fixes
12397 bug 8210; bugfix on 0.2.4.10-alpha.
12399 o Code simplification and refactoring:
12400 - Add a wrapper function for the common "log a message with a
12404 Changes in version 0.2.4.10-alpha - 2013-02-04
12405 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
12406 certain attacks that flood the network with relays; changes the queue
12407 for circuit create requests from a sized-based limit to a time-based
12408 limit; resumes building with MSVC on Windows; and fixes a wide variety
12411 o Major bugfixes (directory authority):
12412 - When computing directory thresholds, ignore any rejected-as-sybil
12413 nodes during the computation so that they can't influence Fast,
12414 Guard, etc. (We should have done this for proposal 109.) Fixes
12416 - When marking a node as a likely sybil, reset its uptime metrics
12417 to zero, so that it cannot time towards getting marked as Guard,
12418 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
12422 - When a TLS write is partially successful but incomplete, remember
12423 that the flushed part has been flushed, and notice that bytes were
12424 actually written. Reported and fixed pseudonymously. Fixes bug
12425 7708; bugfix on Tor 0.1.0.5-rc.
12426 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
12427 ID: these could be used to create unexpected streams and circuits
12428 which would count as "present" to some parts of Tor but "absent"
12429 to others, leading to zombie circuits and streams or to a bandwidth
12430 denial-of-service. Fixes bug 7889; bugfix on every released version
12431 of Tor. Reported by "oftc_must_be_destroyed".
12432 - Rename all macros in our local copy of queue.h to begin with "TOR_".
12433 This change seems the only good way to permanently prevent conflicts
12434 with queue.h on various operating systems. Fixes bug 8107; bugfix
12437 o Major features (relay):
12438 - Instead of limiting the number of queued onionskins (aka circuit
12439 create requests) to a fixed, hard-to-configure number, we limit
12440 the size of the queue based on how many we expect to be able to
12441 process in a given amount of time. We estimate the time it will
12442 take to process an onionskin based on average processing time
12443 of previous onionskins. Closes ticket 7291. You'll never have to
12444 configure MaxOnionsPending again.
12446 o Major features (portability):
12447 - Resume building correctly with MSVC and Makefile.nmake. This patch
12448 resolves numerous bugs and fixes reported by ultramage, including
12449 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
12450 - Make the ntor and curve25519 code build correctly with MSVC.
12451 Fix on 0.2.4.8-alpha.
12454 - When directory authorities are computing thresholds for flags,
12455 never let the threshold for the Fast flag fall below 4096
12456 bytes. Also, do not consider nodes with extremely low bandwidths
12457 when deciding thresholds for various directory flags. This change
12458 should raise our threshold for Fast relays, possibly in turn
12459 improving overall network performance; see ticket 1854. Resolves
12461 - The Tor client now ignores sub-domain components of a .onion
12462 address. This change makes HTTP "virtual" hosting
12463 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
12464 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
12465 hosted on the same hidden service. Implements proposal 204.
12466 - We compute the overhead from passing onionskins back and forth to
12467 cpuworkers, and report it when dumping statistics in response to
12468 SIGUSR1. Supports ticket 7291.
12470 o Minor features (path selection):
12471 - When deciding whether we have enough descriptors to build circuits,
12472 instead of looking at raw relay counts, look at which fraction
12473 of (bandwidth-weighted) paths we're able to build. This approach
12474 keeps clients from building circuits if their paths are likely to
12475 stand out statistically. The default fraction of paths needed is
12476 taken from the consensus directory; you can override it with the
12477 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
12478 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
12479 and we have GeoIP information, also exclude all nodes with unknown
12480 countries "??" and "A1". This behavior is controlled by the
12481 new GeoIPExcludeUnknown option: you can make such nodes always
12482 excluded with "GeoIPExcludeUnknown 1", and disable the feature
12483 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
12484 gets you the default behavior. Implements feature 7706.
12485 - Path Use Bias: Perform separate accounting for successful circuit
12486 use. Keep separate statistics on stream attempt rates versus stream
12487 success rates for each guard. Provide configurable thresholds to
12488 determine when to emit log messages or disable use of guards that
12489 fail too many stream attempts. Resolves ticket 7802.
12491 o Minor features (log messages):
12492 - When learning a fingerprint for a bridge, log its corresponding
12493 transport type. Implements ticket 7896.
12494 - Improve the log message when "Bug/attack: unexpected sendme cell
12495 from client" occurs, to help us track bug 8093.
12498 - Remove a couple of extraneous semicolons that were upsetting the
12499 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
12500 bugfix on 0.2.2.1-alpha.
12501 - Remove a source of rounding error during path bias count scaling;
12502 don't count cannibalized circuits as used for path bias until we
12503 actually try to use them; and fix a circuit_package_relay_cell()
12504 warning message about n_chan==NULL. Fixes bug 7802.
12505 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
12506 actually link against nacl when we're configured to use it. Fixes
12507 bug 7972; bugfix on 0.2.4.8-alpha.
12508 - Compile correctly with the --disable-curve25519 option. Fixes
12509 bug 8153; bugfix on 0.2.4.8-alpha.
12511 o Build improvements:
12512 - Do not report status verbosely from autogen.sh unless the -v flag
12513 is specified. Fixes issue 4664. Patch from Onizuka.
12514 - Replace all calls to snprintf() outside of src/ext with
12515 tor_snprintf(). Also remove the #define to replace snprintf with
12516 _snprintf on Windows; they have different semantics, and all of
12517 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
12518 - Try to detect if we are ever building on a platform where
12519 memset(...,0,...) does not set the value of a double to 0.0. Such
12520 platforms are permitted by the C standard, though in practice
12521 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
12522 currently support them, but it's better to detect them and fail
12523 than to perform erroneously.
12525 o Removed features:
12526 - Stop exporting estimates of v2 and v3 directory traffic shares
12527 in extrainfo documents. They were unneeded and sometimes inaccurate.
12528 Also stop exporting any v2 directory request statistics. Resolves
12530 - Drop support for detecting and warning about versions of Libevent
12531 before 1.3e. Nothing reasonable ships with them any longer;
12532 warning the user about them shouldn't be needed. Resolves ticket
12535 o Code simplifications and refactoring:
12536 - Rename "isin" functions to "contains", for grammar. Resolves
12538 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
12539 with the natural logarithm function from the system libm. Resolves
12543 Changes in version 0.2.4.9-alpha - 2013-01-15
12544 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
12545 work more robustly.
12548 - Fix backward compatibility logic when receiving an embedded ntor
12549 handshake tunneled in a CREATE cell. This clears up the "Bug:
12550 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
12554 Changes in version 0.2.4.8-alpha - 2013-01-14
12555 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
12556 risks, adds a new stronger and faster circuit handshake, and offers
12557 stronger and faster link encryption when both sides support it.
12560 - Preliminary support for directory guards (proposal 207): when
12561 possible, clients now use their entry guards for non-anonymous
12562 directory requests. This can help prevent client enumeration. Note
12563 that this behavior only works when we have a usable consensus
12564 directory, and when options about what to download are more or less
12565 standard. In the future we should re-bootstrap from our guards,
12566 rather than re-bootstrapping from the preconfigured list of
12567 directory sources that ships with Tor. Resolves ticket 6526.
12568 - Tor relays and clients now support a better CREATE/EXTEND cell
12569 format, allowing the sender to specify multiple address, identity,
12570 and handshake types. Implements Robert Ransom's proposal 200;
12571 closes ticket 7199.
12573 o Major features (new circuit handshake):
12574 - Tor now supports a new circuit extension handshake designed by Ian
12575 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
12576 circuit extension handshake, later called "TAP", was a bit slow
12577 (especially on the relay side), had a fragile security proof, and
12578 used weaker keys than we'd now prefer. The new circuit handshake
12579 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
12580 function, making it significantly more secure than the older
12581 handshake, and significantly faster. Tor can use one of two built-in
12582 pure-C curve25519-donna implementations by Adam Langley, or it
12583 can link against the "nacl" library for a tuned version if present.
12585 The built-in version is very fast for 64-bit systems when building
12586 with GCC. The built-in 32-bit version is still faster than the
12587 old TAP protocol, but using libnacl is better on most such hosts.
12589 Clients don't currently use this protocol by default, since
12590 comparatively few clients support it so far. To try it, set
12591 UseNTorHandshake to 1.
12593 Implements proposal 216; closes ticket 7202.
12595 o Major features (better link encryption):
12596 - Relays can now enable the ECDHE TLS ciphersuites when available
12597 and appropriate. These ciphersuites let us negotiate forward-secure
12598 TLS secret keys more safely and more efficiently than with our
12599 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
12600 public relays prefer the (faster) P224 group, and bridges prefer
12601 the (more common) P256 group; you can override this with the
12604 Enabling these ciphers was a little tricky, since for a long time,
12605 clients had been claiming to support them without actually doing
12606 so, in order to foil fingerprinting. But with the client-side
12607 implementation of proposal 198 in 0.2.3.17-beta, clients can now
12608 match the ciphers from recent Firefox versions *and* list the
12609 ciphers they actually mean, so relays can believe such clients
12610 when they advertise ECDHE support in their TLS ClientHello messages.
12612 This feature requires clients running 0.2.3.17-beta or later,
12613 and requires both sides to be running OpenSSL 1.0.0 or later
12614 with ECC support. OpenSSL 1.0.1, with the compile-time option
12615 "enable-ec_nistp_64_gcc_128", is highly recommended.
12617 Implements the relay side of proposal 198; closes ticket 7200.
12620 - Avoid crashing when, as a relay without IPv6-exit support, a
12621 client insists on getting an IPv6 address or nothing. Fixes bug
12622 7814; bugfix on 0.2.4.7-alpha.
12625 - Improve circuit build timeout handling for hidden services.
12626 In particular: adjust build timeouts more accurately depending
12627 upon the number of hop-RTTs that a particular circuit type
12628 undergoes. Additionally, launch intro circuits in parallel
12629 if they timeout, and take the first one to reply as valid.
12630 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
12631 separate error codes; or at least, don't break for that reason.
12632 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
12633 - Update to the January 2 2013 Maxmind GeoLite Country database.
12635 o Minor features (testing):
12636 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
12637 (P-256) Diffie-Hellman handshakes to src/or/bench.
12638 - Add benchmark functions to test onion handshake performance.
12640 o Minor features (path bias detection):
12641 - Alter the Path Bias log messages to be more descriptive in terms
12642 of reporting timeouts and other statistics.
12643 - Create three levels of Path Bias log messages, as opposed to just
12644 two. These are configurable via consensus as well as via the torrc
12645 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
12646 The default values are 0.70, 0.50, and 0.30 respectively.
12647 - Separate the log message levels from the decision to drop guards,
12648 which also is available via torrc option PathBiasDropGuards.
12649 PathBiasDropGuards still defaults to 0 (off).
12650 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
12651 in combination with PathBiasExtremeRate.
12652 - Increase the default values for PathBiasScaleThreshold and
12653 PathBiasCircThreshold from (200, 20) to (300, 150).
12654 - Add in circuit usage accounting to path bias. If we try to use a
12655 built circuit but fail for any reason, it counts as path bias.
12656 Certain classes of circuits where the adversary gets to pick your
12657 destination node are exempt from this accounting. Usage accounting
12658 can be specifically disabled via consensus parameter or torrc.
12659 - Convert all internal path bias state to double-precision floating
12660 point, to avoid roundoff error and other issues.
12661 - Only record path bias information for circuits that have completed
12662 *two* hops. Assuming end-to-end tagging is the attack vector, this
12663 makes us more resilient to ambient circuit failure without any
12664 detection capability loss.
12666 o Minor bugfixes (log messages):
12667 - Rate-limit the "No circuits are opened. Relaxed timeout for a
12668 circuit with channel state open..." message to once per hour to
12669 keep it from filling the notice logs. Mitigates bug 7799 but does
12670 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
12671 - Avoid spurious warnings when configuring multiple client ports of
12672 which only some are nonlocal. Previously, we had claimed that some
12673 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
12676 o Code simplifications and refactoring:
12677 - Get rid of a couple of harmless clang warnings, where we compared
12678 enums to ints. These warnings are newly introduced in clang 3.2.
12679 - Split the onion.c file into separate modules for the onion queue
12680 and the different handshakes it supports.
12681 - Remove the marshalling/unmarshalling code for sending requests to
12682 cpuworkers over a socket, and instead just send structs. The
12683 recipient will always be the same Tor binary as the sender, so
12684 any encoding is overkill.
12687 Changes in version 0.2.4.7-alpha - 2012-12-24
12688 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
12689 directory mirrors for more robust bootstrapping; fixes more issues where
12690 clients with changing network conditions refuse to make any circuits;
12691 adds initial support for exiting to IPv6 addresses; resumes being able
12692 to update our GeoIP database, and includes the geoip6 file this time;
12693 turns off the client-side DNS cache by default due to privacy risks;
12694 and fixes a variety of other issues.
12696 o Major features (client resilience):
12697 - Add a new "FallbackDir" torrc option to use when we can't use
12698 a directory mirror from the consensus (either because we lack a
12699 consensus, or because they're all down). Currently, all authorities
12700 are fallbacks by default, and there are no other default fallbacks,
12701 but that will change. This option will allow us to give clients a
12702 longer list of servers to try to get a consensus from when first
12703 connecting to the Tor network, and thereby reduce load on the
12704 directory authorities. Implements proposal 206, "Preconfigured
12705 directory sources for bootstrapping". We also removed the old
12706 "FallbackNetworkstatus" option, since we never got it working well
12707 enough to use it. Closes bug 572.
12708 - If we have no circuits open, use a relaxed timeout (the
12709 95-percentile cutoff) until a circuit succeeds. This heuristic
12710 should allow Tor to succeed at building circuits even when the
12711 network connection drastically changes. Should help with bug 3443.
12713 o Major features (IPv6):
12714 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
12715 connectivity, then set the IPv6Exit flag to 1. Also make sure your
12716 exit policy reads as you would like: the address * applies to all
12717 address families, whereas *4 is IPv4 address only, and *6 is IPv6
12718 addresses only. On the client side, you'll need to wait until the
12719 authorities have upgraded, wait for enough exits to support IPv6,
12720 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
12721 ticket 5547, implements proposal 117 as revised in proposal 208.
12723 We DO NOT recommend that clients with actual anonymity needs start
12724 using IPv6 over Tor yet, since not enough exits support it yet.
12726 o Major features (geoip database):
12727 - Maxmind began labelling Tor relays as being in country "A1",
12728 which breaks by-country node selection inside Tor. Now we use a
12729 script to replace "A1" ("Anonymous Proxy") entries in our geoip
12730 file with real country codes. This script fixes about 90% of "A1"
12731 entries automatically and uses manual country code assignments to
12732 fix the remaining 10%. See src/config/README.geoip for details.
12733 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
12734 Country database, as modified above.
12736 o Major bugfixes (client-side DNS):
12737 - Turn off the client-side DNS cache by default. Updating and using
12738 the DNS cache is now configurable on a per-client-port
12739 level. SOCKSPort, DNSPort, etc lines may now contain
12740 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
12741 cache these types of DNS answers when we receive them from an
12742 exit node in response to an application request on this port, and
12743 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
12744 cached DNS answers of these types, we shouldn't use them. It's
12745 potentially risky to use cached DNS answers at the client, since
12746 doing so can indicate to one exit what answers we've gotten
12747 for DNS lookups in the past. With IPv6, this becomes especially
12748 problematic. Using cached DNS answers for requests on the same
12749 circuit would present less linkability risk, since all traffic
12750 on a circuit is already linkable, but it would also provide
12751 little performance benefit: the exit node caches DNS replies
12752 too. Implements a simplified version of Proposal 205. Implements
12755 o Major bugfixes (other):
12756 - Alter circuit build timeout measurement to start at the point
12757 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
12758 initialization). This should make our timeout measurements more
12759 uniform. Previously, we were sometimes including ORconn setup time
12760 in our circuit build time measurements. Should resolve bug 3443.
12761 - Fix an assertion that could trigger in hibernate_go_dormant() when
12762 closing an or_connection_t: call channel_mark_for_close() rather
12763 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
12765 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
12766 7655; bugfix on 0.2.4.6-alpha.
12769 - Add a new torrc option "ServerTransportListenAddr" to let bridge
12770 operators select the address where their pluggable transports will
12771 listen for connections. Resolves ticket 7013.
12772 - Allow an optional $ before the node identity digest in the
12773 controller command GETINFO ns/id/<identity>, for consistency with
12774 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
12775 - Log packaged cell fullness as part of the heartbeat message.
12776 Diagnosis to try to determine the extent of bug 7743.
12778 o Minor features (IPv6):
12779 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
12780 prefer to hand out virtual IPv6 addresses, since there are more of
12781 them and we can't run out. To override this behavior and make IPv4
12782 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
12783 or DNSPort you're using for resolving. Implements ticket 7571.
12784 - AutomapHostsOnResolve responses are now randomized, to avoid
12785 annoying situations where Tor is restarted and applications
12786 connect to the wrong addresses.
12787 - Never try more than 1000 times to pick a new virtual address when
12788 AutomapHostsOnResolve is set. That's good enough so long as we
12789 aren't close to handing out our entire virtual address space;
12790 if you're getting there, it's best to switch to IPv6 virtual
12794 - The ADDRMAP command can no longer generate an ill-formed error
12795 code on a failed MAPADDRESS. It now says "internal" rather than
12796 an English sentence fragment with spaces in the middle. Bugfix on
12797 Tor 0.2.0.19-alpha.
12798 - Fix log messages and comments to avoid saying "GMT" when we mean
12799 "UTC". Fixes bug 6113.
12800 - Compile on win64 using mingw64. Fixes bug 7260; patches from
12802 - Fix a crash when debugging unit tests on Windows: deallocate a
12803 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
12804 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
12807 - The DirServer option is now DirAuthority, for consistency with
12808 current naming patterns. You can still use the old DirServer form.
12810 o Code simplification and refactoring:
12811 - Move the client-side address-map/virtual-address/DNS-cache code
12812 out of connection_edge.c into a new addressmap.c module.
12813 - Remove unused code for parsing v1 directories and "running routers"
12814 documents. Fixes bug 6887.
12817 Changes in version 0.2.3.25 - 2012-11-19
12818 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
12819 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
12820 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
12821 programmer, and friend. Unstinting in his dedication to the cause of
12822 freedom, he inspired and helped many of us as we began our work on
12823 anonymity, and inspires us still. Please honor his memory by writing
12824 software to protect people's freedoms, and by helping others to do so.
12826 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
12827 significantly reduced directory overhead (via microdescriptors),
12828 enormous crypto performance improvements for fast relays on new
12829 enough hardware, a new v3 TLS handshake protocol that can better
12830 resist fingerprinting, support for protocol obfuscation plugins (aka
12831 pluggable transports), better scalability for hidden services, IPv6
12832 support for bridges, performance improvements like allowing clients
12833 to skip the first round-trip on the circuit ("optimistic data") and
12834 refilling token buckets more often, a new "stream isolation" design
12835 to isolate different applications on different circuits, and many
12836 stability, security, and privacy fixes.
12839 - Tor tries to wipe potentially sensitive data after using it, so
12840 that if some subsequent security failure exposes Tor's memory,
12841 the damage will be limited. But we had a bug where the compiler
12842 was eliminating these wipe operations when it decided that the
12843 memory was no longer visible to a (correctly running) program,
12844 hence defeating our attempt at defense in depth. We fix that
12845 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
12846 is unlikely to optimize away. Future versions of Tor may use
12847 a less ridiculously heavy approach for this. Fixes bug 7352.
12848 Reported in an article by Andrey Karpov.
12851 - Fix a harmless bug when opting against publishing a relay descriptor
12852 because DisableNetwork is set. Fixes bug 7464; bugfix on
12856 Changes in version 0.2.4.6-alpha - 2012-11-13
12857 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
12858 makes our defense-in-depth memory wiping more reliable, and begins to
12859 count IPv6 addresses in bridge statistics,
12862 - Fix an assertion failure that could occur when closing a connection
12863 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
12865 - Tor tries to wipe potentially sensitive data after using it, so
12866 that if some subsequent security failure exposes Tor's memory,
12867 the damage will be limited. But we had a bug where the compiler
12868 was eliminating these wipe operations when it decided that the
12869 memory was no longer visible to a (correctly running) program,
12870 hence defeating our attempt at defense in depth. We fix that
12871 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
12872 is unlikely to optimize away. Future versions of Tor may use
12873 a less ridiculously heavy approach for this. Fixes bug 7352.
12874 Reported in an article by Andrey Karpov.
12877 - Add GeoIP database for IPv6 addresses. The new config option
12879 - Bridge statistics now count bridge clients connecting over IPv6:
12880 bridge statistics files now list "bridge-ip-versions" and
12881 extra-info documents list "geoip6-db-digest". The control protocol
12882 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
12883 implementation by "shkoo", addressing ticket 5055.
12886 - Warn when we are binding low ports when hibernation is enabled;
12887 previously we had warned when we were _advertising_ low ports with
12888 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
12889 - Fix a harmless bug when opting against publishing a relay descriptor
12890 because DisableNetwork is set. Fixes bug 7464; bugfix on
12892 - Add warning message when a managed proxy dies during configuration.
12893 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
12894 - Fix a linking error when building tor-fw-helper without miniupnp.
12895 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
12896 - Check for closing an or_connection_t without going through correct
12897 channel functions; emit a warning and then call
12898 connection_or_close_for_error() so we don't assert as in bugs 7212
12900 - Compile correctly on compilers without C99 designated initializer
12901 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
12902 - Avoid a possible assert that can occur when channel_send_destroy() is
12903 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
12904 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
12905 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
12906 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
12907 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
12909 o Code simplification and refactoring:
12910 - Start using OpenBSD's implementation of queue.h, so that we don't
12911 need to hand-roll our own pointer and list structures whenever we
12912 need them. (We can't rely on a sys/queue.h, since some operating
12913 systems don't have them, and the ones that do have them don't all
12914 present the same extensions.)
12917 Changes in version 0.2.4.5-alpha - 2012-10-25
12918 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
12919 two important security vulnerabilities that could lead to remotely
12920 triggerable relay crashes, fix a major bug that was preventing clients
12921 from choosing suitable exit nodes, and refactor some of our code.
12923 o Major bugfixes (security, also in 0.2.3.24-rc):
12924 - Fix a group of remotely triggerable assertion failures related to
12925 incorrect link protocol negotiation. Found, diagnosed, and fixed
12926 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12928 - Fix a denial of service attack by which any directory authority
12929 could crash all the others, or by which a single v2 directory
12930 authority could crash everybody downloading v2 directory
12931 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12933 o Major bugfixes (also in 0.2.3.24-rc):
12934 - When parsing exit policy summaries from microdescriptors, we had
12935 previously been ignoring the last character in each one, so that
12936 "accept 80,443,8080" would be treated by clients as indicating
12937 a node that allows access to ports 80, 443, and 808. That would
12938 lead to clients attempting connections that could never work,
12939 and ignoring exit nodes that would support their connections. Now
12940 clients parse these exit policy summaries correctly. Fixes bug 7192;
12941 bugfix on 0.2.3.1-alpha.
12943 o Minor bugfixes (also in 0.2.3.24-rc):
12944 - Clients now consider the ClientRejectInternalAddresses config option
12945 when using a microdescriptor consensus stanza to decide whether
12946 an exit relay would allow exiting to an internal address. Fixes
12947 bug 7190; bugfix on 0.2.3.1-alpha.
12950 - Only disable TLS session ticket support when running as a TLS
12951 server. Now clients will blend better with regular Firefox
12952 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
12954 o Code simplification and refactoring:
12955 - Start using OpenBSD's implementation of queue.h (originally by
12957 - Move the entry node code from circuitbuild.c to its own file.
12958 - Move the circuit build timeout tracking code from circuitbuild.c
12962 Changes in version 0.2.3.24-rc - 2012-10-25
12963 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
12964 could lead to remotely triggerable relay crashes, and fixes
12965 a major bug that was preventing clients from choosing suitable exit
12968 o Major bugfixes (security):
12969 - Fix a group of remotely triggerable assertion failures related to
12970 incorrect link protocol negotiation. Found, diagnosed, and fixed
12971 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12973 - Fix a denial of service attack by which any directory authority
12974 could crash all the others, or by which a single v2 directory
12975 authority could crash everybody downloading v2 directory
12976 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
12979 - When parsing exit policy summaries from microdescriptors, we had
12980 previously been ignoring the last character in each one, so that
12981 "accept 80,443,8080" would be treated by clients as indicating
12982 a node that allows access to ports 80, 443, and 808. That would
12983 lead to clients attempting connections that could never work,
12984 and ignoring exit nodes that would support their connections. Now
12985 clients parse these exit policy summaries correctly. Fixes bug 7192;
12986 bugfix on 0.2.3.1-alpha.
12989 - Clients now consider the ClientRejectInternalAddresses config option
12990 when using a microdescriptor consensus stanza to decide whether
12991 an exit relay would allow exiting to an internal address. Fixes
12992 bug 7190; bugfix on 0.2.3.1-alpha.
12995 Changes in version 0.2.4.4-alpha - 2012-10-20
12996 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
12997 vulnerability introduced by a change in OpenSSL, fixes a remotely
12998 triggerable assert, and adds new channel_t and circuitmux_t abstractions
12999 that will make it easier to test new connection transport and cell
13000 scheduling algorithms.
13002 o New directory authorities (also in 0.2.3.23-rc):
13003 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
13004 authority. Closes ticket 5749.
13006 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
13007 - Disable TLS session tickets. OpenSSL's implementation was giving
13008 our TLS session keys the lifetime of our TLS context objects, when
13009 perfect forward secrecy would want us to discard anything that
13010 could decrypt a link connection as soon as the link connection
13011 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
13012 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
13013 - Discard extraneous renegotiation attempts once the V3 link
13014 protocol has been initiated. Failure to do so left us open to
13015 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
13016 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
13018 o Internal abstraction features:
13019 - Introduce new channel_t abstraction between circuits and
13020 or_connection_t to allow for implementing alternate OR-to-OR
13021 transports. A channel_t is an abstract object which can either be a
13022 cell-bearing channel, which is responsible for authenticating and
13023 handshaking with the remote OR and transmitting cells to and from
13024 it, or a listening channel, which spawns new cell-bearing channels
13025 at the request of remote ORs. Implements part of ticket 6465.
13026 - Also new is the channel_tls_t subclass of channel_t, adapting it
13027 to the existing or_connection_t code. The V2/V3 protocol handshaking
13028 code which formerly resided in command.c has been moved below the
13029 channel_t abstraction layer and may be found in channeltls.c now.
13030 Implements the rest of ticket 6465.
13031 - Introduce new circuitmux_t storing the queue of circuits for
13032 a channel; this encapsulates and abstracts the queue logic and
13033 circuit selection policy, and allows the latter to be overridden
13034 easily by switching out a policy object. The existing EWMA behavior
13035 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
13037 o Required libraries:
13038 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
13039 strongly recommended.
13042 - Warn users who run hidden services on a Tor client with
13043 UseEntryGuards disabled that their hidden services will be
13044 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
13045 attack which motivated Tor to support entry guards in the first
13046 place). Resolves ticket 6889.
13047 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
13048 dhill. Resolves ticket 6982.
13049 - Option OutboundBindAddress can be specified multiple times and
13050 accepts IPv6 addresses. Resolves ticket 6876.
13052 o Minor bugfixes (also in 0.2.3.23-rc):
13053 - Don't serve or accept v2 hidden service descriptors over a
13054 relay's DirPort. It's never correct to do so, and disabling it
13055 might make it more annoying to exploit any bugs that turn up in the
13056 descriptor-parsing code. Fixes bug 7149.
13057 - Fix two cases in src/or/transports.c where we were calling
13058 fmt_addr() twice in a parameter list. Bug found by David
13059 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
13060 - Fix memory leaks whenever we logged any message about the "path
13061 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
13062 - When relays refuse a "create" cell because their queue of pending
13063 create cells is too big (typically because their cpu can't keep up
13064 with the arrival rate), send back reason "resource limit" rather
13065 than reason "internal", so network measurement scripts can get a
13066 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
13069 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
13070 - Free some more still-in-use memory at exit, to make hunting for
13071 memory leaks easier. Resolves bug 7029.
13072 - When a Tor client gets a "truncated" relay cell, the first byte of
13073 its payload specifies why the circuit was truncated. We were
13074 ignoring this 'reason' byte when tearing down the circuit, resulting
13075 in the controller not being told why the circuit closed. Now we
13076 pass the reason from the truncated cell to the controller. Bugfix
13077 on 0.1.2.3-alpha; fixes bug 7039.
13078 - Downgrade "Failed to hand off onionskin" messages to "debug"
13079 severity, since they're typically redundant with the "Your computer
13080 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
13081 - Make clients running with IPv6 bridges connect over IPv6 again,
13082 even without setting new config options ClientUseIPv6 and
13083 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
13084 - Use square brackets around IPv6 addresses in numerous places
13085 that needed them, including log messages, HTTPS CONNECT proxy
13086 requests, TransportProxy statefile entries, and pluggable transport
13087 extra-info lines. Fixes bug 7011; patch by David Fifield.
13089 o Code refactoring and cleanup:
13090 - Source files taken from other packages now reside in src/ext;
13091 previously they were scattered around the rest of Tor.
13092 - Avoid use of reserved identifiers in our C code. The C standard
13093 doesn't like us declaring anything that starts with an
13094 underscore, so let's knock it off before we get in trouble. Fix
13095 for bug 1031; bugfix on the first Tor commit.
13098 Changes in version 0.2.3.23-rc - 2012-10-20
13099 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
13100 vulnerability introduced by a change in OpenSSL, and fixes a variety
13101 of smaller bugs in preparation for the release.
13103 o New directory authorities:
13104 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
13105 authority. Closes ticket 5749.
13107 o Major bugfixes (security/privacy):
13108 - Disable TLS session tickets. OpenSSL's implementation was giving
13109 our TLS session keys the lifetime of our TLS context objects, when
13110 perfect forward secrecy would want us to discard anything that
13111 could decrypt a link connection as soon as the link connection
13112 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
13113 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
13114 - Discard extraneous renegotiation attempts once the V3 link
13115 protocol has been initiated. Failure to do so left us open to
13116 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
13117 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
13120 - Fix a possible crash bug when checking for deactivated circuits
13121 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
13122 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
13124 o Minor bugfixes (on 0.2.3.x):
13125 - Fix two cases in src/or/transports.c where we were calling
13126 fmt_addr() twice in a parameter list. Bug found by David
13127 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
13128 - Convert an assert in the pathbias code to a log message. The assert
13129 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
13130 bugfix on 0.2.3.17-beta.
13131 - Fix memory leaks whenever we logged any message about the "path
13132 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
13134 o Minor bugfixes (on 0.2.2.x and earlier):
13135 - Don't serve or accept v2 hidden service descriptors over a relay's
13136 DirPort. It's never correct to do so, and disabling it might
13137 make it more annoying to exploit any bugs that turn up in the
13138 descriptor-parsing code. Fixes bug 7149.
13139 - When relays refuse a "create" cell because their queue of pending
13140 create cells is too big (typically because their cpu can't keep up
13141 with the arrival rate), send back reason "resource limit" rather
13142 than reason "internal", so network measurement scripts can get a
13143 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
13144 - Correct file sizes when reading binary files on Cygwin, to avoid
13145 a bug where Tor would fail to read its state file. Fixes bug 6844;
13146 bugfix on 0.1.2.7-alpha.
13147 - Avoid undefined behavior when parsing the list of supported
13148 rendezvous/introduction protocols in a hidden service descriptor.
13149 Previously, Tor would have confused (as-yet-unused) protocol version
13150 numbers greater than 32 with lower ones on many platforms. Fixes
13151 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
13153 o Documentation fixes:
13154 - Clarify that hidden services are TCP only. Fixes bug 6024.
13157 Changes in version 0.2.4.3-alpha - 2012-09-22
13158 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
13159 assertion, resumes letting relays test reachability of their DirPort,
13160 and cleans up a bunch of smaller bugs.
13163 - Fix an assertion failure in tor_timegm() that could be triggered
13164 by a badly formatted directory object. Bug found by fuzzing with
13165 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
13168 - Fix a possible crash bug when checking for deactivated circuits
13169 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
13170 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
13171 - Allow routers to detect that their own DirPorts are running. When
13172 we removed support for versions_supports_begindir, we also
13173 accidentally removed the mechanism we used to self-test our
13174 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
13175 bugfix on 0.2.4.2-alpha.
13177 o Security features:
13178 - Switch to a completely time-invariant approach for picking nodes
13179 weighted by bandwidth. Our old approach would run through the
13180 part of the loop after it had made its choice slightly slower
13181 than it ran through the part of the loop before it had made its
13182 choice. Addresses ticket 6538.
13183 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
13184 by tor2web clients allows hidden services to identify tor2web
13185 clients through their repeated selection of the same rendezvous
13186 and introduction point circuit endpoints (their guards). Resolves
13190 - Enable Tor to read configuration, state, and key information from
13191 a FIFO. Previously Tor would only read from files with a positive
13192 stat.st_size. Code from meejah; fixes bug 6044.
13195 - Correct file sizes when reading binary files on Cygwin, to avoid
13196 a bug where Tor would fail to read its state file. Fixes bug 6844;
13197 bugfix on 0.1.2.7-alpha.
13198 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
13199 bugfix on 0.2.0.3-alpha.
13200 - When complaining about a client port on a public address, log
13201 which address we're complaining about. Fixes bug 4020; bugfix on
13202 0.2.3.3-alpha. Patch by Tom Fitzhenry.
13203 - Convert an assert in the pathbias code to a log message. The assert
13204 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
13205 bugfix on 0.2.3.17-beta.
13206 - Our new buildsystem was overzealous about rebuilding manpages: it
13207 would rebuild them all whenever any one of them changed. Now our
13208 dependency checking should be correct. Fixes bug 6843; bugfix on
13210 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
13211 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
13212 - Correct log printout about which address family is preferred
13213 when connecting to a bridge with both an IPv4 and IPv6 OR port.
13214 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
13216 o Minor bugfixes (code cleanliness):
13217 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
13218 with large values. This situation was untriggered, but nevertheless
13219 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
13220 - Reject consensus votes with more than 64 known-flags. We aren't even
13221 close to that limit yet, and our code doesn't handle it correctly.
13222 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
13223 - Avoid undefined behavior when parsing the list of supported
13224 rendezvous/introduction protocols in a hidden service descriptor.
13225 Previously, Tor would have confused (as-yet-unused) protocol version
13226 numbers greater than 32 with lower ones on many platforms. Fixes
13227 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
13228 - Fix handling of rendezvous client authorization types over 8.
13229 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
13230 - Fix building with older versions of GCC (2.95, for one) that don't
13231 like preprocessor directives inside macro arguments. Found by
13232 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
13233 - Switch weighted node selection rule from using a list of doubles
13234 to using a list of int64_t. This change should make the process
13235 slightly easier to debug and maintain. Needed to finish ticket 6538.
13237 o Code simplification and refactoring:
13238 - Move the generic "config" code into a new file, and have "config.c"
13239 hold only torrc- and state-related code. Resolves ticket 6823.
13240 - Move the core of our "choose a weighted element at random" logic
13241 into its own function, and give it unit tests. Now the logic is
13242 testable, and a little less fragile too.
13243 - Removed the testing_since field of node_t, which hasn't been used
13244 for anything since 0.2.0.9-alpha.
13246 o Documentation fixes:
13247 - Clarify that hidden services are TCP only. Fixes bug 6024.
13248 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
13252 Changes in version 0.2.3.22-rc - 2012-09-11
13253 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
13257 - Fix an assertion failure in tor_timegm() that could be triggered
13258 by a badly formatted directory object. Bug found by fuzzing with
13259 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
13262 - Avoid segfault when starting up having run with an extremely old
13263 version of Tor and parsing its state file. Fixes bug 6801; bugfix
13267 Changes in version 0.2.2.39 - 2012-09-11
13268 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
13272 - Fix an assertion failure in tor_timegm() that could be triggered
13273 by a badly formatted directory object. Bug found by fuzzing with
13274 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
13275 - Do not crash when comparing an address with port value 0 to an
13276 address policy. This bug could have been used to cause a remote
13277 assertion failure by or against directory authorities, or to
13278 allow some applications to crash clients. Fixes bug 6690; bugfix
13282 Changes in version 0.2.4.2-alpha - 2012-09-10
13283 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
13284 raises the default rate limiting even more, and makes the bootstrapping
13285 log messages less noisy.
13288 - Automatically forward the TCP ports of pluggable transport
13289 proxies using tor-fw-helper if PortForwarding is enabled. Implements
13293 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
13294 to 1GB/1GB. The previous defaults were intended to be "basically
13295 infinite", but it turns out they're now limiting our 100mbit+
13296 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
13297 last time we raised it).
13300 - Detect when we're running with a version of OpenSSL other than the
13301 one we compiled with. This has occasionally given people hard-to-
13303 - Log fewer lines at level "notice" about our OpenSSL and Libevent
13304 versions and capabilities when everything is going right. Resolves
13305 part of ticket 6736.
13306 - Directory authorities no long accept descriptors for any version of
13307 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
13308 These versions are insecure, unsupported, or both. Implements
13312 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
13313 to start with a triple-underscore so the controller won't touch it.
13314 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
13315 - Avoid segfault when starting up having run with an extremely old
13316 version of Tor and parsing its state file. Fixes bug 6801; bugfix
13318 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
13319 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
13320 - Don't follow the NULL pointer if microdescriptor generation fails.
13321 (This does not appear to be triggerable, but it's best to be safe.)
13322 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
13323 - Fix mis-declared dependencies on src/common/crypto.c and
13324 src/or/tor_main.c that could break out-of-tree builds under some
13325 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
13326 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
13327 6778; bugfix on 0.2.4.1-alpha.
13328 - Fix a harmless (in this case) build warning for implicitly
13329 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
13331 o Removed features:
13332 - Now that all versions before 0.2.2.x are disallowed, we no longer
13333 need to work around their missing features. Thus we can remove a
13334 bunch of compatibility code.
13336 o Code refactoring:
13337 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
13338 TCP ports to forward. In the past it only accepted two ports:
13339 the ORPort and the DirPort.
13342 Changes in version 0.2.4.1-alpha - 2012-09-05
13343 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
13344 bridgedb; lets relays use IPv6 addresses and directory authorities
13345 advertise them; and switches to a cleaner build interface.
13347 This is the first alpha release in a new series, so expect there to
13348 be bugs. Users who would rather test out a more stable branch should
13349 stay with 0.2.3.x for now.
13351 o Major features (bridges):
13352 - Bridges now report the pluggable transports they support to the
13353 bridge authority, so it can pass the supported transports on to
13354 bridgedb and/or eventually do reachability testing. Implements
13357 o Major features (IPv6):
13358 - Bridge authorities now accept IPv6 bridge addresses and include
13359 them in network status documents. Implements ticket 5534.
13360 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
13361 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
13362 to happen. Implements ticket 5535.
13363 - All kind of relays, not just bridges, can now advertise an IPv6
13364 OR port. Implements ticket 6362.
13365 - Directory authorities vote on IPv6 OR ports using the new consensus
13366 method 14. Implements ticket 6363.
13368 o Major features (build):
13369 - Switch to a nonrecursive Makefile structure. Now instead of each
13370 Makefile.am invoking other Makefile.am's, there is a master
13371 Makefile.am that includes the others. This change makes our build
13372 process slightly more maintainable, and improves parallelism for
13373 building with make -j. Original patch by Stewart Smith; various
13374 fixes by Jim Meyering.
13375 - Where available, we now use automake's "silent" make rules by
13376 default, so that warnings are easier to spot. You can get the old
13377 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
13379 o Minor features (code security and spec conformance):
13380 - Clear keys and key-derived material left on the stack in
13381 rendservice.c and rendclient.c. Check return value of
13382 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
13383 These fixes should make us more forward-secure against cold-boot
13384 attacks and the like. Fixes bug 2385.
13385 - Reject EXTEND cells sent to nonexistent streams. According to the
13386 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
13387 we were only checking for stream IDs that were currently in use.
13388 Found while hunting for more instances of bug 6271. Bugfix on
13389 0.0.2pre8, which introduced incremental circuit construction.
13391 o Minor features (streamlining);
13392 - No longer include the "opt" prefix when generating routerinfos
13393 or v2 directories: it has been needless since Tor 0.1.2. Closes
13395 - Remove some now-needless code that tried to aggressively flush
13396 OR connections as data was added to them. Since 0.2.0.1-alpha, our
13397 cell queue logic has saved us from the failure mode that this code
13398 was supposed to prevent. Removing this code will limit the number
13399 of baroque control flow paths through Tor's network logic. Reported
13400 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
13402 o Minor features (controller):
13403 - Add a "GETINFO signal/names" control port command. Implements
13405 - Provide default values for all options via "GETINFO config/defaults".
13406 Implements ticket 4971.
13408 o Minor features (IPv6):
13409 - New config option "AuthDirHasIPv6Connectivity 1" that directory
13410 authorities should set if they have IPv6 connectivity and want to
13411 do reachability tests for IPv6 relays. Implements feature 5974.
13412 - A relay with an IPv6 OR port now sends that address in NETINFO
13413 cells (in addition to its other address). Implements ticket 6364.
13415 o Minor features (log messages):
13416 - Omit the first heartbeat log message, because it never has anything
13417 useful to say, and it clutters up the bootstrapping messages.
13418 Resolves ticket 6758.
13419 - Don't log about reloading the microdescriptor cache at startup. Our
13420 bootstrap warnings are supposed to tell the user when there's a
13421 problem, and our bootstrap notices say when there isn't. Resolves
13422 ticket 6759; bugfix on 0.2.2.6-alpha.
13423 - Don't log "I learned some more directory information" when we're
13424 reading cached directory information. Reserve it for when new
13425 directory information arrives in response to a fetch. Resolves
13427 - Prevent rounding error in path bias counts when scaling
13428 them down, and use the correct scale factor default. Also demote
13429 some path bias related log messages down a level and make others
13430 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
13431 - We no longer warn so much when generating manpages from their
13434 o Code simplifications and refactoring:
13435 - Enhance our internal sscanf replacement so that we can eliminate
13436 the last remaining uses of the system sscanf. (Though those uses
13437 of sscanf were safe, sscanf itself is generally error prone, so
13438 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
13440 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
13441 - Move last_reachable and testing_since from routerinfo_t to node_t.
13442 Implements ticket 5529.
13443 - Add replaycache_t structure, functions and unit tests, then refactor
13444 rend_service_introduce() to be more clear to read, improve, debug,
13445 and test. Resolves bug 6177.
13446 - Finally remove support for malloc_good_size and malloc_usable_size.
13447 We had hoped that these functions would let us eke a little more
13448 memory out of our malloc implementation. Unfortunately, the only
13449 implementations that provided these functions are also ones that
13450 are already efficient about not overallocation: they never got us
13451 more than 7 or so bytes per allocation. Removing them saves us a
13452 little code complexity and a nontrivial amount of build complexity.
13454 o New requirements:
13455 - Tor maintainers now require Automake version 1.9 or later to build
13456 Tor from the Git repository. (Automake is not required when building
13457 from a source distribution.)
13460 Changes in version 0.2.3.21-rc - 2012-09-05
13461 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
13462 series. It fixes a trio of potential security bugs, fixes a bug where
13463 we were leaving some of the fast relays out of the microdescriptor
13464 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
13465 and cleans up other smaller issues.
13467 o Major bugfixes (security):
13468 - Tear down the circuit if we get an unexpected SENDME cell. Clients
13469 could use this trick to make their circuits receive cells faster
13470 than our flow control would have allowed, or to gum up the network,
13471 or possibly to do targeted memory denial-of-service attacks on
13472 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
13473 from July 2002, before the release of Tor 0.0.0. We had committed
13474 this patch previously, but we had to revert it because of bug 6271.
13475 Now that 6271 is fixed, this patch appears to work.
13476 - Reject any attempt to extend to an internal address. Without
13477 this fix, a router could be used to probe addresses on an internal
13478 network to see whether they were accepting connections. Fixes bug
13479 6710; bugfix on 0.0.8pre1.
13480 - Do not crash when comparing an address with port value 0 to an
13481 address policy. This bug could have been used to cause a remote
13482 assertion failure by or against directory authorities, or to
13483 allow some applications to crash clients. Fixes bug 6690; bugfix
13487 - Remove the upper bound on microdescriptor length. We were hitting
13488 the limit for routers with complex exit policies or family
13489 declarations, causing clients to not use them. Fixes the first
13490 piece of bug 6404; fix on 0.2.2.6-alpha.
13491 - Detect "ORPort 0" as meaning, uniformly, that we're not running
13492 as a relay. Previously, some of our code would treat the presence
13493 of any ORPort line as meaning that we should act like a relay,
13494 even though our new listener code would correctly not open any
13495 ORPorts for ORPort 0. Similar bugs in other Port options are also
13496 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
13499 - Avoid a pair of double-free and use-after-mark bugs that can
13500 occur with certain timings in canceled and re-received DNS
13501 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
13502 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
13503 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
13504 - Allow one-hop directory fetching circuits the full "circuit build
13505 timeout" period, rather than just half of it, before failing them
13506 and marking the relay down. This fix should help reduce cases where
13507 clients declare relays (or worse, bridges) unreachable because
13508 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
13509 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
13511 - Authorities no longer include any router in their microdescriptor
13512 consensuses for which they couldn't generate or agree on a
13513 microdescriptor. Fixes the second piece of bug 6404; fix on
13515 - Detect and reject attempts to specify both "FooPort" and
13516 "FooPort 0" in the same configuration domain. (It's still okay
13517 to have a FooPort in your configuration file, and use "FooPort 0"
13518 on the command line to disable it.) Fixes the second half of bug
13519 6507; bugfix on 0.2.3.3-alpha.
13520 - Make wildcarded addresses (that is, ones beginning with "*.") work
13521 when provided via the controller's MapAddress command. Previously,
13522 they were accepted, but we never actually noticed that they were
13523 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
13524 - Avoid crashing on a malformed state file where EntryGuardPathBias
13525 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
13526 - Add a (probably redundant) memory clear between iterations of
13527 the router status voting loop, to prevent future coding errors
13528 where data might leak between iterations of the loop. Resolves
13531 o Minor bugfixes (log messages):
13532 - Downgrade "set buildtimeout to low value" messages to "info"
13533 severity; they were never an actual problem, there was never
13534 anything reasonable to do about them, and they tended to spam logs
13535 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
13536 - Downgrade path-bias warning messages to "info". We'll try to get
13537 them working better in 0.2.4. Add internal circuit construction
13538 state to protect against the noisy warn message "Unexpectedly high
13539 circuit_successes". Also add some additional rate-limited notice
13540 messages to help determine the root cause of the warn. Fixes bug
13541 6475. Bugfix against 0.2.3.17-beta.
13542 - Move log message when unable to find a microdesc in a routerstatus
13543 entry to parse time. Previously we'd spam this warning every time
13544 we tried to figure out which microdescriptors to download. Fixes
13545 the third piece of bug 6404; fix on 0.2.3.18-rc.
13548 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
13549 change when the authority is deciding whether to accept a newly
13550 uploaded descriptor. Implements ticket 6423.
13551 - Add missing documentation for consensus and microdesc files.
13552 Resolves ticket 6732.
13555 Changes in version 0.2.2.38 - 2012-08-12
13556 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
13557 attack that could in theory leak path information.
13560 - Avoid an uninitialized memory read when reading a vote or consensus
13561 document that has an unrecognized flavor name. This read could
13562 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
13563 - Try to leak less information about what relays a client is
13564 choosing to a side-channel attacker. Previously, a Tor client would
13565 stop iterating through the list of available relays as soon as it
13566 had chosen one, thus finishing a little earlier when it picked
13567 a router earlier in the list. If an attacker can recover this
13568 timing information (nontrivial but not proven to be impossible),
13569 they could learn some coarse-grained information about which relays
13570 a client was picking (middle nodes in particular are likelier to
13571 be affected than exits). The timing attack might be mitigated by
13572 other factors (see bug 6537 for some discussion), but it's best
13573 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
13576 Changes in version 0.2.3.20-rc - 2012-08-05
13577 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
13578 series. It fixes a pair of code security bugs and a potential anonymity
13579 issue, updates our RPM spec files, and cleans up other smaller issues.
13582 - Avoid read-from-freed-memory and double-free bugs that could occur
13583 when a DNS request fails while launching it. Fixes bug 6480;
13584 bugfix on 0.2.0.1-alpha.
13585 - Avoid an uninitialized memory read when reading a vote or consensus
13586 document that has an unrecognized flavor name. This read could
13587 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
13588 - Try to leak less information about what relays a client is
13589 choosing to a side-channel attacker. Previously, a Tor client would
13590 stop iterating through the list of available relays as soon as it
13591 had chosen one, thus finishing a little earlier when it picked
13592 a router earlier in the list. If an attacker can recover this
13593 timing information (nontrivial but not proven to be impossible),
13594 they could learn some coarse-grained information about which relays
13595 a client was picking (middle nodes in particular are likelier to
13596 be affected than exits). The timing attack might be mitigated by
13597 other factors (see bug 6537 for some discussion), but it's best
13598 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
13601 - Try to make the warning when giving an obsolete SOCKSListenAddress
13602 a little more useful.
13603 - Terminate active server managed proxies if Tor stops being a
13604 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
13605 - Provide a better error message about possible OSX Asciidoc failure
13606 reasons. Fixes bug 6436.
13607 - Warn when Tor is configured to use accounting in a way that can
13608 link a hidden service to some other hidden service or public
13609 address. Resolves ticket 6490.
13612 - Check return value of fputs() when writing authority certificate
13613 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
13614 - Ignore ServerTransportPlugin lines when Tor is not configured as
13615 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
13616 - When disabling guards for having too high a proportion of failed
13617 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
13621 - Update our default RPM spec files to work with mock and rpmbuild
13622 on RHEL/Fedora. They have an updated set of dependencies and
13623 conflicts, a fix for an ancient typo when creating the "_tor"
13624 user, and better instructions. Thanks to Ondrej Mikle for the
13625 patch series. Fixes bug 6043.
13628 - Make it possible to set the TestingTorNetwork configuration
13629 option using AlternateDirAuthority and AlternateBridgeAuthority
13630 as an alternative to setting DirServer. Addresses ticket 6377.
13633 - Clarify the documentation for the Alternate*Authority options.
13635 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
13637 o Code simplification and refactoring:
13638 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
13639 10 lines. Also, don't nest them. Doing so in the past has
13640 led to hard-to-debug code. The new style is to use the
13641 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
13644 Changes in version 0.2.3.19-rc - 2012-07-06
13645 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
13646 series. It fixes the compile on Windows, reverts to a GeoIP database
13647 that isn't as broken, and fixes a flow control bug that has been around
13648 since the beginning of Tor.
13651 - Fix a bug handling SENDME cells on nonexistent streams that could
13652 result in bizarre window values. Report and patch contributed
13653 pseudonymously. Fixes part of bug 6271. This bug was introduced
13654 before the first Tor release, in svn commit r152.
13655 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
13656 June 2012 database, Maxmind marked many Tor relays as country "A1",
13657 which will cause risky behavior for clients that set EntryNodes
13658 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
13659 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
13660 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
13663 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
13664 bugfix on 0.2.1.10-alpha.
13667 Changes in version 0.2.3.18-rc - 2012-06-28
13668 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
13669 series. It fixes a few smaller bugs, but generally appears stable.
13670 Please test it and let us know whether it is!
13673 - Allow wildcarded mapaddress targets to be specified on the
13674 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
13675 - Make our linker option detection code more robust against linkers
13676 such as on FreeBSD 8, where a bad combination of options completes
13677 successfully but makes an unrunnable binary. Fixes bug 6173;
13678 bugfix on 0.2.3.17-beta.
13680 o Minor bugfixes (on 0.2.2.x and earlier):
13681 - Avoid a false positive in the util/threads unit test by increasing
13682 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
13683 - Replace "Sending publish request" log messages with "Launching
13684 upload", so that they no longer confusingly imply that we're
13685 sending something to a directory we might not even be connected
13686 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
13687 - Make sure to set *socket_error in all error cases in
13688 connection_connect(), so it can't produce a warning about
13689 errno being zero from errno_to_orconn_end_reason(). Bugfix on
13690 0.2.1.1-alpha; resolves ticket 6028.
13691 - Downgrade "Got a certificate, but we already have it" log messages
13692 from warning to info, except when we're a dirauth. Fixes bug 5238;
13693 bugfix on 0.2.1.7-alpha.
13694 - When checking for requested signatures on the latest consensus
13695 before serving it to a client, make sure to check the right
13696 consensus flavor. Bugfix on 0.2.2.6-alpha.
13697 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
13698 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
13700 o Minor bugfixes (on 0.2.3.x):
13701 - Make format_helper_exit_status() avoid unnecessary space padding
13702 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
13704 - Downgrade a message about cleaning the microdescriptor cache to
13705 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
13706 - Log a BUG message at severity INFO if we have a networkstatus with
13707 a missing entry for some microdescriptor. Continues on a patch
13709 - Improve the log message when a managed proxy fails to launch. Fixes
13710 bug 5099; bugfix on 0.2.3.6-alpha.
13711 - Don't do DNS lookups when parsing corrupted managed proxy protocol
13712 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
13713 - When formatting wildcarded address mappings for the controller,
13714 be sure to include "*." as appropriate. Partially fixes bug 6244;
13715 bugfix on 0.2.3.9-alpha.
13716 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
13717 Bugfix on 0.2.3.13-alpha.
13718 - Stop logging messages about running with circuit timeout learning
13719 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
13720 - Disable a spurious warning about reading on a marked and flushing
13721 connection. We shouldn't be doing that, but apparently we
13722 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
13723 - Fix a bug that stopped AllowDotExit from working on addresses
13724 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
13727 o Code simplification, refactoring, unit tests:
13728 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
13729 Libevent's notion of cached time when possible.
13730 - Remove duplicate code for invoking getrlimit() from control.c.
13731 - Add a unit test for the environment_variable_names_equal function.
13734 - Document the --defaults-torrc option, and the new (in 0.2.3)
13735 semantics for overriding, extending, and clearing lists of
13736 options. Closes bug 4748.
13739 Changes in version 0.2.3.17-beta - 2012-06-15
13740 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
13741 gets our TLS handshake back on track for being able to blend in with
13742 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
13743 with Vidalia, and otherwise continues to get us closer to a release
13747 - Enable gcc and ld hardening by default. Resolves ticket 5210.
13748 - Update TLS cipher list to match Firefox 8 and later. Resolves
13750 - Implement the client side of proposal 198: remove support for
13751 clients falsely claiming to support standard ciphersuites that
13752 they can actually provide. As of modern OpenSSL versions, it's not
13753 necessary to fake any standard ciphersuite, and doing so prevents
13754 us from using better ciphersuites in the future, since servers
13755 can't know whether an advertised ciphersuite is really supported or
13756 not. Some hosts -- notably, ones with very old versions of OpenSSL
13757 or where OpenSSL has been built with ECC disabled -- will stand
13758 out because of this change; TBB users should not be affected.
13761 - Change the default value for DynamicDHGroups (introduced in
13762 0.2.3.9-alpha) to 0. This feature can make Tor relays less
13763 identifiable by their use of the mod_ssl DH group, but at
13764 the cost of some usability (#4721) and bridge tracing (#6087)
13765 regressions. Resolves ticket 5598.
13766 - Send a CRLF at the end of each STATUS_* control protocol event. This
13767 bug tickled a bug in Vidalia which would make it freeze. Fixes
13768 bug 6094; bugfix on 0.2.3.16-alpha.
13771 - Disable writing on marked-for-close connections when they are
13772 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
13773 bug 5263; bugfix on 0.0.2pre13, where we first added a special
13774 case for flushing marked connections.
13775 - Detect SSL handshake even when the initial attempt to write the
13776 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
13777 - Change the AllowDotExit rules so they should actually work.
13778 We now enforce AllowDotExit only immediately after receiving an
13779 address via SOCKS or DNSPort: other sources are free to provide
13780 .exit addresses after the resolution occurs. Fixes bug 3940;
13781 bugfix on 0.2.2.1-alpha.
13782 - Fix a (harmless) integer overflow in cell statistics reported by
13783 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
13784 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
13785 right places and never depends on the consensus parameters or
13786 computes adaptive timeouts when it is disabled. Fixes bug 5049;
13787 bugfix on 0.2.2.14-alpha.
13788 - When building Tor on Windows with -DUNICODE (not default), ensure
13789 that error messages, filenames, and DNS server names are always
13790 NUL-terminated when we convert them to a single-byte encoding.
13791 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
13792 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
13793 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
13794 - Fix an edge case where TestingTorNetwork is set but the authorities
13795 and relays all have an uptime of zero, where the private Tor network
13796 could briefly lack support for hidden services. Fixes bug 3886;
13797 bugfix on 0.2.2.18-alpha.
13798 - Correct the manpage's descriptions for the default values of
13799 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
13801 - Fix the documentation for the --hush and --quiet command line
13802 options, which changed their behavior back in 0.2.3.3-alpha.
13803 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
13807 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
13808 more information to it, so that we can track it down in case it
13809 returns again. Mitigates bug 5235.
13810 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
13811 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
13812 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
13813 - Warn the user when HTTPProxy, but no other proxy type, is
13814 configured. This can cause surprising behavior: it doesn't send
13815 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
13816 directory traffic only. Resolves ticket 4663.
13817 - Issue a notice if a guard completes less than 40% of your circuits.
13818 Threshold is configurable by torrc option PathBiasNoticeRate and
13819 consensus parameter pb_noticepct. There is additional, off-by-
13820 default code to disable guards which fail too many circuits.
13821 Addresses ticket 5458.
13822 - Update to the June 6 2012 Maxmind GeoLite Country database.
13824 o Code simplifications and refactoring:
13825 - Remove validate_pluggable_transports_config(): its warning
13826 message is now handled by connection_or_connect().
13829 Changes in version 0.2.2.37 - 2012-06-06
13830 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
13831 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
13835 - Work around a bug in OpenSSL that broke renegotiation with TLS
13836 1.1 and TLS 1.2. Without this workaround, all attempts to speak
13837 the v2 Tor connection protocol when both sides were using OpenSSL
13838 1.0.1 would fail. Resolves ticket 6033.
13839 - When waiting for a client to renegotiate, don't allow it to add
13840 any bytes to the input buffer. This fixes a potential DoS issue.
13841 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
13842 - Fix an edge case where if we fetch or publish a hidden service
13843 descriptor, we might build a 4-hop circuit and then use that circuit
13844 for exiting afterwards -- even if the new last hop doesn't obey our
13845 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
13848 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13849 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13852 - Tell GCC and Clang to check for any errors in format strings passed
13853 to the tor_v*(print|scan)f functions.
13856 Changes in version 0.2.3.16-alpha - 2012-06-05
13857 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
13858 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
13859 currently). It also fixes a variety of smaller bugs and other cleanups
13860 that get us closer to a release candidate.
13862 o Major bugfixes (general):
13863 - Work around a bug in OpenSSL that broke renegotiation with TLS
13864 1.1 and TLS 1.2. Without this workaround, all attempts to speak
13865 the v2 Tor connection protocol when both sides were using OpenSSL
13866 1.0.1 would fail. Resolves ticket 6033.
13867 - When waiting for a client to renegotiate, don't allow it to add
13868 any bytes to the input buffer. This fixes a potential DoS issue.
13869 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
13870 - Pass correct OR address to managed proxies (like obfsproxy),
13871 even when ORListenAddress is used. Fixes bug 4865; bugfix on
13873 - The advertised platform of a router now includes only its operating
13874 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
13875 service pack level (for Windows) or its CPU architecture (for Unix).
13876 We also no longer include the "git-XYZ" tag in the version. Resolves
13879 o Major bugfixes (clients):
13880 - If we are unable to find any exit that supports our predicted ports,
13881 stop calling them predicted, so that we don't loop and build
13882 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
13883 which introduced predicted ports.
13884 - Fix an edge case where if we fetch or publish a hidden service
13885 descriptor, we might build a 4-hop circuit and then use that circuit
13886 for exiting afterwards -- even if the new last hop doesn't obey our
13887 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
13888 - Check at each new consensus whether our entry guards were picked
13889 long enough ago that we should rotate them. Previously, we only
13890 did this check at startup, which could lead to us holding a guard
13891 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
13892 - When fetching a bridge descriptor from a bridge authority,
13893 always do so anonymously, whether we have been able to open
13894 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
13895 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
13896 but we'll need to wait for bug 6010 before it's actually usable.
13898 o Major bugfixes (directory authorities):
13899 - When computing weight parameters, behave more robustly in the
13900 presence of a bad bwweightscale value. Previously, the authorities
13901 would crash if they agreed on a sufficiently broken weight_scale
13902 value: now, they use a reasonable default and carry on. Partial
13903 fix for 5786; bugfix on 0.2.2.17-alpha.
13904 - Check more thoroughly to prevent a rogue authority from
13905 double-voting on any consensus directory parameter. Previously,
13906 authorities would crash in this case if the total number of
13907 votes for any parameter exceeded the number of active voters,
13908 but would let it pass otherwise. Partial fix for bug 5786; bugfix
13912 - Rate-limit log messages when asked to connect anonymously to
13913 a private address. When these hit, they tended to hit fast and
13914 often. Also, don't bother trying to connect to addresses that we
13915 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
13916 reply makes us think we have been lied to, even when the address the
13917 client tried to connect to was "localhost." Resolves ticket 2822.
13918 - Allow packagers to insert an extra string in server descriptor
13919 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
13920 Resolves the rest of ticket 2988.
13921 - Raise the threshold of server descriptors needed (75%) and exit
13922 server descriptors needed (50%) before we will declare ourselves
13923 bootstrapped. This will make clients start building circuits a
13924 little later, but makes the initially constructed circuits less
13925 skewed and less in conflict with further directory fetches. Fixes
13927 - Close any connection that sends unrecognized junk before the
13928 handshake. Solves an issue noted in bug 4369.
13929 - Improve log messages about managed transports. Resolves ticket 5070.
13930 - Tag a bridge's descriptor as "never to be sent unencrypted".
13931 This shouldn't matter, since bridges don't open non-anonymous
13932 connections to the bridge authority and don't allow unencrypted
13933 directory connections from clients, but we might as well make
13934 sure. Closes bug 5139.
13935 - Expose our view of whether we have gone dormant to the controller,
13936 via a new "GETINFO dormant" value. Torbutton and other controllers
13937 can use this to avoid doing periodic requests through Tor while
13938 it's dormant (bug 4718). Fixes bug 5954.
13939 - Tell GCC and Clang to check for any errors in format strings passed
13940 to the tor_v*(print|scan)f functions.
13941 - Update to the May 1 2012 Maxmind GeoLite Country database.
13943 o Minor bugfixes (already included in 0.2.2.36):
13944 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
13945 Fixes bug 5346; bugfix on 0.0.8pre3.
13946 - Correct parsing of certain date types in parse_http_time().
13947 Without this patch, If-Modified-Since would behave
13948 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
13949 Esteban Manchado Velázques.
13950 - Make our number-parsing functions always treat too-large values
13951 as an error, even when those values exceed the width of the
13952 underlying type. Previously, if the caller provided these
13953 functions with minima or maxima set to the extreme values of the
13954 underlying integer type, these functions would return those
13955 values on overflow rather than treating overflow as an error.
13956 Fixes part of bug 5786; bugfix on 0.0.9.
13957 - If we hit the error case where routerlist_insert() replaces an
13958 existing (old) server descriptor, make sure to remove that
13959 server descriptor from the old_routers list. Fix related to bug
13960 1776. Bugfix on 0.2.2.18-alpha.
13961 - Clarify the behavior of MaxCircuitDirtiness with hidden service
13962 circuits. Fixes issue 5259.
13964 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
13965 - Prevent a null-pointer dereference when receiving a data cell
13966 for a nonexistent stream when the circuit in question has an
13967 empty deliver window. We don't believe this is triggerable,
13968 since we don't currently allow deliver windows to become empty,
13969 but the logic is tricky enough that it's better to make the code
13970 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
13971 - Fix a memory leak when trying to launch a DNS request when the
13972 network is disabled or the nameservers are unconfigurable. Fixes
13973 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
13974 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
13975 - Don't hold a Windows file handle open for every file mapping;
13976 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
13978 - Avoid O(n^2) performance characteristics when parsing a large
13979 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
13980 - Format more doubles with %f, not %lf. Patch from grarpamp to make
13981 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
13983 - Make our replacement implementation of strtok_r() compatible with
13984 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
13985 bugfix on 0.2.2.1-alpha.
13986 - Fix a NULL-pointer dereference on a badly formed
13987 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
13988 bugfix on 0.2.2.9-alpha.
13989 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
13990 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
13991 - Defensively refactor rend_mid_rendezvous() so that protocol
13992 violations and length checks happen in the beginning. Fixes
13994 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
13995 that IPv6 stuff will compile on MSVC, and compilation issues
13996 will be easier to track down. Fixes bug 5861.
13998 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
13999 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
14000 resource exhaustion, so that clients can adjust their load to
14001 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
14002 started using END_STREAM_REASON_RESOURCELIMIT.
14003 - Don't check for whether the address we're using for outbound
14004 connections has changed until after the outbound connection has
14005 completed. On Windows, getsockname() doesn't succeed until the
14006 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
14007 - If the configuration tries to set MyFamily on a bridge, refuse to
14008 do so, and warn about the security implications. Fixes bug 4657;
14009 bugfix on 0.2.0.3-alpha.
14010 - If the client fails to set a reasonable set of ciphersuites
14011 during its v2 handshake renegotiation, allow the renegotiation to
14012 continue nevertheless (i.e. send all the required certificates).
14013 Fixes bug 4591; bugfix on 0.2.0.20-rc.
14014 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
14015 option is set to 0 (which Vidalia version 0.2.16 now does when
14016 a SAVECONF attempt fails), perform other actions that SIGHUP
14017 usually causes (like reopening the logs). Fixes bug 5095; bugfix
14019 - If we fail to write a microdescriptor to the disk cache, do not
14020 continue replacing the old microdescriptor file. Fixes bug 2954;
14021 bugfix on 0.2.2.6-alpha.
14022 - Exit nodes don't need to fetch certificates for authorities that
14023 they don't recognize; only directory authorities, bridges,
14024 and caches need to do that. Fixes part of bug 2297; bugfix on
14026 - Correctly handle checking the permissions on the parent
14027 directory of a control socket in the root directory. Bug found
14028 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
14030 - When told to add a bridge with the same digest as a preexisting
14031 bridge but a different addr:port, change the addr:port as
14032 requested. Previously we would not notice the change. Fixes half
14033 of bug 5603; fix on 0.2.2.26-beta.
14034 - End AUTHCHALLENGE error messages (in the control protocol) with
14035 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
14037 o Minor bugfixes (on 0.2.3.x):
14038 - Turn an assertion (that the number of handshakes received as a
14039 server is not < 1) into a warning. Fixes bug 4873; bugfix on
14041 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
14042 we had reversed them when the answer was cached.) Fixes bug
14043 5723; bugfix on 0.2.3.1-alpha.
14044 - Work correctly on Linux systems with accept4 support advertised in
14045 their headers, but without accept4 support in the kernel. Fix
14046 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
14047 - When told to add a bridge with the same addr:port as a preexisting
14048 bridge but a different transport, change the transport as
14049 requested. Previously we would not notice the change. Fixes half
14050 of bug 5603; fix on 0.2.3.2-alpha.
14051 - Avoid a "double-reply" warning when replying to a SOCKS request
14052 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
14053 bugfix on 0.2.3.4-alpha.
14054 - Fix a bug where a bridge authority crashes if it has seen no
14055 directory requests when it's time to write statistics to disk.
14056 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
14058 - Don't try to open non-control listeners when DisableNetwork is set.
14059 Previously, we'd open all listeners, then immediately close them.
14060 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
14061 - Don't abort the managed proxy protocol if the managed proxy
14062 sends us an unrecognized line; ignore it instead. Fixes bug
14063 5910; bugfix on 0.2.3.9-alpha.
14064 - Fix a compile warning in crypto.c when compiling with clang 3.1.
14065 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
14066 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
14067 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
14068 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
14069 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
14070 - Resolve numerous small warnings and build issues with MSVC. Resolves
14073 o Documentation fixes:
14074 - Improve the manual's documentation for the NT Service command-line
14075 options. Addresses ticket 3964.
14076 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
14077 - Document the changes to the ORPort and DirPort options, and the
14078 fact that {OR/Dir}ListenAddress is now unnecessary (and
14079 therefore deprecated). Resolves ticket 5597.
14082 - Remove the torrc.bridge file: we don't use it for anything, and
14083 it had become badly desynchronized from torrc.sample. Resolves
14087 Changes in version 0.2.2.36 - 2012-05-24
14088 Tor 0.2.2.36 updates the addresses for two of the eight directory
14089 authorities, fixes some potential anonymity and security issues,
14090 and fixes several crash bugs.
14092 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
14093 known flaws, and nobody should be using them. You should upgrade. If
14094 you're using a Linux or BSD and its packages are obsolete, stop using
14095 those packages and upgrade anyway.
14097 o Directory authority changes:
14098 - Change IP address for maatuska (v3 directory authority).
14099 - Change IP address for ides (v3 directory authority), and rename
14103 - When building or running with any version of OpenSSL earlier
14104 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
14105 versions have a bug (CVE-2011-4576) in which their block cipher
14106 padding includes uninitialized data, potentially leaking sensitive
14107 information to any peer with whom they make a SSLv3 connection. Tor
14108 does not use SSL v3 by default, but a hostile client or server
14109 could force an SSLv3 connection in order to gain information that
14110 they shouldn't have been able to get. The best solution here is to
14111 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
14112 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
14113 to make sure that the bug can't happen.
14114 - Never use a bridge or a controller-supplied node as an exit, even
14115 if its exit policy allows it. Found by wanoskarnet. Fixes bug
14116 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
14117 and 0.2.0.3-alpha (for bridge-purpose descriptors).
14118 - Only build circuits if we have a sufficient threshold of the total
14119 descriptors that are marked in the consensus with the "Exit"
14120 flag. This mitigates an attack proposed by wanoskarnet, in which
14121 all of a client's bridges collude to restrict the exit nodes that
14122 the client knows about. Fixes bug 5343.
14123 - Provide controllers with a safer way to implement the cookie
14124 authentication mechanism. With the old method, if another locally
14125 running program could convince a controller that it was the Tor
14126 process, then that program could trick the controller into telling
14127 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
14128 authentication method uses a challenge-response approach to prevent
14129 this attack. Fixes bug 5185; implements proposal 193.
14132 - Avoid logging uninitialized data when unable to decode a hidden
14133 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
14134 - Avoid a client-side assertion failure when receiving an INTRODUCE2
14135 cell on a general purpose circuit. Fixes bug 5644; bugfix on
14137 - Fix builds when the path to sed, openssl, or sha1sum contains
14138 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
14140 - Correct our replacements for the timeradd() and timersub() functions
14141 on platforms that lack them (for example, Windows). The timersub()
14142 function is used when expiring circuits, while timeradd() is
14143 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
14144 bugfix on 0.2.2.24-alpha.
14145 - Fix the SOCKET_OK test that we use to tell when socket
14146 creation fails so that it works on Win64. Fixes part of bug 4533;
14147 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
14150 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
14151 Fixes bug 5346; bugfix on 0.0.8pre3.
14152 - Make our number-parsing functions always treat too-large values
14153 as an error, even when those values exceed the width of the
14154 underlying type. Previously, if the caller provided these
14155 functions with minima or maxima set to the extreme values of the
14156 underlying integer type, these functions would return those
14157 values on overflow rather than treating overflow as an error.
14158 Fixes part of bug 5786; bugfix on 0.0.9.
14159 - Older Linux kernels erroneously respond to strange nmap behavior
14160 by having accept() return successfully with a zero-length
14161 socket. When this happens, just close the connection. Previously,
14162 we would try harder to learn the remote address: but there was
14163 no such remote address to learn, and our method for trying to
14164 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
14165 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
14166 - Correct parsing of certain date types in parse_http_time().
14167 Without this patch, If-Modified-Since would behave
14168 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
14169 Esteban Manchado Velázques.
14170 - Change the BridgePassword feature (part of the "bridge community"
14171 design, which is not yet implemented) to use a time-independent
14172 comparison. The old behavior might have allowed an adversary
14173 to use timing to guess the BridgePassword value. Fixes bug 5543;
14174 bugfix on 0.2.0.14-alpha.
14175 - Detect and reject certain misformed escape sequences in
14176 configuration values. Previously, these values would cause us
14177 to crash if received in a torrc file or over an authenticated
14178 control port. Bug found by Esteban Manchado Velázquez, and
14179 independently by Robert Connolly from Matta Consulting who further
14180 noted that it allows a post-authentication heap overflow. Patch
14181 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
14182 bugfix on 0.2.0.16-alpha.
14183 - Fix a compile warning when using the --enable-openbsd-malloc
14184 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
14185 - During configure, detect when we're building with clang version
14186 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
14187 CFLAGS. clang doesn't support them yet.
14188 - When sending an HTTP/1.1 proxy request, include a Host header.
14189 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
14190 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
14191 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
14192 - If we hit the error case where routerlist_insert() replaces an
14193 existing (old) server descriptor, make sure to remove that
14194 server descriptor from the old_routers list. Fix related to bug
14195 1776. Bugfix on 0.2.2.18-alpha.
14197 o Minor bugfixes (documentation and log messages):
14198 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
14199 Fixes bug 4856; bugfix on Tor 0.0.6.
14200 - Update "ClientOnly" man page entry to explain that there isn't
14201 really any point to messing with it. Resolves ticket 5005.
14202 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
14203 directory authority option (introduced in Tor 0.2.2.34).
14204 - Downgrade the "We're missing a certificate" message from notice
14205 to info: people kept mistaking it for a real problem, whereas it
14206 is seldom the problem even when we are failing to bootstrap. Fixes
14207 bug 5067; bugfix on 0.2.0.10-alpha.
14208 - Correctly spell "connect" in a log message on failure to create a
14209 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
14210 - Clarify the behavior of MaxCircuitDirtiness with hidden service
14211 circuits. Fixes issue 5259.
14214 - Directory authorities now reject versions of Tor older than
14215 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
14216 inclusive. These versions accounted for only a small fraction of
14217 the Tor network, and have numerous known security issues. Resolves
14219 - Update to the May 1 2012 Maxmind GeoLite Country database.
14222 - When sending or relaying a RELAY_EARLY cell, we used to convert
14223 it to a RELAY cell if the connection was using the v1 link
14224 protocol. This was a workaround for older versions of Tor, which
14225 didn't handle RELAY_EARLY cells properly. Now that all supported
14226 versions can handle RELAY_EARLY cells, and now that we're enforcing
14227 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
14228 remove this workaround. Addresses bug 4786.
14231 Changes in version 0.2.3.15-alpha - 2012-04-30
14232 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
14233 the development branch build on Windows again.
14235 o Minor bugfixes (on 0.2.2.x and earlier):
14236 - Make sure that there are no unhandled pending TLS errors before
14237 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
14238 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
14239 Bugfix on 0.1.0.5-rc; fixes bug 4528.
14240 - Fix an assert that directory authorities could trigger on sighup
14241 during some configuration state transitions. We now don't treat
14242 it as a fatal error when the new descriptor we just generated in
14243 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
14244 - After we pick a directory mirror, we would refuse to use it if
14245 it's in our ExcludeExitNodes list, resulting in mysterious failures
14246 to bootstrap for people who just wanted to avoid exiting from
14247 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
14248 - When building with --enable-static-tor on OpenBSD, do not
14249 erroneously attempt to link -lrt. Fixes bug 5103.
14251 o Minor bugfixes (on 0.2.3.x):
14252 - When Tor is built with kernel headers from a recent (last few
14253 years) Linux kernel, do not fail to run on older (pre-2.6.28
14254 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
14255 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
14256 and 0.2.3.12-alpha.
14257 - Fix compilation with miniupnpc version 1.6; patch from
14258 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
14259 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
14260 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
14261 - Fix compilation on platforms without unistd.h, or where environ
14262 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
14265 - Directory authorities are now a little more lenient at accepting
14266 older router descriptors, or newer router descriptors that don't
14267 make big changes. This should help ameliorate past and future
14268 issues where routers think they have uploaded valid descriptors,
14269 but the authorities don't think so. Fix for ticket 2479.
14270 - Make the code that clients use to detect an address change be
14271 IPv6-aware, so that it won't fill clients' logs with error
14272 messages when trying to get the IPv4 address of an IPv6
14273 connection. Implements ticket 5537.
14275 o Removed features:
14276 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
14277 authorities needed to use it for a while to keep the network working
14278 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
14279 that was six months ago. As of now, it should no longer be needed
14283 Changes in version 0.2.3.14-alpha - 2012-04-23
14284 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
14285 candidate. It also dramatically speeds up AES: fast relays should
14286 consider switching to the newer OpenSSL library.
14288 o Directory authority changes:
14289 - Change IP address for ides (v3 directory authority), and rename
14293 - Avoid logging uninitialized data when unable to decode a hidden
14294 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
14295 - Avoid a client-side assertion failure when receiving an INTRODUCE2
14296 cell on a general purpose circuit. Fixes bug 5644; bugfix on
14298 - If authorities are unable to get a v2 consensus document from other
14299 directory authorities, they no longer fall back to fetching
14300 them from regular directory caches. Fixes bug 5635; bugfix on
14301 0.2.2.26-beta, where routers stopped downloading v2 consensus
14302 documents entirely.
14303 - When we start a Tor client with a normal consensus already cached,
14304 be willing to download a microdescriptor consensus. Fixes bug 4011;
14305 fix on 0.2.3.1-alpha.
14307 o Major features (performance):
14308 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
14309 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
14310 vectorized AES implementations as appropriate. These can be much,
14311 much faster than other AES implementations.
14313 o Minor bugfixes (0.2.2.x and earlier):
14314 - Don't launch more than 10 service-side introduction-point circuits
14315 for a hidden service in five minutes. Previously, we would consider
14316 launching more introduction-point circuits if at least one second
14317 had passed without any introduction-point circuits failing. Fixes
14318 bug 4607; bugfix on 0.0.7pre1.
14319 - Change the BridgePassword feature (part of the "bridge community"
14320 design, which is not yet implemented) to use a time-independent
14321 comparison. The old behavior might have allowed an adversary
14322 to use timing to guess the BridgePassword value. Fixes bug 5543;
14323 bugfix on 0.2.0.14-alpha.
14324 - Enforce correct return behavior of tor_vsscanf() when the '%%'
14325 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
14326 - When sending an HTTP/1.1 proxy request, include a Host header.
14327 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
14328 - Don't log that we have "decided to publish new relay descriptor"
14329 unless we are actually publishing a descriptor. Fixes bug 3942;
14330 bugfix on 0.2.2.28-beta.
14332 o Minor bugfixes (0.2.3.x):
14333 - Fix a bug where a bridge authority crashes (on a failed assert)
14334 if it has seen no directory requests when it's time to write
14335 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
14336 - Fix bug stomping on ORPort option NoListen and ignoring option
14337 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
14338 - In the testsuite, provide a large enough buffer in the tor_sscanf
14339 unit test. Otherwise we'd overrun that buffer and crash during
14340 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
14342 - Make sure we create the keys directory if it doesn't exist and we're
14343 about to store the dynamic Diffie-Hellman parameters. Fixes bug
14344 5572; bugfix on 0.2.3.13-alpha.
14345 - Fix a small memory leak when trying to decode incorrect base16
14346 authenticator during SAFECOOKIE authentication. Found by
14347 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
14350 - Add more information to a log statement that might help track down
14351 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
14352 non-IP address" messages (or any Bug messages, for that matter!),
14353 please let us know about it.
14354 - Relays now understand an IPv6 address when they get one from a
14355 directory server. Resolves ticket 4875.
14356 - Resolve IPv6 addresses in bridge and entry statistics to country
14357 code "??" which means we at least count them. Resolves ticket 5053;
14358 improves on 0.2.3.9-alpha.
14359 - Update to the April 3 2012 Maxmind GeoLite Country database.
14360 - Begin a doc/state-contents.txt file to explain the contents of
14361 the Tor state file. Fixes bug 2987.
14363 o Default torrc changes:
14364 - Stop listing "socksport 9050" in torrc.sample. We open a socks
14365 port on 9050 by default anyway, so this should not change anything
14367 - Stop mentioning the deprecated *ListenAddress options in
14368 torrc.sample. Fixes bug 5438.
14369 - Document unit of bandwidth related options in sample torrc.
14372 o Removed features:
14373 - The "torify" script no longer supports the "tsocks" socksifier
14374 tool, since tsocks doesn't support DNS and UDP right for Tor.
14375 Everyone should be using torsocks instead. Fixes bugs 3530 and
14376 5180. Based on a patch by "ugh".
14378 o Code refactoring:
14379 - Change the symmetric cipher interface so that creating and
14380 initializing a stream cipher are no longer separate functions.
14381 - Remove all internal support for unpadded RSA. We never used it, and
14382 it would be a bad idea to start.
14385 Changes in version 0.2.3.13-alpha - 2012-03-26
14386 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
14387 in managed pluggable transports, as well as providing other cleanups
14388 that get us closer to a release candidate.
14390 o Directory authority changes:
14391 - Change IP address for maatuska (v3 directory authority).
14394 - Provide controllers with a safer way to implement the cookie
14395 authentication mechanism. With the old method, if another locally
14396 running program could convince a controller that it was the Tor
14397 process, then that program could trick the controller into telling
14398 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
14399 authentication method uses a challenge-response approach to prevent
14400 this attack. Fixes bug 5185, implements proposal 193.
14401 - Never use a bridge or a controller-supplied node as an exit, even
14402 if its exit policy allows it. Found by wanoskarnet. Fixes bug
14403 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
14404 and 0.2.0.3-alpha (for bridge-purpose descriptors).
14405 - Only build circuits if we have a sufficient threshold of the total
14406 descriptors that are marked in the consensus with the "Exit"
14407 flag. This mitigates an attack proposed by wanoskarnet, in which
14408 all of a client's bridges collude to restrict the exit nodes that
14409 the client knows about. Fixes bug 5343.
14411 o Major bugfixes (on Tor 0.2.3.x):
14412 - Avoid an assert when managed proxies like obfsproxy are configured,
14413 and we receive HUP signals or setconf attempts too rapidly. This
14414 situation happens most commonly when Vidalia tries to attach to
14415 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
14416 bugfix on 0.2.3.6-alpha.
14417 - Fix a relay-side pluggable transports bug where managed proxies were
14418 unreachable from the Internet, because Tor asked them to bind on
14419 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
14420 - Stop discarding command-line arguments when TestingTorNetwork
14421 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
14422 0.2.3.9-alpha, where task 4552 added support for two layers of
14424 - Resume allowing the unit tests to run in gdb. This was accidentally
14425 made impossible when the DisableDebuggerAttachment option was
14426 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
14427 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
14428 0.2.3.11-alpha. Reported by Anthony G. Basile.
14430 o Minor bugfixes (on 0.2.2.x and earlier):
14431 - Ensure we don't cannibalize circuits that are longer than three hops
14432 already, so we don't end up making circuits with 5 or more
14433 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
14434 0.1.0.1-rc which introduced cannibalization.
14435 - Detect and reject certain misformed escape sequences in
14436 configuration values. Previously, these values would cause us
14437 to crash if received in a torrc file or over an authenticated
14438 control port. Bug found by Esteban Manchado Velázquez, and
14439 independently by Robert Connolly from Matta Consulting who further
14440 noted that it allows a post-authentication heap overflow. Patch
14441 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
14442 bugfix on 0.2.0.16-alpha.
14443 - Fix a compile warning when using the --enable-openbsd-malloc
14444 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
14445 - Directory caches no longer refuse to clean out descriptors because
14446 of missing v2 networkstatus documents, unless they're configured
14447 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
14448 0.2.2.26-beta. Patch by Daniel Bryg.
14449 - Update to the latest version of the tinytest unit testing framework.
14450 This includes a couple of bugfixes that can be relevant for
14451 running forked unit tests on Windows, and removes all reserved
14454 o Minor bugfixes (on 0.2.3.x):
14455 - On a failed pipe() call, don't leak file descriptors. Fixes bug
14456 4296; bugfix on 0.2.3.1-alpha.
14457 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
14458 until after we have received a CERTS cell. Fixes bug 4361; bugfix
14459 on 0.2.3.6-alpha. Patch by "frosty".
14460 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
14461 option, so that the IP stack doesn't decide to use it for IPv4
14462 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
14463 - Ensure that variables set in Tor's environment cannot override
14464 environment variables that Tor passes to a managed
14465 pluggable-transport proxy. Previously, Tor would pass every
14466 variable in its environment to managed proxies along with the new
14467 ones, in such a way that on many operating systems, the inherited
14468 environment variables would override those which Tor tried to
14469 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
14470 bugfix on 0.2.3.9-alpha for Windows.
14473 - A wide variety of new unit tests by Esteban Manchado Velázquez.
14474 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
14475 - Update to the March 6 2012 Maxmind GeoLite Country database.
14478 Changes in version 0.2.3.12-alpha - 2012-02-13
14479 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
14480 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
14481 when Tor is configured to use a pluggable transport like obfsproxy.
14484 - Fix builds when the path to sed, openssl, or sha1sum contains
14485 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
14487 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
14488 connections. This change should allow busy exit relays to stop
14489 running out of available sockets as quickly. Fixes bug 4950;
14490 bugfix on 0.2.2.26-beta.
14491 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
14492 would ask the bridge for microdescriptors, which are only supported
14493 in 0.2.3.x, and then fail to bootstrap when it didn't get the
14494 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
14495 - Properly set up obfsproxy's environment when in managed mode. The
14496 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
14497 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
14498 5076 and 5082; bugfix on 0.2.3.6-alpha.
14501 - Use the dead_strip option when building Tor on OS X. This reduces
14502 binary size by almost 19% when linking openssl and libevent
14503 statically, which we do for Tor Browser Bundle.
14504 - Fix broken URLs in the sample torrc file, and tell readers about
14505 the OutboundBindAddress, ExitPolicyRejectPrivate, and
14506 PublishServerDescriptor options. Addresses bug 4652.
14507 - Update to the February 7 2012 Maxmind GeoLite Country database.
14510 - Downgrade the "We're missing a certificate" message from notice
14511 to info: people kept mistaking it for a real problem, whereas it
14512 is seldom the problem even when we are failing to bootstrap. Fixes
14513 bug 5067; bugfix on 0.2.0.10-alpha.
14514 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
14515 managed pluggable transport server proxy's environment.
14516 Previously, we would put it there, even though Tor doesn't
14517 implement an 'extended server port' yet, and even though Tor
14518 almost certainly isn't listening at that address. For now, we set
14519 it to an empty string to avoid crashing older obfsproxies. Bugfix
14521 - Log the heartbeat message every HeartbeatPeriod seconds, not every
14522 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
14523 0.2.3.1-alpha. Bug reported by Scott Bennett.
14524 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
14525 bugfix on 0.2.3.11-alpha.
14526 - Update "ClientOnly" man page entry to explain that there isn't
14527 really any point to messing with it. Resolves ticket 5005.
14528 - Use the correct CVE number for CVE-2011-4576 in our comments and
14529 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
14532 o Code simplifications and refactoring:
14533 - Use the _WIN32 macro throughout our code to detect Windows.
14534 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
14538 Changes in version 0.2.3.11-alpha - 2012-01-22
14539 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
14540 the last step of the plan to limit maximum circuit length, includes
14541 a wide variety of hidden service performance and correctness fixes,
14542 works around an OpenSSL security flaw if your distro is too stubborn
14543 to upgrade, and fixes a bunch of smaller issues.
14546 - Now that Tor 0.2.0.x is completely deprecated, enable the final
14547 part of "Proposal 110: Avoiding infinite length circuits" by
14548 refusing all circuit-extend requests that do not use a relay_early
14549 cell. This change helps Tor resist a class of denial-of-service
14550 attacks by limiting the maximum circuit length.
14551 - Adjust the number of introduction points that a hidden service
14552 will try to maintain based on how long its introduction points
14553 remain in use and how many introductions they handle. Fixes
14555 - Try to use system facilities for enumerating local interface
14556 addresses, before falling back to our old approach (which was
14557 binding a UDP socket, and calling getsockname() on it). That
14558 approach was scaring OS X users whose draconian firewall
14559 software warned about binding to UDP sockets, regardless of
14560 whether packets were sent. Now we try to use getifaddrs(),
14561 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
14562 system supports. Resolves ticket 1827.
14564 o Major security workaround:
14565 - When building or running with any version of OpenSSL earlier
14566 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
14567 versions have a bug (CVE-2011-4576) in which their block cipher
14568 padding includes uninitialized data, potentially leaking sensitive
14569 information to any peer with whom they make a SSLv3 connection. Tor
14570 does not use SSL v3 by default, but a hostile client or server
14571 could force an SSLv3 connection in order to gain information that
14572 they shouldn't have been able to get. The best solution here is to
14573 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
14574 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
14575 to make sure that the bug can't happen.
14578 - Fix the SOCKET_OK test that we use to tell when socket
14579 creation fails so that it works on Win64. Fixes part of bug 4533;
14580 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
14581 - Correct our replacements for the timeradd() and timersub() functions
14582 on platforms that lack them (for example, Windows). The timersub()
14583 function is used when expiring circuits, while timeradd() is
14584 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
14585 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
14586 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
14587 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
14588 bug at runtime, not compile time, because some distributions hack
14589 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
14590 on 0.2.3.9-alpha. Found by Pascal.
14592 o Minor features (controller):
14593 - Use absolute path names when reporting the torrc filename in the
14594 control protocol, so a controller can more easily find the torrc
14595 file. Resolves bug 1101.
14596 - Extend the control protocol to report flags that control a circuit's
14597 path selection in CIRC events and in replies to 'GETINFO
14598 circuit-status'. Implements part of ticket 2411.
14599 - Extend the control protocol to report the hidden service address
14600 and current state of a hidden-service-related circuit in CIRC
14601 events and in replies to 'GETINFO circuit-status'. Implements part
14603 - When reporting the path to the cookie file to the controller,
14604 give an absolute path. Resolves ticket 4881.
14605 - Allow controllers to request an event notification whenever a
14606 circuit is cannibalized or its purpose is changed. Implements
14607 part of ticket 3457.
14608 - Include the creation time of a circuit in CIRC and CIRC2
14609 control-port events and the list produced by the 'GETINFO
14610 circuit-status' control-port command.
14612 o Minor features (directory authorities):
14613 - Directory authorities now reject versions of Tor older than
14614 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
14615 inclusive. These versions accounted for only a small fraction of
14616 the Tor network, and have numerous known security issues. Resolves
14618 - Authority operators can now vote for all relays in a given
14619 set of countries to be BadDir/BadExit/Invalid/Rejected.
14620 - Provide two consensus parameters (FastFlagMinThreshold and
14621 FastFlagMaxThreshold) to control the range of allowable bandwidths
14622 for the Fast directory flag. These allow authorities to run
14623 experiments on appropriate requirements for being a "Fast" node.
14624 The AuthDirFastGuarantee config value still applies. Implements
14626 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
14627 directory authority option (introduced in Tor 0.2.2.34).
14629 o Minor features (other):
14630 - Don't disable the DirPort when we cannot exceed our AccountingMax
14631 limit during this interval because the effective bandwidthrate is
14632 low enough. This is useful in a situation where AccountMax is only
14633 used as an additional safeguard or to provide statistics.
14634 - Prepend an informative header to generated dynamic_dh_params files.
14635 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
14636 EntryNodes will have no effect. Resolves issue 2571.
14637 - Log more useful messages when we fail to disable debugger
14639 - Log which authority we're missing votes from when we go to fetch
14640 them from the other auths.
14641 - Log (at debug level) whenever a circuit's purpose is changed.
14642 - Add missing documentation for the MaxClientCircuitsPending,
14643 UseMicrodescriptors, UserspaceIOCPBuffers, and
14644 _UseFilteringSSLBufferevents options, all introduced during
14645 the 0.2.3.x series.
14646 - Update to the January 3 2012 Maxmind GeoLite Country database.
14648 o Minor bugfixes (hidden services):
14649 - Don't close hidden service client circuits which have almost
14650 finished connecting to their destination when they reach
14651 the normal circuit-build timeout. Previously, we would close
14652 introduction circuits which are waiting for an acknowledgement
14653 from the introduction point, and rendezvous circuits which have
14654 been specified in an INTRODUCE1 cell sent to a hidden service,
14655 after the normal CBT. Now, we mark them as 'timed out', and launch
14656 another rendezvous attempt in parallel. This behavior change can
14657 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
14658 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
14659 - Don't close hidden-service-side rendezvous circuits when they
14660 reach the normal circuit-build timeout. This behavior change can
14661 be disabled using the new
14662 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
14663 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
14664 - Make sure we never mark the wrong rendezvous circuit as having
14665 had its introduction cell acknowledged by the introduction-point
14666 relay. Previously, when we received an INTRODUCE_ACK cell on a
14667 client-side hidden-service introduction circuit, we might have
14668 marked a rendezvous circuit other than the one we specified in
14669 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
14670 a warning message and interfered with the hidden service
14671 connection-establishment process. Fixes bug 4759; bugfix on
14672 0.2.3.3-alpha, when we added the stream-isolation feature which
14673 might cause Tor to open multiple rendezvous circuits for the same
14675 - Don't trigger an assertion failure when we mark a new client-side
14676 hidden-service introduction circuit for close during the process
14677 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
14680 o Minor bugfixes (log messages):
14681 - Correctly spell "connect" in a log message on failure to create a
14682 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
14684 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
14685 Fixes bug 4856; bugfix on Tor 0.0.6.
14686 - Fix the log message describing how we work around discovering
14687 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
14688 4837; bugfix on 0.2.2.9-alpha.
14689 - When logging about a disallowed .exit name, do not also call it
14690 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
14692 o Minor bugfixes (build fixes):
14693 - During configure, detect when we're building with clang version
14694 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
14695 CFLAGS. clang doesn't support them yet.
14696 - During configure, search for library containing cos function as
14697 libm lives in libcore on some platforms (BeOS/Haiku). Linking
14698 against libm was hard-coded before. Fixes the first part of bug
14699 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
14701 - Detect attempts to build Tor on (as yet hypothetical) versions
14702 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
14703 fix for bug 4533. Bugfix on 0.2.2.28-beta.
14704 - Preprocessor directives should not be put inside the arguments
14705 of a macro. This would break compilation with GCC releases prior
14706 to version 3.3. We would never recommend such an old GCC version,
14707 but it is apparently required for binary compatibility on some
14708 platforms (namely, certain builds of Haiku). Fixes the other part
14709 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
14712 o Minor bugfixes (other):
14713 - Older Linux kernels erroneously respond to strange nmap behavior
14714 by having accept() return successfully with a zero-length
14715 socket. When this happens, just close the connection. Previously,
14716 we would try harder to learn the remote address: but there was
14717 no such remote address to learn, and our method for trying to
14718 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
14719 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
14720 - Fix null-pointer access that could occur if TLS allocation failed.
14721 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
14722 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
14723 accidentally been reverted.
14724 - Fix our implementation of crypto_random_hostname() so it can't
14725 overflow on ridiculously large inputs. (No Tor version has ever
14726 provided this kind of bad inputs, but let's be correct in depth.)
14727 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
14728 - Find more places in the code that should have been testing for
14729 invalid sockets using the SOCKET_OK macro. Required for a fix
14730 for bug 4533. Bugfix on 0.2.2.28-beta.
14731 - Fix an assertion failure when, while running with bufferevents, a
14732 connection finishes connecting after it is marked for close, but
14733 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
14734 - test_util_spawn_background_ok() hardcoded the expected value
14735 for ENOENT to 2. This isn't portable as error numbers are
14736 platform specific, and particularly the hurd has ENOENT at
14737 0x40000002. Construct expected string at runtime, using the correct
14738 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
14739 - Reject attempts to disable DisableDebuggerAttachment while Tor is
14740 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
14741 - Use an appropriate-width type for sockets in tor-fw-helper on
14742 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
14745 - When sending or relaying a RELAY_EARLY cell, we used to convert
14746 it to a RELAY cell if the connection was using the v1 link
14747 protocol. This was a workaround for older versions of Tor, which
14748 didn't handle RELAY_EARLY cells properly. Now that all supported
14749 versions can handle RELAY_EARLY cells, and now that we're enforcing
14750 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
14751 remove this workaround. Addresses bug 4786.
14753 o Code simplifications and refactoring:
14754 - Use OpenSSL's built-in SSL_state_string_long() instead of our
14755 own homebrewed ssl_state_to_string() replacement. Patch from
14756 Emile Snyder. Fixes bug 4653.
14757 - Use macros to indicate OpenSSL versions, so we don't need to worry
14758 about accidental hexadecimal bit shifts.
14759 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
14761 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
14762 - Use the smartlist_add_asprintf() alias more consistently.
14763 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
14764 invalid value, rather than just -1.
14765 - Rename a handful of old identifiers, mostly related to crypto
14766 structures and crypto functions. By convention, our "create an
14767 object" functions are called "type_new()", our "free an object"
14768 functions are called "type_free()", and our types indicate that
14769 they are types only with a final "_t". But a handful of older
14770 types and functions broke these rules, with function names like
14771 "type_create" or "subsystem_op_type", or with type names like
14775 Changes in version 0.2.3.10-alpha - 2011-12-16
14776 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
14777 Tor's buffers code. Absolutely everybody should upgrade.
14779 The bug relied on an incorrect calculation when making data continuous
14780 in one of our IO buffers, if the first chunk of the buffer was
14781 misaligned by just the wrong amount. The miscalculation would allow an
14782 attacker to overflow a piece of heap-allocated memory. To mount this
14783 attack, the attacker would need to either open a SOCKS connection to
14784 Tor's SocksPort (usually restricted to localhost), or target a Tor
14785 instance configured to make its connections through a SOCKS proxy
14786 (which Tor does not do by default).
14788 Good security practice requires that all heap-overflow bugs should be
14789 presumed to be exploitable until proven otherwise, so we are treating
14790 this as a potential code execution attack. Please upgrade immediately!
14791 This bug does not affect bufferevents-based builds of Tor. Special
14792 thanks to "Vektor" for reporting this issue to us!
14794 This release also contains a few minor bugfixes for issues discovered
14798 - Fix a heap overflow bug that could occur when trying to pull
14799 data into the first chunk of a buffer, when that chunk had
14800 already had some data drained from it. Fixes CVE-2011-2778;
14801 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14804 - If we can't attach streams to a rendezvous circuit when we
14805 finish connecting to a hidden service, clear the rendezvous
14806 circuit's stream-isolation state and try to attach streams
14807 again. Previously, we cleared rendezvous circuits' isolation
14808 state either too early (if they were freshly built) or not at all
14809 (if they had been built earlier and were cannibalized). Bugfix on
14810 0.2.3.3-alpha; fixes bug 4655.
14811 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
14812 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
14813 - Fix an assertion failure when a relay with accounting enabled
14814 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
14817 - Update to the December 6 2011 Maxmind GeoLite Country database.
14820 Changes in version 0.2.2.35 - 2011-12-16
14821 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
14822 buffers code. Absolutely everybody should upgrade.
14824 The bug relied on an incorrect calculation when making data continuous
14825 in one of our IO buffers, if the first chunk of the buffer was
14826 misaligned by just the wrong amount. The miscalculation would allow an
14827 attacker to overflow a piece of heap-allocated memory. To mount this
14828 attack, the attacker would need to either open a SOCKS connection to
14829 Tor's SocksPort (usually restricted to localhost), or target a Tor
14830 instance configured to make its connections through a SOCKS proxy
14831 (which Tor does not do by default).
14833 Good security practice requires that all heap-overflow bugs should be
14834 presumed to be exploitable until proven otherwise, so we are treating
14835 this as a potential code execution attack. Please upgrade immediately!
14836 This bug does not affect bufferevents-based builds of Tor. Special
14837 thanks to "Vektor" for reporting this issue to us!
14839 Tor 0.2.2.35 also fixes several bugs in previous versions, including
14840 crash bugs for unusual configurations, and a long-term bug that
14841 would prevent Tor from starting on Windows machines with draconian
14844 With this release, we remind everyone that 0.2.0.x has reached its
14845 formal end-of-life. Those Tor versions have many known flaws, and
14846 nobody should be using them. You should upgrade -- ideally to the
14847 0.2.2.x series. If you're using a Linux or BSD and its packages are
14848 obsolete, stop using those packages and upgrade anyway.
14850 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
14851 longer receive support after some time in early 2012.
14854 - Fix a heap overflow bug that could occur when trying to pull
14855 data into the first chunk of a buffer, when that chunk had
14856 already had some data drained from it. Fixes CVE-2011-2778;
14857 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14858 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
14859 that it doesn't attempt to allocate a socketpair. This could cause
14860 some problems on Windows systems with overzealous firewalls. Fix for
14861 bug 4457; workaround for Libevent versions 2.0.1-alpha through
14863 - If we mark an OR connection for close based on a cell we process,
14864 don't process any further cells on it. We already avoid further
14865 reads on marked-for-close connections, but now we also discard the
14866 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
14867 which was the first version where we might mark a connection for
14868 close based on processing a cell on it.
14869 - Correctly sanity-check that we don't underflow on a memory
14870 allocation (and then assert) for hidden service introduction
14871 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14872 bugfix on 0.2.1.5-alpha.
14873 - Fix a memory leak when we check whether a hidden service
14874 descriptor has any usable introduction points left. Fixes bug
14875 4424. Bugfix on 0.2.2.25-alpha.
14876 - Don't crash when we're running as a relay and don't have a GeoIP
14877 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
14878 we've had in the 0.2.3.x branch already.
14879 - When running as a client, do not print a misleading (and plain
14880 wrong) log message that we're collecting "directory request"
14881 statistics: clients don't collect statistics. Also don't create a
14882 useless (because empty) stats file in the stats/ directory. Fixes
14883 bug 4353; bugfix on 0.2.2.34.
14886 - Detect failure to initialize Libevent. This fix provides better
14887 detection for future instances of bug 4457.
14888 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
14889 function. This was eating up hideously large amounts of time on some
14890 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
14891 - Resolve an integer overflow bug in smartlist_ensure_capacity().
14892 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
14894 - Don't warn about unused log_mutex in log.c when building with
14895 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
14896 0.1.0.6-rc which introduced --disable-threads.
14897 - When configuring, starting, or stopping an NT service, stop
14898 immediately after the service configuration attempt has succeeded
14899 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
14900 - When sending a NETINFO cell, include the original address
14901 received for the other side, not its canonical address. Found
14902 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
14903 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
14904 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
14905 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
14906 occurred when a client tried to fetch a descriptor for a bridge
14907 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
14908 - Backport fixes for a pair of compilation warnings on Windows.
14909 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
14910 - If we had ever tried to call tor_addr_to_str on an address of
14911 unknown type, we would have done a strdup on an uninitialized
14912 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
14913 Reported by "troll_un".
14914 - Correctly detect and handle transient lookup failures from
14915 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
14916 Reported by "troll_un".
14917 - Fix null-pointer access that could occur if TLS allocation failed.
14918 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
14919 - Use tor_socket_t type for listener argument to accept(). Fixes bug
14920 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
14923 - Add two new config options for directory authorities:
14924 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
14925 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
14926 that is always sufficient to satisfy the bandwidth requirement for
14927 the Guard flag. Now it will be easier for researchers to simulate
14928 Tor networks with different values. Resolves ticket 4484.
14929 - When Tor ignores a hidden service specified in its configuration,
14930 include the hidden service's directory in the warning message.
14931 Previously, we would only tell the user that some hidden service
14932 was ignored. Bugfix on 0.0.6; fixes bug 4426.
14933 - Update to the December 6 2011 Maxmind GeoLite Country database.
14935 o Packaging changes:
14936 - Make it easier to automate expert package builds on Windows,
14937 by removing an absolute path from makensis.exe command.
14940 Changes in version 0.2.1.32 - 2011-12-16
14941 Tor 0.2.1.32 backports important security and privacy fixes for
14942 oldstable. This release is intended only for package maintainers and
14943 others who cannot use the 0.2.2 stable series. All others should be
14944 using Tor 0.2.2.x or newer.
14946 The Tor 0.2.1.x series will reach formal end-of-life some time in
14947 early 2012; we will stop releasing patches for it then.
14949 o Major bugfixes (also included in 0.2.2.x):
14950 - Correctly sanity-check that we don't underflow on a memory
14951 allocation (and then assert) for hidden service introduction
14952 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
14953 bugfix on 0.2.1.5-alpha.
14954 - Fix a heap overflow bug that could occur when trying to pull
14955 data into the first chunk of a buffer, when that chunk had
14956 already had some data drained from it. Fixes CVE-2011-2778;
14957 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
14960 - Update to the December 6 2011 Maxmind GeoLite Country database.
14963 Changes in version 0.2.3.9-alpha - 2011-12-08
14964 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
14965 a "DisableNetwork" security feature that bundles can use to avoid
14966 touching the network until bridges are configured, moves forward on
14967 the pluggable transport design, fixes a flaw in the hidden service
14968 design that unnecessarily prevented clients with wrong clocks from
14969 reaching hidden services, and fixes a wide variety of other issues.
14972 - Clients can now connect to private bridges over IPv6. Bridges
14973 still need at least one IPv4 address in order to connect to
14974 other relays. Note that we don't yet handle the case where the
14975 user has two bridge lines for the same bridge (one IPv4, one
14976 IPv6). Implements parts of proposal 186.
14977 - New "DisableNetwork" config option to prevent Tor from launching any
14978 connections or accepting any connections except on a control port.
14979 Bundles and controllers can set this option before letting Tor talk
14980 to the rest of the network, for example to prevent any connections
14981 to a non-bridge address. Packages like Orbot can also use this
14982 option to instruct Tor to save power when the network is off.
14983 - Clients and bridges can now be configured to use a separate
14984 "transport" proxy. This approach makes the censorship arms race
14985 easier by allowing bridges to use protocol obfuscation plugins. It
14986 implements the "managed proxy" part of proposal 180 (ticket 3472).
14987 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
14988 implementation. It makes AES_CTR about 7% faster than our old one
14989 (which was about 10% faster than the one OpenSSL used to provide).
14990 Resolves ticket 4526.
14991 - Add a "tor2web mode" for clients that want to connect to hidden
14992 services non-anonymously (and possibly more quickly). As a safety
14993 measure to try to keep users from turning this on without knowing
14994 what they are doing, tor2web mode must be explicitly enabled at
14995 compile time, and a copy of Tor compiled to run in tor2web mode
14996 cannot be used as a normal Tor client. Implements feature 2553.
14997 - Add experimental support for running on Windows with IOCP and no
14998 kernel-space socket buffers. This feature is controlled by a new
14999 "UserspaceIOCPBuffers" config option (off by default), which has
15000 no effect unless Tor has been built with support for bufferevents,
15001 is running on Windows, and has enabled IOCP. This may, in the long
15002 run, help solve or mitigate bug 98.
15003 - Use a more secure consensus parameter voting algorithm. Now at
15004 least three directory authorities or a majority of them must
15005 vote on a given parameter before it will be included in the
15006 consensus. Implements proposal 178.
15009 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
15010 They used to check that the timestamp was within 30 minutes
15011 of their system clock, so they could cap the size of their
15012 replay-detection cache, but that approach unnecessarily refused
15013 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
15014 the v3 intro-point protocol (the first one which sent a timestamp
15015 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
15016 - Only use the EVP interface when AES acceleration is enabled,
15017 to avoid a 5-7% performance regression. Resolves issue 4525;
15018 bugfix on 0.2.3.8-alpha.
15020 o Privacy/anonymity features (bridge detection):
15021 - Make bridge SSL certificates a bit more stealthy by using random
15022 serial numbers, in the same fashion as OpenSSL when generating
15023 self-signed certificates. Implements ticket 4584.
15024 - Introduce a new config option "DynamicDHGroups", enabled by
15025 default, which provides each bridge with a unique prime DH modulus
15026 to be used during SSL handshakes. This option attempts to help
15027 against censors who might use the Apache DH modulus as a static
15028 identifier for bridges. Addresses ticket 4548.
15030 o Minor features (new/different config options):
15031 - New configuration option "DisableDebuggerAttachment" (on by default)
15032 to prevent basic debugging attachment attempts by other processes.
15033 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
15034 - Allow MapAddress directives to specify matches against super-domains,
15035 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
15036 Implements issue 933.
15037 - Slightly change behavior of "list" options (that is, config
15038 options that can appear more than once) when they appear both in
15039 torrc and on the command line. Previously, the command-line options
15040 would be appended to the ones from torrc. Now, the command-line
15041 options override the torrc options entirely. This new behavior
15042 allows the user to override list options (like exit policies and
15043 ports to listen on) from the command line, rather than simply
15044 appending to the list.
15045 - You can get the old (appending) command-line behavior for "list"
15046 options by prefixing the option name with a "+".
15047 - You can remove all the values for a "list" option from the command
15048 line without adding any new ones by prefixing the option name
15050 - Add experimental support for a "defaults" torrc file to be parsed
15051 before the regular torrc. Torrc options override the defaults file's
15052 options in the same way that the command line overrides the torrc.
15053 The SAVECONF controller command saves only those options which
15054 differ between the current configuration and the defaults file. HUP
15055 reloads both files. (Note: This is an experimental feature; its
15056 behavior will probably be refined in future 0.2.3.x-alpha versions
15057 to better meet packagers' needs.) Implements task 4552.
15060 - Try to make the introductory warning message that Tor prints on
15061 startup more useful for actually finding help and information.
15062 Resolves ticket 2474.
15063 - Running "make version" now displays the version of Tor that
15064 we're about to build. Idea from katmagic; resolves issue 4400.
15065 - Expire old or over-used hidden service introduction points.
15066 Required by fix for bug 3460.
15067 - Move the replay-detection cache for the RSA-encrypted parts of
15068 INTRODUCE2 cells to the introduction point data structures.
15069 Previously, we would use one replay-detection cache per hidden
15070 service. Required by fix for bug 3460.
15071 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
15072 public key replay-detection cache from 60 minutes to 5 minutes. This
15073 replay-detection cache is now used only to detect multiple
15074 INTRODUCE2 cells specifying the same rendezvous point, so we can
15075 avoid launching multiple simultaneous attempts to connect to it.
15077 o Minor bugfixes (on Tor 0.2.2.x and earlier):
15078 - Resolve an integer overflow bug in smartlist_ensure_capacity().
15079 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
15081 - Fix a minor formatting issue in one of tor-gencert's error messages.
15083 - Prevent a false positive from the check-spaces script, by disabling
15084 the "whitespace between function name and (" check for functions
15086 - Fix a log message suggesting that people contact a non-existent
15087 email address. Fixes bug 3448.
15088 - Fix null-pointer access that could occur if TLS allocation failed.
15089 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
15090 - Report a real bootstrap problem to the controller on router
15091 identity mismatch. Previously we just said "foo", which probably
15092 made a lot of sense at the time. Fixes bug 4169; bugfix on
15094 - If we had ever tried to call tor_addr_to_str() on an address of
15095 unknown type, we would have done a strdup() on an uninitialized
15096 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
15097 Reported by "troll_un".
15098 - Correctly detect and handle transient lookup failures from
15099 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
15100 Reported by "troll_un".
15101 - Use tor_socket_t type for listener argument to accept(). Fixes bug
15102 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
15103 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
15104 bug 4532; found by "troll_un".
15106 o Minor bugfixes (on Tor 0.2.3.x):
15107 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
15109 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
15110 circuit for use as a hidden service client's rendezvous point.
15111 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
15112 with help from wanoskarnet.
15113 - Restore behavior of overriding SocksPort, ORPort, and similar
15114 options from the command line. Bugfix on 0.2.3.3-alpha.
15117 - Properly handle the case where the build-tree is not the same
15118 as the source tree when generating src/common/common_sha1.i,
15119 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
15120 bugfix on 0.2.0.1-alpha.
15122 o Code simplifications, cleanups, and refactorings:
15123 - Remove the pure attribute from all functions that used it
15124 previously. In many cases we assigned it incorrectly, because the
15125 functions might assert or call impure functions, and we don't have
15126 evidence that keeping the pure attribute is worthwhile. Implements
15127 changes suggested in ticket 4421.
15128 - Remove some dead code spotted by coverity. Fixes cid 432.
15129 Bugfix on 0.2.3.1-alpha, closes bug 4637.
15132 Changes in version 0.2.3.8-alpha - 2011-11-22
15133 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
15134 socketpair-related bug that has been bothering Windows users. It adds
15135 support to serve microdescriptors to controllers, so Vidalia's network
15136 map can resume listing relays (once Vidalia implements its side),
15137 and adds better support for hardware AES acceleration. Finally, it
15138 starts the process of adjusting the bandwidth cutoff for getting the
15139 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
15140 that tiny relays harm performance more than they help network capacity.
15143 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
15144 that it doesn't attempt to allocate a socketpair. This could cause
15145 some problems on Windows systems with overzealous firewalls. Fix for
15146 bug 4457; workaround for Libevent versions 2.0.1-alpha through
15148 - Correctly sanity-check that we don't underflow on a memory
15149 allocation (and then assert) for hidden service introduction
15150 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
15151 bugfix on 0.2.1.5-alpha.
15152 - Remove the artificially low cutoff of 20KB to guarantee the Fast
15153 flag. In the past few years the average relay speed has picked
15154 up, and while the "top 7/8 of the network get the Fast flag" and
15155 "all relays with 20KB or more of capacity get the Fast flag" rules
15156 used to have the same result, now the top 7/8 of the network has
15157 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
15158 - Fix a rare assertion failure when checking whether a v0 hidden
15159 service descriptor has any usable introduction points left, and
15160 we don't have enough information to build a circuit to the first
15161 intro point named in the descriptor. The HS client code in
15162 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
15163 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
15164 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
15165 - Make bridge authorities not crash when they are asked for their own
15166 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
15167 - When running as a client, do not print a misleading (and plain
15168 wrong) log message that we're collecting "directory request"
15169 statistics: clients don't collect statistics. Also don't create a
15170 useless (because empty) stats file in the stats/ directory. Fixes
15171 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
15174 - Allow Tor controllers like Vidalia to obtain the microdescriptor
15175 for a relay by identity digest or nickname. Previously,
15176 microdescriptors were only available by their own digests, so a
15177 controller would have to ask for and parse the whole microdescriptor
15178 consensus in order to look up a single relay's microdesc. Fixes
15179 bug 3832; bugfix on 0.2.3.1-alpha.
15180 - Use OpenSSL's EVP interface for AES encryption, so that all AES
15181 operations can use hardware acceleration (if present). Resolves
15184 o Minor bugfixes (on 0.2.2.x and earlier):
15185 - Detect failure to initialize Libevent. This fix provides better
15186 detection for future instances of bug 4457.
15187 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
15188 function. This was eating up hideously large amounts of time on some
15189 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
15190 - Don't warn about unused log_mutex in log.c when building with
15191 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
15192 0.1.0.6-rc which introduced --disable-threads.
15193 - Allow manual 'authenticate' commands to the controller interface
15194 from netcat (nc) as well as telnet. We were rejecting them because
15195 they didn't come with the expected whitespace at the end of the
15196 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
15197 - Fix some (not actually triggerable) buffer size checks in usage of
15198 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
15200 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
15201 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
15202 - When configuring, starting, or stopping an NT service, stop
15203 immediately after the service configuration attempt has succeeded
15204 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
15205 - When sending a NETINFO cell, include the original address
15206 received for the other side, not its canonical address. Found
15207 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
15208 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
15209 can pick them up when the tests aren't disabled. Bugfix on
15210 0.2.2.4-alpha which introduced tinytest.
15211 - Fix a memory leak when we check whether a hidden service
15212 descriptor has any usable introduction points left. Fixes bug
15213 4424. Bugfix on 0.2.2.25-alpha.
15214 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
15215 occurred when a client tried to fetch a descriptor for a bridge
15216 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
15218 o Minor bugfixes (on 0.2.3.x):
15219 - Make util unit tests build correctly with MSVC. Bugfix on
15220 0.2.3.3-alpha. Patch by Gisle Vanem.
15221 - Successfully detect AUTH_CHALLENGE cells with no recognized
15222 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
15223 Found by frosty_un.
15224 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
15225 it should still send a NETINFO cell to allow the connection to
15226 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
15228 - Log less loudly when we get an invalid authentication certificate
15229 from a source other than a directory authority: it's not unusual
15230 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
15232 - Tolerate servers with more clock skew in their authentication
15233 certificates than previously. Fixes bug 4371; bugfix on
15235 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
15236 on 0.2.3.4-alpha and 0.2.3.6-alpha.
15239 - Add two new config options for directory authorities:
15240 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
15241 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
15242 that is always sufficient to satisfy the bandwidth requirement for
15243 the Guard flag. Now it will be easier for researchers to simulate
15244 Tor networks with different values. Resolves ticket 4484.
15245 - When Tor ignores a hidden service specified in its configuration,
15246 include the hidden service's directory in the warning message.
15247 Previously, we would only tell the user that some hidden service
15248 was ignored. Bugfix on 0.0.6; fixes bug 4426.
15249 - When we fail to initialize Libevent, retry with IOCP disabled so we
15250 don't need to turn on multi-threading support in Libevent, which in
15251 turn requires a working socketpair(). This is a workaround for bug
15252 4457, which affects Libevent versions from 2.0.1-alpha through
15254 - Detect when we try to build on a platform that doesn't define
15255 AF_UNSPEC to 0. We don't work there, so refuse to compile.
15256 - Update to the November 1 2011 Maxmind GeoLite Country database.
15258 o Packaging changes:
15259 - Make it easier to automate expert package builds on Windows,
15260 by removing an absolute path from makensis.exe command.
15262 o Code simplifications and refactoring:
15263 - Remove some redundant #include directives throughout the code.
15264 Patch from Andrea Gelmini.
15265 - Unconditionally use OpenSSL's AES implementation instead of our
15266 old built-in one. OpenSSL's AES has been better for a while, and
15267 relatively few servers should still be on any version of OpenSSL
15268 that doesn't have good optimized assembly AES.
15269 - Use the name "CERTS" consistently to refer to the new cell type;
15270 we were calling it CERT in some places and CERTS in others.
15273 - Numerous new unit tests for functions in util.c and address.c by
15275 - The long-disabled benchmark tests are now split into their own
15276 ./src/test/bench binary.
15277 - The benchmark tests can now use more accurate timers than
15278 gettimeofday() when such timers are available.
15281 Changes in version 0.2.3.7-alpha - 2011-10-30
15282 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
15283 the new v3 handshake. It also resolves yet another bridge address
15287 - If we mark an OR connection for close based on a cell we process,
15288 don't process any further cells on it. We already avoid further
15289 reads on marked-for-close connections, but now we also discard the
15290 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
15291 which was the first version where we might mark a connection for
15292 close based on processing a cell on it.
15293 - Fix a double-free bug that would occur when we received an invalid
15294 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
15295 bugfix on 0.2.3.6-alpha.
15296 - Bridges no longer include their address in NETINFO cells on outgoing
15297 OR connections, to allow them to blend in better with clients.
15298 Removes another avenue for enumerating bridges. Reported by
15299 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
15300 cells were introduced.
15303 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
15304 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
15307 Changes in version 0.2.3.6-alpha - 2011-10-26
15308 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
15309 anonymity vulnerability where an attacker can deanonymize Tor
15310 users. Everybody should upgrade.
15312 This release also features support for a new v3 connection handshake
15313 protocol, and fixes to make hidden service connections more robust.
15316 - Implement a new handshake protocol (v3) for authenticating Tors to
15317 each other over TLS. It should be more resistant to fingerprinting
15318 than previous protocols, and should require less TLS hacking for
15319 future Tor implementations. Implements proposal 176.
15320 - Allow variable-length padding cells to disguise the length of
15321 Tor's TLS records. Implements part of proposal 184.
15323 o Privacy/anonymity fixes (clients):
15324 - Clients and bridges no longer send TLS certificate chains on
15325 outgoing OR connections. Previously, each client or bridge would
15326 use the same cert chain for all outgoing OR connections until
15327 its IP address changes, which allowed any relay that the client
15328 or bridge contacted to determine which entry guards it is using.
15329 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
15330 - If a relay receives a CREATE_FAST cell on a TLS connection, it
15331 no longer considers that connection as suitable for satisfying a
15332 circuit EXTEND request. Now relays can protect clients from the
15333 CVE-2011-2768 issue even if the clients haven't upgraded yet.
15334 - Directory authorities no longer assign the Guard flag to relays
15335 that haven't upgraded to the above "refuse EXTEND requests
15336 to client connections" fix. Now directory authorities can
15337 protect clients from the CVE-2011-2768 issue even if neither
15338 the clients nor the relays have upgraded yet. There's a new
15339 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
15340 to let us transition smoothly, else tomorrow there would be no
15343 o Major bugfixes (hidden services):
15344 - Improve hidden service robustness: when an attempt to connect to
15345 a hidden service ends, be willing to refetch its hidden service
15346 descriptors from each of the HSDir relays responsible for them
15347 immediately. Previously, we would not consider refetching the
15348 service's descriptors from each HSDir for 15 minutes after the last
15349 fetch, which was inconvenient if the hidden service was not running
15350 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
15351 - When one of a hidden service's introduction points appears to be
15352 unreachable, stop trying it. Previously, we would keep trying
15353 to build circuits to the introduction point until we lost the
15354 descriptor, usually because the user gave up and restarted Tor.
15355 Partly fixes bug 3825.
15356 - Don't launch a useless circuit after failing to use one of a
15357 hidden service's introduction points. Previously, we would
15358 launch a new introduction circuit, but not set the hidden service
15359 which that circuit was intended to connect to, so it would never
15360 actually be used. A different piece of code would then create a
15361 new introduction circuit correctly. Bug reported by katmagic and
15362 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
15364 o Major bugfixes (other):
15365 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
15366 that they initiated. Relays could distinguish incoming bridge
15367 connections from client connections, creating another avenue for
15368 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
15369 Found by "frosty_un".
15370 - Don't update the AccountingSoftLimitHitAt state file entry whenever
15371 tor gets started. This prevents a wrong average bandwidth
15372 estimate, which would cause relays to always start a new accounting
15373 interval at the earliest possible moment. Fixes bug 2003; bugfix
15374 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
15375 immensely in tracking this bug down.
15376 - Fix a crash bug when changing node restrictions while a DNS lookup
15377 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
15380 o Minor bugfixes (on 0.2.2.x and earlier):
15381 - When a hidden service turns an extra service-side introduction
15382 circuit into a general-purpose circuit, free the rend_data and
15383 intro_key fields first, so we won't leak memory if the circuit
15384 is cannibalized for use as another service-side introduction
15385 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
15386 - Rephrase the log message emitted if the TestSocks check is
15387 successful. Patch from Fabian Keil; fixes bug 4094.
15388 - Bridges now skip DNS self-tests, to act a little more stealthily.
15389 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
15390 bridges. Patch by "warms0x".
15391 - Remove a confusing dollar sign from the example fingerprint in the
15392 man page, and also make the example fingerprint a valid one. Fixes
15393 bug 4309; bugfix on 0.2.1.3-alpha.
15394 - Fix internal bug-checking logic that was supposed to catch
15395 failures in digest generation so that it will fail more robustly
15396 if we ask for a nonexistent algorithm. Found by Coverity Scan.
15397 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
15398 - Report any failure in init_keys() calls launched because our
15399 IP address has changed. Spotted by Coverity Scan. Bugfix on
15400 0.1.1.4-alpha; fixes CID 484.
15402 o Minor bugfixes (on 0.2.3.x):
15403 - Fix a bug in configure.in that kept it from building a configure
15404 script with autoconf versions earlier than 2.61. Fixes bug 2430;
15405 bugfix on 0.2.3.1-alpha.
15406 - Don't warn users that they are exposing a client port to the
15407 Internet if they have specified an RFC1918 address. Previously,
15408 we would warn if the user had specified any non-loopback
15409 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
15410 - Fix memory leaks in the failing cases of the new SocksPort and
15411 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
15412 fixes coverity CIDs 485, 486, and 487.
15415 - When a hidden service's introduction point times out, consider
15416 trying it again during the next attempt to connect to the
15417 HS. Previously, we would not try it again unless a newly fetched
15418 descriptor contained it. Required by fixes for bugs 1297 and 3825.
15419 - The next version of Windows will be called Windows 8, and it has
15420 a major version of 6, minor version of 2. Correctly identify that
15421 version instead of calling it "Very recent version". Resolves
15422 ticket 4153; reported by funkstar.
15423 - The Bridge Authority now writes statistics on how many bridge
15424 descriptors it gave out in total, and how many unique descriptors
15425 it gave out. It also lists how often the most and least commonly
15426 fetched descriptors were given out, as well as the median and
15427 25th/75th percentile. Implements tickets 4200 and 4294.
15428 - Update to the October 4 2011 Maxmind GeoLite Country database.
15430 o Code simplifications and refactoring:
15431 - Remove some old code to remember statistics about which descriptors
15432 we've served as a directory mirror. The feature wasn't used and
15433 is outdated now that microdescriptors are around.
15434 - Rename Tor functions that turn strings into addresses, so that
15435 "parse" indicates that no hostname resolution occurs, and
15436 "lookup" indicates that hostname resolution may occur. This
15437 should help prevent mistakes in the future. Fixes bug 3512.
15440 Changes in version 0.2.2.34 - 2011-10-26
15441 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
15442 can deanonymize Tor users. Everybody should upgrade.
15444 The attack relies on four components: 1) Clients reuse their TLS cert
15445 when talking to different relays, so relays can recognize a user by
15446 the identity key in her cert. 2) An attacker who knows the client's
15447 identity key can probe each guard relay to see if that identity key
15448 is connected to that guard relay right now. 3) A variety of active
15449 attacks in the literature (starting from "Low-Cost Traffic Analysis
15450 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
15451 discover the guard relays that a Tor user visiting the website is using.
15452 4) Clients typically pick three guards at random, so the set of guards
15453 for a given user could well be a unique fingerprint for her. This
15454 release fixes components #1 and #2, which is enough to block the attack;
15455 the other two remain as open research problems. Special thanks to
15456 "frosty_un" for reporting the issue to us!
15458 Clients should upgrade so they are no longer recognizable by the TLS
15459 certs they present. Relays should upgrade so they no longer allow a
15460 remote attacker to probe them to test whether unpatched clients are
15461 currently connected to them.
15463 This release also fixes several vulnerabilities that allow an attacker
15464 to enumerate bridge relays. Some bridge enumeration attacks still
15465 remain; see for example proposal 188.
15467 o Privacy/anonymity fixes (clients):
15468 - Clients and bridges no longer send TLS certificate chains on
15469 outgoing OR connections. Previously, each client or bridge would
15470 use the same cert chain for all outgoing OR connections until
15471 its IP address changes, which allowed any relay that the client
15472 or bridge contacted to determine which entry guards it is using.
15473 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
15474 - If a relay receives a CREATE_FAST cell on a TLS connection, it
15475 no longer considers that connection as suitable for satisfying a
15476 circuit EXTEND request. Now relays can protect clients from the
15477 CVE-2011-2768 issue even if the clients haven't upgraded yet.
15478 - Directory authorities no longer assign the Guard flag to relays
15479 that haven't upgraded to the above "refuse EXTEND requests
15480 to client connections" fix. Now directory authorities can
15481 protect clients from the CVE-2011-2768 issue even if neither
15482 the clients nor the relays have upgraded yet. There's a new
15483 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
15484 to let us transition smoothly, else tomorrow there would be no
15487 o Privacy/anonymity fixes (bridge enumeration):
15488 - Bridge relays now do their directory fetches inside Tor TLS
15489 connections, like all the other clients do, rather than connecting
15490 directly to the DirPort like public relays do. Removes another
15491 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
15492 - Bridges relays now build circuits for themselves in a more similar
15493 way to how clients build them. Removes another avenue for
15494 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
15495 when bridges were introduced.
15496 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
15497 that they initiated. Relays could distinguish incoming bridge
15498 connections from client connections, creating another avenue for
15499 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
15500 Found by "frosty_un".
15503 - Fix a crash bug when changing node restrictions while a DNS lookup
15504 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
15506 - Don't launch a useless circuit after failing to use one of a
15507 hidden service's introduction points. Previously, we would
15508 launch a new introduction circuit, but not set the hidden service
15509 which that circuit was intended to connect to, so it would never
15510 actually be used. A different piece of code would then create a
15511 new introduction circuit correctly. Bug reported by katmagic and
15512 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
15515 - Change an integer overflow check in the OpenBSD_Malloc code so
15516 that GCC is less likely to eliminate it as impossible. Patch
15517 from Mansour Moufid. Fixes bug 4059.
15518 - When a hidden service turns an extra service-side introduction
15519 circuit into a general-purpose circuit, free the rend_data and
15520 intro_key fields first, so we won't leak memory if the circuit
15521 is cannibalized for use as another service-side introduction
15522 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
15523 - Bridges now skip DNS self-tests, to act a little more stealthily.
15524 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
15525 bridges. Patch by "warms0x".
15526 - Fix internal bug-checking logic that was supposed to catch
15527 failures in digest generation so that it will fail more robustly
15528 if we ask for a nonexistent algorithm. Found by Coverity Scan.
15529 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
15530 - Report any failure in init_keys() calls launched because our
15531 IP address has changed. Spotted by Coverity Scan. Bugfix on
15532 0.1.1.4-alpha; fixes CID 484.
15534 o Minor bugfixes (log messages and documentation):
15535 - Remove a confusing dollar sign from the example fingerprint in the
15536 man page, and also make the example fingerprint a valid one. Fixes
15537 bug 4309; bugfix on 0.2.1.3-alpha.
15538 - The next version of Windows will be called Windows 8, and it has
15539 a major version of 6, minor version of 2. Correctly identify that
15540 version instead of calling it "Very recent version". Resolves
15541 ticket 4153; reported by funkstar.
15542 - Downgrade log messages about circuit timeout calibration from
15543 "notice" to "info": they don't require or suggest any human
15544 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
15545 bugfix on 0.2.2.14-alpha.
15548 - Turn on directory request statistics by default and include them in
15549 extra-info descriptors. Don't break if we have no GeoIP database.
15550 Backported from 0.2.3.1-alpha; implements ticket 3951.
15551 - Update to the October 4 2011 Maxmind GeoLite Country database.
15554 Changes in version 0.2.1.31 - 2011-10-26
15555 Tor 0.2.1.31 backports important security and privacy fixes for
15556 oldstable. This release is intended only for package maintainers and
15557 others who cannot use the 0.2.2 stable series. All others should be
15558 using Tor 0.2.2.x or newer.
15560 o Security fixes (also included in 0.2.2.x):
15561 - Replace all potentially sensitive memory comparison operations
15562 with versions whose runtime does not depend on the data being
15563 compared. This will help resist a class of attacks where an
15564 adversary can use variations in timing information to learn
15565 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15566 implementation by Robert Ransom based partially on code by DJB.)
15567 - Fix an assert in parsing router descriptors containing IPv6
15568 addresses. This one took down the directory authorities when
15569 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
15571 o Privacy/anonymity fixes (also included in 0.2.2.x):
15572 - Clients and bridges no longer send TLS certificate chains on
15573 outgoing OR connections. Previously, each client or bridge would
15574 use the same cert chain for all outgoing OR connections until
15575 its IP address changes, which allowed any relay that the client
15576 or bridge contacted to determine which entry guards it is using.
15577 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
15578 - If a relay receives a CREATE_FAST cell on a TLS connection, it
15579 no longer considers that connection as suitable for satisfying a
15580 circuit EXTEND request. Now relays can protect clients from the
15581 CVE-2011-2768 issue even if the clients haven't upgraded yet.
15582 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
15583 that they initiated. Relays could distinguish incoming bridge
15584 connections from client connections, creating another avenue for
15585 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
15586 Found by "frosty_un".
15587 - When receiving a hidden service descriptor, check that it is for
15588 the hidden service we wanted. Previously, Tor would store any
15589 hidden service descriptors that a directory gave it, whether it
15590 wanted them or not. This wouldn't have let an attacker impersonate
15591 a hidden service, but it did let directories pre-seed a client
15592 with descriptors that it didn't want. Bugfix on 0.0.6.
15593 - Avoid linkability based on cached hidden service descriptors: forget
15594 all hidden service descriptors cached as a client when processing a
15595 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15596 - Make the bridge directory authority refuse to answer directory
15597 requests for "all" descriptors. It used to include bridge
15598 descriptors in its answer, which was a major information leak.
15599 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
15600 - Don't attach new streams to old rendezvous circuits after SIGNAL
15601 NEWNYM. Previously, we would keep using an existing rendezvous
15602 circuit if it remained open (i.e. if it were kept open by a
15603 long-lived stream, or if a new stream were attached to it before
15604 Tor could notice that it was old and no longer in use). Bugfix on
15605 0.1.1.15-rc; fixes bug 3375.
15607 o Minor bugfixes (also included in 0.2.2.x):
15608 - When we restart our relay, we might get a successful connection
15609 from the outside before we've started our reachability tests,
15610 triggering a warning: "ORPort found reachable, but I have no
15611 routerinfo yet. Failing to inform controller of success." This
15612 bug was harmless unless Tor is running under a controller
15613 like Vidalia, in which case the controller would never get a
15614 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
15616 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
15617 enabled. Fixes bug 1526.
15618 - Remove undocumented option "-F" from tor-resolve: it hasn't done
15619 anything since 0.2.1.16-rc.
15620 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
15621 None of the cases where we did this before were wrong, but by making
15622 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
15623 - Fix a rare crash bug that could occur when a client was configured
15624 with a large number of bridges. Fixes bug 2629; bugfix on
15625 0.2.1.2-alpha. Bugfix by trac user "shitlei".
15626 - Correct the warning displayed when a rendezvous descriptor exceeds
15627 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
15629 - Fix an uncommon assertion failure when running with DNSPort under
15630 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15631 - When warning about missing zlib development packages during compile,
15632 give the correct package names. Bugfix on 0.2.0.1-alpha.
15633 - Require that introduction point keys and onion keys have public
15634 exponent 65537. Bugfix on 0.2.0.10-alpha.
15635 - Do not crash when our configuration file becomes unreadable, for
15636 example due to a permissions change, between when we start up
15637 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15639 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
15641 - Always NUL-terminate the sun_path field of a sockaddr_un before
15642 passing it to the kernel. (Not a security issue: kernels are
15643 smart enough to reject bad sockaddr_uns.) Found by Coverity;
15644 CID #428. Bugfix on Tor 0.2.0.3-alpha.
15645 - Don't stack-allocate the list of supplementary GIDs when we're
15646 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
15647 could take up to 256K, which is way too much stack. Found by
15648 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
15650 o Minor bugfixes (only in 0.2.1.x):
15651 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
15652 rely on them. Bugfix on 0.2.1.30.
15653 - Use git revisions instead of svn revisions when generating our
15654 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
15656 o Minor features (also included in 0.2.2.x):
15657 - Adjust the expiration time on our SSL session certificates to
15658 better match SSL certs seen in the wild. Resolves ticket 4014.
15659 - Allow nameservers with IPv6 address. Resolves bug 2574.
15660 - Update to the October 4 2011 Maxmind GeoLite Country database.
15663 Changes in version 0.2.3.5-alpha - 2011-09-28
15664 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
15665 bridge relays; fixes an assertion error that many users started hitting
15666 today; and adds the ability to refill token buckets more often than
15667 once per second, allowing significant performance improvements.
15670 - Bridge relays now do their directory fetches inside Tor TLS
15671 connections, like all the other clients do, rather than connecting
15672 directly to the DirPort like public relays do. Removes another
15673 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
15674 - Bridges relays now build circuits for themselves in a more similar
15675 way to how clients build them. Removes another avenue for
15676 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
15677 when bridges were introduced.
15680 - Fix an "Assertion md->held_by_node == 1 failed" error that could
15681 occur when the same microdescriptor was referenced by two node_t
15682 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
15684 o Major features (networking):
15685 - Add a new TokenBucketRefillInterval option to refill token buckets
15686 more frequently than once per second. This should improve network
15687 performance, alleviate queueing problems, and make traffic less
15688 bursty. Implements proposal 183; closes ticket 3630. Design by
15689 Florian Tschorsch and Björn Scheuermann; implementation by
15693 - Change an integer overflow check in the OpenBSD_Malloc code so
15694 that GCC is less likely to eliminate it as impossible. Patch
15695 from Mansour Moufid. Fixes bug 4059.
15697 o Minor bugfixes (usability):
15698 - Downgrade log messages about circuit timeout calibration from
15699 "notice" to "info": they don't require or suggest any human
15700 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
15701 bugfix on 0.2.2.14-alpha.
15703 o Minor features (diagnostics):
15704 - When the system call to create a listener socket fails, log the
15705 error message explaining why. This may help diagnose bug 4027.
15708 Changes in version 0.2.3.4-alpha - 2011-09-13
15709 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
15710 tweak to Tor's TLS handshake that makes relays and bridges that run
15711 this new version reachable from Iran again. It also fixes a few new
15712 bugs in 0.2.3.x, and teaches relays to recognize when they're not
15713 listed in the network consensus and republish.
15715 o Major bugfixes (also part of 0.2.2.33):
15716 - Avoid an assertion failure when reloading a configuration with
15717 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
15718 3923; bugfix on 0.2.2.25-alpha.
15720 o Minor features (security, also part of 0.2.2.33):
15721 - Check for replays of the public-key encrypted portion of an
15722 INTRODUCE1 cell, in addition to the current check for replays of
15723 the g^x value. This prevents a possible class of active attacks
15724 by an attacker who controls both an introduction point and a
15725 rendezvous point, and who uses the malleability of AES-CTR to
15726 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
15727 that these attacks are infeasible (requiring the attacker to send
15728 on the order of zettabytes of altered cells in a short interval),
15729 but we'd rather block them off in case there are any classes of
15730 this attack that we missed. Reported by Willem Pinckaers.
15732 o Minor features (also part of 0.2.2.33):
15733 - Adjust the expiration time on our SSL session certificates to
15734 better match SSL certs seen in the wild. Resolves ticket 4014.
15735 - Change the default required uptime for a relay to be accepted as
15736 a HSDir (hidden service directory) from 24 hours to 25 hours.
15737 Improves on 0.2.0.10-alpha; resolves ticket 2649.
15738 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
15739 authorities to abstain from voting on assignment of the HSDir
15740 consensus flag. Related to bug 2649.
15741 - Update to the September 6 2011 Maxmind GeoLite Country database.
15743 o Minor bugfixes (also part of 0.2.2.33):
15744 - Demote the 'replay detected' log message emitted when a hidden
15745 service receives the same Diffie-Hellman public key in two different
15746 INTRODUCE2 cells to info level. A normal Tor client can cause that
15747 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
15748 fixes part of bug 2442.
15749 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
15750 level. There is nothing that a hidden service's operator can do
15751 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
15753 - Clarify a log message specifying the characters permitted in
15754 HiddenServiceAuthorizeClient client names. Previously, the log
15755 message said that "[A-Za-z0-9+-_]" were permitted; that could have
15756 given the impression that every ASCII character between "+" and "_"
15757 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
15759 o Build fixes (also part of 0.2.2.33):
15760 - Clean up some code issues that prevented Tor from building on older
15761 BSDs. Fixes bug 3894; reported by "grarpamp".
15762 - Search for a platform-specific version of "ar" when cross-compiling.
15763 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
15766 - Fix a bug where the SocksPort option (for example) would get
15767 ignored and replaced by the default if a SocksListenAddress
15768 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
15772 - Relays now try regenerating and uploading their descriptor more
15773 frequently if they are not listed in the consensus, or if the
15774 version of their descriptor listed in the consensus is too
15775 old. This fix should prevent situations where a server declines
15776 to re-publish itself because it has done so too recently, even
15777 though the authorities decided not to list its recent-enough
15778 descriptor. Fix for bug 3327.
15781 - Relays now include a reason for regenerating their descriptors
15782 in an HTTP header when uploading to the authorities. This will
15783 make it easier to debug descriptor-upload issues in the future.
15784 - When starting as root and then changing our UID via the User
15785 control option, and we have a ControlSocket configured, make sure
15786 that the ControlSocket is owned by the same account that Tor will
15787 run under. Implements ticket 3421; fix by Jérémy Bobbio.
15790 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
15791 utility function used in the control-port code). This shouldn't
15792 ever happen unless Tor is completely out of memory, but if it did
15793 happen and Tor somehow recovered from it, Tor could have sent a log
15794 message to a control port in the middle of a reply to a controller
15795 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
15796 - Make 'FetchUselessDescriptors' cause all descriptor types and
15797 all consensus types (including microdescriptors) to get fetched.
15798 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
15800 o Code refactoring:
15801 - Make a new "entry connection" struct as an internal subtype of "edge
15802 connection", to simplify the code and make exit connections smaller.
15805 Changes in version 0.2.2.33 - 2011-09-13
15806 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
15807 TLS handshake that makes relays and bridges that run this new version
15808 reachable from Iran again.
15811 - Avoid an assertion failure when reloading a configuration with
15812 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
15813 3923; bugfix on 0.2.2.25-alpha.
15815 o Minor features (security):
15816 - Check for replays of the public-key encrypted portion of an
15817 INTRODUCE1 cell, in addition to the current check for replays of
15818 the g^x value. This prevents a possible class of active attacks
15819 by an attacker who controls both an introduction point and a
15820 rendezvous point, and who uses the malleability of AES-CTR to
15821 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
15822 that these attacks are infeasible (requiring the attacker to send
15823 on the order of zettabytes of altered cells in a short interval),
15824 but we'd rather block them off in case there are any classes of
15825 this attack that we missed. Reported by Willem Pinckaers.
15828 - Adjust the expiration time on our SSL session certificates to
15829 better match SSL certs seen in the wild. Resolves ticket 4014.
15830 - Change the default required uptime for a relay to be accepted as
15831 a HSDir (hidden service directory) from 24 hours to 25 hours.
15832 Improves on 0.2.0.10-alpha; resolves ticket 2649.
15833 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
15834 authorities to abstain from voting on assignment of the HSDir
15835 consensus flag. Related to bug 2649.
15836 - Update to the September 6 2011 Maxmind GeoLite Country database.
15838 o Minor bugfixes (documentation and log messages):
15839 - Correct the man page to explain that HashedControlPassword and
15840 CookieAuthentication can both be set, in which case either method
15841 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15842 when we decided to allow these config options to both be set. Issue
15843 raised by bug 3898.
15844 - Demote the 'replay detected' log message emitted when a hidden
15845 service receives the same Diffie-Hellman public key in two different
15846 INTRODUCE2 cells to info level. A normal Tor client can cause that
15847 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
15848 fixes part of bug 2442.
15849 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
15850 level. There is nothing that a hidden service's operator can do
15851 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
15853 - Clarify a log message specifying the characters permitted in
15854 HiddenServiceAuthorizeClient client names. Previously, the log
15855 message said that "[A-Za-z0-9+-_]" were permitted; that could have
15856 given the impression that every ASCII character between "+" and "_"
15857 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
15860 - Provide a substitute implementation of lround() for MSVC, which
15861 apparently lacks it. Patch from Gisle Vanem.
15862 - Clean up some code issues that prevented Tor from building on older
15863 BSDs. Fixes bug 3894; reported by "grarpamp".
15864 - Search for a platform-specific version of "ar" when cross-compiling.
15865 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
15868 Changes in version 0.2.3.3-alpha - 2011-09-01
15869 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
15870 security, and provides client-side support for the microdescriptor
15871 and optimistic data features introduced earlier in the 0.2.3.x
15872 series. It also includes numerous critical bugfixes in the (optional)
15873 bufferevent-based networking backend.
15875 o Major features (stream isolation):
15876 - You can now configure Tor so that streams from different
15877 applications are isolated on different circuits, to prevent an
15878 attacker who sees your streams as they leave an exit node from
15879 linking your sessions to one another. To do this, choose some way
15880 to distinguish the applications: have them connect to different
15881 SocksPorts, or have one of them use SOCKS4 while the other uses
15882 SOCKS5, or have them pass different authentication strings to the
15883 SOCKS proxy. Then, use the new SocksPort syntax to configure the
15884 degree of isolation you need. This implements Proposal 171.
15885 - There's a new syntax for specifying multiple client ports (such as
15886 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
15887 multiple *Port entries with full addr:port syntax on each.
15888 The old *ListenAddress format is still supported, but you can't
15889 mix it with the new *Port syntax.
15891 o Major features (other):
15892 - Enable microdescriptor fetching by default for clients. This allows
15893 clients to download a much smaller amount of directory information.
15894 To disable it (and go back to the old-style consensus and
15895 descriptors), set "UseMicrodescriptors 0" in your torrc file.
15896 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
15897 "PortForwarding" config option), now supports Windows.
15898 - When using an exit relay running 0.2.3.x, clients can now
15899 "optimistically" send data before the exit relay reports that
15900 the stream has opened. This saves a round trip when starting
15901 connections where the client speaks first (such as web browsing).
15902 This behavior is controlled by a consensus parameter (currently
15903 disabled). To turn it on or off manually, use the "OptimisticData"
15904 torrc option. Implements proposal 181; code by Ian Goldberg.
15906 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
15907 - When using IOCP on Windows, we need to enable Libevent windows
15909 - The IOCP backend now works even when the user has not specified
15910 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
15911 Fixes part of bug 3752.
15912 - Correctly record the bytes we've read and written when using
15913 bufferevents, so that we can include them in our bandwidth history
15914 and advertised bandwidth. Fixes bug 3803.
15915 - Apply rate-limiting only at the bottom of a chain of filtering
15916 bufferevents. This prevents us from filling up internal read
15917 buffers and violating rate-limits when filtering bufferevents
15918 are enabled. Fixes part of bug 3804.
15919 - Add high-watermarks to the output buffers for filtered
15920 bufferevents. This prevents us from filling up internal write
15921 buffers and wasting CPU cycles when filtering bufferevents are
15922 enabled. Fixes part of bug 3804.
15923 - Correctly notice when data has been written from a bufferevent
15924 without flushing it completely. Fixes bug 3805.
15925 - Fix a bug where server-side tunneled bufferevent-based directory
15926 streams would get closed prematurely. Fixes bug 3814.
15927 - Fix a use-after-free error with per-connection rate-limiting
15928 buckets. Fixes bug 3888.
15930 o Major bugfixes (also part of 0.2.2.31-rc):
15931 - If we're configured to write our ControlPorts to disk, only write
15932 them after switching UID and creating the data directory. This way,
15933 we don't fail when starting up with a nonexistent DataDirectory
15934 and a ControlPortWriteToFile setting based on that directory. Fixes
15935 bug 3747; bugfix on Tor 0.2.2.26-beta.
15938 - Added a new CONF_CHANGED event so that controllers can be notified
15939 of any configuration changes made by other controllers, or by the
15940 user. Implements ticket 1692.
15941 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
15942 leak when using bufferevents, and lets Libevent worry about how to
15943 best copy data out of a buffer.
15944 - Replace files in stats/ rather than appending to them. Now that we
15945 include statistics in extra-info descriptors, it makes no sense to
15946 keep old statistics forever. Implements ticket 2930.
15948 o Minor features (build compatibility):
15949 - Limited, experimental support for building with nmake and MSVC.
15950 - Provide a substitute implementation of lround() for MSVC, which
15951 apparently lacks it. Patch from Gisle Vanem.
15953 o Minor features (also part of 0.2.2.31-rc):
15954 - Update to the August 2 2011 Maxmind GeoLite Country database.
15956 o Minor bugfixes (on 0.2.3.x-alpha):
15957 - Fix a spurious warning when parsing SOCKS requests with
15958 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
15959 - Get rid of a harmless warning that could happen on relays running
15960 with bufferevents. The warning was caused by someone doing an http
15961 request to a relay's orport. Also don't warn for a few related
15962 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
15964 o Minor bugfixes (on 2.2.x and earlier):
15965 - Correct the man page to explain that HashedControlPassword and
15966 CookieAuthentication can both be set, in which case either method
15967 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15968 when we decided to allow these config options to both be set. Issue
15969 raised by bug 3898.
15970 - The "--quiet" and "--hush" options now apply not only to Tor's
15971 behavior before logs are configured, but also to Tor's behavior in
15972 the absence of configured logs. Fixes bug 3550; bugfix on
15975 o Minor bugfixes (also part of 0.2.2.31-rc):
15976 - Write several files in text mode, on OSes that distinguish text
15977 mode from binary mode (namely, Windows). These files are:
15978 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
15979 that collect those statistics; 'client_keys' and 'hostname' for
15980 hidden services that use authentication; and (in the tor-gencert
15981 utility) newly generated identity and signing keys. Previously,
15982 we wouldn't specify text mode or binary mode, leading to an
15983 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
15984 the DirRecordUsageByCountry option which would have triggered
15985 the assertion failure was added), although this assertion failure
15986 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
15987 - Selectively disable deprecation warnings on OS X because Lion
15988 started deprecating the shipped copy of openssl. Fixes bug 3643.
15989 - Remove an extra pair of quotation marks around the error
15990 message in control-port STATUS_GENERAL BUG events. Bugfix on
15991 0.1.2.6-alpha; fixes bug 3732.
15992 - When unable to format an address as a string, report its value
15993 as "???" rather than reusing the last formatted address. Bugfix
15996 o Code simplifications and refactoring:
15997 - Rewrite the listener-selection logic so that parsing which ports
15998 we want to listen on is now separate from binding to the ports
16002 - Building Tor with bufferevent support now requires Libevent
16003 2.0.13-stable or later. Previous versions of Libevent had bugs in
16004 SSL-related bufferevents and related issues that would make Tor
16005 work badly with bufferevents. Requiring 2.0.13-stable also allows
16006 Tor with bufferevents to take advantage of Libevent APIs
16007 introduced after 2.0.8-rc.
16010 Changes in version 0.2.2.32 - 2011-08-27
16011 The Tor 0.2.2 release series is dedicated to the memory of Andreas
16012 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
16013 a founder of the PETS community, a leader in our field, a mentor,
16014 and a friend. He left us with these words: "I had the possibility
16015 to contribute to this world that is not as it should be. I hope I
16016 could help in some areas to make the world a better place, and that
16017 I could also encourage other people to be engaged in improving the
16018 world. Please, stay engaged. This world needs you, your love, your
16019 initiative -- now I cannot be part of that anymore."
16021 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
16022 ready. More than two years in the making, this release features improved
16023 client performance and hidden service reliability, better compatibility
16024 for Android, correct behavior for bridges that listen on more than
16025 one address, more extensible and flexible directory object handling,
16026 better reporting of network statistics, improved code security, and
16027 many many other features and bugfixes.
16030 Changes in version 0.2.2.31-rc - 2011-08-17
16031 Tor 0.2.2.31-rc is the second and hopefully final release candidate
16032 for the Tor 0.2.2.x series.
16035 - Remove an extra pair of quotation marks around the error
16036 message in control-port STATUS_GENERAL BUG events. Bugfix on
16037 0.1.2.6-alpha; fixes bug 3732.
16038 - If we're configured to write our ControlPorts to disk, only write
16039 them after switching UID and creating the data directory. This way,
16040 we don't fail when starting up with a nonexistent DataDirectory
16041 and a ControlPortWriteToFile setting based on that directory. Fixes
16042 bug 3747; bugfix on Tor 0.2.2.26-beta.
16045 - Update to the August 2 2011 Maxmind GeoLite Country database.
16048 - Allow GETINFO fingerprint to return a fingerprint even when
16049 we have not yet built a router descriptor. Fixes bug 3577;
16050 bugfix on 0.2.0.1-alpha.
16051 - Write several files in text mode, on OSes that distinguish text
16052 mode from binary mode (namely, Windows). These files are:
16053 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
16054 that collect those statistics; 'client_keys' and 'hostname' for
16055 hidden services that use authentication; and (in the tor-gencert
16056 utility) newly generated identity and signing keys. Previously,
16057 we wouldn't specify text mode or binary mode, leading to an
16058 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
16059 the DirRecordUsageByCountry option which would have triggered
16060 the assertion failure was added), although this assertion failure
16061 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
16062 - Selectively disable deprecation warnings on OS X because Lion
16063 started deprecating the shipped copy of openssl. Fixes bug 3643.
16064 - When unable to format an address as a string, report its value
16065 as "???" rather than reusing the last formatted address. Bugfix
16069 Changes in version 0.2.3.2-alpha - 2011-07-18
16070 Tor 0.2.3.2-alpha introduces two new experimental features:
16071 microdescriptors and pluggable transports. It also continues cleaning
16072 up a variety of recently introduced features.
16075 - Clients can now use microdescriptors instead of regular descriptors
16076 to build circuits. Microdescriptors are authority-generated
16077 summaries of regular descriptors' contents, designed to change
16078 very rarely (see proposal 158 for details). This feature is
16079 designed to save bandwidth, especially for clients on slow internet
16080 connections. It's off by default for now, since nearly no caches
16081 support it, but it will be on-by-default for clients in a future
16082 version. You can use the UseMicrodescriptors option to turn it on.
16083 - Tor clients using bridges can now be configured to use a separate
16084 'transport' proxy for each bridge. This approach helps to resist
16085 censorship by allowing bridges to use protocol obfuscation
16086 plugins. It implements part of proposal 180. Implements ticket 2841.
16087 - While we're trying to bootstrap, record how many TLS connections
16088 fail in each state, and report which states saw the most failures
16089 in response to any bootstrap failures. This feature may speed up
16090 diagnosis of censorship events. Implements ticket 3116.
16092 o Major bugfixes (on 0.2.3.1-alpha):
16093 - When configuring a large set of nodes in EntryNodes (as with
16094 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
16095 random subset to be guards, and choose them in random
16096 order. Fixes bug 2798.
16097 - Tor could crash when remembering a consensus in a non-used consensus
16098 flavor without having a current consensus set. Fixes bug 3361.
16099 - Comparing an unknown address to a microdescriptor's shortened exit
16100 policy would always give a "rejected" result. Fixes bug 3599.
16101 - Using microdescriptors as a client no longer prevents Tor from
16102 uploading and downloading hidden service descriptors. Fixes
16106 - Allow nameservers with IPv6 address. Resolves bug 2574.
16107 - Accept attempts to include a password authenticator in the
16108 handshake, as supported by SOCKS5. This handles SOCKS clients that
16109 don't know how to omit a password when authenticating. Resolves
16111 - When configuring a large set of nodes in EntryNodes, and there are
16112 enough of them listed as Guard so that we don't need to consider
16113 the non-guard entries, prefer the ones listed with the Guard flag.
16114 - Check for and recover from inconsistency in the microdescriptor
16115 cache. This will make it harder for us to accidentally free a
16116 microdescriptor without removing it from the appropriate data
16117 structures. Fixes issue 3135; issue noted by "wanoskarnet".
16118 - Log SSL state transitions at log level DEBUG, log domain
16119 HANDSHAKE. This can be useful for debugging censorship events.
16120 Implements ticket 3264.
16121 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
16122 implements ticket 3439.
16124 o Minor bugfixes (on 0.2.3.1-alpha):
16125 - Do not free all general-purpose regular descriptors just
16126 because microdescriptor use is enabled. Fixes bug 3113.
16127 - Correctly link libevent_openssl when --enable-static-libevent
16128 is passed to configure. Fixes bug 3118.
16129 - Bridges should not complain during their heartbeat log messages that
16130 they are unlisted in the consensus: that's more or less the point
16131 of being a bridge. Fixes bug 3183.
16132 - Report a SIGNAL event to controllers when acting on a delayed
16133 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
16134 event to the controller if we acted on a SIGNAL NEWNYM command
16135 immediately, and otherwise not report a SIGNAL event for the
16136 command at all. Fixes bug 3349.
16137 - Fix a crash when handling the SIGNAL controller command or
16138 reporting ERR-level status events with bufferevents enabled. Found
16139 by Robert Ransom. Fixes bug 3367.
16140 - Always ship the tor-fw-helper manpage in our release tarballs.
16141 Fixes bug 3389. Reported by Stephen Walker.
16142 - Fix a class of double-mark-for-close bugs when bufferevents
16143 are enabled. Fixes bug 3403.
16144 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
16145 - Add SIGNAL to the list returned by the 'GETINFO events/names'
16146 control-port command. Fixes part of bug 3465.
16147 - Prevent using negative indices during unit test runs when read_all()
16148 fails. Spotted by coverity.
16149 - Fix a rare memory leak when checking the nodelist without it being
16150 present. Found by coverity.
16151 - Only try to download a microdescriptor-flavored consensus from
16152 a directory cache that provides them.
16154 o Minor bugfixes (on 0.2.2.x and earlier):
16155 - Assert that hidden-service-related operations are not performed
16156 using single-hop circuits. Previously, Tor would assert that
16157 client-side streams are not attached to single-hop circuits,
16158 but not that other sensitive operations on the client and service
16159 side are not performed using single-hop circuits. Fixes bug 3332;
16161 - Don't publish a new relay descriptor when we reload our onion key,
16162 unless the onion key has actually changed. Fixes bug 3263 and
16163 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
16164 - Allow GETINFO fingerprint to return a fingerprint even when
16165 we have not yet built a router descriptor. Fixes bug 3577;
16166 bugfix on 0.2.0.1-alpha.
16167 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
16168 on 0.2.2.4-alpha; fixes bug 3427.
16170 o Code simplification and refactoring:
16171 - Use tor_sscanf() in place of scanf() in more places through the
16172 code. This makes us a little more locale-independent, and
16173 should help shut up code-analysis tools that can't tell
16174 a safe sscanf string from a dangerous one.
16175 - Use tt_assert(), not tor_assert(), for checking for test failures.
16176 This makes the unit tests more able to go on in the event that
16178 - Split connection_about_to_close() into separate functions for each
16182 - On Windows, we now define the _WIN32_WINNT macros only if they
16183 are not already defined. This lets the person building Tor decide,
16184 if they want, to require a later version of Windows.
16187 Changes in version 0.2.2.30-rc - 2011-07-07
16188 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
16189 series. It fixes a few smaller bugs, but generally appears stable.
16190 Please test it and let us know whether it is!
16193 - Send a SUCCEEDED stream event to the controller when a reverse
16194 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
16195 discovered by katmagic.
16196 - Always NUL-terminate the sun_path field of a sockaddr_un before
16197 passing it to the kernel. (Not a security issue: kernels are
16198 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16199 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16200 - Don't stack-allocate the list of supplementary GIDs when we're
16201 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16202 could take up to 256K, which is way too much stack. Found by
16203 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16204 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
16205 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
16206 fixes part of bug 3465.
16207 - Fix a memory leak when receiving a descriptor for a hidden
16208 service we didn't ask for. Found by Coverity; CID #30. Bugfix
16212 - Update to the July 1 2011 Maxmind GeoLite Country database.
16215 Changes in version 0.2.2.29-beta - 2011-06-20
16216 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
16217 have bridge lines in their torrc but don't want to use them; gets
16218 us closer to having the control socket feature working on Debian;
16219 and fixes a variety of smaller bugs.
16222 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
16223 When we changed the default behavior to "use bridges if any
16224 are listed in the torrc", we surprised users who had bridges
16225 in their torrc files but who didn't actually want to use them.
16226 Partial resolution for bug 3354.
16229 - Don't attach new streams to old rendezvous circuits after SIGNAL
16230 NEWNYM. Previously, we would keep using an existing rendezvous
16231 circuit if it remained open (i.e. if it were kept open by a
16232 long-lived stream, or if a new stream were attached to it before
16233 Tor could notice that it was old and no longer in use). Bugfix on
16234 0.1.1.15-rc; fixes bug 3375.
16237 - Fix a bug when using ControlSocketsGroupWritable with User. The
16238 directory's group would be checked against the current group, not
16239 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
16240 bugfix on 0.2.2.26-beta.
16241 - Make connection_printf_to_buf()'s behavior sane. Its callers
16242 expect it to emit a CRLF iff the format string ends with CRLF;
16243 it actually emitted a CRLF iff (a) the format string ended with
16244 CRLF or (b) the resulting string was over 1023 characters long or
16245 (c) the format string did not end with CRLF *and* the resulting
16246 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
16247 fixes part of bug 3407.
16248 - Make send_control_event_impl()'s behavior sane. Its callers
16249 expect it to always emit a CRLF at the end of the string; it
16250 might have emitted extra control characters as well. Bugfix on
16251 0.1.1.9-alpha; fixes another part of bug 3407.
16252 - Make crypto_rand_int() check the value of its input correctly.
16253 Previously, it accepted values up to UINT_MAX, but could return a
16254 negative number if given a value above INT_MAX+1. Found by George
16255 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
16256 - Avoid a segfault when reading a malformed circuit build state
16257 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
16259 - When asked about a DNS record type we don't support via a
16260 client DNSPort, reply with NOTIMPL rather than an empty
16261 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
16262 - Fix a rare memory leak during stats writing. Found by coverity.
16265 - Update to the June 1 2011 Maxmind GeoLite Country database.
16267 o Code simplifications and refactoring:
16268 - Remove some dead code as indicated by coverity.
16269 - Remove a few dead assignments during router parsing. Found by
16271 - Add some forgotten return value checks during unit tests. Found
16273 - Don't use 1-bit wide signed bit fields. Found by coverity.
16276 Changes in version 0.2.2.28-beta - 2011-06-04
16277 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
16278 fixed a big bug in whether relays stay in the consensus consistently,
16279 we moved closer to handling bridges and hidden services correctly,
16280 and we started the process of better handling the dreaded "my Vidalia
16281 died, and now my Tor demands a password when I try to reconnect to it"
16285 - Don't decide to make a new descriptor when receiving a HUP signal.
16286 This bug has caused a lot of 0.2.2.x relays to disappear from the
16287 consensus periodically. Fixes the most common case of triggering
16288 bug 1810; bugfix on 0.2.2.7-alpha.
16289 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
16290 - Don't try to build descriptors if "ORPort auto" is set and we
16291 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
16293 - Resolve a crash that occurred when setting BridgeRelay to 1 with
16294 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
16295 - Apply circuit timeouts to opened hidden-service-related circuits
16296 based on the correct start time. Previously, we would apply the
16297 circuit build timeout based on time since the circuit's creation;
16298 it was supposed to be applied based on time since the circuit
16299 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
16300 - Use the same circuit timeout for client-side introduction
16301 circuits as for other four-hop circuits, rather than the timeout
16302 for single-hop directory-fetch circuits; the shorter timeout may
16303 have been appropriate with the static circuit build timeout in
16304 0.2.1.x and earlier, but caused many hidden service access attempts
16305 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
16306 on 0.2.2.2-alpha; fixes another part of bug 1297.
16307 - In ticket 2511 we fixed a case where you could use an unconfigured
16308 bridge if you had configured it as a bridge the last time you ran
16309 Tor. Now fix another edge case: if you had configured it as a bridge
16310 but then switched to a different bridge via the controller, you
16311 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
16315 - Add an __OwningControllerProcess configuration option and a
16316 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
16317 that when it exits, Tor will shut down. Implements feature 3049.
16318 - If "UseBridges 1" is set and no bridges are configured, Tor will
16319 now refuse to build any circuits until some bridges are set.
16320 If "UseBridges auto" is set, Tor will use bridges if they are
16321 configured and we are not running as a server, but otherwise will
16322 make circuits as usual. The new default is "auto". Patch by anonym,
16323 so the Tails LiveCD can stop automatically revealing you as a Tor
16327 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16328 - Remove a trailing asterisk from "exit-policy/default" in the
16329 output of the control port command "GETINFO info/names". Bugfix
16331 - Use a wide type to hold sockets when built for 64-bit Windows builds.
16333 - Warn when the user configures two HiddenServiceDir lines that point
16334 to the same directory. Bugfix on 0.0.6 (the version introducing
16335 HiddenServiceDir); fixes bug 3289.
16336 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
16337 part of bug 2748; bugfix on 0.2.0.10-alpha.
16338 - Log malformed requests for rendezvous descriptors as protocol
16339 warnings, not warnings. Also, use a more informative log message
16340 in case someone sees it at log level warning without prior
16341 info-level messages. Fixes the other part of bug 2748; bugfix
16343 - Clear the table recording the time of the last request for each
16344 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
16345 Previously, we would clear our HS descriptor cache on SIGNAL
16346 NEWNYM, but if we had previously retrieved a descriptor (or tried
16347 to) from every directory responsible for it, we would refuse to
16348 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
16350 - Fix a log message that said "bits" while displaying a value in
16351 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
16353 - When checking for 1024-bit keys, check for 1024 bits, not 128
16354 bytes. This allows Tor to correctly discard keys of length 1017
16355 through 1023. Bugfix on 0.0.9pre5.
16358 - Relays now log the reason for publishing a new relay descriptor,
16359 so we have a better chance of hunting down instances of bug 1810.
16360 Resolves ticket 3252.
16361 - Revise most log messages that refer to nodes by nickname to
16362 instead use the "$key=nickname at address" format. This should be
16363 more useful, especially since nicknames are less and less likely
16364 to be unique. Resolves ticket 3045.
16365 - Log (at info level) when purging pieces of hidden-service-client
16366 state because of SIGNAL NEWNYM.
16369 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16370 anything since 0.2.1.16-rc.
16373 Changes in version 0.2.2.27-beta - 2011-05-18
16374 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
16375 release, and also adds a few more general bugfixes.
16378 - Fix a crash bug when changing bridges in a running Tor process.
16379 Fixes bug 3213; bugfix on 0.2.2.26-beta.
16380 - When the controller configures a new bridge, don't wait 10 to 60
16381 seconds before trying to fetch its descriptor. Bugfix on
16382 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
16385 - Require that onion keys have exponent 65537 in microdescriptors too.
16386 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
16387 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
16388 Changed the limit to 512 characters by removing base64 newlines.
16389 Fixes bug 2752. Fix by Michael Yakubovich.
16390 - When a client starts or stops using bridges, never use a circuit
16391 that was built before the configuration change. This behavior could
16392 put at risk a user who uses bridges to ensure that her traffic
16393 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
16397 Changes in version 0.2.2.26-beta - 2011-05-17
16398 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
16399 also introduces a new "socksport auto" approach that should make it
16400 easier to run multiple Tors on the same system, and does a lot of
16401 cleanup to get us closer to a release candidate.
16403 o Security/privacy fixes:
16404 - Replace all potentially sensitive memory comparison operations
16405 with versions whose runtime does not depend on the data being
16406 compared. This will help resist a class of attacks where an
16407 adversary can use variations in timing information to learn
16408 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16409 implementation by Robert Ransom based partially on code by DJB.)
16410 - When receiving a hidden service descriptor, check that it is for
16411 the hidden service we wanted. Previously, Tor would store any
16412 hidden service descriptors that a directory gave it, whether it
16413 wanted them or not. This wouldn't have let an attacker impersonate
16414 a hidden service, but it did let directories pre-seed a client
16415 with descriptors that it didn't want. Bugfix on 0.0.6.
16416 - On SIGHUP, do not clear out all TrackHostExits mappings, client
16417 DNS cache entries, and virtual address mappings: that's what
16418 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
16421 - The options SocksPort, ControlPort, and so on now all accept a
16422 value "auto" that opens a socket on an OS-selected port. A
16423 new ControlPortWriteToFile option tells Tor to write its
16424 actual control port or ports to a chosen file. If the option
16425 ControlPortFileGroupReadable is set, the file is created as
16426 group-readable. Now users can run two Tor clients on the same
16427 system without needing to manually mess with parameters. Resolves
16428 part of ticket 3076.
16429 - Set SO_REUSEADDR on all sockets, not just listeners. This should
16430 help busy exit nodes avoid running out of useable ports just
16431 because all the ports have been used in the near past. Resolves
16435 - New "GETINFO net/listeners/(type)" controller command to return
16436 a list of addresses and ports that are bound for listeners for a
16437 given connection type. This is useful when the user has configured
16438 "SocksPort auto" and the controller needs to know which port got
16439 chosen. Resolves another part of ticket 3076.
16440 - Add a new ControlSocketsGroupWritable configuration option: when
16441 it is turned on, ControlSockets are group-writeable by the default
16442 group of the current user. Patch by Jérémy Bobbio; implements
16444 - Tor now refuses to create a ControlSocket in a directory that is
16445 world-readable (or group-readable if ControlSocketsGroupWritable
16446 is 0). This is necessary because some operating systems do not
16447 enforce permissions on an AF_UNIX sockets. Permissions on the
16448 directory holding the socket, however, seems to work everywhere.
16449 - Rate-limit a warning about failures to download v2 networkstatus
16450 documents. Resolves part of bug 1352.
16451 - Backport code from 0.2.3.x that allows directory authorities to
16452 clean their microdescriptor caches. Needed to resolve bug 2230.
16453 - When an HTTPS proxy reports "403 Forbidden", we now explain
16454 what it means rather than calling it an unexpected status code.
16455 Closes bug 2503. Patch from Michael Yakubovich.
16456 - Update to the May 1 2011 Maxmind GeoLite Country database.
16459 - Authorities now clean their microdesc cache periodically and when
16460 reading from disk initially, not only when adding new descriptors.
16461 This prevents a bug where we could lose microdescriptors. Bugfix
16462 on 0.2.2.6-alpha. Fixes bug 2230.
16463 - Do not crash when our configuration file becomes unreadable, for
16464 example due to a permissions change, between when we start up
16465 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
16467 - Avoid a bug that would keep us from replacing a microdescriptor
16468 cache on Windows. (We would try to replace the file while still
16469 holding it open. That's fine on Unix, but Windows doesn't let us
16470 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
16471 - Add missing explanations for the authority-related torrc options
16472 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
16473 man page. Resolves issue 2379.
16474 - As an authority, do not upload our own vote or signature set to
16475 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
16476 it would get flagged as a duplicate. Resolves bug 3026.
16477 - Accept hidden service descriptors if we think we might be a hidden
16478 service directory, regardless of what our consensus says. This
16479 helps robustness, since clients and hidden services can sometimes
16480 have a more up-to-date view of the network consensus than we do,
16481 and if they think that the directory authorities list us a HSDir,
16482 we might actually be one. Related to bug 2732; bugfix on
16484 - When a controller changes TrackHostExits, remove mappings for
16485 hosts that should no longer have their exits tracked. Bugfix on
16487 - When a controller changes VirtualAddrNetwork, remove any mappings
16488 for hosts that were automapped to the old network. Bugfix on
16490 - When a controller changes one of the AutomapHosts* options, remove
16491 any mappings for hosts that should no longer be automapped. Bugfix
16493 - Do not reset the bridge descriptor download status every time we
16494 re-parse our configuration or get a configuration change. Fixes
16495 bug 3019; bugfix on 0.2.0.3-alpha.
16497 o Minor bugfixes (code cleanup):
16498 - When loading the microdesc journal, remember its current size.
16499 In 0.2.2, this helps prevent the microdesc journal from growing
16500 without limit on authorities (who are the only ones to use it in
16501 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
16502 Fix posted by "cypherpunks."
16503 - The microdesc journal is supposed to get rebuilt only if it is
16504 at least _half_ the length of the store, not _twice_ the length
16505 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
16506 - Fix a potential null-pointer dereference while computing a
16507 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
16509 - Avoid a possible null-pointer dereference when rebuilding the mdesc
16510 cache without actually having any descriptors to cache. Bugfix on
16511 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
16512 - If we fail to compute the identity digest of a v3 legacy keypair,
16513 warn, and don't use a buffer-full of junk instead. Bugfix on
16514 0.2.1.1-alpha; fixes bug 3106.
16515 - Resolve an untriggerable issue in smartlist_string_num_isin(),
16516 where if the function had ever in the future been used to check
16517 for the presence of a too-large number, it would have given an
16518 incorrect result. (Fortunately, we only used it for 16-bit
16519 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
16520 - Require that introduction point keys and onion handshake keys
16521 have a public exponent of 65537. Starts to fix bug 3207; bugfix
16524 o Removed features:
16525 - Caches no longer download and serve v2 networkstatus documents
16526 unless FetchV2Networkstatus flag is set: these documents haven't
16527 haven't been used by clients or relays since 0.2.0.x. Resolves
16531 Changes in version 0.2.3.1-alpha - 2011-05-05
16532 Tor 0.2.3.1-alpha adds some new experimental features, including support
16533 for an improved network IO backend, IOCP networking on Windows,
16534 microdescriptor caching, "fast-start" support for streams, and automatic
16535 home router configuration. There are also numerous internal improvements
16536 to try to make the code easier for developers to work with.
16538 This is the first alpha release in a new series, so expect there to be
16539 bugs. Users who would rather test out a more stable branch should
16540 stay with 0.2.2.x for now.
16543 - Tor can now optionally build with the "bufferevents" buffered IO
16544 backend provided by Libevent 2. To use this feature, make sure you
16545 have the latest possible version of Libevent, and pass the
16546 --enable-bufferevents flag to configure when building Tor from
16547 source. This feature will make our networking code more flexible,
16548 let us stack layers on each other, and let us use more efficient
16549 zero-copy transports where available.
16550 - As an experimental feature, Tor can use IOCP for networking on Windows.
16551 Once this code is tuned and optimized, it promises much better
16552 performance than the select-based backend we've used in the past. To
16553 try this feature, you must build Tor with Libevent 2, configure Tor
16554 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
16555 your torrc. There are known bugs here: only try this if you can help
16556 debug it as it breaks.
16557 - The EntryNodes option can now include country codes like {de} or IP
16558 addresses or network masks. Previously we had disallowed these options
16559 because we didn't have an efficient way to keep the list up to
16560 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
16561 - Exit nodes now accept and queue data on not-yet-connected streams.
16562 Previously, the client wasn't allowed to send data until the stream was
16563 connected, which slowed down all connections. This change will enable
16564 clients to perform a "fast-start" on streams and send data without
16565 having to wait for a confirmation that the stream has opened. (Patch
16566 from Ian Goldberg; implements the server side of Proposal 174.)
16567 - Tor now has initial support for automatic port mapping on the many
16568 home routers that support NAT-PMP or UPnP. (Not yet supported on
16569 Windows). To build the support code, you'll need to have libnatpnp
16570 library and/or the libminiupnpc library, and you'll need to enable the
16571 feature specifically by passing "--enable-upnp" and/or
16572 "--enable-natpnp" to configure. To turn it on, use the new
16573 PortForwarding option.
16574 - Caches now download, cache, and serve multiple "flavors" of the
16575 consensus, including a flavor that describes microdescriptors.
16576 - Caches now download, cache, and serve microdescriptors -- small
16577 summaries of router descriptors that are authenticated by all of the
16578 directory authorities. Once enough caches are running this code,
16579 clients will be able to save significant amounts of directory bandwidth
16580 by downloading microdescriptors instead of router descriptors.
16583 - Make logging resolution configurable with a new LogTimeGranularity
16584 option, and change the default from 1 millisecond to 1 second.
16585 Implements enhancement 1668.
16586 - We log which torrc file we're using on startup. Implements ticket
16588 - Ordinarily, Tor does not count traffic from private addresses (like
16589 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
16590 There is now a new option, CountPrivateBandwidth, to disable this
16591 behavior. Patch from Daniel Cagara.
16592 - New --enable-static-tor configure option for building Tor as
16593 statically as possible. Idea, general hackery and thoughts from
16594 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
16596 - If you set the NumCPUs option to 0, Tor will now try to detect how
16597 many CPUs you have. This is the new default behavior.
16598 - Turn on directory request statistics by default and include them in
16599 extra-info descriptors. Don't break if we have no GeoIP database.
16600 - Relays that set "ConnDirectionStatistics 1" write statistics on the
16601 bidirectional use of connections to disk every 24 hours.
16602 - Add a GeoIP file digest to the extra-info descriptor. Implements
16604 - The NodeFamily option -- which let you declare that you want to
16605 consider nodes to be part of a family whether they list themselves
16606 that way or not -- now allows IP address ranges and country codes.
16607 - Add a new 'Heartbeat' log message type to periodically log a message
16608 describing Tor's status at level Notice. This feature is meant for
16609 operators who log at notice, and want to make sure that their Tor
16610 server is still working. Implementation by George Kadianakis.
16612 o Minor bugfixes (on 0.2.2.25-alpha):
16613 - When loading the microdesc journal, remember its current size.
16614 In 0.2.2, this helps prevent the microdesc journal from growing
16615 without limit on authorities (who are the only ones to use it in
16616 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
16617 Fix posted by "cypherpunks."
16618 - The microdesc journal is supposed to get rebuilt only if it is
16619 at least _half_ the length of the store, not _twice_ the length
16620 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
16621 - If as an authority we fail to compute the identity digest of a v3
16622 legacy keypair, warn, and don't use a buffer-full of junk instead.
16623 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
16624 - Authorities now clean their microdesc cache periodically and when
16625 reading from disk initially, not only when adding new descriptors.
16626 This prevents a bug where we could lose microdescriptors. Bugfix
16629 o Minor features (controller):
16630 - Add a new SIGNAL event to the controller interface so that
16631 controllers can be notified when Tor handles a signal. Resolves
16632 issue 1955. Patch by John Brooks.
16633 - Add a new GETINFO option to get total bytes read and written. Patch
16634 from pipe, revised by atagar. Resolves ticket 2345.
16635 - Implement some GETINFO controller fields to provide information about
16636 the Tor process's pid, euid, username, and resource limits.
16639 - Our build system requires automake 1.6 or later to create the
16640 Makefile.in files. Previously, you could have used 1.4.
16641 This only affects developers and people building Tor from git;
16642 people who build Tor from the source distribution without changing
16643 the Makefile.am files should be fine.
16644 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
16645 so on. This is more robust against some of the failure modes
16646 associated with running the autotools pieces on their own.
16648 o Minor packaging issues:
16649 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
16650 already created. Patch from Andreas Stieger. Fixes bug 2573.
16652 o Code simplifications and refactoring:
16653 - A major revision to our internal node-selecting and listing logic.
16654 Tor already had at least two major ways to look at the question of
16655 "which Tor servers do we know about": a list of router descriptors,
16656 and a list of entries in the current consensus. With
16657 microdescriptors, we're adding a third. Having so many systems
16658 without an abstraction layer over them was hurting the codebase.
16659 Now, we have a new "node_t" abstraction that presents a consistent
16660 interface to a client's view of a Tor node, and holds (nearly) all
16661 of the mutable state formerly in routerinfo_t and routerstatus_t.
16662 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
16663 no longer link against Libevent: they never used it, but
16664 our library structure used to force them to link it.
16666 o Removed features:
16667 - Remove some old code to work around even older versions of Tor that
16668 used forked processes to handle DNS requests. Such versions of Tor
16669 are no longer in use as servers.
16671 o Documentation fixes:
16672 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
16673 - Add missing documentation for the authority-related torrc options
16674 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
16678 Changes in version 0.2.2.25-alpha - 2011-04-29
16679 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
16680 robust, routers no longer overreport their bandwidth, Win7 should crash
16681 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
16682 now prevents hidden service-related activity from being linkable. It
16683 provides more information to Vidalia so you can see if your bridge is
16684 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
16685 StrictNodes configuration options to make them more reliable, more
16686 understandable, and more regularly applied. If you use those options,
16687 please see the revised documentation for them in the manual page.
16690 - Relays were publishing grossly inflated bandwidth values because
16691 they were writing their state files wrong--now they write the
16692 correct value. Also, resume reading bandwidth history from the
16693 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
16694 - Improve hidden service robustness: When we find that we have
16695 extended a hidden service's introduction circuit to a relay not
16696 listed as an introduction point in the HS descriptor we currently
16697 have, retry with an introduction point from the current
16698 descriptor. Previously we would just give up. Fixes bugs 1024 and
16699 1930; bugfix on 0.2.0.10-alpha.
16700 - Clients now stop trying to use an exit node associated with a given
16701 destination by TrackHostExits if they fail to reach that exit node.
16702 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
16703 - Fix crash bug on platforms where gmtime and localtime can return
16704 NULL. Windows 7 users were running into this one. Fixes part of bug
16705 2077. Bugfix on all versions of Tor. Found by boboper.
16707 o Security and stability fixes:
16708 - Don't double-free a parsable, but invalid, microdescriptor, even if
16709 it is followed in the blob we're parsing by an unparsable
16710 microdescriptor. Fixes an issue reported in a comment on bug 2954.
16711 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
16712 - If the Nickname configuration option isn't given, Tor would pick a
16713 nickname based on the local hostname as the nickname for a relay.
16714 Because nicknames are not very important in today's Tor and the
16715 "Unnamed" nickname has been implemented, this is now problematic
16716 behavior: It leaks information about the hostname without being
16717 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
16718 introduced the Unnamed nickname. Reported by tagnaq.
16719 - Fix an uncommon assertion failure when running with DNSPort under
16720 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
16721 - Avoid linkability based on cached hidden service descriptors: forget
16722 all hidden service descriptors cached as a client when processing a
16723 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
16726 - Export GeoIP information on bridge usage to controllers even if we
16727 have not yet been running for 24 hours. Now Vidalia bridge operators
16728 can get more accurate and immediate feedback about their
16729 contributions to the network.
16731 o Major features and bugfixes (node selection):
16732 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
16733 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
16734 options. Previously, we had been ambiguous in describing what
16735 counted as an "exit" node, and what operations exactly "StrictNodes
16736 0" would permit. This created confusion when people saw nodes built
16737 through unexpected circuits, and made it hard to tell real bugs from
16738 surprises. Now the intended behavior is:
16739 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
16740 a node that delivers user traffic outside the Tor network.
16741 . "Entry", in the context of EntryNodes, means a node used as the
16742 first hop of a multihop circuit. It doesn't include direct
16743 connections to directory servers.
16744 . "ExcludeNodes" applies to all nodes.
16745 . "StrictNodes" changes the behavior of ExcludeNodes only. When
16746 StrictNodes is set, Tor should avoid all nodes listed in
16747 ExcludeNodes, even when it will make user requests fail. When
16748 StrictNodes is *not* set, then Tor should follow ExcludeNodes
16749 whenever it can, except when it must use an excluded node to
16750 perform self-tests, connect to a hidden service, provide a
16751 hidden service, fulfill a .exit request, upload directory
16752 information, or fetch directory information.
16753 Collectively, the changes to implement the behavior fix bug 1090.
16754 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
16755 a node is listed in both, it's treated as excluded.
16756 - ExcludeNodes now applies to directory nodes -- as a preference if
16757 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
16758 Don't exclude all the directory authorities and set StrictNodes to 1
16759 unless you really want your Tor to break.
16760 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
16761 - ExcludeExitNodes now overrides .exit requests.
16762 - We don't use bridges listed in ExcludeNodes.
16763 - When StrictNodes is 1:
16764 . We now apply ExcludeNodes to hidden service introduction points
16765 and to rendezvous points selected by hidden service users. This
16766 can make your hidden service less reliable: use it with caution!
16767 . If we have used ExcludeNodes on ourself, do not try relay
16768 reachability self-tests.
16769 . If we have excluded all the directory authorities, we will not
16770 even try to upload our descriptor if we're a relay.
16771 . Do not honor .exit requests to an excluded node.
16772 - Remove a misfeature that caused us to ignore the Fast/Stable flags
16773 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
16774 - When the set of permitted nodes changes, we now remove any mappings
16775 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
16777 - We never cannibalize a circuit that had excluded nodes on it, even
16778 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
16779 - Revert a change where we would be laxer about attaching streams to
16780 circuits than when building the circuits. This was meant to prevent
16781 a set of bugs where streams were never attachable, but our improved
16782 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
16783 - Keep track of how many times we launch a new circuit to handle a
16784 given stream. Too many launches could indicate an inconsistency
16785 between our "launch a circuit to handle this stream" logic and our
16786 "attach this stream to one of the available circuits" logic.
16787 - Improve log messages related to excluded nodes.
16790 - Fix a spurious warning when moving from a short month to a long
16791 month on relays with month-based BandwidthAccounting. Bugfix on
16792 0.2.2.17-alpha; fixes bug 3020.
16793 - When a client finds that an origin circuit has run out of 16-bit
16794 stream IDs, we now mark it as unusable for new streams. Previously,
16795 we would try to close the entire circuit. Bugfix on 0.0.6.
16796 - Add a forgotten cast that caused a compile warning on OS X 10.6.
16797 Bugfix on 0.2.2.24-alpha.
16798 - Be more careful about reporting the correct error from a failed
16799 connect() system call. Under some circumstances, it was possible to
16800 look at an incorrect value for errno when sending the end reason.
16801 Bugfix on 0.1.0.1-rc.
16802 - Correctly handle an "impossible" overflow cases in connection byte
16803 counting, where we write or read more than 4GB on an edge connection
16804 in a single second. Bugfix on 0.1.2.8-beta.
16805 - Correct the warning displayed when a rendezvous descriptor exceeds
16806 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16808 - Clients and hidden services now use HSDir-flagged relays for hidden
16809 service descriptor downloads and uploads even if the relays have no
16810 DirPort set and the client has disabled TunnelDirConns. This will
16811 eventually allow us to give the HSDir flag to relays with no
16812 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
16813 - Downgrade "no current certificates known for authority" message from
16814 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
16815 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
16816 2917. Bugfix on 0.1.1.1-alpha.
16817 - Only limit the lengths of single HS descriptors, even when multiple
16818 HS descriptors are published to an HSDir relay in a single POST
16819 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
16820 - Write the current time into the LastWritten line in our state file,
16821 rather than the time from the previous write attempt. Also, stop
16822 trying to use a time of -1 in our log statements. Fixes bug 3039;
16823 bugfix on 0.2.2.14-alpha.
16824 - Be more consistent in our treatment of file system paths. "~" should
16825 get expanded to the user's home directory in the Log config option.
16826 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
16827 feature for the -f and --DataDirectory options.
16830 - Make sure every relay writes a state file at least every 12 hours.
16831 Previously, a relay could go for weeks without writing its state
16832 file, and on a crash could lose its bandwidth history, capacity
16833 estimates, client country statistics, and so on. Addresses bug 3012.
16834 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
16835 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
16836 clients are already deprecated because of security bugs.
16837 - Don't allow v0 hidden service authorities to act as clients.
16838 Required by fix for bug 3000.
16839 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
16840 by fix for bug 3000.
16841 - Ensure that no empty [dirreq-](read|write)-history lines are added
16842 to an extrainfo document. Implements ticket 2497.
16844 o Code simplification and refactoring:
16845 - Remove workaround code to handle directory responses from servers
16846 that had bug 539 (they would send HTTP status 503 responses _and_
16847 send a body too). Since only server versions before
16848 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
16849 keep the workaround in place.
16850 - Remove the old 'fuzzy time' logic. It was supposed to be used for
16851 handling calculations where we have a known amount of clock skew and
16852 an allowed amount of unknown skew. But we only used it in three
16853 places, and we never adjusted the known/unknown skew values. This is
16854 still something we might want to do someday, but if we do, we'll
16855 want to do it differently.
16856 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16857 None of the cases where we did this before were wrong, but by making
16858 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16859 - Use GetTempDir to find the proper temporary directory location on
16860 Windows when generating temporary files for the unit tests. Patch by
16864 Changes in version 0.2.2.24-alpha - 2011-04-08
16865 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
16866 prevented Tor clients from effectively using "multihomed" bridges,
16867 that is, bridges that listen on multiple ports or IP addresses so users
16868 can continue to use some of their addresses even if others get blocked.
16871 - Fix a bug where bridge users who configure the non-canonical
16872 address of a bridge automatically switch to its canonical
16873 address. If a bridge listens at more than one address, it should be
16874 able to advertise those addresses independently and any non-blocked
16875 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
16877 - If you configured Tor to use bridge A, and then quit and
16878 configured Tor to use bridge B instead, it would happily continue
16879 to use bridge A if it's still reachable. While this behavior is
16880 a feature if your goal is connectivity, in some scenarios it's a
16881 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
16882 - Directory authorities now use data collected from their own
16883 uptime observations when choosing whether to assign the HSDir flag
16884 to relays, instead of trusting the uptime value the relay reports in
16885 its descriptor. This change helps prevent an attack where a small
16886 set of nodes with frequently-changing identity keys can blackhole
16887 a hidden service. (Only authorities need upgrade; others will be
16888 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
16891 - When we restart our relay, we might get a successful connection
16892 from the outside before we've started our reachability tests,
16893 triggering a warning: "ORPort found reachable, but I have no
16894 routerinfo yet. Failing to inform controller of success." This
16895 bug was harmless unless Tor is running under a controller
16896 like Vidalia, in which case the controller would never get a
16897 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16899 - Make directory authorities more accurate at recording when
16900 relays that have failed several reachability tests became
16901 unreachable, so we can provide more accuracy at assigning Stable,
16902 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
16903 - Fix an issue that prevented static linking of libevent on
16904 some platforms (notably Linux). Fixes bug 2698; bugfix on
16905 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
16906 the --with-static-libevent configure option).
16907 - We now ask the other side of a stream (the client or the exit)
16908 for more data on that stream when the amount of queued data on
16909 that stream dips low enough. Previously, we wouldn't ask the
16910 other side for more data until either it sent us more data (which
16911 it wasn't supposed to do if it had exhausted its window!) or we
16912 had completely flushed all our queued data. This flow control fix
16913 should improve throughput. Fixes bug 2756; bugfix on the earliest
16914 released versions of Tor (svn commit r152).
16915 - Avoid a double-mark-for-free warning when failing to attach a
16916 transparent proxy connection. (We thought we had fixed this in
16917 0.2.2.23-alpha, but it turns out our fix was checking the wrong
16918 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
16919 bug) and 0.2.2.23-alpha (the incorrect fix).
16920 - When warning about missing zlib development packages during compile,
16921 give the correct package names. Bugfix on 0.2.0.1-alpha.
16924 - Directory authorities now log the source of a rejected POSTed v3
16925 networkstatus vote.
16926 - Make compilation with clang possible when using
16927 --enable-gcc-warnings by removing two warning options that clang
16928 hasn't implemented yet and by fixing a few warnings. Implements
16930 - When expiring circuits, use microsecond timers rather than
16931 one-second timers. This can avoid an unpleasant situation where a
16932 circuit is launched near the end of one second and expired right
16933 near the beginning of the next, and prevent fluctuations in circuit
16935 - Use computed circuit-build timeouts to decide when to launch
16936 parallel introduction circuits for hidden services. (Previously,
16937 we would retry after 15 seconds.)
16938 - Update to the April 1 2011 Maxmind GeoLite Country database.
16941 - Create the /var/run/tor directory on startup on OpenSUSE if it is
16942 not already created. Patch from Andreas Stieger. Fixes bug 2573.
16944 o Documentation changes:
16945 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
16946 - Resolve all doxygen warnings except those for missing documentation.
16948 - Add doxygen documentation for more functions, fields, and types.
16951 Changes in version 0.2.2.23-alpha - 2011-03-08
16952 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
16953 they restart they don't lose their bandwidth capacity estimate. This
16954 release also fixes a diverse set of user-facing bugs, ranging from
16955 relays overrunning their rate limiting to clients falsely warning about
16956 clock skew to bridge descriptor leaks by our bridge directory authority.
16959 - Stop sending a CLOCK_SKEW controller status event whenever
16960 we fetch directory information from a relay that has a wrong clock.
16961 Instead, only inform the controller when it's a trusted authority
16962 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16963 the rest of bug 1074.
16964 - Fix an assert in parsing router descriptors containing IPv6
16965 addresses. This one took down the directory authorities when
16966 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16967 - Make the bridge directory authority refuse to answer directory
16968 requests for "all" descriptors. It used to include bridge
16969 descriptors in its answer, which was a major information leak.
16970 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16971 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16972 Tor would ignore their RelayBandwidthBurst setting,
16973 potentially using more bandwidth than expected. Bugfix on
16974 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16975 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16976 hidserv" in her torrc. The 'hidserv' argument never controlled
16977 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16980 - Relays now save observed peak bandwidth throughput rates to their
16981 state file (along with total usage, which was already saved)
16982 so that they can determine their correct estimated bandwidth on
16983 restart. Resolves bug 1863, where Tor relays would reset their
16984 estimated bandwidth to 0 after restarting.
16985 - Directory authorities now take changes in router IP address and
16986 ORPort into account when determining router stability. Previously,
16987 if a router changed its IP or ORPort, the authorities would not
16988 treat it as having any downtime for the purposes of stability
16989 calculation, whereas clients would experience downtime since the
16990 change could take a while to propagate to them. Resolves issue 1035.
16991 - Enable Address Space Layout Randomization (ASLR) and Data Execution
16992 Prevention (DEP) by default on Windows to make it harder for
16993 attackers to exploit vulnerabilities. Patch from John Brooks.
16995 o Minor bugfixes (on 0.2.1.x and earlier):
16996 - Fix a rare crash bug that could occur when a client was configured
16997 with a large number of bridges. Fixes bug 2629; bugfix on
16998 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16999 - Avoid a double mark-for-free warning when failing to attach a
17000 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
17002 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
17003 found by "cypherpunks". This bug was introduced before the first
17004 Tor release, in svn commit r110.
17005 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
17006 don't mention them in the manpage. Fixes bug 2450; issue
17007 spotted by keb and G-Lo.
17008 - Fix a bug in bandwidth history state parsing that could have been
17009 triggered if a future version of Tor ever changed the timing
17010 granularity at which bandwidth history is measured. Bugfix on
17011 Tor 0.1.1.11-alpha.
17012 - When a relay decides that its DNS is too broken for it to serve
17013 as an exit server, it advertised itself as a non-exit, but
17014 continued to act as an exit. This could create accidental
17015 partitioning opportunities for users. Instead, if a relay is
17016 going to advertise reject *:* as its exit policy, it should
17017 really act with exit policy "reject *:*". Fixes bug 2366.
17018 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
17019 - In the special case where you configure a public exit relay as your
17020 bridge, Tor would be willing to use that exit relay as the last
17021 hop in your circuit as well. Now we fail that circuit instead.
17022 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
17023 - Fix a bug with our locking implementation on Windows that couldn't
17024 correctly detect when a file was already locked. Fixes bug 2504,
17025 bugfix on 0.2.1.6-alpha.
17026 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
17027 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
17029 - Set target port in get_interface_address6() correctly. Bugfix
17030 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
17031 - Directory authorities are now more robust to hops back in time
17032 when calculating router stability. Previously, if a run of uptime
17033 or downtime appeared to be negative, the calculation could give
17034 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
17036 - Fix an assert that got triggered when using the TestingTorNetwork
17037 configuration option and then issuing a GETINFO config-text control
17038 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
17040 o Minor bugfixes (on 0.2.2.x):
17041 - Clients should not weight BadExit nodes as Exits in their node
17042 selection. Similarly, directory authorities should not count BadExit
17043 bandwidth as Exit bandwidth when computing bandwidth-weights.
17044 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
17045 - Correctly clear our dir_read/dir_write history when there is an
17046 error parsing any bw history value from the state file. Bugfix on
17047 Tor 0.2.2.15-alpha.
17048 - Resolve a bug in verifying signatures of directory objects
17049 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
17050 Fixes bug 2409. Found by "piebeer".
17051 - Bridge authorities no longer crash on SIGHUP when they try to
17052 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
17056 - Log less aggressively about circuit timeout changes, and improve
17057 some other circuit timeout messages. Resolves bug 2004.
17058 - Log a little more clearly about the times at which we're no longer
17059 accepting new connections. Resolves bug 2181.
17060 - Reject attempts at the client side to open connections to private
17061 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
17062 a randomly chosen exit node. Attempts to do so are always
17063 ill-defined, generally prevented by exit policies, and usually
17064 in error. This will also help to detect loops in transparent
17065 proxy configurations. You can disable this feature by setting
17066 "ClientRejectInternalAddresses 0" in your torrc.
17067 - Always treat failure to allocate an RSA key as an unrecoverable
17069 - Update to the March 1 2011 Maxmind GeoLite Country database.
17071 o Minor features (log subsystem):
17072 - Add documentation for configuring logging at different severities in
17073 different log domains. We've had this feature since 0.2.1.1-alpha,
17074 but for some reason it never made it into the manpage. Fixes
17076 - Make it simpler to specify "All log domains except for A and B".
17077 Previously you needed to say "[*,~A,~B]". Now you can just say
17079 - Add a "LogMessageDomains 1" option to include the domains of log
17080 messages along with the messages. Without this, there's no way
17081 to use log domains without reading the source or doing a lot
17084 o Packaging changes:
17085 - Stop shipping the Tor specs files and development proposal documents
17086 in the tarball. They are now in a separate git repository at
17087 git://git.torproject.org/torspec.git
17090 Changes in version 0.2.1.30 - 2011-02-23
17091 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
17092 change is a slight tweak to Tor's TLS handshake that makes relays
17093 and bridges that run this new version reachable from Iran again.
17094 We don't expect this tweak will win the arms race long-term, but it
17095 buys us time until we roll out a better solution.
17098 - Stop sending a CLOCK_SKEW controller status event whenever
17099 we fetch directory information from a relay that has a wrong clock.
17100 Instead, only inform the controller when it's a trusted authority
17101 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
17102 the rest of bug 1074.
17103 - Fix a bounds-checking error that could allow an attacker to
17104 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
17105 Found by "piebeer".
17106 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
17107 Tor would ignore their RelayBandwidthBurst setting,
17108 potentially using more bandwidth than expected. Bugfix on
17109 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
17110 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
17111 hidserv" in her torrc. The 'hidserv' argument never controlled
17112 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
17115 - Adjust our TLS Diffie-Hellman parameters to match those used by
17117 - Update to the February 1 2011 Maxmind GeoLite Country database.
17120 - Check for and reject overly long directory certificates and
17121 directory tokens before they have a chance to hit any assertions.
17122 Bugfix on 0.2.1.28. Found by "doorss".
17123 - Bring the logic that gathers routerinfos and assesses the
17124 acceptability of circuits into line. This prevents a Tor OP from
17125 getting locked in a cycle of choosing its local OR as an exit for a
17126 path (due to a .exit request) and then rejecting the circuit because
17127 its OR is not listed yet. It also prevents Tor clients from using an
17128 OR running in the same instance as an exit (due to a .exit request)
17129 if the OR does not meet the same requirements expected of an OR
17130 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
17132 o Packaging changes:
17133 - Stop shipping the Tor specs files and development proposal documents
17134 in the tarball. They are now in a separate git repository at
17135 git://git.torproject.org/torspec.git
17136 - Do not include Git version tags as though they are SVN tags when
17137 generating a tarball from inside a repository that has switched
17138 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
17141 Changes in version 0.2.2.22-alpha - 2011-01-25
17142 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
17143 main other change is a slight tweak to Tor's TLS handshake that makes
17144 relays and bridges that run this new version reachable from Iran again.
17145 We don't expect this tweak will win the arms race long-term, but it
17146 will buy us a bit more time until we roll out a better solution.
17149 - Fix a bounds-checking error that could allow an attacker to
17150 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
17151 Found by "piebeer".
17152 - Don't assert when changing from bridge to relay or vice versa
17153 via the controller. The assert happened because we didn't properly
17154 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
17155 bug 2433. Reported by bastik.
17158 - Adjust our TLS Diffie-Hellman parameters to match those used by
17160 - Provide a log message stating which geoip file we're parsing
17161 instead of just stating that we're parsing the geoip file.
17162 Implements ticket 2432.
17165 - Check for and reject overly long directory certificates and
17166 directory tokens before they have a chance to hit any assertions.
17167 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
17170 Changes in version 0.2.2.21-alpha - 2011-01-15
17171 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
17172 continues our recent code security audit work. The main fix resolves
17173 a remote heap overflow vulnerability that can allow remote code
17174 execution (CVE-2011-0427). Other fixes address a variety of assert
17175 and crash bugs, most of which we think are hard to exploit remotely.
17177 o Major bugfixes (security), also included in 0.2.1.29:
17178 - Fix a heap overflow bug where an adversary could cause heap
17179 corruption. This bug probably allows remote code execution
17180 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
17182 - Prevent a denial-of-service attack by disallowing any
17183 zlib-compressed data whose compression factor is implausibly
17184 high. Fixes part of bug 2324; reported by "doorss".
17185 - Zero out a few more keys in memory before freeing them. Fixes
17186 bug 2384 and part of bug 2385. These key instances found by
17187 "cypherpunks", based on Andrew Case's report about being able
17188 to find sensitive data in Tor's memory space if you have enough
17189 permissions. Bugfix on 0.0.2pre9.
17191 o Major bugfixes (crashes), also included in 0.2.1.29:
17192 - Prevent calls to Libevent from inside Libevent log handlers.
17193 This had potential to cause a nasty set of crashes, especially
17194 if running Libevent with debug logging enabled, and running
17195 Tor with a controller watching for low-severity log messages.
17196 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
17197 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
17198 underflow errors there too. Fixes the other part of bug 2324.
17199 - Fix a bug where we would assert if we ever had a
17200 cached-descriptors.new file (or another file read directly into
17201 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
17202 on 0.2.1.25. Found by doorss.
17203 - Fix some potential asserts and parsing issues with grossly
17204 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
17207 o Minor bugfixes (other), also included in 0.2.1.29:
17208 - Fix a bug with handling misformed replies to reverse DNS lookup
17209 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
17210 bug reported by doorss.
17211 - Fix compilation on mingw when a pthreads compatibility library
17212 has been installed. (We don't want to use it, so we shouldn't
17213 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
17214 - Fix a bug where we would declare that we had run out of virtual
17215 addresses when the address space was only half-exhausted. Bugfix
17217 - Correctly handle the case where AutomapHostsOnResolve is set but
17218 no virtual addresses are available. Fixes bug 2328; bugfix on
17219 0.1.2.1-alpha. Bug found by doorss.
17220 - Correctly handle wrapping around when we run out of virtual
17221 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
17223 o Minor features, also included in 0.2.1.29:
17224 - Update to the January 1 2011 Maxmind GeoLite Country database.
17225 - Introduce output size checks on all of our decryption functions.
17227 o Build changes, also included in 0.2.1.29:
17228 - Tor does not build packages correctly with Automake 1.6 and earlier;
17229 added a check to Makefile.am to make sure that we're building with
17230 Automake 1.7 or later.
17231 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
17232 because we built it with a too-old version of automake. Thus that
17233 release broke ./configure --enable-openbsd-malloc, which is popular
17234 among really fast exit relays on Linux.
17236 o Major bugfixes, new in 0.2.2.21-alpha:
17237 - Prevent crash/heap corruption when the cbtnummodes consensus
17238 parameter is set to 0 or large values. Fixes bug 2317; bugfix
17241 o Major features, new in 0.2.2.21-alpha:
17242 - Introduce minimum/maximum values that clients will believe
17243 from the consensus. Now we'll have a better chance to avoid crashes
17244 or worse when a consensus param has a weird value.
17246 o Minor features, new in 0.2.2.21-alpha:
17247 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
17248 used on bridges, and it makes bridge scanning somewhat easier.
17249 - If writing the state file to disk fails, wait up to an hour before
17250 retrying again, rather than trying again each second. Fixes bug
17251 2346; bugfix on Tor 0.1.1.3-alpha.
17252 - Make Libevent log messages get delivered to controllers later,
17253 and not from inside the Libevent log handler. This prevents unsafe
17254 reentrant Libevent calls while still letting the log messages
17256 - Detect platforms that brokenly use a signed size_t, and refuse to
17257 build there. Found and analyzed by doorss and rransom.
17258 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
17261 o Minor bugfixes, new in 0.2.2.21-alpha:
17262 - Handle SOCKS messages longer than 128 bytes long correctly, rather
17263 than waiting forever for them to finish. Fixes bug 2330; bugfix
17264 on 0.2.0.16-alpha. Found by doorss.
17265 - Add assertions to check for overflow in arguments to
17266 base32_encode() and base32_decode(); fix a signed-unsigned
17267 comparison there too. These bugs are not actually reachable in Tor,
17268 but it's good to prevent future errors too. Found by doorss.
17269 - Correctly detect failures to create DNS requests when using Libevent
17270 versions before v2. (Before Libevent 2, we used our own evdns
17271 implementation. Its return values for Libevent's evdns_resolve_*()
17272 functions are not consistent with those from Libevent.) Fixes bug
17273 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
17275 o Documentation, new in 0.2.2.21-alpha:
17276 - Document the default socks host and port (127.0.0.1:9050) for
17280 Changes in version 0.2.1.29 - 2011-01-15
17281 Tor 0.2.1.29 continues our recent code security audit work. The main
17282 fix resolves a remote heap overflow vulnerability that can allow remote
17283 code execution. Other fixes address a variety of assert and crash bugs,
17284 most of which we think are hard to exploit remotely.
17286 o Major bugfixes (security):
17287 - Fix a heap overflow bug where an adversary could cause heap
17288 corruption. This bug probably allows remote code execution
17289 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
17291 - Prevent a denial-of-service attack by disallowing any
17292 zlib-compressed data whose compression factor is implausibly
17293 high. Fixes part of bug 2324; reported by "doorss".
17294 - Zero out a few more keys in memory before freeing them. Fixes
17295 bug 2384 and part of bug 2385. These key instances found by
17296 "cypherpunks", based on Andrew Case's report about being able
17297 to find sensitive data in Tor's memory space if you have enough
17298 permissions. Bugfix on 0.0.2pre9.
17300 o Major bugfixes (crashes):
17301 - Prevent calls to Libevent from inside Libevent log handlers.
17302 This had potential to cause a nasty set of crashes, especially
17303 if running Libevent with debug logging enabled, and running
17304 Tor with a controller watching for low-severity log messages.
17305 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
17306 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
17307 underflow errors there too. Fixes the other part of bug 2324.
17308 - Fix a bug where we would assert if we ever had a
17309 cached-descriptors.new file (or another file read directly into
17310 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
17311 on 0.2.1.25. Found by doorss.
17312 - Fix some potential asserts and parsing issues with grossly
17313 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
17316 o Minor bugfixes (other):
17317 - Fix a bug with handling misformed replies to reverse DNS lookup
17318 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
17319 bug reported by doorss.
17320 - Fix compilation on mingw when a pthreads compatibility library
17321 has been installed. (We don't want to use it, so we shouldn't
17322 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
17323 - Fix a bug where we would declare that we had run out of virtual
17324 addresses when the address space was only half-exhausted. Bugfix
17326 - Correctly handle the case where AutomapHostsOnResolve is set but
17327 no virtual addresses are available. Fixes bug 2328; bugfix on
17328 0.1.2.1-alpha. Bug found by doorss.
17329 - Correctly handle wrapping around to when we run out of virtual
17330 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
17331 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
17332 because we built it with a too-old version of automake. Thus that
17333 release broke ./configure --enable-openbsd-malloc, which is popular
17334 among really fast exit relays on Linux.
17337 - Update to the January 1 2011 Maxmind GeoLite Country database.
17338 - Introduce output size checks on all of our decryption functions.
17341 - Tor does not build packages correctly with Automake 1.6 and earlier;
17342 added a check to Makefile.am to make sure that we're building with
17343 Automake 1.7 or later.
17346 Changes in version 0.2.2.20-alpha - 2010-12-17
17347 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
17348 exploitable bugs. We also fix a variety of other significant bugs,
17349 change the IP address for one of our directory authorities, and update
17350 the minimum version that Tor relays must run to join the network.
17353 - Fix a remotely exploitable bug that could be used to crash instances
17354 of Tor remotely by overflowing on the heap. Remote-code execution
17355 hasn't been confirmed, but can't be ruled out. Everyone should
17356 upgrade. Bugfix on the 0.1.1 series and later.
17357 - Fix a bug that could break accounting on 64-bit systems with large
17358 time_t values, making them hibernate for impossibly long intervals.
17359 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
17360 - Fix a logic error in directory_fetches_from_authorities() that
17361 would cause all _non_-exits refusing single-hop-like circuits
17362 to fetch from authorities, when we wanted to have _exits_ fetch
17363 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
17365 - Fix a stream fairness bug that would cause newer streams on a given
17366 circuit to get preference when reading bytes from the origin or
17367 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
17368 introduced before the first Tor release, in svn revision r152.
17370 o Directory authority changes:
17371 - Change IP address and ports for gabelmoo (v3 directory authority).
17374 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
17375 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
17376 - Fix an off-by-one error in calculating some controller command
17377 argument lengths. Fortunately, this mistake is harmless since
17378 the controller code does redundant NUL termination too. Found by
17379 boboper. Bugfix on 0.1.1.1-alpha.
17380 - Do not dereference NULL if a bridge fails to build its
17381 extra-info descriptor. Found by an anonymous commenter on
17382 Trac. Bugfix on 0.2.2.19-alpha.
17385 - Update to the December 1 2010 Maxmind GeoLite Country database.
17386 - Directory authorities now reject relays running any versions of
17387 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
17388 known bugs that keep RELAY_EARLY cells from working on rendezvous
17389 circuits. Followup to fix for bug 2081.
17390 - Directory authorities now reject relays running any version of Tor
17391 older than 0.2.0.26-rc. That version is the earliest that fetches
17392 current directory information correctly. Fixes bug 2156.
17393 - Report only the top 10 ports in exit-port stats in order not to
17394 exceed the maximum extra-info descriptor length of 50 KB. Implements
17398 Changes in version 0.2.1.28 - 2010-12-17
17399 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
17400 exploitable bugs. We also took this opportunity to change the IP address
17401 for one of our directory authorities, and to update the geoip database
17405 - Fix a remotely exploitable bug that could be used to crash instances
17406 of Tor remotely by overflowing on the heap. Remote-code execution
17407 hasn't been confirmed, but can't be ruled out. Everyone should
17408 upgrade. Bugfix on the 0.1.1 series and later.
17410 o Directory authority changes:
17411 - Change IP address and ports for gabelmoo (v3 directory authority).
17414 - Update to the December 1 2010 Maxmind GeoLite Country database.
17417 Changes in version 0.2.1.27 - 2010-11-23
17418 Yet another OpenSSL security patch broke its compatibility with Tor:
17419 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
17420 also took this opportunity to fix several crash bugs, integrate a new
17421 directory authority, and update the bundled GeoIP database.
17424 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
17425 No longer set the tlsext_host_name extension on server SSL objects;
17426 but continue to set it on client SSL objects. Our goal in setting
17427 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
17428 bugfix on 0.2.1.1-alpha.
17429 - Do not log messages to the controller while shrinking buffer
17430 freelists. Doing so would sometimes make the controller connection
17431 try to allocate a buffer chunk, which would mess up the internals
17432 of the freelist and cause an assertion failure. Fixes bug 1125;
17433 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
17434 - Learn our external IP address when we're a relay or bridge, even if
17435 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
17436 where we introduced bridge relays that don't need to publish to
17437 be useful. Fixes bug 2050.
17438 - Do even more to reject (and not just ignore) annotations on
17439 router descriptors received anywhere but from the cache. Previously
17440 we would ignore such annotations at first, but cache them to disk
17441 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
17442 - When you're using bridges and your network goes away and your
17443 bridges get marked as down, recover when you attempt a new socks
17444 connection (if the network is back), rather than waiting up to an
17445 hour to try fetching new descriptors for your bridges. Bugfix on
17446 0.2.0.3-alpha; fixes bug 1981.
17449 - Move to the November 2010 Maxmind GeoLite country db (rather
17450 than the June 2009 ip-to-country GeoIP db) for our statistics that
17451 count how many users relays are seeing from each country. Now we'll
17452 have more accurate data, especially for many African countries.
17454 o New directory authorities:
17455 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
17459 - Fix an assertion failure that could occur in directory caches or
17460 bridge users when using a very short voting interval on a testing
17461 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
17463 - Enforce multiplicity rules when parsing annotations. Bugfix on
17464 0.2.0.8-alpha. Found by piebeer.
17465 - Allow handshaking OR connections to take a full KeepalivePeriod
17466 seconds to handshake. Previously, we would close them after
17467 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
17468 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
17470 - When building with --enable-gcc-warnings on OpenBSD, disable
17471 warnings in system headers. This makes --enable-gcc-warnings
17472 pass on OpenBSD 4.8.
17475 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
17476 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
17477 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
17478 Servers can start sending this code when enough clients recognize
17479 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
17480 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
17481 Patch from mingw-san.
17484 - Remove the old debian/ directory from the main Tor distribution.
17485 The official Tor-for-debian git repository lives at the URL
17486 https://git.torproject.org/debian/tor.git
17487 - Stop shipping the old doc/website/ directory in the tarball. We
17488 changed the website format in late 2010, and what we shipped in
17489 0.2.1.26 really wasn't that useful anyway.
17492 Changes in version 0.2.2.19-alpha - 2010-11-22
17493 Yet another OpenSSL security patch broke its compatibility with Tor:
17494 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
17497 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
17498 No longer set the tlsext_host_name extension on server SSL objects;
17499 but continue to set it on client SSL objects. Our goal in setting
17500 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
17501 bugfix on 0.2.1.1-alpha.
17504 - Try harder not to exceed the maximum length of 50 KB when writing
17505 statistics to extra-info descriptors. This bug was triggered by very
17506 fast relays reporting exit-port, entry, and dirreq statistics.
17507 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
17508 - Publish a router descriptor even if generating an extra-info
17509 descriptor fails. Previously we would not publish a router
17510 descriptor without an extra-info descriptor; this can cause fast
17511 exit relays collecting exit-port statistics to drop from the
17512 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
17515 Changes in version 0.2.2.18-alpha - 2010-11-16
17516 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
17517 us lately, makes unpublished bridge relays able to detect their IP
17518 address, and fixes a wide variety of other bugs to get us much closer
17519 to a stable release.
17522 - Do even more to reject (and not just ignore) annotations on
17523 router descriptors received anywhere but from the cache. Previously
17524 we would ignore such annotations at first, but cache them to disk
17525 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
17526 - Do not log messages to the controller while shrinking buffer
17527 freelists. Doing so would sometimes make the controller connection
17528 try to allocate a buffer chunk, which would mess up the internals
17529 of the freelist and cause an assertion failure. Fixes bug 1125;
17530 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
17531 - Learn our external IP address when we're a relay or bridge, even if
17532 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
17533 where we introduced bridge relays that don't need to publish to
17534 be useful. Fixes bug 2050.
17535 - Maintain separate TLS contexts and certificates for incoming and
17536 outgoing connections in bridge relays. Previously we would use the
17537 same TLS contexts and certs for incoming and outgoing connections.
17538 Bugfix on 0.2.0.3-alpha; addresses bug 988.
17539 - Maintain separate identity keys for incoming and outgoing TLS
17540 contexts in bridge relays. Previously we would use the same
17541 identity keys for incoming and outgoing TLS contexts. Bugfix on
17542 0.2.0.3-alpha; addresses the other half of bug 988.
17543 - Avoid an assertion failure when we as an authority receive a
17544 duplicate upload of a router descriptor that we already have,
17545 but which we previously considered an obsolete descriptor.
17546 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
17547 - Avoid a crash bug triggered by looking at a dangling pointer while
17548 setting the network status consensus. Found by Robert Ransom.
17549 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
17550 - Fix a logic error where servers that _didn't_ act as exits would
17551 try to keep their server lists more aggressively up to date than
17552 exits, when it was supposed to be the other way around. Bugfix
17555 o Minor bugfixes (on Tor 0.2.1.x and earlier):
17556 - When we're trying to guess whether we know our IP address as
17557 a relay, we would log various ways that we failed to guess
17558 our address, but never log that we ended up guessing it
17559 successfully. Now add a log line to help confused and anxious
17560 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
17561 - Bring the logic that gathers routerinfos and assesses the
17562 acceptability of circuits into line. This prevents a Tor OP from
17563 getting locked in a cycle of choosing its local OR as an exit for a
17564 path (due to a .exit request) and then rejecting the circuit because
17565 its OR is not listed yet. It also prevents Tor clients from using an
17566 OR running in the same instance as an exit (due to a .exit request)
17567 if the OR does not meet the same requirements expected of an OR
17568 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
17569 - Correctly describe errors that occur when generating a TLS object.
17570 Previously we would attribute them to a failure while generating a
17571 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
17573 - Enforce multiplicity rules when parsing annotations. Bugfix on
17574 0.2.0.8-alpha. Found by piebeer.
17575 - Fix warnings that newer versions of autoconf produced during
17576 ./autogen.sh. These warnings appear to be harmless in our case,
17577 but they were extremely verbose. Fixes bug 2020.
17579 o Minor bugfixes (on Tor 0.2.2.x):
17580 - Enable protection of small arrays whenever we build with gcc
17581 hardening features, not only when also building with warnings
17582 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
17585 - Make hidden services work better in private Tor networks by not
17586 requiring any uptime to join the hidden service descriptor
17587 DHT. Implements ticket 2088.
17588 - Rate-limit the "your application is giving Tor only an IP address"
17589 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
17590 - When AllowSingleHopExits is set, print a warning to explain to the
17591 relay operator why most clients are avoiding her relay.
17592 - Update to the November 1 2010 Maxmind GeoLite Country database.
17594 o Code simplifications and refactoring:
17595 - When we fixed bug 1038 we had to put in a restriction not to send
17596 RELAY_EARLY cells on rend circuits. This was necessary as long
17597 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
17598 active. Now remove this obsolete check. Resolves bug 2081.
17599 - Some options used different conventions for uppercasing of acronyms
17600 when comparing manpage and source. Fix those in favor of the
17601 manpage, as it makes sense to capitalize acronyms.
17602 - Remove the torrc.complete file. It hasn't been kept up to date
17603 and users will have better luck checking out the manpage.
17604 - Remove the obsolete "NoPublish" option; it has been flagged
17605 as obsolete and has produced a warning since 0.1.1.18-rc.
17606 - Remove everything related to building the expert bundle for OS X.
17607 It has confused many users, doesn't work right on OS X 10.6,
17608 and is hard to get rid of once installed. Resolves bug 1274.
17611 Changes in version 0.2.2.17-alpha - 2010-09-30
17612 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
17613 to use one-hop circuits (which can put the exit relays at higher risk,
17614 plus unbalance the network); fixes a big bug in bandwidth accounting
17615 for relays that want to limit their monthly bandwidth use; fixes a
17616 big pile of bugs in how clients tolerate temporary network failure;
17617 and makes our adaptive circuit build timeout feature (which improves
17618 client performance if your network is fast while not breaking things
17619 if your network is slow) better handle bad networks.
17622 - Exit relays now try harder to block exit attempts from unknown
17623 relays, to make it harder for people to use them as one-hop proxies
17624 a la tortunnel. Controlled by the refuseunknownexits consensus
17625 parameter (currently enabled), or you can override it on your
17626 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
17628 o Major bugfixes (0.2.1.x and earlier):
17629 - Fix a bug in bandwidth accounting that could make us use twice
17630 the intended bandwidth when our interval start changes due to
17631 daylight saving time. Now we tolerate skew in stored vs computed
17632 interval starts: if the start of the period changes by no more than
17633 50% of the period's duration, we remember bytes that we transferred
17634 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
17635 - Always search the Windows system directory for system DLLs, and
17636 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
17637 - When you're using bridges and your network goes away and your
17638 bridges get marked as down, recover when you attempt a new socks
17639 connection (if the network is back), rather than waiting up to an
17640 hour to try fetching new descriptors for your bridges. Bugfix on
17641 0.2.0.3-alpha; fixes bug 1981.
17643 o Major bugfixes (on 0.2.2.x):
17644 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
17646 - Fix a segfault that could happen when operating a bridge relay with
17647 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
17648 - The consensus bandwidth-weights (used by clients to choose fast
17649 relays) entered an unexpected edge case in September where
17650 Exits were much scarcer than Guards, resulting in bad weight
17651 recommendations. Now we compute them using new constraints that
17652 should succeed in all cases. Also alter directory authorities to
17653 not include the bandwidth-weights line if they fail to produce
17654 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
17655 - When weighting bridges during path selection, we used to trust
17656 the bandwidths they provided in their descriptor, only capping them
17657 at 10MB/s. This turned out to be problematic for two reasons:
17658 Bridges could claim to handle a lot more traffic then they
17659 actually would, thus making more clients pick them and have a
17660 pretty effective DoS attack. The other issue is that new bridges
17661 that might not have a good estimate for their bw capacity yet
17662 would not get used at all unless no other bridges are available
17663 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
17665 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
17666 - Ignore cannibalized circuits when recording circuit build times.
17667 This should provide for a minor performance improvement for hidden
17668 service users using 0.2.2.14-alpha, and should remove two spurious
17669 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
17670 - Simplify the logic that causes us to decide if the network is
17671 unavailable for purposes of recording circuit build times. If we
17672 receive no cells whatsoever for the entire duration of a circuit's
17673 full measured lifetime, the network is probably down. Also ignore
17674 one-hop directory fetching circuit timeouts when calculating our
17675 circuit build times. These changes should hopefully reduce the
17676 cases where we see ridiculous circuit build timeouts for people
17677 with spotty wireless connections. Fixes part of bug 1772; bugfix
17679 - Prevent the circuit build timeout from becoming larger than
17680 the maximum build time we have ever seen. Also, prevent the time
17681 period for measurement circuits from becoming larger than twice that
17682 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
17685 - When we run out of directory information such that we can't build
17686 circuits, but then get enough that we can build circuits, log when
17687 we actually construct a circuit, so the user has a better chance of
17688 knowing what's going on. Fixes bug 1362.
17689 - Be more generous with how much bandwidth we'd use up (with
17690 accounting enabled) before entering "soft hibernation". Previously,
17691 we'd refuse new connections and circuits once we'd used up 95% of
17692 our allotment. Now, we use up 95% of our allotment, AND make sure
17693 that we have no more than 500MB (or 3 hours of expected traffic,
17694 whichever is lower) remaining before we enter soft hibernation.
17695 - If we've configured EntryNodes and our network goes away and/or all
17696 our entrynodes get marked down, optimistically retry them all when
17697 a new socks application request appears. Fixes bug 1882.
17698 - Add some more defensive programming for architectures that can't
17699 handle unaligned integer accesses. We don't know of any actual bugs
17700 right now, but that's the best time to fix them. Fixes bug 1943.
17701 - Support line continuations in the torrc config file. If a line
17702 ends with a single backslash character, the newline is ignored, and
17703 the configuration value is treated as continuing on the next line.
17706 o Minor bugfixes (on 0.2.1.x and earlier):
17707 - For bandwidth accounting, calculate our expected bandwidth rate
17708 based on the time during which we were active and not in
17709 soft-hibernation during the last interval. Previously, we were
17710 also considering the time spent in soft-hibernation. If this
17711 was a long time, we would wind up underestimating our bandwidth
17712 by a lot, and skewing our wakeup time towards the start of the
17713 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
17715 o Minor bugfixes (on 0.2.2.x):
17716 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
17717 which were disabled by the circuit build timeout changes in
17718 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
17719 - Make sure we don't warn about missing bandwidth weights when
17720 choosing bridges or other relays not in the consensus. Bugfix on
17721 0.2.2.10-alpha; fixes bug 1805.
17722 - In our logs, do not double-report signatures from unrecognized
17723 authorities both as "from unknown authority" and "not
17724 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
17727 Changes in version 0.2.2.16-alpha - 2010-09-17
17728 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
17729 evident at exit relays), and also continues to resolve all the little
17730 bugs that have been filling up trac lately.
17732 o Major bugfixes (stream-level fairness):
17733 - When receiving a circuit-level SENDME for a blocked circuit, try
17734 to package cells fairly from all the streams that had previously
17735 been blocked on that circuit. Previously, we had started with the
17736 oldest stream, and allowed each stream to potentially exhaust
17737 the circuit's package window. This gave older streams on any
17738 given circuit priority over newer ones. Fixes bug 1937. Detected
17739 originally by Camilo Viecco. This bug was introduced before the
17740 first Tor release, in svn commit r152: it is the new winner of
17741 the longest-lived bug prize.
17742 - When the exit relay got a circuit-level sendme cell, it started
17743 reading on the exit streams, even if had 500 cells queued in the
17744 circuit queue already, so the circuit queue just grew and grew in
17745 some cases. We fix this by not re-enabling reading on receipt of a
17746 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
17747 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
17749 - Newly created streams were allowed to read cells onto circuits,
17750 even if the circuit's cell queue was blocked and waiting to drain.
17751 This created potential unfairness, as older streams would be
17752 blocked, but newer streams would gladly fill the queue completely.
17753 We add code to detect this situation and prevent any stream from
17754 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
17758 - Update to the September 1 2010 Maxmind GeoLite Country database.
17759 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
17760 not. This would lead to a cookie that is still not group readable.
17761 Closes bug 1843. Suggested by katmagic.
17762 - When logging a rate-limited warning, we now mention how many messages
17763 got suppressed since the last warning.
17764 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
17765 do individual connection-level rate limiting of clients. The torrc
17766 config options with the same names trump the consensus params, if
17767 both are present. Replaces the old "bwconnrate" and "bwconnburst"
17768 consensus params which were broken from 0.2.2.7-alpha through
17769 0.2.2.14-alpha. Closes bug 1947.
17770 - When a router changes IP address or port, authorities now launch
17771 a new reachability test for it. Implements ticket 1899.
17772 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
17773 2 no signature, 4 required" messages about consensus signatures
17774 easier to read, and make sure they get logged at the same severity
17775 as the messages explaining which keys are which. Fixes bug 1290.
17776 - Don't warn when we have a consensus that we can't verify because
17777 of missing certificates, unless those certificates are ones
17778 that we have been trying and failing to download. Fixes bug 1145.
17779 - If you configure your bridge with a known identity fingerprint,
17780 and the bridge authority is unreachable (as it is in at least
17781 one country now), fall back to directly requesting the descriptor
17782 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
17784 - When building with --enable-gcc-warnings on OpenBSD, disable
17785 warnings in system headers. This makes --enable-gcc-warnings
17786 pass on OpenBSD 4.8.
17788 o Minor bugfixes (on 0.2.1.x and earlier):
17789 - Authorities will now attempt to download consensuses if their
17790 own efforts to make a live consensus have failed. This change
17791 means authorities that restart will fetch a valid consensus, and
17792 it means authorities that didn't agree with the current consensus
17793 will still fetch and serve it if it has enough signatures. Bugfix
17794 on 0.2.0.9-alpha; fixes bug 1300.
17795 - Ensure DNS requests launched by "RESOLVE" commands from the
17796 controller respect the __LeaveStreamsUnattached setconf options. The
17797 same goes for requests launched via DNSPort or transparent
17798 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
17799 - Allow handshaking OR connections to take a full KeepalivePeriod
17800 seconds to handshake. Previously, we would close them after
17801 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
17802 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
17804 - Rate-limit "Failed to hand off onionskin" warnings.
17805 - Never relay a cell for a circuit we have already destroyed.
17806 Between marking a circuit as closeable and finally closing it,
17807 it may have been possible for a few queued cells to get relayed,
17808 even though they would have been immediately dropped by the next
17809 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
17810 - Never queue a cell for a circuit that's already been marked
17812 - Never vote for a server as "Running" if we have a descriptor for
17813 it claiming to be hibernating, and that descriptor was published
17814 more recently than our last contact with the server. Bugfix on
17815 0.2.0.3-alpha; fixes bug 911.
17816 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
17819 o Minor bugfixes (on 0.2.2.x):
17820 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
17821 down if a directory fetch fails and you've configured either
17822 bridges or EntryNodes. The intent was to mark the relay as down
17823 _unless_ you're using bridges or EntryNodes, since if you are
17824 then you could quickly run out of entry points.
17825 - Fix the Windows directory-listing code. A bug introduced in
17826 0.2.2.14-alpha could make Windows directory servers forget to load
17827 some of their cached v2 networkstatus files.
17828 - Really allow clients to use relays as bridges. Fixes bug 1776;
17829 bugfix on 0.2.2.15-alpha.
17830 - Demote a warn to info that happens when the CellStatistics option
17831 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
17832 Reported by Moritz Bartl.
17833 - On Windows, build correctly either with or without Unicode support.
17834 This is necessary so that Tor can support fringe platforms like
17835 Windows 98 (which has no Unicode), or Windows CE (which has no
17836 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
17839 - Add a unit test for cross-platform directory-listing code.
17842 Changes in version 0.2.2.15-alpha - 2010-08-18
17843 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
17844 fixes a variety of other bugs that were preventing performance
17845 experiments from moving forward, fixes several bothersome memory leaks,
17846 and generally closes a lot of smaller bugs that have been filling up
17850 - Stop assigning the HSDir flag to relays that disable their
17851 DirPort (and thus will refuse to answer directory requests). This
17852 fix should dramatically improve the reachability of hidden services:
17853 hidden services and hidden service clients pick six HSDir relays
17854 to store and retrieve the hidden service descriptor, and currently
17855 about half of the HSDir relays will refuse to work. Bugfix on
17856 0.2.0.10-alpha; fixes part of bug 1693.
17857 - The PerConnBWRate and Burst config options, along with the
17858 bwconnrate and bwconnburst consensus params, initialized each conn's
17859 token bucket values only when the connection is established. Now we
17860 update them if the config options change, and update them every time
17861 we get a new consensus. Otherwise we can encounter an ugly edge
17862 case where we initialize an OR conn to client-level bandwidth,
17863 but then later the relay joins the consensus and we leave it
17864 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
17865 - Fix a regression that caused Tor to rebind its ports if it receives
17866 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
17869 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
17870 should give us approximately 40-50% more Guard-flagged nodes,
17871 improving the anonymity the Tor network can provide and also
17872 decreasing the dropoff in throughput that relays experience when
17873 they first get the Guard flag.
17874 - Allow enabling or disabling the *Statistics config options while
17878 - Update to the August 1 2010 Maxmind GeoLite Country database.
17879 - Have the controller interface give a more useful message than
17880 "Internal Error" in response to failed GETINFO requests.
17881 - Warn when the same option is provided more than once in a torrc
17882 file, on the command line, or in a single SETCONF statement, and
17883 the option is one that only accepts a single line. Closes bug 1384.
17884 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
17885 Patch from mingw-san.
17886 - Add support for the country code "{??}" in torrc options like
17887 ExcludeNodes, to indicate all routers of unknown country. Closes
17889 - Relays report the number of bytes spent on answering directory
17890 requests in extra-info descriptors similar to {read,write}-history.
17891 Implements enhancement 1790.
17893 o Minor bugfixes (on 0.2.1.x and earlier):
17894 - Complain if PublishServerDescriptor is given multiple arguments that
17895 include 0 or 1. This configuration will be rejected in the future.
17896 Bugfix on 0.2.0.1-alpha; closes bug 1107.
17897 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
17898 Bugfix on 0.2.0.13-alpha; closes bug 928.
17899 - Change "Application request when we're believed to be offline."
17900 notice to "Application request when we haven't used client
17901 functionality lately.", to clarify that it's not an error. Bugfix
17902 on 0.0.9.3; fixes bug 1222.
17903 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
17904 would return "551 Internal error" rather than "552 Unrecognized key
17905 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
17906 - Users can't configure a regular relay to be their bridge. It didn't
17907 work because when Tor fetched the bridge descriptor, it found
17908 that it already had it, and didn't realize that the purpose of the
17909 descriptor had changed. Now we replace routers with a purpose other
17910 than bridge with bridge descriptors when fetching them. Bugfix on
17911 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
17912 refetch the descriptor with router purpose 'general', disabling
17914 - Fix a rare bug in rend_fn unit tests: we would fail a test when
17915 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
17916 on 0.2.0.10-alpha; fixes bug 1808.
17917 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
17918 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
17919 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
17920 Servers can start sending this code when enough clients recognize
17921 it. Also update the spec to reflect this new reason. Bugfix on
17922 0.1.0.1-rc; fixes part of bug 1793.
17923 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
17924 when we switch from being a public relay to a bridge. Otherwise
17925 there will still be clients that see the relay in their consensus,
17926 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
17928 - Instead of giving an assertion failure on an internal mismatch
17929 on estimated freelist size, just log a BUG warning and try later.
17930 Mitigates but does not fix bug 1125.
17931 - Fix an assertion failure that could occur in caches or bridge users
17932 when using a very short voting interval on a testing network.
17933 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
17935 o Minor bugfixes (on 0.2.2.x):
17936 - Alter directory authorities to always consider Exit-flagged nodes
17937 as potential Guard nodes in their votes. The actual decision to
17938 use Exits as Guards is done in the consensus bandwidth weights.
17939 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
17940 - When the controller is reporting the purpose of circuits that
17941 didn't finish building before the circuit build timeout, it was
17942 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
17943 - Our libevent version parsing code couldn't handle versions like
17944 1.4.14b-stable and incorrectly warned the user about using an
17945 old and broken version of libevent. Treat 1.4.14b-stable like
17946 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
17948 - Don't use substitution references like $(VAR:MOD) when
17949 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
17950 '$(:x)' to 'x' rather than the empty string. This bites us in
17951 doc/ when configured with --disable-asciidoc. Bugfix on
17952 0.2.2.9-alpha; fixes bug 1773.
17953 - Remove a spurious hidden service server-side log notice about
17954 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
17956 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
17958 - Correctly report written bytes on linked connections. Found while
17959 implementing 1790. Bugfix on 0.2.2.4-alpha.
17960 - Fix three memory leaks: one in circuit_build_times_parse_state(),
17961 one in dirvote_add_signatures_to_pending_consensus(), and one every
17962 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
17963 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
17965 o Code simplifications and refactoring:
17966 - Take a first step towards making or.h smaller by splitting out
17967 function definitions for all source files in src/or/. Leave
17968 structures and defines in or.h for now.
17969 - Remove a bunch of unused function declarations as well as a block of
17970 #if 0'd code from the unit tests. Closes bug 1824.
17971 - New unit tests for exit-port history statistics; refactored exit
17972 statistics code to be more easily tested.
17973 - Remove the old debian/ directory from the main Tor distribution.
17974 The official Tor-for-debian git repository lives at the URL
17975 https://git.torproject.org/debian/tor.git
17978 Changes in version 0.2.2.14-alpha - 2010-07-12
17979 Tor 0.2.2.14-alpha greatly improves client-side handling of
17980 circuit build timeouts, which are used to estimate speed and improve
17981 performance. We also move to a much better GeoIP database, port Tor to
17982 Windows CE, introduce new compile flags that improve code security,
17983 add an eighth v3 directory authority, and address a lot of more
17987 - Tor directory authorities no longer crash when started with a
17988 cached-microdesc-consensus file in their data directory. Bugfix
17989 on 0.2.2.6-alpha; fixes bug 1532.
17990 - Treat an unset $HOME like an empty $HOME rather than triggering an
17991 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
17992 - Ignore negative and large circuit build timeout values that can
17993 happen during a suspend or hibernate. These values caused various
17994 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
17995 - Alter calculation of Pareto distribution parameter 'Xm' for
17996 Circuit Build Timeout learning to use the weighted average of the
17997 top N=3 modes (because we have three entry guards). Considering
17998 multiple modes should improve the timeout calculation in some cases,
17999 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
18001 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
18002 right censored distribution model. This approach improves over the
18003 synthetic timeout generation approach that was producing insanely
18004 high timeout values. Now we calculate build timeouts using truncated
18005 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
18006 - Do not close circuits that are under construction when they reach
18007 the circuit build timeout. Instead, leave them building (but do not
18008 use them) for up until the time corresponding to the 95th percentile
18009 on the Pareto CDF or 60 seconds, whichever is greater. This is done
18010 to provide better data for the new Pareto model. This percentile
18011 can be controlled by the consensus.
18014 - Move to the June 2010 Maxmind GeoLite country db (rather than the
18015 June 2009 ip-to-country GeoIP db) for our statistics that count
18016 how many users relays are seeing from each country. Now we have
18017 more accurate data for many African countries.
18018 - Port Tor to build and run correctly on Windows CE systems, using
18019 the wcecompat library. Contributed by Valerio Lupi.
18020 - New "--enable-gcc-hardening" ./configure flag (off by default)
18021 to turn on gcc compile time hardening options. It ensures
18022 that signed ints have defined behavior (-fwrapv), enables
18023 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
18024 with canaries (-fstack-protector-all), turns on ASLR protection if
18025 supported by the kernel (-fPIE, -pie), and adds additional security
18026 related warnings. Verified to work on Mac OS X and Debian Lenny.
18027 - New "--enable-linker-hardening" ./configure flag (off by default)
18028 to turn on ELF specific hardening features (relro, now). This does
18029 not work with Mac OS X or any other non-ELF binary format.
18031 o New directory authorities:
18032 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
18036 - New config option "WarnUnsafeSocks 0" disables the warning that
18037 occurs whenever Tor receives a socks handshake using a version of
18038 the socks protocol that can only provide an IP address (rather
18039 than a hostname). Setups that do DNS locally over Tor are fine,
18040 and we shouldn't spam the logs in that case.
18041 - Convert the HACKING file to asciidoc, and add a few new sections
18042 to it, explaining how we use Git, how we make changelogs, and
18043 what should go in a patch.
18044 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
18045 event, to give information on the current rate of circuit timeouts
18046 over our stored history.
18047 - Add ability to disable circuit build time learning via consensus
18048 parameter and via a LearnCircuitBuildTimeout config option. Also
18049 automatically disable circuit build time calculation if we are
18050 either a AuthoritativeDirectory, or if we fail to write our state
18051 file. Fixes bug 1296.
18052 - More gracefully handle corrupt state files, removing asserts
18053 in favor of saving a backup and resetting state.
18054 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
18058 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
18060 - When a2x fails, mention that the user could disable manpages instead
18061 of trying to fix their asciidoc installation.
18062 - Where available, use Libevent 2.0's periodic timers so that our
18063 once-per-second cleanup code gets called even more closely to
18064 once per second than it would otherwise. Fixes bug 943.
18065 - If you run a bridge that listens on multiple IP addresses, and
18066 some user configures a bridge address that uses a different IP
18067 address than your bridge writes in its router descriptor, and the
18068 user doesn't specify an identity key, their Tor would discard the
18069 descriptor because "it isn't one of our configured bridges", and
18070 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
18071 Bugfix on 0.2.0.3-alpha.
18072 - If OpenSSL fails to make a duplicate of a private or public key, log
18073 an error message and try to exit cleanly. May help with debugging
18074 if bug 1209 ever remanifests.
18075 - Save a couple bytes in memory allocation every time we escape
18076 certain characters in a string. Patch from Florian Zumbiehl.
18077 - Make it explicit that we don't cannibalize one-hop circuits. This
18078 happens in the wild, but doesn't turn out to be a problem because
18079 we fortunately don't use those circuits. Many thanks to outofwords
18080 for the initial analysis and to swissknife who confirmed that
18081 two-hop circuits are actually created.
18082 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
18083 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
18084 - Eliminate a case where a circuit build time warning was displayed
18085 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
18088 Changes in version 0.2.1.26 - 2010-05-02
18089 Tor 0.2.1.26 addresses the recent connection and memory overload
18090 problems we've been seeing on relays, especially relays with their
18091 DirPort open. If your relay has been crashing, or you turned it off
18092 because it used too many resources, give this release a try.
18094 This release also fixes yet another instance of broken OpenSSL libraries
18095 that was causing some relays to drop out of the consensus.
18098 - Teach relays to defend themselves from connection overload. Relays
18099 now close idle circuits early if it looks like they were intended
18100 for directory fetches. Relays are also more aggressive about closing
18101 TLS connections that have no circuits on them. Such circuits are
18102 unlikely to be re-used, and tens of thousands of them were piling
18103 up at the fast relays, causing the relays to run out of sockets
18104 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
18105 their directory fetches over TLS).
18106 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
18107 that claim to be earlier than 0.9.8m, but which have in reality
18108 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
18109 behavior. Possible fix for some cases of bug 1346.
18110 - Directory mirrors were fetching relay descriptors only from v2
18111 directory authorities, rather than v3 authorities like they should.
18112 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
18113 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
18116 - Finally get rid of the deprecated and now harmful notion of "clique
18117 mode", where directory authorities maintain TLS connections to
18121 - In the util/threads test, no longer free the test_mutex before all
18122 worker threads have finished. Bugfix on 0.2.1.6-alpha.
18123 - The master thread could starve the worker threads quite badly on
18124 certain systems, causing them to run only partially in the allowed
18125 window. This resulted in test failures. Now the master thread sleeps
18126 occasionally for a few microseconds while the two worker-threads
18127 compete for the mutex. Bugfix on 0.2.0.1-alpha.
18130 Changes in version 0.2.2.13-alpha - 2010-04-24
18131 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
18132 problems we've been seeing on relays, especially relays with their
18133 DirPort open. If your relay has been crashing, or you turned it off
18134 because it used too many resources, give this release a try.
18137 - Teach relays to defend themselves from connection overload. Relays
18138 now close idle circuits early if it looks like they were intended
18139 for directory fetches. Relays are also more aggressive about closing
18140 TLS connections that have no circuits on them. Such circuits are
18141 unlikely to be re-used, and tens of thousands of them were piling
18142 up at the fast relays, causing the relays to run out of sockets
18143 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
18144 their directory fetches over TLS).
18147 - Finally get rid of the deprecated and now harmful notion of "clique
18148 mode", where directory authorities maintain TLS connections to
18150 - Directory authorities now do an immediate reachability check as soon
18151 as they hear about a new relay. This change should slightly reduce
18152 the time between setting up a relay and getting listed as running
18153 in the consensus. It should also improve the time between setting
18154 up a bridge and seeing use by bridge users.
18155 - Directory authorities no longer launch a TLS connection to every
18156 relay as they startup. Now that we have 2k+ descriptors cached,
18157 the resulting network hiccup is becoming a burden. Besides,
18158 authorities already avoid voting about Running for the first half
18159 hour of their uptime.
18162 Changes in version 0.2.2.12-alpha - 2010-04-20
18163 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
18164 handle and vote on descriptors. It was causing relays to drop out of
18168 - Many relays have been falling out of the consensus lately because
18169 not enough authorities know about their descriptor for them to get
18170 a majority of votes. When we deprecated the v2 directory protocol,
18171 we got rid of the only way that v3 authorities can hear from each
18172 other about other descriptors. Now authorities examine every v3
18173 vote for new descriptors, and fetch them from that authority. Bugfix
18175 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
18176 and a warning in or.h related to bandwidth_weight_rule_t that
18177 prevented clean compile on OS X. Fixes bug 1363; bugfix on
18179 - Fix a segfault on relays when DirReqStatistics is enabled
18180 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
18184 - Demote a confusing TLS warning that relay operators might get when
18185 someone tries to talk to their OrPort. It is neither the operator's
18186 fault nor can they do anything about it. Fixes bug 1364; bugfix
18190 Changes in version 0.2.2.11-alpha - 2010-04-15
18191 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
18192 libraries that was causing some relays to drop out of the consensus.
18195 - Directory mirrors were fetching relay descriptors only from v2
18196 directory authorities, rather than v3 authorities like they should.
18197 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
18198 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
18199 - Fix a parsing error that made every possible value of
18200 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
18201 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
18202 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
18203 about the option without breaking older ones.
18204 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
18205 that claim to be earlier than 0.9.8m, but which have in reality
18206 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
18207 behavior. Possible fix for some cases of bug 1346.
18210 - Experiment with a more aggressive approach to preventing clients
18211 from making one-hop exit streams. Exit relays who want to try it
18212 out can set "RefuseUnknownExits 1" in their torrc, and then look
18213 for "Attempt by %s to open a stream" log messages. Let us know
18215 - Add support for statically linking zlib by specifying
18216 --enable-static-zlib, to go with our support for statically linking
18217 openssl and libevent. Resolves bug 1358.
18220 - Fix a segfault that happens whenever a Tor client that is using
18221 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
18223 - When we cleaned up the contrib/tor-exit-notice.html file, we left
18224 out the first line. Fixes bug 1295.
18225 - When building the manpage from a tarball, we required asciidoc, but
18226 the asciidoc -> roff/html conversion was already done for the
18227 tarball. Make 'make' complain only when we need asciidoc (either
18228 because we're compiling directly from git, or because we altered
18229 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
18230 - When none of the directory authorities vote on any params, Tor
18231 segfaulted when trying to make the consensus from the votes. We
18232 didn't trigger the bug in practice, because authorities do include
18233 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
18236 - In the util/threads test, no longer free the test_mutex before all
18237 worker threads have finished. Bugfix on 0.2.1.6-alpha.
18238 - The master thread could starve the worker threads quite badly on
18239 certain systems, causing them to run only partially in the allowed
18240 window. This resulted in test failures. Now the master thread sleeps
18241 occasionally for a few microseconds while the two worker-threads
18242 compete for the mutex. Bugfix on 0.2.0.1-alpha.
18245 Changes in version 0.2.2.10-alpha - 2010-03-07
18246 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
18247 could prevent relays from guessing their IP address correctly. It also
18248 starts the groundwork for another client-side performance boost, since
18249 currently we're not making efficient use of relays that have both the
18250 Guard flag and the Exit flag.
18253 - Fix a regression from our patch for bug 1244 that caused relays
18254 to guess their IP address incorrectly if they didn't set Address
18255 in their torrc and/or their address fails to resolve. Bugfix on
18256 0.2.2.9-alpha; fixes bug 1269.
18258 o Major features (performance):
18259 - Directory authorities now compute consensus weightings that instruct
18260 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
18261 and no flag. Clients that use these weightings will distribute
18262 network load more evenly across these different relay types. The
18263 weightings are in the consensus so we can change them globally in
18264 the future. Extra thanks to "outofwords" for finding some nasty
18265 security bugs in the first implementation of this feature.
18267 o Minor features (performance):
18268 - Always perform router selections using weighted relay bandwidth,
18269 even if we don't need a high capacity circuit at the time. Non-fast
18270 circuits now only differ from fast ones in that they can use relays
18271 not marked with the Fast flag. This "feature" could turn out to
18272 be a horrible bug; we should investigate more before it goes into
18276 - Allow disabling building of the manpages. Skipping the manpage
18277 speeds up the build considerably.
18279 o Minor bugfixes (on 0.2.2.x):
18280 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
18281 Bugfix on 0.2.2.9-alpha.
18282 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
18283 config option. Bugfix on 0.2.2.7-alpha.
18284 - Ship the asciidoc-helper file in the tarball, so that people can
18285 build from source if they want to, and touching the .1.txt files
18286 doesn't break the build. Bugfix on 0.2.2.9-alpha.
18288 o Minor bugfixes (on 0.2.1.x or earlier):
18289 - Fix a dereference-then-NULL-check sequence when publishing
18290 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
18292 - Fix another dereference-then-NULL-check sequence. Bugfix on
18293 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
18294 - Make sure we treat potentially not NUL-terminated strings correctly.
18295 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
18297 o Code simplifications and refactoring:
18298 - Fix some urls in the exit notice file and make it XHTML1.1 strict
18299 compliant. Based on a patch from Christian Kujau.
18300 - Don't use sed in asciidoc-helper anymore.
18301 - Make the build process fail if asciidoc cannot be found and
18302 building with asciidoc isn't disabled.
18305 Changes in version 0.2.2.9-alpha - 2010-02-22
18306 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
18307 location of a directory authority, and cleans up a bunch of small bugs.
18309 o Directory authority changes:
18310 - Change IP address for dannenberg (v3 directory authority), and
18311 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
18312 service directory authority) from the list.
18315 - Make Tor work again on the latest OS X: when deciding whether to
18316 use strange flags to turn TLS renegotiation on, detect the OpenSSL
18317 version at run-time, not compile time. We need to do this because
18318 Apple doesn't update its dev-tools headers when it updates its
18319 libraries in a security patch.
18320 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
18321 that could happen on 32-bit platforms with 64-bit time_t. Also fix
18322 a memory leak when requesting a hidden service descriptor we've
18323 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
18325 - Authorities could be tricked into giving out the Exit flag to relays
18326 that didn't allow exiting to any ports. This bug could screw
18327 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
18328 1238. Bug discovered by Martin Kowalczyk.
18329 - When freeing a session key, zero it out completely. We only zeroed
18330 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
18331 patched by ekir. Fixes bug 1254.
18334 - Fix static compilation by listing the openssl libraries in the right
18335 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
18336 - Resume handling .exit hostnames in a special way: originally we
18337 stripped the .exit part and used the requested exit relay. In
18338 0.2.2.1-alpha we stopped treating them in any special way, meaning
18339 if you use a .exit address then Tor will pass it on to the exit
18340 relay. Now we reject the .exit stream outright, since that behavior
18341 might be more expected by the user. Found and diagnosed by Scott
18342 Bennett and Downie on or-talk.
18343 - Don't spam the controller with events when we have no file
18344 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
18345 for log messages was already solved from bug 748.)
18346 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
18348 - Make the DNSPort option work with libevent 2.x. Don't alter the
18349 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
18350 - Emit a GUARD DROPPED controller event for a case we missed.
18351 - Make more fields in the controller protocol case-insensitive, since
18352 control-spec.txt said they were.
18353 - Refactor resolve_my_address() to not use gethostbyname() anymore.
18354 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
18355 - Fix a spec conformance issue: the network-status-version token
18356 must be the first token in a v3 consensus or vote. Discovered by
18357 parakeep. Bugfix on 0.2.0.3-alpha.
18359 o Code simplifications and refactoring:
18360 - Generate our manpage and HTML documentation using Asciidoc. This
18361 change should make it easier to maintain the documentation, and
18362 produce nicer HTML.
18363 - Remove the --enable-iphone option. According to reports from Marco
18364 Bonetti, Tor builds fine without any special tweaking on recent
18365 iPhone SDK versions.
18366 - Removed some unnecessary files from the source distribution. The
18367 AUTHORS file has now been merged into the people page on the
18368 website. The roadmaps and design doc can now be found in the
18369 projects directory in svn.
18370 - Enabled various circuit build timeout constants to be controlled
18371 by consensus parameters. Also set better defaults for these
18372 parameters based on experimentation on broadband and simulated
18373 high latency links.
18376 - The 'EXTENDCIRCUIT' control port command can now be used with
18377 a circ id of 0 and no path. This feature will cause Tor to build
18378 a new 'fast' general purpose circuit using its own path selection
18380 - Added a BUILDTIMEOUT_SET controller event to describe changes
18381 to the circuit build timeout.
18382 - Future-proof the controller protocol a bit by ignoring keyword
18383 arguments we do not recognize.
18384 - Expand homedirs passed to tor-checkkey. This should silence a
18385 coverity complaint about passing a user-supplied string into
18386 open() without checking it.
18389 Changes in version 0.2.1.25 - 2010-03-16
18390 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
18391 prevent relays from guessing their IP address correctly. It also fixes
18392 several minor potential security bugs.
18395 - Fix a regression from our patch for bug 1244 that caused relays
18396 to guess their IP address incorrectly if they didn't set Address
18397 in their torrc and/or their address fails to resolve. Bugfix on
18398 0.2.1.23; fixes bug 1269.
18399 - When freeing a session key, zero it out completely. We only zeroed
18400 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
18401 patched by ekir. Fixes bug 1254.
18404 - Fix a dereference-then-NULL-check sequence when publishing
18405 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
18407 - Fix another dereference-then-NULL-check sequence. Bugfix on
18408 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
18409 - Make sure we treat potentially not NUL-terminated strings correctly.
18410 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
18414 Changes in version 0.2.1.24 - 2010-02-21
18415 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
18419 - Work correctly out-of-the-box with even more vendor-patched versions
18420 of OpenSSL. In particular, make it so Debian and OS X don't need
18421 customized patches to run/build.
18424 Changes in version 0.2.1.23 - 2010-02-13
18425 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
18426 again on the latest OS X, and updates the location of a directory
18429 o Major bugfixes (performance):
18430 - We were selecting our guards uniformly at random, and then weighting
18431 which of our guards we'd use uniformly at random. This imbalance
18432 meant that Tor clients were severely limited on throughput (and
18433 probably latency too) by the first hop in their circuit. Now we
18434 select guards weighted by currently advertised bandwidth. We also
18435 automatically discard guards picked using the old algorithm. Fixes
18436 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
18439 - Make Tor work again on the latest OS X: when deciding whether to
18440 use strange flags to turn TLS renegotiation on, detect the OpenSSL
18441 version at run-time, not compile time. We need to do this because
18442 Apple doesn't update its dev-tools headers when it updates its
18443 libraries in a security patch.
18444 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
18445 that could happen on 32-bit platforms with 64-bit time_t. Also fix
18446 a memory leak when requesting a hidden service descriptor we've
18447 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
18450 o Directory authority changes:
18451 - Change IP address for dannenberg (v3 directory authority), and
18452 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
18453 service directory authority) from the list.
18456 - Refactor resolve_my_address() to not use gethostbyname() anymore.
18457 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
18460 - Avoid a mad rush at the beginning of each month when each client
18461 rotates half of its guards. Instead we spread the rotation out
18462 throughout the month, but we still avoid leaving a precise timestamp
18463 in the state file about when we first picked the guard. Improves
18464 over the behavior introduced in 0.1.2.17.
18467 Changes in version 0.2.2.8-alpha - 2010-01-26
18468 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
18469 causing bridge relays to disappear. If you're running a bridge,
18473 - Fix a memory corruption bug on bridges that occurred during the
18474 inclusion of stats data in extra-info descriptors. Also fix the
18475 interface for geoip_get_bridge_stats* to prevent similar bugs in
18476 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
18477 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
18480 - Ignore OutboundBindAddress when connecting to localhost.
18481 Connections to localhost need to come _from_ localhost, or else
18482 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
18486 Changes in version 0.2.2.7-alpha - 2010-01-19
18487 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
18488 as laying the groundwork for further relay-side performance fixes. It
18489 also starts cleaning up client behavior with respect to the EntryNodes,
18490 ExitNodes, and StrictNodes config options.
18492 This release also rotates two directory authority keys, due to a
18493 security breach of some of the Torproject servers.
18495 o Directory authority changes:
18496 - Rotate keys (both v3 identity and relay identity) for moria1
18499 o Major features (performance):
18500 - We were selecting our guards uniformly at random, and then weighting
18501 which of our guards we'd use uniformly at random. This imbalance
18502 meant that Tor clients were severely limited on throughput (and
18503 probably latency too) by the first hop in their circuit. Now we
18504 select guards weighted by currently advertised bandwidth. We also
18505 automatically discard guards picked using the old algorithm. Fixes
18506 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
18507 - When choosing which cells to relay first, relays can now favor
18508 circuits that have been quiet recently, to provide lower latency
18509 for low-volume circuits. By default, relays enable or disable this
18510 feature based on a setting in the consensus. You can override
18511 this default by using the new "CircuitPriorityHalflife" config
18512 option. Design and code by Ian Goldberg, Can Tang, and Chris
18514 - Add separate per-conn write limiting to go with the per-conn read
18515 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
18516 but never per-conn write limits.
18517 - New consensus params "bwconnrate" and "bwconnburst" to let us
18518 rate-limit client connections as they enter the network. It's
18519 controlled in the consensus so we can turn it on and off for
18520 experiments. It's starting out off. Based on proposal 163.
18522 o Major features (relay selection options):
18523 - Switch to a StrictNodes config option, rather than the previous
18524 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
18525 "StrictExcludeNodes" option.
18526 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
18527 change during a config reload, mark and discard all our origin
18528 circuits. This fix should address edge cases where we change the
18529 config options and but then choose a circuit that we created before
18531 - If EntryNodes or ExitNodes are set, be more willing to use an
18532 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
18534 - Make EntryNodes config option much more aggressive even when
18535 StrictNodes is not set. Before it would prepend your requested
18536 entrynodes to your list of guard nodes, but feel free to use others
18537 after that. Now it chooses only from your EntryNodes if any of
18538 those are available, and only falls back to others if a) they're
18539 all down and b) StrictNodes is not set.
18540 - Now we refresh your entry guards from EntryNodes at each consensus
18541 fetch -- rather than just at startup and then they slowly rot as
18542 the network changes.
18545 - Stop bridge directory authorities from answering dbg-stability.txt
18546 directory queries, which would let people fetch a list of all
18547 bridge identities they track. Bugfix on 0.2.1.6-alpha.
18550 - Log a notice when we get a new control connection. Now it's easier
18551 for security-conscious users to recognize when a local application
18552 is knocking on their controller door. Suggested by bug 1196.
18553 - New config option "CircuitStreamTimeout" to override our internal
18554 timeout schedule for how many seconds until we detach a stream from
18555 a circuit and try a new circuit. If your network is particularly
18556 slow, you might want to set this to a number like 60.
18557 - New controller command "getinfo config-text". It returns the
18558 contents that Tor would write if you send it a SAVECONF command,
18559 so the controller can write the file to disk itself.
18560 - New options for SafeLogging to allow scrubbing only log messages
18561 generated while acting as a relay.
18562 - Ship the bridges spec file in the tarball too.
18563 - Avoid a mad rush at the beginning of each month when each client
18564 rotates half of its guards. Instead we spread the rotation out
18565 throughout the month, but we still avoid leaving a precise timestamp
18566 in the state file about when we first picked the guard. Improves
18567 over the behavior introduced in 0.1.2.17.
18569 o Minor bugfixes (compiling):
18570 - Fix compilation on OS X 10.3, which has a stub mlockall() but
18571 hides it. Bugfix on 0.2.2.6-alpha.
18572 - Fix compilation on Solaris by removing support for the
18573 DisableAllSwap config option. Solaris doesn't have an rlimit for
18574 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
18577 o Minor bugfixes (crashes):
18578 - Do not segfault when writing buffer stats when we haven't observed
18579 a single circuit to report about. Found by Fabian Lanze. Bugfix on
18581 - If we're in the pathological case where there's no exit bandwidth
18582 but there is non-exit bandwidth, or no guard bandwidth but there
18583 is non-guard bandwidth, don't crash during path selection. Bugfix
18585 - Fix an impossible-to-actually-trigger buffer overflow in relay
18586 descriptor generation. Bugfix on 0.1.0.15.
18588 o Minor bugfixes (privacy):
18589 - Fix an instance where a Tor directory mirror might accidentally
18590 log the IP address of a misbehaving Tor client. Bugfix on
18592 - Don't list Windows capabilities in relay descriptors. We never made
18593 use of them, and maybe it's a bad idea to publish them. Bugfix
18596 o Minor bugfixes (other):
18597 - Resolve an edge case in path weighting that could make us misweight
18598 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
18599 - Fix statistics on client numbers by country as seen by bridges that
18600 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
18601 intervals instead of variable 12-to-48-hour intervals.
18602 - After we free an internal connection structure, overwrite it
18603 with a different memory value than we use for overwriting a freed
18604 internal circuit structure. Should help with debugging. Suggested
18606 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
18609 o Removed features:
18610 - Remove the HSAuthorityRecordStats option that version 0 hidden
18611 service authorities could have used to track statistics of overall
18612 hidden service usage.
18615 Changes in version 0.2.1.22 - 2010-01-19
18616 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
18617 authorities -- it would tell you its whole history of bridge descriptors
18618 if you make the right directory request. This stable update also
18619 rotates two of the seven v3 directory authority keys and locations.
18621 o Directory authority changes:
18622 - Rotate keys (both v3 identity and relay identity) for moria1
18626 - Stop bridge directory authorities from answering dbg-stability.txt
18627 directory queries, which would let people fetch a list of all
18628 bridge identities they track. Bugfix on 0.2.1.6-alpha.
18631 Changes in version 0.2.1.21 - 2009-12-21
18632 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
18633 library. If you use Tor on Linux / Unix and you're getting SSL
18634 renegotiation errors, upgrading should help. We also recommend an
18635 upgrade if you're an exit relay.
18638 - Work around a security feature in OpenSSL 0.9.8l that prevents our
18639 handshake from working unless we explicitly tell OpenSSL that we
18640 are using SSL renegotiation safely. We are, of course, but OpenSSL
18641 0.9.8l won't work unless we say we are.
18642 - Avoid crashing if the client is trying to upload many bytes and the
18643 circuit gets torn down at the same time, or if the flip side
18644 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
18647 - Do not refuse to learn about authority certs and v2 networkstatus
18648 documents that are older than the latest consensus. This bug might
18649 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
18650 Spotted and fixed by xmux.
18651 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
18652 trigger platform-specific option misparsing case found by Coverity
18654 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
18655 trigger assert. Fixes bug 1173.
18658 Changes in version 0.2.2.6-alpha - 2009-11-19
18659 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
18660 support for the new lower-footprint "microdescriptor" directory design,
18661 future-proofing our consensus format against new hash functions or
18662 other changes, and an Android port. It also makes Tor compatible with
18663 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
18666 - Directory authorities can now create, vote on, and serve multiple
18667 parallel formats of directory data as part of their voting process.
18668 Partially implements Proposal 162: "Publish the consensus in
18670 - Directory authorities can now agree on and publish small summaries
18671 of router information that clients can use in place of regular
18672 server descriptors. This transition will eventually allow clients
18673 to use far less bandwidth for downloading information about the
18674 network. Begins the implementation of Proposal 158: "Clients
18675 download consensus + microdescriptors".
18676 - The directory voting system is now extensible to use multiple hash
18677 algorithms for signatures and resource selection. Newer formats
18678 are signed with SHA256, with a possibility for moving to a better
18679 hash algorithm in the future.
18680 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
18681 current and future memory pages via mlockall(). On supported
18682 platforms (modern Linux and probably BSD but not Windows or OS X),
18683 this should effectively disable any and all attempts to page out
18684 memory. This option requires that you start your Tor as root --
18685 if you use DisableAllSwap, please consider using the User option
18686 to properly reduce the privileges of your Tor.
18687 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
18688 to help Tor build correctly for Android phones.
18691 - Work around a security feature in OpenSSL 0.9.8l that prevents our
18692 handshake from working unless we explicitly tell OpenSSL that we
18693 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
18694 won't work unless we say we are.
18697 - Fix a crash bug when trying to initialize the evdns module in
18698 Libevent 2. Bugfix on 0.2.1.16-rc.
18699 - Stop logging at severity 'warn' when some other Tor client tries
18700 to establish a circuit with us using weak DH keys. It's a protocol
18701 violation, but that doesn't mean ordinary users need to hear about
18702 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
18703 - Do not refuse to learn about authority certs and v2 networkstatus
18704 documents that are older than the latest consensus. This bug might
18705 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
18706 Spotted and fixed by xmux.
18707 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
18708 - If all authorities restart at once right before a consensus vote,
18709 nobody will vote about "Running", and clients will get a consensus
18710 with no usable relays. Instead, authorities refuse to build a
18711 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
18712 - If your relay can't keep up with the number of incoming create
18713 cells, it would log one warning per failure into your logs. Limit
18714 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
18715 - Bridges now use "reject *:*" as their default exit policy. Bugfix
18716 on 0.2.0.3-alpha; fixes bug 1113.
18717 - Fix a memory leak on directory authorities during voting that was
18718 introduced in 0.2.2.1-alpha. Found via valgrind.
18721 Changes in version 0.2.1.20 - 2009-10-15
18722 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
18723 services at once, prepares for more performance improvements, and
18724 fixes a bunch of smaller bugs.
18726 The Windows and OS X bundles also include a more recent Vidalia,
18727 and switch from Privoxy to Polipo.
18729 The OS X installers are now drag and drop. It's best to un-install
18730 Tor/Vidalia and then install this new bundle, rather than upgrade. If
18731 you want to upgrade, you'll need to update the paths for Tor and Polipo
18732 in the Vidalia Settings window.
18735 - Send circuit or stream sendme cells when our window has decreased
18736 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18737 by Karsten when testing the "reduce circuit window" performance
18738 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18739 before the release of Tor 0.0.0. This is the new winner of the
18741 - Fix a remotely triggerable memory leak when a consensus document
18742 contains more than one signature from the same voter. Bugfix on
18744 - Avoid segfault in rare cases when finishing an introduction circuit
18745 as a client and finding out that we don't have an introduction key
18746 for it. Fixes bug 1073. Reported by Aaron Swartz.
18749 - Tor now reads the "circwindow" parameter out of the consensus,
18750 and uses that value for its circuit package window rather than the
18751 default of 1000 cells. Begins the implementation of proposal 168.
18753 o New directory authorities:
18754 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18756 - Move moria1 and tonga to alternate IP addresses.
18759 - Fix a signed/unsigned compile warning in 0.2.1.19.
18760 - Fix possible segmentation fault on directory authorities. Bugfix on
18762 - Fix an extremely rare infinite recursion bug that could occur if
18763 we tried to log a message after shutting down the log subsystem.
18764 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18765 - Fix an obscure bug where hidden services on 64-bit big-endian
18766 systems might mis-read the timestamp in v3 introduce cells, and
18767 refuse to connect back to the client. Discovered by "rotor".
18768 Bugfix on 0.2.1.6-alpha.
18769 - We were triggering a CLOCK_SKEW controller status event whenever
18770 we connect via the v2 connection protocol to any relay that has
18771 a wrong clock. Instead, we should only inform the controller when
18772 it's a trusted authority that claims our clock is wrong. Bugfix
18773 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18774 - We were telling the controller about CHECKING_REACHABILITY and
18775 REACHABILITY_FAILED status events whenever we launch a testing
18776 circuit or notice that one has failed. Instead, only tell the
18777 controller when we want to inform the user of overall success or
18778 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18780 - Don't warn when we're using a circuit that ends with a node
18781 excluded in ExcludeExitNodes, but the circuit is not used to access
18782 the outside world. This should help fix bug 1090. Bugfix on
18784 - Work around a small memory leak in some versions of OpenSSL that
18785 stopped the memory used by the hostname TLS extension from being
18789 - Add a "getinfo status/accepted-server-descriptor" controller
18790 command, which is the recommended way for controllers to learn
18791 whether our server descriptor has been successfully received by at
18792 least on directory authority. Un-recommend good-server-descriptor
18793 getinfo and status events until we have a better design for them.
18796 Changes in version 0.2.2.5-alpha - 2009-10-11
18797 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
18800 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
18802 o Directory authorities:
18803 - Temporarily (just for this release) move dizum to an alternate
18807 Changes in version 0.2.2.4-alpha - 2009-10-10
18808 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
18809 introduces a new unit test framework, shifts directry authority
18810 addresses around to reduce the impact from recent blocking events,
18811 and fixes a few smaller bugs.
18814 - Fix several more asserts in the circuit_build_times code, for
18815 example one that causes Tor to fail to start once we have
18816 accumulated 5000 build times in the state file. Bugfixes on
18817 0.2.2.2-alpha; fixes bug 1108.
18819 o New directory authorities:
18820 - Move moria1 and Tonga to alternate IP addresses.
18823 - Log SSL state transitions at debug level during handshake, and
18824 include SSL states in error messages. This may help debug future
18825 SSL handshake issues.
18826 - Add a new "Handshake" log domain for activities that happen
18827 during the TLS handshake.
18828 - Revert to the "June 3 2009" ip-to-country file. The September one
18829 seems to have removed most US IP addresses.
18830 - Directory authorities now reject Tor relays with versions less than
18831 0.1.2.14. This step cuts out four relays from the current network,
18832 none of which are very big.
18835 - Fix a couple of smaller issues with gathering statistics. Bugfixes
18837 - Fix two memory leaks in the error case of
18838 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
18839 - Don't count one-hop circuits when we're estimating how long it
18840 takes circuits to build on average. Otherwise we'll set our circuit
18841 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
18842 - Directory authorities no longer change their opinion of, or vote on,
18843 whether a router is Running, unless they have themselves been
18844 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
18847 o Code simplifications and refactoring:
18848 - Revise our unit tests to use the "tinytest" framework, so we
18849 can run tests in their own processes, have smarter setup/teardown
18850 code, and so on. The unit test code has moved to its own
18851 subdirectory, and has been split into multiple modules.
18854 Changes in version 0.2.2.3-alpha - 2009-09-23
18855 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
18858 - Fix an overzealous assert in our new circuit build timeout code.
18859 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
18862 - If the networkstatus consensus tells us that we should use a
18863 negative circuit package window, ignore it. Otherwise we'll
18864 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
18867 Changes in version 0.2.2.2-alpha - 2009-09-21
18868 Tor 0.2.2.2-alpha introduces our latest performance improvement for
18869 clients: Tor tracks the average time it takes to build a circuit, and
18870 avoids using circuits that take too long to build. For fast connections,
18871 this feature can cut your expected latency in half. For slow or flaky
18872 connections, it could ruin your Tor experience. Let us know if it does!
18875 - Tor now tracks how long it takes to build client-side circuits
18876 over time, and adapts its timeout to local network performance.
18877 Since a circuit that takes a long time to build will also provide
18878 bad performance, we get significant latency improvements by
18879 discarding the slowest 20% of circuits. Specifically, Tor creates
18880 circuits more aggressively than usual until it has enough data
18881 points for a good timeout estimate. Implements proposal 151.
18882 We are especially looking for reports (good and bad) from users with
18883 both EDGE and broadband connections that can move from broadband
18884 to EDGE and find out if the build-time data in the .tor/state gets
18885 reset without loss of Tor usability. You should also see a notice
18886 log message telling you that Tor has reset its timeout.
18887 - Directory authorities can now vote on arbitrary integer values as
18888 part of the consensus process. This is designed to help set
18889 network-wide parameters. Implements proposal 167.
18890 - Tor now reads the "circwindow" parameter out of the consensus,
18891 and uses that value for its circuit package window rather than the
18892 default of 1000 cells. Begins the implementation of proposal 168.
18895 - Fix a remotely triggerable memory leak when a consensus document
18896 contains more than one signature from the same voter. Bugfix on
18900 - Fix an extremely rare infinite recursion bug that could occur if
18901 we tried to log a message after shutting down the log subsystem.
18902 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18903 - Fix parsing for memory or time units given without a space between
18904 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
18905 - A networkstatus vote must contain exactly one signature. Spec
18906 conformance issue. Bugfix on 0.2.0.3-alpha.
18907 - Fix an obscure bug where hidden services on 64-bit big-endian
18908 systems might mis-read the timestamp in v3 introduce cells, and
18909 refuse to connect back to the client. Discovered by "rotor".
18910 Bugfix on 0.2.1.6-alpha.
18911 - We were triggering a CLOCK_SKEW controller status event whenever
18912 we connect via the v2 connection protocol to any relay that has
18913 a wrong clock. Instead, we should only inform the controller when
18914 it's a trusted authority that claims our clock is wrong. Bugfix
18915 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18916 - We were telling the controller about CHECKING_REACHABILITY and
18917 REACHABILITY_FAILED status events whenever we launch a testing
18918 circuit or notice that one has failed. Instead, only tell the
18919 controller when we want to inform the user of overall success or
18920 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18922 - Don't warn when we're using a circuit that ends with a node
18923 excluded in ExcludeExitNodes, but the circuit is not used to access
18924 the outside world. This should help fix bug 1090, but more problems
18925 remain. Bugfix on 0.2.1.6-alpha.
18926 - Work around a small memory leak in some versions of OpenSSL that
18927 stopped the memory used by the hostname TLS extension from being
18929 - Make our 'torify' script more portable; if we have only one of
18930 'torsocks' or 'tsocks' installed, don't complain to the user;
18931 and explain our warning about tsocks better.
18934 - Add a "getinfo status/accepted-server-descriptor" controller
18935 command, which is the recommended way for controllers to learn
18936 whether our server descriptor has been successfully received by at
18937 least on directory authority. Un-recommend good-server-descriptor
18938 getinfo and status events until we have a better design for them.
18939 - Update to the "September 4 2009" ip-to-country file.
18942 Changes in version 0.2.2.1-alpha - 2009-08-26
18943 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
18944 Tor clients to bootstrap on networks where only port 80 is reachable,
18945 makes it more straightforward to support hardware crypto accelerators,
18946 and starts the groundwork for gathering stats safely at relays.
18949 - Start the process of disabling ".exit" address notation, since it
18950 can be used for a variety of esoteric application-level attacks
18951 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
18954 o New directory authorities:
18955 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18959 - New AccelName and AccelDir options add support for dynamic OpenSSL
18960 hardware crypto acceleration engines.
18961 - Tor now supports tunneling all of its outgoing connections over
18962 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
18963 configuration options. Code by Christopher Davis.
18966 - Send circuit or stream sendme cells when our window has decreased
18967 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18968 by Karsten when testing the "reduce circuit window" performance
18969 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18970 before the release of Tor 0.0.0. This is the new winner of the
18973 o New options for gathering stats safely:
18974 - Directory mirrors that set "DirReqStatistics 1" write statistics
18975 about directory requests to disk every 24 hours. As compared to the
18976 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
18977 1) stats are written to disk exactly every 24 hours; 2) estimated
18978 shares of v2 and v3 requests are determined as mean values, not at
18979 the end of a measurement period; 3) unresolved requests are listed
18980 with country code '??'; 4) directories also measure download times.
18981 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
18982 number of exit streams and transferred bytes per port to disk every
18984 - Relays that set "CellStatistics 1" write statistics on how long
18985 cells spend in their circuit queues to disk every 24 hours.
18986 - Entry nodes that set "EntryStatistics 1" write statistics on the
18987 rough number and origins of connecting clients to disk every 24
18989 - Relays that write any of the above statistics to disk and set
18990 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
18991 their extra-info documents.
18994 - New --digests command-line switch to output the digests of the
18995 source files Tor was built with.
18996 - The "torify" script now uses torsocks where available.
18997 - The memarea code now uses a sentinel value at the end of each area
18998 to make sure nothing writes beyond the end of an area. This might
18999 help debug some conceivable causes of bug 930.
19000 - Time and memory units in the configuration file can now be set to
19001 fractional units. For example, "2.5 GB" is now a valid value for
19003 - Certain Tor clients (such as those behind check.torproject.org) may
19004 want to fetch the consensus in an extra early manner. To enable this
19005 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
19006 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
19007 as only certain clients who must have this information sooner should
19009 - Instead of adding the svn revision to the Tor version string, report
19010 the git commit (when we're building from a git checkout).
19013 - If any of the v3 certs we download are unparseable, we should
19014 actually notice the failure so we don't retry indefinitely. Bugfix
19015 on 0.2.0.x; reported by "rotator".
19016 - If the cached cert file is unparseable, warn but don't exit.
19017 - Fix possible segmentation fault on directory authorities. Bugfix on
19019 - When Tor fails to parse a descriptor of any kind, dump it to disk.
19020 Might help diagnosing bug 1051.
19022 o Deprecated and removed features:
19023 - The controller no longer accepts the old obsolete "addr-mappings/"
19024 or "unregistered-servers-" GETINFO values.
19025 - Hidden services no longer publish version 0 descriptors, and clients
19026 do not request or use version 0 descriptors. However, the old hidden
19027 service authorities still accept and serve version 0 descriptors
19028 when contacted by older hidden services/clients.
19029 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
19030 always on; using them is necessary for correct forward-compatible
19032 - Remove support for .noconnect style addresses. Nobody was using
19033 them, and they provided another avenue for detecting Tor users
19034 via application-level web tricks.
19036 o Packaging changes:
19037 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
19038 installer bundles. See
19039 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
19040 for details of what's new in Vidalia 0.2.3.
19041 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
19042 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
19043 configuration file, rather than the old Privoxy.
19044 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
19045 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
19046 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
19047 better compatibility with OS X 10.6, aka Snow Leopard.
19048 - OS X Vidalia Bundle: The multi-package installer is now replaced
19049 by a simple drag and drop to the /Applications folder. This change
19050 occurred with the upgrade to Vidalia 0.2.3.
19053 Changes in version 0.2.1.19 - 2009-07-28
19054 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
19055 services on Tor 0.2.1.3-alpha through 0.2.1.18.
19058 - Make accessing hidden services on 0.2.1.x work right again.
19059 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
19060 part of patch provided by "optimist".
19063 - When a relay/bridge is writing out its identity key fingerprint to
19064 the "fingerprint" file and to its logs, write it without spaces. Now
19065 it will look like the fingerprints in our bridges documentation,
19066 and confuse fewer users.
19069 - Relays no longer publish a new server descriptor if they change
19070 their MaxAdvertisedBandwidth config option but it doesn't end up
19071 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
19072 fixes bug 1026. Patch from Sebastian.
19073 - Avoid leaking memory every time we get a create cell but we have
19074 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
19075 fixes bug 1034. Reported by BarkerJr.
19078 Changes in version 0.2.1.18 - 2009-07-24
19079 Tor 0.2.1.18 lays the foundations for performance improvements,
19080 adds status events to help users diagnose bootstrap problems, adds
19081 optional authentication/authorization for hidden services, fixes a
19082 variety of potential anonymity problems, and includes a huge pile of
19083 other features and bug fixes.
19086 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
19089 Changes in version 0.2.1.17-rc - 2009-07-07
19090 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
19091 candidate for the 0.2.1.x series. It lays the groundwork for further
19092 client performance improvements, and also fixes a big bug with directory
19093 authorities that were causing them to assign Guard and Stable flags
19096 The Windows bundles also finally include the geoip database that we
19097 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
19098 should actually install Torbutton rather than giving you a cryptic
19099 failure message (oops).
19102 - Clients now use the bandwidth values in the consensus, rather than
19103 the bandwidth values in each relay descriptor. This approach opens
19104 the door to more accurate bandwidth estimates once the directory
19105 authorities start doing active measurements. Implements more of
19109 - When Tor clients restart after 1-5 days, they discard all their
19110 cached descriptors as too old, but they still use the cached
19111 consensus document. This approach is good for robustness, but
19112 bad for performance: since they don't know any bandwidths, they
19113 end up choosing at random rather than weighting their choice by
19114 speed. Fixed by the above feature of putting bandwidths in the
19115 consensus. Bugfix on 0.2.0.x.
19116 - Directory authorities were neglecting to mark relays down in their
19117 internal histories if the relays fall off the routerlist without
19118 ever being found unreachable. So there were relays in the histories
19119 that haven't been seen for eight months, and are listed as being
19120 up for eight months. This wreaked havoc on the "median wfu"
19121 and "median mtbf" calculations, in turn making Guard and Stable
19122 flags very wrong, hurting network performance. Fixes bugs 696 and
19123 969. Bugfix on 0.2.0.6-alpha.
19126 - Serve the DirPortFrontPage page even when we have been approaching
19127 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
19128 - The control port would close the connection before flushing long
19129 replies, such as the network consensus, if a QUIT command was issued
19130 before the reply had completed. Now, the control port flushes all
19131 pending replies before closing the connection. Also fixed a spurious
19132 warning when a QUIT command is issued after a malformed or rejected
19133 AUTHENTICATE command, but before the connection was closed. Patch
19134 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
19135 - When we can't find an intro key for a v2 hidden service descriptor,
19136 fall back to the v0 hidden service descriptor and log a bug message.
19137 Workaround for bug 1024.
19138 - Fix a log message that did not respect the SafeLogging option.
19142 - If we're a relay and we change our IP address, be more verbose
19143 about the reason that made us change. Should help track down
19144 further bugs for relays on dynamic IP addresses.
19147 Changes in version 0.2.0.35 - 2009-06-24
19149 - Avoid crashing in the presence of certain malformed descriptors.
19150 Found by lark, and by automated fuzzing.
19151 - Fix an edge case where a malicious exit relay could convince a
19152 controller that the client's DNS question resolves to an internal IP
19153 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
19156 - Finally fix the bug where dynamic-IP relays disappear when their
19157 IP address changes: directory mirrors were mistakenly telling
19158 them their old address if they asked via begin_dir, so they
19159 never got an accurate answer about their new address, so they
19160 just vanished after a day. For belt-and-suspenders, relays that
19161 don't set Address in their config now avoid using begin_dir for
19162 all direct connections. Should fix bugs 827, 883, and 900.
19163 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
19164 that would occur on some exit nodes when DNS failures and timeouts
19165 occurred in certain patterns. Fix for bug 957.
19168 - When starting with a cache over a few days old, do not leak
19169 memory for the obsolete router descriptors in it. Bugfix on
19170 0.2.0.33; fixes bug 672.
19171 - Hidden service clients didn't use a cached service descriptor that
19172 was older than 15 minutes, but wouldn't fetch a new one either,
19173 because there was already one in the cache. Now, fetch a v2
19174 descriptor unless the same descriptor was added to the cache within
19175 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
19178 Changes in version 0.2.1.16-rc - 2009-06-20
19179 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
19180 a bunch of minor bugs.
19183 - Fix an edge case where a malicious exit relay could convince a
19184 controller that the client's DNS question resolves to an internal IP
19185 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
19187 o Major performance improvements (on 0.2.0.x):
19188 - Disable and refactor some debugging checks that forced a linear scan
19189 over the whole server-side DNS cache. These accounted for over 50%
19190 of CPU time on a relatively busy exit node's gprof profile. Found
19192 - Disable some debugging checks that appeared in exit node profile
19196 - Update to the "June 3 2009" ip-to-country file.
19197 - Do not have tor-resolve automatically refuse all .onion addresses;
19198 if AutomapHostsOnResolve is set in your torrc, this will work fine.
19200 o Minor bugfixes (on 0.2.0.x):
19201 - Log correct error messages for DNS-related network errors on
19203 - Fix a race condition that could cause crashes or memory corruption
19204 when running as a server with a controller listening for log
19206 - Avoid crashing when we have a policy specified in a DirPolicy or
19207 SocksPolicy or ReachableAddresses option with ports set on it,
19208 and we re-load the policy. May fix bug 996.
19209 - Hidden service clients didn't use a cached service descriptor that
19210 was older than 15 minutes, but wouldn't fetch a new one either,
19211 because there was already one in the cache. Now, fetch a v2
19212 descriptor unless the same descriptor was added to the cache within
19213 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
19215 o Minor bugfixes (on 0.2.1.x):
19216 - Don't warn users about low port and hibernation mix when they
19217 provide a *ListenAddress directive to fix that. Bugfix on
19219 - When switching back and forth between bridge mode, do not start
19220 gathering GeoIP data until two hours have passed.
19221 - Do not complain that the user has requested an excluded node as
19222 an exit when the node is not really an exit. This could happen
19223 because the circuit was for testing, or an introduction point.
19227 Changes in version 0.2.1.15-rc - 2009-05-25
19228 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
19229 series. It fixes a major bug on fast exit relays, as well as a variety
19230 of more minor bugs.
19232 o Major bugfixes (on 0.2.0.x):
19233 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
19234 that would occur on some exit nodes when DNS failures and timeouts
19235 occurred in certain patterns. Fix for bug 957.
19237 o Minor bugfixes (on 0.2.0.x):
19238 - Actually return -1 in the error case for read_bandwidth_usage().
19239 Harmless bug, since we currently don't care about the return value
19240 anywhere. Bugfix on 0.2.0.9-alpha.
19241 - Provide a more useful log message if bug 977 (related to buffer
19242 freelists) ever reappears, and do not crash right away.
19243 - Fix an assertion failure on 64-bit platforms when we allocated
19244 memory right up to the end of a memarea, then realigned the memory
19245 one step beyond the end. Fixes a possible cause of bug 930.
19246 - Protect the count of open sockets with a mutex, so we can't
19247 corrupt it when two threads are closing or opening sockets at once.
19248 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
19249 - Don't allow a bridge to publish its router descriptor to a
19250 non-bridge directory authority. Fixes part of bug 932.
19251 - When we change to or from being a bridge, reset our counts of
19252 client usage by country. Fixes bug 932.
19253 - Fix a bug that made stream bandwidth get misreported to the
19255 - Stop using malloc_usable_size() to use more area than we had
19256 actually allocated: it was safe, but made valgrind really unhappy.
19257 - Fix a memory leak when v3 directory authorities load their keys
19258 and cert from disk. Bugfix on 0.2.0.1-alpha.
19260 o Minor bugfixes (on 0.2.1.x):
19261 - Fix use of freed memory when deciding to mark a non-addable
19262 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
19265 Changes in version 0.2.1.14-rc - 2009-04-12
19266 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
19267 series. It begins fixing some major performance problems, and also
19268 finally addresses the bug that was causing relays on dynamic IP
19269 addresses to fall out of the directory.
19272 - Clients replace entry guards that were chosen more than a few months
19273 ago. This change should significantly improve client performance,
19274 especially once more people upgrade, since relays that have been
19275 a guard for a long time are currently overloaded.
19277 o Major bugfixes (on 0.2.0):
19278 - Finally fix the bug where dynamic-IP relays disappear when their
19279 IP address changes: directory mirrors were mistakenly telling
19280 them their old address if they asked via begin_dir, so they
19281 never got an accurate answer about their new address, so they
19282 just vanished after a day. For belt-and-suspenders, relays that
19283 don't set Address in their config now avoid using begin_dir for
19284 all direct connections. Should fix bugs 827, 883, and 900.
19285 - Relays were falling out of the networkstatus consensus for
19286 part of a day if they changed their local config but the
19287 authorities discarded their new descriptor as "not sufficiently
19288 different". Now directory authorities accept a descriptor as changed
19289 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
19290 patch by Sebastian.
19291 - Avoid crashing in the presence of certain malformed descriptors.
19292 Found by lark, and by automated fuzzing.
19295 - When generating circuit events with verbose nicknames for
19296 controllers, try harder to look up nicknames for routers on a
19297 circuit. (Previously, we would look in the router descriptors we had
19298 for nicknames, but not in the consensus.) Partial fix for bug 941.
19299 - If the bridge config line doesn't specify a port, assume 443.
19300 This makes bridge lines a bit smaller and easier for users to
19302 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
19303 bytes (aka 20KB/s), to match our documentation. Also update
19304 directory authorities so they always assign the Fast flag to relays
19305 with 20KB/s of capacity. Now people running relays won't suddenly
19306 find themselves not seeing any use, if the network gets faster
19308 - Update to the "April 3 2009" ip-to-country file.
19311 - Avoid trying to print raw memory to the logs when we decide to
19312 give up on downloading a given relay descriptor. Bugfix on
19314 - In tor-resolve, when the Tor client to use is specified by
19315 <hostname>:<port>, actually use the specified port rather than
19316 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
19317 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
19318 - When starting with a cache over a few days old, do not leak
19319 memory for the obsolete router descriptors in it. Bugfix on
19321 - Avoid double-free on list of successfully uploaded hidden
19322 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
19323 - Change memarea_strndup() implementation to work even when
19324 duplicating a string at the end of a page. This bug was
19325 harmless for now, but could have meant crashes later. Fix by
19326 lark. Bugfix on 0.2.1.1-alpha.
19327 - Limit uploaded directory documents to be 16M rather than 500K.
19328 The directory authorities were refusing v3 consensus votes from
19329 other authorities, since the votes are now 504K. Fixes bug 959;
19330 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
19331 - Directory authorities should never send a 503 "busy" response to
19332 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
19336 Changes in version 0.2.1.13-alpha - 2009-03-09
19337 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
19338 cleanups. We're finally getting close to a release candidate.
19341 - Correctly update the list of which countries we exclude as
19342 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
19343 lark. Bugfix on 0.2.1.6-alpha.
19345 o Minor bugfixes (on 0.2.0.x and earlier):
19346 - Automatically detect MacOSX versions earlier than 10.4.0, and
19347 disable kqueue from inside Tor when running with these versions.
19348 We previously did this from the startup script, but that was no
19349 help to people who didn't use the startup script. Resolves bug 863.
19350 - When we had picked an exit node for a connection, but marked it as
19351 "optional", and it turned out we had no onion key for the exit,
19352 stop wanting that exit and try again. This situation may not
19353 be possible now, but will probably become feasible with proposal
19354 158. Spotted by rovv. Fixes another case of bug 752.
19355 - Clients no longer cache certificates for authorities they do not
19356 recognize. Bugfix on 0.2.0.9-alpha.
19357 - When we can't transmit a DNS request due to a network error, retry
19358 it after a while, and eventually transmit a failing response to
19359 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
19360 - If the controller claimed responsibility for a stream, but that
19361 stream never finished making its connection, it would live
19362 forever in circuit_wait state. Now we close it after SocksTimeout
19363 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
19364 - Drop begin cells to a hidden service if they come from the middle
19365 of a circuit. Patch from lark.
19366 - When we erroneously receive two EXTEND cells for the same circuit
19367 ID on the same connection, drop the second. Patch from lark.
19368 - Fix a crash that occurs on exit nodes when a nameserver request
19369 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
19370 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
19372 - Do not assume that a stack-allocated character array will be
19373 64-bit aligned on platforms that demand that uint64_t access is
19374 aligned. Possible fix for bug 604.
19375 - Parse dates and IPv4 addresses in a locale- and libc-independent
19376 manner, to avoid platform-dependent behavior on malformed input.
19377 - Build correctly when configured to build outside the main source
19378 path. Patch from Michael Gold.
19379 - We were already rejecting relay begin cells with destination port
19380 of 0. Now also reject extend cells with destination port or address
19381 of 0. Suggested by lark.
19383 o Minor bugfixes (on 0.2.1.x):
19384 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
19385 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
19386 - If we're an exit node, scrub the IP address to which we are exiting
19387 in the logs. Bugfix on 0.2.1.8-alpha.
19390 - On Linux, use the prctl call to re-enable core dumps when the user
19392 - New controller event NEWCONSENSUS that lists the networkstatus
19393 lines for every recommended relay. Now controllers like Torflow
19394 can keep up-to-date on which relays they should be using.
19395 - Update to the "February 26 2009" ip-to-country file.
19398 Changes in version 0.2.0.34 - 2009-02-08
19399 Tor 0.2.0.34 features several more security-related fixes. You should
19400 upgrade, especially if you run an exit relay (remote crash) or a
19401 directory authority (remote infinite loop), or you're on an older
19402 (pre-XP) or not-recently-patched Windows (remote exploit).
19404 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
19405 have many known flaws, and nobody should be using them. You should
19406 upgrade. If you're using a Linux or BSD and its packages are obsolete,
19407 stop using those packages and upgrade anyway.
19410 - Fix an infinite-loop bug on handling corrupt votes under certain
19411 circumstances. Bugfix on 0.2.0.8-alpha.
19412 - Fix a temporary DoS vulnerability that could be performed by
19413 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
19414 - Avoid a potential crash on exit nodes when processing malformed
19415 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
19416 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
19417 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
19420 - Fix compilation on systems where time_t is a 64-bit integer.
19421 Patch from Matthias Drochner.
19422 - Don't consider expiring already-closed client connections. Fixes
19423 bug 893. Bugfix on 0.0.2pre20.
19426 Changes in version 0.2.1.12-alpha - 2009-02-08
19427 Tor 0.2.1.12-alpha features several more security-related fixes. You
19428 should upgrade, especially if you run an exit relay (remote crash) or
19429 a directory authority (remote infinite loop), or you're on an older
19430 (pre-XP) or not-recently-patched Windows (remote exploit). It also
19431 includes a big pile of minor bugfixes and cleanups.
19434 - Fix an infinite-loop bug on handling corrupt votes under certain
19435 circumstances. Bugfix on 0.2.0.8-alpha.
19436 - Fix a temporary DoS vulnerability that could be performed by
19437 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
19438 - Avoid a potential crash on exit nodes when processing malformed
19439 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
19442 - Let controllers actually ask for the "clients_seen" event for
19443 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
19444 reported by Matt Edman.
19445 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
19447 - Fix a bug in address parsing that was preventing bridges or hidden
19448 service targets from being at IPv6 addresses.
19449 - Solve a bug that kept hardware crypto acceleration from getting
19450 enabled when accounting was turned on. Fixes bug 907. Bugfix on
19452 - Remove a bash-ism from configure.in to build properly on non-Linux
19453 platforms. Bugfix on 0.2.1.1-alpha.
19454 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
19455 headers. Bugfix on 0.2.0.10-alpha.
19456 - Don't consider expiring already-closed client connections. Fixes
19457 bug 893. Bugfix on 0.0.2pre20.
19458 - Fix another interesting corner-case of bug 891 spotted by rovv:
19459 Previously, if two hosts had different amounts of clock drift, and
19460 one of them created a new connection with just the wrong timing,
19461 the other might decide to deprecate the new connection erroneously.
19462 Bugfix on 0.1.1.13-alpha.
19463 - Resolve a very rare crash bug that could occur when the user forced
19464 a nameserver reconfiguration during the middle of a nameserver
19465 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
19466 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
19467 Bugfix on 0.2.1.7-alpha.
19468 - If we're using bridges and our network goes away, be more willing
19469 to forgive our bridges and try again when we get an application
19470 request. Bugfix on 0.2.0.x.
19473 - Support platforms where time_t is 64 bits long. (Congratulations,
19474 NetBSD!) Patch from Matthias Drochner.
19475 - Add a 'getinfo status/clients-seen' controller command, in case
19476 controllers want to hear clients_seen events but connect late.
19479 - Disable GCC's strict alias optimization by default, to avoid the
19480 likelihood of its introducing subtle bugs whenever our code violates
19481 the letter of C99's alias rules.
19484 Changes in version 0.2.0.33 - 2009-01-21
19485 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
19486 useful to users. It also finally fixes a bug where a relay or client
19487 that's been off for many days would take a long time to bootstrap.
19489 This update also fixes an important security-related bug reported by
19490 Ilja van Sprundel. You should upgrade. (We'll send out more details
19491 about the bug once people have had some time to upgrade.)
19494 - Fix a heap-corruption bug that may be remotely triggerable on
19495 some platforms. Reported by Ilja van Sprundel.
19498 - When a stream at an exit relay is in state "resolving" or
19499 "connecting" and it receives an "end" relay cell, the exit relay
19500 would silently ignore the end cell and not close the stream. If
19501 the client never closes the circuit, then the exit relay never
19502 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
19503 reported by "wood".
19504 - When sending CREATED cells back for a given circuit, use a 64-bit
19505 connection ID to find the right connection, rather than an addr:port
19506 combination. Now that we can have multiple OR connections between
19507 the same ORs, it is no longer possible to use addr:port to uniquely
19508 identify a connection.
19509 - Bridge relays that had DirPort set to 0 would stop fetching
19510 descriptors shortly after startup, and then briefly resume
19511 after a new bandwidth test and/or after publishing a new bridge
19512 descriptor. Bridge users that try to bootstrap from them would
19513 get a recent networkstatus but would get descriptors from up to
19514 18 hours earlier, meaning most of the descriptors were obsolete
19515 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
19516 - Prevent bridge relays from serving their 'extrainfo' document
19517 to anybody who asks, now that extrainfo docs include potentially
19518 sensitive aggregated client geoip summaries. Bugfix on
19520 - If the cached networkstatus consensus is more than five days old,
19521 discard it rather than trying to use it. In theory it could be
19522 useful because it lists alternate directory mirrors, but in practice
19523 it just means we spend many minutes trying directory mirrors that
19524 are long gone from the network. Also discard router descriptors as
19525 we load them if they are more than five days old, since the onion
19526 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
19529 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
19530 could make gcc generate non-functional binary search code. Bugfix
19532 - Build correctly on platforms without socklen_t.
19533 - Compile without warnings on solaris.
19534 - Avoid potential crash on internal error during signature collection.
19535 Fixes bug 864. Patch from rovv.
19536 - Correct handling of possible malformed authority signing key
19537 certificates with internal signature types. Fixes bug 880.
19538 Bugfix on 0.2.0.3-alpha.
19539 - Fix a hard-to-trigger resource leak when logging credential status.
19541 - When we can't initialize DNS because the network is down, do not
19542 automatically stop Tor from starting. Instead, we retry failed
19543 dns_init() every 10 minutes, and change the exit policy to reject
19544 *:* until one succeeds. Fixes bug 691.
19545 - Use 64 bits instead of 32 bits for connection identifiers used with
19546 the controller protocol, to greatly reduce risk of identifier reuse.
19547 - When we're choosing an exit node for a circuit, and we have
19548 no pending streams, choose a good general exit rather than one that
19549 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
19550 - Fix another case of assuming, when a specific exit is requested,
19551 that we know more than the user about what hosts it allows.
19552 Fixes one case of bug 752. Patch from rovv.
19553 - Clip the MaxCircuitDirtiness config option to a minimum of 10
19554 seconds. Warn the user if lower values are given in the
19555 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
19556 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
19557 user if lower values are given in the configuration. Bugfix on
19558 0.1.1.17-rc. Patch by Sebastian.
19559 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
19560 the cache because we already had a v0 descriptor with the same ID.
19561 Bugfix on 0.2.0.18-alpha.
19562 - Fix a race condition when freeing keys shared between main thread
19563 and CPU workers that could result in a memory leak. Bugfix on
19564 0.1.0.1-rc. Fixes bug 889.
19565 - Send a valid END cell back when a client tries to connect to a
19566 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
19567 840. Patch from rovv.
19568 - Check which hops rendezvous stream cells are associated with to
19569 prevent possible guess-the-streamid injection attacks from
19570 intermediate hops. Fixes another case of bug 446. Based on patch
19572 - If a broken client asks a non-exit router to connect somewhere,
19573 do not even do the DNS lookup before rejecting the connection.
19574 Fixes another case of bug 619. Patch from rovv.
19575 - When a relay gets a create cell it can't decrypt (e.g. because it's
19576 using the wrong onion key), we were dropping it and letting the
19577 client time out. Now actually answer with a destroy cell. Fixes
19578 bug 904. Bugfix on 0.0.2pre8.
19580 o Minor bugfixes (hidden services):
19581 - Do not throw away existing introduction points on SIGHUP. Bugfix on
19582 0.0.6pre1. Patch by Karsten. Fixes bug 874.
19585 - Report the case where all signatures in a detached set are rejected
19586 differently than the case where there is an error handling the
19588 - When we realize that another process has modified our cached
19589 descriptors, print out a more useful error message rather than
19590 triggering an assertion. Fixes bug 885. Patch from Karsten.
19591 - Implement the 0x20 hack to better resist DNS poisoning: set the
19592 case on outgoing DNS requests randomly, and reject responses that do
19593 not match the case correctly. This logic can be disabled with the
19594 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
19595 of servers that do not reliably preserve case in replies. See
19596 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
19598 - Check DNS replies for more matching fields to better resist DNS
19600 - Never use OpenSSL compression: it wastes RAM and CPU trying to
19601 compress cells, which are basically all encrypted, compressed, or
19605 Changes in version 0.2.1.11-alpha - 2009-01-20
19606 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
19607 week it will take a long time to bootstrap again" bug. It also fixes
19608 an important security-related bug reported by Ilja van Sprundel. You
19609 should upgrade. (We'll send out more details about the bug once people
19610 have had some time to upgrade.)
19613 - Fix a heap-corruption bug that may be remotely triggerable on
19614 some platforms. Reported by Ilja van Sprundel.
19617 - Discard router descriptors as we load them if they are more than
19618 five days old. Otherwise if Tor is off for a long time and then
19619 starts with cached descriptors, it will try to use the onion
19620 keys in those obsolete descriptors when building circuits. Bugfix
19621 on 0.2.0.x. Fixes bug 887.
19624 - Try to make sure that the version of Libevent we're running with
19625 is binary-compatible with the one we built with. May address bug
19627 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
19628 for bug 905. Bugfix on 0.2.1.7-alpha.
19629 - Add a new --enable-local-appdata configuration switch to change
19630 the default location of the datadir on win32 from APPDATA to
19631 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
19632 entirely. Patch from coderman.
19635 - Make outbound DNS packets respect the OutboundBindAddress setting.
19636 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
19637 - When our circuit fails at the first hop (e.g. we get a destroy
19638 cell back), avoid using that OR connection anymore, and also
19639 tell all the one-hop directory requests waiting for it that they
19640 should fail. Bugfix on 0.2.1.3-alpha.
19641 - In the torify(1) manpage, mention that tsocks will leak your
19645 Changes in version 0.2.1.10-alpha - 2009-01-06
19646 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
19647 would make the bridge relay not so useful if it had DirPort set to 0,
19648 and one that could let an attacker learn a little bit of information
19649 about the bridge's users), and a bug that would cause your Tor relay
19650 to ignore a circuit create request it can't decrypt (rather than reply
19651 with an error). It also fixes a wide variety of other bugs.
19654 - If the cached networkstatus consensus is more than five days old,
19655 discard it rather than trying to use it. In theory it could
19656 be useful because it lists alternate directory mirrors, but in
19657 practice it just means we spend many minutes trying directory
19658 mirrors that are long gone from the network. Helps bug 887 a bit;
19660 - Bridge relays that had DirPort set to 0 would stop fetching
19661 descriptors shortly after startup, and then briefly resume
19662 after a new bandwidth test and/or after publishing a new bridge
19663 descriptor. Bridge users that try to bootstrap from them would
19664 get a recent networkstatus but would get descriptors from up to
19665 18 hours earlier, meaning most of the descriptors were obsolete
19666 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
19667 - Prevent bridge relays from serving their 'extrainfo' document
19668 to anybody who asks, now that extrainfo docs include potentially
19669 sensitive aggregated client geoip summaries. Bugfix on
19673 - New controller event "clients_seen" to report a geoip-based summary
19674 of which countries we've seen clients from recently. Now controllers
19675 like Vidalia can show bridge operators that they're actually making
19677 - Build correctly against versions of OpenSSL 0.9.8 or later built
19678 without support for deprecated functions.
19679 - Update to the "December 19 2008" ip-to-country file.
19681 o Minor bugfixes (on 0.2.0.x):
19682 - Authorities now vote for the Stable flag for any router whose
19683 weighted MTBF is at least 5 days, regardless of the mean MTBF.
19684 - Do not remove routers as too old if we do not have any consensus
19685 document. Bugfix on 0.2.0.7-alpha.
19686 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
19687 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
19688 - When an exit relay resolves a stream address to a local IP address,
19689 do not just keep retrying that same exit relay over and
19690 over. Instead, just close the stream. Addresses bug 872. Bugfix
19691 on 0.2.0.32. Patch from rovv.
19692 - If a hidden service sends us an END cell, do not consider
19693 retrying the connection; just close it. Patch from rovv.
19694 - When we made bridge authorities stop serving bridge descriptors over
19695 unencrypted links, we also broke DirPort reachability testing for
19696 bridges. So bridges with a non-zero DirPort were printing spurious
19697 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
19698 - When a relay gets a create cell it can't decrypt (e.g. because it's
19699 using the wrong onion key), we were dropping it and letting the
19700 client time out. Now actually answer with a destroy cell. Fixes
19701 bug 904. Bugfix on 0.0.2pre8.
19702 - Squeeze 2-5% out of client performance (according to oprofile) by
19703 improving the implementation of some policy-manipulation functions.
19705 o Minor bugfixes (on 0.2.1.x):
19706 - Make get_interface_address() function work properly again; stop
19707 guessing the wrong parts of our address as our address.
19708 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
19709 send on that circuit. Otherwise we might violate the proposal-110
19710 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
19712 - When we're sending non-EXTEND cells to the first hop in a circuit,
19713 for example to use an encrypted directory connection, we don't need
19714 to use RELAY_EARLY cells: the first hop knows what kind of cell
19715 it is, and nobody else can even see the cell type. Conserving
19716 RELAY_EARLY cells makes it easier to cannibalize circuits like
19718 - Stop logging nameserver addresses in reverse order.
19719 - If we are retrying a directory download slowly over and over, do
19720 not automatically give up after the 254th failure. Bugfix on
19722 - Resume reporting accurate "stream end" reasons to the local control
19723 port. They were lost in the changes for Proposal 148. Bugfix on
19726 o Deprecated and removed features:
19727 - The old "tor --version --version" command, which would print out
19728 the subversion "Id" of most of the source files, is now removed. It
19729 turned out to be less useful than we'd expected, and harder to
19732 o Code simplifications and refactoring:
19733 - Change our header file guard macros to be less likely to conflict
19734 with system headers. Adam Langley noticed that we were conflicting
19735 with log.h on Android.
19736 - Tool-assisted documentation cleanup. Nearly every function or
19737 static variable in Tor should have its own documentation now.
19740 Changes in version 0.2.1.9-alpha - 2008-12-25
19741 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
19743 o New directory authorities:
19744 - gabelmoo (the authority run by Karsten Loesing) now has a new
19748 - Never use a connection with a mismatched address to extend a
19749 circuit, unless that connection is canonical. A canonical
19750 connection is one whose address is authenticated by the router's
19751 identity key, either in a NETINFO cell or in a router descriptor.
19752 - Avoid a possible memory corruption bug when receiving hidden service
19753 descriptors. Bugfix on 0.2.1.6-alpha.
19756 - Fix a logic error that would automatically reject all but the first
19757 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
19758 part of bug 813/868. Bug spotted by coderman.
19759 - When a stream at an exit relay is in state "resolving" or
19760 "connecting" and it receives an "end" relay cell, the exit relay
19761 would silently ignore the end cell and not close the stream. If
19762 the client never closes the circuit, then the exit relay never
19763 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
19764 reported by "wood".
19765 - When we can't initialize DNS because the network is down, do not
19766 automatically stop Tor from starting. Instead, retry failed
19767 dns_init() every 10 minutes, and change the exit policy to reject
19768 *:* until one succeeds. Fixes bug 691.
19771 - Give a better error message when an overzealous init script says
19772 "sudo -u username tor --user username". Makes Bug 882 easier for
19774 - When a directory authority gives us a new guess for our IP address,
19775 log which authority we used. Hopefully this will help us debug
19776 the recent complaints about bad IP address guesses.
19777 - Detect svn revision properly when we're using git-svn.
19778 - Try not to open more than one descriptor-downloading connection
19779 to an authority at once. This should reduce load on directory
19780 authorities. Fixes bug 366.
19781 - Add cross-certification to newly generated certificates, so that
19782 a signing key is enough information to look up a certificate.
19783 Partial implementation of proposal 157.
19784 - Start serving certificates by <identity digest, signing key digest>
19785 pairs. Partial implementation of proposal 157.
19786 - Clients now never report any stream end reason except 'MISC'.
19787 Implements proposal 148.
19788 - On platforms with a maximum syslog string length, truncate syslog
19789 messages to that length ourselves, rather than relying on the
19790 system to do it for us.
19791 - Optimize out calls to time(NULL) that occur for every IO operation,
19792 or for every cell. On systems where time() is a slow syscall,
19793 this fix will be slightly helpful.
19794 - Exit servers can now answer resolve requests for ip6.arpa addresses.
19795 - When we download a descriptor that we then immediately (as
19796 a directory authority) reject, do not retry downloading it right
19797 away. Should save some bandwidth on authorities. Fix for bug
19798 888. Patch by Sebastian Hahn.
19799 - When a download gets us zero good descriptors, do not notify
19800 Tor that new directory information has arrived.
19801 - Avoid some nasty corner cases in the logic for marking connections
19802 as too old or obsolete or noncanonical for circuits. Partial
19805 o Minor features (controller):
19806 - New CONSENSUS_ARRIVED event to note when a new consensus has
19807 been fetched and validated.
19808 - When we realize that another process has modified our cached
19809 descriptors file, print out a more useful error message rather
19810 than triggering an assertion. Fixes bug 885. Patch from Karsten.
19811 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
19812 controllers to prevent SIGHUP from reloading the
19813 configuration. Fixes bug 856.
19816 - Resume using the correct "REASON=" stream when telling the
19817 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
19818 - When a canonical connection appears later in our internal list
19819 than a noncanonical one for a given OR ID, always use the
19820 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
19822 - Clip the MaxCircuitDirtiness config option to a minimum of 10
19823 seconds. Warn the user if lower values are given in the
19824 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
19825 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
19826 user if lower values are given in the configuration. Bugfix on
19827 0.1.1.17-rc. Patch by Sebastian.
19828 - Fix a race condition when freeing keys shared between main thread
19829 and CPU workers that could result in a memory leak. Bugfix on
19830 0.1.0.1-rc. Fixes bug 889.
19832 o Minor bugfixes (hidden services):
19833 - Do not throw away existing introduction points on SIGHUP (bugfix on
19834 0.0.6pre1); also, do not stall hidden services because we're
19835 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
19836 by John Brooks. Patch by Karsten. Fixes bug 874.
19837 - Fix a memory leak when we decline to add a v2 rendezvous
19838 descriptor to the cache because we already had a v0 descriptor
19839 with the same ID. Bugfix on 0.2.0.18-alpha.
19841 o Deprecated and removed features:
19842 - RedirectExits has been removed. It was deprecated since
19844 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
19845 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
19846 - Cell pools are now always enabled; --disable-cell-pools is ignored.
19848 o Code simplifications and refactoring:
19849 - Rename the confusing or_is_obsolete field to the more appropriate
19850 is_bad_for_new_circs, and move it to or_connection_t where it
19852 - Move edge-only flags from connection_t to edge_connection_t: not
19853 only is this better coding, but on machines of plausible alignment,
19854 it should save 4-8 bytes per connection_t. "Every little bit helps."
19855 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
19856 for consistency; keep old option working for backward compatibility.
19857 - Simplify the code for finding connections to use for a circuit.
19860 Changes in version 0.2.1.8-alpha - 2008-12-08
19861 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
19862 builds better on unusual platforms like Solaris and old OS X, and
19863 fixes a variety of other issues.
19866 - New DirPortFrontPage option that takes an html file and publishes
19867 it as "/" on the DirPort. Now relay operators can provide a
19868 disclaimer without needing to set up a separate webserver. There's
19869 a sample disclaimer in contrib/tor-exit-notice.html.
19872 - When the client is choosing entry guards, now it selects at most
19873 one guard from a given relay family. Otherwise we could end up with
19874 all of our entry points into the network run by the same operator.
19875 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
19878 - Fix a DOS opportunity during the voting signature collection process
19879 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19880 - Fix a possible segfault when establishing an exit connection. Bugfix
19884 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
19886 - Made Tor a little less aggressive about deleting expired
19887 certificates. Partial fix for bug 854.
19888 - Stop doing unaligned memory access that generated bus errors on
19889 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
19890 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
19891 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
19892 - Make USR2 log-level switch take effect immediately. Bugfix on
19894 - If one win32 nameserver fails to get added, continue adding the
19895 rest, and don't automatically fail.
19896 - Use fcntl() for locking when flock() is not available. Should fix
19897 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
19898 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
19899 could make gcc generate non-functional binary search code. Bugfix
19901 - Build correctly on platforms without socklen_t.
19902 - Avoid potential crash on internal error during signature collection.
19903 Fixes bug 864. Patch from rovv.
19904 - Do not use C's stdio library for writing to log files. This will
19905 improve logging performance by a minute amount, and will stop
19906 leaking fds when our disk is full. Fixes bug 861.
19907 - Stop erroneous use of O_APPEND in cases where we did not in fact
19908 want to re-seek to the end of a file before every last write().
19909 - Correct handling of possible malformed authority signing key
19910 certificates with internal signature types. Fixes bug 880. Bugfix
19912 - Fix a hard-to-trigger resource leak when logging credential status.
19916 - Directory mirrors no longer fetch the v1 directory or
19917 running-routers files. They are obsolete, and nobody asks for them
19918 anymore. This is the first step to making v1 authorities obsolete.
19920 o Minor features (controller):
19921 - Return circuit purposes in response to GETINFO circuit-status. Fixes
19925 Changes in version 0.2.0.32 - 2008-11-20
19926 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
19927 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19928 a smaller security flaw that might allow an attacker to access local
19929 services, further improves hidden service performance, and fixes a
19930 variety of other issues.
19933 - The "User" and "Group" config options did not clear the
19934 supplementary group entries for the Tor process. The "User" option
19935 is now more robust, and we now set the groups to the specified
19936 user's primary group. The "Group" option is now ignored. For more
19937 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
19938 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
19939 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
19940 - The "ClientDNSRejectInternalAddresses" config option wasn't being
19941 consistently obeyed: if an exit relay refuses a stream because its
19942 exit policy doesn't allow it, we would remember what IP address
19943 the relay said the destination address resolves to, even if it's
19944 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
19947 - Fix a DOS opportunity during the voting signature collection process
19948 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
19950 o Major bugfixes (hidden services):
19951 - When fetching v0 and v2 rendezvous service descriptors in parallel,
19952 we were failing the whole hidden service request when the v0
19953 descriptor fetch fails, even if the v2 fetch is still pending and
19954 might succeed. Similarly, if the last v2 fetch fails, we were
19955 failing the whole hidden service request even if a v0 fetch is
19956 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
19957 - When extending a circuit to a hidden service directory to upload a
19958 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
19959 requests failed, because the router descriptor has not been
19960 downloaded yet. In these cases, do not attempt to upload the
19961 rendezvous descriptor, but wait until the router descriptor is
19962 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
19963 descriptor from a hidden service directory for which the router
19964 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
19968 - Fix several infrequent memory leaks spotted by Coverity.
19969 - When testing for libevent functions, set the LDFLAGS variable
19970 correctly. Found by Riastradh.
19971 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
19972 bootstrapping with tunneled directory connections. Bugfix on
19973 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
19974 - When asked to connect to A.B.exit:80, if we don't know the IP for A
19975 and we know that server B rejects most-but-not all connections to
19976 port 80, we would previously reject the connection. Now, we assume
19977 the user knows what they were asking for. Fixes bug 752. Bugfix
19978 on 0.0.9rc5. Diagnosed by BarkerJr.
19979 - If we overrun our per-second write limits a little, count this as
19980 having used up our write allocation for the second, and choke
19981 outgoing directory writes. Previously, we had only counted this when
19982 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
19983 Bugfix on 0.2.0.x (??).
19984 - Remove the old v2 directory authority 'lefkada' from the default
19985 list. It has been gone for many months.
19986 - Stop doing unaligned memory access that generated bus errors on
19987 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
19988 - Make USR2 log-level switch take effect immediately. Bugfix on
19991 o Minor bugfixes (controller):
19992 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
19993 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
19996 Changes in version 0.2.1.7-alpha - 2008-11-08
19997 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
19998 packages (and maybe other packages) noticed by Theo de Raadt, fixes
19999 a smaller security flaw that might allow an attacker to access local
20000 services, adds better defense against DNS poisoning attacks on exit
20001 relays, further improves hidden service performance, and fixes a
20002 variety of other issues.
20005 - The "ClientDNSRejectInternalAddresses" config option wasn't being
20006 consistently obeyed: if an exit relay refuses a stream because its
20007 exit policy doesn't allow it, we would remember what IP address
20008 the relay said the destination address resolves to, even if it's
20009 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
20010 - The "User" and "Group" config options did not clear the
20011 supplementary group entries for the Tor process. The "User" option
20012 is now more robust, and we now set the groups to the specified
20013 user's primary group. The "Group" option is now ignored. For more
20014 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
20015 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
20016 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
20017 - Do not use or believe expired v3 authority certificates. Patch
20018 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
20021 - Now NodeFamily and MyFamily config options allow spaces in
20022 identity fingerprints, so it's easier to paste them in.
20023 Suggested by Lucky Green.
20024 - Implement the 0x20 hack to better resist DNS poisoning: set the
20025 case on outgoing DNS requests randomly, and reject responses that do
20026 not match the case correctly. This logic can be disabled with the
20027 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
20028 of servers that do not reliably preserve case in replies. See
20029 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
20031 - Preserve case in replies to DNSPort requests in order to support
20032 the 0x20 hack for resisting DNS poisoning attacks.
20034 o Hidden service performance improvements:
20035 - When the client launches an introduction circuit, retry with a
20036 new circuit after 30 seconds rather than 60 seconds.
20037 - Launch a second client-side introduction circuit in parallel
20038 after a delay of 15 seconds (based on work by Christian Wilms).
20039 - Hidden services start out building five intro circuits rather
20040 than three, and when the first three finish they publish a service
20041 descriptor using those. Now we publish our service descriptor much
20042 faster after restart.
20045 - Minor fix in the warning messages when you're having problems
20046 bootstrapping; also, be more forgiving of bootstrap problems when
20047 we're still making incremental progress on a given bootstrap phase.
20048 - When we're choosing an exit node for a circuit, and we have
20049 no pending streams, choose a good general exit rather than one that
20050 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
20051 - Send a valid END cell back when a client tries to connect to a
20052 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
20053 840. Patch from rovv.
20054 - If a broken client asks a non-exit router to connect somewhere,
20055 do not even do the DNS lookup before rejecting the connection.
20056 Fixes another case of bug 619. Patch from rovv.
20057 - Fix another case of assuming, when a specific exit is requested,
20058 that we know more than the user about what hosts it allows.
20059 Fixes another case of bug 752. Patch from rovv.
20060 - Check which hops rendezvous stream cells are associated with to
20061 prevent possible guess-the-streamid injection attacks from
20062 intermediate hops. Fixes another case of bug 446. Based on patch
20064 - Avoid using a negative right-shift when comparing 32-bit
20065 addresses. Possible fix for bug 845 and bug 811.
20066 - Make the assert_circuit_ok() function work correctly on circuits that
20067 have already been marked for close.
20068 - Fix read-off-the-end-of-string error in unit tests when decoding
20069 introduction points.
20070 - Fix uninitialized size field for memory area allocation: may improve
20071 memory performance during directory parsing.
20072 - Treat duplicate certificate fetches as failures, so that we do
20073 not try to re-fetch an expired certificate over and over and over.
20074 - Do not say we're fetching a certificate when we'll in fact skip it
20075 because of a pending download.
20078 Changes in version 0.2.1.6-alpha - 2008-09-30
20079 Tor 0.2.1.6-alpha further improves performance and robustness of
20080 hidden services, starts work on supporting per-country relay selection,
20081 and fixes a variety of smaller issues.
20084 - Implement proposal 121: make it possible to build hidden services
20085 that only certain clients are allowed to connect to. This is
20086 enforced at several points, so that unauthorized clients are unable
20087 to send INTRODUCE cells to the service, or even (depending on the
20088 type of authentication) to learn introduction points. This feature
20089 raises the bar for certain kinds of active attacks against hidden
20090 services. Code by Karsten Loesing.
20091 - Relays now store and serve v2 hidden service descriptors by default,
20092 i.e., the new default value for HidServDirectoryV2 is 1. This is
20093 the last step in proposal 114, which aims to make hidden service
20094 lookups more reliable.
20095 - Start work to allow node restrictions to include country codes. The
20096 syntax to exclude nodes in a country with country code XX is
20097 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
20098 refinement to decide what config options should take priority if
20099 you ask to both use a particular node and exclude it.
20100 - Allow ExitNodes list to include IP ranges and country codes, just
20101 like the Exclude*Nodes lists. Patch from Robert Hogan.
20104 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
20105 Tor to fail to start if you had it configured to use a bridge
20106 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
20107 - When extending a circuit to a hidden service directory to upload a
20108 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
20109 requests failed, because the router descriptor had not been
20110 downloaded yet. In these cases, we now wait until the router
20111 descriptor is downloaded, and then retry. Likewise, clients
20112 now skip over a hidden service directory if they don't yet have
20113 its router descriptor, rather than futilely requesting it and
20114 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
20116 - When fetching v0 and v2 rendezvous service descriptors in parallel,
20117 we were failing the whole hidden service request when the v0
20118 descriptor fetch fails, even if the v2 fetch is still pending and
20119 might succeed. Similarly, if the last v2 fetch fails, we were
20120 failing the whole hidden service request even if a v0 fetch is
20121 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
20122 - DNS replies need to have names matching their requests, but
20123 these names should be in the questions section, not necessarily
20124 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
20127 - Update to the "September 1 2008" ip-to-country file.
20128 - Allow ports 465 and 587 in the default exit policy again. We had
20129 rejected them in 0.1.0.15, because back in 2005 they were commonly
20130 misconfigured and ended up as spam targets. We hear they are better
20131 locked down these days.
20132 - Use a lockfile to make sure that two Tor processes are not
20133 simultaneously running with the same datadir.
20134 - Serve the latest v3 networkstatus consensus via the control
20135 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
20136 - Better logging about stability/reliability calculations on directory
20138 - Drop the requirement to have an open dir port for storing and
20139 serving v2 hidden service descriptors.
20140 - Directory authorities now serve a /tor/dbg-stability.txt URL to
20141 help debug WFU and MTBF calculations.
20142 - Implement most of Proposal 152: allow specialized servers to permit
20143 single-hop circuits, and clients to use those servers to build
20144 single-hop circuits when using a specialized controller. Patch
20145 from Josh Albrecht. Resolves feature request 768.
20146 - Add a -p option to tor-resolve for specifying the SOCKS port: some
20147 people find host:port too confusing.
20148 - Make TrackHostExit mappings expire a while after their last use, not
20149 after their creation. Patch from Robert Hogan.
20150 - Provide circuit purposes along with circuit events to the controller.
20153 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
20155 - Fixed some memory leaks -- some quite frequent, some almost
20156 impossible to trigger -- based on results from Coverity.
20157 - When testing for libevent functions, set the LDFLAGS variable
20158 correctly. Found by Riastradh.
20159 - Fix an assertion bug in parsing policy-related options; possible fix
20161 - Catch and report a few more bootstrapping failure cases when Tor
20162 fails to establish a TCP connection. Cleanup on 0.2.1.x.
20163 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
20164 bootstrapping with tunneled directory connections. Bugfix on
20165 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
20166 - When asked to connect to A.B.exit:80, if we don't know the IP for A
20167 and we know that server B rejects most-but-not all connections to
20168 port 80, we would previously reject the connection. Now, we assume
20169 the user knows what they were asking for. Fixes bug 752. Bugfix
20170 on 0.0.9rc5. Diagnosed by BarkerJr.
20171 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
20172 service directories if they have no advertised dir port. Bugfix
20174 - If we overrun our per-second write limits a little, count this as
20175 having used up our write allocation for the second, and choke
20176 outgoing directory writes. Previously, we had only counted this when
20177 we had met our limits precisely. Fixes bug 824. Patch by rovv.
20178 Bugfix on 0.2.0.x (??).
20179 - Avoid a "0 divided by 0" calculation when calculating router uptime
20180 at directory authorities. Bugfix on 0.2.0.8-alpha.
20181 - Make DNS resolved controller events into "CLOSED", not
20182 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
20184 - Fix a bug where an unreachable relay would establish enough
20185 reachability testing circuits to do a bandwidth test -- if
20186 we already have a connection to the middle hop of the testing
20187 circuit, then it could establish the last hop by using the existing
20188 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
20189 circuits no longer use entry guards in 0.2.1.3-alpha.
20190 - If we have correct permissions on $datadir, we complain to stdout
20191 and fail to start. But dangerous permissions on
20192 $datadir/cached-status/ would cause us to open a log and complain
20193 there. Now complain to stdout and fail to start in both cases. Fixes
20194 bug 820, reported by seeess.
20195 - Remove the old v2 directory authority 'lefkada' from the default
20196 list. It has been gone for many months.
20198 o Code simplifications and refactoring:
20199 - Revise the connection_new functions so that a more typesafe variant
20200 exists. This will work better with Coverity, and let us find any
20201 actual mistakes we're making here.
20202 - Refactor unit testing logic so that dmalloc can be used sensibly
20203 with unit tests to check for memory leaks.
20204 - Move all hidden-service related fields from connection and circuit
20205 structure to substructures: this way they won't eat so much memory.
20208 Changes in version 0.2.0.31 - 2008-09-03
20209 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
20210 a big bug we're seeing where in rare cases traffic from one Tor stream
20211 gets mixed into another stream, and fixes a variety of smaller issues.
20214 - Make sure that two circuits can never exist on the same connection
20215 with the same circuit ID, even if one is marked for close. This
20216 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
20217 - Relays now reject risky extend cells: if the extend cell includes
20218 a digest of all zeroes, or asks to extend back to the relay that
20219 sent the extend cell, tear down the circuit. Ideas suggested
20221 - If not enough of our entry guards are available so we add a new
20222 one, we might use the new one even if it overlapped with the
20223 current circuit's exit relay (or its family). Anonymity bugfix
20224 pointed out by rovv.
20227 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
20228 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
20229 - Correctly detect the presence of the linux/netfilter_ipv4.h header
20230 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
20231 - Pick size of default geoip filename string correctly on windows.
20232 Fixes bug 806. Bugfix on 0.2.0.30.
20233 - Make the autoconf script accept the obsolete --with-ssl-dir
20234 option as an alias for the actually-working --with-openssl-dir
20235 option. Fix the help documentation to recommend --with-openssl-dir.
20236 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
20237 - When using the TransPort option on OpenBSD, and using the User
20238 option to change UID and drop privileges, make sure to open
20239 /dev/pf before dropping privileges. Fixes bug 782. Patch from
20240 Christopher Davis. Bugfix on 0.1.2.1-alpha.
20241 - Try to attach connections immediately upon receiving a RENDEZVOUS2
20242 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
20243 on the client side when connecting to a hidden service. Bugfix
20244 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
20245 - When closing an application-side connection because its circuit is
20246 getting torn down, generate the stream event correctly. Bugfix on
20247 0.1.2.x. Anonymous patch.
20250 Changes in version 0.2.1.5-alpha - 2008-08-31
20251 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
20252 in a lot of the infrastructure for adding authorization to hidden
20253 services, lays the groundwork for having clients read their load
20254 balancing information out of the networkstatus consensus rather than
20255 the individual router descriptors, addresses two potential anonymity
20256 issues, and fixes a variety of smaller issues.
20259 - Convert many internal address representations to optionally hold
20261 - Generate and accept IPv6 addresses in many protocol elements.
20262 - Make resolver code handle nameservers located at ipv6 addresses.
20263 - Begin implementation of proposal 121 ("Client authorization for
20264 hidden services"): configure hidden services with client
20265 authorization, publish descriptors for them, and configure
20266 authorization data for hidden services at clients. The next
20267 step is to actually access hidden services that perform client
20269 - More progress toward proposal 141: Network status consensus
20270 documents and votes now contain bandwidth information for each
20271 router and a summary of that router's exit policy. Eventually this
20272 will be used by clients so that they do not have to download every
20273 known descriptor before building circuits.
20275 o Major bugfixes (on 0.2.0.x and before):
20276 - When sending CREATED cells back for a given circuit, use a 64-bit
20277 connection ID to find the right connection, rather than an addr:port
20278 combination. Now that we can have multiple OR connections between
20279 the same ORs, it is no longer possible to use addr:port to uniquely
20280 identify a connection.
20281 - Relays now reject risky extend cells: if the extend cell includes
20282 a digest of all zeroes, or asks to extend back to the relay that
20283 sent the extend cell, tear down the circuit. Ideas suggested
20285 - If not enough of our entry guards are available so we add a new
20286 one, we might use the new one even if it overlapped with the
20287 current circuit's exit relay (or its family). Anonymity bugfix
20288 pointed out by rovv.
20291 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
20292 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
20293 - When using the TransPort option on OpenBSD, and using the User
20294 option to change UID and drop privileges, make sure to open /dev/pf
20295 before dropping privileges. Fixes bug 782. Patch from Christopher
20296 Davis. Bugfix on 0.1.2.1-alpha.
20297 - Correctly detect the presence of the linux/netfilter_ipv4.h header
20298 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
20299 - Add a missing safe_str() call for a debug log message.
20300 - Use 64 bits instead of 32 bits for connection identifiers used with
20301 the controller protocol, to greatly reduce risk of identifier reuse.
20302 - Make the autoconf script accept the obsolete --with-ssl-dir
20303 option as an alias for the actually-working --with-openssl-dir
20304 option. Fix the help documentation to recommend --with-openssl-dir.
20305 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
20308 - Rate-limit too-many-sockets messages: when they happen, they happen
20309 a lot. Resolves bug 748.
20310 - Resist DNS poisoning a little better by making sure that names in
20311 answer sections match.
20312 - Print the SOCKS5 error message string as well as the error code
20313 when a tor-resolve request fails. Patch from Jacob.
20316 Changes in version 0.2.1.4-alpha - 2008-08-04
20317 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
20320 - The address part of exit policies was not correctly written
20321 to router descriptors. This generated router descriptors that failed
20322 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
20324 - Tor triggered a false assert when extending a circuit to a relay
20325 but we already have a connection open to that relay. Noticed by
20326 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
20329 - Fix a hidden service logging bug: in some edge cases, the router
20330 descriptor of a previously picked introduction point becomes
20331 obsolete and we need to give up on it rather than continually
20332 complaining that it has become obsolete. Observed by xiando. Bugfix
20335 o Removed features:
20336 - Take out the TestVia config option, since it was a workaround for
20337 a bug that was fixed in Tor 0.1.1.21.
20340 Changes in version 0.2.1.3-alpha - 2008-08-03
20341 Tor 0.2.1.3-alpha implements most of the pieces to prevent
20342 infinite-length circuit attacks (see proposal 110); fixes a bug that
20343 might cause exit relays to corrupt streams they send back; allows
20344 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
20345 ExcludeExitNodes config options; and fixes a big pile of bugs.
20347 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
20348 - Send a bootstrap problem "warn" event on the first problem if the
20349 reason is NO_ROUTE (that is, our network is down).
20352 - Implement most of proposal 110: The first K cells to be sent
20353 along a circuit are marked as special "early" cells; only K "early"
20354 cells will be allowed. Once this code is universal, we can block
20355 certain kinds of DOS attack by requiring that EXTEND commands must
20356 be sent using an "early" cell.
20359 - Try to attach connections immediately upon receiving a RENDEZVOUS2
20360 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
20361 on the client side when connecting to a hidden service. Bugfix
20362 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
20363 - Ensure that two circuits can never exist on the same connection
20364 with the same circuit ID, even if one is marked for close. This
20365 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
20368 - When relays do their initial bandwidth measurement, don't limit
20369 to just our entry guards for the test circuits. Otherwise we tend
20370 to have multiple test circuits going through a single entry guard,
20371 which makes our bandwidth test less accurate. Fixes part of bug 654;
20372 patch contributed by Josh Albrecht.
20373 - Add an ExcludeExitNodes option so users can list a set of nodes
20374 that should be be excluded from the exit node position, but
20375 allowed elsewhere. Implements proposal 151.
20376 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
20377 ExcludeNodes and ExcludeExitNodes lists.
20378 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
20379 be more efficient. Formerly it was quadratic in the number of
20380 servers; now it should be linear. Fixes bug 509.
20381 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
20382 and n_conn_id_digest fields into a separate structure that's
20383 only needed when the circuit has not yet attached to an n_conn.
20386 - Change the contrib/tor.logrotate script so it makes the new
20387 logs as "_tor:_tor" rather than the default, which is generally
20388 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
20389 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
20390 warnings (occasionally), but it can also cause the compiler to
20391 eliminate error-checking code. Suggested by Peter Gutmann.
20392 - When a hidden service is giving up on an introduction point candidate
20393 that was not included in the last published rendezvous descriptor,
20394 don't reschedule publication of the next descriptor. Fixes bug 763.
20396 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
20397 HiddenServiceExcludeNodes as obsolete: they never worked properly,
20398 and nobody claims to be using them. Fixes bug 754. Bugfix on
20399 0.1.0.1-rc. Patch from Christian Wilms.
20400 - Fix a small alignment and memory-wasting bug on buffer chunks.
20403 o Minor bugfixes (controller):
20404 - When closing an application-side connection because its circuit
20405 is getting torn down, generate the stream event correctly.
20406 Bugfix on 0.1.2.x. Anonymous patch.
20408 o Removed features:
20409 - Remove all backward-compatibility code to support relays running
20410 versions of Tor so old that they no longer work at all on the
20414 Changes in version 0.2.0.30 - 2008-07-15
20416 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
20417 warnings (occasionally), but it can also cause the compiler to
20418 eliminate error-checking code. Suggested by Peter Gutmann.
20421 Changes in version 0.2.0.29-rc - 2008-07-08
20422 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
20423 hidden-service performance bugs, and fixes a bunch of smaller bugs.
20426 - If you have more than one bridge but don't know their keys,
20427 you would only launch a request for the descriptor of the first one
20428 on your list. (Tor considered launching requests for the others, but
20429 found that it already had a connection on the way for $0000...0000
20430 so it didn't open another.) Bugfix on 0.2.0.x.
20431 - If you have more than one bridge but don't know their keys, and the
20432 connection to one of the bridges failed, you would cancel all
20433 pending bridge connections. (After all, they all have the same
20434 digest.) Bugfix on 0.2.0.x.
20435 - When a hidden service was trying to establish an introduction point,
20436 and Tor had built circuits preemptively for such purposes, we
20437 were ignoring all the preemptive circuits and launching a new one
20438 instead. Bugfix on 0.2.0.14-alpha.
20439 - When a hidden service was trying to establish an introduction point,
20440 and Tor *did* manage to reuse one of the preemptively built
20441 circuits, it didn't correctly remember which one it used,
20442 so it asked for another one soon after, until there were no
20443 more preemptive circuits, at which point it launched one from
20444 scratch. Bugfix on 0.0.9.x.
20445 - Make directory servers include the X-Your-Address-Is: http header in
20446 their responses even for begin_dir conns. Now clients who only
20447 ever use begin_dir connections still have a way to learn their IP
20448 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
20451 - Fix a macro/CPP interaction that was confusing some compilers:
20452 some GCCs don't like #if/#endif pairs inside macro arguments.
20454 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
20455 Fixes bug 704; fix from Steven Murdoch.
20456 - When opening /dev/null in finish_daemonize(), do not pass the
20457 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
20458 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
20459 - Correctly detect transparent proxy support on Linux hosts that
20460 require in.h to be included before netfilter_ipv4.h. Patch
20462 - Disallow session resumption attempts during the renegotiation
20463 stage of the v2 handshake protocol. Clients should never be trying
20464 session resumption at this point, but apparently some did, in
20465 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
20466 found by Geoff Goodell.
20469 Changes in version 0.2.1.2-alpha - 2008-06-20
20470 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
20471 make it easier to set up your own private Tor network; fixes several
20472 big bugs with using more than one bridge relay; fixes a big bug with
20473 offering hidden services quickly after Tor starts; and uses a better
20474 API for reporting potential bootstrapping problems to the controller.
20477 - New TestingTorNetwork config option to allow adjustment of
20478 previously constant values that, while reasonable, could slow
20479 bootstrapping. Implements proposal 135. Patch from Karsten.
20482 - If you have more than one bridge but don't know their digests,
20483 you would only learn a request for the descriptor of the first one
20484 on your list. (Tor considered launching requests for the others, but
20485 found that it already had a connection on the way for $0000...0000
20486 so it didn't open another.) Bugfix on 0.2.0.x.
20487 - If you have more than one bridge but don't know their digests,
20488 and the connection to one of the bridges failed, you would cancel
20489 all pending bridge connections. (After all, they all have the
20490 same digest.) Bugfix on 0.2.0.x.
20491 - When establishing a hidden service, introduction points that
20492 originate from cannibalized circuits are completely ignored and not
20493 included in rendezvous service descriptors. This might be another
20494 reason for delay in making a hidden service available. Bugfix
20495 from long ago (0.0.9.x?)
20498 - Allow OpenSSL to use dynamic locks if it wants.
20499 - When building a consensus, do not include routers that are down.
20500 This will cut down 30% to 40% on consensus size. Implements
20502 - In directory authorities' approved-routers files, allow
20503 fingerprints with or without space.
20504 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
20505 controller can query our current bootstrap state in case it attaches
20506 partway through and wants to catch up.
20507 - Send an initial "Starting" bootstrap status event, so we have a
20508 state to start out in.
20511 - Asking for a conditional consensus at .../consensus/<fingerprints>
20512 would crash a dirserver if it did not already have a
20513 consensus. Bugfix on 0.2.1.1-alpha.
20514 - Clean up some macro/CPP interactions: some GCC versions don't like
20515 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
20518 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
20519 - Directory authorities shouldn't complain about bootstrapping
20520 problems just because they do a lot of reachability testing and
20521 some of the connection attempts fail.
20522 - Start sending "count" and "recommendation" key/value pairs in
20523 bootstrap problem status events, so the controller can hear about
20524 problems even before Tor decides they're worth reporting for sure.
20525 - If you're using bridges, generate "bootstrap problem" warnings
20526 as soon as you run out of working bridges, rather than waiting
20527 for ten failures -- which will never happen if you have less than
20529 - If we close our OR connection because there's been a circuit
20530 pending on it for too long, we were telling our bootstrap status
20531 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
20534 Changes in version 0.2.1.1-alpha - 2008-06-13
20535 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
20536 were making the Tor process bloat especially on Linux; makes our TLS
20537 handshake blend in better; sends "bootstrap phase" status events to
20538 the controller, so it can keep the user informed of progress (and
20539 problems) fetching directory information and establishing circuits;
20540 and adds a variety of smaller features.
20543 - More work on making our TLS handshake blend in: modify the list
20544 of ciphers advertised by OpenSSL in client mode to even more
20545 closely resemble a common web browser. We cheat a little so that
20546 we can advertise ciphers that the locally installed OpenSSL doesn't
20548 - Start sending "bootstrap phase" status events to the controller,
20549 so it can keep the user informed of progress fetching directory
20550 information and establishing circuits. Also inform the controller
20551 if we think we're stuck at a particular bootstrap phase. Implements
20553 - Resume using OpenSSL's RAND_poll() for better (and more portable)
20554 cross-platform entropy collection again. We used to use it, then
20555 stopped using it because of a bug that could crash systems that
20556 called RAND_poll when they had a lot of fds open. It looks like the
20557 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
20558 at startup, and to call RAND_poll() when we reseed later only if
20559 we have a non-buggy OpenSSL version.
20562 - When we choose to abandon a new entry guard because we think our
20563 older ones might be better, close any circuits pending on that
20564 new entry guard connection. This fix should make us recover much
20565 faster when our network is down and then comes back. Bugfix on
20566 0.1.2.8-beta; found by lodger.
20568 o Memory fixes and improvements:
20569 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
20570 to avoid unused RAM in buffer chunks and memory pools.
20571 - Speed up parsing and cut down on memory fragmentation by using
20572 stack-style allocations for parsing directory objects. Previously,
20573 this accounted for over 40% of allocations from within Tor's code
20574 on a typical directory cache.
20575 - Use a Bloom filter rather than a digest-based set to track which
20576 descriptors we need to keep around when we're cleaning out old
20577 router descriptors. This speeds up the computation significantly,
20578 and may reduce fragmentation.
20579 - Reduce the default smartlist size from 32 to 16; it turns out that
20580 most smartlists hold around 8-12 elements tops.
20581 - Make dumpstats() log the fullness and size of openssl-internal
20583 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
20584 patch to their OpenSSL, turn it on to save memory on servers. This
20585 patch will (with any luck) get included in a mainline distribution
20587 - Never use OpenSSL compression: it wastes RAM and CPU trying to
20588 compress cells, which are basically all encrypted, compressed,
20592 - Stop reloading the router list from disk for no reason when we
20593 run out of reachable directory mirrors. Once upon a time reloading
20594 it would set the 'is_running' flag back to 1 for them. It hasn't
20595 done that for a long time.
20596 - In very rare situations new hidden service descriptors were
20597 published earlier than 30 seconds after the last change to the
20598 service. (We currently think that a hidden service descriptor
20599 that's been stable for 30 seconds is worth publishing.)
20602 - Allow separate log levels to be configured for different logging
20603 domains. For example, this allows one to log all notices, warnings,
20604 or errors, plus all memory management messages of level debug or
20605 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
20606 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
20607 and stop using a warning that had become unfixably verbose under
20609 - New --hush command-line option similar to --quiet. While --quiet
20610 disables all logging to the console on startup, --hush limits the
20611 output to messages of warning and error severity.
20612 - Servers support a new URL scheme for consensus downloads that
20613 allows the client to specify which authorities are trusted.
20614 The server then only sends the consensus if the client will trust
20615 it. Otherwise a 404 error is sent back. Clients use this
20616 new scheme when the server supports it (meaning it's running
20617 0.2.1.1-alpha or later). Implements proposal 134.
20618 - New configure/torrc options (--enable-geoip-stats,
20619 DirRecordUsageByCountry) to record how many IPs we've served
20620 directory info to in each country code, how many status documents
20621 total we've sent to each country code, and what share of the total
20622 directory requests we should expect to see.
20623 - Use the TLS1 hostname extension to more closely resemble browser
20625 - Lots of new unit tests.
20626 - Add a macro to implement the common pattern of iterating through
20627 two parallel lists in lockstep.
20630 Changes in version 0.2.0.28-rc - 2008-06-13
20631 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
20632 performance bug, and fixes a bunch of smaller bugs.
20635 - Fix a bug where, when we were choosing the 'end stream reason' to
20636 put in our relay end cell that we send to the exit relay, Tor
20637 clients on Windows were sometimes sending the wrong 'reason'. The
20638 anonymity problem is that exit relays may be able to guess whether
20639 the client is running Windows, thus helping partition the anonymity
20640 set. Down the road we should stop sending reasons to exit relays,
20641 or otherwise prevent future versions of this bug.
20644 - While setting up a hidden service, some valid introduction circuits
20645 were overlooked and abandoned. This might be the reason for
20646 the long delay in making a hidden service available. Bugfix on
20650 - Update to the "June 9 2008" ip-to-country file.
20651 - Run 'make test' as part of 'make dist', so we stop releasing so
20652 many development snapshots that fail their unit tests.
20655 - When we're checking if we have enough dir info for each relay
20656 to begin establishing circuits, make sure that we actually have
20657 the descriptor listed in the consensus, not just any descriptor.
20659 - Bridge relays no longer print "xx=0" in their extrainfo document
20660 for every single country code in the geoip db. Bugfix on
20662 - Only warn when we fail to load the geoip file if we were planning to
20663 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
20664 - If we change our MaxAdvertisedBandwidth and then reload torrc,
20665 Tor won't realize it should publish a new relay descriptor. Fixes
20666 bug 688, reported by mfr. Bugfix on 0.1.2.x.
20667 - When we haven't had any application requests lately, don't bother
20668 logging that we have expired a bunch of descriptors. Bugfix
20670 - Make relay cells written on a connection count as non-padding when
20671 tracking how long a connection has been in use. Bugfix on
20672 0.2.0.1-alpha. Spotted by lodger.
20673 - Fix unit tests in 0.2.0.27-rc.
20674 - Fix compile on Windows.
20677 Changes in version 0.2.0.27-rc - 2008-06-03
20678 Tor 0.2.0.27-rc adds a few features we left out of the earlier
20679 release candidates. In particular, we now include an IP-to-country
20680 GeoIP database, so controllers can easily look up what country a
20681 given relay is in, and so bridge relays can give us some sanitized
20682 summaries about which countries are making use of bridges. (See proposal
20683 126-geoip-fetching.txt for details.)
20686 - Include an IP-to-country GeoIP file in the tarball, so bridge
20687 relays can report sanitized summaries of the usage they're seeing.
20690 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
20691 Robert Hogan. Fixes the first part of bug 681.
20692 - Make bridge authorities never serve extrainfo docs.
20693 - Add support to detect Libevent versions in the 1.4.x series
20695 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
20696 - Include a new contrib/tor-exit-notice.html file that exit relay
20697 operators can put on their website to help reduce abuse queries.
20700 - When tunneling an encrypted directory connection, and its first
20701 circuit fails, do not leave it unattached and ask the controller
20702 to deal. Fixes the second part of bug 681.
20703 - Make bridge authorities correctly expire old extrainfo documents
20707 Changes in version 0.2.0.26-rc - 2008-05-13
20708 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
20709 in Debian's OpenSSL packages. All users running any 0.2.0.x version
20710 should upgrade, whether they're running Debian or not.
20712 o Major security fixes:
20713 - Use new V3 directory authority keys on the tor26, gabelmoo, and
20714 moria1 V3 directory authorities. The old keys were generated with
20715 a vulnerable version of Debian's OpenSSL package, and must be
20716 considered compromised. Other authorities' keys were not generated
20717 with an affected version of OpenSSL.
20720 - List authority signatures as "unrecognized" based on DirServer
20721 lines, not on cert cache. Bugfix on 0.2.0.x.
20724 - Add a new V3AuthUseLegacyKey option to make it easier for
20725 authorities to change their identity keys if they have to.
20728 Changes in version 0.2.0.25-rc - 2008-04-23
20729 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
20732 - Remember to initialize threading before initializing logging.
20733 Otherwise, many BSD-family implementations will crash hard on
20734 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
20737 - Authorities correctly free policies on bad servers on
20738 exit. Fixes bug 672. Bugfix on 0.2.0.x.
20741 Changes in version 0.2.0.24-rc - 2008-04-22
20742 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
20743 v3 directory authority, makes relays with dynamic IP addresses and no
20744 DirPort notice more quickly when their IP address changes, fixes a few
20745 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
20747 o New directory authorities:
20748 - Take lefkada out of the list of v3 directory authorities, since
20749 it has been down for months.
20750 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
20754 - Detect address changes more quickly on non-directory mirror
20755 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
20757 o Minor features (security):
20758 - Reject requests for reverse-dns lookup of names that are in
20759 a private address space. Patch from lodger.
20760 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
20763 o Minor bugfixes (crashes):
20764 - Avoid a rare assert that can trigger when Tor doesn't have much
20765 directory information yet and it tries to fetch a v2 hidden
20766 service descriptor. Fixes bug 651, reported by nwf.
20767 - Initialize log mutex before initializing dmalloc. Otherwise,
20768 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
20769 - Use recursive pthread mutexes in order to avoid deadlock when
20770 logging debug-level messages to a controller. Bug spotted by nwf,
20771 bugfix on 0.2.0.16-alpha.
20773 o Minor bugfixes (resource management):
20774 - Keep address policies from leaking memory: start their refcount
20775 at 1, not 2. Bugfix on 0.2.0.16-alpha.
20776 - Free authority certificates on exit, so they don't look like memory
20777 leaks. Bugfix on 0.2.0.19-alpha.
20778 - Free static hashtables for policy maps and for TLS connections on
20779 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
20780 - Avoid allocating extra space when computing consensuses on 64-bit
20781 platforms. Bug spotted by aakova.
20783 o Minor bugfixes (misc):
20784 - Do not read the configuration file when we've only been told to
20785 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
20786 based on patch from Sebastian Hahn.
20787 - Exit relays that are used as a client can now reach themselves
20788 using the .exit notation, rather than just launching an infinite
20789 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
20790 - When attempting to open a logfile fails, tell us why.
20791 - Fix a dumb bug that was preventing us from knowing that we should
20792 preemptively build circuits to handle expected directory requests.
20793 Fixes bug 660. Bugfix on 0.1.2.x.
20794 - Warn less verbosely about clock skew from netinfo cells from
20795 untrusted sources. Fixes bug 663.
20796 - Make controller stream events for DNS requests more consistent,
20797 by adding "new stream" events for DNS requests, and removing
20798 spurious "stream closed" events" for cached reverse resolves.
20799 Patch from mwenge. Fixes bug 646.
20800 - Correctly notify one-hop connections when a circuit build has
20801 failed. Possible fix for bug 669. Found by lodger.
20804 Changes in version 0.2.0.23-rc - 2008-03-24
20805 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
20806 makes bootstrapping faster if the first directory mirror you contact
20807 is down. The bundles also include the new Vidalia 0.1.2 release.
20810 - When a tunneled directory request is made to a directory server
20811 that's down, notice after 30 seconds rather than 120 seconds. Also,
20812 fail any begindir streams that are pending on it, so they can
20813 retry elsewhere. This was causing multi-minute delays on bootstrap.
20816 Changes in version 0.2.0.22-rc - 2008-03-18
20817 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
20818 enables encrypted directory connections by default for non-relays, fixes
20819 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
20820 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
20823 - Enable encrypted directory connections by default for non-relays,
20824 so censor tools that block Tor directory connections based on their
20825 plaintext patterns will no longer work. This means Tor works in
20826 certain censored countries by default again.
20829 - Make sure servers always request certificates from clients during
20830 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
20831 - Do not enter a CPU-eating loop when a connection is closed in
20832 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
20833 diagnosed by lodger; bugfix on 0.2.0.20-rc.
20834 - Fix assertion failure that could occur when a blocked circuit
20835 became unblocked, and it had pending client DNS requests. Bugfix
20836 on 0.2.0.1-alpha. Fixes bug 632.
20838 o Minor bugfixes (on 0.1.2.x):
20839 - Generate "STATUS_SERVER" events rather than misspelled
20840 "STATUS_SEVER" events. Caught by mwenge.
20841 - When counting the number of bytes written on a TLS connection,
20842 look at the BIO actually used for writing to the network, not
20843 at the BIO used (sometimes) to buffer data for the network.
20844 Looking at different BIOs could result in write counts on the
20845 order of ULONG_MAX. Fixes bug 614.
20846 - On Windows, correctly detect errors when listing the contents of
20847 a directory. Fix from lodger.
20849 o Minor bugfixes (on 0.2.0.x):
20850 - Downgrade "sslv3 alert handshake failure" message to INFO.
20851 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
20852 left BandwidthRate and BandwidthBurst at the default, we would be
20853 silently limited by those defaults. Now raise them to match the
20854 RelayBandwidth* values.
20855 - Fix the SVK version detection logic to work correctly on a branch.
20856 - Make --enable-openbsd-malloc work correctly on Linux with alpha
20857 CPUs. Fixes bug 625.
20858 - Logging functions now check that the passed severity is sane.
20859 - Use proper log levels in the testsuite call of
20860 get_interface_address6().
20861 - When using a nonstandard malloc, do not use the platform values for
20862 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
20863 - Make the openbsd malloc code use 8k pages on alpha CPUs and
20865 - Detect mismatched page sizes when using --enable-openbsd-malloc.
20866 - Avoid double-marked-for-close warning when certain kinds of invalid
20867 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
20868 for bug 617. Bugfix on 0.2.0.1-alpha.
20869 - Make sure that the "NULL-means-reject *:*" convention is followed by
20870 all the policy manipulation functions, avoiding some possible crash
20871 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
20872 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
20873 actually works, and doesn't warn about every single reverse lookup.
20874 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
20877 - Only log guard node status when guard node status has changed.
20878 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
20879 make "INFO" 75% less verbose.
20882 Changes in version 0.2.0.21-rc - 2008-03-02
20883 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
20884 makes Tor work well with Vidalia again, fixes a rare assert bug,
20885 and fixes a pair of more minor bugs. The bundles also include Vidalia
20886 0.1.0 and Torbutton 1.1.16.
20889 - The control port should declare that it requires password auth
20890 when HashedControlSessionPassword is set too. Patch from Matt Edman;
20891 bugfix on 0.2.0.20-rc. Fixes bug 615.
20892 - Downgrade assert in connection_buckets_decrement() to a log message.
20893 This may help us solve bug 614, and in any case will make its
20894 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
20895 - We were sometimes miscounting the number of bytes read from the
20896 network, causing our rate limiting to not be followed exactly.
20897 Bugfix on 0.2.0.16-alpha. Reported by lodger.
20900 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
20901 OpenSSL versions should have been working fine. Diagnosis and patch
20902 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
20903 Bugfix on 0.2.0.20-rc.
20906 Changes in version 0.2.0.20-rc - 2008-02-24
20907 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
20908 makes more progress towards normalizing Tor's TLS handshake, makes
20909 hidden services work better again, helps relays bootstrap if they don't
20910 know their IP address, adds optional support for linking in openbsd's
20911 allocator or tcmalloc, allows really fast relays to scale past 15000
20912 sockets, and fixes a bunch of minor bugs reported by Veracode.
20915 - Enable the revised TLS handshake based on the one designed by
20916 Steven Murdoch in proposal 124, as revised in proposal 130. It
20917 includes version negotiation for OR connections as described in
20918 proposal 105. The new handshake is meant to be harder for censors
20919 to fingerprint, and it adds the ability to detect certain kinds of
20920 man-in-the-middle traffic analysis attacks. The version negotiation
20921 feature will allow us to improve Tor's link protocol more safely
20923 - Choose which bridge to use proportional to its advertised bandwidth,
20924 rather than uniformly at random. This should speed up Tor for
20925 bridge users. Also do this for people who set StrictEntryNodes.
20926 - When a TrackHostExits-chosen exit fails too many times in a row,
20927 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
20930 - Resolved problems with (re-)fetching hidden service descriptors.
20931 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
20932 and 0.2.0.19-alpha.
20933 - If we only ever used Tor for hidden service lookups or posts, we
20934 would stop building circuits and start refusing connections after
20935 24 hours, since we falsely believed that Tor was dormant. Reported
20936 by nwf; bugfix on 0.1.2.x.
20937 - Servers that don't know their own IP address should go to the
20938 authorities for their first directory fetch, even if their DirPort
20939 is off or if they don't know they're reachable yet. This will help
20940 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
20941 - When counting the number of open sockets, count not only the number
20942 of sockets we have received from the socket() call, but also
20943 the number we've gotten from accept() and socketpair(). This bug
20944 made us fail to count all sockets that we were using for incoming
20945 connections. Bugfix on 0.2.0.x.
20946 - Fix code used to find strings within buffers, when those strings
20947 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
20948 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
20949 - Add a new __HashedControlSessionPassword option for controllers
20950 to use for one-off session password hashes that shouldn't get
20951 saved to disk by SAVECONF --- Vidalia users were accumulating a
20952 pile of HashedControlPassword lines in their torrc files, one for
20953 each time they had restarted Tor and then clicked Save. Make Tor
20954 automatically convert "HashedControlPassword" to this new option but
20955 only when it's given on the command line. Partial fix for bug 586.
20957 o Minor features (performance):
20958 - Tune parameters for cell pool allocation to minimize amount of
20960 - Add OpenBSD malloc code from phk as an optional malloc
20961 replacement on Linux: some glibc libraries do very poorly
20962 with Tor's memory allocation patterns. Pass
20963 --enable-openbsd-malloc to get the replacement malloc code.
20964 - Add a --with-tcmalloc option to the configure script to link
20965 against tcmalloc (if present). Does not yet search for
20966 non-system include paths.
20967 - Stop imposing an arbitrary maximum on the number of file descriptors
20968 used for busy servers. Bug reported by Olaf Selke; patch from
20971 o Minor features (other):
20972 - When SafeLogging is disabled, log addresses along with all TLS
20974 - When building with --enable-gcc-warnings, check for whether Apple's
20975 warning "-Wshorten-64-to-32" is available.
20976 - Add a --passphrase-fd argument to the tor-gencert command for
20979 o Minor bugfixes (memory leaks and code problems):
20980 - We were leaking a file descriptor if Tor started with a zero-length
20981 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
20982 - Detect size overflow in zlib code. Reported by Justin Ferguson and
20984 - We were comparing the raw BridgePassword entry with a base64'ed
20985 version of it, when handling a "/tor/networkstatus-bridges"
20986 directory request. Now compare correctly. Noticed by Veracode.
20987 - Recover from bad tracked-since value in MTBF-history file.
20988 Should fix bug 537.
20989 - Alter the code that tries to recover from unhandled write
20990 errors, to not try to flush onto a socket that's given us
20991 unhandled errors. Bugfix on 0.1.2.x.
20992 - Make Unix controlsockets work correctly on OpenBSD. Patch from
20993 tup. Bugfix on 0.2.0.3-alpha.
20995 o Minor bugfixes (other):
20996 - If we have an extra-info document for our server, always make
20997 it available on the control port, even if we haven't gotten
20998 a copy of it from an authority yet. Patch from mwenge.
20999 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
21000 - Directory mirrors no longer include a guess at the client's IP
21001 address if the connection appears to be coming from the same /24
21002 network; it was producing too many wrong guesses.
21003 - Make the new hidden service code respect the SafeLogging setting.
21004 Bugfix on 0.2.0.x. Patch from Karsten.
21005 - When starting as an authority, do not overwrite all certificates
21006 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
21007 - If we're trying to flush the last bytes on a connection (for
21008 example, when answering a directory request), reset the
21009 time-to-give-up timeout every time we manage to write something
21010 on the socket. Bugfix on 0.1.2.x.
21011 - Change the behavior of "getinfo status/good-server-descriptor"
21012 so it doesn't return failure when any authority disappears.
21013 - Even though the man page said that "TrackHostExits ." should
21014 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
21015 - Report TLS "zero return" case as a "clean close" and "IO error"
21016 as a "close". Stop calling closes "unexpected closes": existing
21017 Tors don't use SSL_close(), so having a connection close without
21018 the TLS shutdown handshake is hardly unexpected.
21019 - Send NAMESERVER_STATUS messages for a single failed nameserver
21022 o Code simplifications and refactoring:
21023 - Remove the tor_strpartition function: its logic was confused,
21024 and it was only used for one thing that could be implemented far
21028 Changes in version 0.2.0.19-alpha - 2008-02-09
21029 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
21030 handshake, makes path selection for relays more secure and IP address
21031 guessing more robust, and generally fixes a lot of bugs in preparation
21032 for calling the 0.2.0 branch stable.
21035 - Do not include recognizeable strings in the commonname part of
21036 Tor's x509 certificates.
21039 - If we're a relay, avoid picking ourselves as an introduction point,
21040 a rendezvous point, or as the final hop for internal circuits. Bug
21041 reported by taranis and lodger. Bugfix on 0.1.2.x.
21042 - Patch from "Andrew S. Lists" to catch when we contact a directory
21043 mirror at IP address X and he says we look like we're coming from
21044 IP address X. Bugfix on 0.1.2.x.
21046 o Minor features (security):
21047 - Be more paranoid about overwriting sensitive memory on free(),
21048 as a defensive programming tactic to ensure forward secrecy.
21050 o Minor features (directory authority):
21051 - Actually validate the options passed to AuthDirReject,
21052 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
21053 - Reject router descriptors with out-of-range bandwidthcapacity or
21054 bandwidthburst values.
21056 o Minor features (controller):
21057 - Reject controller commands over 1MB in length. This keeps rogue
21058 processes from running us out of memory.
21060 o Minor features (misc):
21061 - Give more descriptive well-formedness errors for out-of-range
21062 hidden service descriptor/protocol versions.
21063 - Make memory debugging information describe more about history
21064 of cell allocation, so we can help reduce our memory use.
21066 o Deprecated features (controller):
21067 - The status/version/num-versioning and status/version/num-concurring
21068 GETINFO options are no longer useful in the v3 directory protocol:
21069 treat them as deprecated, and warn when they're used.
21072 - When our consensus networkstatus has been expired for a while, stop
21073 being willing to build circuits using it. Fixes bug 401. Bugfix
21075 - Directory caches now fetch certificates from all authorities
21076 listed in a networkstatus consensus, even when they do not
21077 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
21078 - When connecting to a bridge without specifying its key, insert
21079 the connection into the identity-to-connection map as soon as
21080 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
21081 - Detect versions of OS X where malloc_good_size() is present in the
21082 library but never actually declared. Resolves bug 587. Bugfix
21084 - Stop incorrectly truncating zlib responses to directory authority
21085 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
21086 - Stop recommending that every server operator send mail to tor-ops.
21087 Resolves bug 597. Bugfix on 0.1.2.x.
21088 - Don't trigger an assert if we start a directory authority with a
21089 private IP address (like 127.0.0.1).
21090 - Avoid possible failures when generating a directory with routers
21091 with over-long versions strings, or too many flags set. Bugfix
21093 - If an attempt to launch a DNS resolve request over the control
21094 port fails because we have overrun the limit on the number of
21095 connections, tell the controller that the request has failed.
21096 - Avoid using too little bandwidth when our clock skips a few
21097 seconds. Bugfix on 0.1.2.x.
21098 - Fix shell error when warning about missing packages in configure
21099 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
21100 - Do not become confused when receiving a spurious VERSIONS-like
21101 cell from a confused v1 client. Bugfix on 0.2.0.x.
21102 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
21103 introduction points for a hidden service have failed. Patch from
21104 Karsten Loesing. Bugfix on 0.2.0.x.
21106 o Code simplifications and refactoring:
21107 - Remove some needless generality from cpuworker code, for improved
21109 - Stop overloading the circuit_t.onionskin field for both "onionskin
21110 from a CREATE cell that we are waiting for a cpuworker to be
21111 assigned" and "onionskin from an EXTEND cell that we are going to
21112 send to an OR as soon as we are connected". Might help with bug 600.
21113 - Add an in-place version of aes_crypt() so that we can avoid doing a
21114 needless memcpy() call on each cell payload.
21117 Changes in version 0.2.0.18-alpha - 2008-01-25
21118 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
21119 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
21120 that can warn or reject connections to ports generally associated with
21121 vulnerable-plaintext protocols.
21123 o New directory authorities:
21124 - Set up dannenberg (run by CCC) as the sixth v3 directory
21128 - Fix a major memory leak when attempting to use the v2 TLS
21129 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
21130 - We accidentally enabled the under-development v2 TLS handshake
21131 code, which was causing log entries like "TLS error while
21132 renegotiating handshake". Disable it again. Resolves bug 590.
21133 - We were computing the wrong Content-Length: header for directory
21134 responses that need to be compressed on the fly, causing clients
21135 asking for those items to always fail. Bugfix on 0.2.0.x; partially
21139 - Avoid going directly to the directory authorities even if you're a
21140 relay, if you haven't found yourself reachable yet or if you've
21141 decided not to advertise your dirport yet. Addresses bug 556.
21142 - If we've gone 12 hours since our last bandwidth check, and we
21143 estimate we have less than 50KB bandwidth capacity but we could
21144 handle more, do another bandwidth test.
21145 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
21146 Tor can warn and/or refuse connections to ports commonly used with
21147 vulnerable-plaintext protocols. Currently we warn on ports 23,
21148 109, 110, and 143, but we don't reject any.
21151 - When we setconf ClientOnly to 1, close any current OR and Dir
21152 listeners. Reported by mwenge.
21153 - When we get a consensus that's been signed by more people than
21154 we expect, don't log about it; it's not a big deal. Reported
21158 - Don't answer "/tor/networkstatus-bridges" directory requests if
21159 the request isn't encrypted.
21160 - Make "ClientOnly 1" config option disable directory ports too.
21161 - Patches from Karsten Loesing to make v2 hidden services more
21162 robust: work even when there aren't enough HSDir relays available;
21163 retry when a v2 rend desc fetch fails; but don't retry if we
21164 already have a usable v0 rend desc.
21167 Changes in version 0.2.0.17-alpha - 2008-01-17
21168 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
21171 - Make the tor-gencert man page get included correctly in the tarball.
21174 Changes in version 0.2.0.16-alpha - 2008-01-17
21175 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
21176 Loesing, and generally cleans up a lot of features and minor bugs.
21178 o New directory authorities:
21179 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
21182 o Major performance improvements:
21183 - Switch our old ring buffer implementation for one more like that
21184 used by free Unix kernels. The wasted space in a buffer with 1mb
21185 of data will now be more like 8k than 1mb. The new implementation
21186 also avoids realloc();realloc(); patterns that can contribute to
21187 memory fragmentation.
21190 - Configuration files now accept C-style strings as values. This
21191 helps encode characters not allowed in the current configuration
21192 file format, such as newline or #. Addresses bug 557.
21193 - Although we fixed bug 539 (where servers would send HTTP status 503
21194 responses _and_ send a body too), there are still servers out
21195 there that haven't upgraded. Therefore, make clients parse such
21196 bodies when they receive them.
21197 - When we're not serving v2 directory information, there is no reason
21198 to actually keep any around. Remove the obsolete files and directory
21199 on startup if they are very old and we aren't going to serve them.
21201 o Minor performance improvements:
21202 - Reference-count and share copies of address policy entries; only 5%
21203 of them were actually distinct.
21204 - Never walk through the list of logs if we know that no log is
21205 interested in a given message.
21208 - When an authority has not signed a consensus, do not try to
21209 download a nonexistent "certificate with key 00000000". Bugfix
21210 on 0.2.0.x. Fixes bug 569.
21211 - Fix a rare assert error when we're closing one of our threads:
21212 use a mutex to protect the list of logs, so we never write to the
21213 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
21214 bug 575, which is kind of the revenge of bug 222.
21215 - Patch from Karsten Loesing to complain less at both the client
21216 and the relay when a relay used to have the HSDir flag but doesn't
21217 anymore, and we try to upload a hidden service descriptor.
21218 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
21220 - Do not try to download missing certificates until we have tried
21221 to check our fallback consensus. Fixes bug 583.
21222 - Make bridges round reported GeoIP stats info up to the nearest
21223 estimate, not down. Now we can distinguish between "0 people from
21224 this country" and "1 person from this country".
21225 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
21226 - Avoid possible segfault if key generation fails in
21227 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
21228 - Avoid segfault in the case where a badly behaved v2 versioning
21229 directory sends a signed networkstatus with missing client-versions.
21231 - Avoid segfaults on certain complex invocations of
21232 router_get_by_hexdigest(). Bugfix on 0.1.2.
21233 - Correct bad index on array access in parse_http_time(). Bugfix
21235 - Fix possible bug in vote generation when server versions are present
21236 but client versions are not.
21237 - Fix rare bug on REDIRECTSTREAM control command when called with no
21238 port set: it could erroneously report an error when none had
21240 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
21241 compressing large objects and find ourselves with more than 4k
21242 left over. Bugfix on 0.2.0.
21243 - Fix a small memory leak when setting up a hidden service.
21244 - Fix a few memory leaks that could in theory happen under bizarre
21246 - Fix an assert if we post a general-purpose descriptor via the
21247 control port but that descriptor isn't mentioned in our current
21248 network consensus. Bug reported by Jon McLachlan; bugfix on
21251 o Minor features (controller):
21252 - Get NS events working again. Patch from tup.
21253 - The GETCONF command now escapes and quotes configuration values
21254 that don't otherwise fit into the torrc file.
21255 - The SETCONF command now handles quoted values correctly.
21257 o Minor features (directory authorities):
21258 - New configuration options to override default maximum number of
21259 servers allowed on a single IP address. This is important for
21260 running a test network on a single host.
21261 - Actually implement the -s option to tor-gencert.
21262 - Add a manual page for tor-gencert.
21264 o Minor features (bridges):
21265 - Bridge authorities no longer serve bridge descriptors over
21266 unencrypted connections.
21268 o Minor features (other):
21269 - Add hidden services and DNSPorts to the list of things that make
21270 Tor accept that it has running ports. Change starting Tor with no
21271 ports from a fatal error to a warning; we might change it back if
21272 this turns out to confuse anybody. Fixes bug 579.
21275 Changes in version 0.1.2.19 - 2008-01-17
21276 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
21277 exit policy a little bit more conservative so it's safer to run an
21278 exit relay on a home system, and fixes a variety of smaller issues.
21281 - Exit policies now reject connections that are addressed to a
21282 relay's public (external) IP address too, unless
21283 ExitPolicyRejectPrivate is turned off. We do this because too
21284 many relays are running nearby to services that trust them based
21285 on network address.
21288 - When the clock jumps forward a lot, do not allow the bandwidth
21289 buckets to become negative. Fixes bug 544.
21290 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
21291 on every successful resolve. Reported by Mike Perry.
21292 - Purge old entries from the "rephist" database and the hidden
21293 service descriptor database even when DirPort is zero.
21294 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
21295 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
21296 crashing or mis-answering these requests.
21297 - When we decide to send a 503 response to a request for servers, do
21298 not then also send the server descriptors: this defeats the whole
21299 purpose. Fixes bug 539.
21302 - Changing the ExitPolicyRejectPrivate setting should cause us to
21303 rebuild our server descriptor.
21304 - Fix handling of hex nicknames when answering controller requests for
21305 networkstatus by name, or when deciding whether to warn about
21306 unknown routers in a config option. (Patch from mwenge.)
21307 - Fix a couple of hard-to-trigger autoconf problems that could result
21308 in really weird results on platforms whose sys/types.h files define
21309 nonstandard integer types.
21310 - Don't try to create the datadir when running --verify-config or
21311 --hash-password. Resolves bug 540.
21312 - If we were having problems getting a particular descriptor from the
21313 directory caches, and then we learned about a new descriptor for
21314 that router, we weren't resetting our failure count. Reported
21316 - Although we fixed bug 539 (where servers would send HTTP status 503
21317 responses _and_ send a body too), there are still servers out there
21318 that haven't upgraded. Therefore, make clients parse such bodies
21319 when they receive them.
21320 - Run correctly on systems where rlim_t is larger than unsigned long.
21321 This includes some 64-bit systems.
21322 - Run correctly on platforms (like some versions of OS X 10.5) where
21323 the real limit for number of open files is OPEN_FILES, not rlim_max
21324 from getrlimit(RLIMIT_NOFILES).
21325 - Avoid a spurious free on base64 failure.
21326 - Avoid segfaults on certain complex invocations of
21327 router_get_by_hexdigest().
21328 - Fix rare bug on REDIRECTSTREAM control command when called with no
21329 port set: it could erroneously report an error when none had
21333 Changes in version 0.2.0.15-alpha - 2007-12-25
21334 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
21335 features added in 0.2.0.13-alpha.
21338 - Fix several remotely triggerable asserts based on DirPort requests
21339 for a v2 or v3 networkstatus object before we were prepared. This
21340 was particularly bad for 0.2.0.13 and later bridge relays, who
21341 would never have a v2 networkstatus and would thus always crash
21342 when used. Bugfixes on 0.2.0.x.
21343 - Estimate the v3 networkstatus size more accurately, rather than
21344 estimating it at zero bytes and giving it artificially high priority
21345 compared to other directory requests. Bugfix on 0.2.0.x.
21348 - Fix configure.in logic for cross-compilation.
21349 - When we load a bridge descriptor from the cache, and it was
21350 previously unreachable, mark it as retriable so we won't just
21351 ignore it. Also, try fetching a new copy immediately. Bugfixes
21353 - The bridge GeoIP stats were counting other relays, for example
21354 self-reachability and authority-reachability tests.
21357 - Support compilation to target iPhone; patch from cjacker huang.
21358 To build for iPhone, pass the --enable-iphone option to configure.
21361 Changes in version 0.2.0.14-alpha - 2007-12-23
21363 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
21364 without a datadirectory from a previous Tor install. Reported
21366 - Fix a crash when we fetch a descriptor that turns out to be
21367 unexpected (it used to be in our networkstatus when we started
21368 fetching it, but it isn't in our current networkstatus), and we
21369 aren't using bridges. Bugfix on 0.2.0.x.
21370 - Fix a crash when accessing hidden services: it would work the first
21371 time you use a given introduction point for your service, but
21372 on subsequent requests we'd be using garbage memory. Fixed by
21373 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
21374 - Fix a crash when we load a bridge descriptor from disk but we don't
21375 currently have a Bridge line for it in our torrc. Bugfix on
21379 - If bridge authorities set BridgePassword, they will serve a
21380 snapshot of known bridge routerstatuses from their DirPort to
21381 anybody who knows that password. Unset by default.
21384 - Make the unit tests build again.
21385 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
21386 - Make PublishServerDescriptor default to 1, so the default doesn't
21387 have to change as we invent new directory protocol versions.
21388 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
21389 be included unless sys/time.h is already included. Fixes
21390 bug 553. Bugfix on 0.2.0.x.
21391 - If we receive a general-purpose descriptor and then receive an
21392 identical bridge-purpose descriptor soon after, don't discard
21393 the next one as a duplicate.
21396 - If BridgeRelay is set to 1, then the default for
21397 PublishServerDescriptor is now "bridge" rather than "v2,v3".
21398 - If the user sets RelayBandwidthRate but doesn't set
21399 RelayBandwidthBurst, then make them equal rather than erroring out.
21402 Changes in version 0.2.0.13-alpha - 2007-12-21
21403 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
21404 Goodell, fixes many more bugs, and adds a lot of infrastructure for
21407 o New directory authorities:
21408 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
21412 - Only update guard status (usable / not usable) once we have
21413 enough directory information. This was causing us to always pick
21414 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
21415 causing us to discard all our guards on startup if we hadn't been
21416 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
21417 - Purge old entries from the "rephist" database and the hidden
21418 service descriptor databases even when DirPort is zero. Bugfix
21420 - We were ignoring our RelayBandwidthRate for the first 30 seconds
21421 after opening a circuit -- even a relayed circuit. Bugfix on
21423 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
21424 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
21425 crashing or mis-answering these types of requests.
21426 - Relays were publishing their server descriptor to v1 and v2
21427 directory authorities, but they didn't try publishing to v3-only
21428 authorities. Fix this; and also stop publishing to v1 authorities.
21430 - When we were reading router descriptors from cache, we were ignoring
21431 the annotations -- so for example we were reading in bridge-purpose
21432 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
21433 - When we decided to send a 503 response to a request for servers, we
21434 were then also sending the server descriptors: this defeats the
21435 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
21438 - Bridge relays now behave like clients with respect to time
21439 intervals for downloading new consensus documents -- otherwise they
21440 stand out. Bridge users now wait until the end of the interval,
21441 so their bridge relay will be sure to have a new consensus document.
21442 - Three new config options (AlternateDirAuthority,
21443 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
21444 user selectively replace the default directory authorities by type,
21445 rather than the all-or-nothing replacement that DirServer offers.
21446 - Tor can now be configured to read a GeoIP file from disk in one
21447 of two formats. This can be used by controllers to map IP addresses
21448 to countries. Eventually, it may support exit-by-country.
21449 - When possible, bridge relays remember which countries users
21450 are coming from, and report aggregate information in their
21451 extra-info documents, so that the bridge authorities can learn
21452 where Tor is blocked.
21453 - Bridge directory authorities now do reachability testing on the
21454 bridges they know. They provide router status summaries to the
21455 controller via "getinfo ns/purpose/bridge", and also dump summaries
21456 to a file periodically.
21457 - Stop fetching directory info so aggressively if your DirPort is
21458 on but your ORPort is off; stop fetching v2 dir info entirely.
21459 You can override these choices with the new FetchDirInfoEarly
21463 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
21464 consensus documents when there are too many relays at a single
21465 IP address. Now clear it in v2 network status documents too, and
21466 also clear it in routerinfo_t when the relay is no longer listed
21467 in the relevant networkstatus document.
21468 - Don't crash if we get an unexpected value for the
21469 PublishServerDescriptor config option. Reported by Matt Edman;
21470 bugfix on 0.2.0.9-alpha.
21471 - Our new v2 hidden service descriptor format allows descriptors
21472 that have no introduction points. But Tor crashed when we tried
21473 to build a descriptor with no intro points (and it would have
21474 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
21475 by Karsten Loesing.
21476 - Fix building with dmalloc 5.5.2 with glibc.
21477 - Reject uploaded descriptors and extrainfo documents if they're
21478 huge. Otherwise we'll cache them all over the network and it'll
21479 clog everything up. Reported by Aljosha Judmayer.
21480 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
21481 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
21482 - When the DANGEROUS_VERSION controller status event told us we're
21483 running an obsolete version, it used the string "OLD" to describe
21484 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
21485 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
21486 - If we can't expand our list of entry guards (e.g. because we're
21487 using bridges or we have StrictEntryNodes set), don't mark relays
21488 down when they fail a directory request. Otherwise we're too quick
21489 to mark all our entry points down. Bugfix on 0.1.2.x.
21490 - Fix handling of hex nicknames when answering controller requests for
21491 networkstatus by name, or when deciding whether to warn about unknown
21492 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
21493 - Fix a couple of hard-to-trigger autoconf problems that could result
21494 in really weird results on platforms whose sys/types.h files define
21495 nonstandard integer types. Bugfix on 0.1.2.x.
21496 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
21497 - Don't crash on name lookup when we have no current consensus. Fixes
21498 bug 538; bugfix on 0.2.0.x.
21499 - Only Tors that want to mirror the v2 directory info should
21500 create the "cached-status" directory in their datadir. (All Tors
21501 used to create it.) Bugfix on 0.2.0.9-alpha.
21502 - Directory authorities should only automatically download Extra Info
21503 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
21506 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
21507 consumers. (We already do this on HUP.)
21508 - Authorities and caches fetch the v2 networkstatus documents
21509 less often, now that v3 is encouraged.
21510 - Add a new config option BridgeRelay that specifies you want to
21511 be a bridge relay. Right now the only difference is that it makes
21512 you answer begin_dir requests, and it makes you cache dir info,
21513 even if your DirPort isn't on.
21514 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
21515 ask about source, timestamp of arrival, purpose, etc. We need
21516 something like this to help Vidalia not do GeoIP lookups on bridge
21518 - Allow multiple HashedControlPassword config lines, to support
21519 multiple controller passwords.
21520 - Authorities now decide whether they're authoritative for a given
21521 router based on the router's purpose.
21522 - New config options AuthDirBadDir and AuthDirListBadDirs for
21523 authorities to mark certain relays as "bad directories" in the
21524 networkstatus documents. Also supports the "!baddir" directive in
21525 the approved-routers file.
21528 Changes in version 0.2.0.12-alpha - 2007-11-16
21529 This twelfth development snapshot fixes some more build problems as
21530 well as a few minor bugs.
21533 - Make it build on OpenBSD again. Patch from tup.
21534 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
21535 package-building for Red Hat, OS X, etc.
21537 o Minor bugfixes (on 0.1.2.x):
21538 - Changing the ExitPolicyRejectPrivate setting should cause us to
21539 rebuild our server descriptor.
21541 o Minor bugfixes (on 0.2.0.x):
21542 - When we're lacking a consensus, don't try to perform rendezvous
21543 operations. Reported by Karsten Loesing.
21544 - Fix a small memory leak whenever we decide against using a
21545 newly picked entry guard. Reported by Mike Perry.
21546 - When authorities detected more than two relays running on the same
21547 IP address, they were clearing all the status flags but forgetting
21548 to clear the "hsdir" flag. So clients were being told that a
21549 given relay was the right choice for a v2 hsdir lookup, yet they
21550 never had its descriptor because it was marked as 'not running'
21552 - If we're trying to fetch a bridge descriptor and there's no way
21553 the bridge authority could help us (for example, we don't know
21554 a digest, or there is no bridge authority), don't be so eager to
21555 fall back to asking the bridge authority.
21556 - If we're using bridges or have strictentrynodes set, and our
21557 chosen exit is in the same family as all our bridges/entry guards,
21558 then be flexible about families.
21561 - When we negotiate a v2 link-layer connection (not yet implemented),
21562 accept RELAY_EARLY cells and turn them into RELAY cells if we've
21563 negotiated a v1 connection for their next step. Initial code for
21567 Changes in version 0.2.0.11-alpha - 2007-11-12
21568 This eleventh development snapshot fixes some build problems with
21569 the previous snapshot. It also includes a more secure-by-default exit
21570 policy for relays, fixes an enormous memory leak for exit relays, and
21571 fixes another bug where servers were falling out of the directory list.
21574 - Exit policies now reject connections that are addressed to a
21575 relay's public (external) IP address too, unless
21576 ExitPolicyRejectPrivate is turned off. We do this because too
21577 many relays are running nearby to services that trust them based
21578 on network address. Bugfix on 0.1.2.x.
21581 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
21582 on every successful resolve. Reported by Mike Perry; bugfix
21584 - On authorities, never downgrade to old router descriptors simply
21585 because they're listed in the consensus. This created a catch-22
21586 where we wouldn't list a new descriptor because there was an
21587 old one in the consensus, and we couldn't get the new one in the
21588 consensus because we wouldn't list it. Possible fix for bug 548.
21589 Also, this might cause bug 543 to appear on authorities; if so,
21590 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
21592 o Packaging fixes on 0.2.0.10-alpha:
21593 - We were including instructions about what to do with the
21594 src/config/fallback-consensus file, but we weren't actually
21595 including it in the tarball. Disable all of that for now.
21598 - Allow people to say PreferTunnelledDirConns rather than
21599 PreferTunneledDirConns, for those alternate-spellers out there.
21602 - Don't reevaluate all the information from our consensus document
21603 just because we've downloaded a v2 networkstatus that we intend
21604 to cache. Fixes bug 545; bugfix on 0.2.0.x.
21607 Changes in version 0.2.0.10-alpha - 2007-11-10
21608 This tenth development snapshot adds a third v3 directory authority
21609 run by Mike Perry, adds most of Karsten Loesing's new hidden service
21610 descriptor format, fixes a bad crash bug and new bridge bugs introduced
21611 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
21612 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
21613 addresses many more minor issues.
21615 o New directory authorities:
21616 - Set up ides (run by Mike Perry) as the third v3 directory authority.
21619 - Allow tunnelled directory connections to ask for an encrypted
21620 "begin_dir" connection or an anonymized "uses a full Tor circuit"
21621 connection independently. Now we can make anonymized begin_dir
21622 connections for (e.g.) more secure hidden service posting and
21624 - More progress on proposal 114: code from Karsten Loesing to
21625 implement new hidden service descriptor format.
21626 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
21627 accommodate the growing number of servers that use the default
21628 and are reaching it.
21629 - Directory authorities use a new formula for selecting which nodes
21630 to advertise as Guards: they must be in the top 7/8 in terms of
21631 how long we have known about them, and above the median of those
21632 nodes in terms of weighted fractional uptime.
21633 - Make "not enough dir info yet" warnings describe *why* Tor feels
21634 it doesn't have enough directory info yet.
21637 - Stop servers from crashing if they set a Family option (or
21638 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
21640 - Make bridge users work again -- the move to v3 directories in
21641 0.2.0.9-alpha had introduced a number of bugs that made bridges
21642 no longer work for clients.
21643 - When the clock jumps forward a lot, do not allow the bandwidth
21644 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
21646 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
21647 - When the consensus lists a router descriptor that we previously were
21648 mirroring, but that we considered non-canonical, reload the
21649 descriptor as canonical. This fixes bug 543 where Tor servers
21650 would start complaining after a few days that they don't have
21651 enough directory information to build a circuit.
21652 - Consider replacing the current consensus when certificates arrive
21653 that make the pending consensus valid. Previously, we were only
21654 considering replacement when the new certs _didn't_ help.
21655 - Fix an assert error on startup if we didn't already have the
21656 consensus and certs cached in our datadirectory: we were caching
21657 the consensus in consensus_waiting_for_certs but then free'ing it
21659 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
21660 Request) if we need more v3 certs but we've already got pending
21661 requests for all of them.
21662 - Correctly back off from failing certificate downloads. Fixes
21664 - Authorities don't vote on the Running flag if they have been running
21665 for less than 30 minutes themselves. Fixes bug 547, where a newly
21666 started authority would vote that everyone was down.
21668 o New requirements:
21669 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
21670 it, it had no AES, and it hasn't seen any security patches since
21674 - Clients now hold circuitless TLS connections open for 1.5 times
21675 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
21676 rebuild a new circuit over them within that timeframe. Previously,
21677 they held them open only for KeepalivePeriod (5 minutes).
21678 - Use "If-Modified-Since" to avoid retrieving consensus
21679 networkstatuses that we already have.
21680 - When we have no consensus, check FallbackNetworkstatusFile (defaults
21681 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
21682 we start knowing some directory caches.
21683 - When we receive a consensus from the future, warn about skew.
21684 - Improve skew reporting: try to give the user a better log message
21685 about how skewed they are, and how much this matters.
21686 - When we have a certificate for an authority, believe that
21687 certificate's claims about the authority's IP address.
21688 - New --quiet command-line option to suppress the default console log.
21689 Good in combination with --hash-password.
21690 - Authorities send back an X-Descriptor-Not-New header in response to
21691 an accepted-but-discarded descriptor upload. Partially implements
21693 - Make the log message for "tls error. breaking." more useful.
21694 - Better log messages about certificate downloads, to attempt to
21695 track down the second incarnation of bug 546.
21697 o Minor features (bridges):
21698 - If bridge users set UpdateBridgesFromAuthority, but the digest
21699 they ask for is a 404 from the bridge authority, they now fall
21700 back to trying the bridge directly.
21701 - Bridges now use begin_dir to publish their server descriptor to
21702 the bridge authority, even when they haven't set TunnelDirConns.
21704 o Minor features (controller):
21705 - When reporting clock skew, and we know that the clock is _at least
21706 as skewed_ as some value, but we don't know the actual value,
21707 report the value as a "minimum skew."
21710 - Update linux-tor-prio.sh script to allow QoS based on the uid of
21711 the Tor process. Patch from Marco Bonetti with tweaks from Mike
21715 - Refuse to start if both ORPort and UseBridges are set. Bugfix
21716 on 0.2.0.x, suggested by Matt Edman.
21717 - Don't stop fetching descriptors when FetchUselessDescriptors is
21718 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
21719 reported by tup and ioerror.
21720 - Better log message on vote from unknown authority.
21721 - Don't log "Launching 0 request for 0 router" message.
21723 o Minor bugfixes (memory leaks):
21724 - Stop leaking memory every time we parse a v3 certificate. Bugfix
21726 - Stop leaking memory every time we load a v3 certificate. Bugfix
21727 on 0.2.0.1-alpha. Fixes bug 536.
21728 - Stop leaking a cached networkstatus on exit. Bugfix on
21730 - Stop leaking voter information every time we free a consensus.
21731 Bugfix on 0.2.0.3-alpha.
21732 - Stop leaking signed data every time we check a voter signature.
21733 Bugfix on 0.2.0.3-alpha.
21734 - Stop leaking a signature every time we fail to parse a consensus or
21735 a vote. Bugfix on 0.2.0.3-alpha.
21736 - Stop leaking v2_download_status_map on shutdown. Bugfix on
21738 - Stop leaking conn->nickname every time we make a connection to a
21739 Tor relay without knowing its expected identity digest (e.g. when
21740 using bridges). Bugfix on 0.2.0.3-alpha.
21742 - Minor bugfixes (portability):
21743 - Run correctly on platforms where rlim_t is larger than unsigned
21744 long, and/or where the real limit for number of open files is
21745 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
21746 particular, these may be needed for OS X 10.5.
21749 Changes in version 0.1.2.18 - 2007-10-28
21750 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
21751 hidden service introduction that were causing huge delays, and a big
21752 bug that was causing some servers to disappear from the network status
21753 lists for a few hours each day.
21755 o Major bugfixes (crashes):
21756 - If a connection is shut down abruptly because of something that
21757 happened inside connection_flushed_some(), do not call
21758 connection_finished_flushing(). Should fix bug 451:
21759 "connection_stop_writing: Assertion conn->write_event failed"
21760 Bugfix on 0.1.2.7-alpha.
21761 - Fix possible segfaults in functions called from
21762 rend_process_relay_cell().
21764 o Major bugfixes (hidden services):
21765 - Hidden services were choosing introduction points uniquely by
21766 hexdigest, but when constructing the hidden service descriptor
21767 they merely wrote the (potentially ambiguous) nickname.
21768 - Clients now use the v2 intro format for hidden service
21769 connections: they specify their chosen rendezvous point by identity
21770 digest rather than by (potentially ambiguous) nickname. These
21771 changes could speed up hidden service connections dramatically.
21773 o Major bugfixes (other):
21774 - Stop publishing a new server descriptor just because we get a
21775 HUP signal. This led (in a roundabout way) to some servers getting
21776 dropped from the networkstatus lists for a few hours each day.
21777 - When looking for a circuit to cannibalize, consider family as well
21778 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
21779 circuit cannibalization).
21780 - When a router wasn't listed in a new networkstatus, we were leaving
21781 the flags for that router alone -- meaning it remained Named,
21782 Running, etc -- even though absence from the networkstatus means
21783 that it shouldn't be considered to exist at all anymore. Now we
21784 clear all the flags for routers that fall out of the networkstatus
21785 consensus. Fixes bug 529.
21788 - Don't try to access (or alter) the state file when running
21789 --list-fingerprint or --verify-config or --hash-password. Resolves
21791 - When generating information telling us how to extend to a given
21792 router, do not try to include the nickname if it is
21793 absent. Resolves bug 467.
21794 - Fix a user-triggerable segfault in expand_filename(). (There isn't
21795 a way to trigger this remotely.)
21796 - When sending a status event to the controller telling it that an
21797 OR address is reachable, set the port correctly. (Previously we
21798 were reporting the dir port.)
21799 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
21800 command. Bugfix on 0.1.2.17.
21801 - When loading bandwidth history, do not believe any information in
21802 the future. Fixes bug 434.
21803 - When loading entry guard information, do not believe any information
21805 - When we have our clock set far in the future and generate an
21806 onion key, then re-set our clock to be correct, we should not stop
21807 the onion key from getting rotated.
21808 - On some platforms, accept() can return a broken address. Detect
21809 this more quietly, and deal accordingly. Fixes bug 483.
21810 - It's not actually an error to find a non-pending entry in the DNS
21811 cache when canceling a pending resolve. Don't log unless stuff
21812 is fishy. Resolves bug 463.
21813 - Don't reset trusted dir server list when we set a configuration
21814 option. Patch from Robert Hogan.
21815 - Don't try to create the datadir when running --verify-config or
21816 --hash-password. Resolves bug 540.
21819 Changes in version 0.2.0.9-alpha - 2007-10-24
21820 This ninth development snapshot switches clients to the new v3 directory
21821 system; allows servers to be listed in the network status even when they
21822 have the same nickname as a registered server; and fixes many other
21823 bugs including a big one that was causing some servers to disappear
21824 from the network status lists for a few hours each day.
21826 o Major features (directory system):
21827 - Clients now download v3 consensus networkstatus documents instead
21828 of v2 networkstatus documents. Clients and caches now base their
21829 opinions about routers on these consensus documents. Clients only
21830 download router descriptors listed in the consensus.
21831 - Authorities now list servers who have the same nickname as
21832 a different named server, but list them with a new flag,
21833 "Unnamed". Now we can list servers that happen to pick the same
21834 nickname as a server that registered two years ago and then
21835 disappeared. Partially implements proposal 122.
21836 - If the consensus lists a router as "Unnamed", the name is assigned
21837 to a different router: do not identify the router by that name.
21838 Partially implements proposal 122.
21839 - Authorities can now come to a consensus on which method to use to
21840 compute the consensus. This gives us forward compatibility.
21843 - Stop publishing a new server descriptor just because we HUP or
21844 when we find our DirPort to be reachable but won't actually publish
21845 it. New descriptors without any real changes are dropped by the
21846 authorities, and can screw up our "publish every 18 hours" schedule.
21848 - When a router wasn't listed in a new networkstatus, we were leaving
21849 the flags for that router alone -- meaning it remained Named,
21850 Running, etc -- even though absence from the networkstatus means
21851 that it shouldn't be considered to exist at all anymore. Now we
21852 clear all the flags for routers that fall out of the networkstatus
21853 consensus. Fixes bug 529; bugfix on 0.1.2.x.
21854 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
21855 extrainfo documents and then discard them immediately for not
21856 matching the latest router. Bugfix on 0.2.0.1-alpha.
21858 o Minor features (v3 directory protocol):
21859 - Allow tor-gencert to generate a new certificate without replacing
21861 - Allow certificates to include an address.
21862 - When we change our directory-cache settings, reschedule all voting
21863 and download operations.
21864 - Reattempt certificate downloads immediately on failure, as long as
21865 we haven't failed a threshold number of times yet.
21866 - Delay retrying consensus downloads while we're downloading
21867 certificates to verify the one we just got. Also, count getting a
21868 consensus that we already have (or one that isn't valid) as a failure,
21869 and count failing to get the certificates after 20 minutes as a
21871 - Build circuits and download descriptors even if our consensus is a
21872 little expired. (This feature will go away once authorities are
21875 o Minor features (router descriptor cache):
21876 - If we find a cached-routers file that's been sitting around for more
21877 than 28 days unmodified, then most likely it's a leftover from
21878 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
21880 - When we (as a cache) download a descriptor because it was listed
21881 in a consensus, remember when the consensus was supposed to expire,
21882 and don't expire the descriptor until then.
21884 o Minor features (performance):
21885 - Call routerlist_remove_old_routers() much less often. This should
21886 speed startup, especially on directory caches.
21887 - Don't try to launch new descriptor downloads quite so often when we
21888 already have enough directory information to build circuits.
21889 - Base64 decoding was actually showing up on our profile when parsing
21890 the initial descriptor file; switch to an in-process all-at-once
21891 implementation that's about 3.5x times faster than calling out to
21894 o Minor features (compilation):
21895 - Detect non-ASCII platforms (if any still exist) and refuse to
21896 build there: some of our code assumes that 'A' is 65 and so on.
21898 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
21899 - Make the "next period" votes into "current period" votes immediately
21900 after publishing the consensus; avoid a heisenbug that made them
21901 stick around indefinitely.
21902 - When we discard a vote as a duplicate, do not report this as
21904 - Treat missing v3 keys or certificates as an error when running as a
21905 v3 directory authority.
21906 - When we're configured to be a v3 authority, but we're only listed
21907 as a non-v3 authority in our DirServer line for ourself, correct
21909 - If an authority doesn't have a qualified hostname, just put
21910 its address in the vote. This fixes the problem where we referred to
21911 "moria on moria:9031."
21912 - Distinguish between detached signatures for the wrong period, and
21913 detached signatures for a divergent vote.
21914 - Fix a small memory leak when computing a consensus.
21915 - When there's no consensus, we were forming a vote every 30
21916 minutes, but writing the "valid-after" line in our vote based
21917 on our configured V3AuthVotingInterval: so unless the intervals
21918 matched up, we immediately rejected our own vote because it didn't
21919 start at the voting interval that caused us to construct a vote.
21921 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
21922 - Delete unverified-consensus when the real consensus is set.
21923 - Consider retrying a consensus networkstatus fetch immediately
21924 after one fails: don't wait 60 seconds to notice.
21925 - When fetching a consensus as a cache, wait until a newer consensus
21926 should exist before trying to replace the current one.
21927 - Use a more forgiving schedule for retrying failed consensus
21928 downloads than for other types.
21930 o Minor bugfixes (other directory issues):
21931 - Correct the implementation of "download votes by digest." Bugfix on
21933 - Authorities no longer send back "400 you're unreachable please fix
21934 it" errors to Tor servers that aren't online all the time. We're
21935 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
21937 o Minor bugfixes (controller):
21938 - Don't reset trusted dir server list when we set a configuration
21939 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
21940 - Respond to INT and TERM SIGNAL commands before we execute the
21941 signal, in case the signal shuts us down. We had a patch in
21942 0.1.2.1-alpha that tried to do this by queueing the response on
21943 the connection's buffer before shutting down, but that really
21944 isn't the same thing at all. Bug located by Matt Edman.
21946 o Minor bugfixes (misc):
21947 - Correctly check for bad options to the "PublishServerDescriptor"
21948 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
21949 - Stop leaking memory on failing case of base32_decode, and make
21950 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
21951 - Don't try to download extrainfo documents when we're trying to
21952 fetch enough directory info to build a circuit: having enough
21953 info should get priority. Bugfix on 0.2.0.x.
21954 - Don't complain that "your server has not managed to confirm that its
21955 ports are reachable" if we haven't been able to build any circuits
21956 yet. Bug found by spending four hours without a v3 consensus. Bugfix
21958 - Detect the reason for failing to mmap a descriptor file we just
21959 wrote, and give a more useful log message. Fixes bug 533. Bugfix
21962 o Code simplifications and refactoring:
21963 - Remove support for the old bw_accounting file: we've been storing
21964 bandwidth accounting information in the state file since
21965 0.1.2.5-alpha. This may result in bandwidth accounting errors
21966 if you try to upgrade from 0.1.1.x or earlier, or if you try to
21967 downgrade to 0.1.1.x or earlier.
21968 - New convenience code to locate a file within the DataDirectory.
21969 - Move non-authority functionality out of dirvote.c.
21970 - Refactor the arguments for router_pick_{directory_|trusteddir}server
21971 so that they all take the same named flags.
21974 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
21975 Unix users an easy way to script their Tor process (e.g. by
21976 adjusting bandwidth based on the time of the day).
21979 Changes in version 0.2.0.8-alpha - 2007-10-12
21980 This eighth development snapshot fixes a crash bug that's been bothering
21981 us since February 2007, lets bridge authorities store a list of bridge
21982 descriptors they've seen, gets v3 directory voting closer to working,
21983 starts caching v3 directory consensus documents on directory mirrors,
21984 and fixes a variety of smaller issues including some minor memory leaks.
21986 o Major features (router descriptor cache):
21987 - Store routers in a file called cached-descriptors instead of in
21988 cached-routers. Initialize cached-descriptors from cached-routers
21989 if the old format is around. The new format allows us to store
21990 annotations along with descriptors.
21991 - Use annotations to record the time we received each descriptor, its
21992 source, and its purpose.
21993 - Disable the SETROUTERPURPOSE controller command: it is now
21995 - Controllers should now specify cache=no or cache=yes when using
21996 the +POSTDESCRIPTOR command.
21997 - Bridge authorities now write bridge descriptors to disk, meaning
21998 we can export them to other programs and begin distributing them
22001 o Major features (directory authorities):
22002 - When a v3 authority is missing votes or signatures, it now tries
22004 - Directory authorities track weighted fractional uptime as well as
22005 weighted mean-time-between failures. WFU is suitable for deciding
22006 whether a node is "usually up", while MTBF is suitable for deciding
22007 whether a node is "likely to stay up." We need both, because
22008 "usually up" is a good requirement for guards, while "likely to
22009 stay up" is a good requirement for long-lived connections.
22011 o Major features (v3 directory system):
22012 - Caches now download v3 network status documents as needed,
22013 and download the descriptors listed in them.
22014 - All hosts now attempt to download and keep fresh v3 authority
22015 certificates, and re-attempt after failures.
22016 - More internal-consistency checks for vote parsing.
22018 o Major bugfixes (crashes):
22019 - If a connection is shut down abruptly because of something that
22020 happened inside connection_flushed_some(), do not call
22021 connection_finished_flushing(). Should fix bug 451. Bugfix on
22024 o Major bugfixes (performance):
22025 - Fix really bad O(n^2) performance when parsing a long list of
22026 routers: Instead of searching the entire list for an "extra-info "
22027 string which usually wasn't there, once for every routerinfo
22028 we read, just scan lines forward until we find one we like.
22030 - When we add data to a write buffer in response to the data on that
22031 write buffer getting low because of a flush, do not consider the
22032 newly added data as a candidate for immediate flushing, but rather
22033 make it wait until the next round of writing. Otherwise, we flush
22034 and refill recursively, and a single greedy TLS connection can
22035 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
22037 o Minor features (v3 authority system):
22038 - Add more ways for tools to download the votes that lead to the
22040 - Send a 503 when low on bandwidth and a vote, consensus, or
22041 certificate is requested.
22042 - If-modified-since is now implemented properly for all kinds of
22043 certificate requests.
22045 o Minor bugfixes (network statuses):
22046 - Tweak the implementation of proposal 109 slightly: allow at most
22047 two Tor servers on the same IP address, except if it's the location
22048 of a directory authority, in which case allow five. Bugfix on
22051 o Minor bugfixes (controller):
22052 - When sending a status event to the controller telling it that an
22053 OR address is reachable, set the port correctly. (Previously we
22054 were reporting the dir port.) Bugfix on 0.1.2.x.
22056 o Minor bugfixes (v3 directory system):
22057 - Fix logic to look up a cert by its signing key digest. Bugfix on
22059 - Only change the reply to a vote to "OK" if it's not already
22060 set. This gets rid of annoying "400 OK" log messages, which may
22061 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
22062 - When we get a valid consensus, recompute the voting schedule.
22063 - Base the valid-after time of a vote on the consensus voting
22064 schedule, not on our preferred schedule.
22065 - Make the return values and messages from signature uploads and
22066 downloads more sensible.
22067 - Fix a memory leak when serving votes and consensus documents, and
22068 another when serving certificates.
22070 o Minor bugfixes (performance):
22071 - Use a slightly simpler string hashing algorithm (copying Python's
22072 instead of Java's) and optimize our digest hashing algorithm to take
22073 advantage of 64-bit platforms and to remove some possibly-costly
22075 - Fix a minor memory leak whenever we parse guards from our state
22076 file. Bugfix on 0.2.0.7-alpha.
22077 - Fix a minor memory leak whenever we write out a file. Bugfix on
22079 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
22080 command. Bugfix on 0.2.0.5-alpha.
22082 o Minor bugfixes (portability):
22083 - On some platforms, accept() can return a broken address. Detect
22084 this more quietly, and deal accordingly. Fixes bug 483.
22085 - Stop calling tor_strlower() on uninitialized memory in some cases.
22086 Bugfix in 0.2.0.7-alpha.
22088 o Minor bugfixes (usability):
22089 - Treat some 403 responses from directory servers as INFO rather than
22090 WARN-severity events.
22091 - It's not actually an error to find a non-pending entry in the DNS
22092 cache when canceling a pending resolve. Don't log unless stuff is
22093 fishy. Resolves bug 463.
22095 o Minor bugfixes (anonymity):
22096 - Never report that we've used more bandwidth than we're willing to
22097 relay: it leaks how much non-relay traffic we're using. Resolves
22099 - When looking for a circuit to cannibalize, consider family as well
22100 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
22101 circuit cannibalization).
22103 o Code simplifications and refactoring:
22104 - Make a bunch of functions static. Remove some dead code.
22105 - Pull out about a third of the really big routerlist.c; put it in a
22106 new module, networkstatus.c.
22107 - Merge the extra fields in local_routerstatus_t back into
22108 routerstatus_t: we used to need one routerstatus_t for each
22109 authority's opinion, plus a local_routerstatus_t for the locally
22110 computed consensus opinion. To save space, we put the locally
22111 modified fields into local_routerstatus_t, and only the common
22112 stuff into routerstatus_t. But once v3 directories are in use,
22113 clients and caches will no longer need to hold authority opinions;
22114 thus, the rationale for keeping the types separate is now gone.
22115 - Make the code used to reschedule and reattempt downloads more
22117 - Turn all 'Are we a directory server/mirror?' logic into a call to
22119 - Remove the code to generate the oldest (v1) directory format.
22120 The code has been disabled since 0.2.0.5-alpha.
22123 Changes in version 0.2.0.7-alpha - 2007-09-21
22124 This seventh development snapshot makes bridges work again, makes bridge
22125 authorities work for the first time, fixes two huge performance flaws
22126 in hidden services, and fixes a variety of minor issues.
22128 o New directory authorities:
22129 - Set up moria1 and tor26 as the first v3 directory authorities. See
22130 doc/spec/dir-spec.txt for details on the new directory design.
22132 o Major bugfixes (crashes):
22133 - Fix possible segfaults in functions called from
22134 rend_process_relay_cell(). Bugfix on 0.1.2.x.
22136 o Major bugfixes (bridges):
22137 - Fix a bug that made servers send a "404 Not found" in response to
22138 attempts to fetch their server descriptor. This caused Tor servers
22139 to take many minutes to establish reachability for their DirPort,
22140 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
22141 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
22142 users configure that and specify a bridge with an identity
22143 fingerprint, now they will lookup the bridge descriptor at the
22144 default bridge authority via a one-hop tunnel, but once circuits
22145 are established they will switch to a three-hop tunnel for later
22146 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
22148 o Major bugfixes (hidden services):
22149 - Hidden services were choosing introduction points uniquely by
22150 hexdigest, but when constructing the hidden service descriptor
22151 they merely wrote the (potentially ambiguous) nickname.
22152 - Clients now use the v2 intro format for hidden service
22153 connections: they specify their chosen rendezvous point by identity
22154 digest rather than by (potentially ambiguous) nickname. Both
22155 are bugfixes on 0.1.2.x, and they could speed up hidden service
22156 connections dramatically. Thanks to Karsten Loesing.
22158 o Minor features (security):
22159 - As a client, do not believe any server that tells us that an
22160 address maps to an internal address space.
22161 - Make it possible to enable HashedControlPassword and
22162 CookieAuthentication at the same time.
22164 o Minor features (guard nodes):
22165 - Tag every guard node in our state file with the version that
22166 we believe added it, or with our own version if we add it. This way,
22167 if a user temporarily runs an old version of Tor and then switches
22168 back to a new one, she doesn't automatically lose her guards.
22170 o Minor features (speed):
22171 - When implementing AES counter mode, update only the portions of the
22172 counter buffer that need to change, and don't keep separate
22173 network-order and host-order counters when they are the same (i.e.,
22174 on big-endian hosts.)
22176 o Minor features (controller):
22177 - Accept LF instead of CRLF on controller, since some software has a
22178 hard time generating real Internet newlines.
22179 - Add GETINFO values for the server status events
22180 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
22183 o Removed features:
22184 - Routers no longer include bandwidth-history lines in their
22185 descriptors; this information is already available in extra-info
22186 documents, and including it in router descriptors took up 60%
22187 (!) of compressed router descriptor downloads. Completes
22188 implementation of proposal 104.
22189 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
22190 and TorControl.py, as they use the old v0 controller protocol,
22191 and are obsoleted by TorFlow anyway.
22192 - Drop support for v1 rendezvous descriptors, since we never used
22193 them anyway, and the code has probably rotted by now. Based on
22194 patch from Karsten Loesing.
22195 - On OSX, stop warning the user that kqueue support in libevent is
22196 "experimental", since it seems to have worked fine for ages.
22199 - When generating information telling us how to extend to a given
22200 router, do not try to include the nickname if it is absent. Fixes
22201 bug 467. Bugfix on 0.2.0.3-alpha.
22202 - Fix a user-triggerable (but not remotely-triggerable) segfault
22203 in expand_filename(). Bugfix on 0.1.2.x.
22204 - Fix a memory leak when freeing incomplete requests from DNSPort.
22205 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
22206 - Don't try to access (or alter) the state file when running
22207 --list-fingerprint or --verify-config or --hash-password. (Resolves
22208 bug 499.) Bugfix on 0.1.2.x.
22209 - Servers used to decline to publish their DirPort if their
22210 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
22211 were below a threshold. Now they only look at BandwidthRate and
22212 RelayBandwidthRate. Bugfix on 0.1.2.x.
22213 - Remove an optimization in the AES counter-mode code that assumed
22214 that the counter never exceeded 2^68. When the counter can be set
22215 arbitrarily as an IV (as it is by Karsten's new hidden services
22216 code), this assumption no longer holds. Bugfix on 0.1.2.x.
22217 - Resume listing "AUTHORITY" flag for authorities in network status.
22218 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
22220 o Code simplifications and refactoring:
22221 - Revamp file-writing logic so we don't need to have the entire
22222 contents of a file in memory at once before we write to disk. Tor,
22224 - Turn "descriptor store" into a full-fledged type.
22225 - Move all NT services code into a separate source file.
22226 - Unify all code that computes medians, percentile elements, etc.
22227 - Get rid of a needless malloc when parsing address policies.
22230 Changes in version 0.1.2.17 - 2007-08-30
22231 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
22232 X bundles. Vidalia 0.0.14 makes authentication required for the
22233 ControlPort in the default configuration, which addresses important
22234 security risks. Everybody who uses Vidalia (or another controller)
22237 In addition, this Tor update fixes major load balancing problems with
22238 path selection, which should speed things up a lot once many people
22241 o Major bugfixes (security):
22242 - We removed support for the old (v0) control protocol. It has been
22243 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
22244 become more of a headache than it's worth.
22246 o Major bugfixes (load balancing):
22247 - When choosing nodes for non-guard positions, weight guards
22248 proportionally less, since they already have enough load. Patch
22250 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
22251 will allow fast Tor servers to get more attention.
22252 - When we're upgrading from an old Tor version, forget our current
22253 guards and pick new ones according to the new weightings. These
22254 three load balancing patches could raise effective network capacity
22255 by a factor of four. Thanks to Mike Perry for measurements.
22257 o Major bugfixes (stream expiration):
22258 - Expire not-yet-successful application streams in all cases if
22259 they've been around longer than SocksTimeout. Right now there are
22260 some cases where the stream will live forever, demanding a new
22261 circuit every 15 seconds. Fixes bug 454; reported by lodger.
22263 o Minor features (controller):
22264 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
22265 is valid before any authentication has been received. It tells
22266 a controller what kind of authentication is expected, and what
22267 protocol is spoken. Implements proposal 119.
22269 o Minor bugfixes (performance):
22270 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
22271 greatly speeding up loading cached-routers from disk on startup.
22272 - Disable sentinel-based debugging for buffer code: we squashed all
22273 the bugs that this was supposed to detect a long time ago, and now
22274 its only effect is to change our buffer sizes from nice powers of
22275 two (which platform mallocs tend to like) to values slightly over
22276 powers of two (which make some platform mallocs sad).
22278 o Minor bugfixes (misc):
22279 - If exit bandwidth ever exceeds one third of total bandwidth, then
22280 use the correct formula to weight exit nodes when choosing paths.
22281 Based on patch from Mike Perry.
22282 - Choose perfectly fairly among routers when choosing by bandwidth and
22283 weighting by fraction of bandwidth provided by exits. Previously, we
22284 would choose with only approximate fairness, and correct ourselves
22285 if we ran off the end of the list.
22286 - If we require CookieAuthentication but we fail to write the
22287 cookie file, we would warn but not exit, and end up in a state
22288 where no controller could authenticate. Now we exit.
22289 - If we require CookieAuthentication, stop generating a new cookie
22290 every time we change any piece of our config.
22291 - Refuse to start with certain directory authority keys, and
22292 encourage people using them to stop.
22293 - Terminate multi-line control events properly. Original patch
22295 - Fix a minor memory leak when we fail to find enough suitable
22296 servers to choose a circuit.
22297 - Stop leaking part of the descriptor when we run into a particularly
22298 unparseable piece of it.
22301 Changes in version 0.2.0.6-alpha - 2007-08-26
22302 This sixth development snapshot features a new Vidalia version in the
22303 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
22304 the ControlPort in the default configuration, which addresses important
22307 In addition, this snapshot fixes major load balancing problems
22308 with path selection, which should speed things up a lot once many
22309 people have upgraded. The directory authorities also use a new
22310 mean-time-between-failure approach to tracking which servers are stable,
22311 rather than just looking at the most recent uptime.
22313 o New directory authorities:
22314 - Set up Tonga as the default bridge directory authority.
22317 - Directory authorities now track servers by weighted
22318 mean-times-between-failures. When we have 4 or more days of data,
22319 use measured MTBF rather than declared uptime to decide whether
22320 to call a router Stable. Implements proposal 108.
22322 o Major bugfixes (load balancing):
22323 - When choosing nodes for non-guard positions, weight guards
22324 proportionally less, since they already have enough load. Patch
22326 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
22327 will allow fast Tor servers to get more attention.
22328 - When we're upgrading from an old Tor version, forget our current
22329 guards and pick new ones according to the new weightings. These
22330 three load balancing patches could raise effective network capacity
22331 by a factor of four. Thanks to Mike Perry for measurements.
22333 o Major bugfixes (descriptor parsing):
22334 - Handle unexpected whitespace better in malformed descriptors. Bug
22335 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
22338 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
22339 GETINFO for Torstat to use until it can switch to using extrainfos.
22340 - Optionally (if built with -DEXPORTMALLINFO) export the output
22341 of mallinfo via http, as tor/mallinfo.txt. Only accessible
22345 - Do not intermix bridge routers with controller-added
22346 routers. (Bugfix on 0.2.0.x)
22347 - Do not fail with an assert when accept() returns an unexpected
22348 address family. Addresses but does not wholly fix bug 483. (Bugfix
22350 - Let directory authorities startup even when they can't generate
22351 a descriptor immediately, e.g. because they don't know their
22353 - Stop putting the authentication cookie in a file called "0"
22354 in your working directory if you don't specify anything for the
22355 new CookieAuthFile option. Reported by Matt Edman.
22356 - Make it possible to read the PROTOCOLINFO response in a way that
22357 conforms to our control-spec. Reported by Matt Edman.
22358 - Fix a minor memory leak when we fail to find enough suitable
22359 servers to choose a circuit. Bugfix on 0.1.2.x.
22360 - Stop leaking part of the descriptor when we run into a particularly
22361 unparseable piece of it. Bugfix on 0.1.2.x.
22362 - Unmap the extrainfo cache file on exit.
22365 Changes in version 0.2.0.5-alpha - 2007-08-19
22366 This fifth development snapshot fixes compilation on Windows again;
22367 fixes an obnoxious client-side bug that slowed things down and put
22368 extra load on the network; gets us closer to using the v3 directory
22369 voting scheme; makes it easier for Tor controllers to use cookie-based
22370 authentication; and fixes a variety of other bugs.
22372 o Removed features:
22373 - Version 1 directories are no longer generated in full. Instead,
22374 authorities generate and serve "stub" v1 directories that list
22375 no servers. This will stop Tor versions 0.1.0.x and earlier from
22376 working, but (for security reasons) nobody should be running those
22379 o Major bugfixes (compilation, 0.2.0.x):
22380 - Try to fix Win32 compilation again: improve checking for IPv6 types.
22381 - Try to fix MSVC compilation: build correctly on platforms that do
22382 not define s6_addr16 or s6_addr32.
22383 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
22386 o Major bugfixes (stream expiration):
22387 - Expire not-yet-successful application streams in all cases if
22388 they've been around longer than SocksTimeout. Right now there are
22389 some cases where the stream will live forever, demanding a new
22390 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
22391 reported by lodger.
22393 o Minor features (directory servers):
22394 - When somebody requests a list of statuses or servers, and we have
22395 none of those, return a 404 rather than an empty 200.
22397 o Minor features (directory voting):
22398 - Store v3 consensus status consensuses on disk, and reload them
22401 o Minor features (security):
22402 - Warn about unsafe ControlPort configurations.
22403 - Refuse to start with certain directory authority keys, and
22404 encourage people using them to stop.
22406 o Minor features (controller):
22407 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
22408 is valid before any authentication has been received. It tells
22409 a controller what kind of authentication is expected, and what
22410 protocol is spoken. Implements proposal 119.
22411 - New config option CookieAuthFile to choose a new location for the
22412 cookie authentication file, and config option
22413 CookieAuthFileGroupReadable to make it group-readable.
22415 o Minor features (unit testing):
22416 - Add command-line arguments to unit-test executable so that we can
22417 invoke any chosen test from the command line rather than having
22418 to run the whole test suite at once; and so that we can turn on
22419 logging for the unit tests.
22421 o Minor bugfixes (on 0.1.2.x):
22422 - If we require CookieAuthentication but we fail to write the
22423 cookie file, we would warn but not exit, and end up in a state
22424 where no controller could authenticate. Now we exit.
22425 - If we require CookieAuthentication, stop generating a new cookie
22426 every time we change any piece of our config.
22427 - When loading bandwidth history, do not believe any information in
22428 the future. Fixes bug 434.
22429 - When loading entry guard information, do not believe any information
22431 - When we have our clock set far in the future and generate an
22432 onion key, then re-set our clock to be correct, we should not stop
22433 the onion key from getting rotated.
22434 - Clean up torrc sample config file.
22435 - Do not automatically run configure from autogen.sh. This
22436 non-standard behavior tended to annoy people who have built other
22439 o Minor bugfixes (on 0.2.0.x):
22440 - Fix a bug with AutomapHostsOnResolve that would always cause
22441 the second request to fail. Bug reported by Kate. Bugfix on
22443 - Fix a bug in ADDRMAP controller replies that would sometimes
22444 try to print a NULL. Patch from tup.
22445 - Read v3 directory authority keys from the right location.
22446 - Numerous bugfixes to directory voting code.
22449 Changes in version 0.1.2.16 - 2007-08-01
22450 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
22451 remote attacker in certain situations to rewrite the user's torrc
22452 configuration file. This can completely compromise anonymity of users
22453 in most configurations, including those running the Vidalia bundles,
22454 TorK, etc. Or worse.
22456 o Major security fixes:
22457 - Close immediately after missing authentication on control port;
22458 do not allow multiple authentication attempts.
22461 Changes in version 0.2.0.4-alpha - 2007-08-01
22462 This fourth development snapshot fixes a critical security vulnerability
22463 for most users, specifically those running Vidalia, TorK, etc. Everybody
22464 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
22466 o Major security fixes:
22467 - Close immediately after missing authentication on control port;
22468 do not allow multiple authentication attempts.
22470 o Major bugfixes (compilation):
22471 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
22474 o Minor features (performance):
22475 - Be even more aggressive about releasing RAM from small
22476 empty buffers. Thanks to our free-list code, this shouldn't be too
22477 performance-intensive.
22478 - Disable sentinel-based debugging for buffer code: we squashed all
22479 the bugs that this was supposed to detect a long time ago, and
22480 now its only effect is to change our buffer sizes from nice
22481 powers of two (which platform mallocs tend to like) to values
22482 slightly over powers of two (which make some platform mallocs sad).
22483 - Log malloc statistics from mallinfo() on platforms where it
22487 Changes in version 0.2.0.3-alpha - 2007-07-29
22488 This third development snapshot introduces new experimental
22489 blocking-resistance features and a preliminary version of the v3
22490 directory voting design, and includes many other smaller features
22494 - The first pieces of our "bridge" design for blocking-resistance
22495 are implemented. People can run bridge directory authorities;
22496 people can run bridges; and people can configure their Tor clients
22497 with a set of bridges to use as the first hop into the Tor network.
22498 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
22500 - Create listener connections before we setuid to the configured
22501 User and Group. Now non-Windows users can choose port values
22502 under 1024, start Tor as root, and have Tor bind those ports
22503 before it changes to another UID. (Windows users could already
22505 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
22506 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
22507 on "vserver" accounts. (Patch from coderman.)
22508 - Be even more aggressive about separating local traffic from relayed
22509 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
22511 o Major features (experimental):
22512 - First cut of code for "v3 dir voting": directory authorities will
22513 vote on a common network status document rather than each publishing
22514 their own opinion. This code needs more testing and more corner-case
22515 handling before it's ready for use.
22518 - Directory authorities now call routers Fast if their bandwidth is
22519 at least 100KB/s, and consider their bandwidth adequate to be a
22520 Guard if it is at least 250KB/s, no matter the medians. This fix
22521 complements proposal 107. [Bugfix on 0.1.2.x]
22522 - Directory authorities now never mark more than 3 servers per IP as
22523 Valid and Running. (Implements proposal 109, by Kevin Bauer and
22525 - Minor change to organizationName and commonName generation
22526 procedures in TLS certificates during Tor handshakes, to invalidate
22527 some earlier censorware approaches. This is not a long-term
22528 solution, but applying it will give us a bit of time to look into
22529 the epidemiology of countermeasures as they spread.
22531 o Major bugfixes (directory):
22532 - Rewrite directory tokenization code to never run off the end of
22533 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
22535 o Minor features (controller):
22536 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
22537 match requests to applications. (Patch from Robert Hogan.)
22538 - Report address and port correctly on connections to DNSPort. (Patch
22539 from Robert Hogan.)
22540 - Add a RESOLVE command to launch hostname lookups. (Original patch
22541 from Robert Hogan.)
22542 - Add GETINFO status/enough-dir-info to let controllers tell whether
22543 Tor has downloaded sufficient directory information. (Patch
22545 - You can now use the ControlSocket option to tell Tor to listen for
22546 controller connections on Unix domain sockets on systems that
22547 support them. (Patch from Peter Palfrader.)
22548 - STREAM NEW events are generated for DNSPort requests and for
22549 tunneled directory connections. (Patch from Robert Hogan.)
22550 - New "GETINFO address-mappings/*" command to get address mappings
22551 with expiry information. "addr-mappings/*" is now deprecated.
22554 o Minor features (misc):
22555 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
22557 - The tor-gencert tool for v3 directory authorities now creates all
22558 files as readable to the file creator only, and write-protects
22559 the authority identity key.
22560 - When dumping memory usage, list bytes used in buffer memory
22562 - When running with dmalloc, dump more stats on hup and on exit.
22563 - Directory authorities now fail quickly and (relatively) harmlessly
22564 if they generate a network status document that is somehow
22567 o Traffic load balancing improvements:
22568 - If exit bandwidth ever exceeds one third of total bandwidth, then
22569 use the correct formula to weight exit nodes when choosing paths.
22570 (Based on patch from Mike Perry.)
22571 - Choose perfectly fairly among routers when choosing by bandwidth and
22572 weighting by fraction of bandwidth provided by exits. Previously, we
22573 would choose with only approximate fairness, and correct ourselves
22574 if we ran off the end of the list. [Bugfix on 0.1.2.x]
22576 o Performance improvements:
22577 - Be more aggressive with freeing buffer RAM or putting it on the
22579 - Use Critical Sections rather than Mutexes for synchronizing threads
22580 on win32; Mutexes are heavier-weight, and designed for synchronizing
22583 o Deprecated and removed features:
22584 - RedirectExits is now deprecated.
22585 - Stop allowing address masks that do not correspond to bit prefixes.
22586 We have warned about these for a really long time; now it's time
22587 to reject them. (Patch from croup.)
22589 o Minor bugfixes (directory):
22590 - Fix another crash bug related to extra-info caching. (Bug found by
22591 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
22592 - Directories no longer return a "304 not modified" when they don't
22593 have the networkstatus the client asked for. Also fix a memory
22594 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
22595 - We had accidentally labelled 0.1.2.x directory servers as not
22596 suitable for begin_dir requests, and had labelled no directory
22597 servers as suitable for uploading extra-info documents. [Bugfix
22600 o Minor bugfixes (dns):
22601 - Fix a crash when DNSPort is set more than once. (Patch from Robert
22602 Hogan.) [Bugfix on 0.2.0.2-alpha]
22603 - Add DNSPort connections to the global connection list, so that we
22604 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
22606 - Fix a dangling reference that could lead to a crash when DNSPort is
22607 changed or closed (Patch from Robert Hogan.) [Bugfix on
22610 o Minor bugfixes (controller):
22611 - Provide DNS expiry times in GMT, not in local time. For backward
22612 compatibility, ADDRMAP events only provide GMT expiry in an extended
22613 field. "GETINFO address-mappings" always does the right thing.
22614 - Use CRLF line endings properly in NS events.
22615 - Terminate multi-line control events properly. (Original patch
22616 from tup.) [Bugfix on 0.1.2.x-alpha]
22617 - Do not include spaces in SOURCE_ADDR fields in STREAM
22618 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
22621 Changes in version 0.1.2.15 - 2007-07-17
22622 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
22623 problems, fixes compilation on BSD, and fixes a variety of other
22624 bugs. Everybody should upgrade.
22626 o Major bugfixes (compilation):
22627 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
22629 o Major bugfixes (crashes):
22630 - Try even harder not to dereference the first character after
22631 an mmap(). Reported by lodger.
22632 - Fix a crash bug in directory authorities when we re-number the
22633 routerlist while inserting a new router.
22634 - When the cached-routers file is an even multiple of the page size,
22635 don't run off the end and crash. (Fixes bug 455; based on idea
22637 - Fix eventdns.c behavior on Solaris: It is critical to include
22638 orconfig.h _before_ sys/types.h, so that we can get the expected
22639 definition of _FILE_OFFSET_BITS.
22641 o Major bugfixes (security):
22642 - Fix a possible buffer overrun when using BSD natd support. Bug
22644 - When sending destroy cells from a circuit's origin, don't include
22645 the reason for tearing down the circuit. The spec says we didn't,
22646 and now we actually don't. Reported by lodger.
22647 - Keep streamids from different exits on a circuit separate. This
22648 bug may have allowed other routers on a given circuit to inject
22649 cells into streams. Reported by lodger; fixes bug 446.
22650 - If there's a never-before-connected-to guard node in our list,
22651 never choose any guards past it. This way we don't expand our
22652 guard list unless we need to.
22654 o Minor bugfixes (guard nodes):
22655 - Weight guard selection by bandwidth, so that low-bandwidth nodes
22656 don't get overused as guards.
22658 o Minor bugfixes (directory):
22659 - Correctly count the number of authorities that recommend each
22660 version. Previously, we were under-counting by 1.
22661 - Fix a potential crash bug when we load many server descriptors at
22662 once and some of them make others of them obsolete. Fixes bug 458.
22664 o Minor bugfixes (hidden services):
22665 - Stop tearing down the whole circuit when the user asks for a
22666 connection to a port that the hidden service didn't configure.
22669 o Minor bugfixes (misc):
22670 - On Windows, we were preventing other processes from reading
22671 cached-routers while Tor was running. Reported by janbar.
22672 - Fix a possible (but very unlikely) bug in picking routers by
22673 bandwidth. Add a log message to confirm that it is in fact
22674 unlikely. Patch from lodger.
22675 - Backport a couple of memory leak fixes.
22676 - Backport miscellaneous cosmetic bugfixes.
22679 Changes in version 0.2.0.2-alpha - 2007-06-02
22680 o Major bugfixes on 0.2.0.1-alpha:
22681 - Fix an assertion failure related to servers without extra-info digests.
22682 Resolves bugs 441 and 442.
22684 o Minor features (directory):
22685 - Support "If-Modified-Since" when answering HTTP requests for
22686 directories, running-routers documents, and network-status documents.
22687 (There's no need to support it for router descriptors, since those
22688 are downloaded by descriptor digest.)
22690 o Minor build issues:
22691 - Clear up some MIPSPro compiler warnings.
22692 - When building from a tarball on a machine that happens to have SVK
22693 installed, report the micro-revision as whatever version existed
22694 in the tarball, not as "x".
22697 Changes in version 0.2.0.1-alpha - 2007-06-01
22698 This early development snapshot provides new features for people running
22699 Tor as both a client and a server (check out the new RelayBandwidth
22700 config options); lets Tor run as a DNS proxy; and generally moves us
22701 forward on a lot of fronts.
22703 o Major features, server usability:
22704 - New config options RelayBandwidthRate and RelayBandwidthBurst:
22705 a separate set of token buckets for relayed traffic. Right now
22706 relayed traffic is defined as answers to directory requests, and
22707 OR connections that don't have any local circuits on them.
22709 o Major features, client usability:
22710 - A client-side DNS proxy feature to replace the need for
22711 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
22712 for DNS requests on port 9999, use the Tor network to resolve them
22713 anonymously, and send the reply back like a regular DNS server.
22714 The code still only implements a subset of DNS.
22715 - Make PreferTunneledDirConns and TunnelDirConns work even when
22716 we have no cached directory info. This means Tor clients can now
22717 do all of their connections protected by TLS.
22719 o Major features, performance and efficiency:
22720 - Directory authorities accept and serve "extra info" documents for
22721 routers. These documents contain fields from router descriptors
22722 that aren't usually needed, and that use a lot of excess
22723 bandwidth. Once these fields are removed from router descriptors,
22724 the bandwidth savings should be about 60%. [Partially implements
22726 - Servers upload extra-info documents to any authority that accepts
22727 them. Authorities (and caches that have been configured to download
22728 extra-info documents) download them as needed. [Partially implements
22730 - Change the way that Tor buffers data that it is waiting to write.
22731 Instead of queueing data cells in an enormous ring buffer for each
22732 client->OR or OR->OR connection, we now queue cells on a separate
22733 queue for each circuit. This lets us use less slack memory, and
22734 will eventually let us be smarter about prioritizing different kinds
22736 - Use memory pools to allocate cells with better speed and memory
22737 efficiency, especially on platforms where malloc() is inefficient.
22738 - Stop reading on edge connections when their corresponding circuit
22739 buffers are full; start again as the circuits empty out.
22741 o Major features, other:
22742 - Add an HSAuthorityRecordStats option that hidden service authorities
22743 can use to track statistics of overall hidden service usage without
22744 logging information that would be very useful to an attacker.
22745 - Start work implementing multi-level keys for directory authorities:
22746 Add a standalone tool to generate key certificates. (Proposal 103.)
22749 - Directory authorities now call routers Stable if they have an
22750 uptime of at least 30 days, even if that's not the median uptime
22751 in the network. Implements proposal 107, suggested by Kevin Bauer
22754 o Minor fixes (resource management):
22755 - Count the number of open sockets separately from the number
22756 of active connection_t objects. This will let us avoid underusing
22757 our allocated connection limit.
22758 - We no longer use socket pairs to link an edge connection to an
22759 anonymous directory connection or a DirPort test connection.
22760 Instead, we track the link internally and transfer the data
22761 in-process. This saves two sockets per "linked" connection (at the
22762 client and at the server), and avoids the nasty Windows socketpair()
22764 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
22765 for every single inactive connection_t. Free items from the
22766 4k/16k-buffer free lists when they haven't been used for a while.
22768 o Minor features (build):
22769 - Make autoconf search for libevent, openssl, and zlib consistently.
22770 - Update deprecated macros in configure.in.
22771 - When warning about missing headers, tell the user to let us
22772 know if the compile succeeds anyway, so we can downgrade the
22774 - Include the current subversion revision as part of the version
22775 string: either fetch it directly if we're in an SVN checkout, do
22776 some magic to guess it if we're in an SVK checkout, or use
22777 the last-detected version if we're building from a .tar.gz.
22778 Use this version consistently in log messages.
22780 o Minor features (logging):
22781 - Always prepend "Bug: " to any log message about a bug.
22782 - Put a platform string (e.g. "Linux i686") in the startup log
22783 message, so when people paste just their logs, we know if it's
22784 OpenBSD or Windows or what.
22785 - When logging memory usage, break down memory used in buffers by
22788 o Minor features (directory system):
22789 - New config option V2AuthoritativeDirectory that all directory
22790 authorities should set. This will let future authorities choose
22791 not to serve V2 directory information.
22792 - Directory authorities allow multiple router descriptors and/or extra
22793 info documents to be uploaded in a single go. This will make
22794 implementing proposal 104 simpler.
22796 o Minor features (controller):
22797 - Add a new config option __DisablePredictedCircuits designed for
22798 use by the controller, when we don't want Tor to build any circuits
22800 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
22801 so we can exit from the middle of the circuit.
22802 - Implement "getinfo status/circuit-established".
22803 - Implement "getinfo status/version/..." so a controller can tell
22804 whether the current version is recommended, and whether any versions
22805 are good, and how many authorities agree. (Patch from shibz.)
22807 o Minor features (hidden services):
22808 - Allow multiple HiddenServicePort directives with the same virtual
22809 port; when they occur, the user is sent round-robin to one
22810 of the target ports chosen at random. Partially fixes bug 393 by
22811 adding limited ad-hoc round-robining.
22813 o Minor features (other):
22815 - Add a new AutomapHostsOnResolve option: when it is enabled, any
22816 resolve request for hosts matching a given pattern causes Tor to
22817 generate an internal virtual address mapping for that host. This
22818 allows DNSPort to work sensibly with hidden service users. By
22819 default, .exit and .onion addresses are remapped; the list of
22820 patterns can be reconfigured with AutomapHostsSuffixes.
22821 - Add an "-F" option to tor-resolve to force a resolve for a .onion
22822 address. Thanks to the AutomapHostsOnResolve option, this is no
22823 longer a completely silly thing to do.
22824 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
22825 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
22826 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
22827 minus 1 byte: the actual maximum declared bandwidth.
22829 o Removed features:
22830 - Removed support for the old binary "version 0" controller protocol.
22831 This has been deprecated since 0.1.1, and warnings have been issued
22832 since 0.1.2. When we encounter a v0 control message, we now send
22833 back an error and close the connection.
22834 - Remove the old "dns worker" server DNS code: it hasn't been default
22835 since 0.1.2.2-alpha, and all the servers seem to be using the new
22838 o Minor bugfixes (portability):
22839 - Even though Windows is equally happy with / and \ as path separators,
22840 try to use \ consistently on Windows and / consistently on Unix: it
22841 makes the log messages nicer.
22842 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
22843 - Read resolv.conf files correctly on platforms where read() returns
22844 partial results on small file reads.
22846 o Minor bugfixes (directory):
22847 - Correctly enforce that elements of directory objects do not appear
22848 more often than they are allowed to appear.
22849 - When we are reporting the DirServer line we just parsed, we were
22850 logging the second stanza of the key fingerprint, not the first.
22852 o Minor bugfixes (logging):
22853 - When we hit an EOF on a log (probably because we're shutting down),
22854 don't try to remove the log from the list: just mark it as
22855 unusable. (Bulletproofs against bug 222.)
22857 o Minor bugfixes (other):
22858 - In the exitlist script, only consider the most recently published
22859 server descriptor for each server. Also, when the user requests
22860 a list of servers that _reject_ connections to a given address,
22861 explicitly exclude the IPs that also have servers that accept
22862 connections to that address. (Resolves bug 405.)
22863 - Stop allowing hibernating servers to be "stable" or "fast".
22864 - On Windows, we were preventing other processes from reading
22865 cached-routers while Tor was running. (Reported by janbar)
22866 - Make the NodeFamilies config option work. (Reported by
22867 lodger -- it has never actually worked, even though we added it
22869 - Check return values from pthread_mutex functions.
22870 - Don't save non-general-purpose router descriptors to the disk cache,
22871 because we have no way of remembering what their purpose was when
22873 - Add even more asserts to hunt down bug 417.
22874 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
22875 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
22876 Add a log message to confirm that it is in fact unlikely.
22878 o Minor bugfixes (controller):
22879 - Make 'getinfo fingerprint' return a 551 error if we're not a
22880 server, so we match what the control spec claims we do. Reported
22882 - Fix a typo in an error message when extendcircuit fails that
22883 caused us to not follow the \r\n-based delimiter protocol. Reported
22886 o Code simplifications and refactoring:
22887 - Stop passing around circuit_t and crypt_path_t pointers that are
22888 implicit in other procedure arguments.
22889 - Drop the old code to choke directory connections when the
22890 corresponding OR connections got full: thanks to the cell queue
22891 feature, OR conns don't get full any more.
22892 - Make dns_resolve() handle attaching connections to circuits
22893 properly, so the caller doesn't have to.
22894 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
22895 - Keep the connection array as a dynamic smartlist_t, rather than as
22896 a fixed-sized array. This is important, as the number of connections
22897 is becoming increasingly decoupled from the number of sockets.
22900 Changes in version 0.1.2.14 - 2007-05-25
22901 Tor 0.1.2.14 changes the addresses of two directory authorities (this
22902 change especially affects those who serve or use hidden services),
22903 and fixes several other crash- and security-related bugs.
22905 o Directory authority changes:
22906 - Two directory authorities (moria1 and moria2) just moved to new
22907 IP addresses. This change will particularly affect those who serve
22908 or use hidden services.
22910 o Major bugfixes (crashes):
22911 - If a directory server runs out of space in the connection table
22912 as it's processing a begin_dir request, it will free the exit stream
22913 but leave it attached to the circuit, leading to unpredictable
22914 behavior. (Reported by seeess, fixes bug 425.)
22915 - Fix a bug in dirserv_remove_invalid() that would cause authorities
22916 to corrupt memory under some really unlikely scenarios.
22917 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
22918 - Avoid segfaults when reading from mmaped descriptor file. (Reported
22921 o Major bugfixes (security):
22922 - When choosing an entry guard for a circuit, avoid using guards
22923 that are in the same family as the chosen exit -- not just guards
22924 that are exactly the chosen exit. (Reported by lodger.)
22926 o Major bugfixes (resource management):
22927 - If a directory authority is down, skip it when deciding where to get
22928 networkstatus objects or descriptors. Otherwise we keep asking
22929 every 10 seconds forever. Fixes bug 384.
22930 - Count it as a failure if we fetch a valid network-status but we
22931 don't want to keep it. Otherwise we'll keep fetching it and keep
22932 not wanting to keep it. Fixes part of bug 422.
22933 - If all of our dirservers have given us bad or no networkstatuses
22934 lately, then stop hammering them once per minute even when we
22935 think they're failed. Fixes another part of bug 422.
22938 - Actually set the purpose correctly for descriptors inserted with
22939 purpose=controller.
22940 - When we have k non-v2 authorities in our DirServer config,
22941 we ignored the last k authorities in the list when updating our
22943 - Correctly back-off from requesting router descriptors that we are
22944 having a hard time downloading.
22945 - Read resolv.conf files correctly on platforms where read() returns
22946 partial results on small file reads.
22947 - Don't rebuild the entire router store every time we get 32K of
22948 routers: rebuild it when the journal gets very large, or when
22949 the gaps in the store get very large.
22952 - When routers publish SVN revisions in their router descriptors,
22953 authorities now include those versions correctly in networkstatus
22955 - Warn when using a version of libevent before 1.3b to run a server on
22956 OSX or BSD: these versions interact badly with userspace threads.
22959 Changes in version 0.1.2.13 - 2007-04-24
22960 This release features some major anonymity fixes, such as safer path
22961 selection; better client performance; faster bootstrapping, better
22962 address detection, and better DNS support for servers; write limiting as
22963 well as read limiting to make servers easier to run; and a huge pile of
22964 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
22966 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
22967 of the Freenode IRC network, remembering his patience and vision for
22968 free speech on the Internet.
22971 - Fix a memory leak when we ask for "all" networkstatuses and we
22972 get one we don't recognize.
22973 - Add more asserts to hunt down bug 417.
22974 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
22977 Changes in version 0.1.2.12-rc - 2007-03-16
22979 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
22980 directory information requested inside Tor connections (i.e. via
22981 begin_dir cells). It only triggered when the same connection was
22982 serving other data at the same time. Reported by seeess.
22985 - When creating a circuit via the controller, send a 'launched'
22986 event when we're done, so we follow the spec better.
22989 Changes in version 0.1.2.11-rc - 2007-03-15
22990 o Minor bugfixes (controller), reported by daejees:
22991 - Correct the control spec to match how the code actually responds
22992 to 'getinfo addr-mappings/*'.
22993 - The control spec described a GUARDS event, but the code
22994 implemented a GUARD event. Standardize on GUARD, but let people
22995 ask for GUARDS too.
22998 Changes in version 0.1.2.10-rc - 2007-03-07
22999 o Major bugfixes (Windows):
23000 - Do not load the NT services library functions (which may not exist)
23001 just to detect if we're a service trying to shut down. Now we run
23002 on Win98 and friends again.
23004 o Minor bugfixes (other):
23005 - Clarify a couple of log messages.
23006 - Fix a misleading socks5 error number.
23009 Changes in version 0.1.2.9-rc - 2007-03-02
23010 o Major bugfixes (Windows):
23011 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
23012 of the usual GCC "%llu". This prevents a bug when saving 64-bit
23013 int configuration values: the high-order 32 bits would get
23014 truncated. In particular, we were being bitten by the default
23015 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
23016 and maybe also bug 397.)
23018 o Minor bugfixes (performance):
23019 - Use OpenSSL's AES implementation on platforms where it's faster.
23020 This could save us as much as 10% CPU usage.
23022 o Minor bugfixes (server):
23023 - Do not rotate onion key immediately after setting it for the first
23026 o Minor bugfixes (directory authorities):
23027 - Stop calling servers that have been hibernating for a long time
23028 "stable". Also, stop letting hibernating or obsolete servers affect
23029 uptime and bandwidth cutoffs.
23030 - Stop listing hibernating servers in the v1 directory.
23032 o Minor bugfixes (hidden services):
23033 - Upload hidden service descriptors slightly less often, to reduce
23034 load on authorities.
23036 o Minor bugfixes (other):
23037 - Fix an assert that could trigger if a controller quickly set then
23038 cleared EntryNodes. Bug found by Udo van den Heuvel.
23039 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
23041 - Fix a potential race condition in the rpm installer. Found by
23043 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
23044 of 2 as indicating that the server is completely bad; it sometimes
23045 means that the server is just bad for the request in question. (may fix
23046 the last of bug 326.)
23047 - Disable encrypted directory connections when we don't have a server
23048 descriptor for the destination. We'll get this working again in
23052 Changes in version 0.1.2.8-beta - 2007-02-26
23053 o Major bugfixes (crashes):
23054 - Stop crashing when the controller asks us to resetconf more than
23055 one config option at once. (Vidalia 0.0.11 does this.)
23056 - Fix a crash that happened on Win98 when we're given command-line
23057 arguments: don't try to load NT service functions from advapi32.dll
23058 except when we need them. (Bug introduced in 0.1.2.7-alpha;
23060 - Fix a longstanding obscure crash bug that could occur when
23061 we run out of DNS worker processes. (Resolves bug 390.)
23063 o Major bugfixes (hidden services):
23064 - Correctly detect whether hidden service descriptor downloads are
23065 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
23067 o Major bugfixes (accounting):
23068 - When we start during an accounting interval before it's time to wake
23069 up, remember to wake up at the correct time. (May fix bug 342.)
23071 o Minor bugfixes (controller):
23072 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
23073 clear the corresponding on_circuit variable, and remember later
23074 that we don't need to send a redundant CLOSED event. Resolves part
23076 - Report events where a resolve succeeded or where we got a socks
23077 protocol error correctly, rather than calling both of them
23079 - Change reported stream target addresses to IP consistently when
23080 we finally get the IP from an exit node.
23081 - Send log messages to the controller even if they happen to be very
23084 o Minor bugfixes (other):
23085 - Display correct results when reporting which versions are
23086 recommended, and how recommended they are. (Resolves bug 383.)
23087 - Improve our estimates for directory bandwidth to be less random:
23088 guess that an unrecognized directory will have the average bandwidth
23089 from all known directories, not that it will have the average
23090 bandwidth from those directories earlier than it on the list.
23091 - If we start a server with ClientOnly 1, then set ClientOnly to 0
23092 and hup, stop triggering an assert based on an empty onion_key.
23093 - On platforms with no working mmap() equivalent, don't warn the
23094 user when cached-routers doesn't exist.
23095 - Warn the user when mmap() [or its equivalent] fails for some reason
23096 other than file-not-found.
23097 - Don't warn the user when cached-routers.new doesn't exist: that's
23098 perfectly fine when starting up for the first time.
23099 - When EntryNodes are configured, rebuild the guard list to contain,
23100 in order: the EntryNodes that were guards before; the rest of the
23101 EntryNodes; the nodes that were guards before.
23102 - Mask out all signals in sub-threads; only the libevent signal
23103 handler should be processing them. This should prevent some crashes
23104 on some machines using pthreads. (Patch from coderman.)
23105 - Fix switched arguments on memset in the implementation of
23106 tor_munmap() for systems with no mmap() call.
23107 - When Tor receives a router descriptor that it asked for, but
23108 no longer wants (because it has received fresh networkstatuses
23109 in the meantime), do not warn the user. Cache the descriptor if
23110 we're a cache; drop it if we aren't.
23111 - Make earlier entry guards _really_ get retried when the network
23113 - On a malformed DNS reply, always give an error to the corresponding
23115 - Build with recent libevents on platforms that do not define the
23116 nonstandard types "u_int8_t" and friends.
23118 o Minor features (controller):
23119 - Warn the user when an application uses the obsolete binary v0
23120 control protocol. We're planning to remove support for it during
23121 the next development series, so it's good to give people some
23123 - Add STREAM_BW events to report per-entry-stream bandwidth
23124 use. (Patch from Robert Hogan.)
23125 - Rate-limit SIGNEWNYM signals in response to controllers that
23126 impolitely generate them for every single stream. (Patch from
23127 mwenge; closes bug 394.)
23128 - Make REMAP stream events have a SOURCE (cache or exit), and
23129 make them generated in every case where we get a successful
23130 connected or resolved cell.
23132 o Minor bugfixes (performance):
23133 - Call router_have_min_dir_info half as often. (This is showing up in
23134 some profiles, but not others.)
23135 - When using GCC, make log_debug never get called at all, and its
23136 arguments never get evaluated, when no debug logs are configured.
23137 (This is showing up in some profiles, but not others.)
23140 - Remove some never-implemented options. Mark PathlenCoinWeight as
23142 - Implement proposal 106: Stop requiring clients to have well-formed
23143 certificates; stop checking nicknames in certificates. (Clients
23144 have certificates so that they can look like Tor servers, but in
23145 the future we might want to allow them to look like regular TLS
23146 clients instead. Nicknames in certificates serve no purpose other
23147 than making our protocol easier to recognize on the wire.)
23148 - Revise messages on handshake failure again to be even more clear about
23149 which are incoming connections and which are outgoing.
23150 - Discard any v1 directory info that's over 1 month old (for
23151 directories) or over 1 week old (for running-routers lists).
23152 - Do not warn when individual nodes in the configuration's EntryNodes,
23153 ExitNodes, etc are down: warn only when all possible nodes
23154 are down. (Fixes bug 348.)
23155 - Always remove expired routers and networkstatus docs before checking
23156 whether we have enough information to build circuits. (Fixes
23158 - Put a lower-bound on MaxAdvertisedBandwidth.
23161 Changes in version 0.1.2.7-alpha - 2007-02-06
23162 o Major bugfixes (rate limiting):
23163 - Servers decline directory requests much more aggressively when
23164 they're low on bandwidth. Otherwise they end up queueing more and
23165 more directory responses, which can't be good for latency.
23166 - But never refuse directory requests from local addresses.
23167 - Fix a memory leak when sending a 503 response for a networkstatus
23169 - Be willing to read or write on local connections (e.g. controller
23170 connections) even when the global rate limiting buckets are empty.
23171 - If our system clock jumps back in time, don't publish a negative
23172 uptime in the descriptor. Also, don't let the global rate limiting
23173 buckets go absurdly negative.
23174 - Flush local controller connection buffers periodically as we're
23175 writing to them, so we avoid queueing 4+ megabytes of data before
23178 o Major bugfixes (NT services):
23179 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
23180 command-line flag so that admins can override the default by saying
23181 "tor --service install --user "SomeUser"". This will not affect
23182 existing installed services. Also, warn the user that the service
23183 will look for its configuration file in the service user's
23184 %appdata% directory. (We can't do the 'hardwire the user's appdata
23185 directory' trick any more, since we may not have read access to that
23188 o Major bugfixes (other):
23189 - Previously, we would cache up to 16 old networkstatus documents
23190 indefinitely, if they came from nontrusted authorities. Now we
23191 discard them if they are more than 10 days old.
23192 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
23194 - Detect and reject malformed DNS responses containing circular
23196 - If exits are rare enough that we're not marking exits as guards,
23197 ignore exit bandwidth when we're deciding the required bandwidth
23199 - When we're handling a directory connection tunneled over Tor,
23200 don't fill up internal memory buffers with all the data we want
23201 to tunnel; instead, only add it if the OR connection that will
23202 eventually receive it has some room for it. (This can lead to
23203 slowdowns in tunneled dir connections; a better solution will have
23204 to wait for 0.2.0.)
23206 o Minor bugfixes (dns):
23207 - Add some defensive programming to eventdns.c in an attempt to catch
23208 possible memory-stomping bugs.
23209 - Detect and reject DNS replies containing IPv4 or IPv6 records with
23210 an incorrect number of bytes. (Previously, we would ignore the
23212 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
23213 in the correct order, and doesn't crash.
23214 - Free memory held in recently-completed DNS lookup attempts on exit.
23215 This was not a memory leak, but may have been hiding memory leaks.
23216 - Handle TTL values correctly on reverse DNS lookups.
23217 - Treat failure to parse resolv.conf as an error.
23219 o Minor bugfixes (other):
23220 - Fix crash with "tor --list-fingerprint" (reported by seeess).
23221 - When computing clock skew from directory HTTP headers, consider what
23222 time it was when we finished asking for the directory, not what
23224 - Expire socks connections if they spend too long waiting for the
23225 handshake to finish. Previously we would let them sit around for
23226 days, if the connecting application didn't close them either.
23227 - And if the socks handshake hasn't started, don't send a
23228 "DNS resolve socks failed" handshake reply; just close it.
23229 - Stop using C functions that OpenBSD's linker doesn't like.
23230 - Don't launch requests for descriptors unless we have networkstatuses
23231 from at least half of the authorities. This delays the first
23232 download slightly under pathological circumstances, but can prevent
23233 us from downloading a bunch of descriptors we don't need.
23234 - Do not log IPs with TLS failures for incoming TLS
23235 connections. (Fixes bug 382.)
23236 - If the user asks to use invalid exit nodes, be willing to use
23238 - Stop using the reserved ac_cv namespace in our configure script.
23239 - Call stat() slightly less often; use fstat() when possible.
23240 - Refactor the way we handle pending circuits when an OR connection
23241 completes or fails, in an attempt to fix a rare crash bug.
23242 - Only rewrite a conn's address based on X-Forwarded-For: headers
23243 if it's a parseable public IP address; and stop adding extra quotes
23244 to the resulting address.
23247 - Weight directory requests by advertised bandwidth. Now we can
23248 let servers enable write limiting but still allow most clients to
23249 succeed at their directory requests. (We still ignore weights when
23250 choosing a directory authority; I hope this is a feature.)
23253 - Create a new file ReleaseNotes which was the old ChangeLog. The
23254 new ChangeLog file now includes the summaries for all development
23256 - Check for addresses with invalid characters at the exit as well
23257 as at the client, and warn less verbosely when they fail. You can
23258 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
23259 - Adapt a patch from goodell to let the contrib/exitlist script
23260 take arguments rather than require direct editing.
23261 - Inform the server operator when we decide not to advertise a
23262 DirPort due to AccountingMax enabled or a low BandwidthRate. It
23263 was confusing Zax, so now we're hopefully more helpful.
23264 - Bring us one step closer to being able to establish an encrypted
23265 directory tunnel without knowing a descriptor first. Still not
23266 ready yet. As part of the change, now assume we can use a
23267 create_fast cell if we don't know anything about a router.
23268 - Allow exit nodes to use nameservers running on ports other than 53.
23269 - Servers now cache reverse DNS replies.
23270 - Add an --ignore-missing-torrc command-line option so that we can
23271 get the "use sensible defaults if the configuration file doesn't
23272 exist" behavior even when specifying a torrc location on the command
23275 o Minor features (controller):
23276 - Track reasons for OR connection failure; make these reasons
23277 available via the controller interface. (Patch from Mike Perry.)
23278 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
23279 can learn when clients are sending malformed hostnames to Tor.
23280 - Clean up documentation for controller status events.
23281 - Add a REMAP status to stream events to note that a stream's
23282 address has changed because of a cached address or a MapAddress
23286 Changes in version 0.1.2.6-alpha - 2007-01-09
23288 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
23289 connection handles more than 4 gigs in either direction, we crash.
23290 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
23291 advertised exit node, somebody might try to exit from us when
23292 we're bootstrapping and before we've built our descriptor yet.
23293 Refuse the connection rather than crashing.
23296 - Warn if we (as a server) find that we've resolved an address that we
23297 weren't planning to resolve.
23298 - Warn that using select() on any libevent version before 1.1 will be
23299 unnecessarily slow (even for select()).
23300 - Flush ERR-level controller status events just like we currently
23301 flush ERR-level log events, so that a Tor shutdown doesn't prevent
23302 the controller from learning about current events.
23304 o Minor features (more controller status events):
23305 - Implement EXTERNAL_ADDRESS server status event so controllers can
23306 learn when our address changes.
23307 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
23308 can learn when directories reject our descriptor.
23309 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
23310 can learn when a client application is speaking a non-socks protocol
23312 - Implement DANGEROUS_SOCKS client status event so controllers
23313 can learn when a client application is leaking DNS addresses.
23314 - Implement BUG general status event so controllers can learn when
23315 Tor is unhappy about its internal invariants.
23316 - Implement CLOCK_SKEW general status event so controllers can learn
23317 when Tor thinks the system clock is set incorrectly.
23318 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
23319 server status events so controllers can learn when their descriptors
23320 are accepted by a directory.
23321 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
23322 server status events so controllers can learn about Tor's progress in
23323 deciding whether it's reachable from the outside.
23324 - Implement BAD_LIBEVENT general status event so controllers can learn
23325 when we have a version/method combination in libevent that needs to
23327 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
23328 and DNS_USELESS server status events so controllers can learn
23329 about changes to DNS server status.
23331 o Minor features (directory):
23332 - Authorities no longer recommend exits as guards if this would shift
23333 too much load to the exit nodes.
23336 Changes in version 0.1.2.5-alpha - 2007-01-06
23338 - Enable write limiting as well as read limiting. Now we sacrifice
23339 capacity if we're pushing out lots of directory traffic, rather
23340 than overrunning the user's intended bandwidth limits.
23341 - Include TLS overhead when counting bandwidth usage; previously, we
23342 would count only the bytes sent over TLS, but not the bytes used
23344 - Support running the Tor service with a torrc not in the same
23345 directory as tor.exe and default to using the torrc located in
23346 the %appdata%\Tor\ of the user who installed the service. Patch
23348 - Servers now check for the case when common DNS requests are going to
23349 wildcarded addresses (i.e. all getting the same answer), and change
23350 their exit policy to reject *:* if it's happening.
23351 - Implement BEGIN_DIR cells, so we can connect to the directory
23352 server via TLS to do encrypted directory requests rather than
23353 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
23354 config options if you like.
23356 o Minor features (config and docs):
23357 - Start using the state file to store bandwidth accounting data:
23358 the bw_accounting file is now obsolete. We'll keep generating it
23359 for a while for people who are still using 0.1.2.4-alpha.
23360 - Try to batch changes to the state file so that we do as few
23361 disk writes as possible while still storing important things in
23363 - The state file and the bw_accounting file get saved less often when
23364 the AvoidDiskWrites config option is set.
23365 - Make PIDFile work on Windows (untested).
23366 - Add internal descriptions for a bunch of configuration options:
23367 accessible via controller interface and in comments in saved
23369 - Reject *:563 (NNTPS) in the default exit policy. We already reject
23370 NNTP by default, so this seems like a sensible addition.
23371 - Clients now reject hostnames with invalid characters. This should
23372 avoid some inadvertent info leaks. Add an option
23373 AllowNonRFC953Hostnames to disable this behavior, in case somebody
23374 is running a private network with hosts called @, !, and #.
23375 - Add a maintainer script to tell us which options are missing
23376 documentation: "make check-docs".
23377 - Add a new address-spec.txt document to describe our special-case
23378 addresses: .exit, .onion, and .noconnnect.
23380 o Minor features (DNS):
23381 - Ongoing work on eventdns infrastructure: now it has dns server
23382 and ipv6 support. One day Tor will make use of it.
23383 - Add client-side caching for reverse DNS lookups.
23384 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
23385 - When we change nameservers or IP addresses, reset and re-launch
23386 our tests for DNS hijacking.
23388 o Minor features (directory):
23389 - Authorities now specify server versions in networkstatus. This adds
23390 about 2% to the size of compressed networkstatus docs, and allows
23391 clients to tell which servers support BEGIN_DIR and which don't.
23392 The implementation is forward-compatible with a proposed future
23393 protocol version scheme not tied to Tor versions.
23394 - DirServer configuration lines now have an orport= option so
23395 clients can open encrypted tunnels to the authorities without
23396 having downloaded their descriptors yet. Enabled for moria1,
23397 moria2, tor26, and lefkada now in the default configuration.
23398 - Directory servers are more willing to send a 503 "busy" if they
23399 are near their write limit, especially for v1 directory requests.
23400 Now they can use their limited bandwidth for actual Tor traffic.
23401 - Clients track responses with status 503 from dirservers. After a
23402 dirserver has given us a 503, we try not to use it until an hour has
23403 gone by, or until we have no dirservers that haven't given us a 503.
23404 - When we get a 503 from a directory, and we're not a server, we don't
23405 count the failure against the total number of failures allowed
23406 for the thing we're trying to download.
23407 - Report X-Your-Address-Is correctly from tunneled directory
23408 connections; don't report X-Your-Address-Is when it's an internal
23409 address; and never believe reported remote addresses when they're
23411 - Protect against an unlikely DoS attack on directory servers.
23412 - Add a BadDirectory flag to network status docs so that authorities
23413 can (eventually) tell clients about caches they believe to be
23416 o Minor features (controller):
23417 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
23418 - Reimplement GETINFO so that info/names stays in sync with the
23420 - Implement "GETINFO fingerprint".
23421 - Implement "SETEVENTS GUARD" so controllers can get updates on
23422 entry guard status as it changes.
23424 o Minor features (clean up obsolete pieces):
23425 - Remove some options that have been deprecated since at least
23426 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
23427 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
23428 to set log options.
23429 - We no longer look for identity and onion keys in "identity.key" and
23430 "onion.key" -- these were replaced by secret_id_key and
23431 secret_onion_key in 0.0.8pre1.
23432 - We no longer require unrecognized directory entries to be
23435 o Major bugfixes (security):
23436 - Stop sending the HttpProxyAuthenticator string to directory
23437 servers when directory connections are tunnelled through Tor.
23438 - Clients no longer store bandwidth history in the state file.
23439 - Do not log introduction points for hidden services if SafeLogging
23441 - When generating bandwidth history, round down to the nearest
23442 1k. When storing accounting data, round up to the nearest 1k.
23443 - When we're running as a server, remember when we last rotated onion
23444 keys, so that we will rotate keys once they're a week old even if
23445 we never stay up for a week ourselves.
23447 o Major bugfixes (other):
23448 - Fix a longstanding bug in eventdns that prevented the count of
23449 timed-out resolves from ever being reset. This bug caused us to
23450 give up on a nameserver the third time it timed out, and try it
23451 10 seconds later... and to give up on it every time it timed out
23453 - Take out the '5 second' timeout from the connection retry
23454 schedule. Now the first connect attempt will wait a full 10
23455 seconds before switching to a new circuit. Perhaps this will help
23456 a lot. Based on observations from Mike Perry.
23457 - Fix a bug on the Windows implementation of tor_mmap_file() that
23458 would prevent the cached-routers file from ever loading. Reported
23462 - Fix an assert failure when a directory authority sets
23463 AuthDirRejectUnlisted and then receives a descriptor from an
23464 unlisted router. Reported by seeess.
23465 - Avoid a double-free when parsing malformed DirServer lines.
23466 - Fix a bug when a BSD-style PF socket is first used. Patch from
23468 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
23469 to resolve an address at a given exit node even when they ask for
23471 - Servers no longer ever list themselves in their "family" line,
23472 even if configured to do so. This makes it easier to configure
23473 family lists conveniently.
23474 - When running as a server, don't fall back to 127.0.0.1 when no
23475 nameservers are configured in /etc/resolv.conf; instead, make the
23476 user fix resolv.conf or specify nameservers explicitly. (Resolves
23478 - Stop accepting certain malformed ports in configured exit policies.
23479 - Don't re-write the fingerprint file every restart, unless it has
23481 - Stop warning when a single nameserver fails: only warn when _all_ of
23482 our nameservers have failed. Also, when we only have one nameserver,
23483 raise the threshold for deciding that the nameserver is dead.
23484 - Directory authorities now only decide that routers are reachable
23485 if their identity keys are as expected.
23486 - When the user uses bad syntax in the Log config line, stop
23487 suggesting other bad syntax as a replacement.
23488 - Correctly detect ipv6 DNS capability on OpenBSD.
23490 o Minor bugfixes (controller):
23491 - Report the circuit number correctly in STREAM CLOSED events. Bug
23492 reported by Mike Perry.
23493 - Do not report bizarre values for results of accounting GETINFOs
23494 when the last second's write or read exceeds the allotted bandwidth.
23495 - Report "unrecognized key" rather than an empty string when the
23496 controller tries to fetch a networkstatus that doesn't exist.
23499 Changes in version 0.1.1.26 - 2006-12-14
23500 o Security bugfixes:
23501 - Stop sending the HttpProxyAuthenticator string to directory
23502 servers when directory connections are tunnelled through Tor.
23503 - Clients no longer store bandwidth history in the state file.
23504 - Do not log introduction points for hidden services if SafeLogging
23508 - Fix an assert failure when a directory authority sets
23509 AuthDirRejectUnlisted and then receives a descriptor from an
23510 unlisted router (reported by seeess).
23513 Changes in version 0.1.2.4-alpha - 2006-12-03
23515 - Add support for using natd; this allows FreeBSDs earlier than
23516 5.1.2 to have ipfw send connections through Tor without using
23517 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
23520 - Make all connections to addresses of the form ".noconnect"
23521 immediately get closed. This lets application/controller combos
23522 successfully test whether they're talking to the same Tor by
23523 watching for STREAM events.
23524 - Make cross.sh cross-compilation script work even when autogen.sh
23525 hasn't been run. (Patch from Michael Mohr.)
23526 - Statistics dumped by -USR2 now include a breakdown of public key
23527 operations, for profiling.
23530 - Fix a major leak when directory authorities parse their
23531 approved-routers list, a minor memory leak when we fail to pick
23532 an exit node, and a few rare leaks on errors.
23533 - Handle TransPort connections even when the server sends data before
23534 the client sends data. Previously, the connection would just hang
23535 until the client sent data. (Patch from tup based on patch from
23537 - Avoid assert failure when our cached-routers file is empty on
23541 - Don't log spurious warnings when we see a circuit close reason we
23542 don't recognize; it's probably just from a newer version of Tor.
23543 - Have directory authorities allow larger amounts of drift in uptime
23544 without replacing the server descriptor: previously, a server that
23545 restarted every 30 minutes could have 48 "interesting" descriptors
23547 - Start linking to the Tor specification and Tor reference manual
23548 correctly in the Windows installer.
23549 - Add Vidalia to the OS X uninstaller script, so when we uninstall
23550 Tor/Privoxy we also uninstall Vidalia.
23551 - Resume building on Irix64, and fix a lot of warnings from its
23552 MIPSpro C compiler.
23553 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
23554 when we're running as a client.
23557 Changes in version 0.1.1.25 - 2006-11-04
23559 - When a client asks us to resolve (rather than connect to)
23560 an address, and we have a cached answer, give them the cached
23561 answer. Previously, we would give them no answer at all.
23562 - We were building exactly the wrong circuits when we predict
23563 hidden service requirements, meaning Tor would have to build all
23564 its circuits on demand.
23565 - If none of our live entry guards have a high uptime, but we
23566 require a guard with a high uptime, try adding a new guard before
23567 we give up on the requirement. This patch should make long-lived
23568 connections more stable on average.
23569 - When testing reachability of our DirPort, don't launch new
23570 tests when there's already one in progress -- unreachable
23571 servers were stacking up dozens of testing streams.
23573 o Security bugfixes:
23574 - When the user sends a NEWNYM signal, clear the client-side DNS
23575 cache too. Otherwise we continue to act on previous information.
23578 - Avoid a memory corruption bug when creating a hash table for
23580 - Avoid possibility of controller-triggered crash when misusing
23581 certain commands from a v0 controller on platforms that do not
23582 handle printf("%s",NULL) gracefully.
23583 - Avoid infinite loop on unexpected controller input.
23584 - Don't log spurious warnings when we see a circuit close reason we
23585 don't recognize; it's probably just from a newer version of Tor.
23586 - Add Vidalia to the OS X uninstaller script, so when we uninstall
23587 Tor/Privoxy we also uninstall Vidalia.
23590 Changes in version 0.1.2.3-alpha - 2006-10-29
23592 - Prepare for servers to publish descriptors less often: never
23593 discard a descriptor simply for being too old until either it is
23594 recommended by no authorities, or until we get a better one for
23595 the same router. Make caches consider retaining old recommended
23596 routers for even longer.
23597 - If most authorities set a BadExit flag for a server, clients
23598 don't think of it as a general-purpose exit. Clients only consider
23599 authorities that advertise themselves as listing bad exits.
23600 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
23601 headers for content, so that we can work better in the presence of
23602 caching HTTP proxies.
23603 - Allow authorities to list nodes as bad exits by fingerprint or by
23606 o Minor features, controller:
23607 - Add a REASON field to CIRC events; for backward compatibility, this
23608 field is sent only to controllers that have enabled the extended
23609 event format. Also, add additional reason codes to explain why
23610 a given circuit has been destroyed or truncated. (Patches from
23612 - Add a REMOTE_REASON field to extended CIRC events to tell the
23613 controller about why a remote OR told us to close a circuit.
23614 - Stream events also now have REASON and REMOTE_REASON fields,
23615 working much like those for circuit events.
23616 - There's now a GETINFO ns/... field so that controllers can ask Tor
23617 about the current status of a router.
23618 - A new event type "NS" to inform a controller when our opinion of
23619 a router's status has changed.
23620 - Add a GETINFO events/names and GETINFO features/names so controllers
23621 can tell which events and features are supported.
23622 - A new CLEARDNSCACHE signal to allow controllers to clear the
23623 client-side DNS cache without expiring circuits.
23625 o Security bugfixes:
23626 - When the user sends a NEWNYM signal, clear the client-side DNS
23627 cache too. Otherwise we continue to act on previous information.
23630 - Avoid sending junk to controllers or segfaulting when a controller
23631 uses EVENT_NEW_DESC with verbose nicknames.
23632 - Stop triggering asserts if the controller tries to extend hidden
23633 service circuits (reported by mwenge).
23634 - Avoid infinite loop on unexpected controller input.
23635 - When the controller does a "GETINFO network-status", tell it
23636 about even those routers whose descriptors are very old, and use
23637 long nicknames where appropriate.
23638 - Change NT service functions to be loaded on demand. This lets us
23639 build with MinGW without breaking Tor for Windows 98 users.
23640 - Do DirPort reachability tests less often, since a single test
23641 chews through many circuits before giving up.
23642 - In the hidden service example in torrc.sample, stop recommending
23643 esoteric and discouraged hidden service options.
23644 - When stopping an NT service, wait up to 10 sec for it to actually
23645 stop. Patch from Matt Edman; resolves bug 295.
23646 - Fix handling of verbose nicknames with ORCONN controller events:
23647 make them show up exactly when requested, rather than exactly when
23649 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
23650 printing a duplicate "$" in the keys we send (reported by mwenge).
23651 - Correctly set maximum connection limit on Cygwin. (This time
23653 - Try to detect Windows correctly when cross-compiling.
23654 - Detect the size of the routers file correctly even if it is
23655 corrupted (on systems without mmap) or not page-aligned (on systems
23656 with mmap). This bug was harmless.
23657 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
23658 to open a stream fails; now we do in more cases. This should
23659 make clients able to find a good exit faster in some cases, since
23660 unhandleable requests will now get an error rather than timing out.
23661 - Resolve two memory leaks when rebuilding the on-disk router cache
23662 (reported by fookoowa).
23663 - Clean up minor code warnings suggested by the MIPSpro C compiler,
23664 and reported by some Centos users.
23665 - Controller signals now work on non-Unix platforms that don't define
23666 SIGUSR1 and SIGUSR2 the way we expect.
23667 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
23668 values before failing, and always enables eventdns.
23669 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
23670 Try to fix this in configure.in by checking for most functions
23671 before we check for libevent.
23674 Changes in version 0.1.2.2-alpha - 2006-10-07
23676 - Make our async eventdns library on-by-default for Tor servers,
23677 and plan to deprecate the separate dnsworker threads.
23678 - Add server-side support for "reverse" DNS lookups (using PTR
23679 records so clients can determine the canonical hostname for a given
23680 IPv4 address). Only supported by servers using eventdns; servers
23681 now announce in their descriptors whether they support eventdns.
23682 - Specify and implement client-side SOCKS5 interface for reverse DNS
23683 lookups (see doc/socks-extensions.txt).
23684 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
23685 connect to directory servers through Tor. Previously, clients needed
23686 to find Tor exits to make private connections to directory servers.
23687 - Avoid choosing Exit nodes for entry or middle hops when the
23688 total bandwidth available from non-Exit nodes is much higher than
23689 the total bandwidth available from Exit nodes.
23690 - Workaround for name servers (like Earthlink's) that hijack failing
23691 DNS requests and replace the no-such-server answer with a "helpful"
23692 redirect to an advertising-driven search portal. Also work around
23693 DNS hijackers who "helpfully" decline to hijack known-invalid
23694 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
23695 lets you turn it off.
23696 - Send out a burst of long-range padding cells once we've established
23697 that we're reachable. Spread them over 4 circuits, so hopefully
23698 a few will be fast. This exercises our bandwidth and bootstraps
23699 us into the directory more quickly.
23701 o New/improved config options:
23702 - Add new config option "ResolvConf" to let the server operator
23703 choose an alternate resolve.conf file when using eventdns.
23704 - Add an "EnforceDistinctSubnets" option to control our "exclude
23705 servers on the same /16" behavior. It's still on by default; this
23706 is mostly for people who want to operate private test networks with
23707 all the machines on the same subnet.
23708 - If one of our entry guards is on the ExcludeNodes list, or the
23709 directory authorities don't think it's a good guard, treat it as
23710 if it were unlisted: stop using it as a guard, and throw it off
23711 the guards list if it stays that way for a long time.
23712 - Allow directory authorities to be marked separately as authorities
23713 for the v1 directory protocol, the v2 directory protocol, and
23714 as hidden service directories, to make it easier to retire old
23715 authorities. V1 authorities should set "HSAuthoritativeDir 1"
23716 to continue being hidden service authorities too.
23717 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
23719 o Minor features, controller:
23720 - Fix CIRC controller events so that controllers can learn the
23721 identity digests of non-Named servers used in circuit paths.
23722 - Let controllers ask for more useful identifiers for servers. Instead
23723 of learning identity digests for un-Named servers and nicknames
23724 for Named servers, the new identifiers include digest, nickname,
23725 and indication of Named status. Off by default; see control-spec.txt
23726 for more information.
23727 - Add a "getinfo address" controller command so it can display Tor's
23728 best guess to the user.
23729 - New controller event to alert the controller when our server
23730 descriptor has changed.
23731 - Give more meaningful errors on controller authentication failure.
23733 o Minor features, other:
23734 - When asked to resolve a hostname, don't use non-exit servers unless
23735 requested to do so. This allows servers with broken DNS to be
23736 useful to the network.
23737 - Divide eventdns log messages into warn and info messages.
23738 - Reserve the nickname "Unnamed" for routers that can't pick
23739 a hostname: any router can call itself Unnamed; directory
23740 authorities will never allocate Unnamed to any particular router;
23741 clients won't believe that any router is the canonical Unnamed.
23742 - Only include function names in log messages for info/debug messages.
23743 For notice/warn/err, the content of the message should be clear on
23744 its own, and printing the function name only confuses users.
23745 - Avoid some false positives during reachability testing: don't try
23746 to test via a server that's on the same /24 as us.
23747 - If we fail to build a circuit to an intended enclave, and it's
23748 not mandatory that we use that enclave, stop wanting it.
23749 - When eventdns is enabled, allow multithreaded builds on NetBSD and
23750 OpenBSD. (We had previously disabled threads on these platforms
23751 because they didn't have working thread-safe resolver functions.)
23753 o Major bugfixes, anonymity/security:
23754 - If a client asked for a server by name, and there's a named server
23755 in our network-status but we don't have its descriptor yet, we
23756 could return an unnamed server instead.
23757 - Fix NetBSD bug that could allow someone to force uninitialized RAM
23758 to be sent to a server's DNS resolver. This only affects NetBSD
23759 and other platforms that do not bounds-check tolower().
23760 - Reject (most) attempts to use Tor circuits with length one. (If
23761 many people start using Tor as a one-hop proxy, exit nodes become
23762 a more attractive target for compromise.)
23763 - Just because your DirPort is open doesn't mean people should be
23764 able to remotely teach you about hidden service descriptors. Now
23765 only accept rendezvous posts if you've got HSAuthoritativeDir set.
23767 o Major bugfixes, other:
23768 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
23769 - When a client asks the server to resolve (not connect to)
23770 an address, and it has a cached answer, give them the cached answer.
23771 Previously, the server would give them no answer at all.
23772 - Allow really slow clients to not hang up five minutes into their
23773 directory downloads (suggested by Adam J. Richter).
23774 - We were building exactly the wrong circuits when we anticipated
23775 hidden service requirements, meaning Tor would have to build all
23776 its circuits on demand.
23777 - Avoid crashing when we mmap a router cache file of size 0.
23778 - When testing reachability of our DirPort, don't launch new
23779 tests when there's already one in progress -- unreachable
23780 servers were stacking up dozens of testing streams.
23782 o Minor bugfixes, correctness:
23783 - If we're a directory mirror and we ask for "all" network status
23784 documents, we would discard status documents from authorities
23785 we don't recognize.
23786 - Avoid a memory corruption bug when creating a hash table for
23788 - Avoid controller-triggered crash when misusing certain commands
23789 from a v0 controller on platforms that do not handle
23790 printf("%s",NULL) gracefully.
23791 - Don't crash when a controller sends a third argument to an
23792 "extendcircuit" request.
23793 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
23794 response; fix error code when "getinfo dir/status/" fails.
23795 - Avoid crash when telling controller stream-status and a stream
23797 - Patch from Adam Langley to fix assert() in eventdns.c.
23798 - Fix a debug log message in eventdns to say "X resolved to Y"
23799 instead of "X resolved to X".
23800 - Make eventdns give strings for DNS errors, not just error numbers.
23801 - Track unreachable entry guards correctly: don't conflate
23802 'unreachable by us right now' with 'listed as down by the directory
23803 authorities'. With the old code, if a guard was unreachable by
23804 us but listed as running, it would clog our guard list forever.
23805 - Behave correctly in case we ever have a network with more than
23806 2GB/s total advertised capacity.
23807 - Make TrackExitHosts case-insensitive, and fix the behavior of
23808 ".suffix" TrackExitHosts items to avoid matching in the middle of
23810 - Finally fix the openssl warnings from newer gccs that believe that
23811 ignoring a return value is okay, but casting a return value and
23812 then ignoring it is a sign of madness.
23813 - Prevent the contrib/exitlist script from printing the same
23814 result more than once.
23815 - Patch from Steve Hildrey: Generate network status correctly on
23816 non-versioning dirservers.
23817 - Don't listen to the X-Your-Address-Is hint if you did the lookup
23818 via Tor; otherwise you'll think you're the exit node's IP address.
23820 o Minor bugfixes, performance:
23821 - Two small performance improvements on parsing descriptors.
23822 - Major performance improvement on inserting descriptors: change
23823 algorithm from O(n^2) to O(n).
23824 - Make the common memory allocation path faster on machines where
23825 malloc(0) returns a pointer.
23826 - Start remembering X-Your-Address-Is directory hints even if you're
23827 a client, so you can become a server more smoothly.
23828 - Avoid duplicate entries on MyFamily line in server descriptor.
23830 o Packaging, features:
23831 - Remove architecture from OS X builds. The official builds are
23832 now universal binaries.
23833 - The Debian package now uses --verify-config when (re)starting,
23834 to distinguish configuration errors from other errors.
23835 - Update RPMs to require libevent 1.1b.
23837 o Packaging, bugfixes:
23838 - Patches so Tor builds with MinGW on Windows.
23839 - Patches so Tor might run on Cygwin again.
23840 - Resume building on non-gcc compilers and ancient gcc. Resume
23841 building with the -O0 compile flag. Resume building cleanly on
23843 - Run correctly on OS X platforms with case-sensitive filesystems.
23844 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
23845 - Add autoconf checks so Tor can build on Solaris x86 again.
23848 - Documented (and renamed) ServerDNSSearchDomains and
23849 ServerDNSResolvConfFile options.
23850 - Be clearer that the *ListenAddress directives can be repeated
23854 Changes in version 0.1.1.24 - 2006-09-29
23856 - Allow really slow clients to not hang up five minutes into their
23857 directory downloads (suggested by Adam J. Richter).
23858 - Fix major performance regression from 0.1.0.x: instead of checking
23859 whether we have enough directory information every time we want to
23860 do something, only check when the directory information has changed.
23861 This should improve client CPU usage by 25-50%.
23862 - Don't crash if, after a server has been running for a while,
23863 it can't resolve its hostname.
23866 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23867 - Don't crash when the controller receives a third argument to an
23868 "extendcircuit" request.
23869 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
23870 response; fix error code when "getinfo dir/status/" fails.
23871 - Fix configure.in to not produce broken configure files with
23872 more recent versions of autoconf. Thanks to Clint for his auto*
23874 - Fix security bug on NetBSD that could allow someone to force
23875 uninitialized RAM to be sent to a server's DNS resolver. This
23876 only affects NetBSD and other platforms that do not bounds-check
23878 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
23879 methods: these are known to be buggy.
23880 - If we're a directory mirror and we ask for "all" network status
23881 documents, we would discard status documents from authorities
23882 we don't recognize.
23885 Changes in version 0.1.2.1-alpha - 2006-08-27
23887 - Add "eventdns" async dns library from Adam Langley, tweaked to
23888 build on OSX and Windows. Only enabled if you pass the
23889 --enable-eventdns argument to configure.
23890 - Allow servers with no hostname or IP address to learn their
23891 IP address by asking the directory authorities. This code only
23892 kicks in when you would normally have exited with a "no address"
23893 error. Nothing's authenticated, so use with care.
23894 - Rather than waiting a fixed amount of time between retrying
23895 application connections, we wait only 5 seconds for the first,
23896 10 seconds for the second, and 15 seconds for each retry after
23897 that. Hopefully this will improve the expected user experience.
23898 - Patch from Tup to add support for transparent AP connections:
23899 this basically bundles the functionality of trans-proxy-tor
23900 into the Tor mainline. Now hosts with compliant pf/netfilter
23901 implementations can redirect TCP connections straight to Tor
23902 without diverting through SOCKS. Needs docs.
23903 - Busy directory servers save lots of memory by spooling server
23904 descriptors, v1 directories, and v2 networkstatus docs to buffers
23905 as needed rather than en masse. Also mmap the cached-routers
23906 files, so we don't need to keep the whole thing in memory too.
23907 - Automatically avoid picking more than one node from the same
23908 /16 network when constructing a circuit.
23909 - Revise and clean up the torrc.sample that we ship with; add
23910 a section for BandwidthRate and BandwidthBurst.
23913 - Split circuit_t into origin_circuit_t and or_circuit_t, and
23914 split connection_t into edge, or, dir, control, and base structs.
23915 These will save quite a bit of memory on busy servers, and they'll
23916 also help us track down bugs in the code and bugs in the spec.
23917 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
23918 or later. Log when we are doing this, so we can diagnose it when
23919 it fails. (Also, recommend libevent 1.1b for kqueue and
23920 win32 methods; deprecate libevent 1.0b harder; make libevent
23921 recommendation system saner.)
23922 - Start being able to build universal binaries on OS X (thanks
23924 - Export the default exit policy via the control port, so controllers
23925 don't need to guess what it is / will be later.
23926 - Add a man page entry for ProtocolWarnings.
23927 - Add TestVia config option to the man page.
23928 - Remove even more protocol-related warnings from Tor server logs,
23929 such as bad TLS handshakes and malformed begin cells.
23930 - Stop fetching descriptors if you're not a dir mirror and you
23931 haven't tried to establish any circuits lately. [This currently
23932 causes some dangerous behavior, because when you start up again
23933 you'll use your ancient server descriptors.]
23934 - New DirPort behavior: if you have your dirport set, you download
23935 descriptors aggressively like a directory mirror, whether or not
23936 your ORPort is set.
23937 - Get rid of the router_retry_connections notion. Now routers
23938 no longer try to rebuild long-term connections to directory
23939 authorities, and directory authorities no longer try to rebuild
23940 long-term connections to all servers. We still don't hang up
23941 connections in these two cases though -- we need to look at it
23942 more carefully to avoid flapping, and we likely need to wait til
23943 0.1.1.x is obsolete.
23944 - Drop compatibility with obsolete Tors that permit create cells
23945 to have the wrong circ_id_type.
23946 - Re-enable per-connection rate limiting. Get rid of the "OP
23947 bandwidth" concept. Lay groundwork for "bandwidth classes" --
23948 separate global buckets that apply depending on what sort of conn
23950 - Start publishing one minute or so after we find our ORPort
23951 to be reachable. This will help reduce the number of descriptors
23952 we have for ourselves floating around, since it's quite likely
23953 other things (e.g. DirPort) will change during that minute too.
23954 - Fork the v1 directory protocol into its own spec document,
23955 and mark dir-spec.txt as the currently correct (v2) spec.
23958 - When we find our DirPort to be reachable, publish a new descriptor
23959 so we'll tell the world (reported by pnx).
23960 - Publish a new descriptor after we hup/reload. This is important
23961 if our config has changed such that we'll want to start advertising
23962 our DirPort now, etc.
23963 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23964 - When we have a state file we cannot parse, tell the user and
23965 move it aside. Now we avoid situations where the user starts
23966 Tor in 1904, Tor writes a state file with that timestamp in it,
23967 the user fixes her clock, and Tor refuses to start.
23968 - Fix configure.in to not produce broken configure files with
23969 more recent versions of autoconf. Thanks to Clint for his auto*
23971 - "tor --verify-config" now exits with -1(255) or 0 depending on
23972 whether the config options are bad or good.
23973 - Resolve bug 321 when using dnsworkers: append a period to every
23974 address we resolve at the exit node, so that we do not accidentally
23975 pick up local addresses, and so that failing searches are retried
23976 in the resolver search domains. (This is already solved for
23977 eventdns.) (This breaks Blossom servers for now.)
23978 - If we are using an exit enclave and we can't connect, e.g. because
23979 its webserver is misconfigured to not listen on localhost, then
23980 back off and try connecting from somewhere else before we fail.
23983 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
23984 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
23985 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
23986 when the IP address is mapped through MapAddress to a hostname.
23987 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
23988 useless IPv6 DNS resolves.
23989 - Patch suggested by Karsten Loesing: respond to SIGNAL command
23990 before we execute the signal, in case the signal shuts us down.
23991 - Clean up AllowInvalidNodes man page entry.
23992 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
23993 - Add more asserts to track down an assert error on a windows Tor
23994 server with connection_add being called with socket == -1.
23995 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
23996 - Fix misleading log messages: an entry guard that is "unlisted",
23997 as well as not known to be "down" (because we've never heard
23998 of it), is not therefore "up".
23999 - Remove code to special-case "-cvs" ending, since it has not
24000 actually mattered since 0.0.9.
24001 - Make our socks5 handling more robust to broken socks clients:
24002 throw out everything waiting on the buffer in between socks
24003 handshake phases, since they can't possibly (so the theory
24004 goes) have predicted what we plan to respond to them.
24007 Changes in version 0.1.1.23 - 2006-07-30
24009 - Fast Tor servers, especially exit nodes, were triggering asserts
24010 due to a bug in handling the list of pending DNS resolves. Some
24011 bugs still remain here; we're hunting them.
24012 - Entry guards could crash clients by sending unexpected input.
24013 - More fixes on reachability testing: if you find yourself reachable,
24014 then don't ever make any client requests (so you stop predicting
24015 circuits), then hup or have your clock jump, then later your IP
24016 changes, you won't think circuits are working, so you won't try to
24017 test reachability, so you won't publish.
24020 - Avoid a crash if the controller does a resetconf firewallports
24021 and then a setconf fascistfirewall=1.
24022 - Avoid an integer underflow when the dir authority decides whether
24023 a router is stable: we might wrongly label it stable, and compute
24024 a slightly wrong median stability, when a descriptor is published
24026 - Fix a place where we might trigger an assert if we can't build our
24027 own server descriptor yet.
24030 Changes in version 0.1.1.22 - 2006-07-05
24032 - Fix a big bug that was causing servers to not find themselves
24033 reachable if they changed IP addresses. Since only 0.1.1.22+
24034 servers can do reachability testing correctly, now we automatically
24035 make sure to test via one of these.
24036 - Fix to allow clients and mirrors to learn directory info from
24037 descriptor downloads that get cut off partway through.
24038 - Directory authorities had a bug in deciding if a newly published
24039 descriptor was novel enough to make everybody want a copy -- a few
24040 servers seem to be publishing new descriptors many times a minute.
24042 - Fix a rare bug that was causing some servers to complain about
24043 "closing wedged cpuworkers" and skip some circuit create requests.
24044 - Make the Exit flag in directory status documents actually work.
24047 Changes in version 0.1.1.21 - 2006-06-10
24048 o Crash and assert fixes from 0.1.1.20:
24049 - Fix a rare crash on Tor servers that have enabled hibernation.
24050 - Fix a seg fault on startup for Tor networks that use only one
24051 directory authority.
24052 - Fix an assert from a race condition that occurs on Tor servers
24053 while exiting, where various threads are trying to log that they're
24054 exiting, and delete the logs, at the same time.
24055 - Make our unit tests pass again on certain obscure platforms.
24058 - Add support for building SUSE RPM packages.
24059 - Speed up initial bootstrapping for clients: if we are making our
24060 first ever connection to any entry guard, then don't mark it down
24062 - When only one Tor server in the network is labelled as a guard,
24063 and we've already picked him, we would cycle endlessly picking him
24064 again, being unhappy about it, etc. Now we specifically exclude
24065 current guards when picking a new guard.
24066 - Servers send create cells more reliably after the TLS connection
24067 is established: we were sometimes forgetting to send half of them
24068 when we had more than one pending.
24069 - If we get a create cell that asks us to extend somewhere, but the
24070 Tor server there doesn't match the expected digest, we now send
24071 a destroy cell back, rather than silently doing nothing.
24072 - Make options->RedirectExit work again.
24073 - Make cookie authentication for the controller work again.
24074 - Stop being picky about unusual characters in the arguments to
24075 mapaddress. It's none of our business.
24076 - Add a new config option "TestVia" that lets you specify preferred
24077 middle hops to use for test circuits. Perhaps this will let me
24078 debug the reachability problems better.
24080 o Log / documentation fixes:
24081 - If we're a server and some peer has a broken TLS certificate, don't
24082 log about it unless ProtocolWarnings is set, i.e., we want to hear
24083 about protocol violations by others.
24084 - Fix spelling of VirtualAddrNetwork in man page.
24085 - Add a better explanation at the top of the autogenerated torrc file
24086 about what happened to our old torrc.
24089 Changes in version 0.1.1.20 - 2006-05-23
24091 - Downgrade a log severity where servers complain that they're
24093 - Avoid a compile warning on FreeBSD.
24094 - Remove string size limit on NEWDESC messages; solve bug 291.
24095 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
24096 more thoroughly when we're running on windows.
24099 Changes in version 0.1.1.19-rc - 2006-05-03
24101 - Regenerate our local descriptor if it's dirty and we try to use
24102 it locally (e.g. if it changes during reachability detection).
24103 - If we setconf our ORPort to 0, we continued to listen on the
24104 old ORPort and receive connections.
24105 - Avoid a second warning about machine/limits.h on Debian
24107 - Be willing to add our own routerinfo into the routerlist.
24108 Now authorities will include themselves in their directories
24109 and network-statuses.
24110 - Stop trying to upload rendezvous descriptors to every
24111 directory authority: only try the v1 authorities.
24112 - Servers no longer complain when they think they're not
24113 registered with the directory authorities. There were too many
24115 - Backport dist-rpm changes so rpms can be built without errors.
24118 - Implement an option, VirtualAddrMask, to set which addresses
24119 get handed out in response to mapaddress requests. This works
24120 around a bug in tsocks where 127.0.0.0/8 is never socksified.
24123 Changes in version 0.1.1.18-rc - 2006-04-10
24125 - Work harder to download live network-statuses from all the
24126 directory authorities we know about. Improve the threshold
24127 decision logic so we're more robust to edge cases.
24128 - When fetching rendezvous descriptors, we were willing to ask
24129 v2 authorities too, which would always return 404.
24132 - Stop listing down or invalid nodes in the v1 directory. This will
24133 reduce its bulk by about 1/3, and reduce load on directory
24135 - When deciding whether a router is Fast or Guard-worthy, consider
24136 his advertised BandwidthRate and not just the BandwidthCapacity.
24137 - No longer ship INSTALL and README files -- they are useless now.
24138 - Force rpmbuild to behave and honor target_cpu.
24139 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
24140 - Start to include translated versions of the tor-doc-*.html
24141 files, along with the screenshots. Still needs more work.
24142 - Start sending back 512 and 451 errors if mapaddress fails,
24143 rather than not sending anything back at all.
24144 - When we fail to bind or listen on an incoming or outgoing
24145 socket, we should close it before failing. otherwise we just
24146 leak it. (thanks to weasel for finding.)
24147 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
24148 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
24149 - Make NoPublish (even though deprecated) work again.
24150 - Fix a minor security flaw where a versioning auth dirserver
24151 could list a recommended version many times in a row to make
24152 clients more convinced that it's recommended.
24153 - Fix crash bug if there are two unregistered servers running
24154 with the same nickname, one of them is down, and you ask for
24155 them by nickname in your EntryNodes or ExitNodes. Also, try
24156 to pick the one that's running rather than an arbitrary one.
24157 - Fix an infinite loop we could hit if we go offline for too long.
24158 - Complain when we hit WSAENOBUFS on recv() or write() too.
24159 Perhaps this will help us hunt the bug.
24160 - If you're not a versioning dirserver, don't put the string
24161 "client-versions \nserver-versions \n" in your network-status.
24162 - Lower the minimum required number of file descriptors to 1000,
24163 so we can have some overhead for Valgrind on Linux, where the
24164 default ulimit -n is 1024.
24167 - Add tor.dizum.com as the fifth authoritative directory server.
24168 - Add a new config option FetchUselessDescriptors, off by default,
24169 for when you plan to run "exitlist" on your client and you want
24170 to know about even the non-running descriptors.
24173 Changes in version 0.1.1.17-rc - 2006-03-28
24175 - Clients and servers since 0.1.1.10-alpha have been expiring
24176 connections whenever they are idle for 5 minutes and they *do*
24177 have circuits on them. Oops. With this new version, clients will
24178 discard their previous entry guard choices and avoid choosing
24179 entry guards running these flawed versions.
24180 - Fix memory leak when uncompressing concatenated zlib streams. This
24181 was causing substantial leaks over time on Tor servers.
24182 - The v1 directory was including servers as much as 48 hours old,
24183 because that's how the new routerlist->routers works. Now only
24184 include them if they're 20 hours old or less.
24187 - Resume building on irix64, netbsd 2.0, etc.
24188 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
24190 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
24191 and it is confusing some users.
24192 - Mirrors stop caching the v1 directory so often.
24193 - Make the max number of old descriptors that a cache will hold
24194 rise with the number of directory authorities, so we can scale.
24195 - Change our win32 uname() hack to be more forgiving about what
24196 win32 versions it thinks it's found.
24199 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
24201 - When the controller's *setconf commands fail, collect an error
24202 message in a string and hand it back to the controller.
24203 - Make the v2 dir's "Fast" flag based on relative capacity, just
24204 like "Stable" is based on median uptime. Name everything in the
24205 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
24206 - Log server fingerprint on startup, so new server operators don't
24207 have to go hunting around their filesystem for it.
24208 - Return a robots.txt on our dirport to discourage google indexing.
24209 - Let the controller ask for GETINFO dir/status/foo so it can ask
24210 directly rather than connecting to the dir port. Only works when
24211 dirport is set for now.
24213 o New config options rather than constants in the code:
24214 - SocksTimeout: How long do we let a socks connection wait
24215 unattached before we fail it?
24216 - CircuitBuildTimeout: Cull non-open circuits that were born
24217 at least this many seconds ago.
24218 - CircuitIdleTimeout: Cull open clean circuits that were born
24219 at least this many seconds ago.
24222 Changes in version 0.1.1.16-rc - 2006-03-18
24223 o Bugfixes on 0.1.1.15-rc:
24224 - Fix assert when the controller asks to attachstream a connect-wait
24225 or resolve-wait stream.
24226 - Now do address rewriting when the controller asks us to attach
24227 to a particular circuit too. This will let Blossom specify
24228 "moria2.exit" without having to learn what moria2's IP address is.
24229 - Make the "tor --verify-config" command-line work again, so people
24230 can automatically check if their torrc will parse.
24231 - Authoritative dirservers no longer require an open connection from
24232 a server to consider him "reachable". We need this change because
24233 when we add new auth dirservers, old servers won't know not to
24235 - Let Tor build on Sun CC again.
24236 - Fix an off-by-one buffer size in dirserv.c that magically never
24237 hit our three authorities but broke sjmurdoch's own tor network.
24238 - If we as a directory mirror don't know of any v1 directory
24239 authorities, then don't try to cache any v1 directories.
24240 - Stop warning about unknown servers in our family when they are
24241 given as hex digests.
24242 - Stop complaining as quickly to the server operator that he
24243 hasn't registered his nickname/key binding.
24244 - Various cleanups so we can add new V2 Auth Dirservers.
24245 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
24246 reflect the updated flags in our v2 dir protocol.
24247 - Resume allowing non-printable characters for exit streams (both
24248 for connecting and for resolving). Now we tolerate applications
24249 that don't follow the RFCs. But continue to block malformed names
24252 o Bugfixes on 0.1.0.x:
24253 - Fix assert bug in close_logs(): when we close and delete logs,
24254 remove them all from the global "logfiles" list.
24255 - Fix minor integer overflow in calculating when we expect to use up
24256 our bandwidth allocation before hibernating.
24257 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
24258 there are multiple SSLs installed with different versions.
24259 - When we try to be a server and Address is not explicitly set and
24260 our hostname resolves to a private IP address, try to use an
24261 interface address if it has a public address. Now Windows machines
24262 that think of themselves as localhost can work by default.
24265 - Let the controller ask for GETINFO dir/server/foo so it can ask
24266 directly rather than connecting to the dir port.
24267 - Let the controller tell us about certain router descriptors
24268 that it doesn't want Tor to use in circuits. Implement
24269 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
24270 - New config option SafeSocks to reject all application connections
24271 using unsafe socks protocols. Defaults to off.
24274 Changes in version 0.1.1.15-rc - 2006-03-11
24275 o Bugfixes and cleanups:
24276 - When we're printing strings from the network, don't try to print
24277 non-printable characters. This protects us against shell escape
24278 sequence exploits, and also against attacks to fool humans into
24279 misreading their logs.
24280 - Fix a bug where Tor would fail to establish any connections if you
24281 left it off for 24 hours and then started it: we were happy with
24282 the obsolete network statuses, but they all referred to router
24283 descriptors that were too old to fetch, so we ended up with no
24284 valid router descriptors.
24285 - Fix a seg fault in the controller's "getinfo orconn-status"
24286 command while listing status on incoming handshaking connections.
24287 Introduce a status name "NEW" for these connections.
24288 - If we get a linelist or linelist_s config option from the torrc
24289 (e.g. ExitPolicy) and it has no value, warn and skip rather than
24290 silently resetting it to its default.
24291 - Don't abandon entry guards until they've been down or gone for
24293 - Cleaner and quieter log messages.
24296 - New controller signal NEWNYM that makes new application requests
24297 use clean circuits.
24298 - Add a new circuit purpose 'controller' to let the controller ask
24299 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
24300 controller command to let you specify the purpose if you're
24301 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
24302 command to let you change a circuit's purpose after it's been
24304 - Accept "private:*" in routerdesc exit policies; not generated yet
24305 because older Tors do not understand it.
24306 - Add BSD-style contributed startup script "rc.subr" from Peter
24310 Changes in version 0.1.1.14-alpha - 2006-02-20
24311 o Bugfixes on 0.1.1.x:
24312 - Don't die if we ask for a stdout or stderr log (even implicitly)
24313 and we're set to RunAsDaemon -- just warn.
24314 - We still had a few bugs in the OR connection rotation code that
24315 caused directory servers to slowly aggregate connections to other
24316 fast Tor servers. This time for sure!
24317 - Make log entries on Win32 include the name of the function again.
24318 - We were treating a pair of exit policies if they were equal even
24319 if one said accept and the other said reject -- causing us to
24320 not always publish a new descriptor since we thought nothing
24322 - Retry pending server downloads as well as pending networkstatus
24323 downloads when we unexpectedly get a socks request.
24324 - We were ignoring the IS_FAST flag in the directory status,
24325 meaning we were willing to pick trivial-bandwidth nodes for "fast"
24327 - If the controller's SAVECONF command fails (e.g. due to file
24328 permissions), let the controller know that it failed.
24331 - If we're trying to be a Tor server and running Windows 95/98/ME
24332 as a server, explain that we'll likely crash.
24333 - When we're a server, a client asks for an old-style directory,
24334 and our write bucket is empty, don't give it to him. This way
24335 small servers can continue to serve the directory *sometimes*,
24336 without getting overloaded.
24337 - Compress exit policies even more -- look for duplicate lines
24339 - Clients now honor the "guard" flag in the router status when
24340 picking entry guards, rather than looking at is_fast or is_stable.
24341 - Retain unrecognized lines in $DATADIR/state file, so that we can
24342 be forward-compatible.
24343 - Generate 18.0.0.0/8 address policy format in descs when we can;
24344 warn when the mask is not reducible to a bit-prefix.
24345 - Let the user set ControlListenAddress in the torrc. This can be
24346 dangerous, but there are some cases (like a secured LAN) where it
24348 - Split ReachableAddresses into ReachableDirAddresses and
24349 ReachableORAddresses, so we can restrict Dir conns to port 80
24350 and OR conns to port 443.
24351 - Now we can target arch and OS in rpm builds (contributed by
24352 Phobos). Also make the resulting dist-rpm filename match the
24354 - New config options to help controllers: FetchServerDescriptors
24355 and FetchHidServDescriptors for whether to fetch server
24356 info and hidserv info or let the controller do it, and
24357 PublishServerDescriptor and PublishHidServDescriptors.
24358 - Also let the controller set the __AllDirActionsPrivate config
24359 option if you want all directory fetches/publishes to happen via
24360 Tor (it assumes your controller bootstraps your circuits).
24363 Changes in version 0.1.0.17 - 2006-02-17
24364 o Crash bugfixes on 0.1.0.x:
24365 - When servers with a non-zero DirPort came out of hibernation,
24366 sometimes they would trigger an assert.
24368 o Other important bugfixes:
24369 - On platforms that don't have getrlimit (like Windows), we were
24370 artificially constraining ourselves to a max of 1024
24371 connections. Now just assume that we can handle as many as 15000
24372 connections. Hopefully this won't cause other problems.
24374 o Backported features:
24375 - When we're a server, a client asks for an old-style directory,
24376 and our write bucket is empty, don't give it to him. This way
24377 small servers can continue to serve the directory *sometimes*,
24378 without getting overloaded.
24379 - Whenever you get a 503 in response to a directory fetch, try
24380 once more. This will become important once servers start sending
24381 503's whenever they feel busy.
24382 - Fetch a new directory every 120 minutes, not every 40 minutes.
24383 Now that we have hundreds of thousands of users running the old
24384 directory algorithm, it's starting to hurt a lot.
24385 - Bump up the period for forcing a hidden service descriptor upload
24386 from 20 minutes to 1 hour.
24389 Changes in version 0.1.1.13-alpha - 2006-02-09
24390 o Crashes in 0.1.1.x:
24391 - When you tried to setconf ORPort via the controller, Tor would
24392 crash. So people using TorCP to become a server were sad.
24393 - Solve (I hope) the stack-smashing bug that we were seeing on fast
24394 servers. The problem appears to be something do with OpenSSL's
24395 random number generation, or how we call it, or something. Let me
24396 know if the crashes continue.
24397 - Turn crypto hardware acceleration off by default, until we find
24398 somebody smart who can test it for us. (It appears to produce
24399 seg faults in at least some cases.)
24400 - Fix a rare assert error when we've tried all intro points for
24401 a hidden service and we try fetching the service descriptor again:
24402 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
24405 - Fix a major load balance bug: we were round-robining in 16 KB
24406 chunks, and servers with bandwidthrate of 20 KB, while downloading
24407 a 600 KB directory, would starve their other connections. Now we
24408 try to be a bit more fair.
24409 - Dir authorities and mirrors were never expiring the newest
24410 descriptor for each server, causing memory and directory bloat.
24411 - Fix memory-bloating and connection-bloating bug on servers: We
24412 were never closing any connection that had ever had a circuit on
24413 it, because we were checking conn->n_circuits == 0, yet we had a
24414 bug that let it go negative.
24415 - Make Tor work using squid as your http proxy again -- squid
24416 returns an error if you ask for a URL that's too long, and it uses
24417 a really generic error message. Plus, many people are behind a
24418 transparent squid so they don't even realize it.
24419 - On platforms that don't have getrlimit (like Windows), we were
24420 artificially constraining ourselves to a max of 1024
24421 connections. Now just assume that we can handle as many as 15000
24422 connections. Hopefully this won't cause other problems.
24423 - Add a new config option ExitPolicyRejectPrivate which defaults to
24424 1. This means all exit policies will begin with rejecting private
24425 addresses, unless the server operator explicitly turns it off.
24428 - Clients no longer download descriptors for non-running
24430 - Before we add new directory authorities, we should make it
24431 clear that only v1 authorities should receive/publish hidden
24432 service descriptors.
24435 - As soon as we've fetched some more directory info, immediately
24436 try to download more server descriptors. This way we don't have
24437 a 10 second pause during initial bootstrapping.
24438 - Remove even more loud log messages that the server operator can't
24440 - When we're running an obsolete or un-recommended version, make
24441 the log message more clear about what the problem is and what
24442 versions *are* still recommended.
24443 - Provide a more useful warn message when our onion queue gets full:
24444 the CPU is too slow or the exit policy is too liberal.
24445 - Don't warn when we receive a 503 from a dirserver/cache -- this
24446 will pave the way for them being able to refuse if they're busy.
24447 - When we fail to bind a listener, try to provide a more useful
24448 log message: e.g., "Is Tor already running?"
24449 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
24450 Goldberg can prove things about our handshake protocol more
24452 - MaxConn has been obsolete for a while now. Document the ConnLimit
24453 config option, which is a *minimum* number of file descriptors
24454 that must be available else Tor refuses to start.
24455 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
24456 if you log to syslog and want something other than LOG_DAEMON.
24457 - Make dirservers generate a separate "guard" flag to mean,
24458 "would make a good entry guard". Make clients parse it and vote
24459 on it. Not used by clients yet.
24460 - Implement --with-libevent-dir option to ./configure. Also, improve
24461 search techniques to find libevent, and use those for openssl too.
24462 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
24463 - Only start testing reachability once we've established a
24464 circuit. This will make startup on dirservers less noisy.
24465 - Don't try to upload hidden service descriptors until we have
24466 established a circuit.
24467 - Fix the controller's "attachstream 0" command to treat conn like
24468 it just connected, doing address remapping, handling .exit and
24469 .onion idioms, and so on. Now we're more uniform in making sure
24470 that the controller hears about new and closing connections.
24473 Changes in version 0.1.1.12-alpha - 2006-01-11
24474 o Bugfixes on 0.1.1.x:
24475 - The fix to close duplicate server connections was closing all
24476 Tor client connections if they didn't establish a circuit
24477 quickly enough. Oops.
24478 - Fix minor memory issue (double-free) that happened on exit.
24480 o Bugfixes on 0.1.0.x:
24481 - Tor didn't warn when it failed to open a log file.
24484 Changes in version 0.1.1.11-alpha - 2006-01-10
24485 o Crashes in 0.1.1.x:
24486 - Include all the assert/crash fixes from 0.1.0.16.
24487 - If you start Tor and then quit very quickly, there were some
24488 races that tried to free things that weren't allocated yet.
24489 - Fix a rare memory stomp if you're running hidden services.
24490 - Fix segfault when specifying DirServer in config without nickname.
24491 - Fix a seg fault when you finish connecting to a server but at
24492 that moment you dump his server descriptor.
24493 - Extendcircuit and Attachstream controller commands would
24494 assert/crash if you don't give them enough arguments.
24495 - Fix an assert error when we're out of space in the connection_list
24496 and we try to post a hidden service descriptor (reported by weasel).
24497 - If you specify a relative torrc path and you set RunAsDaemon in
24498 your torrc, then it chdir()'s to the new directory. If you HUP,
24499 it tries to load the new torrc location, fails, and exits.
24500 The fix: no longer allow a relative path to torrc using -f.
24503 - Implement "entry guards": automatically choose a handful of entry
24504 nodes and stick with them for all circuits. Only pick new guards
24505 when the ones you have are unsuitable, and if the old guards
24506 become suitable again, switch back. This will increase security
24507 dramatically against certain end-point attacks. The EntryNodes
24508 config option now provides some hints about which entry guards you
24509 want to use most; and StrictEntryNodes means to only use those.
24510 - New directory logic: download by descriptor digest, not by
24511 fingerprint. Caches try to download all listed digests from
24512 authorities; clients try to download "best" digests from caches.
24513 This avoids partitioning and isolating attacks better.
24514 - Make the "stable" router flag in network-status be the median of
24515 the uptimes of running valid servers, and make clients pay
24516 attention to the network-status flags. Thus the cutoff adapts
24517 to the stability of the network as a whole, making IRC, IM, etc
24518 connections more reliable.
24521 - Tor servers with dynamic IP addresses were needing to wait 18
24522 hours before they could start doing reachability testing using
24523 the new IP address and ports. This is because they were using
24524 the internal descriptor to learn what to test, yet they were only
24525 rebuilding the descriptor once they decided they were reachable.
24526 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
24527 to download certain server descriptors, throw them away, and then
24528 fetch them again after 30 minutes. Now mirrors throw away these
24529 server descriptors so clients can't get them.
24530 - We were leaving duplicate connections to other ORs open for a week,
24531 rather than closing them once we detect a duplicate. This only
24532 really affected authdirservers, but it affected them a lot.
24533 - Spread the authdirservers' reachability testing over the entire
24534 testing interval, so we don't try to do 500 TLS's at once every
24538 - If the network is down, and we try to connect to a conn because
24539 we have a circuit in mind, and we timeout (30 seconds) because the
24540 network never answers, we were expiring the circuit, but we weren't
24541 obsoleting the connection or telling the entry_guards functions.
24542 - Some Tor servers process billions of cells per day. These statistics
24543 need to be uint64_t's.
24544 - Check for integer overflows in more places, when adding elements
24545 to smartlists. This could possibly prevent a buffer overflow
24546 on malicious huge inputs. I don't see any, but I haven't looked
24548 - ReachableAddresses kept growing new "reject *:*" lines on every
24550 - When you "setconf log" via the controller, it should remove all
24551 logs. We were automatically adding back in a "log notice stdout".
24552 - Newly bootstrapped Tor networks couldn't establish hidden service
24553 circuits until they had nodes with high uptime. Be more tolerant.
24554 - We were marking servers down when they could not answer every piece
24555 of the directory request we sent them. This was far too harsh.
24556 - Fix the torify (tsocks) config file to not use Tor for localhost
24558 - Directory authorities now go to the proper authority when asking for
24559 a networkstatus, even when they want a compressed one.
24560 - Fix a harmless bug that was causing Tor servers to log
24561 "Got an end because of misc error, but we're not an AP. Closing."
24562 - Authorities were treating their own descriptor changes as cosmetic,
24563 meaning the descriptor available in the network-status and the
24564 descriptor that clients downloaded were different.
24565 - The OS X installer was adding a symlink for tor_resolve but
24566 the binary was called tor-resolve (reported by Thomas Hardly).
24567 - Workaround a problem with some http proxies where they refuse GET
24568 requests that specify "Content-Length: 0" (reported by Adrian).
24569 - Fix wrong log message when you add a "HiddenServiceNodes" config
24570 line without any HiddenServiceDir line (reported by Chris Thomas).
24573 - Write the TorVersion into the state file so we have a prayer of
24574 keeping forward and backward compatibility.
24575 - Revive the FascistFirewall config option rather than eliminating it:
24576 now it's a synonym for ReachableAddresses *:80,*:443.
24577 - Clients choose directory servers from the network status lists,
24578 not from their internal list of router descriptors. Now they can
24579 go to caches directly rather than needing to go to authorities
24581 - Directory authorities ignore router descriptors that have only
24582 cosmetic differences: do this for 0.1.0.x servers now too.
24583 - Add a new flag to network-status indicating whether the server
24584 can answer v2 directory requests too.
24585 - Authdirs now stop whining so loudly about bad descriptors that
24586 they fetch from other dirservers. So when there's a log complaint,
24587 it's for sure from a freshly uploaded descriptor.
24588 - Reduce memory requirements in our structs by changing the order
24590 - There used to be two ways to specify your listening ports in a
24591 server descriptor: on the "router" line and with a separate "ports"
24592 line. Remove support for the "ports" line.
24593 - New config option "AuthDirRejectUnlisted" for auth dirservers as
24594 a panic button: if we get flooded with unusable servers we can
24595 revert to only listing servers in the approved-routers file.
24596 - Auth dir servers can now mark a fingerprint as "!reject" or
24597 "!invalid" in the approved-routers file (as its nickname), to
24598 refuse descriptors outright or include them but marked as invalid.
24599 - Servers store bandwidth history across restarts/crashes.
24600 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
24601 get a better idea of why their circuits failed. Not used yet.
24602 - Directory mirrors now cache up to 16 unrecognized network-status
24603 docs. Now we can add new authdirservers and they'll be cached too.
24604 - When picking a random directory, prefer non-authorities if any
24606 - New controller option "getinfo desc/all-recent" to fetch the
24607 latest server descriptor for every router that Tor knows about.
24610 Changes in version 0.1.0.16 - 2006-01-02
24611 o Crash bugfixes on 0.1.0.x:
24612 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
24613 corrupting the heap, losing FDs, or crashing when we need to resize
24614 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
24615 - It turns out sparc64 platforms crash on unaligned memory access
24616 too -- so detect and avoid this.
24617 - Handle truncated compressed data correctly (by detecting it and
24619 - Fix possible-but-unlikely free(NULL) in control.c.
24620 - When we were closing connections, there was a rare case that
24621 stomped on memory, triggering seg faults and asserts.
24622 - Avoid potential infinite recursion when building a descriptor. (We
24623 don't know that it ever happened, but better to fix it anyway.)
24624 - We were neglecting to unlink marked circuits from soon-to-close OR
24625 connections, which caused some rare scribbling on freed memory.
24626 - Fix a memory stomping race bug when closing the joining point of two
24627 rendezvous circuits.
24628 - Fix an assert in time parsing found by Steven Murdoch.
24630 o Other bugfixes on 0.1.0.x:
24631 - When we're doing reachability testing, provide more useful log
24632 messages so the operator knows what to expect.
24633 - Do not check whether DirPort is reachable when we are suppressing
24634 advertising it because of hibernation.
24635 - When building with -static or on Solaris, we sometimes needed -ldl.
24636 - When we're deciding whether a stream has enough circuits around
24637 that can handle it, count the freshly dirty ones and not the ones
24638 that are so dirty they won't be able to handle it.
24639 - When we're expiring old circuits, we had a logic error that caused
24640 us to close new rendezvous circuits rather than old ones.
24641 - Give a more helpful log message when you try to change ORPort via
24642 the controller: you should upgrade Tor if you want that to work.
24643 - We were failing to parse Tor versions that start with "Tor ".
24644 - Tolerate faulty streams better: when a stream fails for reason
24645 exitpolicy, stop assuming that the router is lying about his exit
24646 policy. When a stream fails for reason misc, allow it to retry just
24647 as if it was resolvefailed. When a stream has failed three times,
24648 reset its failure count so we can try again and get all three tries.
24651 Changes in version 0.1.1.10-alpha - 2005-12-11
24652 o Correctness bugfixes on 0.1.0.x:
24653 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
24654 corrupting the heap, losing FDs, or crashing when we need to resize
24655 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
24656 - Stop doing the complex voodoo overkill checking for insecure
24657 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
24658 - When we were closing connections, there was a rare case that
24659 stomped on memory, triggering seg faults and asserts.
24660 - We were neglecting to unlink marked circuits from soon-to-close OR
24661 connections, which caused some rare scribbling on freed memory.
24662 - When we're deciding whether a stream has enough circuits around
24663 that can handle it, count the freshly dirty ones and not the ones
24664 that are so dirty they won't be able to handle it.
24665 - Recover better from TCP connections to Tor servers that are
24666 broken but don't tell you (it happens!); and rotate TLS
24667 connections once a week.
24668 - When we're expiring old circuits, we had a logic error that caused
24669 us to close new rendezvous circuits rather than old ones.
24670 - Fix a scary-looking but apparently harmless bug where circuits
24671 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
24672 servers, and never switch to state CIRCUIT_STATE_OPEN.
24673 - When building with -static or on Solaris, we sometimes needed to
24675 - Give a useful message when people run Tor as the wrong user,
24676 rather than telling them to start chowning random directories.
24677 - We were failing to inform the controller about new .onion streams.
24679 o Security bugfixes on 0.1.0.x:
24680 - Refuse server descriptors if the fingerprint line doesn't match
24681 the included identity key. Tor doesn't care, but other apps (and
24682 humans) might actually be trusting the fingerprint line.
24683 - We used to kill the circuit when we receive a relay command we
24684 don't recognize. Now we just drop it.
24685 - Start obeying our firewall options more rigorously:
24686 . If we can't get to a dirserver directly, try going via Tor.
24687 . Don't ever try to connect (as a client) to a place our
24688 firewall options forbid.
24689 . If we specify a proxy and also firewall options, obey the
24690 firewall options even when we're using the proxy: some proxies
24691 can only proxy to certain destinations.
24692 - Fix a bug found by Lasse Overlier: when we were making internal
24693 circuits (intended to be cannibalized later for rendezvous and
24694 introduction circuits), we were picking them so that they had
24695 useful exit nodes. There was no need for this, and it actually
24696 aids some statistical attacks.
24697 - Start treating internal circuits and exit circuits separately.
24698 It's important to keep them separate because internal circuits
24699 have their last hops picked like middle hops, rather than like
24700 exit hops. So exiting on them will break the user's expectations.
24702 o Bugfixes on 0.1.1.x:
24703 - Take out the mis-feature where we tried to detect IP address
24704 flapping for people with DynDNS, and chose not to upload a new
24705 server descriptor sometimes.
24706 - Try to be compatible with OpenSSL 0.9.6 again.
24707 - Log fix: when the controller is logging about .onion addresses,
24708 sometimes it didn't include the ".onion" part of the address.
24709 - Don't try to modify options->DirServers internally -- if the
24710 user didn't specify any, just add the default ones directly to
24711 the trusted dirserver list. This fixes a bug where people running
24712 controllers would use SETCONF on some totally unrelated config
24713 option, and Tor would start yelling at them about changing their
24715 - Let the controller's redirectstream command specify a port, in
24716 case the controller wants to change that too.
24717 - When we requested a pile of server descriptors, we sometimes
24718 accidentally launched a duplicate request for the first one.
24719 - Bugfix for trackhostexits: write down the fingerprint of the
24720 chosen exit, not its nickname, because the chosen exit might not
24722 - When parsing foo.exit, if foo is unknown, and we are leaving
24723 circuits unattached, set the chosen_exit field and leave the
24724 address empty. This matters because controllers got confused
24726 - Directory authorities no longer try to download server
24727 descriptors that they know they will reject.
24729 o Features and updates:
24730 - Replace balanced trees with hash tables: this should make stuff
24731 significantly faster.
24732 - Resume using the AES counter-mode implementation that we ship,
24733 rather than OpenSSL's. Ours is significantly faster.
24734 - Many other CPU and memory improvements.
24735 - Add a new config option FastFirstHopPK (on by default) so clients
24736 do a trivial crypto handshake for their first hop, since TLS has
24737 already taken care of confidentiality and authentication.
24738 - Add a new config option TestSocks so people can see if their
24739 applications are using socks4, socks4a, socks5-with-ip, or
24740 socks5-with-hostname. This way they don't have to keep mucking
24741 with tcpdump and wondering if something got cached somewhere.
24742 - Warn when listening on a public address for socks. I suspect a
24743 lot of people are setting themselves up as open socks proxies,
24744 and they have no idea that jerks on the Internet are using them,
24745 since they simply proxy the traffic into the Tor network.
24746 - Add "private:*" as an alias in configuration for policies. Now
24747 you can simplify your exit policy rather than needing to list
24748 every single internal or nonroutable network space.
24749 - Add a new controller event type that allows controllers to get
24750 all server descriptors that were uploaded to a router in its role
24751 as authoritative dirserver.
24752 - Start shipping socks-extensions.txt, tor-doc-unix.html,
24753 tor-doc-server.html, and stylesheet.css in the tarball.
24754 - Stop shipping tor-doc.html in the tarball.
24757 Changes in version 0.1.1.9-alpha - 2005-11-15
24758 o Usability improvements:
24759 - Start calling it FooListenAddress rather than FooBindAddress,
24760 since few of our users know what it means to bind an address
24762 - Reduce clutter in server logs. We're going to try to make
24763 them actually usable now. New config option ProtocolWarnings that
24764 lets you hear about how _other Tors_ are breaking the protocol. Off
24766 - Divide log messages into logging domains. Once we put some sort
24767 of interface on this, it will let people looking at more verbose
24768 log levels specify the topics they want to hear more about.
24769 - Make directory servers return better http 404 error messages
24770 instead of a generic "Servers unavailable".
24771 - Check for even more Windows version flags when writing the platform
24772 string in server descriptors, and note any we don't recognize.
24773 - Clean up more of the OpenSSL memory when exiting, so we can detect
24774 memory leaks better.
24775 - Make directory authorities be non-versioning, non-naming by
24776 default. Now we can add new directory servers without requiring
24777 their operators to pay close attention.
24778 - When logging via syslog, include the pid whenever we provide
24779 a log entry. Suggested by Todd Fries.
24781 o Performance improvements:
24782 - Directory servers now silently throw away new descriptors that
24783 haven't changed much if the timestamps are similar. We do this to
24784 tolerate older Tor servers that upload a new descriptor every 15
24785 minutes. (It seemed like a good idea at the time.)
24786 - Inline bottleneck smartlist functions; use fast versions by default.
24787 - Add a "Map from digest to void*" abstraction digestmap_t so we
24788 can do less hex encoding/decoding. Use it in router_get_by_digest()
24789 to resolve a performance bottleneck.
24790 - Allow tor_gzip_uncompress to extract as much as possible from
24791 truncated compressed data. Try to extract as many
24792 descriptors as possible from truncated http responses (when
24793 DIR_PURPOSE_FETCH_ROUTERDESC).
24794 - Make circ->onionskin a pointer, not a static array. moria2 was using
24795 125000 circuit_t's after it had been up for a few weeks, which
24796 translates to 20+ megs of wasted space.
24797 - The private half of our EDH handshake keys are now chosen out
24798 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
24800 o Security improvements:
24801 - Start making directory caches retain old routerinfos, so soon
24802 clients can start asking by digest of descriptor rather than by
24803 fingerprint of server.
24804 - Add half our entropy from RAND_poll in OpenSSL. This knows how
24805 to use egd (if present), openbsd weirdness (if present), vms/os2
24806 weirdness (if we ever port there), and more in the future.
24808 o Bugfixes on 0.1.0.x:
24809 - Do round-robin writes of at most 16 kB per write. This might be
24810 more fair on loaded Tor servers, and it might resolve our Windows
24811 crash bug. It might also slow things down.
24812 - Our TLS handshakes were generating a single public/private
24813 keypair for the TLS context, rather than making a new one for
24814 each new connections. Oops. (But we were still rotating them
24815 periodically, so it's not so bad.)
24816 - When we were cannibalizing a circuit with a particular exit
24817 node in mind, we weren't checking to see if that exit node was
24818 already present earlier in the circuit. Oops.
24819 - When a Tor server's IP changes (e.g. from a dyndns address),
24820 upload a new descriptor so clients will learn too.
24821 - Really busy servers were keeping enough circuits open on stable
24822 connections that they were wrapping around the circuit_id
24823 space. (It's only two bytes.) This exposed a bug where we would
24824 feel free to reuse a circuit_id even if it still exists but has
24825 been marked for close. Try to fix this bug. Some bug remains.
24826 - If we would close a stream early (e.g. it asks for a .exit that
24827 we know would refuse it) but the LeaveStreamsUnattached config
24828 option is set by the controller, then don't close it.
24830 o Bugfixes on 0.1.1.8-alpha:
24831 - Fix a big pile of memory leaks, some of them serious.
24832 - Do not try to download a routerdesc if we would immediately reject
24834 - Resume inserting a newline between all router descriptors when
24835 generating (old style) signed directories, since our spec says
24837 - When providing content-type application/octet-stream for
24838 server descriptors using .z, we were leaving out the
24839 content-encoding header. Oops. (Everything tolerated this just
24840 fine, but that doesn't mean we need to be part of the problem.)
24841 - Fix a potential seg fault in getconf and getinfo using version 1
24842 of the controller protocol.
24843 - Avoid crash: do not check whether DirPort is reachable when we
24844 are suppressing it because of hibernation.
24845 - Make --hash-password not crash on exit.
24848 Changes in version 0.1.1.8-alpha - 2005-10-07
24849 o New features (major):
24850 - Clients don't download or use the directory anymore. Now they
24851 download and use network-statuses from the trusted dirservers,
24852 and fetch individual server descriptors as needed from mirrors.
24853 See dir-spec.txt for all the gory details.
24854 - Be more conservative about whether to advertise our DirPort.
24855 The main change is to not advertise if we're running at capacity
24856 and either a) we could hibernate or b) our capacity is low and
24857 we're using a default DirPort.
24858 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
24860 o New features (minor):
24861 - Try to be smart about when to retry network-status and
24862 server-descriptor fetches. Still needs some tuning.
24863 - Stop parsing, storing, or using running-routers output (but
24864 mirrors still cache and serve it).
24865 - Consider a threshold of versioning dirservers (dirservers who have
24866 an opinion about which Tor versions are still recommended) before
24867 deciding whether to warn the user that he's obsolete.
24868 - Dirservers can now reject/invalidate by key and IP, with the
24869 config options "AuthDirInvalid" and "AuthDirReject". This is
24870 useful since currently we automatically list servers as running
24871 and usable even if we know they're jerks.
24872 - Provide dire warnings to any users who set DirServer; move it out
24873 of torrc.sample and into torrc.complete.
24874 - Add MyFamily to torrc.sample in the server section.
24875 - Add nicknames to the DirServer line, so we can refer to them
24876 without requiring all our users to memorize their IP addresses.
24877 - When we get an EOF or a timeout on a directory connection, note
24878 how many bytes of serverdesc we are dropping. This will help
24879 us determine whether it is smart to parse incomplete serverdesc
24881 - Add a new function to "change pseudonyms" -- that is, to stop
24882 using any currently-dirty circuits for new streams, so we don't
24883 link new actions to old actions. Currently it's only called on
24884 HUP (or SIGNAL RELOAD).
24885 - On sighup, if UseHelperNodes changed to 1, use new circuits.
24886 - Start using RAND_bytes rather than RAND_pseudo_bytes from
24887 OpenSSL. Also, reseed our entropy every hour, not just at
24888 startup. And entropy in 512-bit chunks, not 160-bit chunks.
24890 o Fixes on 0.1.1.7-alpha:
24891 - Nobody ever implemented EVENT_ADDRMAP for control protocol
24892 version 0, so don't let version 0 controllers ask for it.
24893 - If you requested something with too many newlines via the
24894 v1 controller protocol, you could crash tor.
24895 - Fix a number of memory leaks, including some pretty serious ones.
24896 - Re-enable DirPort testing again, so Tor servers will be willing
24897 to advertise their DirPort if it's reachable.
24898 - On TLS handshake, only check the other router's nickname against
24899 its expected nickname if is_named is set.
24901 o Fixes forward-ported from 0.1.0.15:
24902 - Don't crash when we don't have any spare file descriptors and we
24903 try to spawn a dns or cpu worker.
24904 - Make the numbers in read-history and write-history into uint64s,
24905 so they don't overflow and publish negatives in the descriptor.
24907 o Fixes on 0.1.0.x:
24908 - For the OS X package's modified privoxy config file, comment
24909 out the "logfile" line so we don't log everything passed
24911 - We were whining about using socks4 or socks5-with-local-lookup
24912 even when it's an IP in the "virtual" range we designed exactly
24914 - We were leaking some memory every time the client changes IPs.
24915 - Never call free() on tor_malloc()d memory. This will help us
24916 use dmalloc to detect memory leaks.
24917 - Check for named servers when looking them up by nickname;
24918 warn when we'recalling a non-named server by its nickname;
24919 don't warn twice about the same name.
24920 - Try to list MyFamily elements by key, not by nickname, and warn
24921 if we've not heard of the server.
24922 - Make windows platform detection (uname equivalent) smarter.
24923 - It turns out sparc64 doesn't like unaligned access either.
24926 Changes in version 0.1.0.15 - 2005-09-23
24927 o Bugfixes on 0.1.0.x:
24928 - Reject ports 465 and 587 (spam targets) in default exit policy.
24929 - Don't crash when we don't have any spare file descriptors and we
24930 try to spawn a dns or cpu worker.
24931 - Get rid of IgnoreVersion undocumented config option, and make us
24932 only warn, never exit, when we're running an obsolete version.
24933 - Don't try to print a null string when your server finds itself to
24934 be unreachable and the Address config option is empty.
24935 - Make the numbers in read-history and write-history into uint64s,
24936 so they don't overflow and publish negatives in the descriptor.
24937 - Fix a minor memory leak in smartlist_string_remove().
24938 - We were only allowing ourselves to upload a server descriptor at
24939 most every 20 minutes, even if it changed earlier than that.
24940 - Clean up log entries that pointed to old URLs.
24943 Changes in version 0.1.1.7-alpha - 2005-09-14
24944 o Fixes on 0.1.1.6-alpha:
24945 - Exit servers were crashing when people asked them to make a
24946 connection to an address not in their exit policy.
24947 - Looking up a non-existent stream for a v1 control connection would
24949 - Fix a seg fault if we ask a dirserver for a descriptor by
24950 fingerprint but he doesn't know about him.
24951 - SETCONF was appending items to linelists, not clearing them.
24952 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
24953 out and refuse the setconf if it would fail.
24954 - Downgrade the dirserver log messages when whining about
24958 - Add Peter Palfrader's check-tor script to tor/contrib/
24959 It lets you easily check whether a given server (referenced by
24960 nickname) is reachable by you.
24961 - Numerous changes to move towards client-side v2 directories. Not
24964 o Fixes on 0.1.0.x:
24965 - If the user gave tor an odd number of command-line arguments,
24966 we were silently ignoring the last one. Now we complain and fail.
24967 [This wins the oldest-bug prize -- this bug has been present since
24968 November 2002, as released in Tor 0.0.0.]
24969 - Do not use unaligned memory access on alpha, mips, or mipsel.
24970 It *works*, but is very slow, so we treat them as if it doesn't.
24971 - Retry directory requests if we fail to get an answer we like
24972 from a given dirserver (we were retrying before, but only if
24973 we fail to connect).
24974 - When writing the RecommendedVersions line, sort them first.
24975 - When the client asked for a rendezvous port that the hidden
24976 service didn't want to provide, we were sending an IP address
24977 back along with the end cell. Fortunately, it was zero. But stop
24979 - Correct "your server is reachable" log entries to indicate that
24980 it was self-testing that told us so.
24983 Changes in version 0.1.1.6-alpha - 2005-09-09
24984 o Fixes on 0.1.1.5-alpha:
24985 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
24986 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
24987 - Fix bug with tor_memmem finding a match at the end of the string.
24988 - Make unit tests run without segfaulting.
24989 - Resolve some solaris x86 compile warnings.
24990 - Handle duplicate lines in approved-routers files without warning.
24991 - Fix bug where as soon as a server refused any requests due to his
24992 exit policy (e.g. when we ask for localhost and he tells us that's
24993 127.0.0.1 and he won't do it), we decided he wasn't obeying his
24994 exit policy using him for any exits.
24995 - Only do openssl hardware accelerator stuff if openssl version is
24998 o New controller features/fixes:
24999 - Add a "RESETCONF" command so you can set config options like
25000 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
25001 a config option in the torrc with no value, then it clears it
25002 entirely (rather than setting it to its default).
25003 - Add a "GETINFO config-file" to tell us where torrc is.
25004 - Avoid sending blank lines when GETINFO replies should be empty.
25005 - Add a QUIT command for the controller (for using it manually).
25006 - Fix a bug in SAVECONF that was adding default dirservers and
25007 other redundant entries to the torrc file.
25009 o Start on the new directory design:
25010 - Generate, publish, cache, serve new network-status format.
25011 - Publish individual descriptors (by fingerprint, by "all", and by
25013 - Publish client and server recommended versions separately.
25014 - Allow tor_gzip_uncompress() to handle multiple concatenated
25015 compressed strings. Serve compressed groups of router
25016 descriptors. The compression logic here could be more
25018 - Distinguish v1 authorities (all currently trusted directories)
25019 from v2 authorities (all trusted directories).
25020 - Change DirServers config line to note which dirs are v1 authorities.
25021 - Add configuration option "V1AuthoritativeDirectory 1" which
25022 moria1, moria2, and tor26 should set.
25023 - Remove option when getting directory cache to see whether they
25024 support running-routers; they all do now. Replace it with one
25025 to see whether caches support v2 stuff.
25028 - Dirservers now do their own external reachability testing of each
25029 Tor server, and only list them as running if they've been found to
25030 be reachable. We also send back warnings to the server's logs if
25031 it uploads a descriptor that we already believe is unreachable.
25032 - Implement exit enclaves: if we know an IP address for the
25033 destination, and there's a running Tor server at that address
25034 which allows exit to the destination, then extend the circuit to
25035 that exit first. This provides end-to-end encryption and end-to-end
25036 authentication. Also, if the user wants a .exit address or enclave,
25037 use 4 hops rather than 3, and cannibalize a general circ for it
25039 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
25040 controller. Also, rotate dns and cpu workers if the controller
25041 changes options that will affect them; and initialize the dns
25042 worker cache tree whether or not we start out as a server.
25043 - Only upload a new server descriptor when options change, 18
25044 hours have passed, uptime is reset, or bandwidth changes a lot.
25045 - Check [X-]Forwarded-For headers in HTTP requests when generating
25046 log messages. This lets people run dirservers (and caches) behind
25047 Apache but still know which IP addresses are causing warnings.
25049 o Config option changes:
25050 - Replace (Fascist)Firewall* config options with a new
25051 ReachableAddresses option that understands address policies.
25052 For example, "ReachableAddresses *:80,*:443"
25053 - Get rid of IgnoreVersion undocumented config option, and make us
25054 only warn, never exit, when we're running an obsolete version.
25055 - Make MonthlyAccountingStart config option truly obsolete now.
25057 o Fixes on 0.1.0.x:
25058 - Reject ports 465 and 587 in the default exit policy, since
25059 people have started using them for spam too.
25060 - It turns out we couldn't bootstrap a network since we added
25061 reachability detection in 0.1.0.1-rc. Good thing the Tor network
25062 has never gone down. Add an AssumeReachable config option to let
25063 servers and dirservers bootstrap. When we're trying to build a
25064 high-uptime or high-bandwidth circuit but there aren't enough
25065 suitable servers, try being less picky rather than simply failing.
25066 - Our logic to decide if the OR we connected to was the right guy
25067 was brittle and maybe open to a mitm for unverified routers.
25068 - We weren't cannibalizing circuits correctly for
25069 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
25070 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
25071 build those from scratch. This should make hidden services faster.
25072 - Predict required circuits better, with an eye toward making hidden
25073 services faster on the service end.
25074 - Retry streams if the exit node sends back a 'misc' failure. This
25075 should result in fewer random failures. Also, after failing
25076 from resolve failed or misc, reset the num failures, so we give
25077 it a fair shake next time we try.
25078 - Clean up the rendezvous warn log msgs, and downgrade some to info.
25079 - Reduce severity on logs about dns worker spawning and culling.
25080 - When we're shutting down and we do something like try to post a
25081 server descriptor or rendezvous descriptor, don't complain that
25082 we seem to be unreachable. Of course we are, we're shutting down.
25083 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
25084 We don't use them yet, but maybe one day our DNS resolver will be
25085 able to discover them.
25086 - Make ContactInfo mandatory for authoritative directory servers.
25087 - Require server descriptors to list IPv4 addresses -- hostnames
25088 are no longer allowed. This also fixes some potential security
25089 problems with people providing hostnames as their address and then
25090 preferentially resolving them to partition users.
25091 - Change log line for unreachability to explicitly suggest /etc/hosts
25092 as the culprit. Also make it clearer what IP address and ports we're
25093 testing for reachability.
25094 - Put quotes around user-supplied strings when logging so users are
25095 more likely to realize if they add bad characters (like quotes)
25097 - Let auth dir servers start without specifying an Address config
25099 - Make unit tests (and other invocations that aren't the real Tor)
25100 run without launching listeners, creating subdirectories, and so on.
25103 Changes in version 0.1.1.5-alpha - 2005-08-08
25104 o Bugfixes included in 0.1.0.14.
25106 o Bugfixes on 0.1.0.x:
25107 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
25108 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
25109 it would silently using ignore the 6668.
25112 Changes in version 0.1.0.14 - 2005-08-08
25113 o Bugfixes on 0.1.0.x:
25114 - Fix the other half of the bug with crypto handshakes
25116 - Fix an assert trigger if you send a 'signal term' via the
25117 controller when it's listening for 'event info' messages.
25120 Changes in version 0.1.1.4-alpha - 2005-08-04
25121 o Bugfixes included in 0.1.0.13.
25124 - Improve tor_gettimeofday() granularity on windows.
25125 - Make clients regenerate their keys when their IP address changes.
25126 - Implement some more GETINFO goodness: expose helper nodes, config
25127 options, getinfo keys.
25130 Changes in version 0.1.0.13 - 2005-08-04
25131 o Bugfixes on 0.1.0.x:
25132 - Fix a critical bug in the security of our crypto handshakes.
25133 - Fix a size_t underflow in smartlist_join_strings2() that made
25134 it do bad things when you hand it an empty smartlist.
25135 - Fix Windows installer to ship Tor license (thanks to Aphex for
25136 pointing out this oversight) and put a link to the doc directory
25138 - Explicitly set no-unaligned-access for sparc: it turns out the
25139 new gcc's let you compile broken code, but that doesn't make it
25143 Changes in version 0.1.1.3-alpha - 2005-07-23
25144 o Bugfixes on 0.1.1.2-alpha:
25145 - Fix a bug in handling the controller's "post descriptor"
25147 - Fix several bugs in handling the controller's "extend circuit"
25149 - Fix a bug in handling the controller's "stream status" event.
25150 - Fix an assert failure if we have a controller listening for
25151 circuit events and we go offline.
25152 - Re-allow hidden service descriptors to publish 0 intro points.
25153 - Fix a crash when generating your hidden service descriptor if
25154 you don't have enough intro points already.
25156 o New features on 0.1.1.2-alpha:
25157 - New controller function "getinfo accounting", to ask how
25158 many bytes we've used in this time period.
25159 - Experimental support for helper nodes: a lot of the risk from
25160 a small static adversary comes because users pick new random
25161 nodes every time they rebuild a circuit. Now users will try to
25162 stick to the same small set of entry nodes if they can. Not
25163 enabled by default yet.
25165 o Bugfixes on 0.1.0.12:
25166 - If you're an auth dir server, always publish your dirport,
25167 even if you haven't yet found yourself to be reachable.
25168 - Fix a size_t underflow in smartlist_join_strings2() that made
25169 it do bad things when you hand it an empty smartlist.
25172 Changes in version 0.1.0.12 - 2005-07-18
25173 o New directory servers:
25174 - tor26 has changed IP address.
25176 o Bugfixes on 0.1.0.x:
25177 - Fix a possible double-free in tor_gzip_uncompress().
25178 - When --disable-threads is set, do not search for or link against
25179 pthreads libraries.
25180 - Don't trigger an assert if an authoritative directory server
25181 claims its dirport is 0.
25182 - Fix bug with removing Tor as an NT service: some people were
25183 getting "The service did not return an error." Thanks to Matt
25187 Changes in version 0.1.1.2-alpha - 2005-07-15
25188 o New directory servers:
25189 - tor26 has changed IP address.
25191 o Bugfixes on 0.1.0.x, crashes/leaks:
25192 - Port the servers-not-obeying-their-exit-policies fix from
25194 - Fix an fd leak in start_daemon().
25195 - On Windows, you can't always reopen a port right after you've
25196 closed it. So change retry_listeners() to only close and re-open
25197 ports that have changed.
25198 - Fix a possible double-free in tor_gzip_uncompress().
25200 o Bugfixes on 0.1.0.x, usability:
25201 - When tor_socketpair() fails in Windows, give a reasonable
25202 Windows-style errno back.
25203 - Let people type "tor --install" as well as "tor -install" when
25205 want to make it an NT service.
25206 - NT service patch from Matt Edman to improve error messages.
25207 - When the controller asks for a config option with an abbreviated
25208 name, give the full name in our response.
25209 - Correct the man page entry on TrackHostExitsExpire.
25210 - Looks like we were never delivering deflated (i.e. compressed)
25211 running-routers lists, even when asked. Oops.
25212 - When --disable-threads is set, do not search for or link against
25213 pthreads libraries.
25215 o Bugfixes on 0.1.1.x:
25216 - Fix a seg fault with autodetecting which controller version is
25220 - New hidden service descriptor format: put a version in it, and
25221 let people specify introduction/rendezvous points that aren't
25222 in "the directory" (which is subjective anyway).
25223 - Allow the DEBUG controller event to work again. Mark certain log
25224 entries as "don't tell this to controllers", so we avoid cycles.
25227 Changes in version 0.1.0.11 - 2005-06-30
25228 o Bugfixes on 0.1.0.x:
25229 - Fix major security bug: servers were disregarding their
25230 exit policies if clients behaved unexpectedly.
25231 - Make OS X init script check for missing argument, so we don't
25232 confuse users who invoke it incorrectly.
25233 - Fix a seg fault in "tor --hash-password foo".
25234 - The MAPADDRESS control command was broken.
25237 Changes in version 0.1.1.1-alpha - 2005-06-29
25239 - Make OS X init script check for missing argument, so we don't
25240 confuse users who invoke it incorrectly.
25241 - Fix a seg fault in "tor --hash-password foo".
25242 - Fix a possible way to DoS dirservers.
25243 - When we complain that your exit policy implicitly allows local or
25244 private address spaces, name them explicitly so operators can
25246 - Make the log message less scary when all the dirservers are
25247 temporarily unreachable.
25248 - We were printing the number of idle dns workers incorrectly when
25252 - Revised controller protocol (version 1) that uses ascii rather
25253 than binary. Add supporting libraries in python and java so you
25254 can use the controller from your applications without caring how
25255 our protocol works.
25256 - Spiffy new support for crypto hardware accelerators. Can somebody
25260 Changes in version 0.0.9.10 - 2005-06-16
25261 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
25262 - Refuse relay cells that claim to have a length larger than the
25263 maximum allowed. This prevents a potential attack that could read
25264 arbitrary memory (e.g. keys) from an exit server's process
25268 Changes in version 0.1.0.10 - 2005-06-14
25269 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
25270 libevent before 1.1a.
25273 Changes in version 0.1.0.9-rc - 2005-06-09
25275 - Reset buf->highwater every time buf_shrink() is called, not just on
25276 a successful shrink. This was causing significant memory bloat.
25277 - Fix buffer overflow when checking hashed passwords.
25278 - Security fix: if seeding the RNG on Win32 fails, quit.
25279 - Allow seeding the RNG on Win32 even when you're not running as
25281 - Disable threading on Solaris too. Something is wonky with it,
25282 cpuworkers, and reentrant libs.
25283 - Reenable the part of the code that tries to flush as soon as an
25284 OR outbuf has a full TLS record available. Perhaps this will make
25285 OR outbufs not grow as huge except in rare cases, thus saving lots
25286 of CPU time plus memory.
25287 - Reject malformed .onion addresses rather then passing them on as
25288 normal web requests.
25289 - Adapt patch from Adam Langley: fix possible memory leak in
25290 tor_lookup_hostname().
25291 - Initialize libevent later in the startup process, so the logs are
25292 already established by the time we start logging libevent warns.
25293 - Use correct errno on win32 if libevent fails.
25294 - Check and warn about known-bad/slow libevent versions.
25295 - Pay more attention to the ClientOnly config option.
25296 - Have torctl.in/tor.sh.in check for location of su binary (needed
25298 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
25299 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
25300 HttpProxyAuthenticator
25301 - Stop warning about sigpipes in the logs. We're going to
25302 pretend that getting these occasionally is normal and fine.
25303 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
25305 installer screens; and don't put stuff into StartupItems unless
25306 the user asks you to.
25307 - Require servers that use the default dirservers to have public IP
25308 addresses. We have too many servers that are configured with private
25309 IPs and their admins never notice the log entries complaining that
25310 their descriptors are being rejected.
25311 - Add OSX uninstall instructions. An actual uninstall script will
25315 Changes in version 0.1.0.8-rc - 2005-05-23
25317 - It turns out that kqueue on OS X 10.3.9 was causing kernel
25318 panics. Disable kqueue on all OS X Tors.
25319 - Fix RPM: remove duplicate line accidentally added to the rpm
25321 - Disable threads on openbsd too, since its gethostaddr is not
25323 - Tolerate libevent 0.8 since it still works, even though it's
25325 - Enable building on Red Hat 9.0 again.
25326 - Allow the middle hop of the testing circuit to be running any
25327 version, now that most of them have the bugfix to let them connect
25328 to unknown servers. This will allow reachability testing to work
25329 even when 0.0.9.7-0.0.9.9 become obsolete.
25330 - Handle relay cells with rh.length too large. This prevents
25331 a potential attack that could read arbitrary memory (maybe even
25332 keys) from the exit server's process.
25333 - We screwed up the dirport reachability testing when we don't yet
25334 have a cached version of the directory. Hopefully now fixed.
25335 - Clean up router_load_single_router() (used by the controller),
25336 so it doesn't seg fault on error.
25337 - Fix a minor memory leak when somebody establishes an introduction
25338 point at your Tor server.
25339 - If a socks connection ends because read fails, don't warn that
25340 you're not sending a socks reply back.
25343 - Add HttpProxyAuthenticator config option too, that works like
25344 the HttpsProxyAuthenticator config option.
25345 - Encode hashed controller passwords in hex instead of base64,
25346 to make it easier to write controllers.
25349 Changes in version 0.1.0.7-rc - 2005-05-17
25351 - Fix a bug in the OS X package installer that prevented it from
25352 installing on Tiger.
25353 - Fix a script bug in the OS X package installer that made it
25354 complain during installation.
25355 - Find libevent even if it's hiding in /usr/local/ and your
25356 CFLAGS and LDFLAGS don't tell you to look there.
25357 - Be able to link with libevent as a shared library (the default
25358 after 1.0d), even if it's hiding in /usr/local/lib and even
25359 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
25360 assuming you're running gcc. Otherwise fail and give a useful
25362 - Fix a bug in the RPM packager: set home directory for _tor to
25363 something more reasonable when first installing.
25364 - Free a minor amount of memory that is still reachable on exit.
25367 Changes in version 0.1.0.6-rc - 2005-05-14
25369 - Implement --disable-threads configure option. Disable threads on
25370 netbsd by default, because it appears to have no reentrant resolver
25372 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
25373 release (1.1) detects and disables kqueue if it's broken.
25374 - Append default exit policy before checking for implicit internal
25375 addresses. Now we don't log a bunch of complaints on startup
25376 when using the default exit policy.
25377 - Some people were putting "Address " in their torrc, and they had
25378 a buggy resolver that resolved " " to 0.0.0.0. Oops.
25379 - If DataDir is ~/.tor, and that expands to /.tor, then default to
25380 LOCALSTATEDIR/tor instead.
25381 - Fix fragmented-message bug in TorControl.py.
25382 - Resolve a minor bug which would prevent unreachable dirports
25383 from getting suppressed in the published descriptor.
25384 - When the controller gave us a new descriptor, we weren't resolving
25385 it immediately, so Tor would think its address was 0.0.0.0 until
25386 we fetched a new directory.
25387 - Fix an uppercase/lowercase case error in suppressing a bogus
25388 libevent warning on some Linuxes.
25391 - Begin scrubbing sensitive strings from logs by default. Turn off
25392 the config option SafeLogging if you need to do debugging.
25393 - Switch to a new buffer management algorithm, which tries to avoid
25394 reallocing and copying quite as much. In first tests it looks like
25395 it uses *more* memory on average, but less cpu.
25396 - First cut at support for "create-fast" cells. Clients can use
25397 these when extending to their first hop, since the TLS already
25398 provides forward secrecy and authentication. Not enabled on
25400 - When dirservers refuse a router descriptor, we now log its
25401 contactinfo, platform, and the poster's IP address.
25402 - Call tor_free_all instead of connections_free_all after forking, to
25403 save memory on systems that need to fork.
25404 - Whine at you if you're a server and you don't set your contactinfo.
25405 - Implement --verify-config command-line option to check if your torrc
25406 is valid without actually launching Tor.
25407 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
25408 rather than just rejecting it.
25411 Changes in version 0.1.0.5-rc - 2005-04-27
25413 - Stop trying to print a null pointer if an OR conn fails because
25414 we didn't like its cert.
25416 - Switch our internal buffers implementation to use a ring buffer,
25417 to hopefully improve performance for fast servers a lot.
25418 - Add HttpsProxyAuthenticator support (basic auth only), based
25419 on patch from Adam Langley.
25420 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
25421 the fast servers that have been joining lately.
25422 - Give hidden service accesses extra time on the first attempt,
25423 since 60 seconds is often only barely enough. This might improve
25425 - Improve performance for dirservers: stop re-parsing the whole
25426 directory every time you regenerate it.
25427 - Add more debugging info to help us find the weird dns freebsd
25428 pthreads bug; cleaner debug messages to help track future issues.
25431 Changes in version 0.0.9.9 - 2005-04-23
25432 o Bugfixes on 0.0.9.x:
25433 - If unofficial Tor clients connect and send weird TLS certs, our
25434 Tor server triggers an assert. This release contains a minimal
25435 backport from the broader fix that we put into 0.1.0.4-rc.
25438 Changes in version 0.1.0.4-rc - 2005-04-23
25440 - If unofficial Tor clients connect and send weird TLS certs, our
25441 Tor server triggers an assert. Stop asserting, and start handling
25442 TLS errors better in other situations too.
25443 - When the controller asks us to tell it about all the debug-level
25444 logs, it turns out we were generating debug-level logs while
25445 telling it about them, which turns into a bad loop. Now keep
25446 track of whether you're sending a debug log to the controller,
25447 and don't log when you are.
25448 - Fix the "postdescriptor" feature of the controller interface: on
25449 non-complete success, only say "done" once.
25451 - Clients are now willing to load balance over up to 2mB, not 1mB,
25452 of advertised bandwidth capacity.
25453 - Add a NoPublish config option, so you can be a server (e.g. for
25454 testing running Tor servers in other Tor networks) without
25455 publishing your descriptor to the primary dirservers.
25458 Changes in version 0.1.0.3-rc - 2005-04-08
25459 o Improvements on 0.1.0.2-rc:
25460 - Client now retries when streams end early for 'hibernating' or
25461 'resource limit' reasons, rather than failing them.
25462 - More automated handling for dirserver operators:
25463 - Automatically approve nodes running 0.1.0.2-rc or later,
25464 now that the the reachability detection stuff is working.
25465 - Now we allow two unverified servers with the same nickname
25466 but different keys. But if a nickname is verified, only that
25467 nickname+key are allowed.
25468 - If you're an authdirserver connecting to an address:port,
25469 and it's not the OR you were expecting, forget about that
25470 descriptor. If he *was* the one you were expecting, then forget
25471 about all other descriptors for that address:port.
25472 - Allow servers to publish descriptors from 12 hours in the future.
25473 Corollary: only whine about clock skew from the dirserver if
25474 he's a trusted dirserver (since now even verified servers could
25475 have quite wrong clocks).
25476 - Adjust maximum skew and age for rendezvous descriptors: let skew
25477 be 48 hours rather than 90 minutes.
25478 - Efficiency improvements:
25479 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
25480 it much faster to look up a circuit for each relay cell.
25481 - Remove most calls to assert_all_pending_dns_resolves_ok(),
25482 since they're eating our cpu on exit nodes.
25483 - Stop wasting time doing a case insensitive comparison for every
25484 dns name every time we do any lookup. Canonicalize the names to
25485 lowercase and be done with it.
25486 - Start sending 'truncated' cells back rather than destroy cells,
25487 if the circuit closes in front of you. This means we won't have
25488 to abandon partially built circuits.
25489 - Only warn once per nickname from add_nickname_list_to_smartlist
25490 per failure, so an entrynode or exitnode choice that's down won't
25492 - Put a note in the torrc about abuse potential with the default
25494 - Revise control spec and implementation to allow all log messages to
25495 be sent to controller with their severities intact (suggested by
25496 Matt Edman). Update TorControl to handle new log event types.
25497 - Provide better explanation messages when controller's POSTDESCRIPTOR
25499 - Stop putting nodename in the Platform string in server descriptors.
25500 It doesn't actually help, and it is confusing/upsetting some people.
25502 o Bugfixes on 0.1.0.2-rc:
25503 - We were printing the host mask wrong in exit policies in server
25504 descriptors. This isn't a critical bug though, since we were still
25505 obeying the exit policy internally.
25506 - Fix Tor when compiled with libevent but without pthreads: move
25507 connection_unregister() from _connection_free() to
25509 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
25510 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
25511 when we look through the connection array, we'll find any of the
25512 cpu/dnsworkers. This is no good.
25514 o Bugfixes on 0.0.9.8:
25515 - Fix possible bug on threading platforms (e.g. win32) which was
25516 leaking a file descriptor whenever a cpuworker or dnsworker died.
25517 - When using preferred entry or exit nodes, ignore whether the
25518 circuit wants uptime or capacity. They asked for the nodes, they
25520 - chdir() to your datadirectory at the *end* of the daemonize process,
25521 not the beginning. This was a problem because the first time you
25522 run tor, if your datadir isn't there, and you have runasdaemon set
25523 to 1, it will try to chdir to it before it tries to create it. Oops.
25524 - Handle changed router status correctly when dirserver reloads
25525 fingerprint file. We used to be dropping all unverified descriptors
25526 right then. The bug was hidden because we would immediately
25527 fetch a directory from another dirserver, which would include the
25528 descriptors we just dropped.
25529 - When we're connecting to an OR and he's got a different nickname/key
25530 than we were expecting, only complain loudly if we're an OP or a
25531 dirserver. Complaining loudly to the OR admins just confuses them.
25532 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
25533 artificially capped at 500kB.
25536 Changes in version 0.0.9.8 - 2005-04-07
25537 o Bugfixes on 0.0.9.x:
25538 - We have a bug that I haven't found yet. Sometimes, very rarely,
25539 cpuworkers get stuck in the 'busy' state, even though the cpuworker
25540 thinks of itself as idle. This meant that no new circuits ever got
25541 established. Here's a workaround to kill any cpuworker that's been
25542 busy for more than 100 seconds.
25545 Changes in version 0.1.0.2-rc - 2005-04-01
25546 o Bugfixes on 0.1.0.1-rc:
25547 - Fixes on reachability detection:
25548 - Don't check for reachability while hibernating.
25549 - If ORPort is reachable but DirPort isn't, still publish the
25550 descriptor, but zero out DirPort until it's found reachable.
25551 - When building testing circs for ORPort testing, use only
25552 high-bandwidth nodes, so fewer circuits fail.
25553 - Complain about unreachable ORPort separately from unreachable
25554 DirPort, so the user knows what's going on.
25555 - Make sure we only conclude ORPort reachability if we didn't
25556 initiate the conn. Otherwise we could falsely conclude that
25557 we're reachable just because we connected to the guy earlier
25558 and he used that same pipe to extend to us.
25559 - Authdirservers shouldn't do ORPort reachability detection,
25560 since they're in clique mode, so it will be rare to find a
25561 server not already connected to them.
25562 - When building testing circuits, always pick middle hops running
25563 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
25564 bug. (This is a kludge; it will go away when 0.0.9.x becomes
25566 - When we decide we're reachable, actually publish our descriptor
25568 - Fix bug in redirectstream in the controller.
25569 - Fix the state descriptor strings so logs don't claim edge streams
25570 are in a different state than they actually are.
25571 - Use recent libevent features when possible (this only really affects
25572 win32 and osx right now, because the new libevent with these
25573 features hasn't been released yet). Add code to suppress spurious
25575 - Prevent possible segfault in connection_close_unattached_ap().
25576 - Fix newlines on torrc in win32.
25577 - Improve error msgs when tor-resolve fails.
25579 o Improvements on 0.0.9.x:
25580 - New experimental script tor/contrib/ExerciseServer.py (needs more
25581 work) that uses the controller interface to build circuits and
25582 fetch pages over them. This will help us bootstrap servers that
25583 have lots of capacity but haven't noticed it yet.
25584 - New experimental script tor/contrib/PathDemo.py (needs more work)
25585 that uses the controller interface to let you choose whole paths
25587 "<hostname>.<path,separated by dots>.<length of path>.path"
25588 - When we've connected to an OR and handshaked but didn't like
25589 the result, we were closing the conn without sending destroy
25590 cells back for pending circuits. Now send those destroys.
25593 Changes in version 0.0.9.7 - 2005-04-01
25594 o Bugfixes on 0.0.9.x:
25595 - Fix another race crash bug (thanks to Glenn Fink for reporting).
25596 - Compare identity to identity, not to nickname, when extending to
25597 a router not already in the directory. This was preventing us from
25598 extending to unknown routers. Oops.
25599 - Make sure to create OS X Tor user in <500 range, so we aren't
25600 creating actual system users.
25601 - Note where connection-that-hasn't-sent-end was marked, and fix
25602 a few really loud instances of this harmless bug (it's fixed more
25606 Changes in version 0.1.0.1-rc - 2005-03-28
25608 - Add reachability testing. Your Tor server will automatically try
25609 to see if its ORPort and DirPort are reachable from the outside,
25610 and it won't upload its descriptor until it decides they are.
25611 - Handle unavailable hidden services better. Handle slow or busy
25612 hidden services better.
25613 - Add support for CONNECTing through https proxies, with "HttpsProxy"
25615 - New exit policy: accept most low-numbered ports, rather than
25616 rejecting most low-numbered ports.
25617 - More Tor controller support (still experimental). See
25618 http://tor.eff.org/doc/control-spec.txt for all the new features,
25619 including signals to emulate unix signals from any platform;
25620 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
25621 closestream; closecircuit; etc.
25622 - Make nt services work and start on startup on win32 (based on
25623 patch by Matt Edman).
25624 - Add a new AddressMap config directive to rewrite incoming socks
25625 addresses. This lets you, for example, declare an implicit
25626 required exit node for certain sites.
25627 - Add a new TrackHostExits config directive to trigger addressmaps
25628 for certain incoming socks addresses -- for sites that break when
25629 your exit keeps changing (based on patch by Mike Perry).
25630 - Redo the client-side dns cache so it's just an addressmap too.
25631 - Notice when our IP changes, and reset stats/uptime/reachability.
25632 - When an application is using socks5, give him the whole variety of
25633 potential socks5 responses (connect refused, host unreachable, etc),
25634 rather than just "success" or "failure".
25635 - A more sane version numbering system. See
25636 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
25637 - New contributed script "exitlist": a simple python script to
25638 parse directories and find Tor nodes that exit to listed
25640 - New contributed script "privoxy-tor-toggle" to toggle whether
25641 Privoxy uses Tor. Seems to be configured for Debian by default.
25642 - Report HTTP reasons to client when getting a response from directory
25643 servers -- so you can actually know what went wrong.
25644 - New config option MaxAdvertisedBandwidth which lets you advertise
25645 a low bandwidthrate (to not attract as many circuits) while still
25646 allowing a higher bandwidthrate in reality.
25648 o Robustness/stability fixes:
25649 - Make Tor use Niels Provos's libevent instead of its current
25650 poll-but-sometimes-select mess. This will let us use faster async
25651 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
25653 - pthread support now too. This was forced because when we forked,
25654 we ended up wasting a lot of duplicate ram over time. Also switch
25655 to foo_r versions of some library calls to allow reentry and
25657 - Better handling for heterogeneous / unreliable nodes:
25658 - Annotate circuits w/ whether they aim to contain high uptime nodes
25659 and/or high capacity nodes. When building circuits, choose
25661 - This means that every single node in an intro rend circuit,
25662 not just the last one, will have a minimum uptime.
25663 - New config option LongLivedPorts to indicate application streams
25664 that will want high uptime circuits.
25665 - Servers reset uptime when a dir fetch entirely fails. This
25666 hopefully reflects stability of the server's network connectivity.
25667 - If somebody starts his tor server in Jan 2004 and then fixes his
25668 clock, don't make his published uptime be a year.
25669 - Reset published uptime when you wake up from hibernation.
25670 - Introduce a notion of 'internal' circs, which are chosen without
25671 regard to the exit policy of the last hop. Intro and rendezvous
25672 circs must be internal circs, to avoid leaking information. Resolve
25673 and connect streams can use internal circs if they want.
25674 - New circuit pooling algorithm: make sure to have enough circs around
25675 to satisfy any predicted ports, and also make sure to have 2 internal
25676 circs around if we've required internal circs lately (and with high
25677 uptime if we've seen that lately too).
25678 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
25679 which describes how often we retry making new circuits if current
25680 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
25681 how long we're willing to make use of an already-dirty circuit.
25682 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
25683 circ as necessary, if there are any completed ones lying around
25684 when we try to launch one.
25685 - Make hidden services try to establish a rendezvous for 30 seconds,
25686 rather than for n (where n=3) attempts to build a circuit.
25687 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
25688 "ShutdownWaitLength".
25689 - Try to be more zealous about calling connection_edge_end when
25690 things go bad with edge conns in connection.c.
25691 - Revise tor-spec to add more/better stream end reasons.
25692 - Revise all calls to connection_edge_end to avoid sending "misc",
25693 and to take errno into account where possible.
25696 - Fix a race condition that can trigger an assert, when we have a
25697 pending create cell and an OR connection fails right then.
25698 - Fix several double-mark-for-close bugs, e.g. where we were finding
25699 a conn for a cell even if that conn is already marked for close.
25700 - Make sequence of log messages when starting on win32 with no config
25701 file more reasonable.
25702 - When choosing an exit node for a new non-internal circ, don't take
25703 into account whether it'll be useful for any pending x.onion
25704 addresses -- it won't.
25705 - Turn addr_policy_compare from a tristate to a quadstate; this should
25706 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
25707 for google.com" problem.
25708 - Make "platform" string in descriptor more accurate for Win32 servers,
25709 so it's not just "unknown platform".
25710 - Fix an edge case in parsing config options (thanks weasel).
25711 If they say "--" on the commandline, it's not an option.
25712 - Reject odd-looking addresses at the client (e.g. addresses that
25713 contain a colon), rather than having the server drop them because
25715 - tor-resolve requests were ignoring .exit if there was a working circuit
25716 they could use instead.
25717 - REUSEADDR on normal platforms means you can rebind to the port
25718 right after somebody else has let it go. But REUSEADDR on win32
25719 means to let you bind to the port _even when somebody else
25720 already has it bound_! So, don't do that on Win32.
25721 - Change version parsing logic: a version is "obsolete" if it is not
25722 recommended and (1) there is a newer recommended version in the
25723 same series, or (2) there are no recommended versions in the same
25724 series, but there are some recommended versions in a newer series.
25725 A version is "new" if it is newer than any recommended version in
25727 - Stop most cases of hanging up on a socks connection without sending
25731 - Require BandwidthRate to be at least 20kB/s for servers.
25732 - When a dirserver causes you to give a warn, mention which dirserver
25734 - New config option DirAllowPrivateAddresses for authdirservers.
25735 Now by default they refuse router descriptors that have non-IP or
25736 private-IP addresses.
25737 - Stop publishing socksport in the directory, since it's not
25738 actually meant to be public. For compatibility, publish a 0 there
25740 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
25741 smart" value, that is low for servers and high for clients.
25742 - If our clock jumps forward by 100 seconds or more, assume something
25743 has gone wrong with our network and abandon all not-yet-used circs.
25744 - Warn when exit policy implicitly allows local addresses.
25745 - If we get an incredibly skewed timestamp from a dirserver mirror
25746 that isn't a verified OR, don't warn -- it's probably him that's
25748 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
25749 cookies to disk and doesn't log each web request to disk. (Thanks
25750 to Brett Carrington for pointing this out.)
25751 - When a client asks us for a dir mirror and we don't have one,
25752 launch an attempt to get a fresh one.
25753 - If we're hibernating and we get a SIGINT, exit immediately.
25754 - Add --with-dmalloc ./configure option, to track memory leaks.
25755 - And try to free all memory on closing, so we can detect what
25757 - Cache local dns resolves correctly even when they're .exit
25759 - Give a better warning when some other server advertises an
25760 ORPort that is actually an apache running ssl.
25761 - Add "opt hibernating 1" to server descriptor to make it clearer
25762 whether the server is hibernating.
25765 Changes in version 0.0.9.6 - 2005-03-24
25766 o Bugfixes on 0.0.9.x (crashes and asserts):
25767 - Add new end stream reasons to maintenance branch. Fix bug where
25768 reason (8) could trigger an assert. Prevent bug from recurring.
25769 - Apparently win32 stat wants paths to not end with a slash.
25770 - Fix assert triggers in assert_cpath_layer_ok(), where we were
25771 blowing away the circuit that conn->cpath_layer points to, then
25772 checking to see if the circ is well-formed. Backport check to make
25773 sure we dont use the cpath on a closed connection.
25774 - Prevent circuit_resume_edge_reading_helper() from trying to package
25775 inbufs for marked-for-close streams.
25776 - Don't crash on hup if your options->address has become unresolvable.
25777 - Some systems (like OS X) sometimes accept() a connection and tell
25778 you the remote host is 0.0.0.0:0. If this happens, due to some
25779 other mis-features, we get confused; so refuse the conn for now.
25781 o Bugfixes on 0.0.9.x (other):
25782 - Fix harmless but scary "Unrecognized content encoding" warn message.
25783 - Add new stream error reason: TORPROTOCOL reason means "you are not
25784 speaking a version of Tor I understand; say bye-bye to your stream."
25785 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
25786 into the future, now that we are more tolerant of skew. This
25787 resolves a bug where a Tor server would refuse to cache a directory
25788 because all the directories it gets are too far in the future;
25789 yet the Tor server never logs any complaints about clock skew.
25790 - Mac packaging magic: make man pages useable, and do not overwrite
25791 existing torrc files.
25792 - Make OS X log happily to /var/log/tor/tor.log
25795 Changes in version 0.0.9.5 - 2005-02-22
25796 o Bugfixes on 0.0.9.x:
25797 - Fix an assert race at exit nodes when resolve requests fail.
25798 - Stop picking unverified dir mirrors--it only leads to misery.
25799 - Patch from Matt Edman to make NT services work better. Service
25800 support is still not compiled into the executable by default.
25801 - Patch from Dmitri Bely so the Tor service runs better under
25802 the win32 SYSTEM account.
25803 - Make tor-resolve actually work (?) on Win32.
25804 - Fix a sign bug when getrlimit claims to have 4+ billion
25805 file descriptors available.
25806 - Stop refusing to start when bandwidthburst == bandwidthrate.
25807 - When create cells have been on the onion queue more than five
25808 seconds, just send back a destroy and take them off the list.
25811 Changes in version 0.0.9.4 - 2005-02-03
25812 o Bugfixes on 0.0.9:
25813 - Fix an assert bug that took down most of our servers: when
25814 a server claims to have 1 GB of bandwidthburst, don't
25816 - Don't crash as badly if we have spawned the max allowed number
25817 of dnsworkers, or we're out of file descriptors.
25818 - Block more file-sharing ports in the default exit policy.
25819 - MaxConn is now automatically set to the hard limit of max
25820 file descriptors we're allowed (ulimit -n), minus a few for
25822 - Give a clearer message when servers need to raise their
25823 ulimit -n when they start running out of file descriptors.
25824 - SGI Compatibility patches from Jan Schaumann.
25825 - Tolerate a corrupt cached directory better.
25826 - When a dirserver hasn't approved your server, list which one.
25827 - Go into soft hibernation after 95% of the bandwidth is used,
25828 not 99%. This is especially important for daily hibernators who
25829 have a small accounting max. Hopefully it will result in fewer
25830 cut connections when the hard hibernation starts.
25831 - Load-balance better when using servers that claim more than
25832 800kB/s of capacity.
25833 - Make NT services work (experimental, only used if compiled in).
25836 Changes in version 0.0.9.3 - 2005-01-21
25837 o Bugfixes on 0.0.9:
25838 - Backport the cpu use fixes from main branch, so busy servers won't
25839 need as much processor time.
25840 - Work better when we go offline and then come back, or when we
25841 run Tor at boot before the network is up. We do this by
25842 optimistically trying to fetch a new directory whenever an
25843 application request comes in and we think we're offline -- the
25844 human is hopefully a good measure of when the network is back.
25845 - Backport some minimal hidserv bugfixes: keep rend circuits open as
25846 long as you keep using them; actually publish hidserv descriptors
25847 shortly after they change, rather than waiting 20-40 minutes.
25848 - Enable Mac startup script by default.
25849 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
25850 - When you update AllowUnverifiedNodes or FirewallPorts via the
25851 controller's setconf feature, we were always appending, never
25853 - When you update HiddenServiceDir via setconf, it was screwing up
25854 the order of reading the lines, making it fail.
25855 - Do not rewrite a cached directory back to the cache; otherwise we
25856 will think it is recent and not fetch a newer one on startup.
25857 - Workaround for webservers that lie about Content-Encoding: Tor
25858 now tries to autodetect compressed directories and compression
25859 itself. This lets us Proxypass dir fetches through apache.
25862 Changes in version 0.0.9.2 - 2005-01-04
25863 o Bugfixes on 0.0.9 (crashes and asserts):
25864 - Fix an assert on startup when the disk is full and you're logging
25866 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
25867 style address, then we'd crash.
25868 - Fix an assert trigger when the running-routers string we get from
25869 a dirserver is broken.
25870 - Make worker threads start and run on win32. Now win32 servers
25872 - Bandaid (not actually fix, but now it doesn't crash) an assert
25873 where the dns worker dies mysteriously and the main Tor process
25874 doesn't remember anything about the address it was resolving.
25876 o Bugfixes on 0.0.9 (Win32):
25877 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
25878 name out of the warning/assert messages.
25879 - Fix a superficial "unhandled error on read" bug on win32.
25880 - The win32 installer no longer requires a click-through for our
25881 license, since our Free Software license grants rights but does not
25883 - Win32: When connecting to a dirserver fails, try another one
25884 immediately. (This was already working for non-win32 Tors.)
25885 - Stop trying to parse $HOME on win32 when hunting for default
25887 - Make tor-resolve.c work on win32 by calling network_init().
25889 o Bugfixes on 0.0.9 (other):
25890 - Make 0.0.9.x build on Solaris again.
25891 - Due to a fencepost error, we were blowing away the \n when reporting
25892 confvalue items in the controller. So asking for multiple config
25893 values at once couldn't work.
25894 - When listing circuits that are pending on an opening OR connection,
25895 if we're an OR we were listing circuits that *end* at us as
25896 being pending on every listener, dns/cpu worker, etc. Stop that.
25897 - Dirservers were failing to create 'running-routers' or 'directory'
25898 strings if we had more than some threshold of routers. Fix them so
25899 they can handle any number of routers.
25900 - Fix a superficial "Duplicate mark for close" bug.
25901 - Stop checking for clock skew for OR connections, even for servers.
25902 - Fix a fencepost error that was chopping off the last letter of any
25903 nickname that is the maximum allowed nickname length.
25904 - Update URLs in log messages so they point to the new website.
25905 - Fix a potential problem in mangling server private keys while
25906 writing to disk (not triggered yet, as far as we know).
25907 - Include the licenses for other free software we include in Tor,
25908 now that we're shipping binary distributions more regularly.
25911 Changes in version 0.0.9.1 - 2004-12-15
25912 o Bugfixes on 0.0.9:
25913 - Make hibernation actually work.
25914 - Make HashedControlPassword config option work.
25915 - When we're reporting event circuit status to a controller,
25916 don't use the stream status code.
25919 Changes in version 0.0.9 - 2004-12-12
25921 - Clean up manpage and torrc.sample file.
25922 - Clean up severities and text of log warnings.
25924 - Make servers trigger an assert when they enter hibernation.
25927 Changes in version 0.0.9rc7 - 2004-12-08
25928 o Bugfixes on 0.0.9rc:
25929 - Fix a stack-trashing crash when an exit node begins hibernating.
25930 - Avoid looking at unallocated memory while considering which
25931 ports we need to build circuits to cover.
25932 - Stop a sigpipe: when an 'end' cell races with eof from the app,
25933 we shouldn't hold-open-until-flush if the eof arrived first.
25934 - Fix a bug with init_cookie_authentication() in the controller.
25935 - When recommending new-format log lines, if the upper bound is
25936 LOG_ERR, leave it implicit.
25938 o Bugfixes on 0.0.8.1:
25939 - Fix a whole slew of memory leaks.
25940 - Fix isspace() and friends so they still make Solaris happy
25941 but also so they don't trigger asserts on win32.
25942 - Fix parse_iso_time on platforms without strptime (eg win32).
25943 - win32: tolerate extra "readable" events better.
25944 - win32: when being multithreaded, leave parent fdarray open.
25945 - Make unit tests work on win32.
25948 Changes in version 0.0.9rc6 - 2004-12-06
25949 o Bugfixes on 0.0.9pre:
25950 - Clean up some more integer underflow opportunities (not exploitable
25952 - While hibernating, hup should not regrow our listeners.
25953 - Send an end to the streams we close when we hibernate, rather
25954 than just chopping them off.
25955 - React to eof immediately on non-open edge connections.
25957 o Bugfixes on 0.0.8.1:
25958 - Calculate timeout for waiting for a connected cell from the time
25959 we sent the begin cell, not from the time the stream started. If
25960 it took a long time to establish the circuit, we would time out
25961 right after sending the begin cell.
25962 - Fix router_compare_addr_to_addr_policy: it was not treating a port
25963 of * as always matching, so we were picking reject *:* nodes as
25964 exit nodes too. Oops.
25967 - New circuit building strategy: keep a list of ports that we've
25968 used in the past 6 hours, and always try to have 2 circuits open
25969 or on the way that will handle each such port. Seed us with port
25970 80 so web users won't complain that Tor is "slow to start up".
25971 - Make kill -USR1 dump more useful stats about circuits.
25972 - When warning about retrying or giving up, print the address, so
25973 the user knows which one it's talking about.
25974 - If you haven't used a clean circuit in an hour, throw it away,
25975 just to be on the safe side. (This means after 6 hours a totally
25976 unused Tor client will have no circuits open.)
25979 Changes in version 0.0.9rc5 - 2004-12-01
25980 o Bugfixes on 0.0.8.1:
25981 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
25982 - Let resolve conns retry/expire also, rather than sticking around
25984 - If we are using select, make sure we stay within FD_SETSIZE.
25986 o Bugfixes on 0.0.9pre:
25987 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
25988 but doesn't seem to be currently; thanks to Ilja van Sprundel for
25990 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
25991 instead. Impose minima and maxima for all *Period options; impose
25992 even tighter maxima for fetching if we are a caching dirserver.
25993 Clip rather than rejecting.
25994 - Fetch cached running-routers from servers that serve it (that is,
25995 authdirservers and servers running 0.0.9rc5-cvs or later.)
25998 - Accept *:706 (silc) in default exit policy.
25999 - Implement new versioning format for post 0.1.
26000 - Support "foo.nickname.exit" addresses, to let Alice request the
26001 address "foo" as viewed by exit node "nickname". Based on a patch
26003 - Make tor --version --version dump the cvs Id of every file.
26006 Changes in version 0.0.9rc4 - 2004-11-28
26007 o Bugfixes on 0.0.8.1:
26008 - Make windows sockets actually non-blocking (oops), and handle
26009 win32 socket errors better.
26011 o Bugfixes on 0.0.9rc1:
26012 - Actually catch the -USR2 signal.
26015 Changes in version 0.0.9rc3 - 2004-11-25
26016 o Bugfixes on 0.0.8.1:
26017 - Flush the log file descriptor after we print "Tor opening log file",
26018 so we don't see those messages days later.
26020 o Bugfixes on 0.0.9rc1:
26021 - Make tor-resolve work again.
26022 - Avoid infinite loop in tor-resolve if tor hangs up on it.
26023 - Fix an assert trigger for clients/servers handling resolves.
26026 Changes in version 0.0.9rc2 - 2004-11-24
26027 o Bugfixes on 0.0.9rc1:
26028 - I broke socks5 support while fixing the eof bug.
26029 - Allow unitless bandwidths and intervals; they default to bytes
26031 - New servers don't start out hibernating; they are active until
26032 they run out of bytes, so they have a better estimate of how
26033 long it takes, and so their operators can know they're working.
26036 Changes in version 0.0.9rc1 - 2004-11-23
26037 o Bugfixes on 0.0.8.1:
26038 - Finally fix a bug that's been plaguing us for a year:
26039 With high load, circuit package window was reaching 0. Whenever
26040 we got a circuit-level sendme, we were reading a lot on each
26041 socket, but only writing out a bit. So we would eventually reach
26042 eof. This would be noticed and acted on even when there were still
26043 bytes sitting in the inbuf.
26044 - When poll() is interrupted, we shouldn't believe the revents values.
26046 o Bugfixes on 0.0.9pre6:
26047 - Fix hibernate bug that caused pre6 to be broken.
26048 - Don't keep rephist info for routers that haven't had activity for
26049 24 hours. (This matters now that clients have keys, since we track
26051 - Never call close_temp_logs while validating log options.
26052 - Fix backslash-escaping on tor.sh.in and torctl.in.
26055 - Implement weekly/monthly/daily accounting: now you specify your
26056 hibernation properties by
26057 AccountingMax N bytes|KB|MB|GB|TB
26058 AccountingStart day|week|month [day] HH:MM
26059 Defaults to "month 1 0:00".
26060 - Let bandwidth and interval config options be specified as 5 bytes,
26061 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
26062 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
26063 get back to normal.)
26064 - If your requested entry or exit node has advertised bandwidth 0,
26066 - Be more greedy about filling up relay cells -- we try reading again
26067 once we've processed the stuff we read, in case enough has arrived
26068 to fill the last cell completely.
26069 - Apply NT service patch from Osamu Fujino. Still needs more work.
26072 Changes in version 0.0.9pre6 - 2004-11-15
26073 o Bugfixes on 0.0.8.1:
26074 - Fix assert failure on malformed socks4a requests.
26075 - Use identity comparison, not nickname comparison, to choose which
26076 half of circuit-ID-space each side gets to use. This is needed
26077 because sometimes we think of a router as a nickname, and sometimes
26078 as a hex ID, and we can't predict what the other side will do.
26079 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
26080 write() call will fail and we handle it there.
26081 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
26082 and smartlist_len, which are two major profiling offenders.
26084 o Bugfixes on 0.0.9pre5:
26085 - Fix a bug in read_all that was corrupting config files on windows.
26086 - When we're raising the max number of open file descriptors to
26087 'unlimited', don't log that we just raised it to '-1'.
26088 - Include event code with events, as required by control-spec.txt.
26089 - Don't give a fingerprint when clients do --list-fingerprint:
26090 it's misleading, because it will never be the same again.
26091 - Stop using strlcpy in tor_strndup, since it was slowing us
26093 - Remove warn on startup about missing cached-directory file.
26094 - Make kill -USR1 work again.
26095 - Hibernate if we start tor during the "wait for wakeup-time" phase
26096 of an accounting interval. Log our hibernation plans better.
26097 - Authoritative dirservers now also cache their directory, so they
26098 have it on start-up.
26101 - Fetch running-routers; cache running-routers; compress
26102 running-routers; serve compressed running-routers.z
26103 - Add NSI installer script contributed by J Doe.
26104 - Commit VC6 and VC7 workspace/project files.
26105 - Commit a tor.spec for making RPM files, with help from jbash.
26106 - Add contrib/torctl.in contributed by Glenn Fink.
26107 - Implement the control-spec's SAVECONF command, to write your
26108 configuration to torrc.
26109 - Get cookie authentication for the controller closer to working.
26110 - Include control-spec.txt in the tarball.
26111 - When set_conf changes our server descriptor, upload a new copy.
26112 But don't upload it too often if there are frequent changes.
26113 - Document authentication config in man page, and document signals
26115 - Clean up confusing parts of man page and torrc.sample.
26116 - Make expand_filename handle ~ and ~username.
26117 - Use autoconf to enable largefile support where necessary. Use
26118 ftello where available, since ftell can fail at 2GB.
26119 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
26120 log more informatively.
26121 - Give a slightly more useful output for "tor -h".
26122 - Refuse application socks connections to port 0.
26123 - Check clock skew for verified servers, but allow unverified
26124 servers and clients to have any clock skew.
26125 - Break DirFetchPostPeriod into:
26126 - DirFetchPeriod for fetching full directory,
26127 - StatusFetchPeriod for fetching running-routers,
26128 - DirPostPeriod for posting server descriptor,
26129 - RendPostPeriod for posting hidden service descriptors.
26130 - Make sure the hidden service descriptors are at a random offset
26131 from each other, to hinder linkability.
26134 Changes in version 0.0.9pre5 - 2004-11-09
26135 o Bugfixes on 0.0.9pre4:
26136 - Fix a seg fault in unit tests (doesn't affect main program).
26137 - Fix an assert bug where a hidden service provider would fail if
26138 the first hop of his rendezvous circuit was down.
26139 - Hidden service operators now correctly handle version 1 style
26140 INTRODUCE1 cells (nobody generates them still, so not a critical
26142 - If do_hup fails, actually notice.
26143 - Handle more errnos from accept() without closing the listener.
26144 Some OpenBSD machines were closing their listeners because
26145 they ran out of file descriptors.
26146 - Send resolve cells to exit routers that are running a new
26147 enough version of the resolve code to work right.
26148 - Better handling of winsock includes on non-MSV win32 compilers.
26149 - Some people had wrapped their tor client/server in a script
26150 that would restart it whenever it died. This did not play well
26151 with our "shut down if your version is obsolete" code. Now people
26152 don't fetch a new directory if their local cached version is
26154 - Make our autogen.sh work on ksh as well as bash.
26157 - Hibernation: New config option "AccountingMaxKB" lets you
26158 set how many KBytes per month you want to allow your server to
26159 consume. Rather than spreading those bytes out evenly over the
26160 month, we instead hibernate for some of the month and pop up
26161 at a deterministic time, work until the bytes are consumed, then
26162 hibernate again. Config option "MonthlyAccountingStart" lets you
26163 specify which day of the month your billing cycle starts on.
26164 - Control interface: a separate program can now talk to your
26165 client/server over a socket, and get/set config options, receive
26166 notifications of circuits and streams starting/finishing/dying,
26167 bandwidth used, etc. The next step is to get some GUIs working.
26168 Let us know if you want to help out. See doc/control-spec.txt .
26169 - Ship a contrib/tor-control.py as an example script to interact
26170 with the control port.
26171 - "tor --hash-password zzyxz" will output a salted password for
26172 use in authenticating to the control interface.
26173 - New log format in config:
26174 "Log minsev[-maxsev] stdout|stderr|syslog" or
26175 "Log minsev[-maxsev] file /var/foo"
26178 - DirPolicy config option, to let people reject incoming addresses
26179 from their dirserver.
26180 - "tor --list-fingerprint" will list your identity key fingerprint
26182 - Add "pass" target for RedirectExit, to make it easier to break
26183 out of a sequence of RedirectExit rules.
26184 - Clients now generate a TLS cert too, in preparation for having
26185 them act more like real nodes.
26186 - Ship src/win32/ in the tarball, so people can use it to build.
26187 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
26189 - New "router-status" line in directory, to better bind each verified
26190 nickname to its identity key.
26191 - Deprecate unofficial config option abbreviations, and abbreviations
26192 not on the command line.
26193 - Add a pure-C tor-resolve implementation.
26194 - Use getrlimit and friends to ensure we can reach MaxConn (currently
26195 1024) file descriptors.
26197 o Code security improvements, inspired by Ilja:
26198 - Replace sprintf with snprintf. (I think they were all safe, but
26200 - Replace strcpy/strncpy with strlcpy in more places.
26201 - Avoid strcat; use snprintf or strlcat instead.
26202 - snprintf wrapper with consistent (though not C99) overflow behavior.
26205 Changes in version 0.0.9pre4 - 2004-10-17
26206 o Bugfixes on 0.0.9pre3:
26207 - If the server doesn't specify an exit policy, use the real default
26208 exit policy, not reject *:*.
26209 - Ignore fascistfirewall when uploading/downloading hidden service
26210 descriptors, since we go through Tor for those; and when using
26211 an HttpProxy, since we assume it can reach them all.
26212 - When looking for an authoritative dirserver, use only the ones
26213 configured at boot. Don't bother looking in the directory.
26214 - The rest of the fix for get_default_conf_file() on older win32.
26215 - Make 'Routerfile' config option obsolete.
26218 - New 'MyFamily nick1,...' config option for a server to
26219 specify other servers that shouldn't be used in the same circuit
26220 with it. Only believed if nick1 also specifies us.
26221 - New 'NodeFamily nick1,nick2,...' config option for a client to
26222 specify nodes that it doesn't want to use in the same circuit.
26223 - New 'Redirectexit pattern address:port' config option for a
26224 server to redirect exit connections, e.g. to a local squid.
26227 Changes in version 0.0.9pre3 - 2004-10-13
26228 o Bugfixes on 0.0.8.1:
26229 - Better torrc example lines for dirbindaddress and orbindaddress.
26230 - Improved bounds checking on parsed ints (e.g. config options and
26231 the ones we find in directories.)
26232 - Better handling of size_t vs int, so we're more robust on 64
26234 - Fix the rest of the bug where a newly started OR would appear
26235 as unverified even after we've added his fingerprint and hupped
26237 - Fix a bug from 0.0.7: when read() failed on a stream, we would
26238 close it without sending back an end. So 'connection refused'
26239 would simply be ignored and the user would get no response.
26241 o Bugfixes on 0.0.9pre2:
26242 - Serving the cached-on-disk directory to people is bad. We now
26243 provide no directory until we've fetched a fresh one.
26244 - Workaround for bug on windows where cached-directories get crlf
26246 - Make get_default_conf_file() work on older windows too.
26247 - If we write a *:* exit policy line in the descriptor, don't write
26248 any more exit policy lines.
26251 - Use only 0.0.9pre1 and later servers for resolve cells.
26252 - Make the dirservers file obsolete.
26253 - Include a dir-signing-key token in directories to tell the
26254 parsing entity which key is being used to sign.
26255 - Remove the built-in bulky default dirservers string.
26256 - New config option "Dirserver %s:%d [fingerprint]", which can be
26257 repeated as many times as needed. If no dirservers specified,
26258 default to moria1,moria2,tor26.
26259 - Make moria2 advertise a dirport of 80, so people behind firewalls
26260 will be able to get a directory.
26261 - Http proxy support
26262 - Dirservers translate requests for http://%s:%d/x to /x
26263 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
26264 be routed through this host.
26265 - Clients ask for /tor/x rather than /x for new enough dirservers.
26266 This way we can one day coexist peacefully with apache.
26267 - Clients specify a "Host: %s%d" http header, to be compatible
26268 with more proxies, and so running squid on an exit node can work.
26271 Changes in version 0.0.8.1 - 2004-10-13
26273 - Fix a seg fault that can be triggered remotely for Tor
26274 clients/servers with an open dirport.
26275 - Fix a rare assert trigger, where routerinfos for entries in
26276 our cpath would expire while we're building the path.
26277 - Fix a bug in OutboundBindAddress so it (hopefully) works.
26278 - Fix a rare seg fault for people running hidden services on
26279 intermittent connections.
26280 - Fix a bug in parsing opt keywords with objects.
26281 - Fix a stale pointer assert bug when a stream detaches and
26283 - Fix a string format vulnerability (probably not exploitable)
26284 in reporting stats locally.
26285 - Fix an assert trigger: sometimes launching circuits can fail
26286 immediately, e.g. because too many circuits have failed recently.
26287 - Fix a compile warning on 64 bit platforms.
26290 Changes in version 0.0.9pre2 - 2004-10-03
26292 - Make fetching a cached directory work for 64-bit platforms too.
26293 - Make zlib.h a required header, not an optional header.
26296 Changes in version 0.0.9pre1 - 2004-10-01
26298 - Stop using separate defaults for no-config-file and
26299 empty-config-file. Now you have to explicitly turn off SocksPort,
26300 if you don't want it open.
26301 - Fix a bug in OutboundBindAddress so it (hopefully) works.
26302 - Improve man page to mention more of the 0.0.8 features.
26303 - Fix a rare seg fault for people running hidden services on
26304 intermittent connections.
26305 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
26307 - Fix more dns related bugs: send back resolve_failed and end cells
26308 more reliably when the resolve fails, rather than closing the
26309 circuit and then trying to send the cell. Also attach dummy resolve
26310 connections to a circuit *before* calling dns_resolve(), to fix
26311 a bug where cached answers would never be sent in RESOLVED cells.
26312 - When we run out of disk space, or other log writing error, don't
26313 crash. Just stop logging to that log and continue.
26314 - We were starting to daemonize before we opened our logs, so if
26315 there were any problems opening logs, we would complain to stderr,
26316 which wouldn't work, and then mysteriously exit.
26317 - Fix a rare bug where sometimes a verified OR would connect to us
26318 before he'd uploaded his descriptor, which would cause us to
26319 assign conn->nickname as though he's unverified. Now we look through
26320 the fingerprint list to see if he's there.
26321 - Fix a rare assert trigger, where routerinfos for entries in
26322 our cpath would expire while we're building the path.
26325 - Clients can ask dirservers for /dir.z to get a compressed version
26326 of the directory. Only works for servers running 0.0.9, of course.
26327 - Make clients cache directories and use them to seed their router
26328 lists at startup. This means clients have a datadir again.
26329 - Configuration infrastructure support for warning on obsolete
26331 - Respond to content-encoding headers by trying to uncompress as
26333 - Reply with a deflated directory when a client asks for "dir.z".
26334 We could use allow-encodings instead, but allow-encodings isn't
26335 specified in HTTP 1.0.
26336 - Raise the max dns workers from 50 to 100.
26337 - Discourage people from setting their dirfetchpostperiod more often
26338 than once per minute.
26339 - Protect dirservers from overzealous descriptor uploading -- wait
26340 10 seconds after directory gets dirty, before regenerating.
26343 Changes in version 0.0.8 - 2004-08-25
26344 o Port it to SunOS 5.9 / Athena
26347 Changes in version 0.0.8rc2 - 2004-08-20
26348 o Make it compile on cygwin again.
26349 o When picking unverified routers, skip those with low uptime and/or
26350 low bandwidth, depending on what properties you care about.
26353 Changes in version 0.0.8rc1 - 2004-08-18
26354 o Changes from 0.0.7.3:
26356 - Fix assert triggers: if the other side returns an address 0.0.0.0,
26357 don't put it into the client dns cache.
26358 - If a begin failed due to exit policy, but we believe the IP address
26359 should have been allowed, switch that router to exitpolicy reject *:*
26360 until we get our next directory.
26362 - Clients choose nodes proportional to advertised bandwidth.
26363 - Avoid using nodes with low uptime as introduction points.
26364 - Handle servers with dynamic IP addresses: don't replace
26365 options->Address with the resolved one at startup, and
26366 detect our address right before we make a routerinfo each time.
26367 - 'FascistFirewall' option to pick dirservers and ORs on specific
26368 ports; plus 'FirewallPorts' config option to tell FascistFirewall
26369 which ports are open. (Defaults to 80,443)
26370 - Be more aggressive about trying to make circuits when the network
26371 has changed (e.g. when you unsuspend your laptop).
26372 - Check for time skew on http headers; report date in response to
26374 - If the entrynode config line has only one node, don't pick it as
26376 - Add strict{entry|exit}nodes config options. If set to 1, then
26377 we refuse to build circuits that don't include the specified entry
26379 - OutboundBindAddress config option, to bind to a specific
26380 IP address for outgoing connect()s.
26381 - End truncated log entries (e.g. directories) with "[truncated]".
26383 o Patches to 0.0.8preX:
26385 - Patches to compile and run on win32 again (maybe)?
26386 - Fix crash when looking for ~/.torrc with no $HOME set.
26387 - Fix a race bug in the unit tests.
26388 - Handle verified/unverified name collisions better when new
26389 routerinfo's arrive in a directory.
26390 - Sometimes routers were getting entered into the stats before
26391 we'd assigned their identity_digest. Oops.
26392 - Only pick and establish intro points after we've gotten a
26395 - AllowUnverifiedNodes config option to let circuits choose no-name
26396 routers in entry,middle,exit,introduction,rendezvous positions.
26397 Allow middle and rendezvous positions by default.
26398 - Add a man page for tor-resolve.
26401 Changes in version 0.0.7.3 - 2004-08-12
26402 o Stop dnsworkers from triggering an assert failure when you
26403 ask them to resolve the host "".
26406 Changes in version 0.0.8pre3 - 2004-08-09
26407 o Changes from 0.0.7.2:
26408 - Allow multiple ORs with same nickname in routerlist -- now when
26409 people give us one identity key for a nickname, then later
26410 another, we don't constantly complain until the first expires.
26411 - Remember used bandwidth (both in and out), and publish 15-minute
26412 snapshots for the past day into our descriptor.
26413 - You can now fetch $DIRURL/running-routers to get just the
26414 running-routers line, not the whole descriptor list. (But
26415 clients don't use this yet.)
26416 - When people mistakenly use Tor as an http proxy, point them
26417 at the tor-doc.html rather than the INSTALL.
26418 - Remove our mostly unused -- and broken -- hex_encode()
26419 function. Use base16_encode() instead. (Thanks to Timo Lindfors
26420 for pointing out this bug.)
26421 - Rotate onion keys every 12 hours, not every 2 hours, so we have
26422 fewer problems with people using the wrong key.
26423 - Change the default exit policy to reject the default edonkey,
26424 kazaa, gnutella ports.
26425 - Add replace_file() to util.[ch] to handle win32's rename().
26427 o Changes from 0.0.8preX:
26428 - Fix two bugs in saving onion keys to disk when rotating, so
26429 hopefully we'll get fewer people using old onion keys.
26430 - Fix an assert error that was making SocksPolicy not work.
26431 - Be willing to expire routers that have an open dirport -- it's
26432 just the authoritative dirservers we want to not forget.
26433 - Reject tor-resolve requests for .onion addresses early, so we
26434 don't build a whole rendezvous circuit and then fail.
26435 - When you're warning a server that he's unverified, don't cry
26436 wolf unpredictably.
26437 - Fix a race condition: don't try to extend onto a connection
26438 that's still handshaking.
26439 - For servers in clique mode, require the conn to be open before
26440 you'll choose it for your path.
26441 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
26442 end relay cell, etc.
26443 - Measure bandwidth capacity over the last 24 hours, not just 12
26444 - Bugfix: authoritative dirservers were making and signing a new
26445 directory for each client, rather than reusing the cached one.
26448 Changes in version 0.0.8pre2 - 2004-08-04
26449 o Changes from 0.0.7.2:
26451 - Check directory signature _before_ you decide whether you're
26452 you're running an obsolete version and should exit.
26453 - Check directory signature _before_ you parse the running-routers
26454 list to decide who's running or verified.
26455 - Bugfixes and features:
26456 - Check return value of fclose while writing to disk, so we don't
26457 end up with broken files when servers run out of disk space.
26458 - Log a warning if the user uses an unsafe socks variant, so people
26459 are more likely to learn about privoxy or socat.
26460 - Dirservers now include RFC1123-style dates in the HTTP headers,
26461 which one day we will use to better detect clock skew.
26463 o Changes from 0.0.8pre1:
26464 - Make it compile without warnings again on win32.
26465 - Log a warning if you're running an unverified server, to let you
26466 know you might want to get it verified.
26467 - Only pick a default nickname if you plan to be a server.
26470 Changes in version 0.0.8pre1 - 2004-07-23
26472 - Made our unit tests compile again on OpenBSD 3.5, and tor
26473 itself compile again on OpenBSD on a sparc64.
26474 - We were neglecting milliseconds when logging on win32, so
26475 everything appeared to happen at the beginning of each second.
26477 o Protocol changes:
26478 - 'Extend' relay cell payloads now include the digest of the
26479 intended next hop's identity key. Now we can verify that we're
26480 extending to the right router, and also extend to routers we
26481 hadn't heard of before.
26484 - Tor nodes can now act as relays (with an advertised ORPort)
26485 without being manually verified by the dirserver operators.
26486 - Uploaded descriptors of unverified routers are now accepted
26487 by the dirservers, and included in the directory.
26488 - Verified routers are listed by nickname in the running-routers
26489 list; unverified routers are listed as "$<fingerprint>".
26490 - We now use hash-of-identity-key in most places rather than
26491 nickname or addr:port, for improved security/flexibility.
26492 - To avoid Sybil attacks, paths still use only verified servers.
26493 But now we have a chance to play around with hybrid approaches.
26494 - Nodes track bandwidth usage to estimate capacity (not used yet).
26495 - ClientOnly option for nodes that never want to become servers.
26496 - Directory caching.
26497 - "AuthoritativeDir 1" option for the official dirservers.
26498 - Now other nodes (clients and servers) will cache the latest
26499 directory they've pulled down.
26500 - They can enable their DirPort to serve it to others.
26501 - Clients will pull down a directory from any node with an open
26502 DirPort, and check the signature/timestamp correctly.
26503 - Authoritative dirservers now fetch directories from other
26504 authdirservers, to stay better synced.
26505 - Running-routers list tells who's down also, along with noting
26506 if they're verified (listed by nickname) or unverified (listed
26508 - Allow dirservers to serve running-router list separately.
26509 This isn't used yet.
26510 - ORs connect-on-demand to other ORs
26511 - If you get an extend cell to an OR you're not connected to,
26512 connect, handshake, and forward the create cell.
26513 - The authoritative dirservers stay connected to everybody,
26514 and everybody stays connected to 0.0.7 servers, but otherwise
26515 clients/servers expire unused connections after 5 minutes.
26516 - When servers get a sigint, they delay 30 seconds (refusing new
26517 connections) then exit. A second sigint causes immediate exit.
26518 - File and name management:
26519 - Look for .torrc if no CONFDIR "torrc" is found.
26520 - If no datadir is defined, then choose, make, and secure ~/.tor
26522 - If torrc not found, exitpolicy reject *:*.
26523 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
26524 - If no nickname is defined, derive default from hostname.
26525 - Rename secret key files, e.g. identity.key -> secret_id_key,
26526 to discourage people from mailing their identity key to tor-ops.
26527 - Refuse to build a circuit before the directory has arrived --
26528 it won't work anyway, since you won't know the right onion keys
26530 - Try other dirservers immediately if the one you try is down. This
26531 should tolerate down dirservers better now.
26532 - Parse tor version numbers so we can do an is-newer-than check
26533 rather than an is-in-the-list check.
26534 - New socks command 'resolve', to let us shim gethostbyname()
26536 - A 'tor_resolve' script to access the socks resolve functionality.
26537 - A new socks-extensions.txt doc file to describe our
26538 interpretation and extensions to the socks protocols.
26539 - Add a ContactInfo option, which gets published in descriptor.
26540 - Publish OR uptime in descriptor (and thus in directory) too.
26541 - Write tor version at the top of each log file
26542 - New docs in the tarball:
26544 - Document that you should proxy your SSL traffic too.
26547 Changes in version 0.0.7.2 - 2004-07-07
26548 o A better fix for the 0.0.0.0 problem, that will hopefully
26549 eliminate the remaining related assertion failures.
26552 Changes in version 0.0.7.1 - 2004-07-04
26553 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
26554 since internally we use 0.0.0.0 to signify "not yet resolved".
26557 Changes in version 0.0.7 - 2004-06-07
26558 o Updated the man page to reflect the new features.
26561 Changes in version 0.0.7rc2 - 2004-06-06
26562 o Changes from 0.0.7rc1:
26563 - Make it build on Win32 again.
26564 o Changes from 0.0.6.2:
26565 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
26569 Changes in version 0.0.7rc1 - 2004-06-02
26571 - On sighup, we were adding another log without removing the first
26572 one. So log messages would get duplicated n times for n sighups.
26573 - Several cases of using a connection after we'd freed it. The
26574 problem was that connections that are pending resolve are in both
26575 the pending_resolve tree, and also the circuit's resolving_streams
26576 list. When you want to remove one, you must remove it from both.
26577 - Fix a double-mark-for-close where an end cell arrived for a
26578 resolving stream, and then the resolve failed.
26579 - Check directory signatures based on name of signer, not on whom
26580 we got the directory from. This will let us cache directories more
26583 - Crank up some of our constants to handle more users.
26586 Changes in version 0.0.7pre1 - 2004-06-02
26587 o Fixes for crashes and other obnoxious bugs:
26588 - Fix an epipe bug: sometimes when directory connections failed
26589 to connect, we would give them a chance to flush before closing
26591 - When we detached from a circuit because of resolvefailed, we
26592 would immediately try the same circuit twice more, and then
26593 give up on the resolve thinking we'd tried three different
26595 - Limit the number of intro circuits we'll attempt to build for a
26596 hidden service per 15-minute period.
26597 - Check recommended-software string *early*, before actually parsing
26598 the directory. Thus we can detect an obsolete version and exit,
26599 even if the new directory format doesn't parse.
26600 o Fixes for security bugs:
26601 - Remember which nodes are dirservers when you startup, and if a
26602 random OR enables his dirport, don't automatically assume he's
26603 a trusted dirserver.
26605 - Directory connections were asking the wrong poll socket to
26606 start writing, and not asking themselves to start writing.
26607 - When we detached from a circuit because we sent a begin but
26608 didn't get a connected, we would use it again the first time;
26609 but after that we would correctly switch to a different one.
26610 - Stop warning when the first onion decrypt attempt fails; they
26611 will sometimes legitimately fail now that we rotate keys.
26612 - Override unaligned-access-ok check when $host_cpu is ia64 or
26613 arm. Apparently they allow it but the kernel whines.
26614 - Dirservers try to reconnect periodically too, in case connections
26616 - Fix some memory leaks in directory servers.
26617 - Allow backslash in Win32 filenames.
26618 - Made Tor build complain-free on FreeBSD, hopefully without
26619 breaking other BSD builds. We'll see.
26621 - Doxygen markup on all functions and global variables.
26622 - Make directory functions update routerlist, not replace it. So
26623 now directory disagreements are not so critical a problem.
26624 - Remove the upper limit on number of descriptors in a dirserver's
26625 directory (not that we were anywhere close).
26626 - Allow multiple logfiles at different severity ranges.
26627 - Allow *BindAddress to specify ":port" rather than setting *Port
26628 separately. Allow multiple instances of each BindAddress config
26629 option, so you can bind to multiple interfaces if you want.
26630 - Allow multiple exit policy lines, which are processed in order.
26631 Now we don't need that huge line with all the commas in it.
26632 - Enable accept/reject policies on SOCKS connections, so you can bind
26633 to 0.0.0.0 but still control who can use your OP.
26636 Changes in version 0.0.6.2 - 2004-05-16
26637 o Our integrity-checking digest was checking only the most recent cell,
26638 not the previous cells like we'd thought.
26639 Thanks to Stefan Mark for finding the flaw!
26642 Changes in version 0.0.6.1 - 2004-05-06
26643 o Fix two bugs in our AES counter-mode implementation (this affected
26644 onion-level stream encryption, but not TLS-level). It turns
26645 out we were doing something much more akin to a 16-character
26646 polyalphabetic cipher. Oops.
26647 Thanks to Stefan Mark for finding the flaw!
26648 o Retire moria3 as a directory server, and add tor26 as a directory
26652 Changes in version 0.0.6 - 2004-05-02
26653 [version bump only]
26656 Changes in version 0.0.6rc4 - 2004-05-01
26657 o Update the built-in dirservers list to use the new directory format
26658 o Fix a rare seg fault: if a node offering a hidden service attempts
26659 to build a circuit to Alice's rendezvous point and fails before it
26660 reaches the last hop, it retries with a different circuit, but
26662 o Handle windows socket errors correctly.
26665 Changes in version 0.0.6rc3 - 2004-04-28
26666 o Don't expire non-general excess circuits (if we had enough
26667 circuits open, we were expiring rendezvous circuits -- even
26668 when they had a stream attached. oops.)
26669 o Fetch randomness from /dev/urandom better (not via fopen/fread)
26670 o Better debugging for tls errors
26671 o Some versions of openssl have an SSL_pending function that erroneously
26672 returns bytes when there is a non-application record pending.
26673 o Set Content-Type on the directory and hidserv descriptor.
26674 o Remove IVs from cipher code, since AES-ctr has none.
26675 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
26676 o We were using an array of length zero in a few places.
26677 o win32's gethostbyname can't resolve an IP to an IP.
26678 o win32's close can't close a socket.
26681 Changes in version 0.0.6rc2 - 2004-04-26
26682 o Fix a bug where we were closing tls connections intermittently.
26683 It turns out openssl keeps its errors around -- so if an error
26684 happens, and you don't ask about it, and then another openssl
26685 operation happens and succeeds, and you ask if there was an error,
26686 it tells you about the first error. Fun fun.
26687 o Fix a bug that's been lurking since 27 may 03 (!)
26688 When passing back a destroy cell, we would use the wrong circ id.
26689 'Mostly harmless', but still worth fixing.
26690 o Since we don't support truncateds much, don't bother sending them;
26691 just close the circ.
26692 o check for <machine/limits.h> so we build on NetBSD again (I hope).
26693 o don't crash if a conn that sent a begin has suddenly lost its circuit
26694 (this was quite rare).
26697 Changes in version 0.0.6rc1 - 2004-04-25
26698 o We now rotate link (tls context) keys and onion keys.
26699 o CREATE cells now include oaep padding, so you can tell
26700 if you decrypted them correctly.
26701 o Add bandwidthburst to server descriptor.
26702 o Directories now say which dirserver signed them.
26703 o Use a tor_assert macro that logs failed assertions too.
26706 Changes in version 0.0.6pre5 - 2004-04-18
26707 o changes from 0.0.6pre4:
26708 - make tor build on broken freebsd 5.2 installs
26709 - fix a failed assert when you try an intro point, get a nack, and try
26710 a second one and it works.
26711 - when alice uses a port that the hidden service doesn't accept,
26712 it now sends back an end cell (denied by exit policy). otherwise
26713 alice would just have to wait to time out.
26714 - fix another rare bug: when we had tried all the intro
26715 points for a hidden service, we fetched the descriptor
26716 again, but we left our introcirc thinking it had already
26717 sent an intro, so it kept waiting for a response...
26718 - bugfix: when you sleep your hidden-service laptop, as soon
26719 as it wakes up it tries to upload a service descriptor, but
26720 socketpair fails for some reason (localhost not up yet?).
26721 now we simply give up on that upload, and we'll try again later.
26722 i'd still like to find the bug though.
26723 - if an intro circ waiting for an ack dies before getting one, then
26725 - we were reusing stale service descriptors and refetching usable
26729 Changes in version 0.0.6pre4 - 2004-04-14
26730 o changes from 0.0.6pre3:
26731 - when bob fails to connect to the rendezvous point, and his
26732 circ didn't fail because of the rendezvous point itself, then
26733 he retries a couple of times
26734 - we expire introduction and rendezvous circs more thoroughly
26735 (sometimes they were hanging around forever)
26736 - we expire unattached rendezvous streams that have been around
26737 too long (they were sticking around forever).
26738 - fix a measly fencepost error that was crashing everybody with
26742 Changes in version 0.0.6pre3 - 2004-04-14
26743 o changes from 0.0.6pre2:
26744 - make hup work again
26745 - fix some memory leaks for dirservers
26746 - allow more skew in rendezvous descriptor timestamps, to help
26747 handle people like blanu who don't know what time it is
26748 - normal circs are 3 hops, but some rend/intro circs are 4, if
26749 the initiator doesn't get to choose the last hop
26750 - send acks for introductions, so alice can know whether to try
26752 - bob publishes intro points more correctly
26753 o changes from 0.0.5:
26754 - fix an assert trigger that's been plaguing us since the days
26755 of 0.0.2prexx (thanks weasel!)
26756 - retry stream correctly when we fail to connect because of
26757 exit-policy-reject (should try another) or can't-resolve-address
26758 (also should try another, because dns on random internet servers
26760 - when we hup a dirserver and we've *removed* a server from the
26761 approved-routers list, now we remove that server from the
26762 in-memory directories too
26765 Changes in version 0.0.6pre2 - 2004-04-08
26766 o We fixed our base32 implementation. Now it works on all architectures.
26769 Changes in version 0.0.6pre1 - 2004-04-08
26771 - Hidden services and rendezvous points are implemented. Go to
26772 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
26773 hidden services. (This only works via a socks4a proxy such as
26774 Privoxy, and currently it's quite slow.)
26777 Changes in version 0.0.5 - 2004-03-30
26778 [version bump only]
26781 Changes in version 0.0.5rc3 - 2004-03-29
26782 o Install torrc as torrc.sample -- we no longer clobber your
26784 o Re-enable recommendedversion checking (we broke it in rc2, oops)
26785 o Add in a 'notice' log level for things the operator should hear
26786 but that aren't warnings
26789 Changes in version 0.0.5rc2 - 2004-03-29
26790 o Hold socks connection open until reply is flushed (if possible)
26791 o Make exit nodes resolve IPs to IPs immediately, rather than asking
26792 the dns farm to do it.
26793 o Fix c99 aliasing warnings in rephist.c
26794 o Don't include server descriptors that are older than 24 hours in the
26796 o Give socks 'reject' replies their whole 15s to attempt to flush,
26797 rather than seeing the 60s timeout and assuming the flush had failed.
26798 o Clean automake droppings from the cvs repository
26801 Changes in version 0.0.5rc1 - 2004-03-28
26802 o Fix mangled-state bug in directory fetching (was causing sigpipes).
26803 o Only build circuits after we've fetched the directory: clients were
26804 using only the directory servers before they'd fetched a directory.
26805 This also means longer startup time; so it goes.
26806 o Fix an assert trigger where an OP would fail to handshake, and we'd
26807 expect it to have a nickname.
26808 o Work around a tsocks bug: do a socks reject when AP connection dies
26809 early, else tsocks goes into an infinite loop.
26812 Changes in version 0.0.4 - 2004-03-26
26813 o When connecting to a dirserver or OR and the network is down,
26817 Changes in version 0.0.3 - 2004-03-26
26818 o Warn and fail if server chose a nickname with illegal characters
26819 o Port to Solaris and Sparc:
26820 - include missing header fcntl.h
26821 - have autoconf find -lsocket -lnsl automatically
26822 - deal with hardware word alignment
26823 - make uname() work (solaris has a different return convention)
26824 - switch from using signal() to sigaction()
26825 o Preliminary work on reputation system:
26826 - Keep statistics on success/fail of connect attempts; they're published
26827 by kill -USR1 currently.
26828 - Add a RunTesting option to try to learn link state by creating test
26829 circuits, even when SocksPort is off.
26830 - Remove unused open circuits when there are too many.
26833 Changes in version 0.0.2 - 2004-03-19
26834 - Include strlcpy and strlcat for safer string ops
26835 - define INADDR_NONE so we compile (but still not run) on solaris
26838 Changes in version 0.0.2pre27 - 2004-03-14
26840 - Allow internal tor networks (we were rejecting internal IPs,
26841 now we allow them if they're set explicitly).
26842 - And fix a few endian issues.
26845 Changes in version 0.0.2pre26 - 2004-03-14
26847 - If a stream times out after 15s without a connected cell, don't
26848 try that circuit again: try a new one.
26849 - Retry streams at most 4 times. Then give up.
26850 - When a dirserver gets a descriptor from an unknown router, it
26851 logs its fingerprint (so the dirserver operator can choose to
26852 accept it even without mail from the server operator).
26853 - Inform unapproved servers when we reject their descriptors.
26854 - Make tor build on Windows again. It works as a client, who knows
26856 - Clearer instructions in the torrc for how to set up a server.
26857 - Be more efficient about reading fd's when our global token bucket
26858 (used for rate limiting) becomes empty.
26860 - Stop asserting that computers always go forward in time. It's
26862 - When we sent a cell (e.g. destroy) and then marked an OR connection
26863 expired, we might close it before finishing a flush if the other
26864 side isn't reading right then.
26865 - Don't allow dirservers to start if they haven't defined
26866 RecommendedVersions
26867 - We were caching transient dns failures. Oops.
26868 - Prevent servers from publishing an internal IP as their address.
26869 - Address a strcat vulnerability in circuit.c
26872 Changes in version 0.0.2pre25 - 2004-03-04
26874 - Put the OR's IP in its router descriptor, not its fqdn. That way
26875 we'll stop being stalled by gethostbyname for nodes with flaky dns,
26878 - If the user typed in an address that didn't resolve, the server
26882 Changes in version 0.0.2pre24 - 2004-03-03
26884 - Fix an assertion failure in dns.c, where we were trying to dequeue
26885 a pending dns resolve even if it wasn't pending
26886 - Fix a spurious socks5 warning about still trying to write after the
26887 connection is finished.
26888 - Hold certain marked_for_close connections open until they're finished
26889 flushing, rather than losing bytes by closing them too early.
26890 - Correctly report the reason for ending a stream
26891 - Remove some duplicate calls to connection_mark_for_close
26892 - Put switch_id and start_daemon earlier in the boot sequence, so it
26893 will actually try to chdir() to options.DataDirectory
26894 - Make 'make test' exit(1) if a test fails; fix some unit tests
26895 - Make tor fail when you use a config option it doesn't know about,
26896 rather than warn and continue.
26897 - Make --version work
26898 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
26901 Changes in version 0.0.2pre23 - 2004-02-29
26903 - Print a statement when the first circ is finished, so the user
26904 knows it's working.
26905 - If a relay cell is unrecognized at the end of the circuit,
26906 send back a destroy. (So attacks to mutate cells are more
26908 - New config option 'excludenodes' to avoid certain nodes for circuits.
26909 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
26910 so you can collect coredumps there.
26912 - Fix a bug in tls flushing where sometimes data got wedged and
26913 didn't flush until more data got sent. Hopefully this bug was
26914 a big factor in the random delays we were seeing.
26915 - Make 'connected' cells include the resolved IP, so the client
26916 dns cache actually gets populated.
26917 - Disallow changing from ORPort=0 to ORPort>0 on hup.
26918 - When we time-out on a stream and detach from the circuit, send an
26919 end cell down it first.
26920 - Only warn about an unknown router (in exitnodes, entrynodes,
26921 excludenodes) after we've fetched a directory.
26924 Changes in version 0.0.2pre22 - 2004-02-26
26926 - Servers publish less revealing uname information in descriptors.
26927 - More memory tracking and assertions, to crash more usefully when
26929 - If the default torrc isn't there, just use some default defaults.
26930 Plus provide an internal dirservers file if they don't have one.
26931 - When the user tries to use Tor as an http proxy, give them an http
26932 501 failure explaining that we're a socks proxy.
26933 - Dump a new router.desc on hup, to help confused people who change
26934 their exit policies and then wonder why router.desc doesn't reflect
26936 - Clean up the generic tor.sh init script that we ship with.
26938 - If the exit stream is pending on the resolve, and a destroy arrives,
26939 then the stream wasn't getting removed from the pending list. I
26940 think this was the one causing recent server crashes.
26941 - Use a more robust poll on OSX 10.3, since their poll is flaky.
26942 - When it couldn't resolve any dirservers, it was useless from then on.
26943 Now it reloads the RouterFile (or default dirservers) if it has no
26945 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
26946 many users don't even *have* a /usr/local/sbin/.
26949 Changes in version 0.0.2pre21 - 2004-02-18
26951 - There's a ChangeLog file that actually reflects the changelog.
26952 - There's a 'torify' wrapper script, with an accompanying
26953 tor-tsocks.conf, that simplifies the process of using tsocks for
26954 tor. It even has a man page.
26955 - The tor binary gets installed to sbin rather than bin now.
26956 - Retry streams where the connected cell hasn't arrived in 15 seconds
26957 - Clean up exit policy handling -- get the default out of the torrc,
26958 so we can update it without forcing each server operator to fix
26960 - Allow imaps and pop3s in default exit policy
26962 - Prevent picking middleman nodes as the last node in the circuit
26965 Changes in version 0.0.2pre20 - 2004-01-30
26967 - We now have a deb package, and it's in debian unstable. Go to
26968 it, apt-getters. :)
26969 - I've split the TotalBandwidth option into BandwidthRate (how many
26970 bytes per second you want to allow, long-term) and
26971 BandwidthBurst (how many bytes you will allow at once before the cap
26972 kicks in). This better token bucket approach lets you, say, set
26973 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
26974 performance while not exceeding your monthly bandwidth quota.
26975 - Push out a tls record's worth of data once you've got it, rather
26976 than waiting until you've read everything waiting to be read. This
26977 may improve performance by pipelining better. We'll see.
26978 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
26979 from failed circuits (if they haven't been connected yet) and attach
26981 - Expire old streams that haven't managed to connect. Some day we'll
26982 have them reattach to new circuits instead.
26985 - Fix several memory leaks that were causing servers to become bloated
26987 - Fix a few very rare assert triggers. A few more remain.
26988 - Setuid to User _before_ complaining about running as root.
26991 Changes in version 0.0.2pre19 - 2004-01-07
26993 - Fix deadlock condition in dns farm. We were telling a child to die by
26994 closing the parent's file descriptor to him. But newer children were
26995 inheriting the open file descriptor from the parent, and since they
26996 weren't closing it, the socket never closed, so the child never read
26997 eof, so he never knew to exit. Similarly, dns workers were holding
26998 open other sockets, leading to all sorts of chaos.
26999 - New cleaner daemon() code for forking and backgrounding.
27000 - If you log to a file, it now prints an entry at the top of the
27001 logfile so you know it's working.
27002 - The onionskin challenge length was 30 bytes longer than necessary.
27003 - Started to patch up the spec so it's not quite so out of date.
27006 Changes in version 0.0.2pre18 - 2004-01-02
27008 - Fix endian issues with the 'integrity' field in the relay header.
27009 - Fix a potential bug where connections in state
27010 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
27013 Changes in version 0.0.2pre17 - 2003-12-30
27015 - Made --debuglogfile (or any second log file, actually) work.
27016 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
27017 adversary could force us into an infinite loop.
27020 - Each onionskin handshake now includes a hash of the computed key,
27021 to prove the server's identity and help perfect forward secrecy.
27022 - Changed cell size from 256 to 512 bytes (working toward compatibility
27024 - Changed cell length to 2 bytes, and moved it to the relay header.
27025 - Implemented end-to-end integrity checking for the payloads of
27027 - Separated streamid from 'recognized' (otherwise circuits will get
27028 messed up when we try to have streams exit from the middle). We
27029 use the integrity-checking to confirm that a cell is addressed to
27031 - Randomize the initial circid and streamid values, so an adversary who
27032 breaks into a node can't learn how many circuits or streams have
27036 Changes in version 0.0.2pre16 - 2003-12-14
27038 - Fixed a bug that made HUP trigger an assert
27039 - Fixed a bug where a circuit that immediately failed wasn't being
27040 counted as a failed circuit in counting retries.
27043 - Now we close the circuit when we get a truncated cell: otherwise we're
27044 open to an anonymity attack where a bad node in the path truncates
27045 the circuit and then we open streams at him.
27046 - Add port ranges to exit policies
27047 - Add a conservative default exit policy
27048 - Warn if you're running tor as root
27049 - on HUP, retry OR connections and close/rebind listeners
27050 - options.EntryNodes: try these nodes first when picking the first node
27051 - options.ExitNodes: if your best choices happen to include any of
27052 your preferred exit nodes, you choose among just those preferred
27054 - options.ExcludedNodes: nodes that are never picked in path building
27057 Changes in version 0.0.2pre15 - 2003-12-03
27058 o Robustness and bugfixes:
27059 - Sometimes clients would cache incorrect DNS resolves, which would
27060 really screw things up.
27061 - An OP that goes offline would slowly leak all its sockets and stop
27063 - A wide variety of bugfixes in exit node selection, exit policy
27064 handling, and processing pending streams when a new circuit is
27066 - Pick nodes for a path only from those the directory says are up
27067 - Choose randomly from all running dirservers, not always the first one
27068 - Increase allowed http header size for directory fetch.
27069 - Stop writing to stderr (if we're daemonized it will be closed).
27070 - Enable -g always, so cores will be more useful to me.
27071 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
27074 - Wrote a man page. It lists commonly used options.
27077 - Change default loglevel to warn.
27078 - Make PidFile default to null rather than littering in your CWD.
27079 - OnionRouter config option is now obsolete. Instead it just checks
27081 - Moved to a single unified torrc file for both clients and servers.
27084 Changes in version 0.0.2pre14 - 2003-11-29
27085 o Robustness and bugfixes:
27086 - Force the admin to make the DataDirectory himself
27087 - to get ownership/permissions right
27088 - so clients no longer make a DataDirectory and then never use it
27089 - fix bug where a client who was offline for 45 minutes would never
27090 pull down a directory again
27091 - fix (or at least hide really well) the dns assert bug that was
27092 causing server crashes
27093 - warnings and improved robustness wrt clockskew for certs
27094 - use the native daemon(3) to daemonize, when available
27095 - exit if bind() fails
27096 - exit if neither socksport nor orport is defined
27097 - include our own tor_timegm (Win32 doesn't have its own)
27098 - bugfix for win32 with lots of connections
27099 - fix minor bias in PRNG
27100 - make dirserver more robust to corrupt cached directory
27103 - Wrote the design document (woo)
27105 o Circuit building and exit policies:
27106 - Circuits no longer try to use nodes that the directory has told them
27108 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
27109 bitcounts (18.0.0.0/8).
27110 - Make AP connections standby for a circuit if no suitable circuit
27111 exists, rather than failing
27112 - Circuits choose exit node based on addr/port, exit policies, and
27113 which AP connections are standing by
27114 - Bump min pathlen from 2 to 3
27115 - Relay end cells have a payload to describe why the stream ended.
27116 - If the stream failed because of exit policy, try again with a new
27118 - Clients have a dns cache to remember resolved addresses.
27119 - Notice more quickly when we have no working circuits
27122 - APPort is now called SocksPort
27123 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
27125 - RecommendedVersions is now a config variable rather than
27126 hardcoded (for dirservers)
27127 - Reloads config on HUP
27128 - Usage info on -h or --help
27129 - If you set User and Group config vars, it'll setu/gid to them.
27132 Changes in version 0.0.2pre13 - 2003-10-19
27133 o General stability:
27134 - SSL_write no longer fails when it returns WANTWRITE and the number
27135 of bytes in the buf has changed by the next SSL_write call.
27136 - Fix segfault fetching directory when network is down
27137 - Fix a variety of minor memory leaks
27138 - Dirservers reload the fingerprints file on HUP, so I don't have
27139 to take down the network when I approve a new router
27140 - Default server config file has explicit Address line to specify fqdn
27143 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
27144 - Make listener connections not ever alloc bufs
27146 o Autoconf improvements:
27147 - don't clobber an external CFLAGS in ./configure
27148 - Make install now works
27149 - create var/lib/tor on make install
27150 - autocreate a tor.sh initscript to help distribs
27151 - autocreate the torrc and sample-server-torrc with correct paths
27153 o Log files and Daemonizing now work:
27154 - If --DebugLogFile is specified, log to it at -l debug
27155 - If --LogFile is specified, use it instead of commandline
27156 - If --RunAsDaemon is set, tor forks and backgrounds on startup