1 This document summarizes new features and bugfixes in each stable
2 release of Tor. If you want to see more detailed descriptions of the
3 changes in each development snapshot, see the ChangeLog file.
5 Changes in version 0.3.3.7 - 2018-06-12
6 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
7 fixes for bugs affecting compatibility and stability.
9 o Directory authority changes:
10 - Add an IPv6 address for the "dannenberg" directory authority.
13 o Minor features (geoip):
14 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
15 Country database. Closes ticket 26351.
17 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
18 - Work around a change in OpenSSL 1.1.1 where return values that
19 would previously indicate "no password" now indicate an empty
20 password. Without this workaround, Tor instances running with
21 OpenSSL 1.1.1 would accept descriptors that other Tor instances
22 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
24 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
25 - Silence unused-const-variable warnings in zstd.h with some GCC
26 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
28 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
29 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
30 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
31 miscounting the total number of circuits for these field values.)
32 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
34 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
35 - Prevent a possible out-of-bounds smartlist read in
36 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
38 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
39 - Only select relays when they have the descriptors we prefer to use
40 for them. This change fixes a bug where we could select a relay
41 because it had _some_ descriptor, but reject it later with a
42 nonfatal assertion error because it didn't have the exact one we
43 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
46 Changes in version 0.3.3.6 - 2018-05-22
47 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
48 backports several important fixes from the 0.3.4.1-alpha.
50 The Tor 0.3.3 series includes controller support and other
51 improvements for v3 onion services, official support for embedding Tor
52 within other applications, and our first non-trivial module written in
53 the Rust programming language. (Rust is still not enabled by default
54 when building Tor.) And as usual, there are numerous other smaller
55 bugfixes, features, and improvements.
57 Below are the changes since 0.3.2.10. For a list of only the changes
58 since 0.3.3.5-rc, see the ChangeLog file.
60 o New system requirements:
61 - When built with Rust, Tor now depends on version 0.2.39 of the
62 libc crate. Closes tickets 25310 and 25664.
64 o Major features (embedding):
65 - There is now a documented stable API for programs that need to
66 embed Tor. See tor_api.h for full documentation and known bugs.
68 - Tor now has support for restarting in the same process.
69 Controllers that run Tor using the "tor_api.h" interface can now
70 restart Tor after Tor has exited. This support is incomplete,
71 however: we fixed crash bugs that prevented it from working at
72 all, but many bugs probably remain, including a possibility of
73 security issues. Implements ticket 24581.
75 o Major features (IPv6, directory documents):
76 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
77 consensus. This information makes it easier for IPv6 clients to
78 bootstrap and choose reachable entry guards. Implements
80 - Add consensus method 28, which removes IPv6 ORPorts from
81 microdescriptors. Now that the consensus contains IPv6 ORPorts,
82 they are redundant in microdescs. This change will be used by Tor
83 clients on 0.2.8.x and later. (That is to say, with all Tor
84 clients that have IPv6 bootstrap and guard support.) Implements
86 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
87 set by different numbers of authorities. Fixes 23870
90 o Major features (onion service v3, control port):
91 - The control port now supports commands and events for v3 onion
92 services. It is now possible to create ephemeral v3 services using
93 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
94 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
95 DEL_ONION) have been extended to support v3 onion services. Closes
96 ticket 20699; implements proposal 284.
98 o Major features (onion services):
99 - Provide torrc options to pin the second and third hops of onion
100 service circuits to a list of nodes. The option HSLayer2Guards
101 pins the second hop, and the option HSLayer3Guards pins the third
102 hop. These options are for use in conjunction with experiments
103 with "vanguards" for preventing guard enumeration attacks. Closes
105 - When v3 onion service clients send introduce cells, they now
106 include the IPv6 address of the rendezvous point, if it has one.
107 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
108 in future Tor versions, IPv6-only v3 single onion services will be
109 able to use IPv6 addresses to connect directly to the rendezvous
110 point. Closes ticket 23577. Patch by Neel Chauhan.
112 o Major features (relay):
113 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
114 operator to use a more reasonable ("reduced") exit policy, rather
115 than the default one. If you want to run an exit node without
116 thinking too hard about which ports to allow, this one is for you.
117 Closes ticket 13605. Patch from Neel Chauhan.
119 o Major features (rust, portability, experimental):
120 - Tor now ships with an optional implementation of one of its
121 smaller modules (protover.c) in the Rust programming language. To
122 try it out, install a Rust build environment, and configure Tor
123 with "--enable-rust --enable-cargo-online-mode". This should not
124 cause any user-visible changes, but should help us gain more
125 experience with Rust, and plan future Rust integration work.
126 Implementation by Chelsea Komlo. Closes ticket 22840.
128 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
129 - When directory authorities read a zero-byte bandwidth file, they
130 would previously log a warning with the contents of an
131 uninitialised buffer. They now log a warning about the empty file
132 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
134 o Major bugfixes (security, directory authority, denial-of-service):
135 - Fix a bug that could have allowed an attacker to force a directory
136 authority to use up all its RAM by passing it a maliciously
137 crafted protocol versions string. Fixes bug 25517; bugfix on
138 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
140 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
141 - Avoid a rare assertion failure in the circuit build timeout code
142 if we fail to allow any circuits to actually complete. Fixes bug
143 25733; bugfix on 0.2.2.2-alpha.
145 o Major bugfixes (netflow padding):
146 - Stop adding unneeded channel padding right after we finish
147 flushing to a connection that has been trying to flush for many
148 seconds. Instead, treat all partial or complete flushes as
149 activity on the channel, which will defer the time until we need
150 to add padding. This fix should resolve confusing and scary log
151 messages like "Channel padding timeout scheduled 221453ms in the
152 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
154 o Major bugfixes (networking):
155 - Tor will no longer reject IPv6 address strings from Tor Browser
156 when they are passed as hostnames in SOCKS5 requests. Fixes bug
157 25036, bugfix on Tor 0.3.1.2.
159 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
160 - Correctly detect when onion services get disabled after HUP. Fixes
161 bug 25761; bugfix on 0.3.2.1.
163 o Major bugfixes (performance, load balancing):
164 - Directory authorities no longer vote in favor of the Guard flag
165 for relays without directory support. Starting in Tor
166 0.3.0.1-alpha, clients have been avoiding using such relays in the
167 Guard position, leading to increasingly broken load balancing for
168 the 5%-or-so of Guards that don't advertise directory support.
169 Fixes bug 22310; bugfix on 0.3.0.6.
171 o Major bugfixes (relay):
172 - If we have failed to connect to a relay and received a connection
173 refused, timeout, or similar error (at the TCP level), do not try
174 that same address/port again for 60 seconds after the failure has
175 occurred. Fixes bug 24767; bugfix on 0.0.6.
177 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
178 - Impose a limit on circuit cell queue size. The limit can be
179 controlled by a consensus parameter. Fixes bug 25226; bugfix
182 o Minor features (cleanup):
183 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
184 when it stops. Closes ticket 23271.
186 o Minor features (compatibility, backport from 0.3.4.1-alpha):
187 - Avoid some compilation warnings with recent versions of LibreSSL.
190 o Minor features (config options):
191 - Change the way the default value for MaxMemInQueues is calculated.
192 We now use 40% of the hardware RAM if the system has 8 GB RAM or
193 more. Otherwise we use the former value of 75%. Closes
196 o Minor features (continuous integration):
197 - Update the Travis CI configuration to use the stable Rust channel,
198 now that we have decided to require that. Closes ticket 25714.
200 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
201 - Our .travis.yml configuration now includes support for testing the
202 results of "make distcheck". (It's not uncommon for "make check"
203 to pass but "make distcheck" to fail.) Closes ticket 25814.
204 - Our Travis CI configuration now integrates with the Coveralls
205 coverage analysis tool. Closes ticket 25818.
207 o Minor features (defensive programming):
208 - Most of the functions in Tor that free objects have been replaced
209 with macros that free the objects and set the corresponding
210 pointers to NULL. This change should help prevent a large class of
211 dangling pointer bugs. Closes ticket 24337.
212 - Where possible, the tor_free() macro now only evaluates its input
213 once. Part of ticket 24337.
214 - Check that microdesc ed25519 ids are non-zero in
215 node_get_ed25519_id() before returning them. Implements ticket
216 24001, patch by "aruna1234".
218 o Minor features (directory authority):
219 - When directory authorities are unable to add signatures to a
220 pending consensus, log the reason why. Closes ticket 24849.
222 o Minor features (embedding):
223 - Tor can now start with a preauthenticated control connection
224 created by the process that launched it. This feature is meant for
225 use by programs that want to launch and manage a Tor process
226 without allowing other programs to manage it as well. For more
227 information, see the __OwningControllerFD option documented in
228 control-spec.txt. Closes ticket 23900.
229 - On most errors that would cause Tor to exit, it now tries to
230 return from the tor_main() function, rather than calling the
231 system exit() function. Most users won't notice a difference here,
232 but it should be significant for programs that run Tor inside a
233 separate thread: they should now be able to survive Tor's exit
234 conditions rather than having Tor shut down the entire process.
236 - Applications that want to embed Tor can now tell Tor not to
237 register any of its own POSIX signal handlers, using the
238 __DisableSignalHandlers option. Closes ticket 24588.
240 o Minor features (fallback directory list):
241 - Avoid selecting fallbacks that change their IP addresses too
242 often. Select more fallbacks by ignoring the Guard flag, and
243 allowing lower cutoffs for the Running and V2Dir flags. Also allow
244 a lower bandwidth, and a higher number of fallbacks per operator
245 (5% of the list). Implements ticket 24785.
246 - Update the fallback whitelist and blacklist based on opt-ins and
247 relay changes. Closes tickets 22321, 24678, 22527, 24135,
250 o Minor features (fallback directory mirror configuration):
251 - Add a nickname to each fallback in a C comment. This makes it
252 easier for operators to find their relays, and allows stem to use
253 nicknames to identify fallbacks. Implements ticket 24600.
254 - Add a type and version header to the fallback directory mirror
255 file. Also add a delimiter to the end of each fallback entry. This
256 helps external parsers like stem and Relay Search. Implements
258 - Add an extrainfo cache flag for each fallback in a C comment. This
259 allows stem to use fallbacks to fetch extra-info documents, rather
260 than using authorities. Implements ticket 22759.
261 - Add the generateFallbackDirLine.py script for automatically
262 generating fallback directory mirror lines from relay fingerprints.
263 No more typos! Add the lookupFallbackDirContact.py script for
264 automatically looking up operator contact info from relay
265 fingerprints. Implements ticket 24706, patch by teor and atagar.
266 - Reject any fallback directory mirror that serves an expired
267 consensus. Implements ticket 20942, patch by "minik".
268 - Remove commas and equals signs from external string inputs to the
269 fallback list. This avoids format confusion attacks. Implements
271 - Remove the "weight=10" line from fallback directory mirror
272 entries. Ticket 24681 will maintain the current fallback weights
273 by changing Tor's default fallback weight to 10. Implements
275 - Stop logging excessive information about fallback netblocks.
276 Implements ticket 24791.
278 o Minor features (forward-compatibility):
279 - If a relay supports some link authentication protocol that we do
280 not recognize, then include that relay's ed25519 key when telling
281 other relays to extend to it. Previously, we treated future
282 versions as if they were too old to support ed25519 link
283 authentication. Closes ticket 20895.
285 o Minor features (geoip):
286 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
287 database. Closes ticket 26104.
289 o Minor features (heartbeat):
290 - Add onion service information to our heartbeat logs, displaying
291 stats about the activity of configured onion services. Closes
294 o Minor features (instrumentation, development):
295 - Add the MainloopStats option to allow developers to get
296 instrumentation information from the main event loop via the
297 heartbeat messages. We hope to use this to improve Tor's behavior
298 when it's trying to sleep. Closes ticket 24605.
300 o Minor features (IPv6):
301 - Make IPv6-only clients wait for microdescs for relays, even if we
302 were previously using descriptors (or were using them as a bridge)
303 and have a cached descriptor for them. Implements ticket 23827.
304 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
305 them, rather than waiting to download microdescriptors. Implements
308 o Minor features (log messages):
309 - Improve log message in the out-of-memory handler to include
310 information about memory usage from the different compression
311 backends. Closes ticket 25372.
312 - Improve a warning message that happens when we fail to re-parse an
313 old router because of an expired certificate. Closes ticket 20020.
314 - Make the log more quantitative when we hit MaxMemInQueues
315 threshold exposing some values. Closes ticket 24501.
317 o Minor features (logging):
318 - Clarify the log messages produced when getrandom() or a related
319 entropy-generation mechanism gives an error. Closes ticket 25120.
320 - Added support for the Android logging subsystem. Closes
323 o Minor features (performance):
324 - Support predictive circuit building for onion service circuits
325 with multiple layers of guards. Closes ticket 23101.
326 - Use stdatomic.h where available, rather than mutexes, to implement
327 atomic_counter_t. Closes ticket 23953.
329 o Minor features (performance, 32-bit):
330 - Improve performance on 32-bit systems by avoiding 64-bit division
331 when calculating the timestamp in milliseconds for channel padding
332 computations. Implements ticket 24613.
333 - Improve performance on 32-bit systems by avoiding 64-bit division
334 when timestamping cells and buffer chunks for OOM calculations.
335 Implements ticket 24374.
337 o Minor features (performance, OSX, iOS):
338 - Use the mach_approximate_time() function (when available) to
339 implement coarse monotonic time. Having a coarse time function
340 should avoid a large number of system calls, and improve
341 performance slightly, especially under load. Closes ticket 24427.
343 o Minor features (performance, windows):
344 - Improve performance on Windows Vista and Windows 7 by adjusting
345 TCP send window size according to the recommendation from
346 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
349 o Minor features (sandbox):
350 - Explicitly permit the poll() system call when the Linux
351 seccomp2-based sandbox is enabled: apparently, some versions of
352 libc use poll() when calling getpwnam(). Closes ticket 25313.
354 o Minor features (storage, configuration):
355 - Users can store cached directory documents somewhere other than
356 the DataDirectory by using the CacheDirectory option. Similarly,
357 the storage location for relay's keys can be overridden with the
358 KeyDirectory option. Closes ticket 22703.
360 o Minor features (testing):
361 - Add a "make test-rust" target to run the rust tests only. Closes
364 o Minor features (testing, debugging, embedding):
365 - For development purposes, Tor now has a mode in which it runs for
366 a few seconds, then stops, and starts again without exiting the
367 process. This mode is meant to help us debug various issues with
368 ticket 23847. To use this feature, compile with
369 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
370 environment variable. This is expected to crash a lot, and is
371 really meant for developers only. It will likely be removed in a
372 future release. Implements ticket 24583.
374 o Minor bugfixes (build, rust):
375 - Fix output of autoconf checks to display success messages for Rust
376 dependencies and a suitable rustc compiler version. Fixes bug
377 24612; bugfix on 0.3.1.3-alpha.
378 - Don't pass the --quiet option to cargo: it seems to suppress some
379 errors, which is not what we want to do when building. Fixes bug
380 24518; bugfix on 0.3.1.7.
381 - Build correctly when building from outside Tor's source tree with
382 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
385 o Minor bugfixes (C correctness):
386 - Fix a very unlikely (impossible, we believe) null pointer
387 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
388 Coverity; this is CID 1430932.
390 o Minor bugfixes (channel, client):
391 - Better identify client connection when reporting to the geoip
392 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
394 o Minor bugfixes (circuit, cannibalization):
395 - Don't cannibalize preemptively-built circuits if we no longer
396 recognize their first hop. This situation can happen if our Guard
397 relay went off the consensus after the circuit was created. Fixes
398 bug 24469; bugfix on 0.0.6.
400 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
401 - Don't consider Tor running as a client if the ControlPort is open,
402 but no actual client ports are open. Fixes bug 26062; bugfix
405 o Minor bugfixes (compilation):
406 - Fix a C99 compliance issue in our configuration script that caused
407 compilation issues when compiling Tor with certain versions of
408 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
410 o Minor bugfixes (controller):
411 - Restore the correct operation of the RESOLVE command, which had
412 been broken since we added the ability to enable/disable DNS on
413 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
414 - Avoid a (nonfatal) assertion failure when extending a one-hop
415 circuit from the controller to become a multihop circuit. Fixes
416 bug 24903; bugfix on 0.2.5.2-alpha.
418 o Minor bugfixes (correctness):
419 - Remove a nonworking, unnecessary check to see whether a circuit
420 hop's identity digest was set when the circuit failed. Fixes bug
421 24927; bugfix on 0.2.4.4-alpha.
423 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
424 - Upon receiving a malformed connected cell, stop processing the
425 cell immediately. Previously we would mark the connection for
426 close, but continue processing the cell as if the connection were
427 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
429 o Minor bugfixes (directory authorities, IPv6):
430 - When creating a routerstatus (vote) from a routerinfo (descriptor),
431 set the IPv6 address to the unspecified IPv6 address, and
432 explicitly initialize the port to zero. Fixes bug 24488; bugfix
435 o Minor bugfixes (documentation):
436 - Document that the PerConnBW{Rate,Burst} options will fall back to
437 their corresponding consensus parameters only if those parameters
438 are set. Previously we had claimed that these values would always
439 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
441 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
442 - Stop saying in the manual that clients cache ipv4 dns answers from
443 exit relays. We haven't used them since 0.2.6.3-alpha, and in
444 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
445 we forgot to say so in the man page. Fixes bug 26052; bugfix
448 o Minor bugfixes (exit relay DNS retries):
449 - Re-attempt timed-out DNS queries 3 times before failure, since our
450 timeout is 5 seconds for them, but clients wait 10-15. Also allow
451 slightly more timeouts per resolver when an exit has multiple
452 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
454 o Minor bugfixes (fallback directory mirrors):
455 - Make updateFallbackDirs.py search harder for python. (Some OSs
456 don't put it in /usr/bin.) Fixes bug 24708; bugfix
459 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
460 - When hibernating, close connections normally and allow them to
461 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
463 - Do not attempt to launch self-reachability tests when entering
464 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
465 - Resolve several bugs related to descriptor fetching on bridge
466 clients with bandwidth accounting enabled. (This combination is
467 not recommended!) Fixes a case of bug 12062; bugfix
469 - When hibernating, do not attempt to launch DNS checks. Fixes a
470 case of bug 12062; bugfix on 0.1.2.2-alpha.
471 - When hibernating, do not try to upload or download descriptors.
472 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
474 o Minor bugfixes (IPv6, bridges):
475 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
476 bugfix on 0.2.8.2-alpha.
477 - Tor now sets IPv6 address in the routerstatus as well as in the
478 router descriptors when updating addresses for a bridge. Closes
479 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
481 o Minor bugfixes (Linux seccomp2 sandbox):
482 - When running with the sandbox enabled, reload configuration files
483 correctly even when %include was used. Previously we would crash.
484 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
486 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
487 - Allow the nanosleep() system call, which glibc uses to implement
488 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
490 o Minor bugfixes (logging):
491 - Fix a (mostly harmless) race condition when invoking
492 LOG_PROTOCOL_WARN message from a subthread while the torrc options
493 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
495 o Minor bugfixes (man page, SocksPort):
496 - Remove dead code from the old "SocksSocket" option, and rename
497 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
498 option still works, but is deprecated. Fixes bug 24343; bugfix
501 o Minor bugfixes (memory leaks):
502 - Avoid possible at-exit memory leaks related to use of Libevent's
503 event_base_once() function. (This function tends to leak memory if
504 the event_base is closed before the event fires.) Fixes bug 24584;
505 bugfix on 0.2.8.1-alpha.
506 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
509 o Minor bugfixes (network IPv6 test):
510 - Tor's test scripts now check if "ping -6 ::1" works when the user
511 runs "make test-network-all". Fixes bug 24677; bugfix on
512 0.2.9.3-alpha. Patch by "ffmancera".
514 o Minor bugfixes (networking):
515 - string_is_valid_hostname() will not consider IP strings to be
516 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
518 o Minor bugfixes (onion service v3):
519 - Avoid an assertion failure when the next onion service descriptor
520 rotation type is out of sync with the consensus's valid-after
521 time. Instead, log a warning message with extra information, so we
522 can better hunt down the cause of this assertion. Fixes bug 25306;
523 bugfix on 0.3.2.1-alpha.
525 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
526 - Fix a memory leak when a v3 onion service is configured and gets a
527 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
528 - When parsing the descriptor signature, look for the token plus an
529 extra white-space at the end. This is more correct but also will
530 allow us to support new fields that might start with "signature".
531 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
533 o Minor bugfixes (onion services):
534 - If we are configured to offer a single onion service, don't log
535 long-term established one hop rendezvous points in the heartbeat.
536 Fixes bug 25116; bugfix on 0.2.9.6-rc.
538 o Minor bugfixes (performance):
539 - Reduce the number of circuits that will be opened at once during
540 the circuit build timeout phase. This is done by increasing the
541 idle timeout to 3 minutes, and lowering the maximum number of
542 concurrent learning circuits to 10. Fixes bug 24769; bugfix
544 - Avoid calling protocol_list_supports_protocol() from inside tight
545 loops when running with cached routerinfo_t objects. Instead,
546 summarize the relevant protocols as flags in the routerinfo_t, as
547 we do for routerstatus_t objects. This change simplifies our code
548 a little, and saves a large amount of short-term memory allocation
549 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
551 o Minor bugfixes (performance, timeouts):
552 - Consider circuits for timeout as soon as they complete a hop. This
553 is more accurate than applying the timeout in
554 circuit_expire_building() because that function is only called
555 once per second, which is now too slow for typical timeouts on the
556 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
557 - Use onion service circuits (and other circuits longer than 3 hops)
558 to calculate a circuit build timeout. Previously, Tor only
559 calculated its build timeout based on circuits that planned to be
560 exactly 3 hops long. With this change, we include measurements
561 from all circuits at the point where they complete their third
562 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
564 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
565 - Avoid a crash when running with DirPort set but ORPort tuned off.
566 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
568 o Minor bugfixes (Rust FFI):
569 - Fix a minor memory leak which would happen whenever the C code
570 would call the Rust implementation of
571 protover_get_supported_protocols(). This was due to the C version
572 returning a static string, whereas the Rust version newly allocated
573 a CString to pass across the FFI boundary. Consequently, the C
574 code was not expecting to need to free() what it was given. Fixes
575 bug 25127; bugfix on 0.3.2.1-alpha.
577 o Minor bugfixes (spelling):
578 - Use the "misspell" tool to detect and fix typos throughout the
579 source code. Fixes bug 23650; bugfix on various versions of Tor.
580 Patch from Deepesh Pathak.
582 o Minor bugfixes (testing):
583 - Avoid intermittent test failures due to a test that had relied on
584 onion service introduction point creation finishing within 5
585 seconds of real clock time. Fixes bug 25450; bugfix
587 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
588 bugfix on 0.2.3.1-alpha.
590 o Minor bugfixes (unit test, monotonic time):
591 - Increase a constant (1msec to 10msec) in the monotonic time test
592 that makes sure the nsec/usec/msec times read are synchronized.
593 This change was needed to accommodate slow systems like armel or
594 when the clock_gettime() is not a VDSO on the running kernel.
595 Fixes bug 25113; bugfix on 0.2.9.1.
597 o Code simplification and refactoring:
598 - Move the list of default directory authorities to its own file.
599 Closes ticket 24854. Patch by "beastr0".
600 - Remove the old (deterministic) directory retry logic entirely:
601 We've used exponential backoff exclusively for some time. Closes
603 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
605 - Remove a series of counters used to track circuit extend attempts
606 and connection status but that in reality we aren't using for
607 anything other than stats logged by a SIGUSR1 signal. Closes
609 - Remove /usr/athena from search path in configure.ac. Closes
611 - Remove duplicate code in node_has_curve25519_onion_key() and
612 node_get_curve25519_onion_key(), and add a check for a zero
613 microdesc curve25519 onion key. Closes ticket 23966, patch by
614 "aruna1234" and teor.
615 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
616 memory allocations with large numbers of OR connections (e.g.
617 relays). Closes ticket 24119.
618 - Separate the function that deletes ephemeral files when Tor
620 - Small changes to Tor's buf_t API to make it suitable for use as a
621 general-purpose safe string constructor. Closes ticket 22342.
622 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
623 avoid source code identifier confusion. Closes ticket 24467.
624 - The tor_git_revision[] constant no longer needs to be redeclared
625 by everything that links against the rest of Tor. Done as part of
626 ticket 23845, to simplify our external API.
627 - We make extend_info_from_node() use node_get_curve25519_onion_key()
628 introduced in ticket 23577 to access the curve25519 public keys
629 rather than accessing it directly. Closes ticket 23760. Patch by
631 - Add a function to log channels' scheduler state changes to aid
632 debugging efforts. Closes ticket 24531.
635 - Improved the documentation of AccountingStart parameter. Closes
637 - Update the documentation for "Log" to include the current list of
638 logging domains. Closes ticket 25378.
639 - Add documentation on how to build tor with Rust dependencies
640 without having to be online. Closes ticket 22907; bugfix
642 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
643 traffic. Closes ticket 24318.
644 - Document that OutboundBindAddress doesn't apply to DNS requests.
645 Closes ticket 22145. Patch from Aruna Maurya.
647 o Code simplification and refactoring (channels):
648 - Remove the incoming and outgoing channel queues. These were never
649 used, but still took up a step in our fast path.
650 - The majority of the channel unit tests have been rewritten and the
651 code coverage has now been raised to 83.6% for channel.c. Closes
653 - Remove other dead code from the channel subsystem: All together,
654 this cleanup has removed more than 1500 lines of code overall and
655 adding very little except for unit test.
657 o Code simplification and refactoring (circuit rendezvous):
658 - Split the client-side rendezvous circuit lookup into two
659 functions: one that returns only established circuits and another
660 that returns all kinds of circuits. Closes ticket 23459.
662 o Code simplification and refactoring (controller):
663 - Make most of the variables in networkstatus_getinfo_by_purpose()
664 const. Implements ticket 24489.
666 o Documentation (backport from 0.3.4.1-alpha):
667 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
668 ticket 25857. Patch from "CTassisF".
670 o Documentation (man page):
671 - The HiddenServiceVersion torrc option accepts only one number:
672 either version 2 or 3. Closes ticket 25026; bugfix
675 o Documentation (manpage, denial of service):
676 - Provide more detail about the denial-of-service options, by
677 listing each mitigation and explaining how they relate. Closes
681 Changes in version 0.3.1.10 - 2018-03-03
682 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
685 It includes an important security fix for a remote crash attack
686 against directory authorities, tracked as TROVE-2018-001.
688 This release also backports our new system for improved resistance to
689 denial-of-service attacks against relays.
691 This release also fixes several minor bugs and annoyances from
694 All directory authorities should upgrade to one of the versions
695 released today. Relays running 0.3.1.x may wish to update to one of
696 the versions released today, for the DoS mitigations.
698 Please note: according to our release calendar, Tor 0.3.1 will no
699 longer be supported after 1 July 2018. If you will be running Tor
700 after that date, you should make sure to plan to upgrade to the latest
701 stable version, or downgrade to 0.2.9 (which will receive long-term
704 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
705 - Fix a protocol-list handling bug that could be used to remotely crash
706 directory authorities with a null-pointer exception. Fixes bug 25074;
707 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
710 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
711 - Give relays some defenses against the recent network overload. We
712 start with three defenses (default parameters in parentheses).
713 First: if a single client address makes too many concurrent
714 connections (>100), hang up on further connections. Second: if a
715 single client address makes circuits too quickly (more than 3 per
716 second, with an allowed burst of 90) while also having too many
717 connections open (3), refuse new create cells for the next while
718 (1-2 hours). Third: if a client asks to establish a rendezvous
719 point to you directly, ignore the request. These defenses can be
720 manually controlled by new torrc options, but relays will also
721 take guidance from consensus parameters, so there's no need to
722 configure anything manually. Implements ticket 24902.
724 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
725 - Update the sandbox rules so that they should now work correctly
726 with Glibc 2.26. Closes ticket 24315.
728 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
729 - Fix an "off by 2" error in counting rendezvous failures on the
730 onion service side. While we thought we would stop the rendezvous
731 attempt after one failed circuit, we were actually making three
732 circuit attempts before giving up. Now switch to a default of 2,
733 and allow the consensus parameter "hs_service_max_rdv_failures" to
734 override. Fixes bug 24895; bugfix on 0.0.6.
736 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
737 - Add Link protocol version 5 to the supported protocols list. Fixes
738 bug 25070; bugfix on 0.3.1.1-alpha.
740 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
741 - Fix a set of false positives where relays would consider
742 connections to other relays as being client-only connections (and
743 thus e.g. deserving different link padding schemes) if those
744 relays fell out of the consensus briefly. Now we look only at the
745 initial handshake and whether the connection authenticated as a
746 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
748 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
749 - Make our OOM handler aware of the geoip client history cache so it
750 doesn't fill up the memory. This check is important for IPv6 and
751 our DoS mitigation subsystem. Closes ticket 25122.
753 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
754 - Change relay bandwidth reporting stats interval from 4 hours to 24
755 hours in order to reduce the efficiency of guard discovery
756 attacks. Fixes ticket 23856.
758 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
759 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
760 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
761 since they neither disabled TLS 1.3 nor enabled any of the
762 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
765 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
766 - The fallback directory list has been re-generated based on the
767 current status of the network. Tor uses fallback directories to
768 bootstrap when it doesn't yet have up-to-date directory
769 information. Closes ticket 24801.
770 - Make the default DirAuthorityFallbackRate 0.1, so that clients
771 prefer to bootstrap from fallback directory mirrors. This is a
772 follow-up to 24679, which removed weights from the default
773 fallbacks. Implements ticket 24681.
775 o Minor features (geoip):
776 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
779 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
780 - Use the actual observed address of an incoming relay connection,
781 not the canonical address of the relay from its descriptor, when
782 making decisions about how to handle the incoming connection.
783 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
785 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
786 - Directory authorities, when refusing a descriptor from a rejected
787 relay, now explicitly tell the relay (in its logs) to set a valid
788 ContactInfo address and contact the bad-relays@ mailing list.
789 Fixes bug 25170; bugfix on 0.2.9.1.
791 o Minor bugfixes (address selection, backport from 0.3.2.9):
792 - When the fascist_firewall_choose_address_ functions don't find a
793 reachable address, set the returned address to the null address
794 and port. This is a precautionary measure, because some callers do
795 not check the return value. Fixes bug 24736; bugfix
798 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
799 - Fetch descriptors aggressively whenever we lack enough to build
800 circuits, regardless of how many descriptors we are missing.
801 Previously, we would delay launching the fetch when we had fewer
802 than 15 missing descriptors, even if some of those descriptors
803 were blocking circuits from building. Fixes bug 23985; bugfix on
804 0.1.1.11-alpha. The effects of this bug became worse in
805 0.3.0.3-alpha, when we began treating missing descriptors from our
806 primary guards as a reason to delay circuits.
807 - Don't try fetching microdescriptors from relays that have failed
808 to deliver them in the past. Fixes bug 23817; bugfix
811 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
812 - Fix a signed/unsigned comparison warning introduced by our fix to
813 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
815 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
816 - Avoid a crash when attempting to use the seccomp2 sandbox together
817 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
820 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
821 - Fix a possible crash on malformed consensus. If a consensus had
822 contained an unparseable protocol line, it could have made clients
823 and relays crash with a null-pointer exception. To exploit this
824 issue, however, an attacker would need to be able to subvert the
825 directory authority system. Fixes bug 25251; bugfix on
826 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
828 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
829 - Recover better from empty or corrupt files in the consensus cache
830 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
831 - When a consensus diff calculation is only partially successful,
832 only record the successful parts as having succeeded. Partial
833 success can happen if (for example) one compression method fails
834 but the others succeed. Previously we misrecorded all the
835 calculations as having succeeded, which would later cause a
836 nonfatal assertion failure. Fixes bug 24086; bugfix
839 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
840 - Tor now updates its guard state when it reads a consensus
841 regardless of whether it's missing descriptors. That makes tor use
842 its primary guards to fetch descriptors in some edge cases where
843 it would previously have used fallback directories. Fixes bug
844 23862; bugfix on 0.3.0.1-alpha.
846 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
847 - Don't treat inability to store a cached consensus object as a bug:
848 it can happen normally when we are out of disk space. Fixes bug
849 24859; bugfix on 0.3.1.1-alpha.
851 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
852 - When queuing DESTROY cells on a channel, only queue the circuit-id
853 and reason fields: not the entire 514-byte cell. This fix should
854 help mitigate any bugs or attacks that fill up these queues, and
855 free more RAM for other uses. Fixes bug 24666; bugfix
858 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
859 - When closing a connection via close_connection_immediately(), we
860 mark it as "not blocked on bandwidth", to prevent later calls from
861 trying to unblock it, and give it permission to read. This fixes a
862 backtrace warning that can happen on relays under various
863 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
865 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
866 - When selecting relays by bandwidth, avoid a rounding error that
867 could sometimes cause load to be imbalanced incorrectly.
868 Previously, we would always round upwards; now, we round towards
869 the nearest integer. This had the biggest effect when a relay's
870 weight adjustments should have given it weight 0, but it got
871 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
872 - When calculating the fraction of nodes that have descriptors, and
873 all nodes in the network have zero bandwidths, count the number of
874 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
875 - Actually log the total bandwidth in compute_weighted_bandwidths().
876 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
878 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
879 - Improve the performance of our consensus-diff application code
880 when Tor is built with the --enable-fragile-hardening option set.
881 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
883 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
884 - Don't exit the Tor process if setrlimit() fails to change the file
885 limit (which can happen sometimes on some versions of OSX). Fixes
886 bug 21074; bugfix on 0.0.9pre5.
888 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
889 - Fix a bug in the bit-counting parts of our timing-wheel code on
890 MSVC. (Note that MSVC is still not a supported build platform, due
891 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
894 o Minor bugfixes (relay, partial backport):
895 - Make the internal channel_is_client() function look at what sort
896 of connection handshake the other side used, rather than whether
897 the other side ever sent a create_fast cell to us. Backports part
898 of the fixes from bugs 22805 and 24898.
900 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
901 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
903 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
904 bugfix on 0.2.9.4-alpha.
906 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
907 - Update the "rust dependencies" submodule to be a project-level
908 repository, rather than a user repository. Closes ticket 25323.
911 Changes in version 0.2.9.15 - 2018-03-03
912 Tor 0.2.9.15 backports important security and stability bugfixes from
915 It includes an important security fix for a remote crash attack
916 against directory authorities, tracked as TROVE-2018-001.
918 This release also backports our new system for improved resistance to
919 denial-of-service attacks against relays.
921 This release also fixes several minor bugs and annoyances from
924 All directory authorities should upgrade to one of the versions
925 released today. Relays running 0.2.9.x may wish to update to one of
926 the versions released today, for the DoS mitigations.
928 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
929 - Fix a protocol-list handling bug that could be used to remotely crash
930 directory authorities with a null-pointer exception. Fixes bug 25074;
931 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
934 o Major features (denial-of-service mitigation):
935 - Give relays some defenses against the recent network overload. We
936 start with three defenses (default parameters in parentheses).
937 First: if a single client address makes too many concurrent
938 connections (>100), hang up on further connections. Second: if a
939 single client address makes circuits too quickly (more than 3 per
940 second, with an allowed burst of 90) while also having too many
941 connections open (3), refuse new create cells for the next while
942 (1-2 hours). Third: if a client asks to establish a rendezvous
943 point to you directly, ignore the request. These defenses can be
944 manually controlled by new torrc options, but relays will also
945 take guidance from consensus parameters, so there's no need to
946 configure anything manually. Implements ticket 24902.
948 o Major bugfixes (bootstrapping):
949 - Fetch descriptors aggressively whenever we lack enough to build
950 circuits, regardless of how many descriptors we are missing.
951 Previously, we would delay launching the fetch when we had fewer
952 than 15 missing descriptors, even if some of those descriptors
953 were blocking circuits from building. Fixes bug 23985; bugfix on
954 0.1.1.11-alpha. The effects of this bug became worse in
955 0.3.0.3-alpha, when we began treating missing descriptors from our
956 primary guards as a reason to delay circuits.
958 o Major bugfixes (onion services, retry behavior):
959 - Fix an "off by 2" error in counting rendezvous failures on the
960 onion service side. While we thought we would stop the rendezvous
961 attempt after one failed circuit, we were actually making three
962 circuit attempts before giving up. Now switch to a default of 2,
963 and allow the consensus parameter "hs_service_max_rdv_failures" to
964 override. Fixes bug 24895; bugfix on 0.0.6.
966 o Minor feature (relay statistics):
967 - Change relay bandwidth reporting stats interval from 4 hours to 24
968 hours in order to reduce the efficiency of guard discovery
969 attacks. Fixes ticket 23856.
971 o Minor features (compatibility, OpenSSL):
972 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
973 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
974 since they neither disabled TLS 1.3 nor enabled any of the
975 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
978 o Minor features (denial-of-service avoidance):
979 - Make our OOM handler aware of the geoip client history cache so it
980 doesn't fill up the memory. This check is important for IPv6 and
981 our DoS mitigation subsystem. Closes ticket 25122.
983 o Minor features (fallback directory mirrors):
984 - The fallback directory list has been re-generated based on the
985 current status of the network. Tor uses fallback directories to
986 bootstrap when it doesn't yet have up-to-date directory
987 information. Closes ticket 24801.
988 - Make the default DirAuthorityFallbackRate 0.1, so that clients
989 prefer to bootstrap from fallback directory mirrors. This is a
990 follow-up to 24679, which removed weights from the default
991 fallbacks. Implements ticket 24681.
993 o Minor features (geoip):
994 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
997 o Minor features (linux seccomp2 sandbox):
998 - Update the sandbox rules so that they should now work correctly
999 with Glibc 2.26. Closes ticket 24315.
1001 o Minor bugfix (channel connection):
1002 - Use the actual observed address of an incoming relay connection,
1003 not the canonical address of the relay from its descriptor, when
1004 making decisions about how to handle the incoming connection.
1005 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1007 o Minor bugfix (directory authority):
1008 - Directory authorities, when refusing a descriptor from a rejected
1009 relay, now explicitly tell the relay (in its logs) to set a valid
1010 ContactInfo address and contact the bad-relays@ mailing list.
1011 Fixes bug 25170; bugfix on 0.2.9.1.
1013 o Minor bugfixes (address selection):
1014 - When the fascist_firewall_choose_address_ functions don't find a
1015 reachable address, set the returned address to the null address
1016 and port. This is a precautionary measure, because some callers do
1017 not check the return value. Fixes bug 24736; bugfix
1020 o Minor bugfixes (compilation):
1021 - Fix a signed/unsigned comparison warning introduced by our fix to
1022 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1024 o Minor bugfixes (control port, linux seccomp2 sandbox):
1025 - Avoid a crash when attempting to use the seccomp2 sandbox together
1026 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1029 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1030 - Fix a possible crash on malformed consensus. If a consensus had
1031 contained an unparseable protocol line, it could have made clients
1032 and relays crash with a null-pointer exception. To exploit this
1033 issue, however, an attacker would need to be able to subvert the
1034 directory authority system. Fixes bug 25251; bugfix on
1035 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1037 o Minor bugfixes (memory usage):
1038 - When queuing DESTROY cells on a channel, only queue the circuit-id
1039 and reason fields: not the entire 514-byte cell. This fix should
1040 help mitigate any bugs or attacks that fill up these queues, and
1041 free more RAM for other uses. Fixes bug 24666; bugfix
1044 o Minor bugfixes (network layer):
1045 - When closing a connection via close_connection_immediately(), we
1046 mark it as "not blocked on bandwidth", to prevent later calls from
1047 trying to unblock it, and give it permission to read. This fixes a
1048 backtrace warning that can happen on relays under various
1049 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1051 o Minor bugfixes (OSX):
1052 - Don't exit the Tor process if setrlimit() fails to change the file
1053 limit (which can happen sometimes on some versions of OSX). Fixes
1054 bug 21074; bugfix on 0.0.9pre5.
1056 o Minor bugfixes (path selection):
1057 - When selecting relays by bandwidth, avoid a rounding error that
1058 could sometimes cause load to be imbalanced incorrectly.
1059 Previously, we would always round upwards; now, we round towards
1060 the nearest integer. This had the biggest effect when a relay's
1061 weight adjustments should have given it weight 0, but it got
1062 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1063 - When calculating the fraction of nodes that have descriptors, and
1064 all nodes in the network have zero bandwidths, count the number of
1065 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1066 - Actually log the total bandwidth in compute_weighted_bandwidths().
1067 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1069 o Minor bugfixes (portability, msvc):
1070 - Fix a bug in the bit-counting parts of our timing-wheel code on
1071 MSVC. (Note that MSVC is still not a supported build platform, due
1072 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1075 o Minor bugfixes (relay):
1076 - Make the internal channel_is_client() function look at what sort
1077 of connection handshake the other side used, rather than whether
1078 the other side ever sent a create_fast cell to us. Backports part
1079 of the fixes from bugs 22805 and 24898.
1081 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1082 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1084 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1085 bugfix on 0.2.9.4-alpha.
1088 Changes in version 0.3.2.10 - 2018-03-03
1089 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
1090 backports a number of bugfixes, including important fixes for security
1093 It includes an important security fix for a remote crash attack
1094 against directory authorities, tracked as TROVE-2018-001.
1096 Additionally, it backports a fix for a bug whose severity we have
1097 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
1098 triggered in order to crash relays with a use-after-free pattern. As
1099 such, we are now tracking that bug as TROVE-2018-002 and
1100 CVE-2018-0491, and backporting it to earlier releases. This bug
1101 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
1104 This release also backports our new system for improved resistance to
1105 denial-of-service attacks against relays.
1107 This release also fixes several minor bugs and annoyances from
1110 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
1111 today, for the fix to TROVE-2018-002. Directory authorities should
1112 also upgrade. (Relays on earlier versions might want to update too for
1113 the DoS mitigations.)
1115 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1116 - Fix a protocol-list handling bug that could be used to remotely crash
1117 directory authorities with a null-pointer exception. Fixes bug 25074;
1118 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1121 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
1122 - Avoid adding the same channel twice in the KIST scheduler pending
1123 list, which could lead to remote denial-of-service use-after-free
1124 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
1126 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1127 - Give relays some defenses against the recent network overload. We
1128 start with three defenses (default parameters in parentheses).
1129 First: if a single client address makes too many concurrent
1130 connections (>100), hang up on further connections. Second: if a
1131 single client address makes circuits too quickly (more than 3 per
1132 second, with an allowed burst of 90) while also having too many
1133 connections open (3), refuse new create cells for the next while
1134 (1-2 hours). Third: if a client asks to establish a rendezvous
1135 point to you directly, ignore the request. These defenses can be
1136 manually controlled by new torrc options, but relays will also
1137 take guidance from consensus parameters, so there's no need to
1138 configure anything manually. Implements ticket 24902.
1140 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1141 - Fix an "off by 2" error in counting rendezvous failures on the
1142 onion service side. While we thought we would stop the rendezvous
1143 attempt after one failed circuit, we were actually making three
1144 circuit attempts before giving up. Now switch to a default of 2,
1145 and allow the consensus parameter "hs_service_max_rdv_failures" to
1146 override. Fixes bug 24895; bugfix on 0.0.6.
1147 - New-style (v3) onion services now obey the "max rendezvous circuit
1148 attempts" logic. Previously they would make as many rendezvous
1149 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1150 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1152 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1153 - Add Link protocol version 5 to the supported protocols list. Fixes
1154 bug 25070; bugfix on 0.3.1.1-alpha.
1156 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1157 - Fix a set of false positives where relays would consider
1158 connections to other relays as being client-only connections (and
1159 thus e.g. deserving different link padding schemes) if those
1160 relays fell out of the consensus briefly. Now we look only at the
1161 initial handshake and whether the connection authenticated as a
1162 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1164 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
1165 - The scheduler subsystem was failing to promptly notice changes in
1166 consensus parameters, making it harder to switch schedulers
1167 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1169 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1170 - Make our OOM handler aware of the geoip client history cache so it
1171 doesn't fill up the memory. This check is important for IPv6 and
1172 our DoS mitigation subsystem. Closes ticket 25122.
1174 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1175 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1176 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1177 since they neither disabled TLS 1.3 nor enabled any of the
1178 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1179 Closes ticket 24978.
1181 o Minor features (geoip):
1182 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1185 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
1186 - When logging a failure to create an onion service's descriptor,
1187 also log what the problem with the descriptor was. Diagnostic
1190 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1191 - Use the actual observed address of an incoming relay connection,
1192 not the canonical address of the relay from its descriptor, when
1193 making decisions about how to handle the incoming connection.
1194 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1196 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1197 - Fix a possible crash on malformed consensus. If a consensus had
1198 contained an unparseable protocol line, it could have made clients
1199 and relays crash with a null-pointer exception. To exploit this
1200 issue, however, an attacker would need to be able to subvert the
1201 directory authority system. Fixes bug 25251; bugfix on
1202 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1204 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1205 - Directory authorities, when refusing a descriptor from a rejected
1206 relay, now explicitly tell the relay (in its logs) to set a valid
1207 ContactInfo address and contact the bad-relays@ mailing list.
1208 Fixes bug 25170; bugfix on 0.2.9.1.
1210 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
1211 - When building with Rust on OSX, link against libresolv, to work
1212 around the issue at https://github.com/rust-lang/rust/issues/46797.
1213 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1215 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
1216 - Remove a BUG() statement when a client fetches an onion descriptor
1217 that has a lower revision counter than the one in its cache. This
1218 can happen in normal circumstances due to HSDir desync. Fixes bug
1219 24976; bugfix on 0.3.2.1-alpha.
1221 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1222 - Don't treat inability to store a cached consensus object as a bug:
1223 it can happen normally when we are out of disk space. Fixes bug
1224 24859; bugfix on 0.3.1.1-alpha.
1226 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1227 - Improve the performance of our consensus-diff application code
1228 when Tor is built with the --enable-fragile-hardening option set.
1229 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1231 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1232 - Don't exit the Tor process if setrlimit() fails to change the file
1233 limit (which can happen sometimes on some versions of OSX). Fixes
1234 bug 21074; bugfix on 0.0.9pre5.
1236 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1237 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1239 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1240 bugfix on 0.2.9.4-alpha.
1242 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
1243 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1244 25005; bugfix on 0.3.2.7-rc.
1246 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
1247 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1248 version, when deciding whether a consensus entry can support the
1249 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1250 bugfix on 0.3.2.1-alpha.
1252 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1253 - Update the "rust dependencies" submodule to be a project-level
1254 repository, rather than a user repository. Closes ticket 25323.
1256 o Documentation (backport from 0.3.3.1-alpha)
1257 - Document that operators who run more than one relay or bridge are
1258 expected to set MyFamily and ContactInfo correctly. Closes
1262 Changes in version 0.3.2.9 - 2018-01-09
1263 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
1265 The 0.3.2 series includes our long-anticipated new onion service
1266 design, with numerous security features. (For more information, see
1267 our blog post at https://blog.torproject.org/fall-harvest.) We also
1268 have a new circuit scheduler algorithm for improved performance on
1269 relays everywhere (see https://blog.torproject.org/kist-and-tell),
1270 along with many smaller features and bugfixes.
1272 Per our stable release policy, we plan to support each stable release
1273 series for at least the next nine months, or for three months after
1274 the first stable release of the next series: whichever is longer. If
1275 you need a release with long-term support, we recommend that you stay
1276 with the 0.2.9 series.
1278 Below is a list of the changes since 0.3.1.7. For a list of all
1279 changes since 0.3.2.8-rc, see the ChangeLog file.
1281 o Directory authority changes:
1282 - Add "Bastet" as a ninth directory authority to the default list.
1283 Closes ticket 23910.
1284 - The directory authority "Longclaw" has changed its IP address.
1285 Closes ticket 23592.
1286 - Remove longclaw's IPv6 address, as it will soon change. Authority
1287 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1288 3/8 directory authorities with IPv6 addresses, but there are also
1289 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1290 - Add an IPv6 address for the "bastet" directory authority. Closes
1293 o Major features (next-generation onion services):
1294 - Tor now supports the next-generation onion services protocol for
1295 clients and services! As part of this release, the core of
1296 proposal 224 has been implemented and is available for
1297 experimentation and testing by our users. This newer version of
1298 onion services ("v3") features many improvements over the legacy
1301 a) Better crypto (replaced SHA1/DH/RSA1024
1302 with SHA3/ed25519/curve25519)
1304 b) Improved directory protocol, leaking much less information to
1307 c) Improved directory protocol, with smaller surface for
1310 d) Better onion address security against impersonation.
1312 e) More extensible introduction/rendezvous protocol.
1314 f) A cleaner and more modular codebase.
1316 You can identify a next-generation onion address by its length:
1317 they are 56 characters long, as in
1318 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
1320 In the future, we will release more options and features for v3
1321 onion services, but we first need a testing period, so that the
1322 current codebase matures and becomes more robust. Planned features
1323 include: offline keys, advanced client authorization, improved
1324 guard algorithms, and statistics. For full details, see
1327 Legacy ("v2") onion services will still work for the foreseeable
1328 future, and will remain the default until this new codebase gets
1329 tested and hardened. Service operators who want to experiment with
1330 the new system can use the 'HiddenServiceVersion 3' torrc
1331 directive along with the regular onion service configuration
1332 options. For more information, see our blog post at
1333 "https://blog.torproject.org/fall-harvest". Enjoy!
1335 o Major feature (scheduler, channel):
1336 - Tor now uses new schedulers to decide which circuits should
1337 deliver cells first, in order to improve congestion at relays. The
1338 first type is called "KIST" ("Kernel Informed Socket Transport"),
1339 and is only available on Linux-like systems: it uses feedback from
1340 the kernel to prevent the kernel's TCP buffers from growing too
1341 full. The second new scheduler type is called "KISTLite": it
1342 behaves the same as KIST, but runs on systems without kernel
1343 support for inspecting TCP implementation details. The old
1344 scheduler is still available, under the name "Vanilla". To change
1345 the default scheduler preference order, use the new "Schedulers"
1346 option. (The default preference order is "KIST,KISTLite,Vanilla".)
1348 Matt Traudt implemented KIST, based on research by Rob Jansen,
1349 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
1350 more information, see the design paper at
1351 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
1352 followup implementation paper at https://arxiv.org/abs/1709.01044.
1353 Closes ticket 12541. For more information, see our blog post at
1354 "https://blog.torproject.org/kist-and-tell".
1356 o Major bugfixes (security, general):
1357 - Fix a denial of service bug where an attacker could use a
1358 malformed directory object to cause a Tor instance to pause while
1359 OpenSSL would try to read a passphrase from the terminal. (Tor
1360 instances run without a terminal, which is the case for most Tor
1361 packages, are not impacted.) Fixes bug 24246; bugfix on every
1362 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1363 Found by OSS-Fuzz as testcase 6360145429790720.
1365 o Major bugfixes (security, directory authority):
1366 - Fix a denial of service issue where an attacker could crash a
1367 directory authority using a malformed router descriptor. Fixes bug
1368 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1371 o Major bugfixes (security, onion service v2):
1372 - Fix a use-after-free error that could crash v2 Tor onion services
1373 when they failed to open circuits while expiring introduction
1374 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1375 also tracked as TROVE-2017-013 and CVE-2017-8823.
1376 - When checking for replays in the INTRODUCE1 cell data for a
1377 (legacy) onion service, correctly detect replays in the RSA-
1378 encrypted part of the cell. We were previously checking for
1379 replays on the entire cell, but those can be circumvented due to
1380 the malleability of Tor's legacy hybrid encryption. This fix helps
1381 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1382 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1385 o Major bugfixes (security, relay):
1386 - When running as a relay, make sure that we never build a path
1387 through ourselves, even in the case where we have somehow lost the
1388 version of our descriptor appearing in the consensus. Fixes part
1389 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1390 as TROVE-2017-012 and CVE-2017-8822.
1391 - When running as a relay, make sure that we never choose ourselves
1392 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1393 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1395 o Major bugfixes (bootstrapping):
1396 - Fetch descriptors aggressively whenever we lack enough to build
1397 circuits, regardless of how many descriptors we are missing.
1398 Previously, we would delay launching the fetch when we had fewer
1399 than 15 missing descriptors, even if some of those descriptors
1400 were blocking circuits from building. Fixes bug 23985; bugfix on
1401 0.1.1.11-alpha. The effects of this bug became worse in
1402 0.3.0.3-alpha, when we began treating missing descriptors from our
1403 primary guards as a reason to delay circuits.
1404 - Don't try fetching microdescriptors from relays that have failed
1405 to deliver them in the past. Fixes bug 23817; bugfix
1408 o Major bugfixes (circuit prediction):
1409 - Fix circuit prediction logic so that a client doesn't treat a port
1410 as being "handled" by a circuit if that circuit already has
1411 isolation settings on it. This change should make Tor clients more
1412 responsive by improving their chances of having a pre-created
1413 circuit ready for use when a request arrives. Fixes bug 18859;
1414 bugfix on 0.2.3.3-alpha.
1416 o Major bugfixes (exit relays, DNS):
1417 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1418 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1419 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1420 identifying and finding a workaround to this bug and to Moritz,
1421 Arthur Edelstein, and Roger for helping to track it down and
1424 o Major bugfixes (relay, crash, assertion failure):
1425 - Fix a timing-based assertion failure that could occur when the
1426 circuit out-of-memory handler freed a connection's output buffer.
1427 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1429 o Major bugfixes (usability, control port):
1430 - Report trusted clock skew indications as bootstrap errors, so
1431 controllers can more easily alert users when their clocks are
1432 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
1434 o Minor features (bridge):
1435 - Bridge relays can now set the BridgeDistribution config option to
1436 add a "bridge-distribution-request" line to their bridge
1437 descriptor, which tells BridgeDB how they'd like their bridge
1438 address to be given out. (Note that as of Oct 2017, BridgeDB does
1439 not yet implement this feature.) As a side benefit, this feature
1440 provides a way to distinguish bridge descriptors from non-bridge
1441 descriptors. Implements tickets 18329.
1442 - When handling the USERADDR command on an ExtOrPort, warn when the
1443 transports provides a USERADDR with no port. In a future version,
1444 USERADDR commands of this format may be rejected. Detects problems
1445 related to ticket 23080.
1447 o Minor features (bug detection):
1448 - Log a warning message with a stack trace for any attempt to call
1449 get_options() during option validation. This pattern has caused
1450 subtle bugs in the past. Closes ticket 22281.
1452 o Minor features (build, compilation):
1453 - The "check-changes" feature is now part of the "make check" tests;
1454 we'll use it to try to prevent misformed changes files from
1455 accumulating. Closes ticket 23564.
1456 - Tor builds should now fail if there are any mismatches between the
1457 C type representing a configuration variable and the C type the
1458 data-driven parser uses to store a value there. Previously, we
1459 needed to check these by hand, which sometimes led to mistakes.
1460 Closes ticket 23643.
1462 o Minor features (client):
1463 - You can now use Tor as a tunneled HTTP proxy: use the new
1464 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
1465 requests. Closes ticket 22407.
1466 - Add an extra check to make sure that we always use the newer guard
1467 selection code for picking our guards. Closes ticket 22779.
1468 - When downloading (micro)descriptors, don't split the list into
1469 multiple requests unless we want at least 32 descriptors.
1470 Previously, we split at 4, not 32, which led to significant
1471 overhead in HTTP request size and degradation in compression
1472 performance. Closes ticket 23220.
1473 - Improve log messages when missing descriptors for primary guards.
1474 Resolves ticket 23670.
1476 o Minor features (command line):
1477 - Add a new commandline option, --key-expiration, which prints when
1478 the current signing key is going to expire. Implements ticket
1479 17639; patch by Isis Lovecruft.
1481 o Minor features (control port):
1482 - If an application tries to use the control port as an HTTP proxy,
1483 respond with a meaningful "This is the Tor control port" message,
1484 and log the event. Closes ticket 1667. Patch from Ravi
1486 - Provide better error message for GETINFO desc/(id|name) when not
1487 fetching router descriptors. Closes ticket 5847. Patch by
1489 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
1490 whether Tor will try to download router descriptors and
1491 microdescriptors respectively. Closes ticket 22684.
1492 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
1493 so controllers can tell whether the geoip databases are loaded.
1494 Closes ticket 23237.
1495 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
1496 events. Closes ticket 19254. Patch by "DonnchaC".
1498 o Minor features (development support):
1499 - Developers can now generate a call-graph for Tor using the
1500 "calltool" python program, which post-processes object dumps. It
1501 should work okay on many Linux and OSX platforms, and might work
1502 elsewhere too. To run it, install calltool from
1503 https://gitweb.torproject.org/user/nickm/calltool.git and run
1504 "make callgraph". Closes ticket 19307.
1506 o Minor features (directory authority):
1507 - Make the "Exit" flag assignment only depend on whether the exit
1508 policy allows connections to ports 80 and 443. Previously relays
1509 would get the Exit flag if they allowed connections to one of
1510 these ports and also port 6667. Resolves ticket 23637.
1512 o Minor features (ed25519):
1513 - Add validation function to checks for torsion components in
1514 ed25519 public keys, used by prop224 client-side code. Closes
1515 ticket 22006. Math help by Ian Goldberg.
1517 o Minor features (exit relay, DNS):
1518 - Improve the clarity and safety of the log message from evdns when
1519 receiving an apparently spoofed DNS reply. Closes ticket 3056.
1521 o Minor features (fallback directory mirrors):
1522 - The fallback directory list has been re-generated based on the
1523 current status of the network. Tor uses fallback directories to
1524 bootstrap when it doesn't yet have up-to-date directory
1525 information. Closes ticket 24801.
1526 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1527 prefer to bootstrap from fallback directory mirrors. This is a
1528 follow-up to 24679, which removed weights from the default
1529 fallbacks. Implements ticket 24681.
1531 o Minor features (geoip):
1532 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
1535 o Minor features (integration, hardening):
1536 - Add a new NoExec option to prevent Tor from running other
1537 programs. When this option is set to 1, Tor will never try to run
1538 another program, regardless of the settings of
1539 PortForwardingHelper, ClientTransportPlugin, or
1540 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
1541 without restarting Tor. Closes ticket 22976.
1543 o Minor features (linux seccomp2 sandbox):
1544 - Update the sandbox rules so that they should now work correctly
1545 with Glibc 2.26. Closes ticket 24315.
1547 o Minor features (logging):
1548 - Provide better warnings when the getrandom() syscall fails. Closes
1550 - Downgrade a pair of log messages that could occur when an exit's
1551 resolver gave us an unusual (but not forbidden) response. Closes
1553 - Improve the message we log when re-enabling circuit build timeouts
1554 after having received a consensus. Closes ticket 20963.
1555 - Log more circuit information whenever we are about to try to
1556 package a relay cell on a circuit with a nonexistent n_chan.
1557 Attempt to diagnose ticket 8185.
1558 - Improve info-level log identification of particular circuits, to
1559 help with debugging. Closes ticket 23645.
1560 - Improve the warning message for specifying a relay by nickname.
1561 The previous message implied that nickname registration was still
1562 part of the Tor network design, which it isn't. Closes
1564 - If the sandbox filter fails to load, suggest to the user that
1565 their kernel might not support seccomp2. Closes ticket 23090.
1567 o Minor features (onion service, circuit, logging):
1568 - Improve logging of many callsite in the circuit subsystem to print
1569 the circuit identifier(s).
1570 - Log when we cleanup an intro point from a service so we know when
1571 and for what reason it happened. Closes ticket 23604.
1573 o Minor features (portability):
1574 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
1575 (It doesn't yet work with the sandbox enabled.) Closes
1577 - Check at configure time whether uint8_t is the same type as
1578 unsigned char. Lots of existing code already makes this
1579 assumption, and there could be strict aliasing issues if the
1580 assumption is violated. Closes ticket 22410.
1582 o Minor features (relay):
1583 - When choosing which circuits can be expired as unused, consider
1584 circuits from clients even if those clients used regular CREATE
1585 cells to make them; and do not consider circuits from relays even
1586 if they were made with CREATE_FAST. Part of ticket 22805.
1587 - Reject attempts to use relative file paths when RunAsDaemon is
1588 set. Previously, Tor would accept these, but the directory-
1589 changing step of RunAsDaemon would give strange and/or confusing
1590 results. Closes ticket 22731.
1592 o Minor features (relay statistics):
1593 - Change relay bandwidth reporting stats interval from 4 hours to 24
1594 hours in order to reduce the efficiency of guard discovery
1595 attacks. Fixes ticket 23856.
1597 o Minor features (reverted deprecations):
1598 - The ClientDNSRejectInternalAddresses flag can once again be set in
1599 non-testing Tor networks, so long as they do not use the default
1600 directory authorities. This change also removes the deprecation of
1601 this flag from 0.2.9.2-alpha. Closes ticket 21031.
1603 o Minor features (robustness):
1604 - Change several fatal assertions when flushing buffers into non-
1605 fatal assertions, to prevent any recurrence of 23690.
1607 o Minor features (startup, safety):
1608 - When configured to write a PID file, Tor now exits if it is unable
1609 to do so. Previously, it would warn and continue. Closes
1612 o Minor features (static analysis):
1613 - The BUG() macro has been changed slightly so that Coverity no
1614 longer complains about dead code if the bug is impossible. Closes
1617 o Minor features (testing):
1618 - Our fuzzing tests now test the encrypted portions of v3 onion
1619 service descriptors. Implements more of 21509.
1620 - Add a unit test to make sure that our own generated platform
1621 string will be accepted by directory authorities. Closes
1623 - The default chutney network tests now include tests for the v3
1624 onion service design. Make sure you have the latest version of
1625 chutney if you want to run these. Closes ticket 22437.
1626 - Add a unit test to verify that we can parse a hardcoded v2 onion
1627 service descriptor. Closes ticket 15554.
1629 o Minor bugfixes (address selection):
1630 - When the fascist_firewall_choose_address_ functions don't find a
1631 reachable address, set the returned address to the null address
1632 and port. This is a precautionary measure, because some callers do
1633 not check the return value. Fixes bug 24736; bugfix
1636 o Minor bugfixes (bootstrapping):
1637 - When warning about state file clock skew, report the correct
1638 direction for the detected skew. Fixes bug 23606; bugfix
1641 o Minor bugfixes (bridge clients, bootstrap):
1642 - Retry directory downloads when we get our first bridge descriptor
1643 during bootstrap or while reconnecting to the network. Keep
1644 retrying every time we get a bridge descriptor, until we have a
1645 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
1646 - Stop delaying bridge descriptor fetches when we have cached bridge
1647 descriptors. Instead, only delay bridge descriptor fetches when we
1648 have at least one reachable bridge. Fixes part of bug 24367;
1649 bugfix on 0.2.0.3-alpha.
1650 - Stop delaying directory fetches when we have cached bridge
1651 descriptors. Instead, only delay bridge descriptor fetches when
1652 all our bridges are definitely unreachable. Fixes part of bug
1653 24367; bugfix on 0.2.0.3-alpha.
1655 o Minor bugfixes (bridge):
1656 - Overwrite the bridge address earlier in the process of retrieving
1657 its descriptor, to make sure we reach it on the configured
1658 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
1660 o Minor bugfixes (build, compilation):
1661 - Fix a compilation warning when building with zstd support on
1662 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1663 and fixed by Andreas Stieger.
1664 - When searching for OpenSSL, don't accept any OpenSSL library that
1665 lacks TLSv1_1_method(): Tor doesn't build with those versions.
1666 Additionally, look in /usr/local/opt/openssl, if it's present.
1667 These changes together repair the default build on OSX systems
1668 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
1669 - Fix a signed/unsigned comparison warning introduced by our fix to
1670 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1671 - Fix a memory leak warning in one of the libevent-related
1672 configuration tests that could occur when manually specifying
1673 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
1674 Found and patched by Alex Xu.
1675 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
1676 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1678 o Minor bugfixes (certificate handling):
1679 - Fix a time handling bug in Tor certificates set to expire after
1680 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
1681 Coverity as CID 1415728.
1683 o Minor bugfixes (client):
1684 - By default, do not enable storage of client-side DNS values. These
1685 values were unused by default previously, but they should not have
1686 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
1688 o Minor bugfixes (client, usability):
1689 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
1690 SOCKS4a requests that contain IP address strings, even when
1691 SafeSocks in enabled, as this prevents user from connecting to
1692 known IP addresses without relying on DNS for resolving. SafeSocks
1693 still rejects SOCKS connections that connect to IP addresses when
1694 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
1695 bugfix on Tor 0.2.6.2-alpha.
1697 o Minor bugfixes (code correctness):
1698 - Call htons() in extend_cell_format() for encoding a 16-bit value.
1699 Previously we used ntohs(), which happens to behave the same on
1700 all the platforms we support, but which isn't really correct.
1701 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
1702 - For defense-in-depth, make the controller's write_escaped_data()
1703 function robust to extremely long inputs. Fixes bug 19281; bugfix
1704 on 0.1.1.1-alpha. Reported by Guido Vranken.
1705 - Fix several places in our codebase where a C compiler would be
1706 likely to eliminate a check, based on assuming that undefined
1707 behavior had not happened elsewhere in the code. These cases are
1708 usually a sign of redundant checking or dubious arithmetic. Found
1709 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
1710 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
1713 o Minor bugfixes (compression):
1714 - Handle a pathological case when decompressing Zstandard data when
1715 the output buffer size is zero. Fixes bug 23551; bugfix
1718 o Minor bugfixes (consensus expiry):
1719 - Check for adequate directory information correctly. Previously, Tor
1720 would reconsider whether it had sufficient directory information
1721 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
1723 o Minor bugfixes (control port, linux seccomp2 sandbox):
1724 - Avoid a crash when attempting to use the seccomp2 sandbox together
1725 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1728 o Minor bugfixes (control port, onion services):
1729 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
1730 HS_DESC event when a service is not able to upload a descriptor.
1731 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
1733 o Minor bugfixes (directory cache):
1734 - Recover better from empty or corrupt files in the consensus cache
1735 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1736 - When a consensus diff calculation is only partially successful,
1737 only record the successful parts as having succeeded. Partial
1738 success can happen if (for example) one compression method fails
1739 but the others succeed. Previously we misrecorded all the
1740 calculations as having succeeded, which would later cause a
1741 nonfatal assertion failure. Fixes bug 24086; bugfix
1744 o Minor bugfixes (directory client):
1745 - On failure to download directory information, delay retry attempts
1746 by a random amount based on the "decorrelated jitter" algorithm.
1747 Our previous delay algorithm tended to produce extra-long delays
1748 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
1750 o Minor bugfixes (directory protocol):
1751 - Directory servers now include a "Date:" http header for response
1752 codes other than 200. Clients starting with a skewed clock and a
1753 recent consensus were getting "304 Not modified" responses from
1754 directory authorities, so without the Date header, the client
1755 would never hear about a wrong clock. Fixes bug 23499; bugfix
1757 - Make clients wait for 6 seconds before trying to download a
1758 consensus from an authority. Fixes bug 17750; bugfix
1761 o Minor bugfixes (documentation):
1762 - Document better how to read gcov, and what our gcov postprocessing
1763 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
1764 - Fix manpage to not refer to the obsolete (and misspelled)
1765 UseEntryGuardsAsDirectoryGuards parameter in the description of
1766 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
1768 o Minor bugfixes (DoS-resistance):
1769 - If future code asks if there are any running bridges, without
1770 checking if bridges are enabled, log a BUG warning rather than
1771 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
1773 o Minor bugfixes (entry guards):
1774 - Tor now updates its guard state when it reads a consensus
1775 regardless of whether it's missing descriptors. That makes tor use
1776 its primary guards to fetch descriptors in some edge cases where
1777 it would previously have used fallback directories. Fixes bug
1778 23862; bugfix on 0.3.0.1-alpha.
1780 o Minor bugfixes (format strictness):
1781 - Restrict several data formats to decimal. Previously, the
1782 BuildTimeHistogram entries in the state file, the "bw=" entries in
1783 the bandwidth authority file, and the process IDs passed to the
1784 __OwningControllerProcess option could all be specified in hex or
1785 octal as well as in decimal. This was not an intentional feature.
1786 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
1789 o Minor bugfixes (heartbeat):
1790 - If we fail to write a heartbeat message, schedule a retry for the
1791 minimum heartbeat interval number of seconds in the future. Fixes
1792 bug 19476; bugfix on 0.2.3.1-alpha.
1794 o Minor bugfixes (logging):
1795 - Suppress a log notice when relay descriptors arrive. We already
1796 have a bootstrap progress for this so no need to log notice
1797 everytime tor receives relay descriptors. Microdescriptors behave
1798 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
1799 - Remove duplicate log messages regarding opening non-local
1800 SocksPorts upon parsing config and opening listeners at startup.
1801 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
1802 - Use a more comprehensible log message when telling the user
1803 they've excluded every running exit node. Fixes bug 7890; bugfix
1805 - When logging the number of descriptors we intend to download per
1806 directory request, do not log a number higher than then the number
1807 of descriptors we're fetching in total. Fixes bug 19648; bugfix
1809 - When warning about a directory owned by the wrong user, log the
1810 actual name of the user owning the directory. Previously, we'd log
1811 the name of the process owner twice. Fixes bug 23487; bugfix
1813 - Fix some messages on unexpected errors from the seccomp2 library.
1814 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
1815 - The tor specification says hop counts are 1-based, so fix two log
1816 messages that mistakenly logged 0-based hop counts. Fixes bug
1817 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
1818 Credit to Xiaofan Li for reporting this issue.
1820 o Minor bugfixes (logging, relay shutdown, annoyance):
1821 - When a circuit is marked for close, do not attempt to package any
1822 cells for channels on that circuit. Previously, we would detect
1823 this condition lower in the call stack, when we noticed that the
1824 circuit had no attached channel, and log an annoying message.
1825 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1827 o Minor bugfixes (memory safety, defensive programming):
1828 - Clear the target address when node_get_prim_orport() returns
1829 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1831 o Minor bugfixes (memory usage):
1832 - When queuing DESTROY cells on a channel, only queue the circuit-id
1833 and reason fields: not the entire 514-byte cell. This fix should
1834 help mitigate any bugs or attacks that fill up these queues, and
1835 free more RAM for other uses. Fixes bug 24666; bugfix
1838 o Minor bugfixes (network layer):
1839 - When closing a connection via close_connection_immediately(), we
1840 mark it as "not blocked on bandwidth", to prevent later calls from
1841 trying to unblock it, and give it permission to read. This fixes a
1842 backtrace warning that can happen on relays under various
1843 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1845 o Minor bugfixes (onion services):
1846 - The introduction circuit was being timed out too quickly while
1847 waiting for the rendezvous circuit to complete. Keep the intro
1848 circuit around longer instead of timing out and reopening new ones
1849 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
1850 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1851 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1853 - When handling multiple SOCKS request for the same .onion address,
1854 only fetch the service descriptor once.
1855 - Avoid a possible double close of a circuit by the intro point on
1856 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1857 bugfix on 0.3.0.1-alpha.
1858 - When reloading configured onion services, copy all information
1859 from the old service object. Previously, some data was omitted,
1860 causing delays in descriptor upload, and other bugs. Fixes bug
1861 23790; bugfix on 0.2.1.9-alpha.
1863 o Minor bugfixes (path selection):
1864 - When selecting relays by bandwidth, avoid a rounding error that
1865 could sometimes cause load to be imbalanced incorrectly.
1866 Previously, we would always round upwards; now, we round towards
1867 the nearest integer. This had the biggest effect when a relay's
1868 weight adjustments should have given it weight 0, but it got
1869 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1870 - When calculating the fraction of nodes that have descriptors, and
1871 all nodes in the network have zero bandwidths, count the number of
1872 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1873 - Actually log the total bandwidth in compute_weighted_bandwidths().
1874 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1876 o Minor bugfixes (portability):
1877 - Stop using the PATH_MAX variable, which is not defined on GNU
1878 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
1879 - Fix a bug in the bit-counting parts of our timing-wheel code on
1880 MSVC. (Note that MSVC is still not a supported build platform, due
1881 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1884 o Minor bugfixes (relay):
1885 - When uploading our descriptor for the first time after startup,
1886 report the reason for uploading as "Tor just started" rather than
1887 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
1888 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1889 relays, to prevent spurious address resolutions and descriptor
1890 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1891 bugfix on in 0.2.8.1-alpha.
1892 - Avoid a crash when transitioning from client mode to bridge mode.
1893 Previously, we would launch the worker threads whenever our
1894 "public server" mode changed, but not when our "server" mode
1895 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1897 o Minor bugfixes (testing):
1898 - Fix a spurious fuzzing-only use of an uninitialized value. Found
1899 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
1900 - Test that IPv6-only clients can use microdescriptors when running
1901 "make test-network-all". Requires chutney master 61c28b9 or later.
1902 Closes ticket 24109.
1903 - Prevent scripts/test/coverage from attempting to move gcov output
1904 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
1905 - Capture and detect several "Result does not fit" warnings in unit
1906 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
1908 - Fix additional channelpadding unit test failures by using mocked
1909 time instead of actual time for all tests. Fixes bug 23608; bugfix
1911 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
1912 to correctly handle cases where a caller gives it an RSA key of
1913 under 160 bits. (This is not actually a bug in Tor itself, but
1914 rather in our fuzzing code.) Fixes bug 24247; bugfix on
1915 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
1916 - Fix a broken unit test for the OutboundAddress option: the parsing
1917 function was never returning an error on failure. Fixes bug 23366;
1918 bugfix on 0.3.0.3-alpha.
1919 - Fix a signed-integer overflow in the unit tests for
1920 dir/download_status_random_backoff, which was untriggered until we
1921 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1923 o Minor bugfixes (usability, control port):
1924 - Stop making an unnecessary routerlist check in NETINFO clock skew
1925 detection; this was preventing clients from reporting NETINFO clock
1926 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1928 o Code simplification and refactoring:
1929 - Remove various ways of testing circuits and connections for
1930 "clientness"; instead, favor channel_is_client(). Part of
1932 - Extract the code for handling newly-open channels into a separate
1933 function from the general code to handle channel state
1934 transitions. This change simplifies our callgraph, reducing the
1935 size of the largest strongly connected component by roughly a
1936 factor of two. Closes ticket 22608.
1937 - Remove dead code for largely unused statistics on the number of
1938 times we've attempted various public key operations. Fixes bug
1939 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1940 - Remove several now-obsolete functions for asking about old
1941 variants directory authority status. Closes ticket 22311; patch
1943 - Remove some of the code that once supported "Named" and "Unnamed"
1944 routers. Authorities no longer vote for these flags. Closes
1946 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1947 and old hidden services, to indicate that they aren't suitable for
1948 new protocols or formats. Closes ticket 23026.
1949 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1950 22521. Patch from Neel Chauhan.
1951 - Split the enormous circuit_send_next_onion_skin() function into
1952 multiple subfunctions. Closes ticket 22804.
1953 - Split the portions of the buffer.c module that handle particular
1954 protocols into separate modules. Part of ticket 23149.
1955 - Use our test macros more consistently, to produce more useful
1956 error messages when our unit tests fail. Add coccinelle patches to
1957 allow us to re-check for test macro uses. Closes ticket 22497.
1959 o Deprecated features:
1960 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
1961 now deprecated; they do not apply to relays, and they have had no
1962 effect on clients since 0.2.8.x. Closes ticket 19704.
1963 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1964 only applies to direct unencrypted HTTP connections to your
1965 directory server, which your Tor probably isn't using. Closes
1969 - Add notes in man page regarding OS support for the various
1970 scheduler types. Attempt to use less jargon in the scheduler
1971 section. Closes ticket 24254.
1972 - Clarify that the Address option is entirely about setting an
1973 advertised IPv4 address. Closes ticket 18891.
1974 - Clarify the manpage's use of the term "address" to clarify what
1975 kind of address is intended. Closes ticket 21405.
1976 - Document that onion service subdomains are allowed, and ignored.
1977 Closes ticket 18736.
1978 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1979 kernels. Closes ticket 22677.
1980 - Document all values of PublishServerDescriptor in the manpage.
1981 Closes ticket 15645.
1982 - Improve the documentation for the directory port part of the
1983 DirAuthority line. Closes ticket 20152.
1984 - Restore documentation for the authorities' "approved-routers"
1985 file. Closes ticket 21148.
1988 - The AllowDotExit option has been removed as unsafe. It has been
1989 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1990 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1991 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1992 Closes ticket 21031.
1993 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1994 nobody was using it any longer. Closes ticket 22377.
1997 Changes in version 0.3.1.9 - 2017-12-01:
1998 Tor 0.3.1.9 backports important security and stability fixes from the
1999 0.3.2 development series. All Tor users should upgrade to this
2000 release, or to another of the releases coming out today.
2002 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2003 - Fix a denial of service bug where an attacker could use a
2004 malformed directory object to cause a Tor instance to pause while
2005 OpenSSL would try to read a passphrase from the terminal. (Tor
2006 instances run without a terminal, which is the case for most Tor
2007 packages, are not impacted.) Fixes bug 24246; bugfix on every
2008 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2009 Found by OSS-Fuzz as testcase 6360145429790720.
2010 - Fix a denial of service issue where an attacker could crash a
2011 directory authority using a malformed router descriptor. Fixes bug
2012 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2014 - When checking for replays in the INTRODUCE1 cell data for a
2015 (legacy) onion service, correctly detect replays in the RSA-
2016 encrypted part of the cell. We were previously checking for
2017 replays on the entire cell, but those can be circumvented due to
2018 the malleability of Tor's legacy hybrid encryption. This fix helps
2019 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2020 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2023 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2024 - Fix a use-after-free error that could crash v2 Tor onion services
2025 when they failed to open circuits while expiring introduction
2026 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2027 also tracked as TROVE-2017-013 and CVE-2017-8823.
2029 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2030 - When running as a relay, make sure that we never build a path
2031 through ourselves, even in the case where we have somehow lost the
2032 version of our descriptor appearing in the consensus. Fixes part
2033 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2034 as TROVE-2017-012 and CVE-2017-8822.
2035 - When running as a relay, make sure that we never choose ourselves
2036 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2037 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2039 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2040 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2041 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2042 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2043 identifying and finding a workaround to this bug and to Moritz,
2044 Arthur Edelstein, and Roger for helping to track it down and
2047 o Minor features (bridge):
2048 - Bridges now include notice in their descriptors that they are
2049 bridges, and notice of their distribution status, based on their
2050 publication settings. Implements ticket 18329. For more fine-
2051 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2054 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2055 - Add an IPv6 address for the "bastet" directory authority. Closes
2058 o Minor features (geoip):
2059 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2062 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2063 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2064 relays, to prevent spurious address resolutions and descriptor
2065 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2066 bugfix on in 0.2.8.1-alpha.
2068 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2069 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2070 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2072 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2073 - When a circuit is marked for close, do not attempt to package any
2074 cells for channels on that circuit. Previously, we would detect
2075 this condition lower in the call stack, when we noticed that the
2076 circuit had no attached channel, and log an annoying message.
2077 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2079 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
2080 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2081 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2084 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2085 - Avoid a crash when transitioning from client mode to bridge mode.
2086 Previously, we would launch the worker threads whenever our
2087 "public server" mode changed, but not when our "server" mode
2088 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2091 Changes in version 0.3.0.13 - 2017-12-01
2092 Tor 0.3.0.13 backports important security and stability bugfixes from
2093 later Tor releases. All Tor users should upgrade to this release, or
2094 to another of the releases coming out today.
2096 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2097 2018. If you need a release with long-term support, please stick with
2098 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2100 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2101 - Fix a denial of service bug where an attacker could use a
2102 malformed directory object to cause a Tor instance to pause while
2103 OpenSSL would try to read a passphrase from the terminal. (Tor
2104 instances run without a terminal, which is the case for most Tor
2105 packages, are not impacted.) Fixes bug 24246; bugfix on every
2106 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2107 Found by OSS-Fuzz as testcase 6360145429790720.
2108 - Fix a denial of service issue where an attacker could crash a
2109 directory authority using a malformed router descriptor. Fixes bug
2110 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2112 - When checking for replays in the INTRODUCE1 cell data for a
2113 (legacy) onion service, correctly detect replays in the RSA-
2114 encrypted part of the cell. We were previously checking for
2115 replays on the entire cell, but those can be circumvented due to
2116 the malleability of Tor's legacy hybrid encryption. This fix helps
2117 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2118 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2121 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2122 - Fix a use-after-free error that could crash v2 Tor onion services
2123 when they failed to open circuits while expiring introduction
2124 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2125 also tracked as TROVE-2017-013 and CVE-2017-8823.
2127 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2128 - When running as a relay, make sure that we never build a path
2129 through ourselves, even in the case where we have somehow lost the
2130 version of our descriptor appearing in the consensus. Fixes part
2131 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2132 as TROVE-2017-012 and CVE-2017-8822.
2133 - When running as a relay, make sure that we never choose ourselves
2134 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2135 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2137 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2138 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2139 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2140 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2141 identifying and finding a workaround to this bug and to Moritz,
2142 Arthur Edelstein, and Roger for helping to track it down and
2145 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2146 - Enable a couple of pieces of Windows hardening: one
2147 (HeapEnableTerminationOnCorruption) that has been on-by-default
2148 since Windows 8, and unavailable before Windows 7; and one
2149 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2150 affect us, but shouldn't do any harm. Closes ticket 21953.
2152 o Minor features (bridge, backport from 0.3.1.9):
2153 - Bridges now include notice in their descriptors that they are
2154 bridges, and notice of their distribution status, based on their
2155 publication settings. Implements ticket 18329. For more fine-
2156 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2159 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2160 - Add an IPv6 address for the "bastet" directory authority. Closes
2163 o Minor features (geoip):
2164 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2167 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2168 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2169 relays, to prevent spurious address resolutions and descriptor
2170 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2171 bugfix on in 0.2.8.1-alpha.
2173 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2174 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2175 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2177 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2178 - When a circuit is marked for close, do not attempt to package any
2179 cells for channels on that circuit. Previously, we would detect
2180 this condition lower in the call stack, when we noticed that the
2181 circuit had no attached channel, and log an annoying message.
2182 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2184 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2185 - Avoid a crash when transitioning from client mode to bridge mode.
2186 Previously, we would launch the worker threads whenever our
2187 "public server" mode changed, but not when our "server" mode
2188 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2190 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2191 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2192 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2195 Changes in version 0.2.9.14 - 2017-12-01
2196 Tor 0.3.0.13 backports important security and stability bugfixes from
2197 later Tor releases. All Tor users should upgrade to this release, or
2198 to another of the releases coming out today.
2200 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2201 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2202 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2203 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2204 identifying and finding a workaround to this bug and to Moritz,
2205 Arthur Edelstein, and Roger for helping to track it down and
2208 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2209 - Fix a denial of service bug where an attacker could use a
2210 malformed directory object to cause a Tor instance to pause while
2211 OpenSSL would try to read a passphrase from the terminal. (Tor
2212 instances run without a terminal, which is the case for most Tor
2213 packages, are not impacted.) Fixes bug 24246; bugfix on every
2214 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2215 Found by OSS-Fuzz as testcase 6360145429790720.
2216 - Fix a denial of service issue where an attacker could crash a
2217 directory authority using a malformed router descriptor. Fixes bug
2218 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2220 - When checking for replays in the INTRODUCE1 cell data for a
2221 (legacy) onion service, correctly detect replays in the RSA-
2222 encrypted part of the cell. We were previously checking for
2223 replays on the entire cell, but those can be circumvented due to
2224 the malleability of Tor's legacy hybrid encryption. This fix helps
2225 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2226 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2229 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2230 - Fix a use-after-free error that could crash v2 Tor onion services
2231 when they failed to open circuits while expiring introduction
2232 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2233 also tracked as TROVE-2017-013 and CVE-2017-8823.
2235 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2236 - When running as a relay, make sure that we never build a path
2237 through ourselves, even in the case where we have somehow lost the
2238 version of our descriptor appearing in the consensus. Fixes part
2239 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2240 as TROVE-2017-012 and CVE-2017-8822.
2242 o Minor features (bridge, backport from 0.3.1.9):
2243 - Bridges now include notice in their descriptors that they are
2244 bridges, and notice of their distribution status, based on their
2245 publication settings. Implements ticket 18329. For more fine-
2246 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2249 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2250 - Add an IPv6 address for the "bastet" directory authority. Closes
2253 o Minor features (geoip):
2254 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2257 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2258 - Enable a couple of pieces of Windows hardening: one
2259 (HeapEnableTerminationOnCorruption) that has been on-by-default
2260 since Windows 8, and unavailable before Windows 7; and one
2261 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2262 affect us, but shouldn't do any harm. Closes ticket 21953.
2264 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2265 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2266 relays, to prevent spurious address resolutions and descriptor
2267 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2268 bugfix on in 0.2.8.1-alpha.
2270 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2271 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2272 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2274 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2275 - When a circuit is marked for close, do not attempt to package any
2276 cells for channels on that circuit. Previously, we would detect
2277 this condition lower in the call stack, when we noticed that the
2278 circuit had no attached channel, and log an annoying message.
2279 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2281 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2282 - Avoid a crash when transitioning from client mode to bridge mode.
2283 Previously, we would launch the worker threads whenever our
2284 "public server" mode changed, but not when our "server" mode
2285 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2287 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2288 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2289 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2292 Changes in version 0.2.8.17 - 2017-12-01
2293 Tor 0.2.8.17 backports important security and stability bugfixes from
2294 later Tor releases. All Tor users should upgrade to this release, or
2295 to another of the releases coming out today.
2297 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2298 2018. If you need a release with long-term support, please upgrade with
2299 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2301 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2302 - Fix a denial of service bug where an attacker could use a
2303 malformed directory object to cause a Tor instance to pause while
2304 OpenSSL would try to read a passphrase from the terminal. (Tor
2305 instances run without a terminal, which is the case for most Tor
2306 packages, are not impacted.) Fixes bug 24246; bugfix on every
2307 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2308 Found by OSS-Fuzz as testcase 6360145429790720.
2309 - When checking for replays in the INTRODUCE1 cell data for a
2310 (legacy) onion service, correctly detect replays in the RSA-
2311 encrypted part of the cell. We were previously checking for
2312 replays on the entire cell, but those can be circumvented due to
2313 the malleability of Tor's legacy hybrid encryption. This fix helps
2314 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2315 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2318 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2319 - Fix a use-after-free error that could crash v2 Tor onion services
2320 when they failed to open circuits while expiring introduction
2321 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2322 also tracked as TROVE-2017-013 and CVE-2017-8823.
2324 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2325 - When running as a relay, make sure that we never build a path through
2326 ourselves, even in the case where we have somehow lost the version of
2327 our descriptor appearing in the consensus. Fixes part of bug 21534;
2328 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
2331 o Minor features (bridge, backport from 0.3.1.9):
2332 - Bridges now include notice in their descriptors that they are
2333 bridges, and notice of their distribution status, based on their
2334 publication settings. Implements ticket 18329. For more fine-
2335 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2338 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2339 - Add an IPv6 address for the "bastet" directory authority. Closes
2342 o Minor features (geoip):
2343 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2346 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2347 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2348 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2351 Changes in version 0.2.5.16 - 2017-12-01
2352 Tor 0.2.5.13 backports important security and stability bugfixes from
2353 later Tor releases. All Tor users should upgrade to this release, or
2354 to another of the releases coming out today.
2356 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2357 2018. If you need a release with long-term support, please upgrade to
2358 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2360 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2361 - Fix a denial of service bug where an attacker could use a
2362 malformed directory object to cause a Tor instance to pause while
2363 OpenSSL would try to read a passphrase from the terminal. (Tor
2364 instances run without a terminal, which is the case for most Tor
2365 packages, are not impacted.) Fixes bug 24246; bugfix on every
2366 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2367 Found by OSS-Fuzz as testcase 6360145429790720.
2368 - When checking for replays in the INTRODUCE1 cell data for a
2369 (legacy) onion service, correctly detect replays in the RSA-
2370 encrypted part of the cell. We were previously checking for
2371 replays on the entire cell, but those can be circumvented due to
2372 the malleability of Tor's legacy hybrid encryption. This fix helps
2373 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2374 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2377 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2378 - When running as a relay, make sure that we never build a path
2379 through ourselves, even in the case where we have somehow lost the
2380 version of our descriptor appearing in the consensus. Fixes part
2381 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2382 as TROVE-2017-012 and CVE-2017-8822.
2384 o Minor features (bridge, backport from 0.3.1.9):
2385 - Bridges now include notice in their descriptors that they are
2386 bridges, and notice of their distribution status, based on their
2387 publication settings. Implements ticket 18329. For more fine-
2388 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2391 o Minor features (geoip):
2392 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2396 Changes in version 0.2.5.15 - 2017-10-25
2397 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
2398 series. It also adds a new directory authority, Bastet.
2400 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2401 2018. If you need a release with long-term support, please upgrade to
2402 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2404 o Directory authority changes:
2405 - Add "Bastet" as a ninth directory authority to the default list.
2406 Closes ticket 23910.
2407 - The directory authority "Longclaw" has changed its IP address.
2408 Closes ticket 23592.
2410 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2411 - Avoid an assertion failure bug affecting our implementation of
2412 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2413 handling of "0xx" differs from what we had expected. Fixes bug
2414 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2416 o Minor features (geoip):
2417 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2420 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2421 - Fix a memset() off the end of an array when packing cells. This
2422 bug should be harmless in practice, since the corrupted bytes are
2423 still in the same structure, and are always padding bytes,
2424 ignored, or immediately overwritten, depending on compiler
2425 behavior. Nevertheless, because the memset()'s purpose is to make
2426 sure that any other cell-handling bugs can't expose bytes to the
2427 network, we need to fix it. Fixes bug 22737; bugfix on
2428 0.2.4.11-alpha. Fixes CID 1401591.
2430 o Build features (backport from 0.3.1.5-alpha):
2431 - Tor's repository now includes a Travis Continuous Integration (CI)
2432 configuration file (.travis.yml). This is meant to help new
2433 developers and contributors who fork Tor to a Github repository be
2434 better able to test their changes, and understand what we expect
2435 to pass. To use this new build feature, you must fork Tor to your
2436 Github account, then go into the "Integrations" menu in the
2437 repository settings for your fork and enable Travis, then push
2438 your changes. Closes ticket 22636.
2441 Changes in version 0.2.8.16 - 2017-10-25
2442 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
2443 series, including a bugfix for a crash issue that had affected relays
2444 under memory pressure. It also adds a new directory authority, Bastet.
2446 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2447 2018. If you need a release with long-term support, please stick with
2448 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2450 o Directory authority changes:
2451 - Add "Bastet" as a ninth directory authority to the default list.
2452 Closes ticket 23910.
2453 - The directory authority "Longclaw" has changed its IP address.
2454 Closes ticket 23592.
2456 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2457 - Fix a timing-based assertion failure that could occur when the
2458 circuit out-of-memory handler freed a connection's output buffer.
2459 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2461 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2462 - Remove longclaw's IPv6 address, as it will soon change. Authority
2463 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2464 3/8 directory authorities with IPv6 addresses, but there are also
2465 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2467 o Minor features (geoip):
2468 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2472 Changes in version 0.2.9.13 - 2017-10-25
2473 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
2474 series, including a bugfix for a crash issue that had affected relays
2475 under memory pressure. It also adds a new directory authority, Bastet.
2477 o Directory authority changes:
2478 - Add "Bastet" as a ninth directory authority to the default list.
2479 Closes ticket 23910.
2480 - The directory authority "Longclaw" has changed its IP address.
2481 Closes ticket 23592.
2483 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2484 - Fix a timing-based assertion failure that could occur when the
2485 circuit out-of-memory handler freed a connection's output buffer.
2486 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2488 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2489 - Remove longclaw's IPv6 address, as it will soon change. Authority
2490 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2491 3/8 directory authorities with IPv6 addresses, but there are also
2492 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2494 o Minor features (geoip):
2495 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2498 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2499 - When a directory authority rejects a descriptor or extrainfo with
2500 a given digest, mark that digest as undownloadable, so that we do
2501 not attempt to download it again over and over. We previously
2502 tried to avoid downloading such descriptors by other means, but we
2503 didn't notice if we accidentally downloaded one anyway. This
2504 behavior became problematic in 0.2.7.2-alpha, when authorities
2505 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2508 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2509 - Clear the address when node_get_prim_orport() returns early.
2510 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2512 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2513 - When running as a Windows service, set the ID of the main thread
2514 correctly. Failure to do so made us fail to send log messages to
2515 the controller in 0.2.1.16-rc, slowed down controller event
2516 delivery in 0.2.7.3-rc and later, and crash with an assertion
2517 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2518 Patch and diagnosis from "Vort".
2521 Changes in version 0.3.0.12 - 2017-10-25
2522 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
2523 series, including a bugfix for a crash issue that had affected relays
2524 under memory pressure. It also adds a new directory authority, Bastet.
2526 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2527 2018. If you need a release with long-term support, please stick with
2528 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2530 o Directory authority changes:
2531 - Add "Bastet" as a ninth directory authority to the default list.
2532 Closes ticket 23910.
2533 - The directory authority "Longclaw" has changed its IP address.
2534 Closes ticket 23592.
2536 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2537 - Fix a timing-based assertion failure that could occur when the
2538 circuit out-of-memory handler freed a connection's output buffer.
2539 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2541 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2542 - Remove longclaw's IPv6 address, as it will soon change. Authority
2543 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2544 3/8 directory authorities with IPv6 addresses, but there are also
2545 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2547 o Minor features (geoip):
2548 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2551 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2552 - When a directory authority rejects a descriptor or extrainfo with
2553 a given digest, mark that digest as undownloadable, so that we do
2554 not attempt to download it again over and over. We previously
2555 tried to avoid downloading such descriptors by other means, but we
2556 didn't notice if we accidentally downloaded one anyway. This
2557 behavior became problematic in 0.2.7.2-alpha, when authorities
2558 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2561 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2562 - Avoid a possible double close of a circuit by the intro point on
2563 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2564 bugfix on 0.3.0.1-alpha.
2566 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2567 - Clear the address when node_get_prim_orport() returns early.
2568 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2570 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2571 - When running as a Windows service, set the ID of the main thread
2572 correctly. Failure to do so made us fail to send log messages to
2573 the controller in 0.2.1.16-rc, slowed down controller event
2574 delivery in 0.2.7.3-rc and later, and crash with an assertion
2575 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2576 Patch and diagnosis from "Vort".
2579 Changes in version 0.3.1.8 - 2017-10-25
2580 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
2581 It includes several bugfixes, including a bugfix for a crash issue
2582 that had affected relays under memory pressure. It also adds
2583 a new directory authority, Bastet.
2585 o Directory authority changes:
2586 - Add "Bastet" as a ninth directory authority to the default list.
2587 Closes ticket 23910.
2588 - The directory authority "Longclaw" has changed its IP address.
2589 Closes ticket 23592.
2591 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2592 - Fix a timing-based assertion failure that could occur when the
2593 circuit out-of-memory handler freed a connection's output buffer.
2594 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2596 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2597 - Remove longclaw's IPv6 address, as it will soon change. Authority
2598 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2599 3/8 directory authorities with IPv6 addresses, but there are also
2600 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2602 o Minor features (geoip):
2603 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2606 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
2607 - Fix a compilation warning when building with zstd support on
2608 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2609 and fixed by Andreas Stieger.
2611 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
2612 - Handle a pathological case when decompressing Zstandard data when
2613 the output buffer size is zero. Fixes bug 23551; bugfix
2616 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
2617 - Remove the length limit on HTTP status lines that authorities can
2618 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
2620 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2621 - Avoid a possible double close of a circuit by the intro point on
2622 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2623 bugfix on 0.3.0.1-alpha.
2625 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2626 - Clear the address when node_get_prim_orport() returns early.
2627 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2629 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
2630 - Fix additional channelpadding unit test failures by using mocked
2631 time instead of actual time for all tests. Fixes bug 23608; bugfix
2635 Changes in version 0.2.8.15 - 2017-09-18
2636 Tor 0.2.8.15 backports a collection of bugfixes from later
2639 Most significantly, it includes a fix for TROVE-2017-008, a
2640 security bug that affects hidden services running with the
2641 SafeLogging option disabled. For more information, see
2642 https://trac.torproject.org/projects/tor/ticket/23490
2644 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
2645 2018. We suggest that you upgrade to the latest stable release if
2646 possible. If you can't, we recommend that you upgrade at least to
2647 0.2.9, which will be supported until 2020.
2649 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2650 - Avoid an assertion failure bug affecting our implementation of
2651 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2652 handling of "0xx" differs from what we had expected. Fixes bug
2653 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2656 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2659 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2660 - Backport a fix for an "unused variable" warning that appeared
2661 in some versions of mingw. Fixes bug 22838; bugfix on
2664 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2665 - Fix a memset() off the end of an array when packing cells. This
2666 bug should be harmless in practice, since the corrupted bytes are
2667 still in the same structure, and are always padding bytes,
2668 ignored, or immediately overwritten, depending on compiler
2669 behavior. Nevertheless, because the memset()'s purpose is to make
2670 sure that any other cell-handling bugs can't expose bytes to the
2671 network, we need to fix it. Fixes bug 22737; bugfix on
2672 0.2.4.11-alpha. Fixes CID 1401591.
2674 o Build features (backport from 0.3.1.5-alpha):
2675 - Tor's repository now includes a Travis Continuous Integration (CI)
2676 configuration file (.travis.yml). This is meant to help new
2677 developers and contributors who fork Tor to a Github repository be
2678 better able to test their changes, and understand what we expect
2679 to pass. To use this new build feature, you must fork Tor to your
2680 Github account, then go into the "Integrations" menu in the
2681 repository settings for your fork and enable Travis, then push
2682 your changes. Closes ticket 22636.
2685 Changes in version 0.2.9.12 - 2017-09-18
2686 Tor 0.2.9.12 backports a collection of bugfixes from later
2689 Most significantly, it includes a fix for TROVE-2017-008, a
2690 security bug that affects hidden services running with the
2691 SafeLogging option disabled. For more information, see
2692 https://trac.torproject.org/projects/tor/ticket/23490
2694 o Major features (security, backport from 0.3.0.2-alpha):
2695 - Change the algorithm used to decide DNS TTLs on client and server
2696 side, to better resist DNS-based correlation attacks like the
2697 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2698 Feamster. Now relays only return one of two possible DNS TTL
2699 values, and clients are willing to believe DNS TTL values up to 3
2700 hours long. Closes ticket 19769.
2702 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
2703 - Fix a rare crash when sending a begin cell on a circuit whose
2704 linked directory connection had already been closed. Fixes bug
2705 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
2707 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
2708 - Fix a bug that prevented exit nodes from caching DNS records for
2709 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2711 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2712 - Fix a typo that had prevented TPROXY-based transparent proxying
2713 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2714 Patch from "d4fq0fQAgoJ".
2716 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2717 - Avoid an assertion failure bug affecting our implementation of
2718 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2719 handling of "0xx" differs from what we had expected. Fixes bug
2720 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2722 o Minor features (code style, backport from 0.3.1.3-alpha):
2723 - Add "Falls through" comments to our codebase, in order to silence
2724 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2725 Stieger. Closes ticket 22446.
2727 o Minor features (geoip):
2728 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2731 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
2732 - Roll over monthly accounting at the configured hour and minute,
2733 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2734 Found by Andrey Karpov with PVS-Studio.
2736 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
2737 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2738 bugfix on 0.2.8.1-alpha.
2739 - Fix warnings when building with libscrypt and openssl scrypt support
2740 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2741 - When building with certain versions the mingw C header files, avoid
2742 float-conversion warnings when calling the C functions isfinite(),
2743 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
2745 o Minor bugfixes (compilation, backport from 0.3.1.7):
2746 - Avoid compiler warnings in the unit tests for running tor_sscanf()
2747 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2749 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2750 - Backport a fix for an "unused variable" warning that appeared
2751 in some versions of mingw. Fixes bug 22838; bugfix on
2754 o Minor bugfixes (controller, backport from 0.3.1.7):
2755 - Do not crash when receiving a HSPOST command with an empty body.
2756 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2757 - Do not crash when receiving a POSTDESCRIPTOR command with an
2758 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2760 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2761 - Avoid Coverity build warnings related to our BUG() macro. By
2762 default, Coverity treats BUG() as the Linux kernel does: an
2763 instant abort(). We need to override that so our BUG() macro
2764 doesn't prevent Coverity from analyzing functions that use it.
2765 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2767 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2768 - Fix a memset() off the end of an array when packing cells. This
2769 bug should be harmless in practice, since the corrupted bytes are
2770 still in the same structure, and are always padding bytes,
2771 ignored, or immediately overwritten, depending on compiler
2772 behavior. Nevertheless, because the memset()'s purpose is to make
2773 sure that any other cell-handling bugs can't expose bytes to the
2774 network, we need to fix it. Fixes bug 22737; bugfix on
2775 0.2.4.11-alpha. Fixes CID 1401591.
2777 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2778 - When setting the maximum number of connections allowed by the OS,
2779 always allow some extra file descriptors for other files. Fixes
2780 bug 22797; bugfix on 0.2.0.10-alpha.
2782 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2783 - Avoid a sandbox failure when trying to re-bind to a socket and
2784 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2786 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2787 - Permit the fchmod system call, to avoid crashing on startup when
2788 starting with the seccomp2 sandbox and an unexpected set of
2789 permissions on the data directory or its contents. Fixes bug
2790 22516; bugfix on 0.2.5.4-alpha.
2792 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
2793 - Avoid a double-marked-circuit warning that could happen when we
2794 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
2797 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2798 - Reject version numbers with non-numeric prefixes (such as +, -, or
2799 whitespace). Disallowing whitespace prevents differential version
2800 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2801 and part of 21508; bugfix on 0.0.8pre1.
2803 o Build features (backport from 0.3.1.5-alpha):
2804 - Tor's repository now includes a Travis Continuous Integration (CI)
2805 configuration file (.travis.yml). This is meant to help new
2806 developers and contributors who fork Tor to a Github repository be
2807 better able to test their changes, and understand what we expect
2808 to pass. To use this new build feature, you must fork Tor to your
2809 Github account, then go into the "Integrations" menu in the
2810 repository settings for your fork and enable Travis, then push
2811 your changes. Closes ticket 22636.
2814 Changes in version 0.3.0.11 - 2017-09-18
2815 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
2818 Most significantly, it includes a fix for TROVE-2017-008, a
2819 security bug that affects hidden services running with the
2820 SafeLogging option disabled. For more information, see
2821 https://trac.torproject.org/projects/tor/ticket/23490
2823 o Minor features (code style, backport from 0.3.1.7):
2824 - Add "Falls through" comments to our codebase, in order to silence
2825 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2826 Stieger. Closes ticket 22446.
2829 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2832 o Minor bugfixes (compilation, backport from 0.3.1.7):
2833 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2834 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2836 o Minor bugfixes (controller, backport from 0.3.1.7):
2837 - Do not crash when receiving a HSPOST command with an empty body.
2838 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2839 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2840 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2842 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2843 - When setting the maximum number of connections allowed by the OS,
2844 always allow some extra file descriptors for other files. Fixes
2845 bug 22797; bugfix on 0.2.0.10-alpha.
2847 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
2848 - Remove a forgotten debugging message when an introduction point
2849 successfully establishes a hidden service prop224 circuit with
2851 - Change three other log_warn() for an introduction point to
2852 protocol warnings, because they can be failure from the network
2853 and are not relevant to the operator. Fixes bug 23078; bugfix on
2854 0.3.0.1-alpha and 0.3.0.2-alpha.
2857 Changes in version 0.3.1.7 - 2017-09-18
2858 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
2860 With the 0.3.1 series, Tor now serves and downloads directory
2861 information in more compact formats, to save on bandwidth overhead. It
2862 also contains a new padding system to resist netflow-based traffic
2863 analysis, and experimental support for building parts of Tor in Rust
2864 (though no parts of Tor are in Rust yet). There are also numerous
2865 small features, bugfixes on earlier release series, and groundwork for
2866 the hidden services revamp of 0.3.2.
2868 This release also includes a fix for TROVE-2017-008, a security bug
2869 that affects hidden services running with the SafeLogging option
2870 disabled. For more information, see
2871 https://trac.torproject.org/projects/tor/ticket/23490
2873 Per our stable release policy, we plan to support each stable release
2874 series for at least the next nine months, or for three months after
2875 the first stable release of the next series: whichever is longer. If
2876 you need a release with long-term support, we recommend that you stay
2877 with the 0.2.9 series.
2879 Below is a list of the changes since 0.3.0. For a list of all
2880 changes since 0.3.1.6-rc, see the ChangeLog file.
2883 - To build with zstd and lzma support, Tor now requires the
2884 pkg-config tool at build time.
2886 o Major bugfixes (security, hidden services, loggging):
2887 - Fix a bug where we could log uninitialized stack when a certain
2888 hidden service error occurred while SafeLogging was disabled.
2889 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
2890 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
2892 o Major features (build system, continuous integration):
2893 - Tor's repository now includes a Travis Continuous Integration (CI)
2894 configuration file (.travis.yml). This is meant to help new
2895 developers and contributors who fork Tor to a Github repository be
2896 better able to test their changes, and understand what we expect
2897 to pass. To use this new build feature, you must fork Tor to your
2898 Github account, then go into the "Integrations" menu in the
2899 repository settings for your fork and enable Travis, then push
2900 your changes. Closes ticket 22636.
2902 o Major features (directory protocol):
2903 - Tor relays and authorities can now serve clients an abbreviated
2904 version of the consensus document, containing only the changes
2905 since an older consensus document that the client holds. Clients
2906 now request these documents when available. When both client and
2907 server use this new protocol, they will use far less bandwidth (up
2908 to 94% less) to keep the client's consensus up-to-date. Implements
2909 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2910 - Tor can now compress directory traffic with lzma or with zstd
2911 compression algorithms, which can deliver better bandwidth
2912 performance. Because lzma is computationally expensive, it's only
2913 used for documents that can be compressed once and served many
2914 times. Support for these algorithms requires that tor is built
2915 with the libzstd and/or liblzma libraries available. Implements
2916 proposal 278; closes ticket 21662.
2917 - Relays now perform the more expensive compression operations, and
2918 consensus diff generation, in worker threads. This separation
2919 avoids delaying the main thread when a new consensus arrives.
2921 o Major features (experimental):
2922 - Tor can now build modules written in Rust. To turn this on, pass
2923 the "--enable-rust" flag to the configure script. It's not time to
2924 get excited yet: currently, there is no actual Rust functionality
2925 beyond some simple glue code, and a notice at startup to tell you
2926 that Rust is running. Still, we hope that programmers and
2927 packagers will try building Tor with Rust support, so that we can
2928 find issues and solve portability problems. Closes ticket 22106.
2930 o Major features (traffic analysis resistance):
2931 - Connections between clients and relays now send a padding cell in
2932 each direction every 1.5 to 9.5 seconds (tunable via consensus
2933 parameters). This padding will not resist specialized
2934 eavesdroppers, but it should be enough to make many ISPs' routine
2935 network flow logging less useful in traffic analysis against
2938 Padding is negotiated using Tor's link protocol, so both relays
2939 and clients must upgrade for this to take effect. Clients may
2940 still send padding despite the relay's version by setting
2941 ConnectionPadding 1 in torrc, and may disable padding by setting
2942 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2943 users with the torrc option ReducedConnectionPadding. Implements
2944 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2945 - Relays will publish 24 hour totals of padding and non-padding cell
2946 counts to their extra-info descriptors, unless PaddingStatistics 0
2947 is set in torrc. These 24 hour totals are also rounded to
2950 o Major bugfixes (hidden service, relay, security):
2951 - Fix a remotely triggerable assertion failure when a hidden service
2952 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2953 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2954 - Fix a remotely triggerable assertion failure caused by receiving a
2955 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2956 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2959 o Major bugfixes (path selection, security):
2960 - When choosing which guard to use for a circuit, avoid the exit's
2961 family along with the exit itself. Previously, the new guard
2962 selection logic avoided the exit, but did not consider its family.
2963 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2964 006 and CVE-2017-0377.
2966 o Major bugfixes (connection usage):
2967 - We use NETINFO cells to try to determine if both relays involved
2968 in a connection will agree on the canonical status of that
2969 connection. We prefer the connections where this is the case for
2970 extend cells, and try to close connections where relays disagree
2971 on their canonical status early. Also, we now prefer the oldest
2972 valid connection for extend cells. These two changes should reduce
2973 the number of long-term connections that are kept open between
2974 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2975 - Relays now log hourly statistics (look for
2976 "channel_check_for_duplicates" lines) on the total number of
2977 connections to other relays. If the number of connections per
2978 relay is unexpectedly large, this log message is at notice level.
2979 Otherwise it is at info.
2981 o Major bugfixes (entry guards):
2982 - When starting with an old consensus, do not add new entry guards
2983 unless the consensus is "reasonably live" (under 1 day old). Fixes
2984 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2985 - Don't block bootstrapping when a primary bridge is offline and we
2986 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2987 21969; bugfix on 0.3.0.3-alpha.
2989 o Major bugfixes (linux TPROXY support):
2990 - Fix a typo that had prevented TPROXY-based transparent proxying
2991 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2992 Patch from "d4fq0fQAgoJ".
2994 o Major bugfixes (openbsd, denial-of-service):
2995 - Avoid an assertion failure bug affecting our implementation of
2996 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2997 handling of "0xx" differs from what we had expected. Fixes bug
2998 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3000 o Major bugfixes (relay, link handshake):
3001 - When performing the v3 link handshake on a TLS connection, report
3002 that we have the x509 certificate that we actually used on that
3003 connection, even if we have changed certificates since that
3004 connection was first opened. Previously, we would claim to have
3005 used our most recent x509 link certificate, which would sometimes
3006 make the link handshake fail. Fixes one case of bug 22460; bugfix
3009 o Major bugfixes (relays, key management):
3010 - Regenerate link and authentication certificates whenever the key
3011 that signs them changes; also, regenerate link certificates
3012 whenever the signed key changes. Previously, these processes were
3013 only weakly coupled, and we relays could (for minutes to hours)
3014 wind up with an inconsistent set of keys and certificates, which
3015 other relays would not accept. Fixes two cases of bug 22460;
3016 bugfix on 0.3.0.1-alpha.
3017 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3018 send the certificate that matches the x509 certificate that we
3019 used on the TLS connection. Previously, there was a race condition
3020 if the TLS context rotated after we began the TLS handshake but
3021 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3024 o Minor features (security, windows):
3025 - Enable a couple of pieces of Windows hardening: one
3026 (HeapEnableTerminationOnCorruption) that has been on-by-default
3027 since Windows 8, and unavailable before Windows 7; and one
3028 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3029 affect us, but shouldn't do any harm. Closes ticket 21953.
3031 o Minor features (bridge authority):
3032 - Add "fingerprint" lines to the networkstatus-bridges file produced
3033 by bridge authorities. Closes ticket 22207.
3035 o Minor features (code style):
3036 - Add "Falls through" comments to our codebase, in order to silence
3037 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3038 Stieger. Closes ticket 22446.
3040 o Minor features (config options):
3041 - Allow "%include" directives in torrc configuration files. These
3042 directives import the settings from other files, or from all the
3043 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
3044 - Make SAVECONF return an error when overwriting a torrc that has
3045 includes. Using SAVECONF with the FORCE option will allow it to
3046 overwrite torrc even if includes are used. Related to ticket 1922.
3047 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
3048 will work without the FORCE option. Related to ticket 1922.
3050 o Minor features (controller):
3051 - Warn the first time that a controller requests data in the long-
3052 deprecated 'GETINFO network-status' format. Closes ticket 21703.
3054 o Minor features (defaults):
3055 - The default value for UseCreateFast is now 0: clients which
3056 haven't yet received a consensus document will now use a proper
3057 ntor handshake to talk to their directory servers whenever they
3058 can. Closes ticket 21407.
3059 - Onion key rotation and expiry intervals are now defined as a
3060 network consensus parameter, per proposal 274. The default
3061 lifetime of an onion key is increased from 7 to 28 days. Old onion
3062 keys will expire after 7 days by default. This change will make
3063 consensus diffs much smaller, and save significant bandwidth.
3064 Closes ticket 21641.
3066 o Minor features (defensive programming):
3067 - Create a pair of consensus parameters, nf_pad_tor2web and
3068 nf_pad_single_onion, to disable netflow padding in the consensus
3069 for non-anonymous connections in case the overhead is high. Closes
3072 o Minor features (diagnostic):
3073 - Add a stack trace to the bug warnings that can be logged when
3074 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
3075 attempt for bug 23105.
3076 - Add logging messages to try to diagnose a rare bug that seems to
3077 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
3078 think this is happening because of incorrect system clocks, but
3079 we'd like to know for certain. Diagnostic for bug 22466.
3080 - Avoid an assertion failure, and log a better error message, when
3081 unable to remove a file from the consensus cache on Windows.
3082 Attempts to mitigate and diagnose bug 22752.
3084 o Minor features (directory authority):
3085 - Improve the message that authorities report to relays that present
3086 RSA/Ed25519 keypairs that conflict with previously pinned keys.
3087 Closes ticket 22348.
3089 o Minor features (directory cache, consensus diff):
3090 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
3091 operators with low-resource environments to adjust the number of
3092 consensuses they'll store and generate diffs from. Most cache
3093 operators should leave it unchanged. Helps to work around
3096 o Minor features (fallback directory list):
3097 - Update the fallback directory mirror whitelist and blacklist based
3098 on operator emails. Closes task 21121.
3099 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3100 December 2016 (of which ~126 were still functional) with a list of
3101 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3102 2017. Resolves ticket 21564.
3104 o Minor features (geoip):
3105 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3108 o Minor features (hidden services, logging):
3109 - Log a message when a hidden service descriptor has fewer
3110 introduction points than specified in
3111 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
3112 - Log a message when a hidden service reaches its introduction point
3113 circuit limit, and when that limit is reset. Follow up to ticket
3114 21594; closes ticket 21622.
3115 - Warn user if multiple entries in EntryNodes and at least one
3116 HiddenService are used together. Pinning EntryNodes along with a
3117 hidden service can be possibly harmful; for instance see ticket
3118 14917 or 21155. Closes ticket 21155.
3120 o Minor features (linux seccomp2 sandbox):
3121 - We now have a document storage backend compatible with the Linux
3122 seccomp2 sandbox. This backend is used for consensus documents and
3123 diffs between them; in the long term, we'd like to use it for
3124 unparseable directory material too. Closes ticket 21645
3125 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
3126 from 1MB to 16MB. This was necessary with the glibc allocator in
3127 order to allow worker threads to allocate more memory -- which in
3128 turn is necessary because of our new use of worker threads for
3129 compression. Closes ticket 22096.
3131 o Minor features (logging):
3132 - Log files are no longer created world-readable by default.
3133 (Previously, most distributors would store the logs in a non-
3134 world-readable location to prevent inappropriate access. This
3135 change is an extra precaution.) Closes ticket 21729; patch
3138 o Minor features (performance):
3139 - Our Keccak (SHA-3) implementation now accesses memory more
3140 efficiently, especially on little-endian systems. Closes
3142 - Add an O(1) implementation of channel_find_by_global_id(), to
3143 speed some controller functions.
3145 o Minor features (relay, configuration):
3146 - The MyFamily option may now be repeated as many times as desired,
3147 for relays that want to configure large families. Closes ticket
3148 4998; patch by Daniel Pinto.
3150 o Minor features (relay, performance):
3151 - Always start relays with at least two worker threads, to prevent
3152 priority inversion on slow tasks. Part of the fix for bug 22883.
3153 - Allow background work to be queued with different priorities, so
3154 that a big pile of slow low-priority jobs will not starve out
3155 higher priority jobs. This lays the groundwork for a fix for
3158 o Minor features (safety):
3159 - Add an explicit check to extrainfo_parse_entry_from_string() for
3160 NULL inputs. We don't believe this can actually happen, but it may
3161 help silence a warning from the Clang analyzer. Closes
3164 o Minor features (testing):
3165 - Add more tests for compression backend initialization. Closes
3167 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
3168 When Tor is compiled with this option, we disable a number of
3169 redundant memory-safety failsafes that are intended to stop bugs
3170 from becoming security issues. This makes it easier to hunt for
3171 bugs that would be security issues without the failsafes turned
3172 on. Closes ticket 21439.
3173 - Add a general event-tracing instrumentation support to Tor. This
3174 subsystem will enable developers and researchers to add fine-
3175 grained instrumentation to their Tor instances, for use when
3176 examining Tor network performance issues. There are no trace
3177 events yet, and event-tracing is off by default unless enabled at
3178 compile time. Implements ticket 13802.
3179 - Improve our version parsing tests: add tests for typical version
3180 components, add tests for invalid versions, including numeric
3181 range and non-numeric prefixes. Unit tests 21278, 21450, and
3182 21507. Partially implements 21470.
3184 o Minor bugfixes (bandwidth accounting):
3185 - Roll over monthly accounting at the configured hour and minute,
3186 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3187 Found by Andrey Karpov with PVS-Studio.
3189 o Minor bugfixes (code correctness):
3190 - Accurately identify client connections by their lack of peer
3191 authentication. This means that we bail out earlier if asked to
3192 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
3195 o Minor bugfixes (compilation warnings):
3196 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
3197 22915; bugfix on 0.2.8.1-alpha.
3198 - Fix warnings when building with libscrypt and openssl scrypt
3199 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3200 - When building with certain versions of the mingw C header files,
3201 avoid float-conversion warnings when calling the C functions
3202 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3205 o Minor bugfixes (compilation):
3206 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3207 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3209 o Minor bugfixes (compression):
3210 - When spooling compressed data to an output buffer, don't try to
3211 spool more data when there is no more data to spool and we are not
3212 trying to flush the input. Previously, we would sometimes launch
3213 compression requests with nothing to do, which interferes with our
3214 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
3216 o Minor bugfixes (configuration):
3217 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3218 bug 22252; bugfix on 0.2.9.3-alpha.
3220 o Minor bugfixes (connection lifespan):
3221 - Allow more control over how long TLS connections are kept open:
3222 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
3223 single option called CircuitsAvailableTimeout. Also, allow the
3224 consensus to control the default values for both this preference
3225 and the lifespan of relay-to-relay connections. Fixes bug 17592;
3226 bugfix on 0.2.5.5-alpha.
3227 - Increase the initial circuit build timeout testing frequency, to
3228 help ensure that ReducedConnectionPadding clients finish learning
3229 a timeout before their orconn would expire. The initial testing
3230 rate was set back in the days of TAP and before the Tor Browser
3231 updater, when we had to be much more careful about new clients
3232 making lots of circuits. With this change, a circuit build timeout
3233 is learned in about 15-20 minutes, instead of 100-120 minutes.
3235 o Minor bugfixes (controller):
3236 - Do not crash when receiving a HSPOST command with an empty body.
3237 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3238 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3239 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3240 - GETINFO onions/current and onions/detached no longer respond with
3241 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
3242 - Trigger HS descriptor events on the control port when the client
3243 fails to pick a hidden service directory for a hidden service.
3244 This can happen if all the hidden service directories are in
3245 ExcludeNodes, or they have all been queried within the last 15
3246 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
3248 o Minor bugfixes (correctness):
3249 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3250 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3252 o Minor bugfixes (coverity build support):
3253 - Avoid Coverity build warnings related to our BUG() macro. By
3254 default, Coverity treats BUG() as the Linux kernel does: an
3255 instant abort(). We need to override that so our BUG() macro
3256 doesn't prevent Coverity from analyzing functions that use it.
3257 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3259 o Minor bugfixes (defensive programming):
3260 - Detect and break out of infinite loops in our compression code. We
3261 don't think that any such loops exist now, but it's best to be
3262 safe. Closes ticket 22672.
3263 - Fix a memset() off the end of an array when packing cells. This
3264 bug should be harmless in practice, since the corrupted bytes are
3265 still in the same structure, and are always padding bytes,
3266 ignored, or immediately overwritten, depending on compiler
3267 behavior. Nevertheless, because the memset()'s purpose is to make
3268 sure that any other cell-handling bugs can't expose bytes to the
3269 network, we need to fix it. Fixes bug 22737; bugfix on
3270 0.2.4.11-alpha. Fixes CID 1401591.
3272 o Minor bugfixes (directory authority):
3273 - When a directory authority rejects a descriptor or extrainfo with
3274 a given digest, mark that digest as undownloadable, so that we do
3275 not attempt to download it again over and over. We previously
3276 tried to avoid downloading such descriptors by other means, but we
3277 didn't notice if we accidentally downloaded one anyway. This
3278 behavior became problematic in 0.2.7.2-alpha, when authorities
3279 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3281 - When rejecting a router descriptor for running an obsolete version
3282 of Tor without ntor support, warn about the obsolete tor version,
3283 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3284 - Prevent the shared randomness subsystem from asserting when
3285 initialized by a bridge authority with an incomplete configuration
3286 file. Fixes bug 21586; bugfix on 0.2.9.8.
3288 o Minor bugfixes (error reporting, windows):
3289 - When formatting Windows error messages, use the English format to
3290 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
3293 o Minor bugfixes (exit-side DNS):
3294 - Fix an untriggerable assertion that checked the output of a
3295 libevent DNS error, so that the assertion actually behaves as
3296 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
3297 Karpov using PVS-Studio.
3299 o Minor bugfixes (fallback directories):
3300 - Make the usage example in updateFallbackDirs.py actually work, and
3301 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
3302 - Decrease the guard flag average required to be a fallback. This
3303 allows us to keep relays that have their guard flag removed when
3304 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3305 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
3306 bugfix on 0.2.8.1-alpha.
3307 - Make sure fallback directory mirrors have the same address, port,
3308 and relay identity key for at least 30 days before they are
3309 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3311 o Minor bugfixes (file limits, osx):
3312 - When setting the maximum number of connections allowed by the OS,
3313 always allow some extra file descriptors for other files. Fixes
3314 bug 22797; bugfix on 0.2.0.10-alpha.
3316 o Minor bugfixes (hidden services):
3317 - Increase the number of circuits that a service is allowed to
3318 open over a specific period of time. The value was lower than it
3319 should be (8 vs 12) in the normal case of 3 introduction points.
3320 Fixes bug 22159; bugfix on 0.3.0.5-rc.
3321 - Fix a BUG warning during HSv3 descriptor decoding that could be
3322 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
3323 on 0.3.0.1-alpha. Bug found by "haxxpop".
3324 - Stop printing a cryptic warning when a hidden service gets a
3325 request to connect to a virtual port that it hasn't configured.
3326 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
3327 - Simplify hidden service descriptor creation by using an existing
3328 flag to check if an introduction point is established. Fixes bug
3329 21599; bugfix on 0.2.7.2-alpha.
3331 o Minor bugfixes (link handshake):
3332 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3333 months, and regenerate it when it is within one month of expiring.
3334 Previously, we had generated this certificate at startup with a
3335 ten-year lifetime, but that could lead to weird behavior when Tor
3336 was started with a grossly inaccurate clock. Mitigates bug 22466;
3337 mitigation on 0.3.0.1-alpha.
3339 o Minor bugfixes (linux seccomp2 sandbox):
3340 - Avoid a sandbox failure when trying to re-bind to a socket and
3341 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3342 - Permit the fchmod system call, to avoid crashing on startup when
3343 starting with the seccomp2 sandbox and an unexpected set of
3344 permissions on the data directory or its contents. Fixes bug
3345 22516; bugfix on 0.2.5.4-alpha.
3347 o Minor bugfixes (logging):
3348 - When decompressing, do not warn if we fail to decompress using a
3349 compression method that we merely guessed. Fixes part of bug
3350 22670; bugfix on 0.1.1.14-alpha.
3351 - When decompressing, treat mismatch between content-encoding and
3352 actual compression type as a protocol warning. Fixes part of bug
3353 22670; bugfix on 0.1.1.9-alpha.
3354 - Downgrade "assigned_to_cpuworker failed" message to info-level
3355 severity. In every case that can reach it, either a better warning
3356 has already been logged, or no warning is warranted. Fixes bug
3357 22356; bugfix on 0.2.6.3-alpha.
3358 - Log a better message when a directory authority replies to an
3359 upload with an unexpected status code. Fixes bug 11121; bugfix
3361 - Downgrade a log statement about unexpected relay cells from "bug"
3362 to "protocol warning", because there is at least one use case
3363 where it can be triggered by a buggy tor implementation. Fixes bug
3364 21293; bugfix on 0.1.1.14-alpha.
3366 o Minor bugfixes (logging, relay):
3367 - Remove a forgotten debugging message when an introduction point
3368 successfully establishes a hidden service prop224 circuit with
3370 - Change three other log_warn() for an introduction point to
3371 protocol warnings, because they can be failure from the network
3372 and are not relevant to the operator. Fixes bug 23078; bugfix on
3373 0.3.0.1-alpha and 0.3.0.2-alpha.
3375 o Minor bugfixes (relay):
3376 - Inform the geoip and rephist modules about all requests, even on
3377 relays that are only fetching microdescriptors. Fixes a bug
3378 related to 21585; bugfix on 0.3.0.1-alpha.
3380 o Minor bugfixes (memory leaks):
3381 - Fix a small memory leak at exit from the backtrace handler code.
3382 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
3383 - When directory authorities reject a router descriptor due to
3384 keypinning, free the router descriptor rather than leaking the
3385 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3386 - Fix a small memory leak when validating a configuration that uses
3387 two or more AF_UNIX sockets for the same port type. Fixes bug
3388 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
3390 o Minor bugfixes (process behavior):
3391 - When exiting because of an error, always exit with a nonzero exit
3392 status. Previously, we would fail to report an error in our exit
3393 status in cases related to __OwningControllerProcess failure,
3394 lockfile contention, and Ed25519 key initialization. Fixes bug
3395 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
3396 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
3399 o Minor bugfixes (robustness, error handling):
3400 - Improve our handling of the cases where OpenSSL encounters a
3401 memory error while encoding keys and certificates. We haven't
3402 observed these errors in the wild, but if they do happen, we now
3403 detect and respond better. Fixes bug 19418; bugfix on all versions
3404 of Tor. Reported by Guido Vranken.
3406 o Minor bugfixes (testing):
3407 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3408 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3409 - Use unbuffered I/O for utility functions around the
3410 process_handle_t type. This fixes unit test failures reported on
3411 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
3412 - Make display of captured unit test log messages consistent. Fixes
3413 bug 21510; bugfix on 0.2.9.3-alpha.
3414 - Make test-network.sh always call chutney's test-network.sh.
3415 Previously, this only worked on systems which had bash installed,
3416 due to some bash-specific code in the script. Fixes bug 19699;
3417 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
3418 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3419 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3420 - The unit tests now pass on systems where localhost is misconfigured
3421 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
3424 o Minor bugfixes (voting consistency):
3425 - Reject version numbers with non-numeric prefixes (such as +, -, or
3426 whitespace). Disallowing whitespace prevents differential version
3427 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3428 and part of 21508; bugfix on 0.0.8pre1.
3430 o Minor bugfixes (Windows service):
3431 - When running as a Windows service, set the ID of the main thread
3432 correctly. Failure to do so made us fail to send log messages to
3433 the controller in 0.2.1.16-rc, slowed down controller event
3434 delivery in 0.2.7.3-rc and later, and crash with an assertion
3435 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3436 Patch and diagnosis from "Vort".
3438 o Minor bugfixes (windows, relay):
3439 - Resolve "Failure from drain_fd: No error" warnings on Windows
3440 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
3442 o Code simplification and refactoring:
3443 - Break up the 630-line function connection_dir_client_reached_eof()
3444 into a dozen smaller functions. This change should help
3445 maintainability and readability of the client directory code.
3446 - Isolate our use of the openssl headers so that they are only
3447 included from our crypto wrapper modules, and from tests that
3448 examine those modules' internals. Closes ticket 21841.
3449 - Simplify our API to launch directory requests, making it more
3450 extensible and less error-prone. Now it's easier to add extra
3451 headers to directory requests. Closes ticket 21646.
3452 - Our base64 decoding functions no longer overestimate the output
3453 space that they need when parsing unpadded inputs. Closes
3455 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
3456 Resolves ticket 22213.
3457 - The logic that directory caches use to spool request to clients,
3458 serving them one part at a time so as not to allocate too much
3459 memory, has been refactored for consistency. Previously there was
3460 a separate spooling implementation per type of spoolable data. Now
3461 there is one common spooling implementation, with extensible data
3462 types. Closes ticket 21651.
3463 - Tor's compression module now supports multiple backends. Part of
3464 the implementation for proposal 278; closes ticket 21663.
3467 - Add a manpage description for the key-pinning-journal file. Closes
3469 - Correctly note that bandwidth accounting values are stored in the
3470 state file, and the bw_accounting file is now obsolete. Closes
3472 - Document more of the files in the Tor data directory, including
3473 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
3474 approved-routers, sr-random, and diff-cache. Found while fixing
3476 - Clarify the manpage for the (deprecated) torify script. Closes
3478 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
3479 Closes ticket 21873.
3480 - Correct documentation about the default DataDirectory value.
3481 Closes ticket 21151.
3482 - Document the default behavior of NumEntryGuards and
3483 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
3485 - Document key=value pluggable transport arguments for Bridge lines
3486 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
3487 - Note that bandwidth-limiting options don't affect TCP headers or
3488 DNS. Closes ticket 17170.
3490 o Removed features (configuration options, all in ticket 22060):
3491 - These configuration options are now marked Obsolete, and no longer
3492 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3493 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3494 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3495 in 0.2.9.2-alpha and have now been removed. The previous default
3496 behavior is now always chosen; the previous (less secure) non-
3497 default behavior is now unavailable.
3498 - CloseHSClientCircuitsImmediatelyOnTimeout and
3499 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3500 0.2.9.2-alpha and now have been removed. HS circuits never close
3501 on circuit build timeout; they have a longer timeout period.
3502 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3503 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3504 (and others) to configure listen-only and advertise-only addresses.
3506 o Removed features (tools):
3507 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3508 used it to help people detect RSA keys that were generated by
3509 versions of Debian affected by CVE-2008-0166. But those keys have
3510 been out of circulation for ages, and this tool is no longer
3511 required. Closes ticket 21842.
3514 Changes in version 0.3.0.10 - 2017-08-02
3515 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
3516 from the current Tor alpha series. OpenBSD users and TPROXY users
3517 should upgrade; others are probably okay sticking with 0.3.0.9.
3519 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
3520 - Tor's repository now includes a Travis Continuous Integration (CI)
3521 configuration file (.travis.yml). This is meant to help new
3522 developers and contributors who fork Tor to a Github repository be
3523 better able to test their changes, and understand what we expect
3524 to pass. To use this new build feature, you must fork Tor to your
3525 Github account, then go into the "Integrations" menu in the
3526 repository settings for your fork and enable Travis, then push
3527 your changes. Closes ticket 22636.
3529 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3530 - Fix a typo that had prevented TPROXY-based transparent proxying
3531 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3532 Patch from "d4fq0fQAgoJ".
3534 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3535 - Avoid an assertion failure bug affecting our implementation of
3536 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3537 handling of "0xbar" differs from what we had expected. Fixes bug
3538 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3540 o Minor features (backport from 0.3.1.5-alpha):
3541 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
3544 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
3545 - Roll over monthly accounting at the configured hour and minute,
3546 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3547 Found by Andrey Karpov with PVS-Studio.
3549 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
3550 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3551 bugfix on 0.2.8.1-alpha.
3552 - Fix warnings when building with libscrypt and openssl scrypt
3553 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3554 - When building with certain versions of the mingw C header files,
3555 avoid float-conversion warnings when calling the C functions
3556 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3559 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3560 - Backport a fix for an "unused variable" warning that appeared
3561 in some versions of mingw. Fixes bug 22838; bugfix on
3564 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3565 - Avoid Coverity build warnings related to our BUG() macro. By
3566 default, Coverity treats BUG() as the Linux kernel does: an
3567 instant abort(). We need to override that so our BUG() macro
3568 doesn't prevent Coverity from analyzing functions that use it.
3569 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3571 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
3572 - When rejecting a router descriptor for running an obsolete version
3573 of Tor without ntor support, warn about the obsolete tor version,
3574 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3576 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3577 - Avoid a sandbox failure when trying to re-bind to a socket and
3578 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3580 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
3581 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3582 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3585 Changes in version 0.3.0.9 - 2017-06-29
3586 Tor 0.3.0.9 fixes a path selection bug that would allow a client
3587 to use a guard that was in the same network family as a chosen exit
3588 relay. This is a security regression; all clients running earlier
3589 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
3592 This release also backports several other bugfixes from the 0.3.1.x
3595 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
3596 - When choosing which guard to use for a circuit, avoid the exit's
3597 family along with the exit itself. Previously, the new guard
3598 selection logic avoided the exit, but did not consider its family.
3599 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3600 006 and CVE-2017-0377.
3602 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
3603 - Don't block bootstrapping when a primary bridge is offline and we
3604 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3605 21969; bugfix on 0.3.0.3-alpha.
3607 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
3608 - When starting with an old consensus, do not add new entry guards
3609 unless the consensus is "reasonably live" (under 1 day old). Fixes
3610 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3612 o Minor features (geoip):
3613 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3616 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3617 - Reject version numbers with non-numeric prefixes (such as +, -, or
3618 whitespace). Disallowing whitespace prevents differential version
3619 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3620 and part of 21508; bugfix on 0.0.8pre1.
3622 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3623 - Permit the fchmod system call, to avoid crashing on startup when
3624 starting with the seccomp2 sandbox and an unexpected set of
3625 permissions on the data directory or its contents. Fixes bug
3626 22516; bugfix on 0.2.5.4-alpha.
3628 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
3629 - Fix a memset() off the end of an array when packing cells. This
3630 bug should be harmless in practice, since the corrupted bytes are
3631 still in the same structure, and are always padding bytes,
3632 ignored, or immediately overwritten, depending on compiler
3633 behavior. Nevertheless, because the memset()'s purpose is to make
3634 sure that any other cell-handling bugs can't expose bytes to the
3635 network, we need to fix it. Fixes bug 22737; bugfix on
3636 0.2.4.11-alpha. Fixes CID 1401591.
3639 Changes in version 0.3.0.8 - 2017-06-08
3640 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
3641 remotely crash a hidden service with an assertion failure. Anyone
3642 running a hidden service should upgrade to this version, or to some
3643 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3645 Tor 0.3.0.8 also includes fixes for several key management bugs
3646 that sometimes made relays unreliable, as well as several other
3647 bugfixes described below.
3649 o Major bugfixes (hidden service, relay, security, backport
3650 from 0.3.1.3-alpha):
3651 - Fix a remotely triggerable assertion failure when a hidden service
3652 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3653 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3654 - Fix a remotely triggerable assertion failure caused by receiving a
3655 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3656 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3659 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3660 - When performing the v3 link handshake on a TLS connection, report
3661 that we have the x509 certificate that we actually used on that
3662 connection, even if we have changed certificates since that
3663 connection was first opened. Previously, we would claim to have
3664 used our most recent x509 link certificate, which would sometimes
3665 make the link handshake fail. Fixes one case of bug 22460; bugfix
3668 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
3669 - Regenerate link and authentication certificates whenever the key
3670 that signs them changes; also, regenerate link certificates
3671 whenever the signed key changes. Previously, these processes were
3672 only weakly coupled, and we relays could (for minutes to hours)
3673 wind up with an inconsistent set of keys and certificates, which
3674 other relays would not accept. Fixes two cases of bug 22460;
3675 bugfix on 0.3.0.1-alpha.
3676 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3677 send the certificate that matches the x509 certificate that we
3678 used on the TLS connection. Previously, there was a race condition
3679 if the TLS context rotated after we began the TLS handshake but
3680 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3683 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
3684 - Stop rejecting v3 hidden service descriptors because their size
3685 did not match an old padding rule. Fixes bug 22447; bugfix on
3688 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3689 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3690 December 2016 (of which ~126 were still functional) with a list of
3691 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3692 2017. Resolves ticket 21564.
3694 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
3695 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3696 bug 22252; bugfix on 0.2.9.3-alpha.
3698 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3699 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3700 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3702 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
3703 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3704 months, and regenerate it when it is within one month of expiring.
3705 Previously, we had generated this certificate at startup with a
3706 ten-year lifetime, but that could lead to weird behavior when Tor
3707 was started with a grossly inaccurate clock. Mitigates bug 22466;
3708 mitigation on 0.3.0.1-alpha.
3710 o Minor bugfixes (memory leak, directory authority, backport from
3712 - When directory authorities reject a router descriptor due to
3713 keypinning, free the router descriptor rather than leaking the
3714 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3717 Changes in version 0.2.9.11 - 2017-06-08
3718 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
3719 remotely crash a hidden service with an assertion failure. Anyone
3720 running a hidden service should upgrade to this version, or to some
3721 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3722 are not affected by TROVE-2017-004.)
3724 Tor 0.2.9.11 also backports fixes for several key management bugs
3725 that sometimes made relays unreliable, as well as several other
3726 bugfixes described below.
3728 o Major bugfixes (hidden service, relay, security, backport
3729 from 0.3.1.3-alpha):
3730 - Fix a remotely triggerable assertion failure caused by receiving a
3731 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3732 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3735 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3736 - When performing the v3 link handshake on a TLS connection, report
3737 that we have the x509 certificate that we actually used on that
3738 connection, even if we have changed certificates since that
3739 connection was first opened. Previously, we would claim to have
3740 used our most recent x509 link certificate, which would sometimes
3741 make the link handshake fail. Fixes one case of bug 22460; bugfix
3744 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3745 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3746 December 2016 (of which ~126 were still functional) with a list of
3747 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3748 2017. Resolves ticket 21564.
3750 o Minor features (future-proofing, backport from 0.3.0.7):
3751 - Tor no longer refuses to download microdescriptors or descriptors if
3752 they are listed as "published in the future". This change will
3753 eventually allow us to stop listing meaningful "published" dates
3754 in microdescriptor consensuses, and thereby allow us to reduce the
3755 resources required to download consensus diffs by over 50%.
3756 Implements part of ticket 21642; implements part of proposal 275.
3758 o Minor features (directory authorities, backport from 0.3.0.4-rc)
3759 - Directory authorities now reject relays running versions
3760 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3761 suffer from bug 20499 and don't keep their consensus cache
3762 up-to-date. Resolves ticket 20509.
3764 o Minor features (geoip):
3765 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3768 o Minor bugfixes (control port, backport from 0.3.0.6):
3769 - The GETINFO extra-info/digest/<digest> command was broken because
3770 of a wrong base16 decode return value check, introduced when
3771 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3773 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3774 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3775 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3777 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
3778 - The getpid() system call is now permitted under the Linux seccomp2
3779 sandbox, to avoid crashing with versions of OpenSSL (and other
3780 libraries) that attempt to learn the process's PID by using the
3781 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3784 o Minor bugfixes (memory leak, directory authority, backport
3785 from 0.3.1.2-alpha):
3786 - When directory authorities reject a router descriptor due to
3787 keypinning, free the router descriptor rather than leaking the
3788 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3790 Changes in version 0.2.8.14 - 2017-06-08
3791 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3792 remotely crash a hidden service with an assertion failure. Anyone
3793 running a hidden service should upgrade to this version, or to some
3794 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3795 are not affected by TROVE-2017-004.)
3797 o Major bugfixes (hidden service, relay, security):
3798 - Fix a remotely triggerable assertion failure caused by receiving a
3799 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3800 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3803 o Minor features (geoip):
3804 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3807 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3808 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3809 December 2016 (of which ~126 were still functional) with a list of
3810 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3811 2017. Resolves ticket 21564.
3813 o Minor bugfixes (correctness):
3814 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3815 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3817 Changes in version 0.2.7.8 - 2017-06-08
3818 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3819 remotely crash a hidden service with an assertion failure. Anyone
3820 running a hidden service should upgrade to this version, or to some
3821 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3822 are not affected by TROVE-2017-004.)
3824 o Major bugfixes (hidden service, relay, security):
3825 - Fix a remotely triggerable assertion failure caused by receiving a
3826 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3827 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3830 o Minor features (geoip):
3831 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3834 o Minor bugfixes (correctness):
3835 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3836 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3839 Changes in version 0.2.6.12 - 2017-06-08
3840 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
3841 remotely crash a hidden service with an assertion failure. Anyone
3842 running a hidden service should upgrade to this version, or to some
3843 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3844 are not affected by TROVE-2017-004.)
3846 o Major bugfixes (hidden service, relay, security):
3847 - Fix a remotely triggerable assertion failure caused by receiving a
3848 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3849 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3852 o Minor features (geoip):
3853 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3856 o Minor bugfixes (correctness):
3857 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3858 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3860 Changes in version 0.2.5.14 - 2017-06-08
3861 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
3862 remotely crash a hidden service with an assertion failure. Anyone
3863 running a hidden service should upgrade to this version, or to some
3864 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3865 are not affected by TROVE-2017-004.)
3867 o Major bugfixes (hidden service, relay, security):
3868 - Fix a remotely triggerable assertion failure caused by receiving a
3869 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3870 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3873 o Minor features (geoip):
3874 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3877 o Minor bugfixes (correctness):
3878 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3879 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3881 Changes in version 0.2.4.29 - 2017-06-08
3882 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
3883 remotely crash a hidden service with an assertion failure. Anyone
3884 running a hidden service should upgrade to this version, or to some
3885 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3886 are not affected by TROVE-2017-004.)
3888 o Major bugfixes (hidden service, relay, security):
3889 - Fix a remotely triggerable assertion failure caused by receiving a
3890 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3891 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3894 o Minor features (geoip):
3895 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3898 o Minor bugfixes (correctness):
3899 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3900 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3903 Changes in version 0.3.0.7 - 2017-05-15
3904 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3905 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3906 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3907 clients are not affected.
3909 o Major bugfixes (hidden service directory, security):
3910 - Fix an assertion failure in the hidden service directory code, which
3911 could be used by an attacker to remotely cause a Tor relay process to
3912 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3913 should upgrade. This security issue is tracked as TROVE-2017-002.
3914 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3917 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3920 o Minor features (future-proofing):
3921 - Tor no longer refuses to download microdescriptors or descriptors
3922 if they are listed as "published in the future". This change will
3923 eventually allow us to stop listing meaningful "published" dates
3924 in microdescriptor consensuses, and thereby allow us to reduce the
3925 resources required to download consensus diffs by over 50%.
3926 Implements part of ticket 21642; implements part of proposal 275.
3928 o Minor bugfixes (Linux seccomp2 sandbox):
3929 - The getpid() system call is now permitted under the Linux seccomp2
3930 sandbox, to avoid crashing with versions of OpenSSL (and other
3931 libraries) that attempt to learn the process's PID by using the
3932 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3936 Changes in version 0.3.0.6 - 2017-04-26
3937 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3939 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3940 authenticate their link connections to relays, rather than the old
3941 RSA1024 keys that they used before. (Circuit crypto has been
3942 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3943 the guard selection and replacement algorithm to behave more robustly
3944 in the presence of unreliable networks, and to resist guard-
3947 This series also includes numerous other small features and bugfixes,
3948 along with more groundwork for the upcoming hidden-services revamp.
3950 Per our stable release policy, we plan to support the Tor 0.3.0
3951 release series for at least the next nine months, or for three months
3952 after the first stable release of the 0.3.1 series: whichever is
3953 longer. If you need a release with long-term support, we recommend
3954 that you stay with the 0.2.9 series.
3956 Below are the changes since 0.2.9.10. For a list of only the changes
3957 since 0.3.0.5-rc, see the ChangeLog file.
3959 o Major features (directory authority, security):
3960 - The default for AuthDirPinKeys is now 1: directory authorities
3961 will reject relays where the RSA identity key matches a previously
3962 seen value, but the Ed25519 key has changed. Closes ticket 18319.
3964 o Major features (guard selection algorithm):
3965 - Tor's guard selection algorithm has been redesigned from the
3966 ground up, to better support unreliable networks and restrictive
3967 sets of entry nodes, and to better resist guard-capture attacks by
3968 hostile local networks. Implements proposal 271; closes
3971 o Major features (next-generation hidden services):
3972 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
3973 prop224 aka "Next Generation Hidden Services". Service and clients
3974 don't use this functionality yet. Closes ticket 19043. Based on
3975 initial code by Alec Heifetz.
3976 - Relays now support the HSDir version 3 protocol, so that they can
3977 can store and serve v3 descriptors. This is part of the next-
3978 generation onion service work detailed in proposal 224. Closes
3981 o Major features (protocol, ed25519 identity keys):
3982 - Clients now support including Ed25519 identity keys in the EXTEND2
3983 cells they generate. By default, this is controlled by a consensus
3984 parameter, currently disabled. You can turn this feature on for
3985 testing by setting ExtendByEd25519ID in your configuration. This
3986 might make your traffic appear different than the traffic
3987 generated by other users, however. Implements part of ticket
3988 15056; part of proposal 220.
3989 - Relays now understand requests to extend to other relays by their
3990 Ed25519 identity keys. When an Ed25519 identity key is included in
3991 an EXTEND2 cell, the relay will only extend the circuit if the
3992 other relay can prove ownership of that identity. Implements part
3993 of ticket 15056; part of proposal 220.
3994 - Relays now use Ed25519 to prove their Ed25519 identities and to
3995 one another, and to clients. This algorithm is faster and more
3996 secure than the RSA-based handshake we've been doing until now.
3997 Implements the second big part of proposal 220; Closes
4000 o Major features (security):
4001 - Change the algorithm used to decide DNS TTLs on client and server
4002 side, to better resist DNS-based correlation attacks like the
4003 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4004 Feamster. Now relays only return one of two possible DNS TTL
4005 values, and clients are willing to believe DNS TTL values up to 3
4006 hours long. Closes ticket 19769.
4008 o Major bugfixes (client, onion service, also in 0.2.9.9):
4009 - Fix a client-side onion service reachability bug, where multiple
4010 socks requests to an onion service (or a single slow request)
4011 could cause us to mistakenly mark some of the service's
4012 introduction points as failed, and we cache that failure so
4013 eventually we run out and can't reach the service. Also resolves a
4014 mysterious "Remote server sent bogus reason code 65021" log
4015 warning. The bug was introduced in ticket 17218, where we tried to
4016 remember the circuit end reason as a uint16_t, which mangled
4017 negative values. Partially fixes bug 21056 and fixes bug 20307;
4018 bugfix on 0.2.8.1-alpha.
4020 o Major bugfixes (crash, directory connections):
4021 - Fix a rare crash when sending a begin cell on a circuit whose
4022 linked directory connection had already been closed. Fixes bug
4023 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
4025 o Major bugfixes (directory authority):
4026 - During voting, when marking a relay as a probable sybil, do not
4027 clear its BadExit flag: sybils can still be bad in other ways
4028 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4031 o Major bugfixes (DNS):
4032 - Fix a bug that prevented exit nodes from caching DNS records for
4033 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4035 o Major bugfixes (IPv6 Exits):
4036 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4037 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4038 exit policy rejects that port on more than an IPv6 /16 of
4039 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4040 which rejected a relay's own IPv6 address by default. Fixes bug
4041 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4043 o Major bugfixes (parsing):
4044 - Fix an integer underflow bug when comparing malformed Tor
4045 versions. This bug could crash Tor when built with
4046 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4047 0.2.9.8, which were built with -ftrapv by default. In other cases
4048 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4049 on 0.0.8pre1. Found by OSS-Fuzz.
4050 - When parsing a malformed content-length field from an HTTP
4051 message, do not read off the end of the buffer. This bug was a
4052 potential remote denial-of-service attack against Tor clients and
4053 relays. A workaround was released in October 2016, to prevent this
4054 bug from crashing Tor. This is a fix for the underlying issue,
4055 which should no longer matter (if you applied the earlier patch).
4056 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
4057 using AFL (http://lcamtuf.coredump.cx/afl/).
4059 o Major bugfixes (scheduler):
4060 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
4061 caused the channel scheduler to behave more or less randomly,
4062 rather than preferring channels with higher-priority circuits.
4063 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
4065 o Major bugfixes (security, also in 0.2.9.9):
4066 - Downgrade the "-ftrapv" option from "always on" to "only on when
4067 --enable-expensive-hardening is provided." This hardening option,
4068 like others, can turn survivable bugs into crashes--and having it
4069 on by default made a (relatively harmless) integer overflow bug
4070 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4071 bugfix on 0.2.9.1-alpha.
4073 o Minor feature (client):
4074 - Enable IPv6 traffic on the SocksPort by default. To disable this,
4075 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
4077 o Minor feature (fallback scripts):
4078 - Add a check_existing mode to updateFallbackDirs.py, which checks
4079 if fallbacks in the hard-coded list are working. Closes ticket
4080 20174. Patch by haxxpop.
4082 o Minor feature (protocol versioning):
4083 - Add new protocol version for proposal 224. HSIntro now advertises
4084 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
4086 o Minor features (ciphersuite selection):
4087 - Allow relays to accept a wider range of ciphersuites, including
4088 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
4089 - Clients now advertise a list of ciphersuites closer to the ones
4090 preferred by Firefox. Closes part of ticket 15426.
4092 o Minor features (controller):
4093 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
4094 shared-random values to the controller. Closes ticket 19925.
4095 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
4096 rather than "unrecognized." Closes ticket 20389; patch from
4099 o Minor features (controller, configuration):
4100 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
4101 and so on, now comes with a __*Port variant that will not be saved
4102 to the torrc file by the controller's SAVECONF command. This
4103 change allows TorBrowser to set up a single-use domain socket for
4104 each time it launches Tor. Closes ticket 20956.
4105 - The GETCONF command can now query options that may only be
4106 meaningful in context-sensitive lists. This allows the controller
4107 to query the mixed SocksPort/__SocksPort style options introduced
4108 in feature 20956. Implements ticket 21300.
4110 o Minor features (diagnostic, directory client):
4111 - Warn when we find an unexpected inconsistency in directory
4112 download status objects. Prevents some negative consequences of
4115 o Minor features (directory authorities):
4116 - Directory authorities now reject descriptors that claim to be
4117 malformed versions of Tor. Helps prevent exploitation of
4119 - Reject version numbers with components that exceed INT32_MAX.
4120 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
4121 Fixes bug 21450; bugfix on 0.0.8pre1.
4123 o Minor features (directory authority):
4124 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
4125 default) to control whether authorities should try to probe relays
4126 by their Ed25519 link keys. This option will go away in a few
4127 releases--unless we encounter major trouble in our ed25519 link
4128 protocol rollout, in which case it will serve as a safety option.
4130 o Minor features (directory cache):
4131 - Relays and bridges will now refuse to serve the consensus they
4132 have if they know it is too old for a client to use. Closes
4135 o Minor features (ed25519 link handshake):
4136 - Advertise support for the ed25519 link handshake using the
4137 subprotocol-versions mechanism, so that clients can tell which
4138 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
4140 o Minor features (entry guards):
4141 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
4142 break regression tests.
4143 - Require UseEntryGuards when UseBridges is set, in order to make
4144 sure bridges aren't bypassed. Resolves ticket 20502.
4146 o Minor features (fallback directories):
4147 - Allow 3 fallback relays per operator, which is safe now that we
4148 are choosing 200 fallback relays. Closes ticket 20912.
4149 - Annotate updateFallbackDirs.py with the bandwidth and consensus
4150 weight for each candidate fallback. Closes ticket 20878.
4151 - Display the relay fingerprint when downloading consensuses from
4152 fallbacks. Closes ticket 20908.
4153 - Exclude relays affected by bug 20499 from the fallback list.
4154 Exclude relays from the fallback list if they are running versions
4155 known to be affected by bug 20499, or if in our tests they deliver
4156 a stale consensus (i.e. one that expired more than 24 hours ago).
4157 Closes ticket 20539.
4158 - Make it easier to change the output sort order of fallbacks.
4159 Closes ticket 20822.
4160 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
4162 - Require fallback directories to have the same address and port for
4163 7 days (now that we have enough relays with this stability).
4164 Relays whose OnionOO stability timer is reset on restart by bug
4165 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
4166 this issue. Closes ticket 20880; maintains short-term fix
4168 - Require fallbacks to have flags for 90% of the time (weighted
4169 decaying average), rather than 95%. This allows at least 73% of
4170 clients to bootstrap in the first 5 seconds without contacting an
4171 authority. Part of ticket 18828.
4172 - Select 200 fallback directories for each release. Closes
4175 o Minor features (fingerprinting resistance, authentication):
4176 - Extend the length of RSA keys used for TLS link authentication to
4177 2048 bits. (These weren't used for forward secrecy; for forward
4178 secrecy, we used P256.) Closes ticket 13752.
4180 o Minor features (geoip):
4181 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
4184 o Minor features (geoip, also in 0.2.9.9):
4185 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4188 o Minor features (infrastructure):
4189 - Implement smartlist_add_strdup() function. Replaces the use of
4190 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
4192 o Minor features (linting):
4193 - Enhance the changes file linter to warn on Tor versions that are
4194 prefixed with "tor-". Closes ticket 21096.
4196 o Minor features (logging):
4197 - In several places, describe unset ed25519 keys as "<unset>",
4198 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
4200 o Minor features (portability, compilation):
4201 - Autoconf now checks to determine if OpenSSL structures are opaque,
4202 instead of explicitly checking for OpenSSL version numbers. Part
4204 - Support building with recent LibreSSL code that uses opaque
4205 structures. Closes ticket 21359.
4207 o Minor features (relay):
4208 - We now allow separation of exit and relay traffic to different
4209 source IP addresses, using the OutboundBindAddressExit and
4210 OutboundBindAddressOR options respectively. Closes ticket 17975.
4211 Written by Michael Sonntag.
4213 o Minor features (reliability, crash):
4214 - Try better to detect problems in buffers where they might grow (or
4215 think they have grown) over 2 GB in size. Diagnostic for
4218 o Minor features (testing):
4219 - During 'make test-network-all', if tor logs any warnings, ask
4220 chutney to output them. Requires a recent version of chutney with
4221 the 21572 patch. Implements 21570.
4223 o Minor bugfix (control protocol):
4224 - The reply to a "GETINFO config/names" request via the control
4225 protocol now spells the type "Dependent" correctly. This is a
4226 breaking change in the control protocol. (The field seems to be
4227 ignored by the most common known controllers.) Fixes bug 18146;
4228 bugfix on 0.1.1.4-alpha.
4229 - The GETINFO extra-info/digest/<digest> command was broken because
4230 of a wrong base16 decode return value check, introduced when
4231 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4233 o Minor bugfix (logging):
4234 - Don't recommend the use of Tor2web in non-anonymous mode.
4235 Recommending Tor2web is a bad idea because the client loses all
4236 anonymity. Tor2web should only be used in specific cases by users
4237 who *know* and understand the issues. Fixes bug 21294; bugfix
4240 o Minor bugfixes (bug resilience):
4241 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
4242 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
4243 Hans Jerry Illikainen.
4245 o Minor bugfixes (build):
4246 - Replace obsolete Autoconf macros with their modern equivalent and
4247 prevent similar issues in the future. Fixes bug 20990; bugfix
4250 o Minor bugfixes (certificate expiration time):
4251 - Avoid using link certificates that don't become valid till some
4252 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
4254 o Minor bugfixes (client):
4255 - Always recover from failures in extend_info_from_node(), in an
4256 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
4257 bugfix on 0.2.3.1-alpha.
4258 - When clients that use bridges start up with a cached consensus on
4259 disk, they were ignoring it and downloading a new one. Now they
4260 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
4262 o Minor bugfixes (code correctness):
4263 - Repair a couple of (unreachable or harmless) cases of the risky
4264 comparison-by-subtraction pattern that caused bug 21278.
4266 o Minor bugfixes (config):
4267 - Don't assert on startup when trying to get the options list and
4268 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
4269 options so of course they aren't ready yet. Fixes bug 21062;
4270 bugfix on 0.2.9.3-alpha.
4272 o Minor bugfixes (configuration):
4273 - Accept non-space whitespace characters after the severity level in
4274 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
4275 - Support "TByte" and "TBytes" units in options given in bytes.
4276 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
4277 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
4279 o Minor bugfixes (configure, autoconf):
4280 - Rename the configure option --enable-expensive-hardening to
4281 --enable-fragile-hardening. Expensive hardening makes the tor
4282 daemon abort when some kinds of issues are detected. Thus, it
4283 makes tor more at risk of remote crashes but safer against RCE or
4284 heartbleed bug category. We now try to explain this issue in a
4285 message from the configure script. Fixes bug 21290; bugfix
4288 o Minor bugfixes (consensus weight):
4289 - Add new consensus method that initializes bw weights to 1 instead
4290 of 0. This prevents a zero weight from making it all the way to
4291 the end (happens in small testing networks) and causing an error.
4292 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
4294 o Minor bugfixes (crash prevention):
4295 - Fix an (currently untriggerable, but potentially dangerous) crash
4296 bug when base32-encoding inputs whose sizes are not a multiple of
4297 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
4299 o Minor bugfixes (dead code):
4300 - Remove a redundant check for PidFile changes at runtime in
4301 options_transition_allowed(): this check is already performed
4302 regardless of whether the sandbox is active. Fixes bug 21123;
4303 bugfix on 0.2.5.4-alpha.
4305 o Minor bugfixes (descriptors):
4306 - Correctly recognise downloaded full descriptors as valid, even
4307 when using microdescriptors as circuits. This affects clients with
4308 FetchUselessDescriptors set, and may affect directory authorities.
4309 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
4311 o Minor bugfixes (directory mirrors):
4312 - Allow relays to use directory mirrors without a DirPort: these
4313 relays need to be contacted over their ORPorts using a begindir
4314 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
4315 - Clarify the message logged when a remote relay is unexpectedly
4316 missing an ORPort or DirPort: users were confusing this with a
4317 local port. Fixes another case of bug 20711; bugfix
4320 o Minor bugfixes (directory system):
4321 - Bridges and relays now use microdescriptors (like clients do)
4322 rather than old-style router descriptors. Now bridges will blend
4323 in with clients in terms of the circuits they build. Fixes bug
4324 6769; bugfix on 0.2.3.2-alpha.
4325 - Download all consensus flavors, descriptors, and authority
4326 certificates when FetchUselessDescriptors is set, regardless of
4327 whether tor is a directory cache or not. Fixes bug 20667; bugfix
4328 on all recent tor versions.
4330 o Minor bugfixes (documentation):
4331 - Update the tor manual page to document every option that can not
4332 be changed while tor is running. Fixes bug 21122.
4334 o Minor bugfixes (ed25519 certificates):
4335 - Correctly interpret ed25519 certificates that would expire some
4336 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
4338 o Minor bugfixes (fallback directories):
4339 - Avoid checking fallback candidates' DirPorts if they are down in
4340 OnionOO. When a relay operator has multiple relays, this
4341 prioritizes relays that are up over relays that are down. Fixes
4342 bug 20926; bugfix on 0.2.8.3-alpha.
4343 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
4344 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
4345 - Stop failing when a relay has no uptime data in
4346 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
4348 o Minor bugfixes (hidden service):
4349 - Clean up the code for expiring intro points with no associated
4350 circuits. It was causing, rarely, a service with some expiring
4351 introduction points to not open enough additional introduction
4352 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
4353 - Resolve two possible underflows which could lead to creating and
4354 closing a lot of introduction point circuits in a non-stop loop.
4355 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
4356 - Stop setting the torrc option HiddenServiceStatistics to "0" just
4357 because we're not a bridge or relay. Instead, we preserve whatever
4358 value the user set (or didn't set). Fixes bug 21150; bugfix
4361 o Minor bugfixes (hidden services):
4362 - Make hidden services check for failed intro point connections,
4363 even when they have exceeded their intro point creation limit.
4364 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
4365 - Make hidden services with 8 to 10 introduction points check for
4366 failed circuits immediately after startup. Previously, they would
4367 wait for 5 minutes before performing their first checks. Fixes bug
4368 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
4369 - Stop ignoring misconfigured hidden services. Instead, refuse to
4370 start tor until the misconfigurations have been corrected. Fixes
4371 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
4374 o Minor bugfixes (IPv6):
4375 - Make IPv6-using clients try harder to find an IPv6 directory
4376 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
4377 - When IPv6 addresses have not been downloaded yet (microdesc
4378 consensus documents don't list relay IPv6 addresses), use hard-
4379 coded addresses for authorities, fallbacks, and configured
4380 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
4381 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
4383 o Minor bugfixes (memory leak at exit):
4384 - Fix a small harmless memory leak at exit of the previously unused
4385 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
4388 o Minor bugfixes (onion services):
4389 - Allow the number of introduction points to be as low as 0, rather
4390 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
4392 o Minor bugfixes (portability):
4393 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
4394 It is supported by OpenBSD itself, and also by most OpenBSD
4395 variants (such as Bitrig). Fixes bug 20980; bugfix
4398 o Minor bugfixes (portability, also in 0.2.9.9):
4399 - Avoid crashing when Tor is built using headers that contain
4400 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4401 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4403 - Fix Libevent detection on platforms without Libevent 1 headers
4404 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4406 o Minor bugfixes (relay):
4407 - Avoid a double-marked-circuit warning that could happen when we
4408 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
4410 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
4411 initializing the keys would reset the DataDirectory to 0700
4412 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
4413 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
4415 o Minor bugfixes (testing):
4416 - Fix Raspbian build issues related to missing socket errno in
4417 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
4418 - Remove undefined behavior from the backtrace generator by removing
4419 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
4420 - Use bash in src/test/test-network.sh. This ensures we reliably
4421 call chutney's newer tools/test-network.sh when available. Fixes
4422 bug 21562; bugfix on 0.2.9.1-alpha.
4424 o Minor bugfixes (tor-resolve):
4425 - The tor-resolve command line tool now rejects hostnames over 255
4426 characters in length. Previously, it would silently truncate them,
4427 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4428 Patch by "junglefowl".
4430 o Minor bugfixes (unit tests):
4431 - Allow the unit tests to pass even when DNS lookups of bogus
4432 addresses do not fail as expected. Fixes bug 20862 and 20863;
4433 bugfix on unit tests introduced in 0.2.8.1-alpha
4434 through 0.2.9.4-alpha.
4436 o Minor bugfixes (util):
4437 - When finishing writing a file to disk, if we were about to replace
4438 the file with the temporary file created before and we fail to
4439 replace it, remove the temporary file so it doesn't stay on disk.
4440 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
4442 o Minor bugfixes (Windows services):
4443 - Be sure to initialize the monotonic time subsystem before using
4444 it, even when running as an NT service. Fixes bug 21356; bugfix
4447 o Minor bugfixes (Windows):
4448 - Check for getpagesize before using it to mmap files. This fixes
4449 compilation in some MinGW environments. Fixes bug 20530; bugfix on
4450 0.1.2.1-alpha. Reported by "ice".
4452 o Code simplification and refactoring:
4453 - Abolish all global guard context in entrynodes.c; replace with new
4454 guard_selection_t structure as preparation for proposal 271.
4455 Closes ticket 19858.
4456 - Extract magic numbers in circuituse.c into defined variables.
4457 - Introduce rend_service_is_ephemeral() that tells if given onion
4458 service is ephemeral. Replace unclear NULL-checkings for service
4459 directory with this function. Closes ticket 20526.
4460 - Refactor circuit_is_available_for_use to remove unnecessary check.
4461 - Refactor circuit_predict_and_launch_new for readability and
4462 testability. Closes ticket 18873.
4463 - Refactor code to manipulate global_origin_circuit_list into
4464 separate functions. Closes ticket 20921.
4465 - Refactor large if statement in purpose_needs_anonymity to use
4466 switch statement instead. Closes part of ticket 20077.
4467 - Refactor the hashing API to return negative values for errors, as
4468 is done as throughout the codebase. Closes ticket 20717.
4469 - Remove data structures that were used to index or_connection
4470 objects by their RSA identity digests. These structures are fully
4471 redundant with the similar structures used in the
4472 channel abstraction.
4473 - Remove duplicate code in the channel_write_*cell() functions.
4474 Closes ticket 13827; patch from Pingl.
4475 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
4476 use only purpose_needs_anonymity. Closes part of ticket 20077.
4477 - The code to generate and parse EXTEND and EXTEND2 cells has been
4478 replaced with code automatically generated by the
4481 o Documentation (formatting):
4482 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
4483 blocks were incorrectly appearing. Closes ticket 20885.
4485 o Documentation (man page):
4486 - Clarify many options in tor.1 and add some min/max values for
4487 HiddenService options. Closes ticket 21058.
4490 - Change '1' to 'weight_scale' in consensus bw weights calculation
4491 comments, as that is reality. Closes ticket 20273. Patch
4493 - Clarify that when ClientRejectInternalAddresses is enabled (which
4494 is the default), multicast DNS hostnames for machines on the local
4495 network (of the form *.local) are also rejected. Closes
4497 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
4498 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
4499 - Include the "TBits" unit in Tor's man page. Fixes part of bug
4500 20622; bugfix on 0.2.5.1-alpha.
4501 - Small fixes to the fuzzing documentation. Closes ticket 21472.
4502 - Stop the man page from incorrectly stating that HiddenServiceDir
4503 must already exist. Fixes 20486.
4504 - Update the description of the directory server options in the
4505 manual page, to clarify that a relay no longer needs to set
4506 DirPort in order to be a directory cache. Closes ticket 21720.
4509 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
4510 limit for relays running on a single IP applies to authority IP
4511 addresses as well as to non-authority IP addresses. Closes
4513 - The UseDirectoryGuards torrc option no longer exists: all users
4514 that use entry guards will also use directory guards. Related to
4515 proposal 271; implements part of ticket 20831.
4518 - Add tests for networkstatus_compute_bw_weights_v10.
4519 - Add unit tests circuit_predict_and_launch_new.
4520 - Extract dummy_origin_circuit_new so it can be used by other
4522 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
4523 from "overcaffeinated".
4524 - Perform the coding style checks when running the tests and fail
4525 when coding style violations are found. Closes ticket 5500.
4528 Changes in version 0.2.8.13 - 2017-03-03
4529 Tor 0.2.8.13 backports a security fix from later Tor
4530 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
4531 this release, if for some reason they cannot upgrade to a later
4532 release series, and if they build Tor with the --enable-expensive-hardening
4535 Note that support for Tor 0.2.8.x is ending next year: we will not issue
4536 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
4537 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4539 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4540 - Fix an integer underflow bug when comparing malformed Tor
4541 versions. This bug could crash Tor when built with
4542 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4543 0.2.9.8, which were built with -ftrapv by default. In other cases
4544 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4545 on 0.0.8pre1. Found by OSS-Fuzz.
4547 o Minor features (geoip):
4548 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4552 Changes in version 0.2.7.7 - 2017-03-03
4553 Tor 0.2.7.7 backports a number of security fixes from later Tor
4554 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
4555 this release, if for some reason they cannot upgrade to a later
4558 Note that support for Tor 0.2.7.x is ending this year: we will not issue
4559 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
4560 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4562 o Directory authority changes (backport from 0.2.8.5-rc):
4563 - Urras is no longer a directory authority. Closes ticket 19271.
4565 o Directory authority changes (backport from 0.2.9.2-alpha):
4566 - The "Tonga" bridge authority has been retired; the new bridge
4567 authority is "Bifroest". Closes tickets 19728 and 19690.
4569 o Directory authority key updates (backport from 0.2.8.1-alpha):
4570 - Update the V3 identity key for the dannenberg directory authority:
4571 it was changed on 18 November 2015. Closes task 17906. Patch
4574 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4575 - Fix a bug in parsing that could cause clients to read a single
4576 byte past the end of an allocated region. This bug could be used
4577 to cause hardened clients (built with --enable-expensive-hardening)
4578 to crash if they tried to visit a hostile hidden service. Non-
4579 hardened clients are only affected depending on the details of
4580 their platform's memory allocator. Fixes bug 21018; bugfix on
4581 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4582 2016-12-002 and as CVE-2016-1254.
4584 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4585 - Stop a crash that could occur when a client running with DNSPort
4586 received a query with multiple address types, and the first
4587 address type was not supported. Found and fixed by Scott Dial.
4588 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4589 - Prevent a class of security bugs caused by treating the contents
4590 of a buffer chunk as if they were a NUL-terminated string. At
4591 least one such bug seems to be present in all currently used
4592 versions of Tor, and would allow an attacker to remotely crash
4593 most Tor instances, especially those compiled with extra compiler
4594 hardening. With this defense in place, such bugs can't crash Tor,
4595 though we should still fix them as they occur. Closes ticket
4596 20384 (TROVE-2016-10-001).
4598 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4599 - Avoid a difficult-to-trigger heap corruption attack when extending
4600 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4601 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4602 Reported by Guido Vranken.
4604 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4605 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4606 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4608 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4609 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4610 pointer to the previous (uninitialized) key value. The impact here
4611 should be limited to a difficult-to-trigger crash, if OpenSSL is
4612 running an engine that makes key generation failures possible, or
4613 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4614 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4617 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4618 - Fix an integer underflow bug when comparing malformed Tor
4619 versions. This bug could crash Tor when built with
4620 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4621 0.2.9.8, which were built with -ftrapv by default. In other cases
4622 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4623 on 0.0.8pre1. Found by OSS-Fuzz.
4625 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4626 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4627 zero size. Check size argument to memwipe() for underflow. Fixes
4628 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4631 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4632 - Make Tor survive errors involving connections without a
4633 corresponding event object. Previously we'd fail with an
4634 assertion; now we produce a log message. Related to bug 16248.
4636 o Minor features (geoip):
4637 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4641 Changes in version 0.2.6.11 - 2017-03-03
4642 Tor 0.2.6.11 backports a number of security fixes from later Tor
4643 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
4644 this release, if for some reason they cannot upgrade to a later
4647 Note that support for Tor 0.2.6.x is ending this year: we will not issue
4648 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
4649 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4651 o Directory authority changes (backport from 0.2.8.5-rc):
4652 - Urras is no longer a directory authority. Closes ticket 19271.
4654 o Directory authority changes (backport from 0.2.9.2-alpha):
4655 - The "Tonga" bridge authority has been retired; the new bridge
4656 authority is "Bifroest". Closes tickets 19728 and 19690.
4658 o Directory authority key updates (backport from 0.2.8.1-alpha):
4659 - Update the V3 identity key for the dannenberg directory authority:
4660 it was changed on 18 November 2015. Closes task 17906. Patch
4663 o Major features (security fixes, backport from 0.2.9.4-alpha):
4664 - Prevent a class of security bugs caused by treating the contents
4665 of a buffer chunk as if they were a NUL-terminated string. At
4666 least one such bug seems to be present in all currently used
4667 versions of Tor, and would allow an attacker to remotely crash
4668 most Tor instances, especially those compiled with extra compiler
4669 hardening. With this defense in place, such bugs can't crash Tor,
4670 though we should still fix them as they occur. Closes ticket
4671 20384 (TROVE-2016-10-001).
4673 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4674 - Fix a bug in parsing that could cause clients to read a single
4675 byte past the end of an allocated region. This bug could be used
4676 to cause hardened clients (built with --enable-expensive-hardening)
4677 to crash if they tried to visit a hostile hidden service. Non-
4678 hardened clients are only affected depending on the details of
4679 their platform's memory allocator. Fixes bug 21018; bugfix on
4680 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4681 2016-12-002 and as CVE-2016-1254.
4683 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4684 - Stop a crash that could occur when a client running with DNSPort
4685 received a query with multiple address types, and the first
4686 address type was not supported. Found and fixed by Scott Dial.
4687 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4689 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4690 - Fix an error that could cause us to read 4 bytes before the
4691 beginning of an openssl string. This bug could be used to cause
4692 Tor to crash on systems with unusual malloc implementations, or
4693 systems with unusual hardening installed. Fixes bug 17404; bugfix
4696 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4697 - Avoid a difficult-to-trigger heap corruption attack when extending
4698 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4699 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4700 Reported by Guido Vranken.
4702 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4703 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4704 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4706 o Major bugfixes (guard selection, backport from 0.2.7.6):
4707 - Actually look at the Guard flag when selecting a new directory
4708 guard. When we implemented the directory guard design, we
4709 accidentally started treating all relays as if they have the Guard
4710 flag during guard selection, leading to weaker anonymity and worse
4711 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4714 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4715 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4716 pointer to the previous (uninitialized) key value. The impact here
4717 should be limited to a difficult-to-trigger crash, if OpenSSL is
4718 running an engine that makes key generation failures possible, or
4719 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4720 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4723 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4724 - Fix an integer underflow bug when comparing malformed Tor
4725 versions. This bug could crash Tor when built with
4726 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4727 0.2.9.8, which were built with -ftrapv by default. In other cases
4728 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4729 on 0.0.8pre1. Found by OSS-Fuzz.
4731 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4732 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4733 zero size. Check size argument to memwipe() for underflow. Fixes
4734 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4737 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4738 - Make Tor survive errors involving connections without a
4739 corresponding event object. Previously we'd fail with an
4740 assertion; now we produce a log message. Related to bug 16248.
4742 o Minor features (geoip):
4743 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4746 o Minor bugfixes (compilation, backport from 0.2.7.6):
4747 - Fix a compilation warning with Clang 3.6: Do not check the
4748 presence of an address which can never be NULL. Fixes bug 17781.
4751 Changes in version 0.2.5.13 - 2017-03-03
4752 Tor 0.2.5.13 backports a number of security fixes from later Tor
4753 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
4754 this release, if for some reason they cannot upgrade to a later
4757 Note that support for Tor 0.2.5.x is ending next year: we will not issue
4758 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
4759 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4761 o Directory authority changes (backport from 0.2.8.5-rc):
4762 - Urras is no longer a directory authority. Closes ticket 19271.
4764 o Directory authority changes (backport from 0.2.9.2-alpha):
4765 - The "Tonga" bridge authority has been retired; the new bridge
4766 authority is "Bifroest". Closes tickets 19728 and 19690.
4768 o Directory authority key updates (backport from 0.2.8.1-alpha):
4769 - Update the V3 identity key for the dannenberg directory authority:
4770 it was changed on 18 November 2015. Closes task 17906. Patch
4773 o Major features (security fixes, backport from 0.2.9.4-alpha):
4774 - Prevent a class of security bugs caused by treating the contents
4775 of a buffer chunk as if they were a NUL-terminated string. At
4776 least one such bug seems to be present in all currently used
4777 versions of Tor, and would allow an attacker to remotely crash
4778 most Tor instances, especially those compiled with extra compiler
4779 hardening. With this defense in place, such bugs can't crash Tor,
4780 though we should still fix them as they occur. Closes ticket
4781 20384 (TROVE-2016-10-001).
4783 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4784 - Fix a bug in parsing that could cause clients to read a single
4785 byte past the end of an allocated region. This bug could be used
4786 to cause hardened clients (built with --enable-expensive-hardening)
4787 to crash if they tried to visit a hostile hidden service. Non-
4788 hardened clients are only affected depending on the details of
4789 their platform's memory allocator. Fixes bug 21018; bugfix on
4790 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4791 2016-12-002 and as CVE-2016-1254.
4793 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4794 - Stop a crash that could occur when a client running with DNSPort
4795 received a query with multiple address types, and the first
4796 address type was not supported. Found and fixed by Scott Dial.
4797 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4799 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4800 - Fix an error that could cause us to read 4 bytes before the
4801 beginning of an openssl string. This bug could be used to cause
4802 Tor to crash on systems with unusual malloc implementations, or
4803 systems with unusual hardening installed. Fixes bug 17404; bugfix
4806 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4807 - Avoid a difficult-to-trigger heap corruption attack when extending
4808 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4809 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4810 Reported by Guido Vranken.
4812 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4813 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4814 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4816 o Major bugfixes (guard selection, backport from 0.2.7.6):
4817 - Actually look at the Guard flag when selecting a new directory
4818 guard. When we implemented the directory guard design, we
4819 accidentally started treating all relays as if they have the Guard
4820 flag during guard selection, leading to weaker anonymity and worse
4821 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4824 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4825 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4826 pointer to the previous (uninitialized) key value. The impact here
4827 should be limited to a difficult-to-trigger crash, if OpenSSL is
4828 running an engine that makes key generation failures possible, or
4829 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4830 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4833 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4834 - Fix an integer underflow bug when comparing malformed Tor
4835 versions. This bug could crash Tor when built with
4836 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4837 0.2.9.8, which were built with -ftrapv by default. In other cases
4838 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4839 on 0.0.8pre1. Found by OSS-Fuzz.
4841 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4842 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4843 zero size. Check size argument to memwipe() for underflow. Fixes
4844 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4847 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4848 - Make Tor survive errors involving connections without a
4849 corresponding event object. Previously we'd fail with an
4850 assertion; now we produce a log message. Related to bug 16248.
4852 o Minor features (geoip):
4853 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4856 o Minor bugfixes (compilation, backport from 0.2.7.6):
4857 - Fix a compilation warning with Clang 3.6: Do not check the
4858 presence of an address which can never be NULL. Fixes bug 17781.
4860 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
4861 - Check for failures from crypto_early_init, and refuse to continue.
4862 A previous typo meant that we could keep going with an
4863 uninitialized crypto library, and would have OpenSSL initialize
4864 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4865 when implementing ticket 4900. Patch by "teor".
4867 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4868 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4869 a client authorized hidden service. Fixes bug 15823; bugfix
4873 Changes in version 0.2.4.28 - 2017-03-03
4874 Tor 0.2.4.28 backports a number of security fixes from later Tor
4875 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
4876 this release, if for some reason they cannot upgrade to a later
4879 Note that support for Tor 0.2.4.x is ending soon: we will not issue
4880 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
4881 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
4883 o Directory authority changes (backport from 0.2.8.5-rc):
4884 - Urras is no longer a directory authority. Closes ticket 19271.
4886 o Directory authority changes (backport from 0.2.9.2-alpha):
4887 - The "Tonga" bridge authority has been retired; the new bridge
4888 authority is "Bifroest". Closes tickets 19728 and 19690.
4890 o Directory authority key updates (backport from 0.2.8.1-alpha):
4891 - Update the V3 identity key for the dannenberg directory authority:
4892 it was changed on 18 November 2015. Closes task 17906. Patch
4895 o Major features (security fixes, backport from 0.2.9.4-alpha):
4896 - Prevent a class of security bugs caused by treating the contents
4897 of a buffer chunk as if they were a NUL-terminated string. At
4898 least one such bug seems to be present in all currently used
4899 versions of Tor, and would allow an attacker to remotely crash
4900 most Tor instances, especially those compiled with extra compiler
4901 hardening. With this defense in place, such bugs can't crash Tor,
4902 though we should still fix them as they occur. Closes ticket
4903 20384 (TROVE-2016-10-001).
4905 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4906 - Fix a bug in parsing that could cause clients to read a single
4907 byte past the end of an allocated region. This bug could be used
4908 to cause hardened clients (built with --enable-expensive-hardening)
4909 to crash if they tried to visit a hostile hidden service. Non-
4910 hardened clients are only affected depending on the details of
4911 their platform's memory allocator. Fixes bug 21018; bugfix on
4912 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4913 2016-12-002 and as CVE-2016-1254.
4915 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4916 - Fix an error that could cause us to read 4 bytes before the
4917 beginning of an openssl string. This bug could be used to cause
4918 Tor to crash on systems with unusual malloc implementations, or
4919 systems with unusual hardening installed. Fixes bug 17404; bugfix
4922 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4923 - Avoid a difficult-to-trigger heap corruption attack when extending
4924 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4925 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4926 Reported by Guido Vranken.
4928 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4929 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4930 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4932 o Major bugfixes (guard selection, backport from 0.2.7.6):
4933 - Actually look at the Guard flag when selecting a new directory
4934 guard. When we implemented the directory guard design, we
4935 accidentally started treating all relays as if they have the Guard
4936 flag during guard selection, leading to weaker anonymity and worse
4937 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4940 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4941 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4942 pointer to the previous (uninitialized) key value. The impact here
4943 should be limited to a difficult-to-trigger crash, if OpenSSL is
4944 running an engine that makes key generation failures possible, or
4945 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4946 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4949 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4950 - Fix an integer underflow bug when comparing malformed Tor
4951 versions. This bug could crash Tor when built with
4952 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4953 0.2.9.8, which were built with -ftrapv by default. In other cases
4954 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4955 on 0.0.8pre1. Found by OSS-Fuzz.
4957 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4958 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4959 zero size. Check size argument to memwipe() for underflow. Fixes
4960 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4963 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4964 - Make Tor survive errors involving connections without a
4965 corresponding event object. Previously we'd fail with an
4966 assertion; now we produce a log message. Related to bug 16248.
4968 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
4969 - Make it harder for attackers to overload hidden services with
4970 introductions, by blocking multiple introduction requests on the
4971 same circuit. Resolves ticket 15515.
4973 o Minor features (geoip):
4974 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4977 o Minor bugfixes (compilation, backport from 0.2.7.6):
4978 - Fix a compilation warning with Clang 3.6: Do not check the
4979 presence of an address which can never be NULL. Fixes bug 17781.
4981 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4982 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4983 a client authorized hidden service. Fixes bug 15823; bugfix
4987 Changes in version 0.2.9.10 - 2017-03-01
4988 Tor 0.2.9.10 backports a security fix from later Tor release. It also
4989 includes fixes for some major issues affecting directory authorities,
4990 LibreSSL compatibility, and IPv6 correctness.
4992 The Tor 0.2.9.x release series is now marked as a long-term-support
4993 series. We intend to backport security fixes to 0.2.9.x until at
4994 least January of 2020.
4996 o Major bugfixes (directory authority, 0.3.0.3-alpha):
4997 - During voting, when marking a relay as a probable sybil, do not
4998 clear its BadExit flag: sybils can still be bad in other ways
4999 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5002 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
5003 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5004 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5005 exit policy rejects that port on more than an IPv6 /16 of
5006 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5007 which rejected a relay's own IPv6 address by default. Fixes bug
5008 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5010 o Major bugfixes (parsing, also in 0.3.0.4-rc):
5011 - Fix an integer underflow bug when comparing malformed Tor
5012 versions. This bug could crash Tor when built with
5013 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5014 0.2.9.8, which were built with -ftrapv by default. In other cases
5015 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5016 on 0.0.8pre1. Found by OSS-Fuzz.
5018 o Minor features (directory authorities, also in 0.3.0.4-rc):
5019 - Directory authorities now reject descriptors that claim to be
5020 malformed versions of Tor. Helps prevent exploitation of
5022 - Reject version numbers with components that exceed INT32_MAX.
5023 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5024 Fixes bug 21450; bugfix on 0.0.8pre1.
5026 o Minor features (geoip):
5027 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5030 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
5031 - Autoconf now checks to determine if OpenSSL structures are opaque,
5032 instead of explicitly checking for OpenSSL version numbers. Part
5034 - Support building with recent LibreSSL code that uses opaque
5035 structures. Closes ticket 21359.
5037 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
5038 - Repair a couple of (unreachable or harmless) cases of the risky
5039 comparison-by-subtraction pattern that caused bug 21278.
5041 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
5042 - The tor-resolve command line tool now rejects hostnames over 255
5043 characters in length. Previously, it would silently truncate them,
5044 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5045 Patch by "junglefowl".
5048 Changes in version 0.2.9.9 - 2017-01-23
5049 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
5050 cause relays and clients to crash, even if they were not built with
5051 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5052 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5053 version should upgrade.
5055 This release also resolves a client-side onion service reachability
5056 bug, and resolves a pair of small portability issues.
5058 o Major bugfixes (security):
5059 - Downgrade the "-ftrapv" option from "always on" to "only on when
5060 --enable-expensive-hardening is provided." This hardening option,
5061 like others, can turn survivable bugs into crashes -- and having
5062 it on by default made a (relatively harmless) integer overflow bug
5063 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
5064 bugfix on 0.2.9.1-alpha.
5066 o Major bugfixes (client, onion service):
5067 - Fix a client-side onion service reachability bug, where multiple
5068 socks requests to an onion service (or a single slow request)
5069 could cause us to mistakenly mark some of the service's
5070 introduction points as failed, and we cache that failure so
5071 eventually we run out and can't reach the service. Also resolves a
5072 mysterious "Remote server sent bogus reason code 65021" log
5073 warning. The bug was introduced in ticket 17218, where we tried to
5074 remember the circuit end reason as a uint16_t, which mangled
5075 negative values. Partially fixes bug 21056 and fixes bug 20307;
5076 bugfix on 0.2.8.1-alpha.
5078 o Minor features (geoip):
5079 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5082 o Minor bugfixes (portability):
5083 - Avoid crashing when Tor is built using headers that contain
5084 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5085 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5087 - Fix Libevent detection on platforms without Libevent 1 headers
5088 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5091 Changes in version 0.2.8.12 - 2016-12-19
5092 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
5093 below) where Tor clients could crash when attempting to visit a
5094 hostile hidden service. Clients are recommended to upgrade as packages
5095 become available for their systems.
5097 It also includes an updated list of fallback directories, backported
5100 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
5101 backported to 0.2.8 in the future.
5103 o Major bugfixes (parsing, security, backported from 0.2.9.8):
5104 - Fix a bug in parsing that could cause clients to read a single
5105 byte past the end of an allocated region. This bug could be used
5106 to cause hardened clients (built with --enable-expensive-hardening)
5107 to crash if they tried to visit a hostile hidden service. Non-
5108 hardened clients are only affected depending on the details of
5109 their platform's memory allocator. Fixes bug 21018; bugfix on
5110 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5111 2016-12-002 and as CVE-2016-1254.
5113 o Minor features (fallback directory list, backported from 0.2.9.8):
5114 - Replace the 81 remaining fallbacks of the 100 originally
5115 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5116 fallbacks (123 new, 54 existing, 27 removed) generated in December
5117 2016. Resolves ticket 20170.
5119 o Minor features (geoip, backported from 0.2.9.7-rc):
5120 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
5124 Changes in version 0.2.9.8 - 2016-12-19
5125 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
5127 The Tor 0.2.9 series makes mandatory a number of security features
5128 that were formerly optional. It includes support for a new shared-
5129 randomness protocol that will form the basis for next generation
5130 hidden services, includes a single-hop hidden service mode for
5131 optimizing .onion services that don't actually want to be hidden,
5132 tries harder not to overload the directory authorities with excessive
5133 downloads, and supports a better protocol versioning scheme for
5134 improved compatibility with other implementations of the Tor protocol.
5136 And of course, there are numerous other bugfixes and improvements.
5138 This release also includes a fix for a medium-severity issue (bug
5139 21018 below) where Tor clients could crash when attempting to visit a
5140 hostile hidden service. Clients are recommended to upgrade as packages
5141 become available for their systems.
5143 Below are listed the changes since Tor 0.2.8.11. For a list of
5144 changes since 0.2.9.7-rc, see the ChangeLog file.
5146 o New system requirements:
5147 - When building with OpenSSL, Tor now requires version 1.0.1 or
5148 later. OpenSSL 1.0.0 and earlier are no longer supported by the
5149 OpenSSL team, and should not be used. Closes ticket 20303.
5150 - Tor now requires Libevent version 2.0.10-stable or later. Older
5151 versions of Libevent have less efficient backends for several
5152 platforms, and lack the DNS code that we use for our server-side
5153 DNS support. This implements ticket 19554.
5154 - Tor now requires zlib version 1.2 or later, for security,
5155 efficiency, and (eventually) gzip support. (Back when we started,
5156 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
5157 released in 2003. We recommend the latest version.)
5159 o Deprecated features:
5160 - A number of DNS-cache-related sub-options for client ports are now
5161 deprecated for security reasons, and may be removed in a future
5162 version of Tor. (We believe that client-side DNS caching is a bad
5163 idea for anonymity, and you should not turn it on.) The options
5164 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
5165 UseIPv4Cache, and UseIPv6Cache.
5166 - A number of options are deprecated for security reasons, and may
5167 be removed in a future version of Tor. The options are:
5168 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
5169 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
5170 CloseHSClientCircuitsImmediatelyOnTimeout,
5171 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
5172 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
5173 UseNTorHandshake, and WarnUnsafeSocks.
5174 - The *ListenAddress options are now deprecated as unnecessary: the
5175 corresponding *Port options should be used instead. These options
5176 may someday be removed. The affected options are:
5177 ControlListenAddress, DNSListenAddress, DirListenAddress,
5178 NATDListenAddress, ORListenAddress, SocksListenAddress,
5179 and TransListenAddress.
5181 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
5182 - Fix a bug in parsing that could cause clients to read a single
5183 byte past the end of an allocated region. This bug could be used
5184 to cause hardened clients (built with --enable-expensive-hardening)
5185 to crash if they tried to visit a hostile hidden service. Non-
5186 hardened clients are only affected depending on the details of
5187 their platform's memory allocator. Fixes bug 21018; bugfix on
5188 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5189 2016-12-002 and as CVE-2016-1254.
5191 o Major features (build, hardening):
5192 - Tor now builds with -ftrapv by default on compilers that support
5193 it. This option detects signed integer overflow (which C forbids),
5194 and turns it into a hard-failure. We do not apply this option to
5195 code that needs to run in constant time to avoid side-channels;
5196 instead, we use -fwrapv in that code. Closes ticket 17983.
5197 - When --enable-expensive-hardening is selected, stop applying the
5198 clang/gcc sanitizers to code that needs to run in constant time.
5199 Although we are aware of no introduced side-channels, we are not
5200 able to prove that there are none. Related to ticket 17983.
5202 o Major features (circuit building, security):
5203 - Authorities, relays, and clients now require ntor keys in all
5204 descriptors, for all hops (except for rare hidden service protocol
5205 cases), for all circuits, and for all other roles. Part of
5207 - Authorities, relays, and clients only use ntor, except for
5208 rare cases in the hidden service protocol. Part of ticket 19163.
5210 o Major features (compilation):
5211 - Our big list of extra GCC warnings is now enabled by default when
5212 building with GCC (or with anything like Clang that claims to be
5213 GCC-compatible). To make all warnings into fatal compilation
5214 errors, pass --enable-fatal-warnings to configure. Closes
5216 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
5217 turn on C and POSIX extensions. (Previously, we attempted to do
5218 this on an ad hoc basis.) Closes ticket 19139.
5220 o Major features (directory authorities, hidden services):
5221 - Directory authorities can now perform the shared randomness
5222 protocol specified by proposal 250. Using this protocol, directory
5223 authorities generate a global fresh random value every day. In the
5224 future, this value will be used by hidden services to select
5225 HSDirs. This release implements the directory authority feature;
5226 the hidden service side will be implemented in the future as part
5227 of proposal 224. Resolves ticket 16943; implements proposal 250.
5229 o Major features (downloading, random exponential backoff):
5230 - When we fail to download an object from a directory service, wait
5231 for an (exponentially increasing) randomized amount of time before
5232 retrying, rather than a fixed interval as we did before. This
5233 prevents a group of Tor instances from becoming too synchronized,
5234 or a single Tor instance from becoming too predictable, in its
5235 download schedule. Closes ticket 15942.
5237 o Major features (resource management):
5238 - Tor can now notice it is about to run out of sockets, and
5239 preemptively close connections of lower priority. (This feature is
5240 off by default for now, since the current prioritizing method is
5241 yet not mature enough. You can enable it by setting
5242 "DisableOOSCheck 0", but watch out: it might close some sockets
5243 you would rather have it keep.) Closes ticket 18640.
5245 o Major features (single-hop "hidden" services):
5246 - Add experimental HiddenServiceSingleHopMode and
5247 HiddenServiceNonAnonymousMode options. When both are set to 1,
5248 every hidden service on that Tor instance becomes a non-anonymous
5249 Single Onion Service. Single Onions make one-hop (direct)
5250 connections to their introduction and rendezvous points. One-hop
5251 circuits make Single Onion servers easily locatable, but clients
5252 remain location-anonymous. This is compatible with the existing
5253 hidden service implementation, and works on the current Tor
5254 network without any changes to older relays or clients. Implements
5255 proposal 260, completes ticket 17178. Patch by teor and asn.
5257 o Major features (subprotocol versions):
5258 - Tor directory authorities now vote on a set of recommended
5259 "subprotocol versions", and on a set of required subprotocol
5260 versions. Clients and relays that lack support for a _required_
5261 subprotocol version will not start; those that lack support for a
5262 _recommended_ subprotocol version will warn the user to upgrade.
5263 This change allows compatible implementations of the Tor protocol(s)
5264 to exist without pretending to be 100% bug-compatible with
5265 particular releases of Tor itself. Closes ticket 19958; implements
5266 part of proposal 264.
5268 o Major bugfixes (circuit building):
5269 - Hidden service client-to-intro-point and service-to-rendezvous-
5270 point circuits use the TAP key supplied by the protocol, to avoid
5271 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
5273 o Major bugfixes (download scheduling):
5274 - Avoid resetting download status for consensuses hourly, since we
5275 already have another, smarter retry mechanism. Fixes bug 8625;
5276 bugfix on 0.2.0.9-alpha.
5277 - If a consensus expires while we are waiting for certificates to
5278 download, stop waiting for certificates.
5279 - If we stop waiting for certificates less than a minute after we
5280 started downloading them, do not consider the certificate download
5281 failure a separate failure. Fixes bug 20533; bugfix
5283 - When using exponential backoff in test networks, use a lower
5284 exponent, so the delays do not vary as much. This helps test
5285 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
5287 o Major bugfixes (exit policies):
5288 - Avoid disclosing exit outbound bind addresses, configured port
5289 bind addresses, and local interface addresses in relay descriptors
5290 by default under ExitPolicyRejectPrivate. Instead, only reject
5291 these (otherwise unlisted) addresses if
5292 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
5293 0.2.7.2-alpha. Patch by teor.
5295 o Major bugfixes (hidden services):
5296 - Allow Tor clients with appropriate controllers to work with
5297 FetchHidServDescriptors set to 0. Previously, this option also
5298 disabled descriptor cache lookup, thus breaking hidden services
5299 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
5300 - Clients now require hidden services to include the TAP keys for
5301 their intro points in the hidden service descriptor. This prevents
5302 an inadvertent upgrade to ntor, which a malicious hidden service
5303 could use to distinguish clients by consensus version. Fixes bug
5304 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
5306 o Major bugfixes (relay, resolver, logging):
5307 - For relays that don't know their own address, avoid attempting a
5308 local hostname resolve for each descriptor we download. This
5309 will cut down on the number of "Success: chose address 'x.x.x.x'"
5310 log lines, and also avoid confusing clock jumps if the resolver
5311 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
5313 o Minor features (port flags):
5314 - Add new flags to the *Port options to give finer control over which
5315 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
5316 and the synthetic flag OnionTrafficOnly, which is equivalent to
5317 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
5318 18693; patch by "teor".
5320 o Minor features (build, hardening):
5321 - Detect and work around a libclang_rt problem that would prevent
5322 clang from finding __mulodi4() on some 32-bit platforms, and thus
5323 keep -ftrapv from linking on those systems. Closes ticket 19079.
5324 - When building on a system without runtime support for the runtime
5325 hardening options, try to log a useful warning at configuration
5326 time, rather than an incomprehensible warning at link time. If
5327 expensive hardening was requested, this warning becomes an error.
5328 Closes ticket 18895.
5330 o Minor features (client, directory):
5331 - Since authorities now omit all routers that lack the Running and
5332 Valid flags, we assume that any relay listed in the consensus must
5333 have those flags. Closes ticket 20001; implements part of
5336 o Minor features (code safety):
5337 - In our integer-parsing functions, ensure that the maximum value we
5338 allow is no smaller than the minimum value. Closes ticket 19063;
5339 patch from "U+039b".
5341 o Minor features (compilation, portability):
5342 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
5345 o Minor features (config):
5346 - Warn users when descriptor and port addresses are inconsistent.
5347 Mitigates bug 13953; patch by teor.
5349 o Minor features (controller):
5350 - Allow controllers to configure basic client authorization on
5351 hidden services when they create them with the ADD_ONION controller
5352 command. Implements ticket 15588. Patch by "special".
5353 - Fire a STATUS_SERVER controller event whenever the hibernation
5354 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
5355 - Implement new GETINFO queries for all downloads that use
5356 download_status_t to schedule retries. This allows controllers to
5357 examine the schedule for pending downloads. Closes ticket 19323.
5359 o Minor features (development tools, etags):
5360 - Teach the "make tags" Makefile target how to correctly find
5361 "MOCK_IMPL" function definitions. Patch from nherring; closes
5364 o Minor features (directory authority):
5365 - After voting, if the authorities decide that a relay is not
5366 "Valid", they no longer include it in the consensus at all. Closes
5367 ticket 20002; implements part of proposal 272.
5368 - Directory authorities now only give the Guard flag to a relay if
5369 they are also giving it the Stable flag. This change allows us to
5370 simplify path selection for clients. It should have minimal effect
5371 in practice, since >99% of Guards already have the Stable flag.
5372 Implements ticket 18624.
5373 - Directory authorities now write their v3-status-votes file out to
5374 disk earlier in the consensus process, so we have a record of the
5375 votes even if we abort the consensus process. Resolves
5378 o Minor features (fallback directory list, new since 0.2.9.7-rc):
5379 - Replace the 81 remaining fallbacks of the 100 originally
5380 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5381 fallbacks (123 new, 54 existing, 27 removed) generated in December
5382 2016. Resolves ticket 20170.
5384 o Minor features (hidden service):
5385 - Stop being so strict about the payload length of "rendezvous1"
5386 cells. We used to be locked in to the "TAP" handshake length, and
5387 now we can handle better handshakes like "ntor". Resolves
5390 o Minor features (infrastructure, time):
5391 - Tor now includes an improved timer backend, so that we can
5392 efficiently support tens or hundreds of thousands of concurrent
5393 timers, as will be needed for some of our planned anti-traffic-
5394 analysis work. This code is based on William Ahern's "timeout.c"
5395 project, which implements a "tickless hierarchical timing wheel".
5396 Closes ticket 18365.
5397 - Tor now uses the operating system's monotonic timers (where
5398 available) for internal fine-grained timing. Previously we would
5399 look at the system clock, and then attempt to compensate for the
5400 clock running backwards. Closes ticket 18908.
5402 o Minor features (logging):
5403 - Add a set of macros to check nonfatal assertions, for internal
5404 use. Migrating more of our checks to these should help us avoid
5405 needless crash bugs. Closes ticket 18613.
5406 - Provide a more useful warning message when configured with an
5407 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
5408 - When dumping unparseable router descriptors, optionally store them
5409 in separate files, named by digest, up to a configurable size
5410 limit. You can change the size limit by setting the
5411 MaxUnparseableDescSizeToLog option, and disable this feature by
5412 setting that option to 0. Closes ticket 18322.
5414 o Minor features (performance):
5415 - Change the "optimistic data" extension from "off by default" to
5416 "on by default". The default was ordinarily overridden by a
5417 consensus option, but when clients were bootstrapping for the
5418 first time, they would not have a consensus to get the option
5419 from. Changing this default saves a round-trip during startup.
5420 Closes ticket 18815.
5422 o Minor features (relay, usability):
5423 - When the directory authorities refuse a bad relay's descriptor,
5424 encourage the relay operator to contact us. Many relay operators
5425 won't notice this line in their logs, but it's a win if even a few
5426 learn why we don't like what their relay was doing. Resolves
5429 o Minor features (security, TLS):
5430 - Servers no longer support clients that lack AES ciphersuites.
5431 (3DES is no longer considered an acceptable cipher.) We believe
5432 that no such Tor clients currently exist, since Tor has required
5433 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
5435 o Minor features (testing):
5436 - Disable memory protections on OpenBSD when performing our unit
5437 tests for memwipe(). The test deliberately invokes undefined
5438 behavior, and the OpenBSD protections interfere with this. Patch
5439 from "rubiate". Closes ticket 20066.
5440 - Move the test-network.sh script to chutney, and modify tor's test-
5441 network.sh to call the (newer) chutney version when available.
5442 Resolves ticket 19116. Patch by teor.
5443 - Use the lcov convention for marking lines as unreachable, so that
5444 we don't count them when we're generating test coverage data.
5445 Update our coverage tools to understand this convention. Closes
5447 - Our link-handshake unit tests now check that when invalid
5448 handshakes fail, they fail with the error messages we expected.
5449 - Our unit testing code that captures log messages no longer
5450 prevents them from being written out if the user asked for them
5451 (by passing --debug or --info or --notice or --warn to the "test"
5452 binary). This change prevents us from missing unexpected log
5453 messages simply because we were looking for others. Related to
5455 - The unit tests now log all warning messages with the "BUG" flag.
5456 Previously, they only logged errors by default. This change will
5457 help us make our testing code more correct, and make sure that we
5458 only hit this code when we mean to. In the meantime, however,
5459 there will be more warnings in the unit test logs than before.
5460 This is preparatory work for ticket 19999.
5461 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5462 assertion as a test failure.
5463 - We've done significant work to make the unit tests run faster.
5465 o Minor features (testing, ipv6):
5466 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5467 tests. Remove bridges+hs, as it's somewhat redundant. This
5468 requires a recent chutney version that supports IPv6 clients,
5469 relays, and authorities. Closes ticket 20069; patch by teor.
5470 - Add the single-onion and single-onion-ipv6 chutney targets to
5471 "make test-network-all". This requires a recent chutney version
5472 with the single onion network flavors (git c72a652 or later).
5473 Closes ticket 20072; patch by teor.
5475 o Minor features (Tor2web):
5476 - Make Tor2web clients respect ReachableAddresses. This feature was
5477 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5478 0.2.8.7. Implements feature 20034. Patch by teor.
5480 o Minor features (unix domain sockets):
5481 - When configuring a unix domain socket for a SocksPort,
5482 ControlPort, or Hidden service, you can now wrap the address in
5483 quotes, using C-style escapes inside the quotes. This allows unix
5484 domain socket paths to contain spaces. Resolves ticket 18753.
5486 o Minor features (user interface):
5487 - Tor now supports the ability to declare options deprecated, so
5488 that we can recommend that people stop using them. Previously, this
5489 was done in an ad-hoc way. There is a new --list-deprecated-options
5490 command-line option to list all of the deprecated options. Closes
5493 o Minor features (virtual addresses):
5494 - Increase the maximum number of bits for the IPv6 virtual network
5495 prefix from 16 to 104. In this way, the condition for address
5496 allocation is less restrictive. Closes ticket 20151; feature
5499 o Minor bug fixes (circuits):
5500 - Use the CircuitBuildTimeout option whenever
5501 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5502 the option when a user disabled it, but not when it was disabled
5503 because some other option was set. Fixes bug 20073; bugfix on
5504 0.2.4.12-alpha. Patch by teor.
5506 o Minor bugfixes (build):
5507 - The current Git revision when building from a local repository is
5508 now detected correctly when using git worktrees. Fixes bug 20492;
5509 bugfix on 0.2.3.9-alpha.
5511 o Minor bugfixes (relay address discovery):
5512 - Stop reordering IP addresses returned by the OS. This makes it
5513 more likely that Tor will guess the same relay IP address every
5514 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
5515 Reported by René Mayrhofer, patch by "cypherpunks".
5517 o Minor bugfixes (memory allocation):
5518 - Change how we allocate memory for large chunks on buffers, to
5519 avoid a (currently impossible) integer overflow, and to waste less
5520 space when allocating unusually large chunks. Fixes bug 20081;
5521 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5523 o Minor bugfixes (bootstrap):
5524 - Remember the directory server we fetched the consensus or previous
5525 certificates from, and use it to fetch future authority
5526 certificates. This change improves bootstrapping performance.
5527 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
5529 o Minor bugfixes (circuits):
5530 - Make sure extend_info_from_router() is only called on servers.
5531 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5533 o Minor bugfixes (client, fascistfirewall):
5534 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
5535 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
5537 o Minor bugfixes (client, unix domain sockets):
5538 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
5539 the client address is meaningless. Fixes bug 20261; bugfix
5542 o Minor bugfixes (code style):
5543 - Fix an integer signedness conversion issue in the case conversion
5544 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
5546 o Minor bugfixes (compilation):
5547 - Build correctly on versions of libevent2 without support for
5548 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
5550 - When building with Clang, use a full set of GCC warnings.
5551 (Previously, we included only a subset, because of the way we
5552 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5553 - Detect Libevent2 functions correctly on systems that provide
5554 libevent2, but where libevent1 is linked with -levent. Fixes bug
5555 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
5556 - Run correctly when built on Windows build environments that
5557 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
5559 o Minor bugfixes (configuration):
5560 - When parsing quoted configuration values from the torrc file,
5561 handle Windows line endings correctly. Fixes bug 19167; bugfix on
5562 0.2.0.16-alpha. Patch from "Pingl".
5564 o Minor bugfixes (directory authority):
5565 - Authorities now sort the "package" lines in their votes, for ease
5566 of debugging. (They are already sorted in consensus documents.)
5567 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5568 - Die with a more useful error when the operator forgets to place
5569 the authority_signing_key file into the keys directory. This
5570 avoids an uninformative assert & traceback about having an invalid
5571 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5572 - When allowing private addresses, mark Exits that only exit to
5573 private locations as such. Fixes bug 20064; bugfix
5575 - When parsing a detached signature, make sure we use the length of
5576 the digest algorithm instead of a hardcoded DIGEST256_LEN in
5577 order to avoid comparing bytes out-of-bounds with a smaller digest
5578 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5580 o Minor bugfixes (getpass):
5581 - Defensively fix a non-triggerable heap corruption at do_getpass()
5582 to protect ourselves from mistakes in the future. Fixes bug
5583 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
5586 o Minor bugfixes (guard selection):
5587 - Don't mark guards as unreachable if connection_connect() fails.
5588 That function fails for local reasons, so it shouldn't reveal
5589 anything about the status of the guard. Fixes bug 14334; bugfix
5591 - Use a single entry guard even if the NumEntryGuards consensus
5592 parameter is not provided. Fixes bug 17688; bugfix
5595 o Minor bugfixes (hidden services):
5596 - Increase the minimum number of internal circuits we preemptively
5597 build from 2 to 3, so a circuit is available when a client
5598 connects to another onion service. Fixes bug 13239; bugfix
5600 - Allow hidden services to run on IPv6 addresses even when the
5601 IPv6Exit option is not set. Fixes bug 18357; bugfix
5603 - Stop logging intro point details to the client log on certain
5604 error conditions. Fixed as part of bug 20012; bugfix on
5605 0.2.4.8-alpha. Patch by teor.
5606 - When deleting an ephemeral hidden service, close its intro points
5607 even if they are not completely open. Fixes bug 18604; bugfix
5609 - When configuring hidden services, check every hidden service
5610 directory's permissions. Previously, we only checked the last
5611 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
5613 o Minor bugfixes (IPv6, testing):
5614 - Check for IPv6 correctly on Linux when running test networks.
5615 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5617 o Minor bugfixes (Linux seccomp2 sandbox):
5618 - Add permission to run the sched_yield() and sigaltstack() system
5619 calls, in order to support versions of Tor compiled with asan or
5620 ubsan code that use these calls. Now "sandbox 1" and
5621 "--enable-expensive-hardening" should be compatible on more
5622 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5624 o Minor bugfixes (logging):
5625 - Downgrade a harmless log message about the
5626 pending_entry_connections list from "warn" to "info". Mitigates
5628 - Log a more accurate message when we fail to dump a microdescriptor.
5629 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
5630 - When logging a directory ownership mismatch, log the owning
5631 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5632 - When we are unable to remove the bw_accounting file, do not warn
5633 if the reason we couldn't remove it was that it didn't exist.
5634 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
5636 o Minor bugfixes (memory leak):
5637 - Fix a series of slow memory leaks related to parsing torrc files
5638 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
5639 - Avoid a small memory leak when informing worker threads about
5640 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
5641 - Fix a small memory leak when receiving AF_UNIX connections on a
5642 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
5643 - When moving a signed descriptor object from a source to an
5644 existing destination, free the allocated memory inside that
5645 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
5646 - Fix a memory leak and use-after-free error when removing entries
5647 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
5648 0.2.5.5-alpha. Patch from "cypherpunks".
5649 - Fix a small, uncommon memory leak that could occur when reading a
5650 truncated ed25519 key file. Fixes bug 18956; bugfix
5653 o Minor bugfixes (option parsing):
5654 - Count unix sockets when counting client listeners (SOCKS, Trans,
5655 NATD, and DNS). This has no user-visible behavior changes: these
5656 options are set once, and never read. Required for correct
5657 behavior in ticket 17178. Fixes bug 19677; bugfix on
5658 0.2.6.3-alpha. Patch by teor.
5660 o Minor bugfixes (options):
5661 - Check the consistency of UseEntryGuards and EntryNodes more
5662 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
5664 - Stop changing the configured value of UseEntryGuards on
5665 authorities and Tor2web clients. Fixes bug 20074; bugfix on
5666 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
5669 o Minor bugfixes (relay):
5670 - Ensure relays don't make multiple connections during bootstrap.
5671 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
5672 - Do not try to parallelize workers more than 16x without the user
5673 explicitly configuring us to do so, even if we do detect more than
5674 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5676 o Minor bugfixes (testing):
5677 - The test-stem and test-network makefile targets now depend only on
5678 the tor binary that they are testing. Previously, they depended on
5679 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
5680 patch from "cypherpunks".
5681 - Allow clients to retry HSDirs much faster in test networks. Fixes
5682 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5683 - Avoid a unit test failure on systems with over 16 detectable CPU
5684 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5685 - Let backtrace tests work correctly under AddressSanitizer:
5686 disable ASAN's detection of segmentation faults while running
5687 test_bt.sh, so that we can make sure that our own backtrace
5688 generation code works. Fixes bug 18934; bugfix
5689 on 0.2.5.2-alpha. Patch from "cypherpunks".
5690 - Fix the test-network-all target on out-of-tree builds by using the
5691 correct path to the test driver script. Fixes bug 19421; bugfix
5693 - Stop spurious failures in the local interface address discovery
5694 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
5696 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
5697 removed the ECDH ciphers which caused the tests to fail on
5698 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
5699 - The tor_tls_server_info_callback unit test no longer crashes when
5700 debug-level logging is turned on. Fixes bug 20041; bugfix
5703 o Minor bugfixes (time):
5704 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5705 bugfix on all released tor versions.
5706 - When computing the difference between two times in milliseconds,
5707 we now round to the nearest millisecond correctly. Previously, we
5708 could sometimes round in the wrong direction. Fixes bug 19428;
5709 bugfix on 0.2.2.2-alpha.
5711 o Minor bugfixes (Tor2web):
5712 - Prevent Tor2web clients from running hidden services: these services
5713 are not anonymous due to the one-hop client paths. Fixes bug
5714 19678. Patch by teor.
5716 o Minor bugfixes (user interface):
5717 - Display a more accurate number of suppressed messages in the log
5718 rate-limiter. Previously, there was a potential integer overflow
5719 in the counter. Now, if the number of messages hits a maximum, the
5720 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5722 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5723 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5725 o Code simplification and refactoring:
5726 - Remove redundant declarations of the MIN macro. Closes
5728 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5729 Closes ticket 18462; patch from "icanhasaccount".
5730 - Split the 600-line directory_handle_command_get function into
5731 separate functions for different URL types. Closes ticket 16698.
5734 - Add module-level internal documentation for 36 C files that
5735 previously didn't have a high-level overview. Closes ticket 20385.
5736 - Correct the IPv6 syntax in our documentation for the
5737 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
5738 - Correct the minimum bandwidth value in torrc.sample, and queue a
5739 corresponding change for torrc.minimal. Closes ticket 20085.
5740 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5741 ticket 19153. Patch from "U+039b".
5742 - Module-level documentation for several more modules. Closes
5743 tickets 19287 and 19290.
5744 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5745 19504; bugfix on 0.2.7.3-rc.
5746 - Document the default PathsNeededToBuildCircuits value that's used
5747 by clients when the directory authorities don't set
5748 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
5749 Patch by teor, reported by Jesse V.
5750 - Fix manual for the User option: it takes a username, not a UID.
5751 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5753 - Fix the description of the --passphrase-fd option in the
5754 tor-gencert manpage. The option is used to pass the number of a
5755 file descriptor to read the passphrase from, not to read the file
5756 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5759 - We no longer include the (dead, deprecated) bufferevent code in
5760 Tor. Closes ticket 19450. Based on a patch from "U+039b".
5763 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5764 "GETINFO dir-usage" controller request, which were only available
5765 via a compile-time option in Tor anyway. Feature was added in
5766 0.2.2.1-alpha. Resolves ticket 19035.
5767 - There is no longer a compile-time option to disable support for
5768 TransPort. (If you don't want TransPort, just don't use it.) Patch
5769 from "U+039b". Closes ticket 19449.
5772 - Run more workqueue tests as part of "make check". These had
5773 previously been implemented, but you needed to know special
5774 command-line options to enable them.
5775 - We now have unit tests for our code to reject zlib "compression
5776 bombs". (Fortunately, the code works fine.)
5779 Changes in version 0.2.8.11 - 2016-12-08
5780 Tor 0.2.8.11 backports fixes for additional portability issues that
5781 could prevent Tor from building correctly on OSX Sierra, or with
5782 OpenSSL 1.1. Affected users should upgrade; others can safely stay
5785 o Minor bugfixes (portability):
5786 - Avoid compilation errors when building on OSX Sierra. Sierra began
5787 to support the getentropy() and clock_gettime() APIs, but created
5788 a few problems in doing so. Tor 0.2.9 has a more thorough set of
5789 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
5790 monotonic time interfaces. Fixes bug 20865. Bugfix
5793 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5794 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
5795 architectures. Closes ticket 20588.
5798 Changes in version 0.2.8.10 - 2016-12-02
5799 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
5800 unusable after they left standby mode. It also backports fixes for
5801 a few portability issues and a small but problematic memory leak.
5803 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
5804 - When Tor leaves standby because of a new application request, open
5805 circuits as needed to serve that request. Previously, we would
5806 potentially wait a very long time. Fixes part of bug 19969; bugfix
5809 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
5810 - Clients now respond to new application stream requests immediately
5811 when they arrive, rather than waiting up to one second before
5812 starting to handle them. Fixes part of bug 19969; bugfix
5815 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
5816 - Work around a bug in the OSX 10.12 SDK that would prevent us from
5817 successfully targeting earlier versions of OSX. Resolves
5820 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5821 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
5822 20551; bugfix on 0.2.1.1-alpha.
5824 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
5825 - Work around a memory leak in OpenSSL 1.1 when encoding public
5826 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
5828 o Minor features (geoip):
5829 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
5833 Changes in version 0.2.8.9 - 2016-10-17
5834 Tor 0.2.8.9 backports a fix for a security hole in previous versions
5835 of Tor that would allow a remote attacker to crash a Tor client,
5836 hidden service, relay, or authority. All Tor users should upgrade to
5837 this version, or to 0.2.9.4-alpha. Patches will be released for older
5840 o Major features (security fixes, also in 0.2.9.4-alpha):
5841 - Prevent a class of security bugs caused by treating the contents
5842 of a buffer chunk as if they were a NUL-terminated string. At
5843 least one such bug seems to be present in all currently used
5844 versions of Tor, and would allow an attacker to remotely crash
5845 most Tor instances, especially those compiled with extra compiler
5846 hardening. With this defense in place, such bugs can't crash Tor,
5847 though we should still fix them as they occur. Closes ticket
5848 20384 (TROVE-2016-10-001).
5850 o Minor features (geoip):
5851 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
5855 Changes in version 0.2.8.8 - 2016-09-23
5856 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
5857 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
5858 who select public relays as their bridges.
5860 o Major bugfixes (crash):
5861 - Fix a complicated crash bug that could affect Tor clients
5862 configured to use bridges when replacing a networkstatus consensus
5863 in which one of their bridges was mentioned. OpenBSD users saw
5864 more crashes here, but all platforms were potentially affected.
5865 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5867 o Major bugfixes (relay, OOM handler):
5868 - Fix a timing-dependent assertion failure that could occur when we
5869 tried to flush from a circuit after having freed its cells because
5870 of an out-of-memory condition. Fixes bug 20203; bugfix on
5871 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5874 o Minor feature (fallback directories):
5875 - Remove broken fallbacks from the hard-coded fallback directory
5876 list. Closes ticket 20190; patch by teor.
5878 o Minor features (geoip):
5879 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5883 Changes in version 0.2.8.7 - 2016-08-24
5884 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
5885 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
5886 who sets the ReachableAddresses option, and all bridges, are strongly
5887 encouraged to upgrade.
5889 o Directory authority changes:
5890 - The "Tonga" bridge authority has been retired; the new bridge
5891 authority is "Bifroest". Closes tickets 19728 and 19690.
5893 o Major bugfixes (client, security):
5894 - Only use the ReachableAddresses option to restrict the first hop
5895 in a path. In earlier versions of 0.2.8.x, it would apply to
5896 every hop in the path, with a possible degradation in anonymity
5897 for anyone using an uncommon ReachableAddress setting. Fixes bug
5898 19973; bugfix on 0.2.8.2-alpha.
5900 o Minor features (geoip):
5901 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5904 o Minor bugfixes (compilation):
5905 - Remove an inappropriate "inline" in tortls.c that was causing
5906 warnings on older versions of GCC. Fixes bug 19903; bugfix
5909 o Minor bugfixes (fallback directories):
5910 - Avoid logging a NULL string pointer when loading fallback
5911 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5912 and 0.2.8.1-alpha. Report and patch by "rubiate".
5915 Changes in version 0.2.8.6 - 2016-08-02
5917 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5919 The Tor 0.2.8 series improves client bootstrapping performance,
5920 completes the authority-side implementation of improved identity
5921 keys for relays, and includes numerous bugfixes and performance
5922 improvements throughout the program. This release continues to
5923 improve the coverage of Tor's test suite. For a full list of
5924 changes since Tor 0.2.7, see the ReleaseNotes file.
5926 Below is a list of the changes since Tor 0.2.7.
5928 o New system requirements:
5929 - Tor no longer attempts to support platforms where the "time_t"
5930 type is unsigned. (To the best of our knowledge, only OpenVMS does
5931 this, and Tor has never actually built on OpenVMS.) Closes
5933 - Tor no longer supports versions of OpenSSL with a broken
5934 implementation of counter mode. (This bug was present in OpenSSL
5935 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
5936 longer runs with, these versions.
5937 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
5938 later (released in 2008 and 2009 respectively). If you are
5939 building Tor from the git repository instead of from the source
5940 distribution, and your tools are older than this, you will need to
5941 upgrade. Closes ticket 17732.
5943 o Directory authority changes:
5944 - Update the V3 identity key for the dannenberg directory authority:
5945 it was changed on 18 November 2015. Closes task 17906. Patch
5947 - Urras is no longer a directory authority. Closes ticket 19271.
5949 o Major features (directory system):
5950 - Include a trial list of default fallback directories, based on an
5951 opt-in survey of suitable relays. Doing this should make clients
5952 bootstrap more quickly and reliably, and reduce the load on the
5953 directory authorities. Closes ticket 15775. Patch by teor.
5954 Candidates identified using an OnionOO script by weasel, teor,
5955 gsathya, and karsten.
5956 - Previously only relays that explicitly opened a directory port
5957 (DirPort) accepted directory requests from clients. Now all
5958 relays, with and without a DirPort, accept and serve tunneled
5959 directory requests that they receive through their ORPort. You can
5960 disable this behavior using the new DirCache option. Closes
5962 - When bootstrapping multiple consensus downloads at a time, use the
5963 first one that starts downloading, and close the rest. This
5964 reduces failures when authorities or fallback directories are slow
5965 or down. Together with the code for feature 15775, this feature
5966 should reduces failures due to fallback churn. Implements ticket
5967 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
5970 o Major features (security, Linux):
5971 - When Tor starts as root on Linux and is told to switch user ID, it
5972 can now retain the capability to bind to low ports. By default,
5973 Tor will do this only when it's switching user ID and some low
5974 ports have been configured. You can change this behavior with the
5975 new option KeepBindCapabilities. Closes ticket 8195.
5977 o Major bugfixes (client, bootstrapping):
5978 - Check if bootstrap consensus downloads are still needed when the
5979 linked connection attaches. This prevents tor making unnecessary
5980 begindir-style connections, which are the only directory
5981 connections tor clients make since the fix for 18483 was merged.
5982 - Fix some edge cases where consensus download connections may not
5983 have been closed, even though they were not needed. Related to fix
5985 - Make relays retry consensus downloads the correct number of times,
5986 rather than the more aggressive client retry count. Fixes part of
5989 o Major bugfixes (dns proxy mode, crash):
5990 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5991 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5993 o Major bugfixes (ed25519, voting):
5994 - Actually enable support for authorities to match routers by their
5995 Ed25519 identities. Previously, the code had been written, but
5996 some debugging code that had accidentally been left in the
5997 codebase made it stay turned off. Fixes bug 17702; bugfix
5999 - When collating votes by Ed25519 identities, authorities now
6000 include a "NoEdConsensus" flag if the ed25519 value (or lack
6001 thereof) for a server does not reflect the majority consensus.
6002 Related to bug 17668; bugfix on 0.2.7.2-alpha.
6003 - When generating a vote with keypinning disabled, never include two
6004 entries for the same ed25519 identity. This bug was causing
6005 authorities to generate votes that they could not parse when a
6006 router violated key pinning by changing its RSA identity but
6007 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
6008 18318. Bugfix on 0.2.7.2-alpha.
6010 o Major bugfixes (key management):
6011 - If OpenSSL fails to generate an RSA key, do not retain a dangling
6012 pointer to the previous (uninitialized) key value. The impact here
6013 should be limited to a difficult-to-trigger crash, if OpenSSL is
6014 running an engine that makes key generation failures possible, or
6015 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
6016 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
6019 o Major bugfixes (security, client, DNS proxy):
6020 - Stop a crash that could occur when a client running with DNSPort
6021 received a query with multiple address types, and the first
6022 address type was not supported. Found and fixed by Scott Dial.
6023 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
6025 o Major bugfixes (security, compilation):
6026 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
6027 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
6028 cause a compiler warning, thereby making other checks fail, and
6029 needlessly disabling compiler-hardening support. Fixes one case of
6030 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
6031 - Repair hardened builds under the clang compiler. Previously, our
6032 use of _FORTIFY_SOURCE would conflict with clang's address
6033 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
6035 o Major bugfixes (security, pointers):
6036 - Avoid a difficult-to-trigger heap corruption attack when extending
6037 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6038 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6039 Reported by Guido Vranken.
6041 o Major bugfixes (testing):
6042 - Fix a bug that would block 'make test-network-all' on systems where
6043 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
6045 o Major bugfixes (user interface):
6046 - Correctly give a warning in the cases where a relay is specified
6047 by nickname, and one such relay is found, but it is not officially
6048 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
6050 o Minor features (accounting):
6051 - Added two modes to the AccountingRule option: One for limiting
6052 only the number of bytes sent ("AccountingRule out"), and one for
6053 limiting only the number of bytes received ("AccountingRule in").
6054 Closes ticket 15989; patch from "unixninja92".
6056 o Minor features (bug-resistance):
6057 - Make Tor survive errors involving connections without a
6058 corresponding event object. Previously we'd fail with an
6059 assertion; now we produce a log message. Related to bug 16248.
6060 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6061 level code, to harden against accidental failures to NUL-
6062 terminate. Part of ticket 17852. Patch from jsturgix. Found
6065 o Minor features (build):
6066 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
6067 as having possible IPFW support. Closes ticket 18448. Patch from
6069 - Since our build process now uses "make distcheck", we no longer
6070 force "make dist" to depend on "make check". Closes ticket 17893;
6071 patch from "cypherpunks".
6072 - Tor now builds once again with the recent OpenSSL 1.1 development
6073 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
6074 tracking OpenSSL 1.1 development as it has progressed, and fixing
6075 numerous compatibility issues as they arose. See tickets
6076 17549, 17921, 17984, 19499, and 18286.
6077 - When building manual pages, set the timezone to "UTC", so that the
6078 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
6079 Patch from intrigeri.
6081 o Minor features (clients):
6082 - Make clients, onion services, and bridge relays always use an
6083 encrypted begindir connection for directory requests. Resolves
6084 ticket 18483. Patch by teor.
6086 o Minor features (controller):
6087 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
6088 controllers can examine the the reject rules added by
6089 ExitPolicyRejectPrivate. This makes it easier for stem to display
6091 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
6092 tickets 16774 and 17817. Patch by George Tankersley.
6093 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
6094 service descriptor from a service's local hidden service
6095 descriptor cache. Closes ticket 14846.
6097 o Minor features (crypto):
6098 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
6099 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
6101 - Improve performance when hashing non-multiple of 8 sized buffers,
6102 based on Andrew Moon's public domain SipHash-2-4 implementation.
6103 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
6104 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6105 p is a safe prime, and g is a suitable generator. Closes
6107 - When allocating a digest state object, allocate no more space than
6108 we actually need. Previously, we would allocate as much space as
6109 the state for the largest algorithm would need. This change saves
6110 up to 672 bytes per circuit. Closes ticket 17796.
6112 o Minor features (directory downloads):
6113 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
6114 directory mirrors. The default is 1; set it to 0 to disable
6115 fallbacks. Implements ticket 17576. Patch by teor.
6116 - Wait for busy authorities and fallback directories to become non-
6117 busy when bootstrapping. (A similar change was made in 6c443e987d
6118 for directory caches chosen from the consensus.) Closes ticket
6119 17864; patch by teor.
6121 o Minor features (geoip):
6122 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
6125 o Minor features (hidden service directory):
6126 - Streamline relay-side hsdir handling: when relays consider whether
6127 to accept an uploaded hidden service descriptor, they no longer
6128 check whether they are one of the relays in the network that is
6129 "supposed" to handle that descriptor. Implements ticket 18332.
6131 o Minor features (IPv6):
6132 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
6133 to 1, tor prefers IPv6 directory addresses.
6134 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
6135 avoids using IPv4 for client OR and directory connections.
6136 - Add address policy assume_action support for IPv6 addresses.
6137 - Add an argument 'ipv6=address:orport' to the DirAuthority and
6138 FallbackDir torrc options, to specify an IPv6 address for an
6139 authority or fallback directory. Add hard-coded ipv6 addresses for
6140 directory authorities that have them. Closes ticket 17327; patch
6141 from Nick Mathewson and teor.
6142 - Allow users to configure directory authorities and fallback
6143 directory servers with IPv6 addresses and ORPorts. Resolves
6145 - Limit IPv6 mask bits to 128.
6146 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
6147 17638; bugfix on 0.0.2pre8. Patch by teor.
6148 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
6149 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
6150 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
6151 - Warn when comparing against an AF_UNSPEC address in a policy, it's
6152 almost always a bug. Closes ticket 17863; patch by teor.
6153 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
6154 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
6156 o Minor features (Linux seccomp2 sandbox):
6157 - Reject attempts to change our Address with "Sandbox 1" enabled.
6158 Changing Address with Sandbox turned on would never actually work,
6159 but previously it would fail in strange and confusing ways. Found
6162 o Minor features (logging):
6163 - When logging to syslog, allow a tag to be added to the syslog
6164 identity (the string prepended to every log message). The tag can
6165 be configured with SyslogIdentityTag and defaults to none. Setting
6166 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
6169 o Minor features (portability):
6170 - Use timingsafe_memcmp() where available. Closes ticket 17944;
6171 patch from <logan@hackers.mu>.
6173 o Minor features (relay, address discovery):
6174 - Add a family argument to get_interface_addresses_raw() and
6175 subfunctions to make network interface address interogation more
6176 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
6177 types of interfaces from the operating system. Resolves
6179 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
6180 fails to enumerate interface addresses using the platform-specific
6181 API, have it rely on the UDP socket fallback technique to try and
6182 find out what IP addresses (both IPv4 and IPv6) our machine has.
6183 Resolves ticket 17951.
6185 o Minor features (replay cache):
6186 - The replay cache now uses SHA256 instead of SHA1. Implements
6187 feature 8961. Patch by teor, issue reported by rransom.
6189 o Minor features (robustness):
6190 - Exit immediately with an error message if the code attempts to use
6191 Libevent without having initialized it. This should resolve some
6192 frequently-made mistakes in our unit tests. Closes ticket 18241.
6194 o Minor features (security, clock):
6195 - Warn when the system clock appears to move back in time (when the
6196 state file was last written in the future). Tor doesn't know that
6197 consensuses have expired if the clock is in the past. Patch by
6198 teor. Implements ticket 17188.
6200 o Minor features (security, exit policies):
6201 - ExitPolicyRejectPrivate now rejects more private addresses by
6202 default. Specifically, it now rejects the relay's outbound bind
6203 addresses (if configured), and the relay's configured port
6204 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
6205 0.2.0.11-alpha. Patch by teor.
6207 o Minor features (security, memory erasure):
6208 - Make memwipe() do nothing when passed a NULL pointer or buffer of
6209 zero size. Check size argument to memwipe() for underflow. Fixes
6210 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
6212 - Set the unused entries in a smartlist to NULL. This helped catch
6213 a (harmless) bug, and shouldn't affect performance too much.
6214 Implements ticket 17026.
6215 - Use SecureMemoryWipe() function to securely clean memory on
6216 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
6217 Implements feature 17986.
6218 - Use explicit_bzero or memset_s when present. Previously, we'd use
6219 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
6220 from <logan@hackers.mu> and <selven@hackers.mu>.
6222 o Minor features (security, RNG):
6223 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
6224 positively are not allowed to fail. Previously we depended on
6225 internal details of OpenSSL's behavior. Closes ticket 17686.
6226 - Never use the system entropy output directly for anything besides
6227 seeding the PRNG. When we want to generate important keys, instead
6228 of using system entropy directly, we now hash it with the PRNG
6229 stream. This may help resist certain attacks based on broken OS
6230 entropy implementations. Closes part of ticket 17694.
6231 - Use modern system calls (like getentropy() or getrandom()) to
6232 generate strong entropy on platforms that have them. Closes
6235 o Minor features (security, win32):
6236 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
6237 attack. Fixes bug 18123; bugfix on all tor versions. Patch
6240 o Minor features (unix domain sockets):
6241 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
6242 Unix domain sockets without checking the permissions on the parent
6243 directory. (Tor checks permissions by default because some
6244 operating systems only check permissions on the parent directory.
6245 However, some operating systems do look at permissions on the
6246 socket, and tor's default check is unneeded.) Closes ticket 18458.
6249 o Minor features (unix file permissions):
6250 - Defer creation of Unix sockets until after setuid. This avoids
6251 needing CAP_CHOWN and CAP_FOWNER when using systemd's
6252 CapabilityBoundingSet, or chown and fowner when using SELinux.
6253 Implements part of ticket 17562. Patch from Jamie Nguyen.
6254 - If any directory created by Tor is marked as group readable, the
6255 filesystem group is allowed to be either the default GID or the
6256 root user. Allowing root to read the DataDirectory prevents the
6257 need for CAP_READ_SEARCH when using systemd's
6258 CapabilityBoundingSet, or dac_read_search when using SELinux.
6259 Implements part of ticket 17562. Patch from Jamie Nguyen.
6260 - Introduce a new DataDirectoryGroupReadable option. If it is set to
6261 1, the DataDirectory will be made readable by the default GID.
6262 Implements part of ticket 17562. Patch from Jamie Nguyen.
6264 o Minor bugfixes (accounting):
6265 - The max bandwidth when using 'AccountRule sum' is now correctly
6266 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
6269 o Minor bugfixes (assert, portability):
6270 - Fix an assertion failure in memarea.c on systems where "long" is
6271 shorter than the size of a pointer. Fixes bug 18716; bugfix
6274 o Minor bugfixes (bootstrap):
6275 - Consistently use the consensus download schedule for authority
6276 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
6278 o Minor bugfixes (build):
6279 - Avoid spurious failures from configure files related to calling
6280 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
6281 0.2.0.1-alpha. Patch from "cypherpunks".
6282 - Do not link the unit tests against both the testing and non-
6283 testing versions of the static libraries. Fixes bug 18490; bugfix
6285 - Resolve warnings when building on systems that are concerned with
6286 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
6288 - Silence spurious clang-scan warnings in the ed25519_donna code by
6289 explicitly initializing some objects. Fixes bug 18384; bugfix on
6290 0.2.7.2-alpha. Patch by teor.
6291 - When libscrypt.h is found, but no libscrypt library can be linked,
6292 treat libscrypt as absent. Fixes bug 19161; bugfix
6294 - Cause the unit tests to compile correctly on mingw64 versions that
6295 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
6296 - Don't try to use the pthread_condattr_setclock() function unless
6297 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
6298 17819; bugfix on 0.2.6.3-alpha.
6299 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
6301 - Fix search for libevent libraries on OpenBSD (and other systems
6302 that install libevent 1 and libevent 2 in parallel). Fixes bug
6303 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
6304 - Isolate environment variables meant for tests from the rest of the
6305 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
6306 - Mark all object files that include micro-revision.i as depending
6307 on it, so as to make parallel builds more reliable. Fixes bug
6308 17826; bugfix on 0.2.5.1-alpha.
6309 - Remove config.log only from make distclean, not from make clean.
6310 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
6311 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
6313 - Remove an #endif from configure.ac so that we correctly detect the
6314 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
6317 o Minor bugfixes (client, bootstrap):
6318 - Count receipt of new microdescriptors as progress towards
6319 bootstrapping. Previously, with EntryNodes set, Tor might not
6320 successfully repopulate the guard set on bootstrapping. Fixes bug
6321 16825; bugfix on 0.2.3.1-alpha.
6323 o Minor bugfixes (code correctness):
6324 - Fix a bad memory handling bug that would occur if we had queued a
6325 cell on a channel's incoming queue. Fortunately, we can't actually
6326 queue a cell like that as our code is constructed today, but it's
6327 best to avoid this kind of error, even if there isn't any code
6328 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
6329 - Assert that allocated memory held by the reputation code is freed
6330 according to its internal counters. Fixes bug 17753; bugfix
6332 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
6334 - Update to the latest version of Trunnel, which tries harder to
6335 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
6336 by clang address sanitizer. Fixes bug 18373; bugfix
6338 - When closing an entry connection, generate a warning if we should
6339 have sent an end cell for it but we haven't. Fixes bug 17876;
6340 bugfix on 0.2.3.2-alpha.
6342 o Minor bugfixes (configuration):
6343 - Fix a tiny memory leak when parsing a port configuration ending in
6344 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
6346 o Minor bugfixes (containers):
6347 - If we somehow attempt to construct a heap with more than
6348 1073741822 elements, avoid an integer overflow when maintaining
6349 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
6351 o Minor bugfixes (controller, microdescriptors):
6352 - Make GETINFO dir/status-vote/current/consensus conform to the
6353 control specification by returning "551 Could not open cached
6354 consensus..." when not caching consensuses. Fixes bug 18920;
6355 bugfix on 0.2.2.6-alpha.
6357 o Minor bugfixes (crypto):
6358 - Check the return value of HMAC() and assert on failure. Fixes bug
6359 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
6361 o Minor bugfixes (directories):
6362 - When fetching extrainfo documents, compare their SHA256 digests
6363 and Ed25519 signing key certificates with the routerinfo that led
6364 us to fetch them, rather than with the most recent routerinfo.
6365 Otherwise we generate many spurious warnings about mismatches.
6366 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
6367 - When generating a URL for a directory server on an IPv6 address,
6368 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
6369 on 0.2.3.9-alpha. Patch from Malek.
6371 o Minor bugfixes (downloading):
6372 - Predict more correctly whether we'll be downloading over HTTP when
6373 we determine the maximum length of a URL. This should avoid a
6374 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
6377 o Minor bugfixes (exit policies, security):
6378 - Refresh an exit relay's exit policy when interface addresses
6379 change. Previously, tor only refreshed the exit policy when the
6380 configured external address changed. Fixes bug 18208; bugfix on
6381 0.2.7.3-rc. Patch by teor.
6383 o Minor bugfixes (fallback directories):
6384 - Mark fallbacks as "too busy" when they return a 503 response,
6385 rather than just marking authorities. Fixes bug 17572; bugfix on
6386 0.2.4.7-alpha. Patch by teor.
6387 - When requesting extrainfo descriptors from a trusted directory
6388 server, check whether it is an authority or a fallback directory
6389 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
6390 0.2.4.7-alpha. Reported by atagar, patch by teor.
6392 o Minor bugfixes (hidden service, client):
6393 - Handle the case where the user makes several fast consecutive
6394 requests to the same .onion address. Previously, the first six
6395 requests would each trigger a descriptor fetch, each picking a
6396 directory (there are 6 overall) and the seventh one would fail
6397 because no directories were left, thereby triggering a close on
6398 all current directory connections asking for the hidden service.
6399 The solution here is to not close the connections if we have
6400 pending directory fetches. Fixes bug 15937; bugfix
6403 o Minor bugfixes (hidden service, control port):
6404 - Add the onion address to the HS_DESC event for the UPLOADED action
6405 both on success or failure. It was previously hardcoded with
6406 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
6408 o Minor bugfixes (hidden service, directory):
6409 - Bridges now refuse "rendezvous2" (hidden service descriptor)
6410 publish attempts. Suggested by ticket 18332.
6412 o Minor bugfixes (IPv6):
6413 - Update the limits in max_dl_per_request for IPv6 address length.
6414 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
6416 o Minor bugfixes (Linux seccomp2 sandbox):
6417 - Allow more syscalls when running with "Sandbox 1" enabled:
6418 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
6419 some systems, these are required for Tor to start. Fixes bug
6420 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
6421 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
6422 so that get_interface_address6_via_udp_socket_hack() can work.
6423 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
6424 - Allow the setrlimit syscall, and the prlimit and prlimit64
6425 syscalls, which some libc implementations use under the hood.
6426 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
6427 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
6428 enabled and no DNS resolvers configured. This should help TAILS
6429 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
6430 - Fix a crash when using offline master ed25519 keys with the Linux
6431 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
6432 - Allow statistics to be written to disk when "Sandbox 1" is
6433 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
6434 0.2.6.1-alpha respectively.
6436 o Minor bugfixes (logging):
6437 - In log messages that include a function name, use __FUNCTION__
6438 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
6439 with clang __PRETTY_FUNCTION__ has extra information we don't
6440 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
6442 - Remove needless quotes from a log message about unparseable
6443 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
6444 - Scrub service name in "unrecognized service ID" log messages.
6445 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
6446 - When logging information about an unparsable networkstatus vote or
6447 consensus, do not say "vote" when we mean consensus. Fixes bug
6448 18368; bugfix on 0.2.0.8-alpha.
6449 - When we can't generate a signing key because OfflineMasterKey is
6450 set, do not imply that we should have been able to load it. Fixes
6451 bug 18133; bugfix on 0.2.7.2-alpha.
6452 - When logging a malformed hostname received through socks4, scrub
6453 it if SafeLogging says we should. Fixes bug 17419; bugfix
6456 o Minor bugfixes (memory safety):
6457 - Avoid freeing an uninitialized pointer when opening a socket fails
6458 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
6459 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
6461 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
6462 18672; bugfix on 0.2.5.1-alpha.
6463 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
6466 o Minor bugfixes (pluggable transports):
6467 - Avoid reporting a spurious error when we decide that we don't need
6468 to terminate a pluggable transport because it has already exited.
6469 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
6471 o Minor bugfixes (pointer arithmetic):
6472 - Fix a bug in memarea_alloc() that could have resulted in remote
6473 heap write access, if Tor had ever passed an unchecked size to
6474 memarea_alloc(). Fortunately, all the sizes we pass to
6475 memarea_alloc() are pre-checked to be less than 128 kilobytes.
6476 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
6479 o Minor bugfixes (private directory):
6480 - Prevent a race condition when creating private directories. Fixes
6481 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
6482 Patch from jsturgix. Found with Flawfinder.
6484 o Minor bugfixes (relays):
6485 - Check that both the ORPort and DirPort (if present) are reachable
6486 before publishing a relay descriptor. Otherwise, relays publish a
6487 descriptor with DirPort 0 when the DirPort reachability test takes
6488 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6489 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
6490 - Resolve some edge cases where we might launch an ORPort
6491 reachability check even when DisableNetwork is set. Noticed while
6492 fixing bug 18616; bugfix on 0.2.3.9-alpha.
6494 o Minor bugfixes (relays, hidden services):
6495 - Refuse connection requests to private OR addresses unless
6496 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6497 then refuse to send any cells to a private address. Fixes bugs
6498 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
6500 o Minor bugfixes (security, hidden services):
6501 - Prevent hidden services connecting to client-supplied rendezvous
6502 addresses that are reserved as internal or multicast. Fixes bug
6503 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6505 o Minor bugfixes (statistics):
6506 - Consistently check for overflow in round_*_to_next_multiple_of
6507 functions, and add unit tests with additional and maximal values.
6508 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6509 - Handle edge cases in the laplace functions: avoid division by
6510 zero, avoid taking the log of zero, and silence clang type
6511 conversion warnings using round and trunc. Add unit tests for edge
6512 cases with maximal values. Fixes part of bug 13192; bugfix
6514 - We now include consensus downloads via IPv6 in our directory-
6515 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
6517 o Minor bugfixes (test networks, IPv6):
6518 - Allow internal IPv6 addresses in descriptors in test networks.
6519 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
6522 o Minor bugfixes (testing):
6523 - Check the full results of SHA256 and SHA512 digests in the unit
6524 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
6525 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6527 - Fix a small memory leak that would occur when the
6528 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
6529 bugfix on 0.2.5.2-alpha.
6530 - Make unit tests pass on IPv6-only systems, and systems without
6531 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6532 bugfix on 0.2.7.3-rc. Patch by teor.
6533 - The test for log_heartbeat was incorrectly failing in timezones
6534 with non-integer offsets. Instead of comparing the end of the time
6535 string against a constant, compare it to the output of
6536 format_local_iso_time when given the correct input. Fixes bug
6537 18039; bugfix on 0.2.5.4-alpha.
6538 - We no longer disable assertions in the unit tests when coverage is
6539 enabled. Instead, we require you to say --disable-asserts-in-tests
6540 to the configure script if you need assertions disabled in the
6541 unit tests (for example, if you want to perform branch coverage).
6542 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
6544 o Minor bugfixes (time handling):
6545 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
6546 field. Otherwise, our unit tests crash on Windows. Fixes bug
6547 18977; bugfix on 0.2.2.25-alpha.
6548 - Avoid overflow in tor_timegm when parsing dates in and after 2038
6549 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
6550 0.0.2pre14. Patch by teor.
6552 o Minor bugfixes (tor-gencert):
6553 - Correctly handle the case where an authority operator enters a
6554 passphrase but sends an EOF before sending a newline. Fixes bug
6555 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
6557 o Code simplification and refactoring:
6558 - Clean up a little duplicated code in
6559 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6561 - Decouple the list of streams waiting to be attached to circuits
6562 from the overall connection list. This change makes it possible to
6563 attach streams quickly while simplifying Tor's callgraph and
6564 avoiding O(N) scans of the entire connection list. Closes
6566 - Extract the more complicated parts of circuit_mark_for_close()
6567 into a new function that we run periodically before circuits are
6568 freed. This change removes more than half of the functions
6569 currently in the "blob". Closes ticket 17218.
6570 - Move logging of redundant policy entries in
6571 policies_parse_exit_policy_internal into its own function. Closes
6572 ticket 17608; patch from "juce".
6573 - Quote all the string interpolations in configure.ac -- even those
6574 which we are pretty sure can't contain spaces. Closes ticket
6575 17744. Patch from zerosion.
6576 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6577 use them. Closes ticket 17926.
6578 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
6579 inplace, so there's no need to have a separate implementation for
6580 the non-inplace code. Closes ticket 18258. Patch from Malek.
6581 - Simplify return types for some crypto functions that can't
6582 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
6583 - When a direct directory request fails immediately on launch,
6584 instead of relaunching that request from inside the code that
6585 launches it, instead mark the connection for teardown. This change
6586 simplifies Tor's callback and prevents the directory-request
6587 launching code from invoking itself recursively. Closes
6591 - Add a description of the correct use of the '--keygen' command-
6592 line option. Closes ticket 17583; based on text by 's7r'.
6593 - Change build messages to refer to "Fedora" instead of "Fedora
6594 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
6595 Patches from "icanhasaccount" and "cypherpunks".
6596 - Document the contents of the 'datadir/keys' subdirectory in the
6597 manual page. Closes ticket 17621.
6598 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6599 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6600 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6601 - Mention torspec URL in the manpage and point the reader to it
6602 whenever we mention a document that belongs in torspce. Fixes
6604 - Stop recommending use of nicknames to identify relays in our
6605 MapAddress documentation. Closes ticket 18312.
6608 - Remove client-side support for connecting to Tor relays running
6609 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6610 the v3 TLS handshake protocol, and are no longer allowed on the
6611 Tor network. Implements the client side of ticket 11150. Based on
6612 patches by Tom van der Woerdt.
6613 - We no longer maintain an internal freelist in memarea.c.
6614 Allocators should be good enough to make this code unnecessary,
6615 and it's doubtful that it ever had any performance benefit.
6618 - Add unit tests to check for common RNG failure modes, such as
6619 returning all zeroes, identical values, or incrementing values
6620 (OpenSSL's rand_predictable feature). Patch by teor.
6621 - Always test both ed25519 backends, so that we can be sure that our
6622 batch-open replacement code works. Part of ticket 16794.
6623 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6624 portion of ticket 16831.
6625 - Fix several warnings from clang's address sanitizer produced in
6627 - Log more information when the backtrace tests fail. Closes ticket
6628 17892. Patch from "cypherpunks."
6629 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6630 util_format.c, directory.c, and options_validate.c. Closes tickets
6631 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6633 - Treat backtrace test failures as expected on FreeBSD until we
6634 solve bug 17808. Closes ticket 18204.
6635 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6636 Patch from Reinaldo de Souza Jr.
6639 Changes in version 0.2.7.6 - 2015-12-10
6640 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6641 well as a minor bug in hidden service reliability.
6643 o Major bugfixes (guard selection):
6644 - Actually look at the Guard flag when selecting a new directory
6645 guard. When we implemented the directory guard design, we
6646 accidentally started treating all relays as if they have the Guard
6647 flag during guard selection, leading to weaker anonymity and worse
6648 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6651 o Minor features (geoip):
6652 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6655 o Minor bugfixes (compilation):
6656 - When checking for net/pfvar.h, include netinet/in.h if possible.
6657 This fixes transparent proxy detection on OpenBSD. Fixes bug
6658 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6659 - Fix a compilation warning with Clang 3.6: Do not check the
6660 presence of an address which can never be NULL. Fixes bug 17781.
6662 o Minor bugfixes (correctness):
6663 - When displaying an IPv6 exit policy, include the mask bits
6664 correctly even when the number is greater than 31. Fixes bug
6665 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6666 - The wrong list was used when looking up expired intro points in a
6667 rend service object, causing what we think could be reachability
6668 issues for hidden services, and triggering a BUG log. Fixes bug
6669 16702; bugfix on 0.2.7.2-alpha.
6670 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6671 bug 17722; bugfix on 0.2.7.2-alpha.
6674 Changes in version 0.2.7.5 - 2015-11-20
6675 The Tor 0.2.7 release series is dedicated to the memory of Tor user
6676 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6677 tirelessly to advocate human rights regardless of national borders,
6678 and oppose the encroachments of mass surveillance. He opposed national
6679 exceptionalism, he brought clarity to legal and policy debates, he
6680 understood and predicted the impact of mass surveillance on the world,
6681 and he laid the groundwork for resisting it. While serving on the Tor
6682 Project's board of directors, he brought us his uncompromising focus
6683 on technical excellence in the service of humankind. Caspar was an
6684 inimitable force for good and a wonderful friend. He was kind,
6685 humorous, generous, gallant, and believed we should protect one
6686 another without exception. We honor him here for his ideals, his
6687 efforts, and his accomplishments. Please honor his memory with works
6688 that would make him proud.
6690 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6692 The 0.2.7 series adds a more secure identity key type for relays,
6693 improves cryptography performance, resolves several longstanding
6694 hidden-service performance issues, improves controller support for
6695 hidden services, and includes small bugfixes and performance
6696 improvements throughout the program. This release series also includes
6697 more tests than before, and significant simplifications to which parts
6698 of Tor invoke which others. For a full list of changes, see below.
6700 o New system requirements:
6701 - Tor no longer includes workarounds to support Libevent versions
6702 before 1.3e. Libevent 2.0 or later is recommended. Closes
6704 - Tor no longer supports copies of OpenSSL that are missing support
6705 for Elliptic Curve Cryptography. (We began using ECC when
6706 available in 0.2.4.8-alpha, for more safe and efficient key
6707 negotiation.) In particular, support for at least one of P256 or
6708 P224 is now required, with manual configuration needed if only
6709 P224 is available. Resolves ticket 16140.
6710 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
6711 on an operating system that has not upgraded to OpenSSL 1.0 or
6712 later, and you compile Tor from source, you will need to install a
6713 more recent OpenSSL to link Tor against.) These versions of
6714 OpenSSL are still supported by the OpenSSL, but the numerous
6715 cryptographic improvements in later OpenSSL releases makes them a
6716 clear choice. Resolves ticket 16034.
6718 o Major features (controller):
6719 - Add the ADD_ONION and DEL_ONION commands that allow the creation
6720 and management of hidden services via the controller. Closes
6722 - New "GETINFO onions/current" and "GETINFO onions/detached"
6723 commands to get information about hidden services created via the
6724 controller. Part of ticket 6411.
6725 - New HSFETCH command to launch a request for a hidden service
6726 descriptor. Closes ticket 14847.
6727 - New HSPOST command to upload a hidden service descriptor. Closes
6728 ticket 3523. Patch by "DonnchaC".
6730 o Major features (Ed25519 identity keys, Proposal 220):
6731 - Add support for offline encrypted Ed25519 master keys. To use this
6732 feature on your tor relay, run "tor --keygen" to make a new master
6733 key (or to make a new signing key if you already have a master
6734 key). Closes ticket 13642.
6735 - All relays now maintain a stronger identity key, using the Ed25519
6736 elliptic curve signature format. This master key is designed so
6737 that it can be kept offline. Relays also generate an online
6738 signing key, and a set of other Ed25519 keys and certificates.
6739 These are all automatically regenerated and rotated as needed.
6740 Implements part of ticket 12498.
6741 - Directory authorities now vote on Ed25519 identity keys along with
6742 RSA1024 keys. Implements part of ticket 12498.
6743 - Directory authorities track which Ed25519 identity keys have been
6744 used with which RSA1024 identity keys, and do not allow them to
6745 vary freely. Implements part of ticket 12498.
6746 - Microdescriptors now include Ed25519 identity keys. Implements
6747 part of ticket 12498.
6748 - Add a --newpass option to allow changing or removing the
6749 passphrase of an encrypted key with tor --keygen. Implements part
6751 - Add a new OfflineMasterKey option to tell Tor never to try loading
6752 or generating a secret Ed25519 identity key. You can use this in
6753 combination with tor --keygen to manage offline and/or encrypted
6754 Ed25519 keys. Implements ticket 16944.
6755 - On receiving a HUP signal, check to see whether the Ed25519
6756 signing key has changed, and reload it if so. Closes ticket 16790.
6757 - Significant usability improvements for Ed25519 key management. Log
6758 messages are better, and the code can recover from far more
6759 failure conditions. Thanks to "s7r" for reporting and diagnosing
6762 o Major features (ECC performance):
6763 - Improve the runtime speed of Ed25519 signature verification by
6764 using Ed25519-donna's batch verification support. Implements
6766 - Improve the speed of Ed25519 operations and Curve25519 keypair
6767 generation when built targeting 32 bit x86 platforms with SSE2
6768 available. Implements ticket 16535.
6769 - Improve the runtime speed of Ed25519 operations by using the
6770 public-domain Ed25519-donna by Andrew M. ("floodyberry").
6771 Implements ticket 16467.
6772 - Improve the runtime speed of the ntor handshake by using an
6773 optimized curve25519 basepoint scalarmult implementation from the
6774 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
6775 ideas by Adam Langley. Implements ticket 9663.
6777 o Major features (Hidden services):
6778 - Hidden services, if using the EntryNodes option, are required to
6779 use more than one EntryNode, in order to avoid a guard discovery
6780 attack. (This would only affect people who had configured hidden
6781 services and manually specified the EntryNodes option with a
6782 single entry-node. The impact was that it would be easy to
6783 remotely identify the guard node used by such a hidden service.
6784 See ticket for more information.) Fixes ticket 14917.
6785 - Add the torrc option HiddenServiceNumIntroductionPoints, to
6786 specify a fixed number of introduction points. Its maximum value
6787 is 10 and default is 3. Using this option can increase a hidden
6788 service's reliability under load, at the cost of making it more
6789 visible that the hidden service is facing extra load. Closes
6791 - Remove the adaptive algorithm for choosing the number of
6792 introduction points, which used to change the number of
6793 introduction points (poorly) depending on the number of
6794 connections the HS sees. Closes ticket 4862.
6796 o Major features (onion key cross-certification):
6797 - Relay descriptors now include signatures of their own identity
6798 keys, made using the TAP and ntor onion keys. These signatures
6799 allow relays to prove ownership of their own onion keys. Because
6800 of this change, microdescriptors will no longer need to include
6801 RSA identity keys. Implements proposal 228; closes ticket 12499.
6803 o Major bugfixes (client-side privacy, also in 0.2.6.9):
6804 - Properly separate out each SOCKSPort when applying stream
6805 isolation. The error occurred because each port's session group
6806 was being overwritten by a default value when the listener
6807 connection was initialized. Fixes bug 16247; bugfix on
6808 0.2.6.3-alpha. Patch by "jojelino".
6810 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
6811 - Stop refusing to store updated hidden service descriptors on a
6812 client. This reverts commit 9407040c59218 (which indeed fixed bug
6813 14219, but introduced a major hidden service reachability
6814 regression detailed in bug 16381). This is a temporary fix since
6815 we can live with the minor issue in bug 14219 (it just results in
6816 some load on the network) but the regression of 16381 is too much
6817 of a setback. First-round fix for bug 16381; bugfix
6820 o Major bugfixes (hidden services):
6821 - Revert commit that made directory authorities assign the HSDir
6822 flag to relays without a DirPort; this was bad because such relays
6823 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6825 - When cannibalizing a circuit for an introduction point, always
6826 extend to the chosen exit node (creating a 4 hop circuit).
6827 Previously Tor would use the current circuit exit node, which
6828 changed the original choice of introduction point, and could cause
6829 the hidden service to skip excluded introduction points or
6830 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
6833 o Major bugfixes (memory leaks):
6834 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6835 17398; bugfix on 0.2.6.1-alpha.
6837 o Major bugfixes (open file limit):
6838 - The open file limit wasn't checked before calling
6839 tor_accept_socket_nonblocking(), which would make Tor exceed the
6840 limit. Now, before opening a new socket, Tor validates the open
6841 file limit just before, and if the max has been reached, return an
6842 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
6844 o Major bugfixes (security, correctness):
6845 - Fix an error that could cause us to read 4 bytes before the
6846 beginning of an openssl string. This bug could be used to cause
6847 Tor to crash on systems with unusual malloc implementations, or
6848 systems with unusual hardening installed. Fixes bug 17404; bugfix
6851 o Major bugfixes (stability, also in 0.2.6.10):
6852 - Stop crashing with an assertion failure when parsing certain kinds
6853 of malformed or truncated microdescriptors. Fixes bug 16400;
6854 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6855 by "cypherpunks_backup".
6856 - Stop random client-side assertion failures that could occur when
6857 connecting to a busy hidden service, or connecting to a hidden
6858 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6861 o Minor features (client, SOCKS):
6862 - Add GroupWritable and WorldWritable options to unix-socket based
6863 SocksPort and ControlPort options. These options apply to a single
6864 socket, and override {Control,Socks}SocketsGroupWritable. Closes
6866 - Relax the validation done to hostnames in SOCKS5 requests, and
6867 allow a single trailing '.' to cope with clients that pass FQDNs
6868 using that syntax to explicitly indicate that the domain name is
6869 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
6870 - Relax the validation of hostnames in SOCKS5 requests, allowing the
6871 character '_' to appear, in order to cope with domains observed in
6872 the wild that are serving non-RFC compliant records. Resolves
6875 o Minor features (client-side privacy):
6876 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6877 lifespan when IsolateSOCKSAuth and streams with SOCKS
6878 authentication are attached to the circuit. This allows
6879 applications like TorBrowser to manage circuit lifetime on their
6880 own. Implements feature 15482.
6881 - When logging malformed hostnames from SOCKS5 requests, respect
6882 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6884 o Minor features (clock-jump tolerance):
6885 - Recover better when our clock jumps back many hours, like might
6886 happen for Tails or Whonix users who start with a very wrong
6887 hardware clock, use Tor to discover a more accurate time, and then
6888 fix their clock. Resolves part of ticket 8766.
6890 o Minor features (command-line interface):
6891 - Make --hash-password imply --hush to prevent unnecessary noise.
6892 Closes ticket 15542. Patch from "cypherpunks".
6893 - Print a warning whenever we find a relative file path being used
6894 as torrc option. Resolves issue 14018.
6896 o Minor features (compilation):
6897 - Give a warning as early as possible when trying to build with an
6898 unsupported OpenSSL version. Closes ticket 16901.
6899 - Use C99 variadic macros when the compiler is not GCC. This avoids
6900 failing compilations on MSVC, and fixes a log-file-based race
6901 condition in our old workarounds. Original patch from Gisle Vanem.
6903 o Minor features (control protocol):
6904 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
6905 the control protocol. Resolves ticket 15358.
6907 o Minor features (controller):
6908 - Add DirAuthority lines for default directory authorities to the
6909 output of the "GETINFO config/defaults" command if not already
6910 present. Implements ticket 14840.
6911 - Controllers can now use "GETINFO hs/client/desc/id/..." to
6912 retrieve items from the client's hidden service descriptor cache.
6913 Closes ticket 14845.
6914 - Implement a new controller command "GETINFO status/fresh-relay-
6915 descs" to fetch a descriptor/extrainfo pair that was generated on
6916 demand just for the controller's use. Implements ticket 14784.
6918 o Minor features (directory authorities):
6919 - Directory authorities no longer vote against the "Fast", "Stable",
6920 and "HSDir" flags just because they were going to vote against
6921 "Running": if the consensus turns out to be that the router was
6922 running, then the authority's vote should count. Patch from Peter
6923 Retzlaff; closes issue 8712.
6925 o Minor features (directory authorities, security, also in 0.2.6.9):
6926 - The HSDir flag given by authorities now requires the Stable flag.
6927 For the current network, this results in going from 2887 to 2806
6928 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6929 attack by raising the effort for a relay to become Stable to
6930 require at the very least 7 days, while maintaining the 96 hours
6931 uptime requirement for HSDir. Implements ticket 8243.
6933 o Minor features (DoS-resistance):
6934 - Make it harder for attackers to overload hidden services with
6935 introductions, by blocking multiple introduction requests on the
6936 same circuit. Resolves ticket 15515.
6938 o Minor features (geoip):
6939 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6942 o Minor features (hidden services):
6943 - Add the new options "HiddenServiceMaxStreams" and
6944 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
6945 limit the maximum number of simultaneous streams per circuit, and
6946 optionally tear down the circuit when the limit is exceeded. Part
6948 - Client now uses an introduction point failure cache to know when
6949 to fetch or keep a descriptor in their cache. Previously, failures
6950 were recorded implicitly, but not explicitly remembered. Closes
6952 - Relays need to have the Fast flag to get the HSDir flag. As this
6953 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6954 drop. This change should make some attacks against the hidden
6955 service directory system harder. Fixes ticket 15963.
6956 - Turn on hidden service statistics collection by setting the torrc
6957 option HiddenServiceStatistics to "1" by default. (This keeps
6958 track only of the fraction of traffic used by hidden services, and
6959 the total number of hidden services in existence.) Closes
6961 - To avoid leaking HS popularity, don't cycle the introduction point
6962 when we've handled a fixed number of INTRODUCE2 cells but instead
6963 cycle it when a random number of introductions is reached, thus
6964 making it more difficult for an attacker to find out the amount of
6965 clients that have used the introduction point for a specific HS.
6966 Closes ticket 15745.
6968 o Minor features (logging):
6969 - Include the Tor version in all LD_BUG log messages, since people
6970 tend to cut and paste those into the bugtracker. Implements
6973 o Minor features (pluggable transports):
6974 - When launching managed pluggable transports on Linux systems,
6975 attempt to have the kernel deliver a SIGTERM on tor exit if the
6976 pluggable transport process is still running. Resolves
6978 - When launching managed pluggable transports, setup a valid open
6979 stdin in the child process that can be used to detect if tor has
6980 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
6981 can be used by implementations to detect this new behavior.
6982 Resolves ticket 15435.
6984 o Minor bugfixes (torrc exit policies):
6985 - In each instance above, usage advice is provided to avoid the
6986 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
6987 16069; bugfix on 0.2.4.7-alpha.
6988 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6989 produce IPv6 wildcard addresses. Previously they would produce
6990 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6991 of bug 16069; bugfix on 0.2.4.7-alpha.
6992 - When parsing torrc ExitPolicies, we now issue an info-level
6993 message when expanding an "accept/reject *" line to include both
6994 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
6995 - When parsing torrc ExitPolicies, we now warn for a number of cases
6996 where the user's intent is likely to differ from Tor's actual
6997 behavior. These include: using an IPv4 address with an accept6 or
6998 reject6 line; using "private" on an accept6 or reject6 line; and
6999 including any ExitPolicy lines after accept *:* or reject *:*.
7000 Related to ticket 16069.
7002 o Minor bugfixes (command-line interface):
7003 - When "--quiet" is provided along with "--validate-config", do not
7004 write anything to stdout on success. Fixes bug 14994; bugfix
7006 - When complaining about bad arguments to "--dump-config", use
7008 - Print usage information for --dump-config when it is used without
7009 an argument. Also, fix the error message to use different wording
7010 and add newline at the end. Fixes bug 15541; bugfix
7013 o Minor bugfixes (compilation):
7014 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
7015 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
7016 - Repair compilation with the most recent (unreleased, alpha)
7017 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
7019 o Minor bugfixes (compilation, also in 0.2.6.9):
7020 - Build with --enable-systemd correctly when libsystemd is
7021 installed, but systemd is not. Fixes bug 16164; bugfix on
7022 0.2.6.3-alpha. Patch from Peter Palfrader.
7024 o Minor bugfixes (configuration, unit tests):
7025 - Only add the default fallback directories when the DirAuthorities,
7026 AlternateDirAuthority, and FallbackDir directory config options
7027 are set to their defaults. The default fallback directory list is
7028 currently empty, this fix will only change tor's behavior when it
7029 has default fallback directories. Includes unit tests for
7030 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7031 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7033 o Minor bugfixes (controller):
7034 - Add the descriptor ID in each HS_DESC control event. It was
7035 missing, but specified in control-spec.txt. Fixes bug 15881;
7036 bugfix on 0.2.5.2-alpha.
7038 o Minor bugfixes (correctness):
7039 - For correctness, avoid modifying a constant string in
7040 handle_control_postdescriptor. Fixes bug 15546; bugfix
7042 - Remove side-effects from tor_assert() calls. This was harmless,
7043 because we never disable assertions, but it is bad style and
7044 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7046 - When calling channel_free_list(), avoid calling smartlist_remove()
7047 while inside a FOREACH loop. This partially reverts commit
7048 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
7049 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
7051 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
7052 - Check for failures from crypto_early_init, and refuse to continue.
7053 A previous typo meant that we could keep going with an
7054 uninitialized crypto library, and would have OpenSSL initialize
7055 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7056 when implementing ticket 4900. Patch by "teor".
7058 o Minor bugfixes (hidden service):
7059 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7060 a client authorized hidden service. Fixes bug 15823; bugfix
7062 - Remove an extraneous newline character from the end of hidden
7063 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7065 o Minor bugfixes (Linux seccomp2 sandbox):
7066 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
7067 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
7068 - Allow bridge authorities to run correctly under the seccomp2
7069 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
7070 - Add the "hidserv-stats" filename to our sandbox filter for the
7071 HiddenServiceStatistics option to work properly. Fixes bug 17354;
7072 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
7074 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
7075 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7076 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7077 on 0.2.6.3-alpha. Patch from "teor".
7079 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
7080 - Allow systemd connections to work with the Linux seccomp2 sandbox
7081 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7083 - Fix sandboxing to work when running as a relay, by allowing the
7084 renaming of secret_id_key, and allowing the eventfd2 and futex
7085 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
7088 o Minor bugfixes (logging):
7089 - When building Tor under Clang, do not include an extra set of
7090 parentheses in log messages that include function names. Fixes bug
7091 15269; bugfix on every released version of Tor when compiled with
7092 recent enough Clang.
7094 o Minor bugfixes (network):
7095 - When attempting to use fallback technique for network interface
7096 lookup, disregard loopback and multicast addresses since they are
7097 unsuitable for public communications.
7099 o Minor bugfixes (open file limit):
7100 - Fix set_max_file_descriptors() to set by default the max open file
7101 limit to the current limit when setrlimit() fails. Fixes bug
7102 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
7104 o Minor bugfixes (portability):
7105 - Check correctly for Windows socket errors in the workqueue
7106 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
7107 - Try harder to normalize the exit status of the Tor process to the
7108 standard-provided range. Fixes bug 16975; bugfix on every version
7110 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
7111 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
7113 o Minor bugfixes (relay):
7114 - Ensure that worker threads actually exit when a fatal error or
7115 shutdown is indicated. This fix doesn't currently affect the
7116 behavior of Tor, because Tor workers never indicates fatal error
7117 or shutdown except in the unit tests. Fixes bug 16868; bugfix
7119 - Fix a rarely-encountered memory leak when failing to initialize
7120 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
7122 - Unblock threads before releasing the work queue mutex to ensure
7123 predictable scheduling behavior. Fixes bug 16644; bugfix
7126 o Minor bugfixes (security, exit policies):
7127 - ExitPolicyRejectPrivate now also rejects the relay's published
7128 IPv6 address (if any), and any publicly routable IPv4 or IPv6
7129 addresses on any local interfaces. ticket 17027. Patch by "teor".
7130 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
7132 o Minor bugfixes (statistics):
7133 - Disregard the ConnDirectionStatistics torrc options when Tor is
7134 not a relay since in that mode of operation no sensible data is
7135 being collected and because Tor might run into measurement hiccups
7136 when running as a client for some time, then becoming a relay.
7137 Fixes bug 15604; bugfix on 0.2.2.35.
7139 o Minor bugfixes (systemd):
7140 - Tor's systemd unit file no longer contains extraneous spaces.
7141 These spaces would sometimes confuse tools like deb-systemd-
7142 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
7144 o Minor bugfixes (test networks):
7145 - When self-testing reachability, use ExtendAllowPrivateAddresses to
7146 determine if local/private addresses imply reachability. The
7147 previous fix used TestingTorNetwork, which implies
7148 ExtendAllowPrivateAddresses, but this excluded rare configurations
7149 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
7150 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
7151 issue discovered by CJ Ess.
7153 o Minor bugfixes (tests, also in 0.2.6.9):
7154 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7155 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7157 o Code simplification and refactoring:
7158 - Change the function that's called when we need to retry all
7159 downloads so that it only reschedules the downloads to happen
7160 immediately, rather than launching them all at once itself. This
7161 further simplifies Tor's callgraph.
7162 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
7163 to ensure they remain consistent and visible everywhere.
7164 - Move some format-parsing functions out of crypto.c and
7165 crypto_curve25519.c into crypto_format.c and/or util_format.c.
7166 - Move the client-only parts of init_keys() into a separate
7167 function. Closes ticket 16763.
7168 - Move the hacky fallback code out of get_interface_address6() into
7169 separate function and get it covered with unit-tests. Resolves
7171 - Refactor hidden service client-side cache lookup to intelligently
7172 report its various failure cases, and disentangle failure cases
7173 involving a lack of introduction points. Closes ticket 14391.
7174 - Remove some vestigial workarounds for the MSVC6 compiler. We
7175 haven't supported that in ages.
7176 - Remove the unused "nulterminate" argument from buf_pullup().
7177 - Simplify the microdesc_free() implementation so that it no longer
7178 appears (to code analysis tools) to potentially invoke a huge
7179 suite of other microdesc functions.
7180 - Simply the control graph further by deferring the inner body of
7181 directory_all_unreachable() into a callback. Closes ticket 16762.
7182 - The link authentication code has been refactored for better
7183 testability and reliability. It now uses code generated with the
7184 "trunnel" binary encoding generator, to reduce the risk of bugs
7185 due to programmer error. Done as part of ticket 12498.
7186 - Treat the loss of an owning controller as equivalent to a SIGTERM
7187 signal. This removes a tiny amount of duplicated code, and
7188 simplifies our callgraph. Closes ticket 16788.
7189 - Use our own Base64 encoder instead of OpenSSL's, to allow more
7190 control over the output. Part of ticket 15652.
7191 - When generating an event to send to the controller, we no longer
7192 put the event over the network immediately. Instead, we queue
7193 these events, and use a Libevent callback to deliver them. This
7194 change simplifies Tor's callgraph by reducing the number of
7195 functions from which all other Tor functions are reachable. Closes
7197 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
7198 that try to scan or compile every file on Unix won't decide that
7202 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
7203 - Improve the descriptions of statistics-related torrc options in
7204 the manpage to describe rationale and possible uses cases. Fixes
7206 - Improve the layout and formatting of ./configure --help messages.
7207 Closes ticket 15024. Patch from "cypherpunks".
7208 - Include a specific and (hopefully) accurate documentation of the
7209 torrc file's meta-format in doc/torrc_format.txt. This is mainly
7210 of interest to people writing programs to parse or generate torrc
7211 files. This document is not a commitment to long-term
7212 compatibility; some aspects of the current format are a bit
7213 ridiculous. Closes ticket 2325.
7214 - Include the TUNING document in our source tarball. It is referred
7215 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
7217 - Note that HiddenServicePorts can take a unix domain socket. Closes
7219 - Recommend a 40 GB example AccountingMax in torrc.sample rather
7220 than a 4 GB max. Closes ticket 16742.
7221 - Standardize on the term "server descriptor" in the manual page.
7222 Previously, we had used "router descriptor", "server descriptor",
7223 and "relay descriptor" interchangeably. Part of ticket 14987.
7224 - Advise users on how to configure separate IPv4 and IPv6 exit
7225 policies in the manpage and sample torrcs. Related to ticket 16069.
7226 - Fix an error in the manual page and comments for
7227 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
7228 required "ORPort connectivity". While this is true, it is in no
7229 way unique to the HSDir flag. Of all the flags, only HSDirs need a
7230 DirPort configured in order for the authorities to assign that
7231 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
7233 - Fix the usage message of tor-resolve(1) so that it no longer lists
7234 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
7237 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
7238 and always use the internal Base64 decoder. The internal decoder
7239 has been part of tor since 0.2.0.10-alpha, and no one should
7240 be using the OpenSSL one. Part of ticket 15652.
7241 - Remove the 'tor_strclear()' function; use memwipe() instead.
7242 Closes ticket 14922.
7243 - Remove the code that would try to aggressively flush controller
7244 connections while writing to them. This code was introduced in
7245 0.1.2.7-alpha, in order to keep output buffers from exceeding
7246 their limits. But there is no longer a maximum output buffer size,
7247 and flushing data in this way caused some undesirable recursions
7248 in our call graph. Closes ticket 16480.
7249 - The internal pure-C tor-fw-helper tool is now removed from the Tor
7250 distribution, in favor of the pure-Go clone available from
7251 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
7252 used by the C tor-fw-helper are not, in our opinion, very
7253 confidence- inspiring in their secure-programming techniques.
7254 Closes ticket 13338.
7257 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
7258 fingerprinting we now recommend pluggable transports; for forward-
7259 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
7260 - Remove the HidServDirectoryV2 option. Now all relays offer to
7261 store hidden service descriptors. Related to 16543.
7262 - Remove the VoteOnHidServDirectoriesV2 option, since all
7263 authorities have long set it to 1. Closes ticket 16543.
7264 - Remove the undocumented "--digests" command-line option. It
7265 complicated our build process, caused subtle build issues on
7266 multiple platforms, and is now redundant since we started
7267 including git version identifiers. Closes ticket 14742.
7268 - Tor no longer contains checks for ancient directory cache versions
7269 that didn't know about microdescriptors.
7270 - Tor no longer contains workarounds for stat files generated by
7271 super-old versions of Tor that didn't choose guards sensibly.
7274 - The test-network.sh script now supports performance testing.
7275 Requires corresponding chutney performance testing changes. Patch
7276 by "teor". Closes ticket 14175.
7277 - Add a new set of callgraph analysis scripts that use clang to
7278 produce a list of which Tor functions are reachable from which
7279 other Tor functions. We're planning to use these to help simplify
7280 our code structure by identifying illogical dependencies.
7281 - Add new 'test-full' and 'test-full-online' targets to run all
7282 tests, including integration tests with stem and chutney.
7283 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
7284 by-side in the same parent directory. Closes ticket 16903. Patch
7286 - Document use of coverity, clang static analyzer, and clang dynamic
7287 undefined behavior and address sanitizers in doc/HACKING. Include
7288 detailed usage instructions in the blacklist. Patch by "teor".
7289 Closes ticket 15817.
7290 - Make "bridges+hs" the default test network. This tests almost all
7291 tor functionality during make test-network, while allowing tests
7292 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
7293 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
7294 (chutney). Patches by "teor".
7295 - Make the test-workqueue test work on Windows by initializing the
7296 network before we begin.
7297 - New make target (make test-network-all) to run multiple applicable
7298 chutney test cases. Patch from Teor; closes 16953.
7299 - Now that OpenSSL has its own scrypt implementation, add an unit
7300 test that checks for interoperability between libscrypt_scrypt()
7301 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
7302 and rely on EVP_PBE_scrypt() whenever possible. Resolves
7304 - The link authentication protocol code now has extensive tests.
7305 - The relay descriptor signature testing code now has
7307 - The test_workqueue program now runs faster, and is enabled by
7308 default as a part of "make check".
7309 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
7310 functions in dns.c. Implements a portion of ticket 16831.
7311 - Use environment variables rather than autoconf substitutions to
7312 send variables from the build system to the test scripts. This
7313 change should be easier to maintain, and cause 'make distcheck' to
7314 work better than before. Fixes bug 17148.
7315 - When building Tor with testing coverage enabled, run Chutney tests
7316 (if any) using the 'tor-cov' coverage binary.
7317 - When running test-network or test-stem, check for the absence of
7318 stem/chutney before doing any build operations.
7319 - Add a test to verify that the compiler does not eliminate our
7320 memwipe() implementation. Closes ticket 15377.
7321 - Add make rule `check-changes` to verify the format of changes
7322 files. Closes ticket 15180.
7323 - Add unit tests for control_event_is_interesting(). Add a compile-
7324 time check that the number of events doesn't exceed the capacity
7325 of control_event_t.event_mask. Closes ticket 15431, checks for
7326 bugs similar to 13085. Patch by "teor".
7327 - Command-line argument tests moved to Stem. Resolves ticket 14806.
7328 - Integrate the ntor, backtrace, and zero-length keys tests into the
7329 automake test suite. Closes ticket 15344.
7330 - Remove assertions during builds to determine Tor's test coverage.
7331 We don't want to trigger these even in assertions, so including
7332 them artificially makes our branch coverage look worse than it is.
7333 This patch provides the new test-stem-full and coverage-html-full
7334 configure options. Implements ticket 15400.
7335 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
7336 explicitly manage consensus flags in testing networks. Patch by
7337 "robgjansen", modified by "teor". Implements part of ticket 14882.
7338 - Check for matching value in server response in ntor_ref.py. Fixes
7339 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
7341 - Set the severity correctly when testing
7342 get_interface_addresses_ifaddrs() and
7343 get_interface_addresses_win32(), so that the tests fail gracefully
7344 instead of triggering an assertion. Fixes bug 15759; bugfix on
7345 0.2.6.3-alpha. Reported by Nicolas Derive.
7347 Changes in version 0.2.6.10 - 2015-07-12
7348 Tor version 0.2.6.10 fixes some significant stability and hidden
7349 service client bugs, bulletproofs the cryptography init process, and
7350 fixes a bug when using the sandbox code with some older versions of
7351 Linux. Everyone running an older version, especially an older version
7352 of 0.2.6, should upgrade.
7354 o Major bugfixes (hidden service clients, stability):
7355 - Stop refusing to store updated hidden service descriptors on a
7356 client. This reverts commit 9407040c59218 (which indeed fixed bug
7357 14219, but introduced a major hidden service reachability
7358 regression detailed in bug 16381). This is a temporary fix since
7359 we can live with the minor issue in bug 14219 (it just results in
7360 some load on the network) but the regression of 16381 is too much
7361 of a setback. First-round fix for bug 16381; bugfix
7364 o Major bugfixes (stability):
7365 - Stop crashing with an assertion failure when parsing certain kinds
7366 of malformed or truncated microdescriptors. Fixes bug 16400;
7367 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7368 by "cypherpunks_backup".
7369 - Stop random client-side assertion failures that could occur when
7370 connecting to a busy hidden service, or connecting to a hidden
7371 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7374 o Minor features (geoip):
7375 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7376 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7378 o Minor bugfixes (crypto error-handling):
7379 - Check for failures from crypto_early_init, and refuse to continue.
7380 A previous typo meant that we could keep going with an
7381 uninitialized crypto library, and would have OpenSSL initialize
7382 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7383 when implementing ticket 4900. Patch by "teor".
7385 o Minor bugfixes (Linux seccomp2 sandbox):
7386 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7387 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7388 on 0.2.6.3-alpha. Patch from "teor".
7391 Changes in version 0.2.6.9 - 2015-06-11
7392 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
7393 requirements for receiving an HSDir flag, and addresses some other small
7394 bugs in the systemd and sandbox code. Clients using circuit isolation
7395 should upgrade; all directory authorities should upgrade.
7397 o Major bugfixes (client-side privacy):
7398 - Properly separate out each SOCKSPort when applying stream
7399 isolation. The error occurred because each port's session group was
7400 being overwritten by a default value when the listener connection
7401 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
7404 o Minor feature (directory authorities, security):
7405 - The HSDir flag given by authorities now requires the Stable flag.
7406 For the current network, this results in going from 2887 to 2806
7407 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7408 attack by raising the effort for a relay to become Stable which
7409 takes at the very least 7 days to do so and by keeping the 96
7410 hours uptime requirement for HSDir. Implements ticket 8243.
7412 o Minor bugfixes (compilation):
7413 - Build with --enable-systemd correctly when libsystemd is
7414 installed, but systemd is not. Fixes bug 16164; bugfix on
7415 0.2.6.3-alpha. Patch from Peter Palfrader.
7417 o Minor bugfixes (Linux seccomp2 sandbox):
7418 - Fix sandboxing to work when running as a relaymby renaming of
7419 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
7420 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
7421 - Allow systemd connections to work with the Linux seccomp2 sandbox
7422 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7425 o Minor bugfixes (tests):
7426 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7427 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7430 Changes in version 0.2.6.8 - 2015-05-21
7431 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
7432 fixes an authority-side bug in assigning the HSDir flag. All directory
7433 authorities should upgrade.
7435 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
7436 - Revert commit that made directory authorities assign the HSDir
7437 flag to relays without a DirPort; this was bad because such relays
7438 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7441 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7442 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7443 a client authorized hidden service. Fixes bug 15823; bugfix
7446 o Minor features (geoip):
7447 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7448 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7452 Changes in version 0.2.6.7 - 2015-04-06
7453 Tor 0.2.6.7 fixes two security issues that could be used by an
7454 attacker to crash hidden services, or crash clients visiting hidden
7455 services. Hidden services should upgrade as soon as possible; clients
7456 should upgrade whenever packages become available.
7458 This release also contains two simple improvements to make hidden
7459 services a bit less vulnerable to denial-of-service attacks.
7461 o Major bugfixes (security, hidden service):
7462 - Fix an issue that would allow a malicious client to trigger an
7463 assertion failure and halt a hidden service. Fixes bug 15600;
7464 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7465 - Fix a bug that could cause a client to crash with an assertion
7466 failure when parsing a malformed hidden service descriptor. Fixes
7467 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7469 o Minor features (DoS-resistance, hidden service):
7470 - Introduction points no longer allow multiple INTRODUCE1 cells to
7471 arrive on the same circuit. This should make it more expensive for
7472 attackers to overwhelm hidden services with introductions.
7473 Resolves ticket 15515.
7474 - Decrease the amount of reattempts that a hidden service performs
7475 when its rendezvous circuits fail. This reduces the computational
7476 cost for running a hidden service under heavy load. Resolves
7480 Changes in version 0.2.5.12 - 2015-04-06
7481 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7482 could be used by an attacker to crash hidden services, or crash clients
7483 visiting hidden services. Hidden services should upgrade as soon as
7484 possible; clients should upgrade whenever packages become available.
7486 This release also backports a simple improvement to make hidden
7487 services a bit less vulnerable to denial-of-service attacks.
7489 o Major bugfixes (security, hidden service):
7490 - Fix an issue that would allow a malicious client to trigger an
7491 assertion failure and halt a hidden service. Fixes bug 15600;
7492 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7493 - Fix a bug that could cause a client to crash with an assertion
7494 failure when parsing a malformed hidden service descriptor. Fixes
7495 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7497 o Minor features (DoS-resistance, hidden service):
7498 - Introduction points no longer allow multiple INTRODUCE1 cells to
7499 arrive on the same circuit. This should make it more expensive for
7500 attackers to overwhelm hidden services with introductions.
7501 Resolves ticket 15515.
7504 Changes in version 0.2.4.27 - 2015-04-06
7505 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7506 could be used by an attacker to crash hidden services, or crash clients
7507 visiting hidden services. Hidden services should upgrade as soon as
7508 possible; clients should upgrade whenever packages become available.
7510 This release also backports a simple improvement to make hidden
7511 services a bit less vulnerable to denial-of-service attacks.
7513 o Major bugfixes (security, hidden service):
7514 - Fix an issue that would allow a malicious client to trigger an
7515 assertion failure and halt a hidden service. Fixes bug 15600;
7516 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7517 - Fix a bug that could cause a client to crash with an assertion
7518 failure when parsing a malformed hidden service descriptor. Fixes
7519 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7521 o Minor features (DoS-resistance, hidden service):
7522 - Introduction points no longer allow multiple INTRODUCE1 cells to
7523 arrive on the same circuit. This should make it more expensive for
7524 attackers to overwhelm hidden services with introductions.
7525 Resolves ticket 15515.
7528 Changes in version 0.2.6.6 - 2015-03-24
7529 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7531 It adds numerous safety, security, correctness, and performance
7532 improvements. Client programs can be configured to use more kinds of
7533 sockets, AutomapHosts works better, the multithreading backend is
7534 improved, cell transmission is refactored, test coverage is much
7535 higher, more denial-of-service attacks are handled, guard selection is
7536 improved to handle long-term guards better, pluggable transports
7537 should work a bit better, and some annoying hidden service performance
7538 bugs should be addressed.
7540 o New compiler and system requirements:
7541 - Tor 0.2.6.x requires that your compiler support more of the C99
7542 language standard than before. The 'configure' script now detects
7543 whether your compiler supports C99 mid-block declarations and
7544 designated initializers. If it does not, Tor will not compile.
7546 We may revisit this requirement if it turns out that a significant
7547 number of people need to build Tor with compilers that don't
7548 bother implementing a 15-year-old standard. Closes ticket 13233.
7549 - Tor no longer supports systems without threading support. When we
7550 began working on Tor, there were several systems that didn't have
7551 threads, or where the thread support wasn't able to run the
7552 threads of a single process on multiple CPUs. That no longer
7553 holds: every system where Tor needs to run well now has threading
7554 support. Resolves ticket 12439.
7556 o Deprecated versions and removed support:
7557 - Tor relays older than 0.2.4.18-rc are no longer allowed to
7558 advertise themselves on the network. Closes ticket 13555.
7559 - Tor clients no longer support connecting to hidden services
7560 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
7561 option has been removed. (There shouldn't be any hidden services
7562 running these versions on the network.) Closes ticket 7803.
7564 o Directory authority changes:
7565 - The directory authority Faravahar has a new IP address. This
7566 closes ticket 14487.
7567 - Remove turtles as a directory authority.
7568 - Add longclaw as a new (v3) directory authority. This implements
7569 ticket 13296. This keeps the directory authority count at 9.
7571 o Major features (bridges):
7572 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
7573 transports if they are configured via the "TOR_PT_PROXY"
7574 environment variable. Implements proposal 232. Resolves
7577 o Major features (changed defaults):
7578 - Prevent relay operators from unintentionally running exits: When a
7579 relay is configured as an exit node, we now warn the user unless
7580 the "ExitRelay" option is set to 1. We warn even more loudly if
7581 the relay is configured with the default exit policy, since this
7582 can indicate accidental misconfiguration. Setting "ExitRelay 0"
7583 stops Tor from running as an exit relay. Closes ticket 10067.
7585 o Major features (client performance, hidden services):
7586 - Allow clients to use optimistic data when connecting to a hidden
7587 service, which should remove a round-trip from hidden service
7588 initialization. See proposal 181 for details. Implements
7591 o Major features (directory system):
7592 - Upon receiving an unparseable directory object, if its digest
7593 matches what we expected, then don't try to download it again.
7594 Previously, when we got a descriptor we didn't like, we would keep
7595 trying to download it over and over. Closes ticket 11243.
7596 - When downloading server- or microdescriptors from a directory
7597 server, we no longer launch multiple simultaneous requests to the
7598 same server. This reduces load on the directory servers,
7599 especially when directory guards are in use. Closes ticket 9969.
7600 - When downloading server- or microdescriptors over a tunneled
7601 connection, do not limit the length of our requests to what the
7602 Squid proxy is willing to handle. Part of ticket 9969.
7603 - Authorities can now vote on the correct digests and latest
7604 versions for different software packages. This allows packages
7605 that include Tor to use the Tor authority system as a way to get
7606 notified of updates and their correct digests. Implements proposal
7607 227. Closes ticket 10395.
7609 o Major features (guards):
7610 - Introduce the Guardfraction feature to improves load balancing on
7611 guard nodes. Specifically, it aims to reduce the traffic gap that
7612 guard nodes experience when they first get the Guard flag. This is
7613 a required step if we want to increase the guard lifetime to 9
7614 months or greater. Closes ticket 9321.
7616 o Major features (hidden services):
7617 - Make HS port scanning more difficult by immediately closing the
7618 circuit when a user attempts to connect to a nonexistent port.
7619 Closes ticket 13667.
7620 - Add a HiddenServiceStatistics option that allows Tor relays to
7621 gather and publish statistics about the overall size and volume of
7622 hidden service usage. Specifically, when this option is turned on,
7623 an HSDir will publish an approximate number of hidden services
7624 that have published descriptors to it the past 24 hours. Also, if
7625 a relay has acted as a hidden service rendezvous point, it will
7626 publish the approximate amount of rendezvous cells it has relayed
7627 the past 24 hours. The statistics themselves are obfuscated so
7628 that the exact values cannot be derived. For more details see
7629 proposal 238, "Better hidden service stats from Tor relays". This
7630 feature is currently disabled by default. Implements feature 13192.
7632 o Major features (performance):
7633 - Make the CPU worker implementation more efficient by avoiding the
7634 kernel and lengthening pipelines. The original implementation used
7635 sockets to transfer data from the main thread to the workers, and
7636 didn't allow any thread to be assigned more than a single piece of
7637 work at once. The new implementation avoids communications
7638 overhead by making requests in shared memory, avoiding kernel IO
7639 where possible, and keeping more requests in flight at once.
7640 Implements ticket 9682.
7642 o Major features (relay):
7643 - Raise the minimum acceptable configured bandwidth rate for bridges
7644 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
7645 20 KiB/sec.) Closes ticket 13822.
7646 - Complete revision of the code that relays use to decide which cell
7647 to send next. Formerly, we selected the best circuit to write on
7648 each channel, but we didn't select among channels in any
7649 sophisticated way. Now, we choose the best circuits globally from
7650 among those whose channels are ready to deliver traffic.
7652 This patch implements a new inter-cmux comparison API, a global
7653 high/low watermark mechanism and a global scheduler loop for
7654 transmission prioritization across all channels as well as among
7655 circuits on one channel. This schedule is currently tuned to
7656 (tolerantly) avoid making changes in network performance, but it
7657 should form the basis for major circuit performance increases in
7658 the future. Code by Andrea; tuning by Rob Jansen; implements
7661 o Major features (sample torrc):
7662 - Add a new, infrequently-changed "torrc.minimal". This file is
7663 similar to torrc.sample, but it will change as infrequently as
7664 possible, for the benefit of users whose systems prompt them for
7665 intervention whenever a default configuration file is changed.
7666 Making this change allows us to update torrc.sample to be a more
7667 generally useful "sample torrc".
7669 o Major features (security, unix domain sockets):
7670 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
7671 applications can reach Tor without having to create AF_INET or
7672 AF_INET6 sockets, meaning they can completely disable their
7673 ability to make non-Tor network connections. To create a socket of
7674 this type, use "SocksPort unix:/path/to/socket". Implements
7676 - Support mapping hidden service virtual ports to AF_UNIX sockets.
7677 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
7678 Implements ticket 11485.
7680 o Major bugfixes (client, automap):
7681 - Repair automapping with IPv6 addresses. This automapping should
7682 have worked previously, but one piece of debugging code that we
7683 inserted to detect a regression actually caused the regression to
7684 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
7685 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
7688 o Major bugfixes (crash, OSX, security):
7689 - Fix a remote denial-of-service opportunity caused by a bug in
7690 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7693 o Major bugfixes (directory authorities):
7694 - Do not assign the HSDir flag to relays if they are not Valid, or
7695 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
7697 o Major bugfixes (directory bandwidth performance):
7698 - Don't flush the zlib buffer aggressively when compressing
7699 directory information for clients. This should save about 7% of
7700 the bandwidth currently used for compressed descriptors and
7701 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
7703 o Major bugfixes (exit node stability):
7704 - Fix an assertion failure that could occur under high DNS load.
7705 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7706 diagnosed and fixed by "cypherpunks".
7708 o Major bugfixes (FreeBSD IPFW transparent proxy):
7709 - Fix address detection with FreeBSD transparent proxies, when
7710 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
7713 o Major bugfixes (hidden services):
7714 - When closing an introduction circuit that was opened in parallel
7715 with others, don't mark the introduction point as unreachable.
7716 Previously, the first successful connection to an introduction
7717 point would make the other introduction points get marked as
7718 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
7720 o Major bugfixes (Linux seccomp2 sandbox):
7721 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7722 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7723 0.2.5.1-alpha. Patch from "sanic".
7725 o Major bugfixes (mixed relay-client operation):
7726 - When running as a relay and client at the same time (not
7727 recommended), if we decide not to use a new guard because we want
7728 to retry older guards, only close the locally-originating circuits
7729 passing through that guard. Previously we would close all the
7730 circuits through that guard. Fixes bug 9819; bugfix on
7731 0.2.1.1-alpha. Reported by "skruffy".
7733 o Major bugfixes (pluggable transports):
7734 - Initialize the extended OR Port authentication cookie before
7735 launching pluggable transports. This prevents a race condition
7736 that occurred when server-side pluggable transports would cache the
7737 authentication cookie before it has been (re)generated. Fixes bug
7738 15240; bugfix on 0.2.5.1-alpha.
7740 o Major bugfixes (relay, stability, possible security):
7741 - Fix a bug that could lead to a relay crashing with an assertion
7742 failure if a buffer of exactly the wrong layout is passed to
7743 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7744 0.2.0.10-alpha. Patch from "cypherpunks".
7745 - Do not assert if the 'data' pointer on a buffer is advanced to the
7746 very end of the buffer; log a BUG message instead. Only assert if
7747 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7749 o Minor features (build):
7750 - New --disable-system-torrc compile-time option to prevent Tor from
7751 looking for the system-wide torrc or torrc-defaults files.
7752 Resolves ticket 13037.
7754 o Minor features (client):
7755 - Clients are now willing to send optimistic data (before they
7756 receive a 'connected' cell) to relays of any version. (Relays
7757 without support for optimistic data are no longer supported on the
7758 Tor network.) Resolves ticket 13153.
7760 o Minor features (client):
7761 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
7762 is enabled, reject requests with IP addresses as hostnames.
7763 Resolves ticket 13315.
7765 o Minor features (controller):
7766 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
7767 write an unscheduled heartbeat message to the log. Implements
7769 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
7770 events so controllers can observe circuit isolation inputs. Closes
7772 - ControlPort now supports the unix:/path/to/socket syntax as an
7773 alternative to the ControlSocket option, for consistency with
7774 SocksPort and HiddenServicePort. Closes ticket 14451.
7775 - New "GETINFO bw-event-cache" to get information about recent
7776 bandwidth events. Closes ticket 14128. Useful for controllers to
7777 get recent bandwidth history after the fix for ticket 13988.
7778 - Messages about problems in the bootstrap process now include
7779 information about the server we were trying to connect to when we
7780 noticed the problem. Closes ticket 15006.
7782 o Minor features (Denial of service resistance):
7783 - Count the total number of bytes used storing hidden service
7784 descriptors against the value of MaxMemInQueues. If we're low on
7785 memory, and more than 20% of our memory is used holding hidden
7786 service descriptors, free them until no more than 10% of our
7787 memory holds hidden service descriptors. Free the least recently
7788 fetched descriptors first. Resolves ticket 13806.
7789 - When we have recently been under memory pressure (over 3/4 of
7790 MaxMemInQueues is allocated), then allocate smaller zlib objects
7791 for small requests. Closes ticket 11791.
7793 o Minor features (directory authorities):
7794 - Don't list relays with a bandwidth estimate of 0 in the consensus.
7795 Implements a feature proposed during discussion of bug 13000.
7796 - In tor-gencert, report an error if the user provides the same
7797 argument more than once.
7798 - If a directory authority can't find a best consensus method in the
7799 votes that it holds, it now falls back to its favorite consensus
7800 method. Previously, it fell back to method 1. Neither of these is
7801 likely to get enough signatures, but "fall back to favorite"
7802 doesn't require us to maintain support an obsolete consensus
7803 method. Implements part of proposal 215.
7805 o Minor features (geoip):
7806 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7807 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7810 o Minor features (guard nodes):
7811 - Reduce the time delay before saving guard status to disk from 10
7812 minutes to 30 seconds (or from one hour to 10 minutes if
7813 AvoidDiskWrites is set). Closes ticket 12485.
7815 o Minor features (heartbeat):
7816 - On relays, report how many connections we negotiated using each
7817 version of the Tor link protocols. This information will let us
7818 know if removing support for very old versions of the Tor
7819 protocols is harming the network. Closes ticket 15212.
7821 o Minor features (hidden service):
7822 - Make Sybil attacks against hidden services harder by changing the
7823 minimum time required to get the HSDir flag from 25 hours up to 96
7824 hours. Addresses ticket 14149.
7825 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
7826 services to disable the anti-scanning feature introduced in
7827 0.2.6.2-alpha. With this option not set, a connection to an
7828 unlisted port closes the circuit. With this option set, only a
7829 RELAY_DONE cell is sent. Closes ticket 14084.
7830 - When re-enabling the network, don't try to build introduction
7831 circuits until we have successfully built a circuit. This makes
7832 hidden services come up faster when the network is re-enabled.
7833 Patch from "akwizgran". Closes ticket 13447.
7834 - When we fail to retrieve a hidden service descriptor, send the
7835 controller an "HS_DESC FAILED" controller event. Implements
7837 - New HiddenServiceDirGroupReadable option to cause hidden service
7838 directories and hostname files to be created group-readable. Patch
7839 from "anon", David Stainton, and "meejah". Closes ticket 11291.
7841 o Minor features (interface):
7842 - Implement "-f -" command-line option to read torrc configuration
7843 from standard input, if you don't want to store the torrc file in
7844 the file system. Implements feature 13865.
7846 o Minor features (logging):
7847 - Add a count of unique clients to the bridge heartbeat message.
7848 Resolves ticket 6852.
7849 - Suppress "router info incompatible with extra info" message when
7850 reading extrainfo documents from cache. (This message got loud
7851 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
7853 - Elevate hidden service authorized-client message from DEBUG to
7854 INFO. Closes ticket 14015.
7855 - On Unix-like systems, you can now use named pipes as the target of
7856 the Log option, and other options that try to append to files.
7857 Closes ticket 12061. Patch from "carlo von lynX".
7858 - When opening a log file at startup, send it every log message that
7859 we generated between startup and opening it. Previously, log
7860 messages that were generated before opening the log file were only
7861 logged to stdout. Closes ticket 6938.
7862 - Add a TruncateLogFile option to overwrite logs instead of
7863 appending to them. Closes ticket 5583.
7864 - Quiet some log messages in the heartbeat and at startup. Closes
7867 o Minor features (portability, Solaris):
7868 - Threads are no longer disabled by default on Solaris; we believe
7869 that the versions of Solaris with broken threading support are all
7870 obsolete by now. Resolves ticket 9495.
7872 o Minor features (relay):
7873 - Re-check our address after we detect a changed IP address from
7874 getsockname(). This ensures that the controller command "GETINFO
7875 address" will report the correct value. Resolves ticket 11582.
7877 - A new AccountingRule option lets Relays set whether they'd like
7878 AccountingMax to be applied separately to inbound and outbound
7879 traffic, or applied to the sum of inbound and outbound traffic.
7880 Resolves ticket 961. Patch by "chobe".
7881 - When identity keypair is generated for first time, log a
7882 congratulatory message that links to the new relay lifecycle
7883 document. Implements feature 10427.
7885 o Minor features (security, memory wiping):
7886 - Ensure we securely wipe keys from memory after
7887 crypto_digest_get_digest and init_curve25519_keypair_from_file
7888 have finished using them. Resolves ticket 13477.
7890 o Minor features (security, out-of-memory handling):
7891 - When handling an out-of-memory condition, allocate less memory for
7892 temporary data structures. Fixes issue 10115.
7893 - When handling an out-of-memory condition, consider more types of
7894 buffers, including those on directory connections, and zlib
7895 buffers. Resolves ticket 11792.
7897 o Minor features (stability):
7898 - Add assertions in our hash-table iteration code to check for
7899 corrupted values that could cause infinite loops. Closes
7902 o Minor features (systemd):
7903 - Various improvements and modernizations in systemd hardening
7904 support. Closes ticket 13805. Patch from Craig Andrews.
7905 - Where supported, when running with systemd, report successful
7906 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
7907 - When running with systemd, support systemd watchdog messages. Part
7908 of ticket 11016. Patch by Michael Scherer.
7910 o Minor features (testing networks):
7911 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
7912 the "Exit" flag regardless of their uptime, bandwidth, or exit
7913 policy. TestingTorNetwork must be set for this option to have any
7914 effect. Previously, authorities would take up to 35 minutes to
7915 give nodes the Exit flag in a test network. Partially implements
7917 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
7918 and the default on a testing network to 2 minutes. Drop the
7919 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
7920 keep the default on a testing network at 30 seconds. This reduces
7921 HS bootstrap time to around 25 seconds. Also, change the default
7922 time in test-network.sh to match. Closes ticket 13401. Patch
7924 - Create TestingDirAuthVoteHSDir to correspond to
7925 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
7926 HSDir flag for the listed relays regardless of uptime or ORPort
7927 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
7928 Partial implementation for ticket 14067. Patch by "teor".
7930 o Minor features (tor2web mode):
7931 - Introduce the config option Tor2webRendezvousPoints, which allows
7932 clients in Tor2webMode to select a specific Rendezvous Point to be
7933 used in HS circuits. This might allow better performance for
7934 Tor2Web nodes. Implements ticket 12844.
7936 o Minor features (transparent proxy):
7937 - Update the transparent proxy option checks to allow for both ipfw
7938 and pf on OS X. Closes ticket 14002.
7939 - Use the correct option when using IPv6 with transparent proxy
7940 support on Linux. Resolves 13808. Patch by Francisco Blas
7943 o Minor features (validation):
7944 - Check all date/time values passed to tor_timegm and
7945 parse_rfc1123_time for validity, taking leap years into account.
7946 Improves HTTP header validation. Implemented with bug 13476.
7947 - In correct_tm(), limit the range of values returned by system
7948 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
7949 This means we don't have to deal with negative or too large dates,
7950 even if a clock is wrong. Otherwise we might fail to read a file
7951 written by us which includes such a date. Fixes bug 13476.
7952 - Stop allowing invalid address patterns like "*/24" that contain
7953 both a wildcard address and a bit prefix length. This affects all
7954 our address-range parsing code. Fixes bug 7484; bugfix
7957 o Minor bugfixes (bridge clients):
7958 - When configured to use a bridge without an identity digest (not
7959 recommended), avoid launching an extra channel to it when
7960 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
7962 o Minor bugfixes (bridges):
7963 - When DisableNetwork is set, do not launch pluggable transport
7964 plugins, and if any are running, terminate them. Fixes bug 13213;
7965 bugfix on 0.2.3.6-alpha.
7967 o Minor bugfixes (C correctness):
7968 - Fix several instances of possible integer overflow/underflow/NaN.
7969 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
7971 - In circuit_build_times_calculate_timeout() in circuitstats.c,
7972 avoid dividing by zero in the pareto calculations. This traps
7973 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
7975 - Fix an integer overflow in format_time_interval(). Fixes bug
7976 13393; bugfix on 0.2.0.10-alpha.
7977 - Set the correct day of year value when the system's localtime(_r)
7978 or gmtime(_r) functions fail to set struct tm. Not externally
7979 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
7980 - Avoid unlikely signed integer overflow in tor_timegm on systems
7981 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
7983 o Minor bugfixes (certificate handling):
7984 - If an authority operator accidentally makes a signing certificate
7985 with a future publication time, do not discard its real signing
7986 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
7987 - Remove any old authority certificates that have been superseded
7988 for at least two days. Previously, we would keep superseded
7989 certificates until they expired, if they were published close in
7990 time to the certificate that superseded them. Fixes bug 11454;
7991 bugfix on 0.2.1.8-alpha.
7993 o Minor bugfixes (client):
7994 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
7995 BadExit flag are not considered worthy candidates. Fixes bug
7996 13066; bugfix on 0.1.2.3-alpha.
7997 - Use the consensus schedule for downloading consensuses, and not
7998 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
7999 - Handle unsupported or malformed SOCKS5 requests properly by
8000 responding with the appropriate error message before closing the
8001 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8003 o Minor bugfixes (client, automapping):
8004 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8005 no value follows the option. Fixes bug 14142; bugfix on
8006 0.2.4.7-alpha. Patch by "teor".
8007 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8008 14195; bugfix on 0.1.0.1-rc.
8009 - Prevent changes to other options from removing the wildcard value
8010 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
8012 - Allow MapAddress and AutomapHostsOnResolve to work together when
8013 an address is mapped into another address type (like .onion) that
8014 must be automapped at resolve time. Fixes bug 7555; bugfix
8017 o Minor bugfixes (client, bridges):
8018 - When we are using bridges and we had a network connectivity
8019 problem, only retry connecting to our currently configured
8020 bridges, not all bridges we know about and remember using. Fixes
8021 bug 14216; bugfix on 0.2.2.17-alpha.
8023 o Minor bugfixes (client, DNS):
8024 - Report the correct cached DNS expiration times on SOCKS port or in
8025 DNS replies. Previously, we would report everything as "never
8026 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8027 - Avoid a small memory leak when we find a cached answer for a
8028 reverse DNS lookup in a client-side DNS cache. (Remember, client-
8029 side DNS caching is off by default, and is not recommended.) Fixes
8030 bug 14259; bugfix on 0.2.0.1-alpha.
8032 o Minor bugfixes (client, IPv6):
8033 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
8034 flag is not set; and not because the NoIPv4Traffic flag was set.
8035 Previously we'd looked at the NoIPv4Traffic flag for both types of
8036 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
8038 o Minor bugfixes (client, microdescriptors):
8039 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
8040 computing which microdescriptors to download. This keeps us from
8041 erroneous download behavior if two microdescriptor digests ever
8042 have the same first 160 bits. Fixes part of bug 13399; bugfix
8044 - Reset a router's status if its microdescriptor digest changes,
8045 even if the first 160 bits remain the same. Fixes part of bug
8046 13399; bugfix on 0.2.3.1-alpha.
8048 o Minor bugfixes (client, torrc):
8049 - Stop modifying the value of our DirReqStatistics torrc option just
8050 because we're not a bridge or relay. This bug was causing Tor
8051 Browser users to write "DirReqStatistics 0" in their torrc files
8052 as if they had chosen to change the config. Fixes bug 4244; bugfix
8054 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8055 that our options have changed every time we SIGHUP. Fixes bug
8056 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8058 o Minor bugfixes (compilation):
8059 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
8061 - Silence clang warnings under --enable-expensive-hardening,
8062 including implicit truncation of 64 bit values to 32 bit, const
8063 char assignment to self, tautological compare, and additional
8064 parentheses around equality tests. Fixes bug 13577; bugfix
8066 - Fix a clang warning about checking whether an address in the
8067 middle of a structure is NULL. Fixes bug 14001; bugfix
8069 - The address of an array in the middle of a structure will always
8070 be non-NULL. clang recognises this and complains. Disable the
8071 tautologous and redundant check to silence this warning. Fixes bug
8072 14001; bugfix on 0.2.1.2-alpha.
8073 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
8074 Addresses ticket 14188.
8075 - Build without warnings with the stock OpenSSL srtp.h header, which
8076 has a duplicate declaration of SSL_get_selected_srtp_profile().
8077 Fixes bug 14220; this is OpenSSL's bug, not ours.
8078 - Do not compile any code related to Tor2Web mode when Tor2Web mode
8079 is not enabled at compile time. Previously, this code was included
8080 in a disabled state. See discussion on ticket 12844.
8081 - Allow our configure script to build correctly with autoconf 2.62
8082 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
8083 - Improve the error message from ./configure to make it clear that
8084 when asciidoc has not been found, the user will have to either add
8085 --disable-asciidoc argument or install asciidoc. Resolves
8088 o Minor bugfixes (controller):
8089 - Report "down" in response to the "GETINFO entry-guards" command
8090 when relays are down with an unreachable_since value. Previously,
8091 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
8092 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
8093 14116; bugfix on 0.2.2.9-alpha.
8095 o Minor bugfixes (controller):
8096 - Return an error when the second or later arguments of the
8097 "setevents" controller command are invalid events. Previously we
8098 would return success while silently skipping invalid events. Fixes
8099 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8101 o Minor bugfixes (directory authority):
8102 - Allow directory authorities to fetch more data from one another if
8103 they find themselves missing lots of votes. Previously, they had
8104 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8105 bugfix on 0.1.2.5-alpha.
8106 - Do not attempt to download extrainfo documents which we will be
8107 unable to validate with a matching server descriptor. Fixes bug
8108 13762; bugfix on 0.2.0.1-alpha.
8109 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
8110 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
8111 - Enlarge the buffer to read bwauth generated files to avoid an
8112 issue when parsing the file in dirserv_read_measured_bandwidths().
8113 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8114 - When running as a v3 directory authority, advertise that you serve
8115 extra-info documents so that clients who want them can find them
8116 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8118 o Minor bugfixes (directory system):
8119 - Always believe that v3 directory authorities serve extra-info
8120 documents, whether they advertise "caches-extra-info" or not.
8121 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8122 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
8123 Previously, directories offering BRIDGE_DIRINFO and some other
8124 flag (i.e. microdescriptors or extrainfo) would be ignored when
8125 looking for bridges. Partially fixes bug 13163; bugfix
8128 o Minor bugfixes (file handling):
8129 - Stop failing when key files are zero-length. Instead, generate new
8130 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
8131 on all versions of Tor. Patch by "teor".
8132 - Stop generating a fresh .old RSA onion key file when the .old file
8133 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
8134 - Avoid overwriting .old key files with empty key files.
8135 - Skip loading zero-length extrainfo store, router store, stats,
8136 state, and key files.
8137 - Avoid crashing when trying to reload a torrc specified as a
8138 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
8141 o Minor bugfixes (hidden services):
8142 - Close the introduction circuit when we have no more usable intro
8143 points, instead of waiting for it to time out. This also ensures
8144 that no follow-up HS descriptor fetch is triggered when the
8145 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
8146 - When fetching a hidden service descriptor for a down service that
8147 was recently up, do not keep refetching until we try the same
8148 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
8149 - Correctly send a controller event when we find that a rendezvous
8150 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
8151 - Pre-check directory permissions for new hidden-services to avoid
8152 at least one case of "Bug: Acting on config options left us in a
8153 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
8154 - When fetching hidden service descriptors, we now check not only
8155 for whether we got the hidden service we had in mind, but also
8156 whether we got the particular descriptors we wanted. This prevents
8157 a class of inefficient but annoying DoS attacks by hidden service
8158 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
8161 o Minor bugfixes (Linux seccomp2 sandbox):
8162 - Make transparent proxy support work along with the seccomp2
8163 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
8164 by Francisco Blas Izquierdo Riera.
8165 - Fix a memory leak in tor-resolve when running with the sandbox
8166 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
8167 - Allow glibc fatal errors to be sent to stderr before Tor exits.
8168 Previously, glibc would try to write them to /dev/tty, and the
8169 sandbox would trap the call and make Tor exit prematurely. Fixes
8170 bug 14759; bugfix on 0.2.5.1-alpha.
8172 o Minor bugfixes (logging):
8173 - Avoid crashing when there are more log domains than entries in
8174 domain_list. Bugfix on 0.2.3.1-alpha.
8175 - Downgrade warnings about RSA signature failures to info log level.
8176 Emit a warning when an extra info document is found incompatible
8177 with a corresponding router descriptor. Fixes bug 9812; bugfix
8179 - Make connection_ap_handshake_attach_circuit() log the circuit ID
8180 correctly. Fixes bug 13701; bugfix on 0.0.6.
8182 o Minor bugfixes (networking):
8183 - Check for orconns and use connection_or_close_for_error() rather
8184 than connection_mark_for_close() directly in the getsockopt()
8185 failure case of connection_handle_write_impl(). Fixes bug 11302;
8186 bugfix on 0.2.4.4-alpha.
8188 o Minor bugfixes (parsing):
8189 - Stop accepting milliseconds (or other junk) at the end of
8190 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
8191 - Support two-number and three-number version numbers correctly, in
8192 case we change the Tor versioning system in the future. Fixes bug
8193 13661; bugfix on 0.0.8pre1.
8195 o Minor bugfixes (portability):
8196 - Fix the ioctl()-based network interface lookup code so that it
8197 will work on systems that have variable-length struct ifreq, for
8199 - Use the correct datatype in the SipHash-2-4 function to prevent
8200 compilers from assuming any sort of alignment. Fixes bug 15436;
8201 bugfix on 0.2.5.3-alpha.
8203 o Minor bugfixes (preventative security, C safety):
8204 - When reading a hexadecimal, base-32, or base-64 encoded value from
8205 a string, always overwrite the whole output buffer. This prevents
8206 some bugs where we would look at (but fortunately, not reveal)
8207 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8209 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
8210 just the part that's used. This makes it harder for data leak bugs
8211 to occur in the event of other programming failures. Resolves
8214 o Minor bugfixes (relay):
8215 - When generating our family list, remove spaces from around the
8216 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
8217 - If our previous bandwidth estimate was 0 bytes, allow publishing a
8218 new relay descriptor immediately. Fixes bug 13000; bugfix
8221 o Minor bugfixes (shutdown):
8222 - When shutting down, always call event_del() on lingering read or
8223 write events before freeing them. Otherwise, we risk double-frees
8224 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
8227 o Minor bugfixes (small memory leaks):
8228 - Avoid leaking memory when using IPv6 virtual address mappings.
8229 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
8232 o Minor bugfixes (statistics):
8233 - Increase period over which bandwidth observations are aggregated
8234 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8236 o Minor bugfixes (systemd support):
8237 - Run correctly under systemd with the RunAsDaemon option set. Fixes
8238 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
8239 - Inform the systemd supervisor about more changes in the Tor
8240 process status. Implements part of ticket 14141. Patch from
8243 o Minor bugfixes (testing networks):
8244 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
8245 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
8246 - Stop using the default authorities in networks which provide both
8247 AlternateDirAuthority and AlternateBridgeAuthority. Partially
8248 fixes bug 13163; bugfix on 0.2.0.13-alpha.
8250 o Minor bugfixes (testing networks, fast startup):
8251 - Allow Tor to build circuits using a consensus with no exits. If
8252 the consensus has no exits (typical of a bootstrapping test
8253 network), allow Tor to build circuits once enough descriptors have
8254 been downloaded. This assists in bootstrapping a testing Tor
8255 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
8257 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
8258 header to directory servers. This allows us to obtain consensuses
8259 promptly when the consensus interval is very short. This assists
8260 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
8261 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
8262 - Stop assuming that private addresses are local when checking
8263 reachability in a TestingTorNetwork. Instead, when testing, assume
8264 all OR connections are remote. (This is necessary due to many test
8265 scenarios running all relays on localhost.) This assists in
8266 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
8267 0.1.0.1-rc. Patch by "teor".
8268 - Avoid building exit circuits from a consensus with no exits. Now
8269 thanks to our fix for 13718, we accept a no-exit network as not
8270 wholly lost, but we need to remember not to try to build exit
8271 circuits on it. Closes ticket 13814; patch by "teor".
8272 - Stop requiring exits to have non-zero bandwithcapacity in a
8273 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
8274 ignore exit bandwidthcapacity. This assists in bootstrapping a
8275 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
8276 on 0.2.0.3-alpha. Patch by "teor".
8277 - Add "internal" to some bootstrap statuses when no exits are
8278 available. If the consensus does not contain Exits, Tor will only
8279 build internal circuits. In this case, relevant statuses will
8280 contain the word "internal" as indicated in the Tor control-
8281 spec.txt. When bootstrap completes, Tor will be ready to build
8282 internal circuits. If a future consensus contains Exits, exit
8283 circuits may become available. Fixes part of bug 13718; bugfix on
8284 0.2.4.10-alpha. Patch by "teor".
8285 - Decrease minimum consensus interval to 10 seconds when
8286 TestingTorNetwork is set, or 5 seconds for the first consensus.
8287 Fix assumptions throughout the code that assume larger intervals.
8288 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
8290 - Avoid excluding guards from path building in minimal test
8291 networks, when we're in a test network and excluding guards would
8292 exclude all relays. This typically occurs in incredibly small tor
8293 networks, and those using "TestingAuthVoteGuard *". Fixes part of
8294 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
8296 o Minor bugfixes (testing):
8297 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
8298 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
8299 - Stop spawn test failures due to a race condition between the
8300 SIGCHLD handler updating the process status, and the test reading
8301 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
8302 - Avoid passing an extra backslash when creating a temporary
8303 directory for running the unit tests on Windows. Fixes bug 12392;
8304 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
8306 o Minor bugfixes (TLS):
8307 - Check more thoroughly throughout the TLS code for possible
8308 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
8310 o Minor bugfixes (transparent proxy):
8311 - Use getsockname, not getsockopt, to retrieve the address for a
8312 TPROXY-redirected connection. Fixes bug 13796; bugfix
8315 o Minor bugfixes (windows):
8316 - Remove code to special-case handling of NTE_BAD_KEYSET when
8317 acquiring windows CryptoAPI context. This error can't actually
8318 occur for the parameters we're providing. Fixes bug 10816; bugfix
8321 o Minor bugfixes (zlib):
8322 - Avoid truncating a zlib stream when trying to finalize it with an
8323 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
8325 o Code simplification and refactoring:
8326 - Change the entry_is_live() function to take named bitfield
8327 elements instead of an unnamed list of booleans. Closes
8329 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
8330 Resolves ticket 12205.
8331 - Use calloc and reallocarray functions instead of multiply-
8332 then-malloc. This makes it less likely for us to fall victim to an
8333 integer overflow attack when allocating. Resolves ticket 12855.
8334 - Use the standard macro name SIZE_MAX, instead of our
8336 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
8337 functions which take them as arguments. Replace 0 with NO_DIRINFO
8338 in a function call for clarity. Seeks to prevent future issues
8340 - Avoid 4 null pointer errors under clang static analysis by using
8341 tor_assert() to prove that the pointers aren't null. Fixes
8343 - Rework the API of policies_parse_exit_policy() to use a bitmask to
8344 represent parsing options, instead of a confusing mess of
8345 booleans. Resolves ticket 8197.
8346 - Introduce a helper function to parse ExitPolicy in
8347 or_options_t structure.
8348 - Move fields related to isolating and configuring client ports into
8349 a shared structure. Previously, they were duplicated across
8350 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
8351 to copy them correctly had been the cause of at least one bug in
8352 the past. Closes ticket 8546.
8353 - Refactor the get_interface_addresses_raw() doom-function into
8354 multiple smaller and simpler subfunctions. Cover the resulting
8355 subfunctions with unit-tests. Fixes a significant portion of
8357 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
8358 only for version <= 0.2.2.24 which is now deprecated. Closes
8360 - Remove a test for a long-defunct broken version-one
8362 - Refactor main loop to extract the 'loop' part. This makes it
8363 easier to run Tor under Shadow. Closes ticket 15176.
8364 - Stop using can_complete_circuits as a global variable; access it
8365 with a function instead.
8366 - Avoid using operators directly as macro arguments: this lets us
8367 apply coccinelle transformations to our codebase more directly.
8368 Closes ticket 13172.
8369 - Combine the functions used to parse ClientTransportPlugin and
8370 ServerTransportPlugin into a single function. Closes ticket 6456.
8371 - Add inline functions and convenience macros for inspecting channel
8372 state. Refactor the code to use convenience macros instead of
8373 checking channel state directly. Fixes issue 7356.
8374 - Document all members of was_router_added_t and rename
8375 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
8376 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
8377 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
8378 constant instead of hardcoded value. Fixes issue 13840.
8379 - Refactor our generic strmap and digestmap types into a single
8380 implementation, so that we can add a new digest256map
8384 - Add a doc/TUNING document with tips for handling large numbers of
8385 TCP connections when running busy Tor relay. Update the warning
8386 message to point to this file when running out of sockets
8387 operating system is allowing to use simultaneously. Resolves
8389 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
8390 for writing the OpenBSD-specific tips. Resolves ticket 13702.
8391 - Make the tor-resolve documentation match its help string and its
8392 options. Resolves part of ticket 14325.
8393 - Log a more useful error message from tor-resolve when failing to
8394 look up a hidden service address. Resolves part of ticket 14325.
8395 - Document the bridge-authority-only 'networkstatus-bridges' file.
8396 Closes ticket 13713; patch from "tom".
8397 - Fix typo in PredictedPortsRelevanceTime option description in
8398 manpage. Resolves issue 13707.
8399 - Stop suggesting that users specify relays by nickname: it isn't a
8400 good idea. Also, properly cross-reference how to specify relays in
8401 all parts of manual documenting options that take a list of
8402 relays. Closes ticket 13381.
8403 - Clarify the HiddenServiceDir option description in manpage to make
8404 it clear that relative paths are taken with respect to the current
8405 working directory. Also clarify that this behavior is not
8406 guaranteed to remain indefinitely. Fixes issue 13913.
8408 o Distribution (systemd):
8409 - systemd unit file: only allow tor to write to /var/lib/tor and
8410 /var/log/tor. The rest of the filesystem is accessible for reading
8411 only. Patch by intrigeri; resolves ticket 12751.
8412 - systemd unit file: ensure that the process and all its children
8413 can never gain new privileges. Patch by intrigeri; resolves
8415 - systemd unit file: set up /var/run/tor as writable for the Tor
8416 service. Patch by intrigeri; resolves ticket 13196.
8418 o Downgraded warnings:
8419 - Don't warn when we've attempted to contact a relay using the wrong
8420 ntor onion key. Closes ticket 9635.
8423 - Remove some lingering dead code that once supported mempools.
8424 Mempools were disabled by default in 0.2.5, and removed entirely
8425 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
8428 o Removed features (directory authorities):
8429 - Remove code that prevented authorities from listing Tor relays
8430 affected by CVE-2011-2769 as guards. These relays are already
8431 rejected altogether due to the minimum version requirement of
8432 0.2.3.16-alpha. Closes ticket 13152.
8433 - The "AuthDirRejectUnlisted" option no longer has any effect, as
8434 the fingerprints file (approved-routers) has been deprecated.
8435 - Directory authorities do not support being Naming dirauths anymore.
8436 The "NamingAuthoritativeDir" config option is now obsolete.
8437 - Directory authorities do not support giving out the BadDirectory
8439 - Directory authorities no longer advertise or support consensus
8440 methods 1 through 12 inclusive. These consensus methods were
8441 obsolete and/or insecure: maintaining the ability to support them
8442 served no good purpose. Implements part of proposal 215; closes
8446 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
8447 longer silently accepted as an alias for "ExitNodes".
8448 - The --enable-mempool and --enable-buf-freelists options, which
8449 were originally created to work around bad malloc implementations,
8450 no longer exist. They were off-by-default in 0.2.5. Closes
8452 - We no longer remind the user about configuration options that have
8453 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
8454 - Remove our old, non-weighted bandwidth-based node selection code.
8455 Previously, we used it as a fallback when we couldn't perform
8456 weighted bandwidth-based node selection. But that would only
8457 happen in the cases where we had no consensus, or when we had a
8458 consensus generated by buggy or ancient directory authorities. In
8459 either case, it's better to use the more modern, better maintained
8460 algorithm, with reasonable defaults for the weights. Closes
8462 - Remove the --disable-curve25519 configure option. Relays and
8463 clients now are required to support curve25519 and the
8465 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
8466 used to be deprecated synonyms for "StrictNodes", are now marked
8467 obsolete. Resolves ticket 12226.
8468 - Clients don't understand the BadDirectory flag in the consensus
8469 anymore, and ignore it.
8471 o Removed platform support:
8472 - We no longer include special code to build on Windows CE; as far
8473 as we know, nobody has used Tor on Windows CE in a very long time.
8474 Closes ticket 11446.
8476 o Testing (test-network.sh):
8477 - Stop using "echo -n", as some shells' built-in echo doesn't
8478 support "-n". Instead, use "/bin/echo -n". Partially fixes
8480 - Stop an apparent test-network hang when used with make -j2. Fixes
8482 - Add a --delay option to test-network.sh, which configures the
8483 delay before the chutney network tests for data transmission.
8484 Partially implements ticket 13161.
8487 - Test that tor does not fail when key files are zero-length. Check
8488 that tor generates new keys, and overwrites the empty key files.
8489 - Test that tor generates new keys when keys are missing
8490 (existing behavior).
8491 - Test that tor does not overwrite key files that already contain
8492 data (existing behavior). Tests bug 13111. Patch by "teor".
8493 - New "make test-stem" target to run stem integration tests.
8494 Requires that the "STEM_SOURCE_DIR" environment variable be set.
8495 Closes ticket 14107.
8496 - Make the test_cmdline_args.py script work correctly on Windows.
8497 Patch from Gisle Vanem.
8498 - Move the slower unit tests into a new "./src/test/test-slow"
8499 binary that can be run independently of the other tests. Closes
8501 - New tests for many parts of channel, relay, and circuitmux
8502 functionality. Code by Andrea; part of 9262.
8503 - New tests for parse_transport_line(). Part of ticket 6456.
8504 - In the unit tests, use chgrp() to change the group of the unit
8505 test temporary directory to the current user, so that the sticky
8506 bit doesn't interfere with tests that check directory groups.
8508 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8510 - Refactor the function that chooses guard nodes so that it can more
8511 easily be tested; write some tests for it.
8512 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
8513 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
8514 - Create unit tests for format_time_interval(). With bug 13393.
8515 - Add unit tests for tor_timegm signed overflow, tor_timegm and
8516 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
8517 tests (visible) fixes in bug 13476.
8518 - Add a "coverage-html" make target to generate HTML-visualized
8519 coverage results when building with --enable-coverage. (Requires
8520 lcov.) Patch from Kevin Murray.
8521 - Enable the backtrace handler (where supported) when running the
8523 - Revise all unit tests that used the legacy test_* macros to
8524 instead use the recommended tt_* macros. This patch was generated
8525 with coccinelle, to avoid manual errors. Closes ticket 13119.
8527 Changes in version 0.2.5.11 - 2015-03-17
8528 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
8530 It backports several bugfixes from the 0.2.6 branch, including a
8531 couple of medium-level security fixes for relays and exit nodes.
8532 It also updates the list of directory authorities.
8534 o Directory authority changes:
8535 - Remove turtles as a directory authority.
8536 - Add longclaw as a new (v3) directory authority. This implements
8537 ticket 13296. This keeps the directory authority count at 9.
8538 - The directory authority Faravahar has a new IP address. This
8539 closes ticket 14487.
8541 o Major bugfixes (crash, OSX, security):
8542 - Fix a remote denial-of-service opportunity caused by a bug in
8543 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8546 o Major bugfixes (relay, stability, possible security):
8547 - Fix a bug that could lead to a relay crashing with an assertion
8548 failure if a buffer of exactly the wrong layout was passed to
8549 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8550 0.2.0.10-alpha. Patch from 'cypherpunks'.
8551 - Do not assert if the 'data' pointer on a buffer is advanced to the
8552 very end of the buffer; log a BUG message instead. Only assert if
8553 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8555 o Major bugfixes (exit node stability):
8556 - Fix an assertion failure that could occur under high DNS load.
8557 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8558 diagnosed and fixed by "cypherpunks".
8560 o Major bugfixes (Linux seccomp2 sandbox):
8561 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8562 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8563 0.2.5.1-alpha. Patch from "sanic".
8565 o Minor features (controller):
8566 - New "GETINFO bw-event-cache" to get information about recent
8567 bandwidth events. Closes ticket 14128. Useful for controllers to
8568 get recent bandwidth history after the fix for ticket 13988.
8570 o Minor features (geoip):
8571 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8572 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8575 o Minor bugfixes (client, automapping):
8576 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8577 no value follows the option. Fixes bug 14142; bugfix on
8578 0.2.4.7-alpha. Patch by "teor".
8579 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8580 14195; bugfix on 0.1.0.1-rc.
8582 o Minor bugfixes (compilation):
8583 - Build without warnings with the stock OpenSSL srtp.h header, which
8584 has a duplicate declaration of SSL_get_selected_srtp_profile().
8585 Fixes bug 14220; this is OpenSSL's bug, not ours.
8587 o Minor bugfixes (directory authority):
8588 - Allow directory authorities to fetch more data from one another if
8589 they find themselves missing lots of votes. Previously, they had
8590 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8591 bugfix on 0.1.2.5-alpha.
8592 - Enlarge the buffer to read bwauth generated files to avoid an
8593 issue when parsing the file in dirserv_read_measured_bandwidths().
8594 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8596 o Minor bugfixes (statistics):
8597 - Increase period over which bandwidth observations are aggregated
8598 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8600 o Minor bugfixes (preventative security, C safety):
8601 - When reading a hexadecimal, base-32, or base-64 encoded value from
8602 a string, always overwrite the whole output buffer. This prevents
8603 some bugs where we would look at (but fortunately, not reveal)
8604 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8608 Changes in version 0.2.4.26 - 2015-03-17
8609 Tor 0.2.4.26 includes an updated list of directory authorities. It
8610 also backports a couple of stability and security bugfixes from 0.2.5
8613 o Directory authority changes:
8614 - Remove turtles as a directory authority.
8615 - Add longclaw as a new (v3) directory authority. This implements
8616 ticket 13296. This keeps the directory authority count at 9.
8617 - The directory authority Faravahar has a new IP address. This
8618 closes ticket 14487.
8620 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
8621 - Fix an assertion failure that could occur under high DNS load.
8622 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8623 diagnosed and fixed by "cypherpunks".
8625 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
8626 - Fix a bug that could lead to a relay crashing with an assertion
8627 failure if a buffer of exactly the wrong layout was passed to
8628 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8629 0.2.0.10-alpha. Patch from 'cypherpunks'.
8630 - Do not assert if the 'data' pointer on a buffer is advanced to the
8631 very end of the buffer; log a BUG message instead. Only assert if
8632 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8634 o Minor features (geoip):
8635 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8636 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8639 Changes in version 0.2.5.10 - 2014-10-24
8640 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
8642 It adds several new security features, including improved
8643 denial-of-service resistance for relays, new compiler hardening
8644 options, and a system-call sandbox for hardened installations on Linux
8645 (requires seccomp2). The controller protocol has several new features,
8646 resolving IPv6 addresses should work better than before, and relays
8647 should be a little more CPU-efficient. We've added support for more
8648 OpenBSD and FreeBSD transparent proxy types. We've improved the build
8649 system and testing infrastructure to allow unit testing of more parts
8650 of the Tor codebase. Finally, we've addressed several nagging pluggable
8651 transport usability issues, and included numerous other small bugfixes
8652 and features mentioned below.
8654 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
8655 have accumulated many known flaws; everyone should upgrade.
8657 o Major features (security):
8658 - The ntor handshake is now on-by-default, no matter what the
8659 directory authorities recommend. Implements ticket 8561.
8660 - Make the "tor-gencert" tool used by directory authority operators
8661 create 2048-bit signing keys by default (rather than 1024-bit, since
8662 1024-bit is uncomfortably small these days). Addresses ticket 10324.
8663 - Warn about attempts to run hidden services and relays in the same
8664 process: that's probably not a good idea. Closes ticket 12908.
8665 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8666 today support TLS 1.0 or later, so we can safely turn off support
8667 for this old (and insecure) protocol. Fixes bug 13426.
8669 o Major features (relay security, DoS-resistance):
8670 - When deciding whether we have run out of memory and we need to
8671 close circuits, also consider memory allocated in buffers for
8672 streams attached to each circuit.
8674 This change, which extends an anti-DoS feature introduced in
8675 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
8676 better resist more memory-based DoS attacks than before. Since the
8677 MaxMemInCellQueues option now applies to all queues, it is renamed
8678 to MaxMemInQueues. This feature fixes bug 10169.
8679 - Avoid hash-flooding denial-of-service attacks by using the secure
8680 SipHash-2-4 hash function for our hashtables. Without this
8681 feature, an attacker could degrade performance of a targeted
8682 client or server by flooding their data structures with a large
8683 number of entries to be stored at the same hash table position,
8684 thereby slowing down the Tor instance. With this feature, hash
8685 table positions are derived from a randomized cryptographic key,
8686 and an attacker cannot predict which entries will collide. Closes
8688 - If you don't specify MaxMemInQueues yourself, Tor now tries to
8689 pick a good value based on your total system memory. Previously,
8690 the default was always 8 GB. You can still override the default by
8691 setting MaxMemInQueues yourself. Resolves ticket 11396.
8693 o Major features (bridges and pluggable transports):
8694 - Add support for passing arguments to managed pluggable transport
8695 proxies. Implements ticket 3594.
8696 - Bridges now track GeoIP information and the number of their users
8697 even when pluggable transports are in use, and report usage
8698 statistics in their extra-info descriptors. Resolves tickets 4773
8700 - Don't launch pluggable transport proxies if we don't have any
8701 bridges configured that would use them. Now we can list many
8702 pluggable transports, and Tor will dynamically start one when it
8703 hears a bridge address that needs it. Resolves ticket 5018.
8704 - The bridge directory authority now assigns status flags (Stable,
8705 Guard, etc) to bridges based on thresholds calculated over all
8706 Running bridges. Now bridgedb can finally make use of its features
8707 to e.g. include at least one Stable bridge in its answers. Fixes
8710 o Major features (controller):
8711 - Extend ORCONN controller event to include an "ID" parameter,
8712 and add four new controller event types CONN_BW, CIRC_BW,
8713 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
8714 The new events are emitted in private Tor networks only, with the
8715 goal of being able to better track performance and load during
8716 full-network simulations. Implements proposal 218 and ticket 7359.
8718 o Major features (relay performance):
8719 - Speed up server-side lookups of rendezvous and introduction point
8720 circuits by using hashtables instead of linear searches. These
8721 functions previously accounted between 3 and 7% of CPU usage on
8722 some busy relays. Resolves ticket 9841.
8723 - Avoid wasting CPU when extending a circuit over a channel that is
8724 nearly out of circuit IDs. Previously, we would do a linear scan
8725 over possible circuit IDs before finding one or deciding that we
8726 had exhausted our possibilities. Now, we try at most 64 random
8727 circuit IDs before deciding that we probably won't succeed. Fixes
8728 a possible root cause of ticket 11553.
8730 o Major features (seccomp2 sandbox, Linux only):
8731 - Use the seccomp2 syscall filtering facility on Linux to limit
8732 which system calls Tor can invoke. This is an experimental,
8733 Linux-only feature to provide defense-in-depth against unknown
8734 attacks. To try turning it on, set "Sandbox 1" in your torrc
8735 file. Please be ready to report bugs. We hope to add support
8736 for better sandboxing in the future, including more fine-grained
8737 filters, better division of responsibility, and support for more
8738 platforms. This work has been done by Cristian-Matei Toader for
8739 Google Summer of Code. Resolves tickets 11351 and 11465.
8741 o Major features (testing networks):
8742 - Make testing Tor networks bootstrap better: lower directory fetch
8743 retry schedules and maximum interval without directory requests,
8744 and raise maximum download tries. Implements ticket 6752.
8745 - Add make target 'test-network' to run tests on a Chutney network.
8746 Implements ticket 8530.
8748 o Major features (other):
8749 - On some platforms (currently: recent OSX versions, glibc-based
8750 platforms that support the ELF format, and a few other
8751 Unix-like operating systems), Tor can now dump stack traces
8752 when a crash occurs or an assertion fails. By default, traces
8753 are dumped to stderr (if possible) and to any logs that are
8754 reporting errors. Implements ticket 9299.
8756 o Deprecated versions:
8757 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
8758 attention for some while.
8760 o Major bugfixes (security, directory authorities):
8761 - Directory authorities now include a digest of each relay's
8762 identity key as a part of its microdescriptor.
8764 This is a workaround for bug 11743 (reported by "cypherpunks"),
8765 where Tor clients do not support receiving multiple
8766 microdescriptors with the same SHA256 digest in the same
8767 consensus. When clients receive a consensus like this, they only
8768 use one of the relays. Without this fix, a hostile relay could
8769 selectively disable some client use of target relays by
8770 constructing a router descriptor with a different identity and the
8771 same microdescriptor parameters and getting the authorities to
8772 list it in a microdescriptor consensus. This fix prevents an
8773 attacker from causing a microdescriptor collision, because the
8774 router's identity is not forgeable.
8776 o Major bugfixes (openssl bug workaround):
8777 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8778 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
8779 bug 13471. This is a workaround for an OpenSSL bug.
8781 o Major bugfixes (client):
8782 - Perform circuit cleanup operations even when circuit
8783 construction operations are disabled (because the network is
8784 disabled, or because there isn't enough directory information).
8785 Previously, when we were not building predictive circuits, we
8786 were not closing expired circuits either. Fixes bug 8387; bugfix on
8787 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
8788 became more strict about when we have "enough directory information
8791 o Major bugfixes (client, pluggable transports):
8792 - When managing pluggable transports, use OS notification facilities
8793 to learn if they have crashed, and don't attempt to kill any
8794 process that has already exited. Fixes bug 8746; bugfix
8797 o Major bugfixes (relay denial of service):
8798 - Instead of writing destroy cells directly to outgoing connection
8799 buffers, queue them and intersperse them with other outgoing cells.
8800 This can prevent a set of resource starvation conditions where too
8801 many pending destroy cells prevent data cells from actually getting
8802 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
8803 bugfix on 0.2.0.1-alpha.
8805 o Major bugfixes (relay):
8806 - Avoid queuing or sending destroy cells for circuit ID zero when we
8807 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
8808 Found and fixed by "cypherpunks".
8809 - Fix ORPort reachability detection on relays running behind a
8810 proxy, by correctly updating the "local" mark on the controlling
8811 channel when changing the address of an or_connection_t after the
8812 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
8813 - Use a direct dirport connection when uploading non-anonymous
8814 descriptors to the directory authorities. Previously, relays would
8815 incorrectly use tunnel connections under a fairly wide variety of
8816 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
8817 - When a circuit accidentally has the same circuit ID for its
8818 forward and reverse direction, correctly detect the direction of
8819 cells using that circuit. Previously, this bug made roughly one
8820 circuit in a million non-functional. Fixes bug 12195; this is a
8821 bugfix on every version of Tor.
8823 o Minor features (security):
8824 - New --enable-expensive-hardening option to enable security
8825 hardening options that consume nontrivial amounts of CPU and
8826 memory. Right now, this includes AddressSanitizer and UbSan, which
8827 are supported in newer versions of GCC and Clang. Closes ticket
8829 - Authorities now assign the Guard flag to the fastest 25% of the
8830 network (it used to be the fastest 50%). Also raise the consensus
8831 weight that guarantees the Guard flag from 250 to 2000. For the
8832 current network, this results in about 1100 guards, down from 2500.
8833 This step paves the way for moving the number of entry guards
8834 down to 1 (proposal 236) while still providing reasonable expected
8835 performance for most users. Implements ticket 12690.
8837 o Minor features (security, memory management):
8838 - Memory allocation tricks (mempools and buffer freelists) are now
8839 disabled by default. You can turn them back on with
8840 --enable-mempools and --enable-buf-freelists respectively. We're
8841 disabling these features because malloc performance is good enough
8842 on most platforms, and a similar feature in OpenSSL exacerbated
8843 exploitation of the Heartbleed attack. Resolves ticket 11476.
8845 o Minor features (bridge client):
8846 - Report a more useful failure message when we can't connect to a
8847 bridge because we don't have the right pluggable transport
8848 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
8850 o Minor features (bridge):
8851 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
8852 cookie file for the ExtORPort g+r by default.
8854 o Minor features (bridges, pluggable transports):
8855 - Bridges now write the SHA1 digest of their identity key
8856 fingerprint (that is, a hash of a hash of their public key) to
8857 notice-level logs, and to a new hashed-fingerprint file. This
8858 information will help bridge operators look up their bridge in
8859 Globe and similar tools. Resolves ticket 10884.
8860 - Improve the message that Tor displays when running as a bridge
8861 using pluggable transports without an Extended ORPort listener.
8862 Also, log the message in the log file too. Resolves ticket 11043.
8863 - Add threshold cutoffs to the networkstatus document created by
8864 the Bridge Authority. Fixes bug 1117.
8865 - On Windows, spawn background processes using the CREATE_NO_WINDOW
8866 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
8867 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
8868 Vidalia set this option for us.) Implements ticket 10297.
8870 o Minor features (build):
8871 - The configure script has a --disable-seccomp option to turn off
8872 support for libseccomp on systems that have it, in case it (or
8873 Tor's use of it) is broken. Resolves ticket 11628.
8874 - Assume that a user using ./configure --host wants to cross-compile,
8875 and give an error if we cannot find a properly named
8876 tool-chain. Add a --disable-tool-name-check option to proceed
8877 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
8878 - If we run ./configure and the compiler recognizes -fstack-protector
8879 but the linker rejects it, warn the user about a potentially missing
8880 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
8881 - Add support for `--library-versions` flag. Implements ticket 6384.
8882 - Return the "unexpected sendme" warnings to a warn severity, but make
8883 them rate limited, to help diagnose ticket 8093.
8884 - Detect a missing asciidoc, and warn the user about it, during
8885 configure rather than at build time. Fixes issue 6506. Patch from
8888 o Minor features (client):
8889 - Add a new option, PredictedPortsRelevanceTime, to control how long
8890 after having received a request to connect to a given port Tor
8891 will try to keep circuits ready in anticipation of future requests
8892 for that port. Patch from "unixninja92"; implements ticket 9176.
8894 o Minor features (config options and command line):
8895 - Add an --allow-missing-torrc commandline option that tells Tor to
8896 run even if the configuration file specified by -f is not available.
8897 Implements ticket 10060.
8898 - Add support for the TPROXY transparent proxying facility on Linux.
8899 See documentation for the new TransProxyType option for more
8900 details. Implementation by "thomo". Closes ticket 10582.
8902 o Minor features (config options):
8903 - Config (torrc) lines now handle fingerprints which are missing
8904 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
8905 - Support a --dump-config option to print some or all of the
8906 configured options. Mainly useful for debugging the command-line
8907 option parsing code. Helps resolve ticket 4647.
8908 - Raise awareness of safer logging: notify user of potentially
8909 unsafe config options, like logging more verbosely than severity
8910 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
8911 - Add a new configuration option TestingV3AuthVotingStartOffset
8912 that bootstraps a network faster by changing the timing for
8913 consensus votes. Addresses ticket 8532.
8914 - Add a new torrc option "ServerTransportOptions" that allows
8915 bridge operators to pass configuration parameters to their
8916 pluggable transports. Resolves ticket 8929.
8917 - The config (torrc) file now accepts bandwidth and space limits in
8918 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
8919 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
8922 o Minor features (controller):
8923 - Make the entire exit policy available from the control port via
8924 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
8926 - Because of the fix for ticket 11396, the real limit for memory
8927 usage may no longer match the configured MaxMemInQueues value. The
8928 real limit is now exposed via GETINFO limits/max-mem-in-queues.
8929 - Add a new "HS_DESC" controller event that reports activities
8930 related to hidden service descriptors. Resolves ticket 8510.
8931 - New "DROPGUARDS" controller command to forget all current entry
8932 guards. Not recommended for ordinary use, since replacing guards
8933 too frequently makes several attacks easier. Resolves ticket 9934;
8935 - Implement the TRANSPORT_LAUNCHED control port event that
8936 notifies controllers about new launched pluggable
8937 transports. Resolves ticket 5609.
8939 o Minor features (diagnostic):
8940 - When logging a warning because of bug 7164, additionally check the
8941 hash table for consistency (as proposed on ticket 11737). This may
8942 help diagnose bug 7164.
8943 - When we log a heartbeat, log how many one-hop circuits we have
8944 that are at least 30 minutes old, and log status information about
8945 a few of them. This is an attempt to track down bug 8387.
8946 - When encountering an unexpected CR while writing text to a file on
8947 Windows, log the name of the file. Should help diagnosing
8949 - Give more specific warnings when a client notices that an onion
8950 handshake has failed. Fixes ticket 9635.
8951 - Add significant new logging code to attempt to diagnose bug 12184,
8952 where relays seem to run out of available circuit IDs.
8953 - Improve the diagnostic log message for bug 8387 even further to
8954 try to improve our odds of figuring out why one-hop directory
8955 circuits sometimes do not get closed.
8956 - Add more log messages to diagnose bug 7164, which causes
8957 intermittent "microdesc_free() called but md was still referenced"
8958 warnings. We now include more information, to figure out why we
8959 might be cleaning a microdescriptor for being too old if it's
8960 still referenced by a live node_t object.
8961 - Log current accounting state (bytes sent and received + remaining
8962 time for the current accounting period) in the relay's heartbeat
8963 message. Implements ticket 5526; patch from Peter Retzlaff.
8965 o Minor features (geoip):
8966 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8969 o Minor features (interface):
8970 - Generate a warning if any ports are listed in the SocksPolicy,
8971 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
8972 AuthDirBadExit options. (These options only support address
8973 ranges.) Fixes part of ticket 11108.
8975 o Minor features (kernel API usage):
8976 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
8977 sockets in a single system call. Implements ticket 5129.
8979 o Minor features (log messages):
8980 - When ServerTransportPlugin is set on a bridge, Tor can write more
8981 useful statistics about bridge use in its extrainfo descriptors,
8982 but only if the Extended ORPort ("ExtORPort") is set too. Add a
8983 log message to inform the user in this case. Resolves ticket 9651.
8984 - When receiving a new controller connection, log the origin address.
8985 Resolves ticket 9698; patch from "sigpipe".
8986 - When logging OpenSSL engine status at startup, log the status of
8987 more engines. Fixes ticket 10043; patch from Joshua Datko.
8989 o Minor features (log verbosity):
8990 - Demote the message that we give when a flushing connection times
8991 out for too long from NOTICE to INFO. It was usually meaningless.
8992 Resolves ticket 5286.
8993 - Don't log so many notice-level bootstrapping messages at startup
8994 about downloading descriptors. Previously, we'd log a notice
8995 whenever we learned about more routers. Now, we only log a notice
8996 at every 5% of progress. Fixes bug 9963.
8997 - Warn less verbosely when receiving a malformed
8998 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9000 o Minor features (performance):
9001 - If we're using the pure-C 32-bit curve25519_donna implementation
9002 of curve25519, build it with the -fomit-frame-pointer option to
9003 make it go faster on register-starved hosts. This improves our
9004 handshake performance by about 6% on i386 hosts without nacl.
9007 o Minor features (relay):
9008 - If a circuit timed out for at least 3 minutes, check if we have a
9009 new external IP address, and publish a new descriptor with the new
9010 IP address if it changed. Resolves ticket 2454.
9012 o Minor features (testing):
9013 - If Python is installed, "make check" now runs extra tests beyond
9014 the unit test scripts.
9015 - When bootstrapping a test network, sometimes very few relays get
9016 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
9017 specify a set of relays which should be voted Guard regardless of
9018 their uptime or bandwidth. Addresses ticket 9206.
9020 o Minor features (transparent proxy, *BSD):
9021 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9022 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9023 10267; patch from "yurivict".
9024 - Support OpenBSD's divert-to rules with the pf firewall for
9025 transparent proxy ports. To enable it, set "TransProxyType
9026 pf-divert". This allows Tor to run a TransPort transparent proxy
9027 port on OpenBSD 4.4 or later without root privileges. See the
9028 pf.conf(5) manual page for information on configuring pf to use
9029 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9031 o Minor bugfixes (bridge client):
9032 - Stop accepting bridge lines containing hostnames. Doing so would
9033 cause clients to perform DNS requests on the hostnames, which was
9034 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
9036 o Minor bugfixes (bridges):
9037 - Avoid potential crashes or bad behavior when launching a
9038 server-side managed proxy with ORPort or ExtORPort temporarily
9039 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
9040 - Fix a bug where the first connection works to a bridge that uses a
9041 pluggable transport with client-side parameters, but we don't send
9042 the client-side parameters on subsequent connections. (We don't
9043 use any pluggable transports with client-side parameters yet,
9044 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
9045 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
9047 o Minor bugfixes (build, auxiliary programs):
9048 - Stop preprocessing the "torify" script with autoconf, since
9049 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
9051 - The tor-fw-helper program now follows the standard convention and
9052 exits with status code "0" on success. Fixes bug 9030; bugfix on
9053 0.2.3.1-alpha. Patch by Arlo Breault.
9054 - Corrected ./configure advice for what openssl dev package you should
9055 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
9057 o Minor bugfixes (client):
9058 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9059 when starting a client with bridges configured and DisableNetwork
9060 set. (Tor launcher starts Tor with DisableNetwork set the first
9061 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9062 - Improve the log message when we can't connect to a hidden service
9063 because all of the hidden service directory nodes hosting its
9064 descriptor are excluded. Improves on our fix for bug 10722, which
9065 was a bugfix on 0.2.0.10-alpha.
9066 - Raise a control port warning when we fail to connect to all of
9067 our bridges. Previously, we didn't inform the controller, and
9068 the bootstrap process would stall. Fixes bug 11069; bugfix on
9070 - Exit immediately when a process-owning controller exits.
9071 Previously, tor relays would wait for a little while after their
9072 controller exited, as if they had gotten an INT signal -- but this
9073 was problematic, since there was no feedback for the user. To do a
9074 clean shutdown, controllers should send an INT signal and give Tor
9075 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
9076 - Stop attempting to connect to bridges before our pluggable
9077 transports are configured (harmless but resulted in some erroneous
9078 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
9079 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
9080 generating incorrect SOCKS5 responses, and confusing client
9081 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
9083 o Minor bugfixes (client, DNSPort):
9084 - When using DNSPort, try to respond to AAAA requests with AAAA
9085 answers. Previously, we hadn't looked at the request type when
9086 deciding which answer type to prefer. Fixes bug 10468; bugfix on
9088 - When receiving a DNS query for an unsupported record type, reply
9089 with no answer rather than with a NOTIMPL error. This behavior
9090 isn't correct either, but it will break fewer client programs, we
9091 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
9094 o Minor bugfixes (client, logging during bootstrap):
9095 - Only report the first fatal bootstrap error on a given OR
9096 connection. This stops us from telling the controller bogus error
9097 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
9098 - Avoid generating spurious warnings when starting with
9099 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
9102 o Minor bugfixes (closing OR connections):
9103 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
9104 check if it's an or_connection_t and correctly call
9105 connection_or_close_for_error() rather than
9106 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
9108 - When closing all connections on setting DisableNetwork to 1, use
9109 connection_or_close_normally() rather than closing OR connections
9110 out from under the channel layer. Fixes bug 11306; bugfix on
9113 o Minor bugfixes (code correctness):
9114 - Previously we used two temporary files when writing descriptors to
9115 disk; now we only use one. Fixes bug 1376.
9116 - Remove an erroneous (but impossible and thus harmless) pointer
9117 comparison that would have allowed compilers to skip a bounds
9118 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
9119 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
9120 - Fix an always-true assertion in pluggable transports code so it
9121 actually checks what it was trying to check. Fixes bug 10046;
9122 bugfix on 0.2.3.9-alpha. Found by "dcb".
9124 o Minor bugfixes (command line):
9125 - Use a single command-line parser for parsing torrc options on the
9126 command line and for finding special command-line options to avoid
9127 inconsistent behavior for torrc option arguments that have the same
9128 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
9130 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
9131 9573; bugfix on 0.0.9pre5.
9133 o Minor bugfixes (compilation):
9134 - Compile correctly with builds and forks of OpenSSL (such as
9135 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
9136 0.2.1.1-alpha. Patch from "dhill".
9137 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
9138 turned off (that is, without support for v2 link handshakes). Fixes
9139 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
9140 - In routerlist_assert_ok(), don't take the address of a
9141 routerinfo's cache_info member unless that routerinfo is non-NULL.
9142 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
9143 - Fix a large number of false positive warnings from the clang
9144 analyzer static analysis tool. This should make real warnings
9145 easier for clang analyzer to find. Patch from "teor". Closes
9147 - Resolve GCC complaints on OpenBSD about discarding constness in
9148 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
9149 on 0.1.1.23. Patch from Dana Koch.
9150 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
9151 treatment of long and time_t as comparable types. Fixes part of
9152 bug 11633. Patch from Dana Koch.
9153 - When deciding whether to build the 64-bit curve25519
9154 implementation, detect platforms where we can compile 128-bit
9155 arithmetic but cannot link it. Fixes bug 11729; bugfix on
9156 0.2.4.8-alpha. Patch from "conradev".
9157 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
9158 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
9159 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
9161 - Build and run correctly on systems like OpenBSD-current that have
9162 patched OpenSSL to remove get_cipher_by_char and/or its
9163 implementations. Fixes issue 13325.
9165 o Minor bugfixes (controller and command-line):
9166 - If changing a config option via "setconf" fails in a recoverable
9167 way, we used to nonetheless write our new control ports to the
9168 file described by the "ControlPortWriteToFile" option. Now we only
9169 write out that file if we successfully switch to the new config
9170 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
9172 o Minor bugfixes (directory server):
9173 - No longer accept malformed http headers when parsing urls from
9174 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
9175 bugfix on 0.0.6pre1.
9176 - When sending a compressed set of descriptors or microdescriptors,
9177 make sure to finalize the zlib stream. Previously, we would write
9178 all the compressed data, but if the last descriptor we wanted to
9179 send was missing or too old, we would not mark the stream as
9180 finished. This caused problems for decompression tools. Fixes bug
9181 11648; bugfix on 0.1.1.23.
9183 o Minor bugfixes (hidden service):
9184 - Only retry attempts to connect to a chosen rendezvous point 8
9185 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
9187 o Minor bugfixes (interface):
9188 - Reject relative control socket paths and emit a warning. Previously,
9189 single-component control socket paths would be rejected, but Tor
9190 would not log why it could not validate the config. Fixes bug 9258;
9191 bugfix on 0.2.3.16-alpha.
9193 o Minor bugfixes (log messages):
9194 - Fix a bug where clients using bridges would report themselves
9195 as 50% bootstrapped even without a live consensus document.
9196 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
9197 - Suppress a warning where, if there's only one directory authority
9198 in the network, we would complain that votes and signatures cannot
9199 be uploaded to other directory authorities. Fixes bug 10842;
9200 bugfix on 0.2.2.26-beta.
9201 - Report bootstrapping progress correctly when we're downloading
9202 microdescriptors. We had updated our "do we have enough microdescs
9203 to begin building circuits?" logic most recently in 0.2.4.10-alpha
9204 (see bug 5956), but we left the bootstrap status event logic at
9205 "how far through getting 1/4 of them are we?" Fixes bug 9958;
9206 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
9208 o Minor bugfixes (logging):
9209 - Downgrade "Unexpected onionskin length after decryption" warning
9210 to a protocol-warn, since there's nothing relay operators can do
9211 about a client that sends them a malformed create cell. Resolves
9212 bug 12996; bugfix on 0.0.6rc1.
9213 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
9214 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
9215 - When logging information about an EXTEND2 or EXTENDED2 cell, log
9216 their names correctly. Fixes part of bug 12700; bugfix
9218 - When logging information about a relay cell whose command we don't
9219 recognize, log its command as an integer. Fixes part of bug 12700;
9220 bugfix on 0.2.1.10-alpha.
9221 - Escape all strings from the directory connection before logging
9222 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
9223 - Squelch a spurious LD_BUG message "No origin circuit for
9224 successful SOCKS stream" in certain hidden service failure cases;
9226 - Downgrade the severity of the 'unexpected sendme cell from client'
9227 from 'warn' to 'protocol warning'. Closes ticket 8093.
9229 o Minor bugfixes (misc code correctness):
9230 - In munge_extrainfo_into_routerinfo(), check the return value of
9231 memchr(). This would have been a serious issue if we ever passed
9232 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
9234 - On the chance that somebody manages to build Tor on a
9235 platform where time_t is unsigned, correct the way that
9236 microdesc_add_to_cache() handles negative time arguments.
9237 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
9238 - Fix various instances of undefined behavior in channeltls.c,
9239 tor_memmem(), and eventdns.c that would cause us to construct
9240 pointers to memory outside an allocated object. (These invalid
9241 pointers were not accessed, but C does not even allow them to
9242 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
9243 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
9244 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
9245 fix some miscellaneous errors in our tests and codebase. Fixes bug
9246 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
9247 - Always check return values for unlink, munmap, UnmapViewOfFile;
9248 check strftime return values more often. In some cases all we can
9249 do is report a warning, but this may help prevent deeper bugs from
9250 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
9252 - Fix numerous warnings from the clang "scan-build" static analyzer.
9253 Some of these are programming style issues; some of them are false
9254 positives that indicated awkward code; some are undefined behavior
9255 cases related to constructing (but not using) invalid pointers;
9256 some are assumptions about API behavior; some are (harmlessly)
9257 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
9258 correct; and one or two are genuine bugs that weren't reachable
9259 from the rest of the program. Fixes bug 8793; bugfixes on many,
9262 o Minor bugfixes (node selection):
9263 - If ExcludeNodes is set, consider non-excluded hidden service
9264 directory servers before excluded ones. Do not consider excluded
9265 hidden service directory servers at all if StrictNodes is
9266 set. (Previously, we would sometimes decide to connect to those
9267 servers, and then realize before we initiated a connection that
9268 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
9270 - If we set the ExitNodes option but it doesn't include any nodes
9271 that have the Exit flag, we would choose not to bootstrap. Now we
9272 bootstrap so long as ExitNodes includes nodes which can exit to
9273 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
9275 o Minor bugfixes (performance):
9276 - Avoid a bug where every successful connection made us recompute
9277 the flag telling us whether we have sufficient information to
9278 build circuits. Previously, we would forget our cached value
9279 whenever we successfully opened a channel (or marked a router as
9280 running or not running for any other reason), regardless of
9281 whether we had previously believed the router to be running. This
9282 forced us to run an expensive update operation far too often.
9283 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
9284 - Avoid using tor_memeq() for checking relay cell integrity. This
9285 removes a possible performance bottleneck. Fixes part of bug
9286 12169; bugfix on 0.2.1.31.
9288 o Minor bugfixes (platform-specific):
9289 - When dumping a malformed directory object to disk, save it in
9290 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
9292 - Don't report failures from make_socket_reuseable() on incoming
9293 sockets on OSX: this can happen when incoming connections close
9294 early. Fixes bug 10081.
9296 o Minor bugfixes (pluggable transports):
9297 - Avoid another 60-second delay when starting Tor in a pluggable-
9298 transport-using configuration when we already have cached
9299 descriptors for our bridges. Fixes bug 11965; bugfix
9302 o Minor bugfixes (protocol correctness):
9303 - When receiving a VERSIONS cell with an odd number of bytes, close
9304 the connection immediately since the cell is malformed. Fixes bug
9305 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
9308 o Minor bugfixes (relay, other):
9309 - We now drop CREATE cells for already-existent circuit IDs and for
9310 zero-valued circuit IDs, regardless of other factors that might
9311 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
9313 - When rejecting DATA cells for stream_id zero, still count them
9314 against the circuit's deliver window so that we don't fail to send
9315 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
9317 o Minor bugfixes (relay, threading):
9318 - Check return code on spawn_func() in cpuworker code, so that we
9319 don't think we've spawned a nonworking cpuworker and write junk to
9320 it forever. Fix related to bug 4345; bugfix on all released Tor
9321 versions. Found by "skruffy".
9322 - Use a pthread_attr to make sure that spawn_func() cannot return an
9323 error while at the same time launching a thread. Fix related to
9324 bug 4345; bugfix on all released Tor versions. Reported
9327 o Minor bugfixes (relays and bridges):
9328 - Avoid crashing on a malformed resolv.conf file when running a
9329 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
9330 - Non-exit relays no longer launch mock DNS requests to check for
9331 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
9332 non-exit relays stopped servicing DNS requests. Fixes bug 965;
9333 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
9334 - Bridges now report complete directory request statistics. Related
9335 to bug 5824; bugfix on 0.2.2.1-alpha.
9336 - Bridges now never collect statistics that were designed for
9337 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
9339 o Minor bugfixes (testing):
9340 - Fix all valgrind warnings produced by the unit tests. There were
9341 over a thousand memory leak warnings previously, mostly produced
9342 by forgetting to free things in the unit test code. Fixes bug
9343 11618, bugfixes on many versions of Tor.
9345 o Minor bugfixes (tor-fw-helper):
9346 - Give a correct log message when tor-fw-helper fails to launch.
9347 (Previously, we would say something like "tor-fw-helper sent us a
9348 string we could not parse".) Fixes bug 9781; bugfix
9351 o Minor bugfixes (trivial memory leaks):
9352 - Fix a small memory leak when signing a directory object. Fixes bug
9353 11275; bugfix on 0.2.4.13-alpha.
9354 - Resolve some memory leaks found by coverity in the unit tests, on
9355 exit in tor-gencert, and on a failure to compute digests for our
9356 own keys when generating a v3 networkstatus vote. These leaks
9357 should never have affected anyone in practice.
9359 o Code simplification and refactoring:
9360 - Remove some old fallback code designed to keep Tor clients working
9361 in a network with only two working relays. Elsewhere in the code we
9362 have long since stopped supporting such networks, so there wasn't
9363 much point in keeping it around. Addresses ticket 9926.
9364 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
9365 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
9366 - Extract the common duplicated code for creating a subdirectory
9367 of the data directory and writing to a file in it. Fixes ticket
9368 4282; patch from Peter Retzlaff.
9369 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
9370 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
9371 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
9372 - Add a set of accessor functions for the circuit timeout data
9373 structure. Fixes ticket 6153; patch from "piet".
9374 - Clean up exit paths from connection_listener_new(). Closes ticket
9375 8789. Patch from Arlo Breault.
9376 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
9377 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
9378 - Use a doubly-linked list to implement the global circuit list.
9379 Resolves ticket 9108. Patch from Marek Majkowski.
9380 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
9381 - Remove constants and tests for PKCS1 padding; it's insecure and
9382 shouldn't be used for anything new. Fixes bug 8792; patch
9384 - Remove instances of strcpy() from the unit tests. They weren't
9385 hurting anything, since they were only in the unit tests, but it's
9386 embarrassing to have strcpy() in the code at all, and some analysis
9387 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
9388 0.2.3.8-alpha. Patch from Arlo Breault.
9389 - Remove is_internal_IP() function. Resolves ticket 4645.
9390 - Remove unused function circuit_dump_by_chan from circuitlist.c.
9391 Closes issue 9107; patch from "marek".
9392 - Change our use of the ENUM_BF macro to avoid declarations that
9394 - Get rid of router->address, since in all cases it was just the
9395 string representation of router->addr. Resolves ticket 5528.
9398 - Adjust the URLs in the README to refer to the new locations of
9399 several documents on the website. Fixes bug 12830. Patch from
9401 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
9403 - Update manpage to describe some of the files you can expect to
9404 find in Tor's DataDirectory. Addresses ticket 9839.
9405 - Clean up several option names in the manpage to match their real
9406 names, add the missing documentation for a couple of testing and
9407 directory authority options, remove the documentation for a
9408 V2-directory fetching option that no longer exists. Resolves
9410 - Correct the documentation so that it lists the correct directory
9411 for the stats files. (They are in a subdirectory called "stats",
9413 - In the manpage, move more authority-only options into the
9414 directory authority section so that operators of regular directory
9415 caches don't get confused.
9416 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
9417 11061; bugfix on 0.2.4.7-alpha.
9418 - Resolve warnings from Doxygen.
9419 - Document in the manpage that "KBytes" may also be written as
9420 "kilobytes" or "KB", that "Kbits" may also be written as
9421 "kilobits", and so forth. Closes ticket 9222.
9422 - Document that the ClientOnly config option overrides ORPort.
9423 Our old explanation made ClientOnly sound as though it did
9424 nothing at all. Resolves bug 9059.
9425 - Explain that SocksPolicy, DirPolicy, and similar options don't
9426 take port arguments. Fixes the other part of ticket 11108.
9427 - Fix a comment about the rend_server_descriptor_t.protocols field
9428 to more accurately describe its range. Also, make that field
9429 unsigned, to more accurately reflect its usage. Fixes bug 9099;
9430 bugfix on 0.2.1.5-alpha.
9431 - Fix the manpage's description of HiddenServiceAuthorizeClient:
9432 the maximum client name length is 16, not 19. Fixes bug 11118;
9433 bugfix on 0.2.1.6-alpha.
9436 - The contrib directory has been sorted and tidied. Before, it was
9437 an unsorted dumping ground for useful and not-so-useful things.
9438 Now, it is divided based on functionality, and the items which
9439 seemed to be nonfunctional or useless have been removed. Resolves
9440 ticket 8966; based on patches from "rl1987".
9442 o Removed code and features:
9443 - Clients now reject any directory authority certificates lacking
9444 a dir-key-crosscert element. These have been included since
9445 0.2.1.9-alpha, so there's no real reason for them to be optional
9446 any longer. Completes proposal 157. Resolves ticket 10162.
9447 - Remove all code that existed to support the v2 directory system,
9448 since there are no longer any v2 directory authorities. Resolves
9450 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
9451 options, which were used for designating authorities as "Hidden
9452 service authorities". There has been no use of hidden service
9453 authorities since 0.2.2.1-alpha, when we stopped uploading or
9454 downloading v0 hidden service descriptors. Fixes bug 10881; also
9455 part of a fix for bug 10841.
9456 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9457 and MTBF calculations, but that nobody was using. Fixes bug 11742.
9458 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9459 exist; tunneled directory connections have been available since
9460 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9461 brute-force fix for 10849, where "TunnelDirConns 0" would break
9463 - Remove all code for the long unused v1 directory protocol.
9464 Resolves ticket 11070.
9465 - Remove all remaining code related to version-0 hidden service
9466 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
9467 the rest of bug 10841.
9468 - Remove migration code from when we renamed the "cached-routers"
9469 file to "cached-descriptors" back in 0.2.0.8-alpha. This
9470 incidentally resolves ticket 6502 by cleaning up the related code
9471 a bit. Patch from Akshay Hebbar.
9473 o Test infrastructure:
9474 - Tor now builds each source file in two modes: a mode that avoids
9475 exposing identifiers needlessly, and another mode that exposes
9476 more identifiers for testing. This lets the compiler do better at
9477 optimizing the production code, while enabling us to take more
9478 radical measures to let the unit tests test things.
9479 - The production builds no longer include functions used only in
9480 the unit tests; all functions exposed from a module only for
9481 unit-testing are now static in production builds.
9482 - Add an --enable-coverage configuration option to make the unit
9483 tests (and a new src/or/tor-cov target) to build with gcov test
9485 - Update to the latest version of tinytest.
9486 - Improve the tinytest implementation of string operation tests so
9487 that comparisons with NULL strings no longer crash the tests; they
9488 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
9489 - New macros in test.h to simplify writing mock-functions for unit
9490 tests. Part of ticket 11507. Patch from Dana Koch.
9491 - We now have rudimentary function mocking support that our unit
9492 tests can use to test functions in isolation. Function mocking
9493 lets the tests temporarily replace a function's dependencies with
9494 stub functions, so that the tests can check the function without
9495 invoking the other functions it calls.
9498 - Complete tests for the status.c module. Resolves ticket 11507.
9499 Patch from Dana Koch.
9500 - Add more unit tests for the <circid,channel>->circuit map, and
9501 the destroy-cell-tracking code to fix bug 7912.
9502 - Unit tests for failing cases of the TAP onion handshake.
9503 - More unit tests for address-manipulation functions.
9505 o Distribution (systemd):
9506 - Include a tor.service file in contrib/dist for use with systemd.
9507 Some distributions will be able to use this file unmodified;
9508 others will need to tweak it, or write their own. Patch from Jamie
9509 Nguyen; resolves ticket 8368.
9510 - Verify configuration file via ExecStartPre in the systemd unit
9511 file. Patch from intrigeri; resolves ticket 12730.
9512 - Explicitly disable RunAsDaemon in the systemd unit file. Our
9513 current systemd unit uses "Type = simple", so systemd does not
9514 expect tor to fork. If the user has "RunAsDaemon 1" in their
9515 torrc, then things won't work as expected. This is e.g. the case
9516 on Debian (and derivatives), since there we pass "--defaults-torrc
9517 /usr/share/tor/tor-service-defaults-torrc" (that contains
9518 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
9522 Changes in version 0.2.4.25 - 2014-10-20
9523 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9524 (even though POODLE does not affect Tor). It also works around a crash
9525 bug caused by some operating systems' response to the "POODLE" attack
9526 (which does affect Tor).
9528 o Major security fixes (also in 0.2.5.9-rc):
9529 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9530 today support TLS 1.0 or later, so we can safely turn off support
9531 for this old (and insecure) protocol. Fixes bug 13426.
9533 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9534 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9535 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9536 13471. This is a workaround for an OpenSSL bug.
9539 Changes in version 0.2.4.24 - 2014-09-22
9540 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9541 connecting to hidden services, and it updates the location of one of
9542 the directory authorities.
9545 - Clients now send the correct address for their chosen rendezvous
9546 point when trying to access a hidden service. They used to send
9547 the wrong address, which would still work some of the time because
9548 they also sent the identity digest of the rendezvous point, and if
9549 the hidden service happened to try connecting to the rendezvous
9550 point from a relay that already had a connection open to it,
9551 the relay would reuse that connection. Now connections to hidden
9552 services should be more robust and faster. Also, this bug meant
9553 that clients were leaking to the hidden service whether they were
9554 on a little-endian (common) or big-endian (rare) system, which for
9555 some users might have reduced their anonymity. Fixes bug 13151;
9556 bugfix on 0.2.1.5-alpha.
9558 o Directory authority changes:
9559 - Change IP address for gabelmoo (v3 directory authority).
9561 o Minor features (geoip):
9562 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9566 Changes in version 0.2.4.23 - 2014-07-28
9567 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
9568 guard rotation, and also backports several important fixes from the
9569 Tor 0.2.5 alpha release series.
9572 - Clients now look at the "usecreatefast" consensus parameter to
9573 decide whether to use CREATE_FAST or CREATE cells for the first hop
9574 of their circuit. This approach can improve security on connections
9575 where Tor's circuit handshake is stronger than the available TLS
9576 connection security levels, but the tradeoff is more computational
9577 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9578 - Make the number of entry guards configurable via a new
9579 NumEntryGuards consensus parameter, and the number of directory
9580 guards configurable via a new NumDirectoryGuards consensus
9581 parameter. Implements ticket 12688.
9584 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9585 implementation that caused incorrect results on 32-bit
9586 implementations when certain malformed inputs were used along with
9587 a small class of private ntor keys. This bug does not currently
9588 appear to allow an attacker to learn private keys or impersonate a
9589 Tor server, but it could provide a means to distinguish 32-bit Tor
9590 implementations from 64-bit Tor implementations. Fixes bug 12694;
9591 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9595 - Warn and drop the circuit if we receive an inbound 'relay early'
9596 cell. Those used to be normal to receive on hidden service circuits
9597 due to bug 1038, but the buggy Tor versions are long gone from
9598 the network so we can afford to resume watching for them. Resolves
9599 the rest of bug 1038; bugfix on 0.2.1.19.
9600 - Correct a confusing error message when trying to extend a circuit
9601 via the control protocol but we don't know a descriptor or
9602 microdescriptor for one of the specified relays. Fixes bug 12718;
9603 bugfix on 0.2.3.1-alpha.
9604 - Avoid an illegal read from stack when initializing the TLS
9605 module using a version of OpenSSL without all of the ciphers
9606 used by the v2 link handshake. Fixes bug 12227; bugfix on
9607 0.2.4.8-alpha. Found by "starlight".
9610 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9614 Changes in version 0.2.4.22 - 2014-05-16
9615 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9616 alpha release series. These include blocking all authority signing
9617 keys that may have been affected by the OpenSSL "heartbleed" bug,
9618 choosing a far more secure set of TLS ciphersuites by default, closing
9619 a couple of memory leaks that could be used to run a target relay out
9620 of RAM, and several others.
9622 o Major features (security, backport from 0.2.5.4-alpha):
9623 - Block authority signing keys that were used on authorities
9624 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9625 don't have any evidence that these keys _were_ compromised; we're
9626 doing this to be prudent.) Resolves ticket 11464.
9628 o Major bugfixes (security, OOM):
9629 - Fix a memory leak that could occur if a microdescriptor parse
9630 fails during the tokenizing step. This bug could enable a memory
9631 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9634 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9635 - The relay ciphersuite list is now generated automatically based on
9636 uniform criteria, and includes all OpenSSL ciphersuites with
9637 acceptable strength and forward secrecy. Previously, we had left
9638 some perfectly fine ciphersuites unsupported due to omission or
9639 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9640 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9641 - Relays now trust themselves to have a better view than clients of
9642 which TLS ciphersuites are better than others. (Thanks to bug
9643 11513, the relay list is now well-considered, whereas the client
9644 list has been chosen mainly for anti-fingerprinting purposes.)
9645 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9646 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9647 AES128. Resolves ticket 11528.
9648 - Clients now try to advertise the same list of ciphersuites as
9649 Firefox 28. This change enables selection of (fast) GCM
9650 ciphersuites, disables some strange old ciphers, and stops
9651 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9652 Resolves ticket 11438.
9654 o Minor bugfixes (configuration, security):
9655 - When running a hidden service, do not allow TunneledDirConns 0:
9656 trying to set that option together with a hidden service would
9657 otherwise prevent the hidden service from running, and also make
9658 it publish its descriptors directly over HTTP. Fixes bug 10849;
9659 bugfix on 0.2.1.1-alpha.
9661 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9662 - Avoid sending a garbage value to the controller when a circuit is
9663 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9665 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9666 - Stop leaking memory when we successfully resolve a PTR record.
9667 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9669 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9670 - Avoid 60-second delays in the bootstrapping process when Tor is
9671 launching for a second time while using bridges. Fixes bug 9229;
9672 bugfix on 0.2.0.3-alpha.
9674 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9675 - Give the correct URL in the warning message when trying to run a
9676 relay on an ancient version of Windows. Fixes bug 9393.
9678 o Minor bugfixes (compilation):
9679 - Fix a compilation error when compiling with --disable-curve25519.
9680 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9683 - Downgrade the warning severity for the the "md was still
9684 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9685 for trying to diagnose this bug, and the current warning in
9686 earlier versions of tor achieves nothing useful. Addresses warning
9689 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9690 - When we run out of usable circuit IDs on a channel, log only one
9691 warning for the whole channel, and describe how many circuits
9692 there were on the channel. Fixes part of ticket 11553.
9694 o Minor features (security, backport from 0.2.5.4-alpha):
9695 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9696 leave the default at 8GBytes), to better support Raspberry Pi
9697 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9699 o Documentation (backport from 0.2.5.4-alpha):
9700 - Correctly document that we search for a system torrc file before
9701 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9705 Changes in version 0.2.4.21 - 2014-02-28
9706 Tor 0.2.4.21 further improves security against potential adversaries who
9707 find breaking 1024-bit crypto doable, and backports several stability
9708 and robustness patches from the 0.2.5 branch.
9710 o Major features (client security):
9711 - When we choose a path for a 3-hop circuit, make sure it contains
9712 at least one relay that supports the NTor circuit extension
9713 handshake. Otherwise, there is a chance that we're building
9714 a circuit that's worth attacking by an adversary who finds
9715 breaking 1024-bit crypto doable, and that chance changes the game
9716 theory. Implements ticket 9777.
9719 - Do not treat streams that fail with reason
9720 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
9721 since it could also indicate an ENETUNREACH connection error. Fixes
9722 part of bug 10777; bugfix on 0.2.4.8-alpha.
9724 o Code simplification and refactoring:
9725 - Remove data structures which were introduced to implement the
9726 CellStatistics option: they are now redundant with the new timestamp
9727 field in the regular packed_cell_t data structure, which we did
9728 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
9731 - Always clear OpenSSL bignums before freeing them -- even bignums
9732 that don't contain secrets. Resolves ticket 10793. Patch by
9734 - Build without warnings under clang 3.4. (We have some macros that
9735 define static functions only some of which will get used later in
9736 the module. Starting with clang 3.4, these give a warning unless the
9737 unused attribute is set on them.) Resolves ticket 10904.
9738 - Update geoip and geoip6 files to the February 7 2014 Maxmind
9739 GeoLite2 Country database.
9742 - Set the listen() backlog limit to the largest actually supported
9743 on the system, not to the value in a header file. Fixes bug 9716;
9744 bugfix on every released Tor.
9745 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
9746 exit node as a NOROUTE error, not an INTERNAL error, since they
9747 can apparently happen when trying to connect to the wrong sort
9748 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
9749 - Fix build warnings about missing "a2x" comment when building the
9750 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
9751 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
9752 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
9753 not entirely remove it from the connection lists. Fixes bug 9602;
9754 bugfix on 0.2.4.4-alpha.
9755 - Fix a segmentation fault in our benchmark code when running with
9756 Fedora's OpenSSL package, or any other OpenSSL that provides
9757 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
9758 - Turn "circuit handshake stats since last time" log messages into a
9759 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
9761 o Documentation fixes:
9762 - Document that all but one DirPort entry must have the NoAdvertise
9763 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
9766 Changes in version 0.2.4.20 - 2013-12-22
9767 Tor 0.2.4.20 fixes potentially poor random number generation for users
9768 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
9769 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
9770 and 4) have no state file in their DataDirectory (as would happen on
9771 first start). Users who generated relay or hidden service identity
9772 keys in such a situation should discard them and generate new ones.
9774 This release also fixes a logic error that caused Tor clients to build
9775 many more preemptive circuits than they actually need.
9778 - Do not allow OpenSSL engines to replace the PRNG, even when
9779 HardwareAccel is set. The only default builtin PRNG engine uses
9780 the Intel RDRAND instruction to replace the entire PRNG, and
9781 ignores all attempts to seed it with more entropy. That's
9782 cryptographically stupid: the right response to a new alleged
9783 entropy source is never to discard all previously used entropy
9784 sources. Fixes bug 10402; works around behavior introduced in
9785 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
9787 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
9788 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
9789 - Avoid launching spurious extra circuits when a stream is pending.
9790 This fixes a bug where any circuit that _wasn't_ unusable for new
9791 streams would be treated as if it were, causing extra circuits to
9792 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
9795 - Avoid a crash bug when starting with a corrupted microdescriptor
9796 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
9797 - If we fail to dump a previously cached microdescriptor to disk, avoid
9798 freeing duplicate data later on. Fixes bug 10423; bugfix on
9799 0.2.4.13-alpha. Spotted by "bobnomnom".
9802 Changes in version 0.2.4.19 - 2013-12-11
9803 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
9804 (1986-2013). Aaron worked on diverse projects including helping to guide
9805 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
9806 transparency to the U.S government's PACER documents, and contributing
9807 design and development for Tor and Tor2Web. Aaron was one of the latest
9808 martyrs in our collective fight for civil liberties and human rights,
9809 and his death is all the more painful because he was one of us.
9811 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
9812 a new circuit handshake and link encryption that use ECC to provide
9813 better security and efficiency; makes relays better manage circuit
9814 creation requests; uses "directory guards" to reduce client enumeration
9815 risks; makes bridges collect and report statistics about the pluggable
9816 transports they support; cleans up and improves our geoip database;
9817 gets much closer to IPv6 support for clients, bridges, and relays; makes
9818 directory authorities use measured bandwidths rather than advertised
9819 ones when computing flags and thresholds; disables client-side DNS
9820 caching to reduce tracking risks; and fixes a big bug in bridge
9821 reachability testing. This release introduces two new design
9822 abstractions in the code: a new "channel" abstraction between circuits
9823 and or_connections to allow for implementing alternate relay-to-relay
9824 transports, and a new "circuitmux" abstraction storing the queue of
9825 circuits for a channel. The release also includes many stability,
9826 security, and privacy fixes.
9828 o Major features (new circuit handshake):
9829 - Tor now supports a new circuit extension handshake designed by Ian
9830 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
9831 circuit extension handshake, later called "TAP", was a bit slow
9832 (especially on the relay side), had a fragile security proof, and
9833 used weaker keys than we'd now prefer. The new circuit handshake
9834 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
9835 function, making it significantly more secure than the older
9836 handshake, and significantly faster. Tor can use one of two built-in
9837 pure-C curve25519-donna implementations by Adam Langley, or it
9838 can link against the "nacl" library for a tuned version if present.
9840 The built-in version is very fast for 64-bit systems when building
9841 with GCC. The built-in 32-bit version is still faster than the
9842 old TAP protocol, but using libnacl is better on most such hosts.
9844 Implements proposal 216; closes ticket 7202.
9846 o Major features (better link encryption):
9847 - Relays can now enable the ECDHE TLS ciphersuites when available
9848 and appropriate. These ciphersuites let us negotiate forward-secure
9849 TLS secret keys more safely and more efficiently than with our
9850 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
9851 public relays prefer the (faster) P224 group, and bridges prefer
9852 the (more common) P256 group; you can override this with the
9855 This feature requires clients running 0.2.3.17-beta or later,
9856 and requires both sides to be running OpenSSL 1.0.0 or later
9857 with ECC support. OpenSSL 1.0.1, with the compile-time option
9858 "enable-ec_nistp_64_gcc_128", is highly recommended.
9860 Implements the relay side of proposal 198; closes ticket 7200.
9862 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
9863 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
9864 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
9865 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
9866 them to solve bug 6033.)
9868 o Major features (relay performance):
9869 - Instead of limiting the number of queued onionskins (aka circuit
9870 create requests) to a fixed, hard-to-configure number, we limit
9871 the size of the queue based on how many we expect to be able to
9872 process in a given amount of time. We estimate the time it will
9873 take to process an onionskin based on average processing time
9874 of previous onionskins. Closes ticket 7291. You'll never have to
9875 configure MaxOnionsPending again.
9876 - Relays process the new "NTor" circuit-level handshake requests
9877 with higher priority than the old "TAP" circuit-level handshake
9878 requests. We still process some TAP requests to not totally starve
9879 0.2.3 clients when NTor becomes popular. A new consensus parameter
9880 "NumNTorsPerTAP" lets us tune the balance later if we need to.
9881 Implements ticket 9574.
9883 o Major features (client bootstrapping resilience):
9884 - Add a new "FallbackDir" torrc option to use when we can't use
9885 a directory mirror from the consensus (either because we lack a
9886 consensus, or because they're all down). Currently, all authorities
9887 are fallbacks by default, and there are no other default fallbacks,
9888 but that will change. This option will allow us to give clients a
9889 longer list of servers to try to get a consensus from when first
9890 connecting to the Tor network, and thereby reduce load on the
9891 directory authorities. Implements proposal 206, "Preconfigured
9892 directory sources for bootstrapping". We also removed the old
9893 "FallbackNetworkstatus" option, since we never got it working well
9894 enough to use it. Closes bug 572.
9895 - If we have no circuits open, use a relaxed timeout (the
9896 95th-percentile cutoff) until a circuit succeeds. This heuristic
9897 should allow Tor to succeed at building circuits even when the
9898 network connection drastically changes. Should help with bug 3443.
9900 o Major features (use of guards):
9901 - Support directory guards (proposal 207): when possible, clients now
9902 use their entry guards for non-anonymous directory requests. This
9903 can help prevent client enumeration. Note that this behavior only
9904 works when we have a usable consensus directory, and when options
9905 about what to download are more or less standard. In the future we
9906 should re-bootstrap from our guards, rather than re-bootstrapping
9907 from the preconfigured list of directory sources that ships with
9908 Tor. Resolves ticket 6526.
9909 - Raise the default time that a client keeps an entry guard from
9910 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
9911 2012 paper. (We would make it even longer, but we need better client
9912 load balancing first.) Also, make the guard lifetime controllable
9913 via a new GuardLifetime torrc option and a GuardLifetime consensus
9914 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9916 o Major features (bridges with pluggable transports):
9917 - Bridges now report the pluggable transports they support to the
9918 bridge authority, so it can pass the supported transports on to
9919 bridgedb and/or eventually do reachability testing. Implements
9921 - Automatically forward the TCP ports of pluggable transport
9922 proxies using tor-fw-helper if PortForwarding is enabled. Implements
9925 o Major features (geoip database):
9926 - Maxmind began labelling Tor relays as being in country "A1",
9927 which breaks by-country node selection inside Tor. Now we use a
9928 script to replace "A1" ("Anonymous Proxy") entries in our geoip
9929 file with real country codes. This script fixes about 90% of "A1"
9930 entries automatically and uses manual country code assignments to
9931 fix the remaining 10%. See src/config/README.geoip for details.
9933 - Add GeoIP database for IPv6 addresses. The new config option
9935 - Update to the October 2 2013 Maxmind GeoLite Country database.
9937 o Major features (IPv6):
9938 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
9939 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
9940 to happen. Implements ticket 5535.
9941 - All kind of relays, not just bridges, can now advertise an IPv6
9942 OR port. Implements ticket 6362.
9943 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
9944 connectivity, then set the IPv6Exit flag to 1. Also make sure your
9945 exit policy reads as you would like: the address * applies to all
9946 address families, whereas *4 is IPv4 address only, and *6 is IPv6
9947 addresses only. On the client side, you'll need to wait for enough
9948 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
9949 and use Socks5. Closes ticket 5547, implements proposal 117 as
9950 revised in proposal 208.
9951 - Bridge authorities now accept IPv6 bridge addresses and include
9952 them in network status documents. Implements ticket 5534.
9953 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
9955 o Major features (directory authorities):
9956 - Directory authorities now prefer using measured bandwidths to
9957 advertised ones when computing flags and thresholds. Resolves
9959 - Directory authorities that vote measured bandwidths about more
9960 than a threshold number of relays now treat relays with
9961 unmeasured bandwidths as having bandwidth 0 when computing their
9962 flags. Resolves ticket 8435.
9963 - Directory authorities now support a new consensus method (17)
9964 where they cap the published bandwidth of relays for which
9965 insufficient bandwidth measurements exist. Fixes part of bug 2286.
9966 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
9967 serve any v2 directory information. Now we can test disabling the
9968 old deprecated v2 directory format, and see whether doing so has
9969 any effect on network load. Begins to fix bug 6783.
9971 o Major features (build and portability):
9972 - Switch to a nonrecursive Makefile structure. Now instead of each
9973 Makefile.am invoking other Makefile.am's, there is a master
9974 Makefile.am that includes the others. This change makes our build
9975 process slightly more maintainable, and improves parallelism for
9976 building with make -j. Original patch by Stewart Smith; various
9977 fixes by Jim Meyering.
9978 - Where available, we now use automake's "silent" make rules by
9979 default, so that warnings are easier to spot. You can get the old
9980 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
9981 - Resume building correctly with MSVC and Makefile.nmake. This patch
9982 resolves numerous bugs and fixes reported by ultramage, including
9983 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
9985 o Security features:
9986 - Switch to a completely time-invariant approach for picking nodes
9987 weighted by bandwidth. Our old approach would run through the
9988 part of the loop after it had made its choice slightly slower
9989 than it ran through the part of the loop before it had made its
9990 choice. Addresses ticket 6538.
9991 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
9992 by tor2web clients allows hidden services to identify tor2web
9993 clients through their repeated selection of the same rendezvous
9994 and introduction point circuit endpoints (their guards). Resolves
9997 o Major bugfixes (relay denial of service):
9998 - When we have too much memory queued in circuits (according to a new
9999 MaxMemInCellQueues option), close the circuits that have the oldest
10000 queued cells, on the theory that those are most responsible for
10001 us running low on memory. This prevents us from running out of
10002 memory as a relay if circuits fill up faster than they can be
10003 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
10004 Tor. This bug is a further fix beyond bug 6252, whose fix was
10005 merged into 0.2.3.21-rc.
10006 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
10007 ID: these could be used to create unexpected streams and circuits
10008 which would count as "present" to some parts of Tor but "absent"
10009 to others, leading to zombie circuits and streams or to a bandwidth
10010 denial-of-service. Fixes bug 7889; bugfix on every released version
10011 of Tor. Reported by "oftc_must_be_destroyed".
10012 - Avoid a bug where our response to TLS renegotiation under certain
10013 network conditions could lead to a busy-loop, with 100% CPU
10014 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
10016 o Major bugfixes (asserts, crashes, leaks):
10017 - Prevent the get_freelists() function from running off the end of
10018 the list of freelists if it somehow gets an unrecognized
10019 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
10021 - Avoid a memory leak where we would leak a consensus body when we
10022 find that a consensus which we couldn't previously verify due to
10023 missing certificates is now verifiable. Fixes bug 8719; bugfix
10025 - If we are unable to save a microdescriptor to the journal, do not
10026 drop it from memory and then reattempt downloading it. Fixes bug
10027 9645; bugfix on 0.2.2.6-alpha.
10028 - Fix an assertion failure that would occur when disabling the
10029 ORPort setting on a running Tor process while accounting was
10030 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10031 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
10032 when an exit connection with optimistic data succeeds immediately
10033 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
10035 - Fix a memory leak that would occur whenever a configuration
10036 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
10038 o Major bugfixes (relay rate limiting):
10039 - When a TLS write is partially successful but incomplete, remember
10040 that the flushed part has been flushed, and notice that bytes were
10041 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
10042 bugfix on Tor 0.1.0.5-rc.
10043 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
10044 to 1GB/1GB. The previous defaults were intended to be "basically
10045 infinite", but it turns out they're now limiting our 100mbit+
10046 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
10047 last time we raised it).
10048 - No longer stop reading or writing on cpuworker connections when
10049 our rate limiting buckets go empty. Now we should handle circuit
10050 handshake requests more promptly. Resolves bug 9731.
10052 o Major bugfixes (client-side privacy):
10053 - When we mark a circuit as unusable for new circuits, have it
10054 continue to be unusable for new circuits even if MaxCircuitDirtiness
10055 is increased too much at the wrong time, or the system clock jumps
10056 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
10057 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
10058 which have resolved to internal addresses") is set, apply that
10059 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
10060 - When an exit relay rejects a stream with reason "exit policy", but
10061 we only know an exit policy summary (e.g. from the microdesc
10062 consensus) for it, do not mark the relay as useless for all exiting.
10063 Instead, mark just the circuit as unsuitable for that particular
10064 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
10066 o Major bugfixes (stream isolation):
10067 - Allow applications to get proper stream isolation with
10068 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
10069 username/password authentication also offer "no authentication". Tor
10070 had previously preferred "no authentication", so the applications
10071 never actually sent Tor their auth details. Now Tor selects
10072 username/password authentication if it's offered. You can disable
10073 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
10074 bug 8117; bugfix on 0.2.3.3-alpha.
10075 - Follow the socks5 protocol when offering username/password
10076 authentication. The fix for bug 8117 exposed this bug, and it
10077 turns out real-world applications like Pidgin do care. Bugfix on
10078 0.2.3.2-alpha; fixes bug 8879.
10080 o Major bugfixes (client circuit building):
10081 - Alter circuit build timeout measurement to start at the point
10082 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
10083 initialization). This should make our timeout measurements more
10084 uniform. Previously, we were sometimes including ORconn setup time
10085 in our circuit build time measurements. Should resolve bug 3443.
10086 - If the circuit build timeout logic is disabled (via the consensus,
10087 or because we are an authority), then don't build testing circuits.
10088 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
10090 o Major bugfixes (client-side DNS):
10091 - Turn off the client-side DNS cache by default. Updating and using
10092 the DNS cache is now configurable on a per-client-port
10093 level. SOCKSPort, DNSPort, etc lines may now contain
10094 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
10095 cache these types of DNS answers when we receive them from an
10096 exit node in response to an application request on this port, and
10097 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
10098 cached DNS answers of these types, we shouldn't use them. It's
10099 potentially risky to use cached DNS answers at the client, since
10100 doing so can indicate to one exit what answers we've gotten
10101 for DNS lookups in the past. With IPv6, this becomes especially
10102 problematic. Using cached DNS answers for requests on the same
10103 circuit would present less linkability risk, since all traffic
10104 on a circuit is already linkable, but it would also provide
10105 little performance benefit: the exit node caches DNS replies
10106 too. Implements a simplified version of Proposal 205. Implements
10109 o Major bugfixes (hidden service privacy):
10110 - Limit hidden service descriptors to at most ten introduction
10111 points, to slow one kind of guard enumeration. Fixes bug 9002;
10112 bugfix on 0.1.1.11-alpha.
10114 o Major bugfixes (directory fetching):
10115 - If the time to download the next old-style networkstatus is in
10116 the future, do not decline to consider whether to download the
10117 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
10119 - We used to always request authority certificates by identity digest,
10120 meaning we'd get the newest one even when we wanted one with a
10121 different signing key. Then we would complain about being given
10122 a certificate we already had, and never get the one we really
10123 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
10124 resource to request the one we want. Fixes bug 5595; bugfix on
10127 o Major bugfixes (bridge reachability):
10128 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
10129 previously they did not, which prevented them from receiving
10130 successful connections from relays for self-test or bandwidth
10131 testing. Also, when a relay is extending a circuit to a bridge,
10132 it needs to send a NETINFO cell, even when the bridge hasn't sent
10133 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
10135 o Major bugfixes (control interface):
10136 - When receiving a new configuration file via the control port's
10137 LOADCONF command, do not treat the defaults file as absent.
10138 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
10140 o Major bugfixes (directory authorities):
10141 - Stop marking every relay as having been down for one hour every
10142 time we restart a directory authority. These artificial downtimes
10143 were messing with our Stable and Guard flag calculations. Fixes
10144 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
10145 - When computing directory thresholds, ignore any rejected-as-sybil
10146 nodes during the computation so that they can't influence Fast,
10147 Guard, etc. (We should have done this for proposal 109.) Fixes
10149 - When marking a node as a likely sybil, reset its uptime metrics
10150 to zero, so that it cannot time towards getting marked as Guard,
10151 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
10153 - Fix a bug in the voting algorithm that could yield incorrect results
10154 when a non-naming authority declared too many flags. Fixes bug 9200;
10155 bugfix on 0.2.0.3-alpha.
10157 o Internal abstraction features:
10158 - Introduce new channel_t abstraction between circuits and
10159 or_connection_t to allow for implementing alternate OR-to-OR
10160 transports. A channel_t is an abstract object which can either be a
10161 cell-bearing channel, which is responsible for authenticating and
10162 handshaking with the remote OR and transmitting cells to and from
10163 it, or a listening channel, which spawns new cell-bearing channels
10164 at the request of remote ORs. Implements part of ticket 6465.
10165 - Make a channel_tls_t subclass of channel_t, adapting it to the
10166 existing or_connection_t code. The V2/V3 protocol handshaking
10167 code which formerly resided in command.c has been moved below the
10168 channel_t abstraction layer and may be found in channeltls.c now.
10169 Implements the rest of ticket 6465.
10170 - Introduce new circuitmux_t storing the queue of circuits for
10171 a channel; this encapsulates and abstracts the queue logic and
10172 circuit selection policy, and allows the latter to be overridden
10173 easily by switching out a policy object. The existing EWMA behavior
10174 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
10176 o New build requirements:
10177 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
10178 strongly recommended.
10179 - Tor maintainers now require Automake version 1.9 or later to build
10180 Tor from the Git repository. (Automake is not required when building
10181 from a source distribution.)
10183 o Minor features (protocol):
10184 - No longer include the "opt" prefix when generating routerinfos
10185 or v2 directories: it has been needless since Tor 0.1.2. Closes
10187 - Reject EXTEND cells sent to nonexistent streams. According to the
10188 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
10189 we were only checking for stream IDs that were currently in use.
10190 Found while hunting for more instances of bug 6271. Bugfix on
10191 0.0.2pre8, which introduced incremental circuit construction.
10192 - Tor relays and clients now support a better CREATE/EXTEND cell
10193 format, allowing the sender to specify multiple address, identity,
10194 and handshake types. Implements Robert Ransom's proposal 200;
10195 closes ticket 7199.
10196 - Reject as invalid most directory objects containing a NUL.
10197 Belt-and-suspender fix for bug 8037.
10199 o Minor features (security):
10200 - Clear keys and key-derived material left on the stack in
10201 rendservice.c and rendclient.c. Check return value of
10202 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
10203 These fixes should make us more forward-secure against cold-boot
10204 attacks and the like. Fixes bug 2385.
10205 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
10206 Irix's random() only return 15 bits; Solaris's random() returns more
10207 bits but its RAND_MAX says it only returns 15, and so on. Motivated
10208 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
10210 o Minor features (control protocol):
10211 - Add a "GETINFO signal/names" control port command. Implements
10213 - Provide default values for all options via "GETINFO config/defaults".
10214 Implements ticket 4971.
10215 - Allow an optional $ before the node identity digest in the
10216 controller command GETINFO ns/id/<identity>, for consistency with
10217 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
10218 - Add CACHED keyword to ADDRMAP events in the control protocol
10219 to indicate whether a DNS result will be cached or not. Resolves
10221 - Generate bootstrapping status update events correctly when fetching
10222 microdescriptors. Fixes bug 9927.
10224 o Minor features (path selection):
10225 - When deciding whether we have enough descriptors to build circuits,
10226 instead of looking at raw relay counts, look at which fraction
10227 of (bandwidth-weighted) paths we're able to build. This approach
10228 keeps clients from building circuits if their paths are likely to
10229 stand out statistically. The default fraction of paths needed is
10230 taken from the consensus directory; you can override it with the
10231 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
10232 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
10233 and we have GeoIP information, also exclude all nodes with unknown
10234 countries "??" and "A1". This behavior is controlled by the
10235 new GeoIPExcludeUnknown option: you can make such nodes always
10236 excluded with "GeoIPExcludeUnknown 1", and disable the feature
10237 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
10238 gets you the default behavior. Implements feature 7706.
10240 o Minor features (hidden services):
10241 - Improve circuit build timeout handling for hidden services.
10242 In particular: adjust build timeouts more accurately depending
10243 upon the number of hop-RTTs that a particular circuit type
10244 undergoes. Additionally, launch intro circuits in parallel
10245 if they timeout, and take the first one to reply as valid.
10246 - The Tor client now ignores sub-domain components of a .onion
10247 address. This change makes HTTP "virtual" hosting
10248 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
10249 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
10250 hosted on the same hidden service. Implements proposal 204.
10251 - Enable Tor to read configuration, state, and key information from
10252 a FIFO. Previously Tor would only read from files with a positive
10253 stat.st_size. Code from meejah; fixes bug 6044.
10255 o Minor features (clients):
10256 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
10257 microdescriptor-related dir requests, and only fall back to normal
10258 descriptors if none of their bridges can handle microdescriptors
10259 (as opposed to the fix in ticket 4013, which caused them to fall
10260 back to normal descriptors if *any* of their bridges preferred
10261 them). Resolves ticket 4994.
10262 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
10263 TCP ports to forward. In the past it only accepted two ports:
10264 the ORPort and the DirPort.
10266 o Minor features (protecting client timestamps):
10267 - Clients no longer send timestamps in their NETINFO cells. These were
10268 not used for anything, and they provided one small way for clients
10269 to be distinguished from each other as they moved from network to
10270 network or behind NAT. Implements part of proposal 222.
10271 - Clients now round timestamps in INTRODUCE cells down to the nearest
10272 10 minutes. If a new Support022HiddenServices option is set to 0, or
10273 if it's set to "auto" and the feature is disabled in the consensus,
10274 the timestamp is sent as 0 instead. Implements part of proposal 222.
10275 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10276 a big deal from a security point of view, but it achieves no actual
10277 good purpose, and isn't needed. Implements part of proposal 222.
10278 - Reduce down accuracy of timestamps in hidden service descriptors.
10279 Implements part of proposal 222.
10281 o Minor features (bridges):
10282 - Make bridge relays check once a minute for whether their IP
10283 address has changed, rather than only every 15 minutes. Resolves
10284 bugs 1913 and 1992.
10285 - Bridge statistics now count bridge clients connecting over IPv6:
10286 bridge statistics files now list "bridge-ip-versions" and
10287 extra-info documents list "geoip6-db-digest". The control protocol
10288 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
10289 implementation by "shkoo", addressing ticket 5055.
10290 - Add a new torrc option "ServerTransportListenAddr" to let bridge
10291 operators select the address where their pluggable transports will
10292 listen for connections. Resolves ticket 7013.
10293 - Randomize the lifetime of our SSL link certificate, so censors can't
10294 use the static value for filtering Tor flows. Resolves ticket 8443;
10295 related to ticket 4014 which was included in 0.2.2.33.
10297 o Minor features (relays):
10298 - Option OutboundBindAddress can be specified multiple times and
10299 accepts IPv6 addresses. Resolves ticket 6876.
10301 o Minor features (IPv6, client side):
10302 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
10303 prefer to hand out virtual IPv6 addresses, since there are more of
10304 them and we can't run out. To override this behavior and make IPv4
10305 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
10306 or DNSPort you're using for resolving. Implements ticket 7571.
10307 - AutomapHostsOnResolve responses are now randomized, to avoid
10308 annoying situations where Tor is restarted and applications
10309 connect to the wrong addresses.
10310 - Never try more than 1000 times to pick a new virtual address when
10311 AutomapHostsOnResolve is set. That's good enough so long as we
10312 aren't close to handing out our entire virtual address space;
10313 if you're getting there, it's best to switch to IPv6 virtual
10316 o Minor features (IPv6, relay/authority side):
10317 - New config option "AuthDirHasIPv6Connectivity 1" that directory
10318 authorities should set if they have IPv6 connectivity and want to
10319 do reachability tests for IPv6 relays. Implements feature 5974.
10320 - A relay with an IPv6 OR port now sends that address in NETINFO
10321 cells (in addition to its other address). Implements ticket 6364.
10323 o Minor features (directory authorities):
10324 - Directory authorities no long accept descriptors for any version of
10325 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
10326 These versions are insecure, unsupported, or both. Implements
10328 - When directory authorities are computing thresholds for flags,
10329 never let the threshold for the Fast flag fall below 4096
10330 bytes. Also, do not consider nodes with extremely low bandwidths
10331 when deciding thresholds for various directory flags. This change
10332 should raise our threshold for Fast relays, possibly in turn
10333 improving overall network performance; see ticket 1854. Resolves
10335 - Directory authorities now include inside each vote a statement of
10336 the performance thresholds they used when assigning flags.
10337 Implements ticket 8151.
10338 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
10339 in directory authority votes to describe whether they have enough
10340 measured bandwidths to ignore advertised (relay descriptor)
10341 bandwidth claims. Resolves ticket 8711.
10343 o Minor features (path bias detection):
10344 - Path Use Bias: Perform separate accounting for successful circuit
10345 use. Keep separate statistics on stream attempt rates versus stream
10346 success rates for each guard. Provide configurable thresholds to
10347 determine when to emit log messages or disable use of guards that
10348 fail too many stream attempts. Resolves ticket 7802.
10349 - Create three levels of Path Bias log messages, as opposed to just
10350 two. These are configurable via consensus as well as via the torrc
10351 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
10352 The default values are 0.70, 0.50, and 0.30 respectively.
10353 - Separate the log message levels from the decision to drop guards,
10354 which also is available via torrc option PathBiasDropGuards.
10355 PathBiasDropGuards still defaults to 0 (off).
10356 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
10357 in combination with PathBiasExtremeRate.
10358 - Increase the default values for PathBiasScaleThreshold and
10359 PathBiasCircThreshold from (200, 20) to (300, 150).
10360 - Add in circuit usage accounting to path bias. If we try to use a
10361 built circuit but fail for any reason, it counts as path bias.
10362 Certain classes of circuits where the adversary gets to pick your
10363 destination node are exempt from this accounting. Usage accounting
10364 can be specifically disabled via consensus parameter or torrc.
10365 - Convert all internal path bias state to double-precision floating
10366 point, to avoid roundoff error and other issues.
10367 - Only record path bias information for circuits that have completed
10368 *two* hops. Assuming end-to-end tagging is the attack vector, this
10369 makes us more resilient to ambient circuit failure without any
10370 detection capability loss.
10372 o Minor features (build):
10373 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
10374 dhill. Resolves ticket 6982.
10375 - Compile on win64 using mingw64. Fixes bug 7260; patches from
10377 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
10378 separate error codes; or at least, don't break for that reason.
10379 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
10381 o Build improvements (autotools):
10382 - Warn if building on a platform with an unsigned time_t: there
10383 are too many places where Tor currently assumes that time_t can
10384 hold negative values. We'd like to fix them all, but probably
10386 - Do not report status verbosely from autogen.sh unless the -v flag
10387 is specified. Fixes issue 4664. Patch from Onizuka.
10388 - Detect and reject attempts to build Tor with threading support
10389 when OpenSSL has been compiled without threading support.
10391 - Try to detect if we are ever building on a platform where
10392 memset(...,0,...) does not set the value of a double to 0.0. Such
10393 platforms are permitted by the C standard, though in practice
10394 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
10395 currently support them, but it's better to detect them and fail
10396 than to perform erroneously.
10397 - We no longer warn so much when generating manpages from their
10399 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
10400 the signs of types during autoconf. This is better than our old
10401 approach, which didn't work when cross-compiling.
10403 o Minor features (log messages, warnings):
10404 - Detect when we're running with a version of OpenSSL other than the
10405 one we compiled with. This conflict has occasionally given people
10406 hard-to-track-down errors.
10407 - Warn users who run hidden services on a Tor client with
10408 UseEntryGuards disabled that their hidden services will be
10409 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
10410 attack which motivated Tor to support entry guards in the first
10411 place). Resolves ticket 6889.
10412 - Warn when we are binding low ports when hibernation is enabled;
10413 previously we had warned when we were _advertising_ low ports with
10414 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
10415 - Issue a warning when running with the bufferevents backend enabled.
10416 It's still not stable, and people should know that they're likely
10417 to hit unexpected problems. Closes ticket 9147.
10419 o Minor features (log messages, notices):
10420 - Refactor resolve_my_address() so it returns the method by which we
10421 decided our public IP address (explicitly configured, resolved from
10422 explicit hostname, guessed from interfaces, learned by gethostname).
10423 Now we can provide more helpful log messages when a relay guesses
10424 its IP address incorrectly (e.g. due to unexpected lines in
10425 /etc/hosts). Resolves ticket 2267.
10426 - Track how many "TAP" and "NTor" circuit handshake requests we get,
10427 and how many we complete, and log it every hour to help relay
10428 operators follow trends in network load. Addresses ticket 9658.
10430 o Minor features (log messages, diagnostics):
10431 - If we fail to free a microdescriptor because of bug 7164, log
10432 the filename and line number from which we tried to free it.
10433 - We compute the overhead from passing onionskins back and forth to
10434 cpuworkers, and report it when dumping statistics in response to
10435 SIGUSR1. Supports ticket 7291.
10436 - Add another diagnostic to the heartbeat message: track and log
10437 overhead that TLS is adding to the data we write. If this is
10438 high, we are sending too little data to SSL_write at a time.
10439 Diagnostic for bug 7707.
10440 - Log packaged cell fullness as part of the heartbeat message.
10441 Diagnosis to try to determine the extent of bug 7743.
10442 - Add more detail to a log message about relaxed timeouts, to help
10444 - When learning a fingerprint for a bridge, log its corresponding
10445 transport type. Implements ticket 7896.
10446 - Warn more aggressively when flushing microdescriptors to a
10447 microdescriptor cache fails, in an attempt to mitigate bug 8031,
10448 or at least make it more diagnosable.
10449 - Improve the log message when "Bug/attack: unexpected sendme cell
10450 from client" occurs, to help us track bug 8093.
10451 - Improve debugging output to help track down bug 8185 ("Bug:
10452 outgoing relay cell has n_chan==NULL. Dropping.")
10454 o Minor features (log messages, quieter bootstrapping):
10455 - Log fewer lines at level "notice" about our OpenSSL and Libevent
10456 versions and capabilities when everything is going right. Resolves
10457 part of ticket 6736.
10458 - Omit the first heartbeat log message, because it never has anything
10459 useful to say, and it clutters up the bootstrapping messages.
10460 Resolves ticket 6758.
10461 - Don't log about reloading the microdescriptor cache at startup. Our
10462 bootstrap warnings are supposed to tell the user when there's a
10463 problem, and our bootstrap notices say when there isn't. Resolves
10464 ticket 6759; bugfix on 0.2.2.6-alpha.
10465 - Don't log "I learned some more directory information" when we're
10466 reading cached directory information. Reserve it for when new
10467 directory information arrives in response to a fetch. Resolves
10469 - Don't complain about bootstrapping problems while hibernating.
10470 These complaints reflect a general code problem, but not one
10471 with any problematic effects (no connections are actually
10472 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
10474 o Minor features (testing):
10475 - In our testsuite, create temporary directories with a bit more
10476 entropy in their name to make name collisions less likely. Fixes
10478 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
10479 (P-256) Diffie-Hellman handshakes to src/or/bench.
10480 - Add benchmark functions to test onion handshake performance.
10483 - The DirServer option is now DirAuthority, for consistency with
10484 current naming patterns. You can still use the old DirServer form.
10486 o Minor bugfixes (protocol):
10487 - Fix the handling of a TRUNCATE cell when it arrives while the
10488 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
10489 - When a Tor client gets a "truncated" relay cell, the first byte of
10490 its payload specifies why the circuit was truncated. We were
10491 ignoring this 'reason' byte when tearing down the circuit, resulting
10492 in the controller not being told why the circuit closed. Now we
10493 pass the reason from the truncated cell to the controller. Bugfix
10494 on 0.1.2.3-alpha; fixes bug 7039.
10495 - Fix a misframing issue when reading the version numbers in a
10496 VERSIONS cell. Previously we would recognize [00 01 00 02] as
10497 'version 1, version 2, and version 0x100', when it should have
10498 only included versions 1 and 2. Fixes bug 8059; bugfix on
10499 0.2.0.10-alpha. Reported pseudonymously.
10500 - Make the format and order of STREAM events for DNS lookups
10501 consistent among the various ways to launch DNS lookups. Fixes
10502 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
10504 o Minor bugfixes (syscalls and disk interaction):
10505 - Always check the return values of functions fcntl() and
10506 setsockopt(). We don't believe these are ever actually failing in
10507 practice, but better safe than sorry. Also, checking these return
10508 values should please analysis tools like Coverity. Patch from
10509 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
10510 - Avoid double-closing the listener socket in our socketpair()
10511 replacement (used on Windows) in the case where the addresses on
10512 our opened sockets don't match what we expected. Fixes bug 9400;
10513 bugfix on 0.0.2pre7. Found by Coverity.
10514 - Correctly store microdescriptors and extrainfo descriptors that
10515 include an internal NUL byte. Fixes bug 8037; bugfix on
10516 0.2.0.1-alpha. Bug reported by "cypherpunks".
10517 - If for some reason we fail to write a microdescriptor while
10518 rebuilding the cache, do not let the annotations from that
10519 microdescriptor linger in the cache file, and do not let the
10520 microdescriptor stay recorded as present in its old location.
10521 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
10522 - Use direct writes rather than stdio when building microdescriptor
10523 caches, in an attempt to mitigate bug 8031, or at least make it
10526 o Minor fixes (config options):
10527 - Warn and fail if a server is configured not to advertise any
10528 ORPorts at all. (We need *something* to put in our descriptor,
10529 or we just won't work.)
10530 - Behave correctly when the user disables LearnCircuitBuildTimeout
10531 but doesn't tell us what they would like the timeout to be. Fixes
10532 bug 6304; bugfix on 0.2.2.14-alpha.
10533 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
10534 to start with a triple-underscore so the controller won't touch it.
10535 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
10536 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
10537 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
10538 - When autodetecting the number of CPUs, use the number of available
10539 CPUs in preference to the number of configured CPUs. Inform the
10540 user if this reduces the number of available CPUs. Fixes bug 8002;
10541 bugfix on 0.2.3.1-alpha.
10542 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
10543 - Make it an error when you set EntryNodes but disable UseGuardNodes,
10544 since it will (surprisingly to some users) ignore EntryNodes. Fixes
10545 bug 8180; bugfix on 0.2.3.11-alpha.
10546 - Avoid overflows when the user sets MaxCircuitDirtiness to a
10547 ridiculously high value, by imposing a (ridiculously high) 30-day
10548 maximum on MaxCircuitDirtiness.
10550 o Minor bugfixes (control protocol):
10551 - Stop sending a stray "(null)" in some cases for the server status
10552 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
10554 - The ADDRMAP command can no longer generate an ill-formed error
10555 code on a failed MAPADDRESS. It now says "internal" rather than
10556 an English sentence fragment with spaces in the middle. Bugfix on
10557 Tor 0.2.0.19-alpha.
10559 o Minor bugfixes (clients / edges):
10560 - When we receive a RELAY_END cell with the reason DONE, or with no
10561 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
10562 status as "connection refused". Previously we reported these cases
10563 as success but then immediately closed the connection. Fixes bug
10564 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
10565 - If the guard we choose first doesn't answer, we would try the
10566 second guard, but once we connected to the second guard we would
10567 abandon it and retry the first one, slowing down bootstrapping.
10568 The fix is to treat all our initially chosen guards as acceptable
10569 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10570 - When choosing which stream on a formerly stalled circuit to wake
10571 first, make better use of the platform's weak RNG. Previously,
10572 we had been using the % ("modulo") operator to try to generate a
10573 1/N chance of picking each stream, but this behaves badly with
10574 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
10577 o Minor bugfixes (path bias detection):
10578 - If the state file's path bias counts are invalid (presumably from a
10579 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
10580 additional checks and log messages to the scaling of Path Bias
10581 counts, in case there still are remaining issues with scaling.
10582 Should help resolve bug 8235.
10583 - Prevent rounding error in path bias counts when scaling
10584 them down, and use the correct scale factor default. Also demote
10585 some path bias related log messages down a level and make others
10586 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
10587 - Remove a source of rounding error during path bias count scaling;
10588 don't count cannibalized circuits as used for path bias until we
10589 actually try to use them; and fix a circuit_package_relay_cell()
10590 warning message about n_chan==NULL. Fixes bug 7802.
10591 - Paste the description for PathBias parameters from the man
10592 page into or.h, so the code documents them too. Fixes bug 7982;
10593 bugfix on 0.2.3.17-beta.
10595 o Minor bugfixes (relays):
10596 - Stop trying to resolve our hostname so often (e.g. every time we
10597 think about doing a directory fetch). Now we reuse the cached
10598 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
10599 and 2410 (bugfix on 0.1.2.2-alpha).
10600 - When examining the list of network interfaces to find our address,
10601 do not consider non-running or disabled network interfaces. Fixes
10602 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10604 o Minor bugfixes (blocking resistance):
10605 - Only disable TLS session ticket support when running as a TLS
10606 server. Now clients will blend better with regular Firefox
10607 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
10609 o Minor bugfixes (IPv6):
10610 - Use square brackets around IPv6 addresses in numerous places
10611 that needed them, including log messages, HTTPS CONNECT proxy
10612 requests, TransportProxy statefile entries, and pluggable transport
10613 extra-info lines. Fixes bug 7011; patch by David Fifield.
10615 o Minor bugfixes (directory authorities):
10616 - Reject consensus votes with more than 64 known-flags. We aren't even
10617 close to that limit yet, and our code doesn't handle it correctly.
10618 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
10619 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
10620 bugfix on 0.2.0.3-alpha.
10622 o Minor bugfixes (memory leaks):
10623 - Avoid leaking memory if we fail to compute a consensus signature
10624 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
10625 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
10626 on 0.2.1.1-alpha; fixes bug 7816.
10627 - Fix a memory leak during safe-cookie controller authentication.
10628 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
10629 - Free some more still-in-use memory at exit, to make hunting for
10630 memory leaks easier. Resolves bug 7029.
10632 o Minor bugfixes (code correctness):
10633 - Increase the width of the field used to remember a connection's
10634 link protocol version to two bytes. Harmless for now, since the
10635 only currently recognized versions are one byte long. Reported
10636 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
10637 - Fix a crash when debugging unit tests on Windows: deallocate a
10638 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
10639 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
10640 - When detecting the largest possible file descriptor (in order to
10641 close all file descriptors when launching a new program), actually
10642 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
10643 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
10645 - Avoid a crash if we fail to generate an extrainfo descriptor.
10646 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
10647 this is CID 718634.
10648 - Avoid an off-by-one error when checking buffer boundaries when
10649 formatting the exit status of a pluggable transport helper.
10650 This is probably not an exploitable bug, but better safe than
10651 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10653 - Get rid of a couple of harmless clang warnings, where we compared
10654 enums to ints. These warnings are newly introduced in clang 3.2.
10656 o Minor bugfixes (code cleanliness):
10657 - Avoid use of reserved identifiers in our C code. The C standard
10658 doesn't like us declaring anything that starts with an
10659 underscore, so let's knock it off before we get in trouble. Fix
10660 for bug 1031; bugfix on the first Tor commit.
10661 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
10662 with large values. This situation was untriggered, but nevertheless
10663 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
10664 - Fix an impossible buffer overrun in the AES unit tests. Fixes
10665 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
10666 - Fix handling of rendezvous client authorization types over 8.
10667 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
10668 - Remove a couple of extraneous semicolons that were upsetting the
10669 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
10670 bugfix on 0.2.2.1-alpha.
10671 - When complaining about a client port on a public address, log
10672 which address we're complaining about. Fixes bug 4020; bugfix on
10673 0.2.3.3-alpha. Patch by Tom Fitzhenry.
10675 o Minor bugfixes (log messages, warnings):
10676 - If we encounter a write failure on a SOCKS connection before we
10677 finish our SOCKS handshake, don't warn that we closed the
10678 connection before we could send a SOCKS reply. Fixes bug 8427;
10679 bugfix on 0.1.0.1-rc.
10680 - Fix a directory authority warn caused when we have a large amount
10681 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
10682 - Downgrade "Failed to hand off onionskin" messages to "debug"
10683 severity, since they're typically redundant with the "Your computer
10684 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
10685 - Avoid spurious warnings when configuring multiple client ports of
10686 which only some are nonlocal. Previously, we had claimed that some
10687 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
10690 o Minor bugfixes (log messages, other):
10691 - Fix log messages and comments to avoid saying "GMT" when we mean
10692 "UTC". Fixes bug 6113.
10693 - When rejecting a configuration because we were unable to parse a
10694 quoted string, log an actual error message. Fixes bug 7950; bugfix
10696 - Correctly recognize that [::1] is a loopback address. Fixes
10697 bug 8377; bugfix on 0.2.1.3-alpha.
10698 - Don't log inappropriate heartbeat messages when hibernating: a
10699 hibernating node is _expected_ to drop out of the consensus,
10700 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
10701 bugfix on 0.2.3.1-alpha.
10702 - Eliminate several instances where we use "Nickname=ID" to refer to
10703 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
10704 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
10707 o Minor bugfixes (build):
10708 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
10709 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
10710 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
10712 o Documentation fixes:
10713 - Make the torify manpage no longer refer to tsocks; torify hasn't
10714 supported tsocks since 0.2.3.14-alpha.
10715 - Make the tor manpage no longer reference tsocks.
10716 - Fix the GeoIPExcludeUnknown documentation to refer to
10717 ExcludeExitNodes rather than the currently nonexistent
10718 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
10719 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
10721 - Say "KBytes" rather than "KB" in the man page (for various values
10722 of K), to further reduce confusion about whether Tor counts in
10723 units of memory or fractions of units of memory. Resolves ticket 7054.
10724 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
10725 names match. Fixes bug 7768.
10726 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
10727 message is logged at notice, not at info.
10728 - Clarify the usage and risks of setting the ContactInfo torrc line
10729 for your relay or bridge. Resolves ticket 9854.
10730 - Add anchors to the manpage so we can link to the html version of
10731 the documentation for specific options. Resolves ticket 9866.
10732 - Replace remaining references to DirServer in man page and
10733 log entries. Resolves ticket 10124.
10735 o Removed features:
10736 - Stop exporting estimates of v2 and v3 directory traffic shares
10737 in extrainfo documents. They were unneeded and sometimes inaccurate.
10738 Also stop exporting any v2 directory request statistics. Resolves
10740 - Drop support for detecting and warning about versions of Libevent
10741 before 1.3e. Nothing reasonable ships with them any longer; warning
10742 the user about them shouldn't be needed. Resolves ticket 6826.
10743 - Now that all versions before 0.2.2.x are disallowed, we no longer
10744 need to work around their missing features. Remove a bunch of
10745 compatibility code.
10748 - The tor-tsocks.conf is no longer distributed or installed. We
10749 recommend that tsocks users use torsocks instead. Resolves
10751 - Remove some of the older contents of doc/ as obsolete; move others
10752 to torspec.git. Fixes bug 8965.
10754 o Code simplification:
10755 - Avoid using character buffers when constructing most directory
10756 objects: this approach was unwieldy and error-prone. Instead,
10757 build smartlists of strings, and concatenate them when done.
10758 - Rename "isin" functions to "contains", for grammar. Resolves
10760 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
10761 with the natural logarithm function from the system libm. Resolves
10763 - Start using OpenBSD's implementation of queue.h, so that we don't
10764 need to hand-roll our own pointer and list structures whenever we
10765 need them. (We can't rely on a sys/queue.h, since some operating
10766 systems don't have them, and the ones that do have them don't all
10767 present the same extensions.)
10768 - Start using OpenBSD's implementation of queue.h (originally by
10770 - Enhance our internal sscanf replacement so that we can eliminate
10771 the last remaining uses of the system sscanf. (Though those uses
10772 of sscanf were safe, sscanf itself is generally error prone, so
10773 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
10775 - Replace all calls to snprintf() outside of src/ext with
10776 tor_snprintf(). Also remove the #define to replace snprintf with
10777 _snprintf on Windows; they have different semantics, and all of
10778 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
10781 - Add a wrapper function for the common "log a message with a
10783 - Split the onion.c file into separate modules for the onion queue
10784 and the different handshakes it supports.
10785 - Move the client-side address-map/virtual-address/DNS-cache code
10786 out of connection_edge.c into a new addressmap.c module.
10787 - Move the entry node code from circuitbuild.c to its own file.
10788 - Move the circuit build timeout tracking code from circuitbuild.c
10790 - Source files taken from other packages now reside in src/ext;
10791 previously they were scattered around the rest of Tor.
10792 - Move the generic "config" code into a new file, and have "config.c"
10793 hold only torrc- and state-related code. Resolves ticket 6823.
10794 - Move the core of our "choose a weighted element at random" logic
10795 into its own function, and give it unit tests. Now the logic is
10796 testable, and a little less fragile too.
10797 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
10798 - Move last_reachable and testing_since from routerinfo_t to node_t.
10799 Implements ticket 5529.
10800 - Add replaycache_t structure, functions and unit tests, then refactor
10801 rend_service_introduce() to be more clear to read, improve, debug,
10802 and test. Resolves bug 6177.
10805 - Remove some now-needless code that tried to aggressively flush
10806 OR connections as data was added to them. Since 0.2.0.1-alpha, our
10807 cell queue logic has saved us from the failure mode that this code
10808 was supposed to prevent. Removing this code will limit the number
10809 of baroque control flow paths through Tor's network logic. Reported
10810 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
10811 - Remove unused code for parsing v1 directories and "running routers"
10812 documents. Fixes bug 6887.
10813 - Remove the marshalling/unmarshalling code for sending requests to
10814 cpuworkers over a socket, and instead just send structs. The
10815 recipient will always be the same Tor binary as the sender, so
10816 any encoding is overkill.
10817 - Remove the testing_since field of node_t, which hasn't been used
10818 for anything since 0.2.0.9-alpha.
10819 - Finally remove support for malloc_good_size and malloc_usable_size.
10820 We had hoped that these functions would let us eke a little more
10821 memory out of our malloc implementation. Unfortunately, the only
10822 implementations that provided these functions are also ones that
10823 are already efficient about not overallocation: they never got us
10824 more than 7 or so bytes per allocation. Removing them saves us a
10825 little code complexity and a nontrivial amount of build complexity.
10828 Changes in version 0.2.3.25 - 2012-11-19
10829 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
10830 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
10831 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
10832 programmer, and friend. Unstinting in his dedication to the cause of
10833 freedom, he inspired and helped many of us as we began our work on
10834 anonymity, and inspires us still. Please honor his memory by writing
10835 software to protect people's freedoms, and by helping others to do so.
10837 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
10838 significantly reduced directory overhead (via microdescriptors),
10839 enormous crypto performance improvements for fast relays on new
10840 enough hardware, a new v3 TLS handshake protocol that can better
10841 resist fingerprinting, support for protocol obfuscation plugins (aka
10842 pluggable transports), better scalability for hidden services, IPv6
10843 support for bridges, performance improvements like allowing clients
10844 to skip the first round-trip on the circuit ("optimistic data") and
10845 refilling token buckets more often, a new "stream isolation" design
10846 to isolate different applications on different circuits, and many
10847 stability, security, and privacy fixes.
10849 Major features (v3 directory protocol):
10850 - Clients now use microdescriptors instead of regular descriptors
10851 to build circuits. Microdescriptors are authority-generated
10852 summaries of regular descriptors' contents, designed to change very
10853 rarely (see proposal 158 for details). This feature is designed
10854 to save bandwidth, especially for clients on slow internet
10855 connections. Use "UseMicrodescriptors 0" to disable it.
10856 - Caches now download, cache, and serve microdescriptors, as well
10857 as multiple "flavors" of the consensus, including a flavor that
10858 describes microdescriptors.
10860 o Major features (build hardening):
10861 - Enable gcc and ld hardening by default. Resolves ticket 5210.
10863 o Major features (relay scaling):
10864 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
10865 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
10866 vectorized AES implementations as appropriate. These can be much,
10867 much faster than other AES implementations.
10868 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
10869 implementation. It makes AES_CTR about 7% faster than our old one
10870 (which was about 10% faster than the one OpenSSL used to provide).
10871 Resolves ticket 4526.
10872 - Use OpenSSL's EVP interface for AES encryption, so that all AES
10873 operations can use hardware acceleration (if present). Resolves
10875 - Unconditionally use OpenSSL's AES implementation instead of our
10876 old built-in one. OpenSSL's AES has been better for a while, and
10877 relatively few servers should still be on any version of OpenSSL
10878 that doesn't have good optimized assembly AES.
10880 o Major features (blocking resistance):
10881 - Update TLS cipher list to match Firefox 8 and later. Resolves
10883 - Remove support for clients falsely claiming to support standard
10884 ciphersuites that they can actually provide. As of modern OpenSSL
10885 versions, it's not necessary to fake any standard ciphersuite,
10886 and doing so prevents us from using better ciphersuites in the
10887 future, since servers can't know whether an advertised ciphersuite
10888 is really supported or not. Some hosts -- notably, ones with very
10889 old versions of OpenSSL or where OpenSSL has been built with ECC
10890 disabled -- will stand out because of this change; TBB users should
10891 not be affected. Implements the client side of proposal 198.
10892 - Implement a new handshake protocol (v3) for authenticating Tors to
10893 each other over TLS. It should be more resistant to fingerprinting
10894 than previous protocols, and should require less TLS hacking for
10895 future Tor implementations. Implements proposal 176.
10896 - Allow variable-length padding cells, to disguise the length of
10897 Tor's TLS records. Implements part of proposal 184.
10898 - While we're trying to bootstrap, record how many TLS connections
10899 fail in each state, and report which states saw the most failures
10900 in response to any bootstrap failures. This feature may speed up
10901 diagnosis of censorship events. Implements ticket 3116.
10903 o Major features (pluggable transports):
10904 - Clients and bridges can now be configured to use a separate
10905 "transport" proxy. This approach makes the censorship arms race
10906 easier by allowing bridges to use protocol obfuscation plugins.
10907 Implements proposal 180 (tickets 2841 and 3472).
10909 o Major features (DoS resistance):
10910 - Now that Tor 0.2.0.x is completely deprecated, enable the final
10911 part of "Proposal 110: Avoiding infinite length circuits" by
10912 refusing all circuit-extend requests that do not use a relay_early
10913 cell. This change helps Tor resist a class of denial-of-service
10914 attacks by limiting the maximum circuit length.
10915 - Tear down the circuit if we get an unexpected SENDME cell. Clients
10916 could use this trick to make their circuits receive cells faster
10917 than our flow control would have allowed, or to gum up the network,
10918 or possibly to do targeted memory denial-of-service attacks on
10919 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
10920 from July 2002, before the release of Tor 0.0.0.
10922 o Major features (hidden services):
10923 - Adjust the number of introduction points that a hidden service
10924 will try to maintain based on how long its introduction points
10925 remain in use and how many introductions they handle. Fixes
10927 - Add a "tor2web mode" for clients that want to connect to hidden
10928 services non-anonymously (and possibly more quickly). As a safety
10929 measure to try to keep users from turning this on without knowing
10930 what they are doing, tor2web mode must be explicitly enabled at
10931 compile time, and a copy of Tor compiled to run in tor2web mode
10932 cannot be used as a normal Tor client. Implements feature 2553.
10934 o Major features (IPv6):
10935 - Clients can now connect to private bridges over IPv6. Bridges
10936 still need at least one IPv4 address in order to connect to
10937 other relays. Note that we don't yet handle the case where the
10938 user has two bridge lines for the same bridge (one IPv4, one
10939 IPv6). Implements parts of proposal 186.
10941 o Major features (directory authorities):
10942 - Use a more secure consensus parameter voting algorithm. Now at
10943 least three directory authorities or a majority of them must
10944 vote on a given parameter before it will be included in the
10945 consensus. Implements proposal 178.
10946 - Remove the artificially low cutoff of 20KB to guarantee the Fast
10947 flag. In the past few years the average relay speed has picked
10948 up, and while the "top 7/8 of the network get the Fast flag" and
10949 "all relays with 20KB or more of capacity get the Fast flag" rules
10950 used to have the same result, now the top 7/8 of the network has
10951 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
10953 o Major features (performance):
10954 - Exit nodes now accept and queue data on not-yet-connected streams.
10955 Previously, the client wasn't allowed to send data until the
10956 stream was connected, which slowed down all connections. This
10957 change will enable clients to perform a "fast-start" on streams
10958 and send data without having to wait for a confirmation that the
10959 stream has opened. Patch from Ian Goldberg; implements the server
10960 side of Proposal 174.
10961 - When using an exit relay running 0.2.3.x, clients can now
10962 "optimistically" send data before the exit relay reports that
10963 the stream has opened. This saves a round trip when starting
10964 connections where the client speaks first (such as web browsing).
10965 This behavior is controlled by a consensus parameter (currently
10966 disabled). To turn it on or off manually, use the "OptimisticData"
10967 torrc option. Implements proposal 181; code by Ian Goldberg.
10968 - Add a new TokenBucketRefillInterval option to refill token buckets
10969 more frequently than once per second. This should improve network
10970 performance, alleviate queueing problems, and make traffic less
10971 bursty. Implements proposal 183; closes ticket 3630. Design by
10972 Florian Tschorsch and Björn Scheuermann; implementation by
10974 - Raise the threshold of server descriptors needed (75%) and exit
10975 server descriptors needed (50%) before we will declare ourselves
10976 bootstrapped. This will make clients start building circuits a
10977 little later, but makes the initially constructed circuits less
10978 skewed and less in conflict with further directory fetches. Fixes
10981 o Major features (relays):
10982 - Relays now try regenerating and uploading their descriptor more
10983 frequently if they are not listed in the consensus, or if the
10984 version of their descriptor listed in the consensus is too
10985 old. This fix should prevent situations where a server declines
10986 to re-publish itself because it has done so too recently, even
10987 though the authorities decided not to list its recent-enough
10988 descriptor. Fix for bug 3327.
10990 o Major features (stream isolation):
10991 - You can now configure Tor so that streams from different
10992 applications are isolated on different circuits, to prevent an
10993 attacker who sees your streams as they leave an exit node from
10994 linking your sessions to one another. To do this, choose some way
10995 to distinguish the applications: have them connect to different
10996 SocksPorts, or have one of them use SOCKS4 while the other uses
10997 SOCKS5, or have them pass different authentication strings to the
10998 SOCKS proxy. Then, use the new SocksPort syntax to configure the
10999 degree of isolation you need. This implements Proposal 171.
11000 - There's a new syntax for specifying multiple client ports (such as
11001 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
11002 multiple *Port entries with full addr:port syntax on each.
11003 The old *ListenAddress format is still supported, but you can't
11004 mix it with the new *Port syntax.
11006 o Major features (bufferevents):
11007 - Tor can now optionally build with the "bufferevents" buffered IO
11008 backend provided by Libevent 2. To use this feature, make sure you
11009 have the latest possible version of Libevent, and pass the
11010 --enable-bufferevents flag to configure when building Tor from
11011 source. This feature will make our networking code more flexible,
11012 let us stack layers on each other, and let us use more efficient
11013 zero-copy transports where available.
11014 - Add experimental support for running on Windows with IOCP and no
11015 kernel-space socket buffers. This feature is controlled by a new
11016 "UserspaceIOCPBuffers" config option (off by default), which has
11017 no effect unless Tor has been built with bufferevents enabled,
11018 you're running on Windows, and you've set "DisableIOCP 0". In the
11019 long run, this may help solve or mitigate bug 98.
11021 o Major features (path selection):
11022 - The EntryNodes option can now include country codes like {de} or IP
11023 addresses or network masks. Previously we had disallowed these
11024 options because we didn't have an efficient way to keep the list up
11025 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
11028 o Major features (port forwarding):
11029 - Add support for automatic port mapping on the many home routers
11030 that support NAT-PMP or UPnP. To build the support code, you'll
11031 need to have the libnatpnp library and/or the libminiupnpc library,
11032 and you'll need to enable the feature specifically by passing
11033 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
11034 it on, use the new PortForwarding option.
11036 o Major features (logging):
11037 - Add a new 'Heartbeat' log message type to periodically log a message
11038 describing Tor's status at level Notice. This feature is meant for
11039 operators who log at notice, and want to make sure that their Tor
11040 server is still working. Implementation by George Kadianakis.
11041 - Make logging resolution configurable with a new LogTimeGranularity
11042 option, and change the default from 1 millisecond to 1 second.
11043 Implements enhancement 1668.
11045 o Major features (other):
11046 - New "DisableNetwork" config option to prevent Tor from launching any
11047 connections or accepting any connections except on a control port.
11048 Bundles and controllers can set this option before letting Tor talk
11049 to the rest of the network, for example to prevent any connections
11050 to a non-bridge address. Packages like Orbot can also use this
11051 option to instruct Tor to save power when the network is off.
11052 - Try to use system facilities for enumerating local interface
11053 addresses, before falling back to our old approach (which was
11054 binding a UDP socket, and calling getsockname() on it). That
11055 approach was scaring OS X users whose draconian firewall
11056 software warned about binding to UDP sockets regardless of
11057 whether packets were sent. Now we try to use getifaddrs(),
11058 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
11059 system supports. Resolves ticket 1827.
11060 - Add experimental support for a "defaults" torrc file to be parsed
11061 before the regular torrc. Torrc options override the defaults file's
11062 options in the same way that the command line overrides the torrc.
11063 The SAVECONF controller command saves only those options which
11064 differ between the current configuration and the defaults file. HUP
11065 reloads both files. Implements task 4552.
11067 o New directory authorities:
11068 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
11069 authority. Closes ticket 5749.
11071 o Security/privacy fixes:
11072 - Avoid read-from-freed-memory and double-free bugs that could occur
11073 when a DNS request fails while launching it. Fixes bug 6480;
11074 bugfix on 0.2.0.1-alpha.
11075 - Reject any attempt to extend to an internal address. Without
11076 this fix, a router could be used to probe addresses on an internal
11077 network to see whether they were accepting connections. Fixes bug
11078 6710; bugfix on 0.0.8pre1.
11079 - Close any connection that sends unrecognized junk before the TLS
11080 handshake. Solves an issue noted in bug 4369.
11081 - The advertised platform of a relay now includes only its operating
11082 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
11083 its service pack level (for Windows) or its CPU architecture
11084 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
11085 can insert an extra string in the platform line by setting the
11086 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
11087 - Disable TLS session tickets. OpenSSL's implementation was giving
11088 our TLS session keys the lifetime of our TLS context objects, when
11089 perfect forward secrecy would want us to discard anything that
11090 could decrypt a link connection as soon as the link connection
11091 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
11092 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
11093 - Tor tries to wipe potentially sensitive data after using it, so
11094 that if some subsequent security failure exposes Tor's memory,
11095 the damage will be limited. But we had a bug where the compiler
11096 was eliminating these wipe operations when it decided that the
11097 memory was no longer visible to a (correctly running) program,
11098 hence defeating our attempt at defense in depth. We fix that
11099 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11100 is unlikely to optimize away. Future versions of Tor may use
11101 a less ridiculously heavy approach for this. Fixes bug 7352.
11102 Reported in an article by Andrey Karpov.
11104 o Major bugfixes (crashes and asserts):
11105 - Avoid a pair of double-free and use-after-mark bugs that can
11106 occur with certain timings in canceled and re-received DNS
11107 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
11108 - Fix a denial of service attack by which any directory authority
11109 could crash all the others, or by which a single v2 directory
11110 authority could crash everybody downloading v2 directory
11111 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
11112 - Fix an assert that directory authorities could trigger on sighup
11113 during some configuration state transitions. We now don't treat
11114 it as a fatal error when the new descriptor we just generated in
11115 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
11116 - Avoid segfault when starting up having run with an extremely old
11117 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11120 o Major bugfixes (clients):
11121 - If we are unable to find any exit that supports our predicted ports,
11122 stop calling them predicted, so that we don't loop and build
11123 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
11124 which introduced predicted ports.
11125 - Check at each new consensus whether our entry guards were picked
11126 long enough ago that we should rotate them. Previously, we only
11127 did this check at startup, which could lead to us holding a guard
11128 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
11129 - When fetching a bridge descriptor from a bridge authority,
11130 always do so anonymously, whether we have been able to open
11131 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
11132 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
11133 but we'll need to wait for bug 6010 before it's actually usable.
11135 o Major bugfixes (directory voting):
11136 - Check more thoroughly to prevent a rogue authority from
11137 double-voting on any consensus directory parameter. Previously,
11138 authorities would crash in this case if the total number of
11139 votes for any parameter exceeded the number of active voters,
11140 but would let it pass otherwise. Partially fixes bug 5786; bugfix
11142 - When computing weight parameters, behave more robustly in the
11143 presence of a bad bwweightscale value. Previously, the authorities
11144 would crash if they agreed on a sufficiently broken weight_scale
11145 value; now, they use a reasonable default and carry on. Fixes the
11146 rest of bug 5786; bugfix on 0.2.2.17-alpha.
11147 - If authorities are unable to get a v2 consensus document from other
11148 directory authorities, they no longer fall back to fetching
11149 them from regular directory caches. Fixes bug 5635; bugfix on
11150 0.2.2.26-beta, where routers stopped downloading v2 consensus
11151 documents entirely.
11153 o Major bugfixes (relays):
11154 - Fix a bug handling SENDME cells on nonexistent streams that could
11155 result in bizarre window values. Report and patch contributed
11156 pseudonymously. Fixes part of bug 6271. This bug was introduced
11157 before the first Tor release, in svn commit r152.
11158 - Don't update the AccountingSoftLimitHitAt state file entry whenever
11159 tor gets started. This prevents a wrong average bandwidth
11160 estimate, which would cause relays to always start a new accounting
11161 interval at the earliest possible moment. Fixes bug 2003; bugfix
11162 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
11163 immensely in tracking this bug down.
11164 - Fix a possible crash bug when checking for deactivated circuits
11165 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
11166 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11167 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
11168 connections. This change should allow busy exit relays to stop
11169 running out of available sockets as quickly. Fixes bug 4950;
11170 bugfix on 0.2.2.26-beta.
11172 o Major bugfixes (blocking resistance):
11173 - Bridges no longer include their address in NETINFO cells on outgoing
11174 OR connections, to allow them to blend in better with clients.
11175 Removes another avenue for enumerating bridges. Reported by
11176 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
11177 cells were introduced.
11178 - Warn the user when HTTPProxy, but no other proxy type, is
11179 configured. This can cause surprising behavior: it doesn't send
11180 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
11181 directory traffic only. Resolves ticket 4663.
11183 o Major bugfixes (hidden services):
11184 - Improve hidden service robustness: when an attempt to connect to
11185 a hidden service ends, be willing to refetch its hidden service
11186 descriptors from each of the HSDir relays responsible for them
11187 immediately. Previously, we would not consider refetching the
11188 service's descriptors from each HSDir for 15 minutes after the last
11189 fetch, which was inconvenient if the hidden service was not running
11190 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
11191 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
11192 They used to check that the timestamp was within 30 minutes
11193 of their system clock, so they could cap the size of their
11194 replay-detection cache, but that approach unnecessarily refused
11195 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
11196 the v3 intro-point protocol (the first one which sent a timestamp
11197 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
11198 - When one of a hidden service's introduction points appears to be
11199 unreachable, stop trying it. Previously, we would keep trying
11200 to build circuits to the introduction point until we lost the
11201 descriptor, usually because the user gave up and restarted Tor.
11202 Fixes part of bug 3825.
11204 o Changes to default torrc file:
11205 - Stop listing "socksport 9050" in torrc.sample. We open a socks
11206 port on 9050 by default anyway, so this should not change anything
11208 - Stop mentioning the deprecated *ListenAddress options in
11209 torrc.sample. Fixes bug 5438.
11210 - Document unit of bandwidth-related options in sample torrc.
11212 - Fix broken URLs in the sample torrc file, and tell readers about
11213 the OutboundBindAddress, ExitPolicyRejectPrivate, and
11214 PublishServerDescriptor options. Addresses bug 4652.
11216 o Minor features (directory authorities):
11217 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
11218 change when the authority is deciding whether to accept a newly
11219 uploaded descriptor. Implements ticket 6423.
11220 - Directory authorities are now a little more lenient at accepting
11221 older router descriptors, or newer router descriptors that don't
11222 make big changes. This should help ameliorate past and future
11223 issues where routers think they have uploaded valid descriptors,
11224 but the authorities don't think so. Fix for ticket 2479.
11225 - Authority operators can now vote for all relays in a given
11226 set of countries to be BadDir/BadExit/Invalid/Rejected.
11227 - Provide two consensus parameters (FastFlagMinThreshold and
11228 FastFlagMaxThreshold) to control the range of allowable bandwidths
11229 for the Fast directory flag. These allow authorities to run
11230 experiments on appropriate requirements for being a "Fast" node.
11231 The AuthDirFastGuarantee config value still applies. Implements
11234 o Minor features (bridges / bridge authorities):
11235 - Make bridge SSL certificates a bit more stealthy by using random
11236 serial numbers, in the same fashion as OpenSSL when generating
11237 self-signed certificates. Implements ticket 4584.
11238 - Tag a bridge's descriptor as "never to be sent unencrypted".
11239 This shouldn't matter, since bridges don't open non-anonymous
11240 connections to the bridge authority and don't allow unencrypted
11241 directory connections from clients, but we might as well make
11242 sure. Closes bug 5139.
11243 - The Bridge Authority now writes statistics on how many bridge
11244 descriptors it gave out in total, and how many unique descriptors
11245 it gave out. It also lists how often the most and least commonly
11246 fetched descriptors were given out, as well as the median and
11247 25th/75th percentile. Implements tickets 4200 and 4294.
11249 o Minor features (IPv6):
11250 - Make the code that clients use to detect an address change be
11251 IPv6-aware, so that it won't fill clients' logs with error
11252 messages when trying to get the IPv4 address of an IPv6
11253 connection. Implements ticket 5537.
11254 - Relays now understand an IPv6 address when they get one from a
11255 directory server. Resolves ticket 4875.
11257 o Minor features (hidden services):
11258 - Expire old or over-used hidden service introduction points.
11259 Required by fix for bug 3460.
11260 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
11261 public key replay-detection cache from 60 minutes to 5 minutes. This
11262 replay-detection cache is now used only to detect multiple
11263 INTRODUCE2 cells specifying the same rendezvous point, so we can
11264 avoid launching multiple simultaneous attempts to connect to it.
11265 - When a hidden service's introduction point times out, consider
11266 trying it again during the next attempt to connect to the
11267 HS. Previously, we would not try it again unless a newly fetched
11268 descriptor contained it. Required by fixes for bugs 1297 and 3825.
11270 o Minor features (relays):
11271 - Relays now include a reason for regenerating their descriptors
11272 in an HTTP header when uploading to the authorities. This will
11273 make it easier to debug descriptor-upload issues in the future.
11274 - Turn on directory request statistics by default and include them in
11275 extra-info descriptors. Don't break if we have no GeoIP database.
11276 - Replace files in stats/ rather than appending to them. Now that we
11277 include statistics in extra-info descriptors, it makes no sense to
11278 keep old statistics forever. Implements ticket 2930.
11279 - Relays that set "ConnDirectionStatistics 1" write statistics on the
11280 bidirectional use of connections to disk every 24 hours.
11281 - Add a GeoIP file digest to the extra-info descriptor. Implements
11284 o Minor features (new config options):
11285 - New config option "DynamicDHGroups" (disabled by default) provides
11286 each bridge with a unique prime DH modulus to be used during
11287 SSL handshakes. This option attempts to help against censors
11288 who might use the Apache DH modulus as a static identifier for
11289 bridges. Addresses ticket 4548.
11290 - New config option "DisableDebuggerAttachment" (on by default)
11291 to prevent basic debugging attachment attempts by other processes.
11292 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
11293 - Ordinarily, Tor does not count traffic from private addresses (like
11294 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
11295 There is now a new option, CountPrivateBandwidth, to disable this
11296 behavior. Patch from Daniel Cagara.
11298 o Minor features (different behavior for old config options):
11299 - Allow MapAddress directives to specify matches against super-domains,
11300 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
11301 Implements issue 933.
11302 - Don't disable the DirPort when we cannot exceed our AccountingMax
11303 limit during this interval because the effective bandwidthrate is
11304 low enough. This is useful in a situation where AccountMax is only
11305 used as an additional safeguard or to provide statistics.
11306 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
11307 implements ticket 3439.
11308 - When configuring a large set of nodes in EntryNodes, and there are
11309 enough of them listed as Guard so that we don't need to consider
11310 the non-guard entries, prefer the ones listed with the Guard flag.
11311 - If you set the NumCPUs option to 0, Tor will now try to detect how
11312 many CPUs you have. This is the new default behavior.
11313 - The NodeFamily option -- which let you declare that you want to
11314 consider nodes to be part of a family whether they list themselves
11315 that way or not -- now allows IP address ranges and country codes.
11317 o Minor features (new command-line config behavior):
11318 - Slightly change behavior of "list" options (that is, config
11319 options that can appear more than once) when they appear both in
11320 torrc and on the command line. Previously, the command-line options
11321 would be appended to the ones from torrc. Now, the command-line
11322 options override the torrc options entirely. This new behavior
11323 allows the user to override list options (like exit policies and
11324 ports to listen on) from the command line, rather than simply
11325 appending to the list.
11326 - You can get the old (appending) command-line behavior for "list"
11327 options by prefixing the option name with a "+".
11328 - You can remove all the values for a "list" option from the command
11329 line without adding any new ones by prefixing the option name
11332 o Minor features (controller, new events):
11333 - Extend the control protocol to report flags that control a circuit's
11334 path selection in CIRC events and in replies to 'GETINFO
11335 circuit-status'. Implements part of ticket 2411.
11336 - Extend the control protocol to report the hidden service address
11337 and current state of a hidden-service-related circuit in CIRC
11338 events and in replies to 'GETINFO circuit-status'. Implements part
11340 - Include the creation time of a circuit in CIRC and CIRC2
11341 control-port events and the list produced by the 'GETINFO
11342 circuit-status' control-port command.
11343 - Add a new CONF_CHANGED event so that controllers can be notified
11344 of any configuration changes made by other controllers, or by the
11345 user. Implements ticket 1692.
11346 - Add a new SIGNAL event to the controller interface so that
11347 controllers can be notified when Tor handles a signal. Resolves
11348 issue 1955. Patch by John Brooks.
11350 o Minor features (controller, new getinfo options):
11351 - Expose our view of whether we have gone dormant to the controller,
11352 via a new "GETINFO dormant" value. Torbutton and other controllers
11353 can use this to avoid doing periodic requests through Tor while
11354 it's dormant (bug 4718). Resolves ticket 5954.
11355 - Add a new GETINFO option to get total bytes read and written. Patch
11356 from pipe, revised by atagar. Resolves ticket 2345.
11357 - Implement new GETINFO controller fields to provide information about
11358 the Tor process's pid, euid, username, and resource limits.
11360 o Minor features (controller, other):
11361 - Allow controllers to request an event notification whenever a
11362 circuit is cannibalized or its purpose is changed. Implements
11363 part of ticket 3457.
11364 - Use absolute path names when reporting the torrc filename in the
11365 control protocol, so a controller can more easily find the torrc
11366 file. Resolves bug 1101.
11367 - When reporting the path to the cookie file to the controller,
11368 give an absolute path. Resolves ticket 4881.
11370 o Minor features (log messages):
11371 - Add more information to a log statement that might help track down
11372 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
11373 non-IP address" messages (or any Bug messages, for that matter!),
11374 please let us know about it.
11375 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
11376 EntryNodes will have no effect. Resolves issue 2571.
11377 - Try to make the introductory warning message that Tor prints on
11378 startup more useful for actually finding help and information.
11379 Resolves ticket 2474.
11380 - When the system call to create a listener socket fails, log the
11381 error message explaining why. This may help diagnose bug 4027.
11383 o Minor features (other):
11384 - When we fail to initialize Libevent, retry with IOCP disabled so we
11385 don't need to turn on multi-threading support in Libevent, which in
11386 turn requires a working socketpair(). This is a workaround for bug
11387 4457, which affects Libevent versions from 2.0.1-alpha through
11389 - When starting as root and then changing our UID via the User
11390 control option, and we have a ControlSocket configured, make sure
11391 that the ControlSocket is owned by the same account that Tor will
11392 run under. Implements ticket 3421; fix by Jérémy Bobbio.
11393 - Accept attempts to include a password authenticator in the
11394 handshake, as supported by SOCKS5. This handles SOCKS clients that
11395 don't know how to omit a password when authenticating. Resolves
11397 - Check for and recover from inconsistency in the microdescriptor
11398 cache. This will make it harder for us to accidentally free a
11399 microdescriptor without removing it from the appropriate data
11400 structures. Fixes issue 3135; issue noted by "wanoskarnet".
11401 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
11403 o Minor bugfixes (code security):
11404 - Prevent a null-pointer dereference when receiving a data cell
11405 for a nonexistent stream when the circuit in question has an
11406 empty deliver window. We don't believe this is triggerable,
11407 since we don't currently allow deliver windows to become empty,
11408 but the logic is tricky enough that it's better to make the code
11409 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
11410 - Fix a (harmless) integer overflow in cell statistics reported by
11411 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
11412 - Fix our implementation of crypto_random_hostname() so it can't
11413 overflow on ridiculously large inputs. (No Tor version has ever
11414 provided this kind of bad inputs, but let's be correct in depth.)
11415 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
11416 - Add a (probably redundant) memory clear between iterations of
11417 the router status voting loop, to prevent future coding errors
11418 where data might leak between iterations of the loop. Resolves
11421 o Minor bugfixes (wrapper functions):
11422 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
11423 utility function used in the control-port code). This shouldn't
11424 ever happen unless Tor is completely out of memory, but if it did
11425 happen and Tor somehow recovered from it, Tor could have sent a log
11426 message to a control port in the middle of a reply to a controller
11427 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
11428 - Fix some (not actually triggerable) buffer size checks in usage of
11429 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
11431 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
11432 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
11433 - Enforce correct return behavior of tor_vsscanf() when the '%%'
11434 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
11435 - Make our replacement implementation of strtok_r() compatible with
11436 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
11437 bugfix on 0.2.2.1-alpha.
11438 - Find more places in the code that should have been testing for
11439 invalid sockets using the SOCKET_OK macro. Required for a fix
11440 for bug 4533. Bugfix on 0.2.2.28-beta.
11442 o Minor bugfixes (code correctness):
11443 - Check return value of fputs() when writing authority certificate
11444 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
11445 - When building Tor on Windows with -DUNICODE (not default), ensure
11446 that error messages, filenames, and DNS server names are always
11447 NUL-terminated when we convert them to a single-byte encoding.
11448 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
11449 - Fix a memory leak when trying to launch a DNS request when the
11450 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
11452 - Correct file sizes when reading binary files on Cygwin, to avoid
11453 a bug where Tor would fail to read its state file. Fixes bug 6844;
11454 bugfix on 0.1.2.7-alpha.
11455 - Make sure to set *socket_error in all error cases in
11456 connection_connect(), so it can't produce a warning about
11457 errno being zero from errno_to_orconn_end_reason(). Bugfix on
11458 0.2.1.1-alpha; resolves ticket 6028.
11459 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
11460 bug 4532; found by "troll_un".
11462 o Minor bugfixes (clients):
11463 - Allow one-hop directory-fetching circuits the full "circuit build
11464 timeout" period, rather than just half of it, before failing them
11465 and marking the relay down. This fix should help reduce cases where
11466 clients declare relays (or worse, bridges) unreachable because
11467 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
11468 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
11470 - Ensure we don't cannibalize circuits that are longer than three hops
11471 already, so we don't end up making circuits with 5 or more
11472 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
11473 0.1.0.1-rc which introduced cannibalization.
11475 o Minor bugfixes (relays):
11476 - Don't publish a new relay descriptor when we reload our onion key,
11477 unless the onion key has actually changed. Fixes bug 3263 and
11478 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
11479 - When relays refuse a "create" cell because their queue of pending
11480 create cells is too big (typically because their cpu can't keep up
11481 with the arrival rate), send back reason "resource limit" rather
11482 than reason "internal", so network measurement scripts can get a
11483 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
11484 - Exit nodes don't need to fetch certificates for authorities that
11485 they don't recognize; only directory authorities, bridges,
11486 and caches need to do that. Fixes part of bug 2297; bugfix on
11489 o Minor bugfixes (directory authority / mirrors):
11490 - Avoid O(n^2) performance characteristics when parsing a large
11491 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
11492 - Authorities no longer include any router in their microdescriptor
11493 consensuses for which they couldn't generate or agree on a
11494 microdescriptor. Fixes the second piece of bug 6404; fix on
11496 - When checking for requested signatures on the latest consensus
11497 before serving it to a client, make sure to check the right
11498 consensus flavor. Bugfix on 0.2.2.6-alpha.
11499 - Fix an edge case where TestingTorNetwork is set but the authorities
11500 and relays all have an uptime of zero, so the private Tor network
11501 could briefly lack support for hidden services. Fixes bug 3886;
11502 bugfix on 0.2.2.18-alpha.
11503 - Directory caches no longer refuse to clean out descriptors because
11504 of missing v2 networkstatus documents, unless they're configured
11505 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
11506 0.2.2.26-beta. Patch by Daniel Bryg.
11507 - Don't serve or accept v2 hidden service descriptors over a relay's
11508 DirPort. It's never correct to do so, and disabling it might
11509 make it more annoying to exploit any bugs that turn up in the
11510 descriptor-parsing code. Fixes bug 7149.
11512 o Minor bugfixes (hidden services, client-side):
11513 - Assert that hidden-service-related operations are not performed
11514 using single-hop circuits. Previously, Tor would assert that
11515 client-side streams are not attached to single-hop circuits,
11516 but not that other sensitive operations on the client and service
11517 side are not performed using single-hop circuits. Fixes bug 3332;
11519 - Avoid undefined behavior when parsing the list of supported
11520 rendezvous/introduction protocols in a hidden service descriptor.
11521 Previously, Tor would have confused (as-yet-unused) protocol version
11522 numbers greater than 32 with lower ones on many platforms. Fixes
11523 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11524 - Don't close hidden service client circuits which have almost
11525 finished connecting to their destination when they reach
11526 the normal circuit-build timeout. Previously, we would close
11527 introduction circuits which are waiting for an acknowledgement
11528 from the introduction point, and rendezvous circuits which have
11529 been specified in an INTRODUCE1 cell sent to a hidden service,
11530 after the normal CBT. Now, we mark them as 'timed out', and launch
11531 another rendezvous attempt in parallel. This behavior change can
11532 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
11533 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
11535 o Minor bugfixes (hidden services, service-side):
11536 - Don't close hidden-service-side rendezvous circuits when they
11537 reach the normal circuit-build timeout. This behavior change can
11538 be disabled using the new
11539 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
11540 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
11541 - Don't launch more than 10 service-side introduction-point circuits
11542 for a hidden service in five minutes. Previously, we would consider
11543 launching more introduction-point circuits if at least one second
11544 had passed without any introduction-point circuits failing. Fixes
11545 bug 4607; bugfix on 0.0.7pre1.
11547 o Minor bugfixes (config option behavior):
11548 - If the user tries to set MyFamily on a bridge, refuse to
11549 do so, and warn about the security implications. Fixes bug 4657;
11550 bugfix on 0.2.0.3-alpha.
11551 - The "--quiet" and "--hush" options now apply not only to Tor's
11552 behavior before logs are configured, but also to Tor's behavior in
11553 the absence of configured logs. Fixes bug 3550; bugfix on
11555 - Change the AllowDotExit rules so they should actually work.
11556 We now enforce AllowDotExit only immediately after receiving an
11557 address via SOCKS or DNSPort: other sources are free to provide
11558 .exit addresses after the resolution occurs. Fixes bug 3940;
11559 bugfix on 0.2.2.1-alpha.
11560 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
11561 don't depend on the consensus parameters or compute adaptive
11562 timeouts when it is disabled. Fixes bug 5049; bugfix on
11564 - After we pick a directory mirror, we would refuse to use it if
11565 it's in our ExcludeExitNodes list, resulting in mysterious failures
11566 to bootstrap for people who just wanted to avoid exiting from
11567 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
11568 - When told to add a bridge with the same digest as a preexisting
11569 bridge but a different addr:port, change the addr:port as
11570 requested. Previously we would not notice the change. Fixes half
11571 of bug 5603; fix on 0.2.2.26-beta.
11573 o Minor bugfixes (controller):
11574 - Allow manual 'authenticate' commands to the controller interface
11575 from netcat (nc) as well as telnet. We were rejecting them because
11576 they didn't come with the expected whitespace at the end of the
11577 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
11578 - Report a real bootstrap problem to the controller on router
11579 identity mismatch. Previously we just said "foo", which probably
11580 made a lot of sense at the time. Fixes bug 4169; bugfix on
11582 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
11583 option is set to 0 (which Vidalia version 0.2.16 now does when
11584 a SAVECONF attempt fails), perform other actions that SIGHUP
11585 usually causes (like reopening the logs). Fixes bug 5095; bugfix
11587 - Correctly handle checking the permissions on the parent
11588 directory of a control socket in the root directory. Bug found
11589 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
11591 - End AUTHCHALLENGE error messages (in the control protocol) with
11592 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
11594 o Minor bugfixes (network reading/writing):
11595 - Disable writing on marked-for-close connections when they are
11596 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
11597 bug 5263; bugfix on 0.0.2pre13, where we first added a special
11598 case for flushing marked connections.
11599 - Make sure that there are no unhandled pending TLS errors before
11600 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
11601 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
11602 Bugfix on 0.1.0.5-rc; fixes bug 4528.
11603 - Detect SSL handshake even when the initial attempt to write the
11604 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
11605 - If the client fails to set a reasonable set of ciphersuites
11606 during its v2 handshake renegotiation, allow the renegotiation to
11607 continue nevertheless (i.e. send all the required certificates).
11608 Fixes bug 4591; bugfix on 0.2.0.20-rc.
11610 o Minor bugfixes (other):
11611 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
11612 resource exhaustion, so that clients can adjust their load to
11613 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
11614 started using END_STREAM_REASON_RESOURCELIMIT.
11615 - Don't check for whether the address we're using for outbound
11616 connections has changed until after the outbound connection has
11617 completed. On Windows, getsockname() doesn't succeed until the
11618 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
11619 - Don't hold a Windows file handle open for every file mapping;
11620 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
11622 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
11623 bugfix on 0.2.1.10-alpha.
11624 - If we fail to write a microdescriptor to the disk cache, do not
11625 continue replacing the old microdescriptor file. Fixes bug 2954;
11626 bugfix on 0.2.2.6-alpha.
11628 o Minor bugfixes (log messages, path selection):
11629 - Downgrade "set buildtimeout to low value" messages to "info"
11630 severity; they were never an actual problem, there was never
11631 anything reasonable to do about them, and they tended to spam logs
11632 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
11633 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
11634 more information to it, so that we can track it down in case it
11635 returns again. Mitigates bug 5235.
11636 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
11637 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
11638 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
11639 - Issue a log message if a guard completes less than 40% of your
11640 circuits. Threshold is configurable by torrc option
11641 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
11642 additional, off-by-default code to disable guards which fail too
11643 many circuits. Addresses ticket 5458.
11645 o Minor bugfixes (log messages, client):
11646 - Downgrade "Got a certificate, but we already have it" log messages
11647 from warning to info, except when we're a dirauth. Fixes bug 5238;
11648 bugfix on 0.2.1.7-alpha.
11649 - Fix the log message describing how we work around discovering
11650 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
11651 4837; bugfix on 0.2.2.9-alpha.
11652 - When logging about a disallowed .exit name, do not also call it
11653 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
11654 - Fix a log message suggesting that people contact a non-existent
11655 email address. Fixes bug 3448.
11656 - Rephrase the log message emitted if the TestSocks check is
11657 successful. Patch from Fabian Keil; fixes bug 4094.
11658 - Log (at debug level) whenever a circuit's purpose is changed.
11659 - Log SSL state transitions at log level DEBUG, log domain
11660 HANDSHAKE. This can be useful for debugging censorship events.
11661 Implements ticket 3264.
11662 - We now log which torrc file we're using on startup. Implements
11664 - Rate-limit log messages when asked to connect anonymously to
11665 a private address. When these hit, they tended to hit fast and
11666 often. Also, don't bother trying to connect to addresses that we
11667 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
11668 reply makes us think we have been lied to, even when the address the
11669 client tried to connect to was "localhost." Resolves ticket 2822.
11671 o Minor bugfixes (log messages, non-client):
11672 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
11673 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
11674 - Don't log that we have "decided to publish new relay descriptor"
11675 unless we are actually publishing a descriptor. Fixes bug 3942;
11676 bugfix on 0.2.2.28-beta.
11677 - Log which authority we're missing votes from when we go to fetch
11678 them from the other auths.
11679 - Replace "Sending publish request" log messages with "Launching
11680 upload", so that they no longer confusingly imply that we're
11681 sending something to a directory we might not even be connected
11682 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
11683 - Warn when Tor is configured to use accounting in a way that can
11684 link a hidden service to some other hidden service or public
11685 address. Resolves ticket 6490.
11686 - Fix a minor formatting issue in one of tor-gencert's error messages.
11690 - Update to the latest version of the tinytest unit testing framework.
11691 This includes a couple of bugfixes that can be relevant for
11692 running forked unit tests on Windows, and removes all reserved
11694 - Avoid a false positive in the util/threads unit test by increasing
11695 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
11696 - Make it possible to set the TestingTorNetwork configuration
11697 option using AlternateDirAuthority and AlternateBridgeAuthority
11698 as an alternative to setting DirServer. Addresses ticket 6377.
11699 - Add a unit test for the environment_variable_names_equal() function.
11700 - A wide variety of new unit tests by Esteban Manchado Velázquez.
11701 - Numerous new unit tests for functions in util.c and address.c by
11703 - The long-disabled benchmark tests are now split into their own
11704 ./src/test/bench binary.
11705 - The benchmark tests can now use more accurate timers than
11706 gettimeofday() when such timers are available.
11707 - Use tt_assert(), not tor_assert(), for checking for test failures.
11708 This makes the unit tests more able to go on in the event that
11711 o Build improvements:
11712 - Use the dead_strip option when building Tor on OS X. This reduces
11713 binary size by almost 19% when linking openssl and libevent
11714 statically, which we do for Tor Browser Bundle.
11715 - Provide a better error message about possible OSX Asciidoc failure
11716 reasons. Fixes bug 6436.
11717 - Detect attempts to build Tor on (as yet hypothetical) versions
11718 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
11719 fix for bug 4533. Bugfix on 0.2.2.28-beta.
11720 - On Windows, we now define the _WIN32_WINNT macros only if they
11721 are not already defined. This lets the person building Tor decide,
11722 if they want, to require a later version of Windows.
11723 - Our autogen.sh script now uses autoreconf to launch autoconf,
11724 automake, and so on. This is more robust against some of the failure
11725 modes associated with running the autotools pieces on their own.
11726 - Running "make version" now displays the version of Tor that
11727 we're about to build. Idea from katmagic; resolves issue 4400.
11728 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
11729 on 0.2.2.4-alpha; fixes bug 3427.
11730 - New --enable-static-tor configure option for building Tor as
11731 statically as possible. Idea, general hackery and thoughts from
11732 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
11734 - Limited, experimental support for building with nmake and MSVC.
11736 o Build requirements:
11737 - Building Tor with bufferevent support now requires Libevent
11738 2.0.13-stable or later. Previous versions of Libevent had bugs in
11739 SSL-related bufferevents and related issues that would make Tor
11740 work badly with bufferevents. Requiring 2.0.13-stable also allows
11741 Tor with bufferevents to take advantage of Libevent APIs
11742 introduced after 2.0.8-rc.
11743 - Our build system requires automake 1.6 or later to create the
11744 Makefile.in files. Previously, you could have used 1.4.
11745 This only affects developers and people building Tor from git;
11746 people who build Tor from the source distribution without changing
11747 the Makefile.am files should be fine.
11748 - Detect when we try to build on a platform that doesn't define
11749 AF_UNSPEC to 0. We don't work there, so refuse to compile.
11751 o Build fixes (compile/link):
11752 - Format more doubles with %f, not %lf. Patch from grarpamp to make
11753 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
11755 - When building with --enable-static-tor on OpenBSD, do not
11756 erroneously attempt to link -lrt. Fixes bug 5103.
11757 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
11758 that IPv6 stuff will compile on MSVC, and compilation issues
11759 will be easier to track down. Fixes bug 5861.
11760 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
11761 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
11762 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
11763 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
11765 o Build fixes (other):
11766 - Use the _WIN32 macro throughout our code to detect Windows.
11767 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
11769 - Properly handle the case where the build-tree is not the same
11770 as the source tree when generating src/common/common_sha1.i,
11771 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
11772 bugfix on 0.2.0.1-alpha.
11773 - During configure, search for library containing cos function as
11774 libm lives in libcore on some platforms (BeOS/Haiku). Linking
11775 against libm was hard-coded before. Fixes the first part of bug
11776 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
11778 - Prevent a false positive from the check-spaces script, by disabling
11779 the "whitespace between function name and (" check for functions
11782 o Packaging (RPM) changes:
11783 - Update our default RPM spec files to work with mock and rpmbuild
11784 on RHEL/Fedora. They have an updated set of dependencies and
11785 conflicts, a fix for an ancient typo when creating the "_tor"
11786 user, and better instructions. Thanks to Ondrej Mikle for the
11787 patch series. Fixes bug 6043.
11788 - On OpenSUSE, create the /var/run/tor directory on startup if it
11789 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
11791 o Code refactoring (safety):
11792 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
11793 10 lines. Also, don't nest them. Doing so in the past has
11794 led to hard-to-debug code. The new style is to use the
11795 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
11796 - Use macros to indicate OpenSSL versions, so we don't need to worry
11797 about accidental hexadecimal bit shifts.
11798 - Use tor_sscanf() in place of scanf() in more places through the
11799 code. This makes us a little more locale-independent, and
11800 should help shut up code-analysis tools that can't tell
11801 a safe sscanf string from a dangerous one.
11802 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
11803 - Use the smartlist_add_asprintf() alias more consistently.
11805 o Code refactoring (consolidate):
11806 - A major revision to our internal node-selecting and listing logic.
11807 Tor already had at least two major ways to look at the question of
11808 "which Tor servers do we know about": a list of router descriptors,
11809 and a list of entries in the current consensus. With
11810 microdescriptors, we're adding a third. Having so many systems
11811 without an abstraction layer over them was hurting the codebase.
11812 Now, we have a new "node_t" abstraction that presents a consistent
11813 interface to a client's view of a Tor node, and holds (nearly) all
11814 of the mutable state formerly in routerinfo_t and routerstatus_t.
11815 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
11816 Libevent's notion of cached time when possible.
11817 - Remove duplicate code for invoking getrlimit() from control.c.
11818 - Use OpenSSL's built-in SSL_state_string_long() instead of our
11819 own homebrewed ssl_state_to_string() replacement. Patch from
11820 Emile Snyder. Fixes bug 4653.
11821 - Change the symmetric cipher interface so that creating and
11822 initializing a stream cipher are no longer separate functions.
11824 o Code refactoring (separate):
11825 - Make a new "entry connection" struct as an internal subtype of "edge
11826 connection", to simplify the code and make exit connections smaller.
11827 - Split connection_about_to_close() into separate functions for each
11829 - Rewrite the listener-selection logic so that parsing which ports
11830 we want to listen on is now separate from binding to the ports
11833 o Code refactoring (name changes):
11834 - Rename a handful of old identifiers, mostly related to crypto
11835 structures and crypto functions. By convention, our "create an
11836 object" functions are called "type_new()", our "free an object"
11837 functions are called "type_free()", and our types indicate that
11838 they are types only with a final "_t". But a handful of older
11839 types and functions broke these rules, with function names like
11840 "type_create" or "subsystem_op_type", or with type names like
11842 - Rename Tor functions that turn strings into addresses, so that
11843 "parse" indicates that no hostname resolution occurs, and
11844 "lookup" indicates that hostname resolution may occur. This
11845 should help prevent mistakes in the future. Fixes bug 3512.
11846 - Use the name "CERTS" consistently to refer to the new cell type;
11847 we were calling it CERT in some places and CERTS in others.
11848 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
11849 invalid value, rather than just -1.
11850 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
11851 can pick them up when the tests aren't disabled. Bugfix on
11852 0.2.2.4-alpha which introduced tinytest.
11854 o Code refactoring (other):
11855 - Defensively refactor rend_mid_rendezvous() so that protocol
11856 violations and length checks happen in the beginning. Fixes
11858 - Remove the pure attribute from all functions that used it
11859 previously. In many cases we assigned it incorrectly, because the
11860 functions might assert or call impure functions, and we don't have
11861 evidence that keeping the pure attribute is worthwhile. Implements
11862 changes suggested in ticket 4421.
11863 - Move the replay-detection cache for the RSA-encrypted parts of
11864 INTRODUCE2 cells to the introduction point data structures.
11865 Previously, we would use one replay-detection cache per hidden
11866 service. Required by fix for bug 3460.
11867 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
11868 no longer link against Libevent: they never used it, but
11869 our library structure used to force them to link it.
11871 o Removed features and files:
11872 - Remove all internal support for unpadded RSA. We never used it, and
11873 it would be a bad idea to start.
11874 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
11876 - Remove some redundant #include directives throughout the code.
11877 Patch from Andrea Gelmini.
11878 - Remove some old code to remember statistics about which descriptors
11879 we've served as a directory mirror. The feature wasn't used and
11880 is outdated now that microdescriptors are around.
11881 - Remove some old code to work around even older versions of Tor that
11882 used forked processes to handle DNS requests. Such versions of Tor
11883 are no longer in use as relays.
11884 - The "torify" script no longer supports the "tsocks" socksifier
11885 tool, since tsocks doesn't support DNS and UDP right for Tor.
11886 Everyone should be using torsocks instead. Fixes bugs 3530 and
11887 5180. Based on a patch by "ugh".
11888 - Remove the torrc.bridge file: we don't use it for anything, and
11889 it had become badly desynchronized from torrc.sample. Resolves
11893 - Begin a doc/state-contents.txt file to explain the contents of
11894 the Tor state file. Fixes bug 2987.
11895 - Clarify the documentation for the Alternate*Authority options.
11897 - Document the --defaults-torrc option, and the new semantics for
11898 overriding, extending, and clearing lists of options. Closes
11900 - Add missing man page documentation for consensus and microdesc
11901 files. Resolves ticket 6732.
11902 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
11904 o Documentation fixes:
11905 - Improve the manual's documentation for the NT Service command-line
11906 options. Addresses ticket 3964.
11907 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
11908 - Document the changes to the ORPort and DirPort options, and the
11909 fact that {OR/Dir}ListenAddress is now unnecessary (and
11910 therefore deprecated). Resolves ticket 5597.
11911 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
11912 - Clarify that hidden services are TCP only. Fixes bug 6024.
11915 Changes in version 0.2.2.39 - 2012-09-11
11916 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
11920 - Fix an assertion failure in tor_timegm() that could be triggered
11921 by a badly formatted directory object. Bug found by fuzzing with
11922 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11923 - Do not crash when comparing an address with port value 0 to an
11924 address policy. This bug could have been used to cause a remote
11925 assertion failure by or against directory authorities, or to
11926 allow some applications to crash clients. Fixes bug 6690; bugfix
11930 Changes in version 0.2.2.38 - 2012-08-12
11931 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
11932 attack that could in theory leak path information.
11935 - Avoid an uninitialized memory read when reading a vote or consensus
11936 document that has an unrecognized flavor name. This read could
11937 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
11938 - Try to leak less information about what relays a client is
11939 choosing to a side-channel attacker. Previously, a Tor client would
11940 stop iterating through the list of available relays as soon as it
11941 had chosen one, thus finishing a little earlier when it picked
11942 a router earlier in the list. If an attacker can recover this
11943 timing information (nontrivial but not proven to be impossible),
11944 they could learn some coarse-grained information about which relays
11945 a client was picking (middle nodes in particular are likelier to
11946 be affected than exits). The timing attack might be mitigated by
11947 other factors (see bug 6537 for some discussion), but it's best
11948 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
11951 Changes in version 0.2.2.37 - 2012-06-06
11952 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
11953 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11957 - Work around a bug in OpenSSL that broke renegotiation with TLS
11958 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11959 the v2 Tor connection protocol when both sides were using OpenSSL
11960 1.0.1 would fail. Resolves ticket 6033.
11961 - When waiting for a client to renegotiate, don't allow it to add
11962 any bytes to the input buffer. This fixes a potential DoS issue.
11963 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11964 - Fix an edge case where if we fetch or publish a hidden service
11965 descriptor, we might build a 4-hop circuit and then use that circuit
11966 for exiting afterwards -- even if the new last hop doesn't obey our
11967 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11970 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11971 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11974 - Tell GCC and Clang to check for any errors in format strings passed
11975 to the tor_v*(print|scan)f functions.
11978 Changes in version 0.2.2.36 - 2012-05-24
11979 Tor 0.2.2.36 updates the addresses for two of the eight directory
11980 authorities, fixes some potential anonymity and security issues,
11981 and fixes several crash bugs.
11983 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
11984 known flaws, and nobody should be using them. You should upgrade. If
11985 you're using a Linux or BSD and its packages are obsolete, stop using
11986 those packages and upgrade anyway.
11988 o Directory authority changes:
11989 - Change IP address for maatuska (v3 directory authority).
11990 - Change IP address for ides (v3 directory authority), and rename
11994 - When building or running with any version of OpenSSL earlier
11995 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11996 versions have a bug (CVE-2011-4576) in which their block cipher
11997 padding includes uninitialized data, potentially leaking sensitive
11998 information to any peer with whom they make a SSLv3 connection. Tor
11999 does not use SSL v3 by default, but a hostile client or server
12000 could force an SSLv3 connection in order to gain information that
12001 they shouldn't have been able to get. The best solution here is to
12002 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
12003 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
12004 to make sure that the bug can't happen.
12005 - Never use a bridge or a controller-supplied node as an exit, even
12006 if its exit policy allows it. Found by wanoskarnet. Fixes bug
12007 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
12008 and 0.2.0.3-alpha (for bridge-purpose descriptors).
12009 - Only build circuits if we have a sufficient threshold of the total
12010 descriptors that are marked in the consensus with the "Exit"
12011 flag. This mitigates an attack proposed by wanoskarnet, in which
12012 all of a client's bridges collude to restrict the exit nodes that
12013 the client knows about. Fixes bug 5343.
12014 - Provide controllers with a safer way to implement the cookie
12015 authentication mechanism. With the old method, if another locally
12016 running program could convince a controller that it was the Tor
12017 process, then that program could trick the controller into telling
12018 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
12019 authentication method uses a challenge-response approach to prevent
12020 this attack. Fixes bug 5185; implements proposal 193.
12023 - Avoid logging uninitialized data when unable to decode a hidden
12024 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12025 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12026 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12028 - Fix builds when the path to sed, openssl, or sha1sum contains
12029 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
12031 - Correct our replacements for the timeradd() and timersub() functions
12032 on platforms that lack them (for example, Windows). The timersub()
12033 function is used when expiring circuits, while timeradd() is
12034 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
12035 bugfix on 0.2.2.24-alpha.
12036 - Fix the SOCKET_OK test that we use to tell when socket
12037 creation fails so that it works on Win64. Fixes part of bug 4533;
12038 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
12041 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
12042 Fixes bug 5346; bugfix on 0.0.8pre3.
12043 - Make our number-parsing functions always treat too-large values
12044 as an error, even when those values exceed the width of the
12045 underlying type. Previously, if the caller provided these
12046 functions with minima or maxima set to the extreme values of the
12047 underlying integer type, these functions would return those
12048 values on overflow rather than treating overflow as an error.
12049 Fixes part of bug 5786; bugfix on 0.0.9.
12050 - Older Linux kernels erroneously respond to strange nmap behavior
12051 by having accept() return successfully with a zero-length
12052 socket. When this happens, just close the connection. Previously,
12053 we would try harder to learn the remote address: but there was
12054 no such remote address to learn, and our method for trying to
12055 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
12056 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
12057 - Correct parsing of certain date types in parse_http_time().
12058 Without this patch, If-Modified-Since would behave
12059 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
12060 Esteban Manchado Velázques.
12061 - Change the BridgePassword feature (part of the "bridge community"
12062 design, which is not yet implemented) to use a time-independent
12063 comparison. The old behavior might have allowed an adversary
12064 to use timing to guess the BridgePassword value. Fixes bug 5543;
12065 bugfix on 0.2.0.14-alpha.
12066 - Detect and reject certain misformed escape sequences in
12067 configuration values. Previously, these values would cause us
12068 to crash if received in a torrc file or over an authenticated
12069 control port. Bug found by Esteban Manchado Velázquez, and
12070 independently by Robert Connolly from Matta Consulting who further
12071 noted that it allows a post-authentication heap overflow. Patch
12072 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
12073 bugfix on 0.2.0.16-alpha.
12074 - Fix a compile warning when using the --enable-openbsd-malloc
12075 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
12076 - During configure, detect when we're building with clang version
12077 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
12078 CFLAGS. clang doesn't support them yet.
12079 - When sending an HTTP/1.1 proxy request, include a Host header.
12080 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12081 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
12082 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
12083 - If we hit the error case where routerlist_insert() replaces an
12084 existing (old) server descriptor, make sure to remove that
12085 server descriptor from the old_routers list. Fix related to bug
12086 1776. Bugfix on 0.2.2.18-alpha.
12088 o Minor bugfixes (documentation and log messages):
12089 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
12090 Fixes bug 4856; bugfix on Tor 0.0.6.
12091 - Update "ClientOnly" man page entry to explain that there isn't
12092 really any point to messing with it. Resolves ticket 5005.
12093 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
12094 directory authority option (introduced in Tor 0.2.2.34).
12095 - Downgrade the "We're missing a certificate" message from notice
12096 to info: people kept mistaking it for a real problem, whereas it
12097 is seldom the problem even when we are failing to bootstrap. Fixes
12098 bug 5067; bugfix on 0.2.0.10-alpha.
12099 - Correctly spell "connect" in a log message on failure to create a
12100 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
12101 - Clarify the behavior of MaxCircuitDirtiness with hidden service
12102 circuits. Fixes issue 5259.
12105 - Directory authorities now reject versions of Tor older than
12106 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
12107 inclusive. These versions accounted for only a small fraction of
12108 the Tor network, and have numerous known security issues. Resolves
12110 - Update to the May 1 2012 Maxmind GeoLite Country database.
12113 - When sending or relaying a RELAY_EARLY cell, we used to convert
12114 it to a RELAY cell if the connection was using the v1 link
12115 protocol. This was a workaround for older versions of Tor, which
12116 didn't handle RELAY_EARLY cells properly. Now that all supported
12117 versions can handle RELAY_EARLY cells, and now that we're enforcing
12118 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12119 remove this workaround. Addresses bug 4786.
12122 Changes in version 0.2.2.35 - 2011-12-16
12123 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
12124 buffers code. Absolutely everybody should upgrade.
12126 The bug relied on an incorrect calculation when making data continuous
12127 in one of our IO buffers, if the first chunk of the buffer was
12128 misaligned by just the wrong amount. The miscalculation would allow an
12129 attacker to overflow a piece of heap-allocated memory. To mount this
12130 attack, the attacker would need to either open a SOCKS connection to
12131 Tor's SocksPort (usually restricted to localhost), or target a Tor
12132 instance configured to make its connections through a SOCKS proxy
12133 (which Tor does not do by default).
12135 Good security practice requires that all heap-overflow bugs should be
12136 presumed to be exploitable until proven otherwise, so we are treating
12137 this as a potential code execution attack. Please upgrade immediately!
12138 This bug does not affect bufferevents-based builds of Tor. Special
12139 thanks to "Vektor" for reporting this issue to us!
12141 Tor 0.2.2.35 also fixes several bugs in previous versions, including
12142 crash bugs for unusual configurations, and a long-term bug that
12143 would prevent Tor from starting on Windows machines with draconian
12146 With this release, we remind everyone that 0.2.0.x has reached its
12147 formal end-of-life. Those Tor versions have many known flaws, and
12148 nobody should be using them. You should upgrade -- ideally to the
12149 0.2.2.x series. If you're using a Linux or BSD and its packages are
12150 obsolete, stop using those packages and upgrade anyway.
12152 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
12153 longer receive support after some time in early 2012.
12156 - Fix a heap overflow bug that could occur when trying to pull
12157 data into the first chunk of a buffer, when that chunk had
12158 already had some data drained from it. Fixes CVE-2011-2778;
12159 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12160 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
12161 that it doesn't attempt to allocate a socketpair. This could cause
12162 some problems on Windows systems with overzealous firewalls. Fix for
12163 bug 4457; workaround for Libevent versions 2.0.1-alpha through
12165 - If we mark an OR connection for close based on a cell we process,
12166 don't process any further cells on it. We already avoid further
12167 reads on marked-for-close connections, but now we also discard the
12168 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
12169 which was the first version where we might mark a connection for
12170 close based on processing a cell on it.
12171 - Correctly sanity-check that we don't underflow on a memory
12172 allocation (and then assert) for hidden service introduction
12173 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12174 bugfix on 0.2.1.5-alpha.
12175 - Fix a memory leak when we check whether a hidden service
12176 descriptor has any usable introduction points left. Fixes bug
12177 4424. Bugfix on 0.2.2.25-alpha.
12178 - Don't crash when we're running as a relay and don't have a GeoIP
12179 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
12180 we've had in the 0.2.3.x branch already.
12181 - When running as a client, do not print a misleading (and plain
12182 wrong) log message that we're collecting "directory request"
12183 statistics: clients don't collect statistics. Also don't create a
12184 useless (because empty) stats file in the stats/ directory. Fixes
12185 bug 4353; bugfix on 0.2.2.34.
12188 - Detect failure to initialize Libevent. This fix provides better
12189 detection for future instances of bug 4457.
12190 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
12191 function. This was eating up hideously large amounts of time on some
12192 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
12193 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12194 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12196 - Don't warn about unused log_mutex in log.c when building with
12197 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
12198 0.1.0.6-rc which introduced --disable-threads.
12199 - When configuring, starting, or stopping an NT service, stop
12200 immediately after the service configuration attempt has succeeded
12201 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
12202 - When sending a NETINFO cell, include the original address
12203 received for the other side, not its canonical address. Found
12204 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
12205 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
12206 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
12207 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
12208 occurred when a client tried to fetch a descriptor for a bridge
12209 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
12210 - Backport fixes for a pair of compilation warnings on Windows.
12211 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
12212 - If we had ever tried to call tor_addr_to_str on an address of
12213 unknown type, we would have done a strdup on an uninitialized
12214 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12215 Reported by "troll_un".
12216 - Correctly detect and handle transient lookup failures from
12217 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
12218 Reported by "troll_un".
12219 - Fix null-pointer access that could occur if TLS allocation failed.
12220 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12221 - Use tor_socket_t type for listener argument to accept(). Fixes bug
12222 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
12225 - Add two new config options for directory authorities:
12226 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
12227 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
12228 that is always sufficient to satisfy the bandwidth requirement for
12229 the Guard flag. Now it will be easier for researchers to simulate
12230 Tor networks with different values. Resolves ticket 4484.
12231 - When Tor ignores a hidden service specified in its configuration,
12232 include the hidden service's directory in the warning message.
12233 Previously, we would only tell the user that some hidden service
12234 was ignored. Bugfix on 0.0.6; fixes bug 4426.
12235 - Update to the December 6 2011 Maxmind GeoLite Country database.
12237 o Packaging changes:
12238 - Make it easier to automate expert package builds on Windows,
12239 by removing an absolute path from makensis.exe command.
12242 Changes in version 0.2.1.32 - 2011-12-16
12243 Tor 0.2.1.32 backports important security and privacy fixes for
12244 oldstable. This release is intended only for package maintainers and
12245 others who cannot use the 0.2.2 stable series. All others should be
12246 using Tor 0.2.2.x or newer.
12248 The Tor 0.2.1.x series will reach formal end-of-life some time in
12249 early 2012; we will stop releasing patches for it then.
12251 o Major bugfixes (also included in 0.2.2.x):
12252 - Correctly sanity-check that we don't underflow on a memory
12253 allocation (and then assert) for hidden service introduction
12254 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12255 bugfix on 0.2.1.5-alpha.
12256 - Fix a heap overflow bug that could occur when trying to pull
12257 data into the first chunk of a buffer, when that chunk had
12258 already had some data drained from it. Fixes CVE-2011-2778;
12259 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12262 - Update to the December 6 2011 Maxmind GeoLite Country database.
12265 Changes in version 0.2.2.34 - 2011-10-26
12266 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
12267 can deanonymize Tor users. Everybody should upgrade.
12269 The attack relies on four components: 1) Clients reuse their TLS cert
12270 when talking to different relays, so relays can recognize a user by
12271 the identity key in her cert. 2) An attacker who knows the client's
12272 identity key can probe each guard relay to see if that identity key
12273 is connected to that guard relay right now. 3) A variety of active
12274 attacks in the literature (starting from "Low-Cost Traffic Analysis
12275 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
12276 discover the guard relays that a Tor user visiting the website is using.
12277 4) Clients typically pick three guards at random, so the set of guards
12278 for a given user could well be a unique fingerprint for her. This
12279 release fixes components #1 and #2, which is enough to block the attack;
12280 the other two remain as open research problems. Special thanks to
12281 "frosty_un" for reporting the issue to us!
12283 Clients should upgrade so they are no longer recognizable by the TLS
12284 certs they present. Relays should upgrade so they no longer allow a
12285 remote attacker to probe them to test whether unpatched clients are
12286 currently connected to them.
12288 This release also fixes several vulnerabilities that allow an attacker
12289 to enumerate bridge relays. Some bridge enumeration attacks still
12290 remain; see for example proposal 188.
12292 o Privacy/anonymity fixes (clients):
12293 - Clients and bridges no longer send TLS certificate chains on
12294 outgoing OR connections. Previously, each client or bridge would
12295 use the same cert chain for all outgoing OR connections until
12296 its IP address changes, which allowed any relay that the client
12297 or bridge contacted to determine which entry guards it is using.
12298 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12299 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12300 no longer considers that connection as suitable for satisfying a
12301 circuit EXTEND request. Now relays can protect clients from the
12302 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12303 - Directory authorities no longer assign the Guard flag to relays
12304 that haven't upgraded to the above "refuse EXTEND requests
12305 to client connections" fix. Now directory authorities can
12306 protect clients from the CVE-2011-2768 issue even if neither
12307 the clients nor the relays have upgraded yet. There's a new
12308 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
12309 to let us transition smoothly, else tomorrow there would be no
12312 o Privacy/anonymity fixes (bridge enumeration):
12313 - Bridge relays now do their directory fetches inside Tor TLS
12314 connections, like all the other clients do, rather than connecting
12315 directly to the DirPort like public relays do. Removes another
12316 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12317 - Bridges relays now build circuits for themselves in a more similar
12318 way to how clients build them. Removes another avenue for
12319 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
12320 when bridges were introduced.
12321 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12322 that they initiated. Relays could distinguish incoming bridge
12323 connections from client connections, creating another avenue for
12324 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12325 Found by "frosty_un".
12328 - Fix a crash bug when changing node restrictions while a DNS lookup
12329 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
12331 - Don't launch a useless circuit after failing to use one of a
12332 hidden service's introduction points. Previously, we would
12333 launch a new introduction circuit, but not set the hidden service
12334 which that circuit was intended to connect to, so it would never
12335 actually be used. A different piece of code would then create a
12336 new introduction circuit correctly. Bug reported by katmagic and
12337 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
12340 - Change an integer overflow check in the OpenBSD_Malloc code so
12341 that GCC is less likely to eliminate it as impossible. Patch
12342 from Mansour Moufid. Fixes bug 4059.
12343 - When a hidden service turns an extra service-side introduction
12344 circuit into a general-purpose circuit, free the rend_data and
12345 intro_key fields first, so we won't leak memory if the circuit
12346 is cannibalized for use as another service-side introduction
12347 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
12348 - Bridges now skip DNS self-tests, to act a little more stealthily.
12349 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
12350 bridges. Patch by "warms0x".
12351 - Fix internal bug-checking logic that was supposed to catch
12352 failures in digest generation so that it will fail more robustly
12353 if we ask for a nonexistent algorithm. Found by Coverity Scan.
12354 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
12355 - Report any failure in init_keys() calls launched because our
12356 IP address has changed. Spotted by Coverity Scan. Bugfix on
12357 0.1.1.4-alpha; fixes CID 484.
12359 o Minor bugfixes (log messages and documentation):
12360 - Remove a confusing dollar sign from the example fingerprint in the
12361 man page, and also make the example fingerprint a valid one. Fixes
12362 bug 4309; bugfix on 0.2.1.3-alpha.
12363 - The next version of Windows will be called Windows 8, and it has
12364 a major version of 6, minor version of 2. Correctly identify that
12365 version instead of calling it "Very recent version". Resolves
12366 ticket 4153; reported by funkstar.
12367 - Downgrade log messages about circuit timeout calibration from
12368 "notice" to "info": they don't require or suggest any human
12369 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
12370 bugfix on 0.2.2.14-alpha.
12373 - Turn on directory request statistics by default and include them in
12374 extra-info descriptors. Don't break if we have no GeoIP database.
12375 Backported from 0.2.3.1-alpha; implements ticket 3951.
12376 - Update to the October 4 2011 Maxmind GeoLite Country database.
12379 Changes in version 0.2.1.31 - 2011-10-26
12380 Tor 0.2.1.31 backports important security and privacy fixes for
12381 oldstable. This release is intended only for package maintainers and
12382 others who cannot use the 0.2.2 stable series. All others should be
12383 using Tor 0.2.2.x or newer.
12385 o Security fixes (also included in 0.2.2.x):
12386 - Replace all potentially sensitive memory comparison operations
12387 with versions whose runtime does not depend on the data being
12388 compared. This will help resist a class of attacks where an
12389 adversary can use variations in timing information to learn
12390 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12391 implementation by Robert Ransom based partially on code by DJB.)
12392 - Fix an assert in parsing router descriptors containing IPv6
12393 addresses. This one took down the directory authorities when
12394 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12396 o Privacy/anonymity fixes (also included in 0.2.2.x):
12397 - Clients and bridges no longer send TLS certificate chains on
12398 outgoing OR connections. Previously, each client or bridge would
12399 use the same cert chain for all outgoing OR connections until
12400 its IP address changes, which allowed any relay that the client
12401 or bridge contacted to determine which entry guards it is using.
12402 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12403 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12404 no longer considers that connection as suitable for satisfying a
12405 circuit EXTEND request. Now relays can protect clients from the
12406 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12407 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12408 that they initiated. Relays could distinguish incoming bridge
12409 connections from client connections, creating another avenue for
12410 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12411 Found by "frosty_un".
12412 - When receiving a hidden service descriptor, check that it is for
12413 the hidden service we wanted. Previously, Tor would store any
12414 hidden service descriptors that a directory gave it, whether it
12415 wanted them or not. This wouldn't have let an attacker impersonate
12416 a hidden service, but it did let directories pre-seed a client
12417 with descriptors that it didn't want. Bugfix on 0.0.6.
12418 - Avoid linkability based on cached hidden service descriptors: forget
12419 all hidden service descriptors cached as a client when processing a
12420 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12421 - Make the bridge directory authority refuse to answer directory
12422 requests for "all" descriptors. It used to include bridge
12423 descriptors in its answer, which was a major information leak.
12424 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12425 - Don't attach new streams to old rendezvous circuits after SIGNAL
12426 NEWNYM. Previously, we would keep using an existing rendezvous
12427 circuit if it remained open (i.e. if it were kept open by a
12428 long-lived stream, or if a new stream were attached to it before
12429 Tor could notice that it was old and no longer in use). Bugfix on
12430 0.1.1.15-rc; fixes bug 3375.
12432 o Minor bugfixes (also included in 0.2.2.x):
12433 - When we restart our relay, we might get a successful connection
12434 from the outside before we've started our reachability tests,
12435 triggering a warning: "ORPort found reachable, but I have no
12436 routerinfo yet. Failing to inform controller of success." This
12437 bug was harmless unless Tor is running under a controller
12438 like Vidalia, in which case the controller would never get a
12439 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12441 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
12442 enabled. Fixes bug 1526.
12443 - Remove undocumented option "-F" from tor-resolve: it hasn't done
12444 anything since 0.2.1.16-rc.
12445 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12446 None of the cases where we did this before were wrong, but by making
12447 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12448 - Fix a rare crash bug that could occur when a client was configured
12449 with a large number of bridges. Fixes bug 2629; bugfix on
12450 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12451 - Correct the warning displayed when a rendezvous descriptor exceeds
12452 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12454 - Fix an uncommon assertion failure when running with DNSPort under
12455 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12456 - When warning about missing zlib development packages during compile,
12457 give the correct package names. Bugfix on 0.2.0.1-alpha.
12458 - Require that introduction point keys and onion keys have public
12459 exponent 65537. Bugfix on 0.2.0.10-alpha.
12460 - Do not crash when our configuration file becomes unreadable, for
12461 example due to a permissions change, between when we start up
12462 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12464 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12466 - Always NUL-terminate the sun_path field of a sockaddr_un before
12467 passing it to the kernel. (Not a security issue: kernels are
12468 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12469 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12470 - Don't stack-allocate the list of supplementary GIDs when we're
12471 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12472 could take up to 256K, which is way too much stack. Found by
12473 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12475 o Minor bugfixes (only in 0.2.1.x):
12476 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
12477 rely on them. Bugfix on 0.2.1.30.
12478 - Use git revisions instead of svn revisions when generating our
12479 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
12481 o Minor features (also included in 0.2.2.x):
12482 - Adjust the expiration time on our SSL session certificates to
12483 better match SSL certs seen in the wild. Resolves ticket 4014.
12484 - Allow nameservers with IPv6 address. Resolves bug 2574.
12485 - Update to the October 4 2011 Maxmind GeoLite Country database.
12488 Changes in version 0.2.2.33 - 2011-09-13
12489 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
12490 TLS handshake that makes relays and bridges that run this new version
12491 reachable from Iran again.
12494 - Avoid an assertion failure when reloading a configuration with
12495 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
12496 3923; bugfix on 0.2.2.25-alpha.
12498 o Minor features (security):
12499 - Check for replays of the public-key encrypted portion of an
12500 INTRODUCE1 cell, in addition to the current check for replays of
12501 the g^x value. This prevents a possible class of active attacks
12502 by an attacker who controls both an introduction point and a
12503 rendezvous point, and who uses the malleability of AES-CTR to
12504 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
12505 that these attacks are infeasible (requiring the attacker to send
12506 on the order of zettabytes of altered cells in a short interval),
12507 but we'd rather block them off in case there are any classes of
12508 this attack that we missed. Reported by Willem Pinckaers.
12511 - Adjust the expiration time on our SSL session certificates to
12512 better match SSL certs seen in the wild. Resolves ticket 4014.
12513 - Change the default required uptime for a relay to be accepted as
12514 a HSDir (hidden service directory) from 24 hours to 25 hours.
12515 Improves on 0.2.0.10-alpha; resolves ticket 2649.
12516 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
12517 authorities to abstain from voting on assignment of the HSDir
12518 consensus flag. Related to bug 2649.
12519 - Update to the September 6 2011 Maxmind GeoLite Country database.
12521 o Minor bugfixes (documentation and log messages):
12522 - Correct the man page to explain that HashedControlPassword and
12523 CookieAuthentication can both be set, in which case either method
12524 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
12525 when we decided to allow these config options to both be set. Issue
12526 raised by bug 3898.
12527 - Demote the 'replay detected' log message emitted when a hidden
12528 service receives the same Diffie-Hellman public key in two different
12529 INTRODUCE2 cells to info level. A normal Tor client can cause that
12530 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
12531 fixes part of bug 2442.
12532 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
12533 level. There is nothing that a hidden service's operator can do
12534 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
12536 - Clarify a log message specifying the characters permitted in
12537 HiddenServiceAuthorizeClient client names. Previously, the log
12538 message said that "[A-Za-z0-9+-_]" were permitted; that could have
12539 given the impression that every ASCII character between "+" and "_"
12540 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
12543 - Provide a substitute implementation of lround() for MSVC, which
12544 apparently lacks it. Patch from Gisle Vanem.
12545 - Clean up some code issues that prevented Tor from building on older
12546 BSDs. Fixes bug 3894; reported by "grarpamp".
12547 - Search for a platform-specific version of "ar" when cross-compiling.
12548 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
12551 Changes in version 0.2.2.32 - 2011-08-27
12552 The Tor 0.2.2 release series is dedicated to the memory of Andreas
12553 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
12554 a founder of the PETS community, a leader in our field, a mentor,
12555 and a friend. He left us with these words: "I had the possibility
12556 to contribute to this world that is not as it should be. I hope I
12557 could help in some areas to make the world a better place, and that
12558 I could also encourage other people to be engaged in improving the
12559 world. Please, stay engaged. This world needs you, your love, your
12560 initiative -- now I cannot be part of that anymore."
12562 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
12563 ready. More than two years in the making, this release features improved
12564 client performance and hidden service reliability, better compatibility
12565 for Android, correct behavior for bridges that listen on more than
12566 one address, more extensible and flexible directory object handling,
12567 better reporting of network statistics, improved code security, and
12568 many many other features and bugfixes.
12570 o Major features (client performance):
12571 - When choosing which cells to relay first, relays now favor circuits
12572 that have been quiet recently, to provide lower latency for
12573 low-volume circuits. By default, relays enable or disable this
12574 feature based on a setting in the consensus. They can override
12575 this default by using the new "CircuitPriorityHalflife" config
12576 option. Design and code by Ian Goldberg, Can Tang, and Chris
12578 - Directory authorities now compute consensus weightings that instruct
12579 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
12580 and no flag. Clients use these weightings to distribute network load
12581 more evenly across these different relay types. The weightings are
12582 in the consensus so we can change them globally in the future. Extra
12583 thanks to "outofwords" for finding some nasty security bugs in
12584 the first implementation of this feature.
12586 o Major features (client performance, circuit build timeout):
12587 - Tor now tracks how long it takes to build client-side circuits
12588 over time, and adapts its timeout to local network performance.
12589 Since a circuit that takes a long time to build will also provide
12590 bad performance, we get significant latency improvements by
12591 discarding the slowest 20% of circuits. Specifically, Tor creates
12592 circuits more aggressively than usual until it has enough data
12593 points for a good timeout estimate. Implements proposal 151.
12594 - Circuit build timeout constants can be controlled by consensus
12595 parameters. We set good defaults for these parameters based on
12596 experimentation on broadband and simulated high-latency links.
12597 - Circuit build time learning can be disabled via consensus parameter
12598 or by the client via a LearnCircuitBuildTimeout config option. We
12599 also automatically disable circuit build time calculation if either
12600 AuthoritativeDirectory is set, or if we fail to write our state
12601 file. Implements ticket 1296.
12603 o Major features (relays use their capacity better):
12604 - Set SO_REUSEADDR socket option on all sockets, not just
12605 listeners. This should help busy exit nodes avoid running out of
12606 useable ports just because all the ports have been used in the
12607 near past. Resolves issue 2850.
12608 - Relays now save observed peak bandwidth throughput rates to their
12609 state file (along with total usage, which was already saved),
12610 so that they can determine their correct estimated bandwidth on
12611 restart. Resolves bug 1863, where Tor relays would reset their
12612 estimated bandwidth to 0 after restarting.
12613 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
12614 should give us approximately 40-50% more Guard-flagged nodes,
12615 improving the anonymity the Tor network can provide and also
12616 decreasing the dropoff in throughput that relays experience when
12617 they first get the Guard flag.
12618 - Directory authorities now take changes in router IP address and
12619 ORPort into account when determining router stability. Previously,
12620 if a router changed its IP or ORPort, the authorities would not
12621 treat it as having any downtime for the purposes of stability
12622 calculation, whereas clients would experience downtime since the
12623 change would take a while to propagate to them. Resolves issue 1035.
12624 - New AccelName and AccelDir options add support for dynamic OpenSSL
12625 hardware crypto acceleration engines.
12627 o Major features (relays control their load better):
12628 - Exit relays now try harder to block exit attempts from unknown
12629 relays, to make it harder for people to use them as one-hop proxies
12630 a la tortunnel. Controlled by the refuseunknownexits consensus
12631 parameter (currently enabled), or you can override it on your
12632 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
12633 based on a variant of proposal 163.
12634 - Add separate per-conn write limiting to go with the per-conn read
12635 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
12636 but never per-conn write limits.
12637 - New consensus params "bwconnrate" and "bwconnburst" to let us
12638 rate-limit client connections as they enter the network. It's
12639 controlled in the consensus so we can turn it on and off for
12640 experiments. It's starting out off. Based on proposal 163.
12642 o Major features (controllers):
12643 - Export GeoIP information on bridge usage to controllers even if we
12644 have not yet been running for 24 hours. Now Vidalia bridge operators
12645 can get more accurate and immediate feedback about their
12646 contributions to the network.
12647 - Add an __OwningControllerProcess configuration option and a
12648 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
12649 that when it exits, Tor will shut down. Implements feature 3049.
12651 o Major features (directory authorities):
12652 - Directory authorities now create, vote on, and serve multiple
12653 parallel formats of directory data as part of their voting process.
12654 Partially implements Proposal 162: "Publish the consensus in
12656 - Directory authorities now agree on and publish small summaries
12657 of router information that clients can use in place of regular
12658 server descriptors. This transition will allow Tor 0.2.3 clients
12659 to use far less bandwidth for downloading information about the
12660 network. Begins the implementation of Proposal 158: "Clients
12661 download consensus + microdescriptors".
12662 - The directory voting system is now extensible to use multiple hash
12663 algorithms for signatures and resource selection. Newer formats
12664 are signed with SHA256, with a possibility for moving to a better
12665 hash algorithm in the future.
12666 - Directory authorities can now vote on arbitrary integer values as
12667 part of the consensus process. This is designed to help set
12668 network-wide parameters. Implements proposal 167.
12670 o Major features and bugfixes (node selection):
12671 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
12672 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
12673 options. Previously, we had been ambiguous in describing what
12674 counted as an "exit" node, and what operations exactly "StrictNodes
12675 0" would permit. This created confusion when people saw nodes built
12676 through unexpected circuits, and made it hard to tell real bugs from
12677 surprises. Now the intended behavior is:
12678 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
12679 a node that delivers user traffic outside the Tor network.
12680 . "Entry", in the context of EntryNodes, means a node used as the
12681 first hop of a multihop circuit. It doesn't include direct
12682 connections to directory servers.
12683 . "ExcludeNodes" applies to all nodes.
12684 . "StrictNodes" changes the behavior of ExcludeNodes only. When
12685 StrictNodes is set, Tor should avoid all nodes listed in
12686 ExcludeNodes, even when it will make user requests fail. When
12687 StrictNodes is *not* set, then Tor should follow ExcludeNodes
12688 whenever it can, except when it must use an excluded node to
12689 perform self-tests, connect to a hidden service, provide a
12690 hidden service, fulfill a .exit request, upload directory
12691 information, or fetch directory information.
12692 Collectively, the changes to implement the behavior fix bug 1090.
12693 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
12694 change during a config reload, mark and discard all our origin
12695 circuits. This fix should address edge cases where we change the
12696 config options and but then choose a circuit that we created before
12698 - Make EntryNodes config option much more aggressive even when
12699 StrictNodes is not set. Before it would prepend your requested
12700 entrynodes to your list of guard nodes, but feel free to use others
12701 after that. Now it chooses only from your EntryNodes if any of
12702 those are available, and only falls back to others if a) they're
12703 all down and b) StrictNodes is not set.
12704 - Now we refresh your entry guards from EntryNodes at each consensus
12705 fetch -- rather than just at startup and then they slowly rot as
12706 the network changes.
12707 - Add support for the country code "{??}" in torrc options like
12708 ExcludeNodes, to indicate all routers of unknown country. Closes
12710 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
12711 a node is listed in both, it's treated as excluded.
12712 - ExcludeNodes now applies to directory nodes -- as a preference if
12713 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
12714 Don't exclude all the directory authorities and set StrictNodes to 1
12715 unless you really want your Tor to break.
12716 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
12717 - ExcludeExitNodes now overrides .exit requests.
12718 - We don't use bridges listed in ExcludeNodes.
12719 - When StrictNodes is 1:
12720 . We now apply ExcludeNodes to hidden service introduction points
12721 and to rendezvous points selected by hidden service users. This
12722 can make your hidden service less reliable: use it with caution!
12723 . If we have used ExcludeNodes on ourself, do not try relay
12724 reachability self-tests.
12725 . If we have excluded all the directory authorities, we will not
12726 even try to upload our descriptor if we're a relay.
12727 . Do not honor .exit requests to an excluded node.
12728 - When the set of permitted nodes changes, we now remove any mappings
12729 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
12731 - We never cannibalize a circuit that had excluded nodes on it, even
12732 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
12733 - Improve log messages related to excluded nodes.
12735 o Major features (misc):
12736 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
12737 to help Tor build correctly for Android phones.
12738 - The options SocksPort, ControlPort, and so on now all accept a
12739 value "auto" that opens a socket on an OS-selected port. A
12740 new ControlPortWriteToFile option tells Tor to write its
12741 actual control port or ports to a chosen file. If the option
12742 ControlPortFileGroupReadable is set, the file is created as
12743 group-readable. Now users can run two Tor clients on the same
12744 system without needing to manually mess with parameters. Resolves
12745 part of ticket 3076.
12746 - Tor now supports tunneling all of its outgoing connections over
12747 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12748 configuration options. Code by Christopher Davis.
12750 o Code security improvements:
12751 - Replace all potentially sensitive memory comparison operations
12752 with versions whose runtime does not depend on the data being
12753 compared. This will help resist a class of attacks where an
12754 adversary can use variations in timing information to learn
12755 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12756 implementation by Robert Ransom based partially on code by DJB.)
12757 - Enable Address Space Layout Randomization (ASLR) and Data Execution
12758 Prevention (DEP) by default on Windows to make it harder for
12759 attackers to exploit vulnerabilities. Patch from John Brooks.
12760 - New "--enable-gcc-hardening" ./configure flag (off by default)
12761 to turn on gcc compile time hardening options. It ensures
12762 that signed ints have defined behavior (-fwrapv), enables
12763 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
12764 with canaries (-fstack-protector-all), turns on ASLR protection if
12765 supported by the kernel (-fPIE, -pie), and adds additional security
12766 related warnings. Verified to work on Mac OS X and Debian Lenny.
12767 - New "--enable-linker-hardening" ./configure flag (off by default)
12768 to turn on ELF specific hardening features (relro, now). This does
12769 not work with Mac OS X or any other non-ELF binary format.
12770 - Always search the Windows system directory for system DLLs, and
12771 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
12772 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
12773 current and future memory pages via mlockall(). On supported
12774 platforms (modern Linux and probably BSD but not Windows or OS X),
12775 this should effectively disable any and all attempts to page out
12776 memory. This option requires that you start your Tor as root --
12777 if you use DisableAllSwap, please consider using the User option
12778 to properly reduce the privileges of your Tor.
12780 o Major bugfixes (crashes):
12781 - Fix crash bug on platforms where gmtime and localtime can return
12782 NULL. Windows 7 users were running into this one. Fixes part of bug
12783 2077. Bugfix on all versions of Tor. Found by boboper.
12784 - Introduce minimum/maximum values that clients will believe
12785 from the consensus. Now we'll have a better chance to avoid crashes
12786 or worse when a consensus param has a weird value.
12787 - Fix a rare crash bug that could occur when a client was configured
12788 with a large number of bridges. Fixes bug 2629; bugfix on
12789 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12790 - Do not crash when our configuration file becomes unreadable, for
12791 example due to a permissions change, between when we start up
12792 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12794 - If we're in the pathological case where there's no exit bandwidth
12795 but there is non-exit bandwidth, or no guard bandwidth but there
12796 is non-guard bandwidth, don't crash during path selection. Bugfix
12798 - Fix a crash bug when trying to initialize the evdns module in
12799 Libevent 2. Bugfix on 0.2.1.16-rc.
12801 o Major bugfixes (stability):
12802 - Fix an assert in parsing router descriptors containing IPv6
12803 addresses. This one took down the directory authorities when
12804 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12805 - Fix an uncommon assertion failure when running with DNSPort under
12806 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12807 - Treat an unset $HOME like an empty $HOME rather than triggering an
12808 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
12809 - More gracefully handle corrupt state files, removing asserts
12810 in favor of saving a backup and resetting state.
12811 - Instead of giving an assertion failure on an internal mismatch
12812 on estimated freelist size, just log a BUG warning and try later.
12813 Mitigates but does not fix bug 1125.
12814 - Fix an assert that got triggered when using the TestingTorNetwork
12815 configuration option and then issuing a GETINFO config-text control
12816 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
12817 - If the cached cert file is unparseable, warn but don't exit.
12819 o Privacy fixes (relays/bridges):
12820 - Don't list Windows capabilities in relay descriptors. We never made
12821 use of them, and maybe it's a bad idea to publish them. Bugfix
12823 - If the Nickname configuration option isn't given, Tor would pick a
12824 nickname based on the local hostname as the nickname for a relay.
12825 Because nicknames are not very important in today's Tor and the
12826 "Unnamed" nickname has been implemented, this is now problematic
12827 behavior: It leaks information about the hostname without being
12828 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
12829 introduced the Unnamed nickname. Reported by tagnaq.
12830 - Maintain separate TLS contexts and certificates for incoming and
12831 outgoing connections in bridge relays. Previously we would use the
12832 same TLS contexts and certs for incoming and outgoing connections.
12833 Bugfix on 0.2.0.3-alpha; addresses bug 988.
12834 - Maintain separate identity keys for incoming and outgoing TLS
12835 contexts in bridge relays. Previously we would use the same
12836 identity keys for incoming and outgoing TLS contexts. Bugfix on
12837 0.2.0.3-alpha; addresses the other half of bug 988.
12838 - Make the bridge directory authority refuse to answer directory
12839 requests for "all descriptors". It used to include bridge
12840 descriptors in its answer, which was a major information leak.
12841 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12843 o Privacy fixes (clients):
12844 - When receiving a hidden service descriptor, check that it is for
12845 the hidden service we wanted. Previously, Tor would store any
12846 hidden service descriptors that a directory gave it, whether it
12847 wanted them or not. This wouldn't have let an attacker impersonate
12848 a hidden service, but it did let directories pre-seed a client
12849 with descriptors that it didn't want. Bugfix on 0.0.6.
12850 - Start the process of disabling ".exit" address notation, since it
12851 can be used for a variety of esoteric application-level attacks
12852 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12854 - Reject attempts at the client side to open connections to private
12855 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
12856 a randomly chosen exit node. Attempts to do so are always
12857 ill-defined, generally prevented by exit policies, and usually
12858 in error. This will also help to detect loops in transparent
12859 proxy configurations. You can disable this feature by setting
12860 "ClientRejectInternalAddresses 0" in your torrc.
12861 - Log a notice when we get a new control connection. Now it's easier
12862 for security-conscious users to recognize when a local application
12863 is knocking on their controller door. Suggested by bug 1196.
12865 o Privacy fixes (newnym):
12866 - Avoid linkability based on cached hidden service descriptors: forget
12867 all hidden service descriptors cached as a client when processing a
12868 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12869 - On SIGHUP, do not clear out all TrackHostExits mappings, client
12870 DNS cache entries, and virtual address mappings: that's what
12871 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
12872 - Don't attach new streams to old rendezvous circuits after SIGNAL
12873 NEWNYM. Previously, we would keep using an existing rendezvous
12874 circuit if it remained open (i.e. if it were kept open by a
12875 long-lived stream, or if a new stream were attached to it before
12876 Tor could notice that it was old and no longer in use). Bugfix on
12877 0.1.1.15-rc; fixes bug 3375.
12879 o Major bugfixes (relay bandwidth accounting):
12880 - Fix a bug that could break accounting on 64-bit systems with large
12881 time_t values, making them hibernate for impossibly long intervals.
12882 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
12883 - Fix a bug in bandwidth accounting that could make us use twice
12884 the intended bandwidth when our interval start changes due to
12885 daylight saving time. Now we tolerate skew in stored vs computed
12886 interval starts: if the start of the period changes by no more than
12887 50% of the period's duration, we remember bytes that we transferred
12888 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
12890 o Major bugfixes (bridges):
12891 - Bridges now use "reject *:*" as their default exit policy. Bugfix
12892 on 0.2.0.3-alpha. Fixes bug 1113.
12893 - If you configure your bridge with a known identity fingerprint,
12894 and the bridge authority is unreachable (as it is in at least
12895 one country now), fall back to directly requesting the descriptor
12896 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
12898 - Fix a bug where bridge users who configure the non-canonical
12899 address of a bridge automatically switch to its canonical
12900 address. If a bridge listens at more than one address, it
12901 should be able to advertise those addresses independently and
12902 any non-blocked addresses should continue to work. Bugfix on Tor
12903 0.2.0.3-alpha. Fixes bug 2510.
12904 - If you configure Tor to use bridge A, and then quit and
12905 configure Tor to use bridge B instead (or if you change Tor
12906 to use bridge B via the controller), it would happily continue
12907 to use bridge A if it's still reachable. While this behavior is
12908 a feature if your goal is connectivity, in some scenarios it's a
12909 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
12910 - When the controller configures a new bridge, don't wait 10 to 60
12911 seconds before trying to fetch its descriptor. Bugfix on
12912 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
12914 o Major bugfixes (directory authorities):
12915 - Many relays have been falling out of the consensus lately because
12916 not enough authorities know about their descriptor for them to get
12917 a majority of votes. When we deprecated the v2 directory protocol,
12918 we got rid of the only way that v3 authorities can hear from each
12919 other about other descriptors. Now authorities examine every v3
12920 vote for new descriptors, and fetch them from that authority. Bugfix
12922 - Authorities could be tricked into giving out the Exit flag to relays
12923 that didn't allow exiting to any ports. This bug could screw
12924 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
12925 1238. Bug discovered by Martin Kowalczyk.
12926 - If all authorities restart at once right before a consensus vote,
12927 nobody will vote about "Running", and clients will get a consensus
12928 with no usable relays. Instead, authorities refuse to build a
12929 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
12931 o Major bugfixes (stream-level fairness):
12932 - When receiving a circuit-level SENDME for a blocked circuit, try
12933 to package cells fairly from all the streams that had previously
12934 been blocked on that circuit. Previously, we had started with the
12935 oldest stream, and allowed each stream to potentially exhaust
12936 the circuit's package window. This gave older streams on any
12937 given circuit priority over newer ones. Fixes bug 1937. Detected
12938 originally by Camilo Viecco. This bug was introduced before the
12939 first Tor release, in svn commit r152: it is the new winner of
12940 the longest-lived bug prize.
12941 - Fix a stream fairness bug that would cause newer streams on a given
12942 circuit to get preference when reading bytes from the origin or
12943 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
12944 introduced before the first Tor release, in svn revision r152.
12945 - When the exit relay got a circuit-level sendme cell, it started
12946 reading on the exit streams, even if had 500 cells queued in the
12947 circuit queue already, so the circuit queue just grew and grew in
12948 some cases. We fix this by not re-enabling reading on receipt of a
12949 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
12950 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
12952 - Newly created streams were allowed to read cells onto circuits,
12953 even if the circuit's cell queue was blocked and waiting to drain.
12954 This created potential unfairness, as older streams would be
12955 blocked, but newer streams would gladly fill the queue completely.
12956 We add code to detect this situation and prevent any stream from
12957 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
12960 o Major bugfixes (hidden services):
12961 - Apply circuit timeouts to opened hidden-service-related circuits
12962 based on the correct start time. Previously, we would apply the
12963 circuit build timeout based on time since the circuit's creation;
12964 it was supposed to be applied based on time since the circuit
12965 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
12966 - Improve hidden service robustness: When we find that we have
12967 extended a hidden service's introduction circuit to a relay not
12968 listed as an introduction point in the HS descriptor we currently
12969 have, retry with an introduction point from the current
12970 descriptor. Previously we would just give up. Fixes bugs 1024 and
12971 1930; bugfix on 0.2.0.10-alpha.
12972 - Directory authorities now use data collected from their own
12973 uptime observations when choosing whether to assign the HSDir flag
12974 to relays, instead of trusting the uptime value the relay reports in
12975 its descriptor. This change helps prevent an attack where a small
12976 set of nodes with frequently-changing identity keys can blackhole
12977 a hidden service. (Only authorities need upgrade; others will be
12978 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
12979 - Stop assigning the HSDir flag to relays that disable their
12980 DirPort (and thus will refuse to answer directory requests). This
12981 fix should dramatically improve the reachability of hidden services:
12982 hidden services and hidden service clients pick six HSDir relays
12983 to store and retrieve the hidden service descriptor, and currently
12984 about half of the HSDir relays will refuse to work. Bugfix on
12985 0.2.0.10-alpha; fixes part of bug 1693.
12987 o Major bugfixes (misc):
12988 - Clients now stop trying to use an exit node associated with a given
12989 destination by TrackHostExits if they fail to reach that exit node.
12990 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
12991 - Fix a regression that caused Tor to rebind its ports if it receives
12992 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
12993 - Remove an extra pair of quotation marks around the error
12994 message in control-port STATUS_GENERAL BUG events. Bugfix on
12995 0.1.2.6-alpha; fixes bug 3732.
12997 o Minor features (relays):
12998 - Ensure that no empty [dirreq-](read|write)-history lines are added
12999 to an extrainfo document. Implements ticket 2497.
13000 - When bandwidth accounting is enabled, be more generous with how
13001 much bandwidth we'll use up before entering "soft hibernation".
13002 Previously, we'd refuse new connections and circuits once we'd
13003 used up 95% of our allotment. Now, we use up 95% of our allotment,
13004 AND make sure that we have no more than 500MB (or 3 hours of
13005 expected traffic, whichever is lower) remaining before we enter
13007 - Relays now log the reason for publishing a new relay descriptor,
13008 so we have a better chance of hunting down instances of bug 1810.
13009 Resolves ticket 3252.
13010 - Log a little more clearly about the times at which we're no longer
13011 accepting new connections (e.g. due to hibernating). Resolves
13013 - When AllowSingleHopExits is set, print a warning to explain to the
13014 relay operator why most clients are avoiding her relay.
13015 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
13016 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
13017 clients are already deprecated because of security bugs.
13019 o Minor features (network statistics):
13020 - Directory mirrors that set "DirReqStatistics 1" write statistics
13021 about directory requests to disk every 24 hours. As compared to the
13022 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
13023 improvements: 1) stats are written to disk exactly every 24 hours;
13024 2) estimated shares of v2 and v3 requests are determined as mean
13025 values, not at the end of a measurement period; 3) unresolved
13026 requests are listed with country code '??'; 4) directories also
13027 measure download times.
13028 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
13029 number of exit streams and transferred bytes per port to disk every
13031 - Relays that set "CellStatistics 1" write statistics on how long
13032 cells spend in their circuit queues to disk every 24 hours.
13033 - Entry nodes that set "EntryStatistics 1" write statistics on the
13034 rough number and origins of connecting clients to disk every 24
13036 - Relays that write any of the above statistics to disk and set
13037 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
13038 their extra-info documents. Implements proposal 166.
13040 o Minor features (GeoIP and statistics):
13041 - Provide a log message stating which geoip file we're parsing
13042 instead of just stating that we're parsing the geoip file.
13043 Implements ticket 2432.
13044 - Make sure every relay writes a state file at least every 12 hours.
13045 Previously, a relay could go for weeks without writing its state
13046 file, and on a crash could lose its bandwidth history, capacity
13047 estimates, client country statistics, and so on. Addresses bug 3012.
13048 - Relays report the number of bytes spent on answering directory
13049 requests in extra-info descriptors similar to {read,write}-history.
13050 Implements enhancement 1790.
13051 - Report only the top 10 ports in exit-port stats in order not to
13052 exceed the maximum extra-info descriptor length of 50 KB. Implements
13054 - If writing the state file to disk fails, wait up to an hour before
13055 retrying again, rather than trying again each second. Fixes bug
13056 2346; bugfix on Tor 0.1.1.3-alpha.
13057 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
13058 when we switch from being a public relay to a bridge. Otherwise
13059 there will still be clients that see the relay in their consensus,
13060 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
13062 - Update to the August 2 2011 Maxmind GeoLite Country database.
13064 o Minor features (clients):
13065 - When expiring circuits, use microsecond timers rather than
13066 one-second timers. This can avoid an unpleasant situation where a
13067 circuit is launched near the end of one second and expired right
13068 near the beginning of the next, and prevent fluctuations in circuit
13070 - If we've configured EntryNodes and our network goes away and/or all
13071 our entrynodes get marked down, optimistically retry them all when
13072 a new socks application request appears. Fixes bug 1882.
13073 - Always perform router selections using weighted relay bandwidth,
13074 even if we don't need a high capacity circuit at the time. Non-fast
13075 circuits now only differ from fast ones in that they can use relays
13076 not marked with the Fast flag. This "feature" could turn out to
13077 be a horrible bug; we should investigate more before it goes into
13079 - When we run out of directory information such that we can't build
13080 circuits, but then get enough that we can build circuits, log when
13081 we actually construct a circuit, so the user has a better chance of
13082 knowing what's going on. Fixes bug 1362.
13083 - Log SSL state transitions at debug level during handshake, and
13084 include SSL states in error messages. This may help debug future
13085 SSL handshake issues.
13087 o Minor features (directory authorities):
13088 - When a router changes IP address or port, authorities now launch
13089 a new reachability test for it. Implements ticket 1899.
13090 - Directory authorities now reject relays running any versions of
13091 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
13092 known bugs that keep RELAY_EARLY cells from working on rendezvous
13093 circuits. Followup to fix for bug 2081.
13094 - Directory authorities now reject relays running any version of Tor
13095 older than 0.2.0.26-rc. That version is the earliest that fetches
13096 current directory information correctly. Fixes bug 2156.
13097 - Directory authorities now do an immediate reachability check as soon
13098 as they hear about a new relay. This change should slightly reduce
13099 the time between setting up a relay and getting listed as running
13100 in the consensus. It should also improve the time between setting
13101 up a bridge and seeing use by bridge users.
13102 - Directory authorities no longer launch a TLS connection to every
13103 relay as they startup. Now that we have 2k+ descriptors cached,
13104 the resulting network hiccup is becoming a burden. Besides,
13105 authorities already avoid voting about Running for the first half
13106 hour of their uptime.
13107 - Directory authorities now log the source of a rejected POSTed v3
13108 networkstatus vote, so we can track failures better.
13109 - Backport code from 0.2.3.x that allows directory authorities to
13110 clean their microdescriptor caches. Needed to resolve bug 2230.
13112 o Minor features (hidden services):
13113 - Use computed circuit-build timeouts to decide when to launch
13114 parallel introduction circuits for hidden services. (Previously,
13115 we would retry after 15 seconds.)
13116 - Don't allow v0 hidden service authorities to act as clients.
13117 Required by fix for bug 3000.
13118 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
13119 by fix for bug 3000.
13120 - Make hidden services work better in private Tor networks by not
13121 requiring any uptime to join the hidden service descriptor
13122 DHT. Implements ticket 2088.
13123 - Log (at info level) when purging pieces of hidden-service-client
13124 state because of SIGNAL NEWNYM.
13126 o Minor features (controller interface):
13127 - New "GETINFO net/listeners/(type)" controller command to return
13128 a list of addresses and ports that are bound for listeners for a
13129 given connection type. This is useful when the user has configured
13130 "SocksPort auto" and the controller needs to know which port got
13131 chosen. Resolves another part of ticket 3076.
13132 - Have the controller interface give a more useful message than
13133 "Internal Error" in response to failed GETINFO requests.
13134 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
13135 event, to give information on the current rate of circuit timeouts
13136 over our stored history.
13137 - The 'EXTENDCIRCUIT' control port command can now be used with
13138 a circ id of 0 and no path. This feature will cause Tor to build
13139 a new 'fast' general purpose circuit using its own path selection
13141 - Added a BUILDTIMEOUT_SET controller event to describe changes
13142 to the circuit build timeout.
13143 - New controller command "getinfo config-text". It returns the
13144 contents that Tor would write if you send it a SAVECONF command,
13145 so the controller can write the file to disk itself.
13147 o Minor features (controller protocol):
13148 - Add a new ControlSocketsGroupWritable configuration option: when
13149 it is turned on, ControlSockets are group-writeable by the default
13150 group of the current user. Patch by Jérémy Bobbio; implements
13152 - Tor now refuses to create a ControlSocket in a directory that is
13153 world-readable (or group-readable if ControlSocketsGroupWritable
13154 is 0). This is necessary because some operating systems do not
13155 enforce permissions on an AF_UNIX sockets. Permissions on the
13156 directory holding the socket, however, seems to work everywhere.
13157 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
13158 not. This would lead to a cookie that is still not group readable.
13159 Closes bug 1843. Suggested by katmagic.
13160 - Future-proof the controller protocol a bit by ignoring keyword
13161 arguments we do not recognize.
13163 o Minor features (more useful logging):
13164 - Revise most log messages that refer to nodes by nickname to
13165 instead use the "$key=nickname at address" format. This should be
13166 more useful, especially since nicknames are less and less likely
13167 to be unique. Resolves ticket 3045.
13168 - When an HTTPS proxy reports "403 Forbidden", we now explain
13169 what it means rather than calling it an unexpected status code.
13170 Closes bug 2503. Patch from Michael Yakubovich.
13171 - Rate-limit a warning about failures to download v2 networkstatus
13172 documents. Resolves part of bug 1352.
13173 - Rate-limit the "your application is giving Tor only an IP address"
13174 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
13175 - Rate-limit "Failed to hand off onionskin" warnings.
13176 - When logging a rate-limited warning, we now mention how many messages
13177 got suppressed since the last warning.
13178 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
13179 2 no signature, 4 required" messages about consensus signatures
13180 easier to read, and make sure they get logged at the same severity
13181 as the messages explaining which keys are which. Fixes bug 1290.
13182 - Don't warn when we have a consensus that we can't verify because
13183 of missing certificates, unless those certificates are ones
13184 that we have been trying and failing to download. Fixes bug 1145.
13186 o Minor features (log domains):
13187 - Add documentation for configuring logging at different severities in
13188 different log domains. We've had this feature since 0.2.1.1-alpha,
13189 but for some reason it never made it into the manpage. Fixes
13191 - Make it simpler to specify "All log domains except for A and B".
13192 Previously you needed to say "[*,~A,~B]". Now you can just say
13194 - Add a "LogMessageDomains 1" option to include the domains of log
13195 messages along with the messages. Without this, there's no way
13196 to use log domains without reading the source or doing a lot
13198 - Add a new "Handshake" log domain for activities that happen
13199 during the TLS handshake.
13201 o Minor features (build process):
13202 - Make compilation with clang possible when using
13203 "--enable-gcc-warnings" by removing two warning options that clang
13204 hasn't implemented yet and by fixing a few warnings. Resolves
13206 - Detect platforms that brokenly use a signed size_t, and refuse to
13207 build there. Found and analyzed by doorss and rransom.
13208 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
13210 - Add support for statically linking zlib by specifying
13211 "--enable-static-zlib", to go with our support for statically
13212 linking openssl and libevent. Resolves bug 1358.
13213 - Instead of adding the svn revision to the Tor version string, report
13214 the git commit (when we're building from a git checkout).
13215 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
13217 - New --digests command-line switch to output the digests of the
13218 source files Tor was built with.
13219 - Generate our manpage and HTML documentation using Asciidoc. This
13220 change should make it easier to maintain the documentation, and
13221 produce nicer HTML. The build process fails if asciidoc cannot
13222 be found and building with asciidoc isn't disabled (via the
13223 "--disable-asciidoc" argument to ./configure. Skipping the manpage
13224 speeds up the build considerably.
13226 o Minor features (options / torrc):
13227 - Warn when the same option is provided more than once in a torrc
13228 file, on the command line, or in a single SETCONF statement, and
13229 the option is one that only accepts a single line. Closes bug 1384.
13230 - Warn when the user configures two HiddenServiceDir lines that point
13231 to the same directory. Bugfix on 0.0.6 (the version introducing
13232 HiddenServiceDir); fixes bug 3289.
13233 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
13234 do individual connection-level rate limiting of clients. The torrc
13235 config options with the same names trump the consensus params, if
13236 both are present. Replaces the old "bwconnrate" and "bwconnburst"
13237 consensus params which were broken from 0.2.2.7-alpha through
13238 0.2.2.14-alpha. Closes bug 1947.
13239 - New config option "WarnUnsafeSocks 0" disables the warning that
13240 occurs whenever Tor receives a socks handshake using a version of
13241 the socks protocol that can only provide an IP address (rather
13242 than a hostname). Setups that do DNS locally over Tor are fine,
13243 and we shouldn't spam the logs in that case.
13244 - New config option "CircuitStreamTimeout" to override our internal
13245 timeout schedule for how many seconds until we detach a stream from
13246 a circuit and try a new circuit. If your network is particularly
13247 slow, you might want to set this to a number like 60.
13248 - New options for SafeLogging to allow scrubbing only log messages
13249 generated while acting as a relay. Specify "SafeLogging relay" if
13250 you want to ensure that only messages known to originate from
13251 client use of the Tor process will be logged unsafely.
13252 - Time and memory units in the configuration file can now be set to
13253 fractional units. For example, "2.5 GB" is now a valid value for
13255 - Support line continuations in the torrc config file. If a line
13256 ends with a single backslash character, the newline is ignored, and
13257 the configuration value is treated as continuing on the next line.
13260 o Minor features (unit tests):
13261 - Revise our unit tests to use the "tinytest" framework, so we
13262 can run tests in their own processes, have smarter setup/teardown
13263 code, and so on. The unit test code has moved to its own
13264 subdirectory, and has been split into multiple modules.
13265 - Add a unit test for cross-platform directory-listing code.
13266 - Add some forgotten return value checks during unit tests. Found
13268 - Use GetTempDir to find the proper temporary directory location on
13269 Windows when generating temporary files for the unit tests. Patch
13272 o Minor features (misc):
13273 - The "torify" script now uses torsocks where available.
13274 - Make Libevent log messages get delivered to controllers later,
13275 and not from inside the Libevent log handler. This prevents unsafe
13276 reentrant Libevent calls while still letting the log messages
13278 - Certain Tor clients (such as those behind check.torproject.org) may
13279 want to fetch the consensus in an extra early manner. To enable this
13280 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
13281 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
13282 as only certain clients who must have this information sooner should
13284 - Expand homedirs passed to tor-checkkey. This should silence a
13285 coverity complaint about passing a user-supplied string into
13286 open() without checking it.
13287 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
13288 used on bridges, and it makes bridge scanning somewhat easier.
13289 - Create the /var/run/tor directory on startup on OpenSUSE if it is
13290 not already created. Patch from Andreas Stieger. Fixes bug 2573.
13292 o Minor bugfixes (relays):
13293 - When a relay decides that its DNS is too broken for it to serve
13294 as an exit server, it advertised itself as a non-exit, but
13295 continued to act as an exit. This could create accidental
13296 partitioning opportunities for users. Instead, if a relay is
13297 going to advertise reject *:* as its exit policy, it should
13298 really act with exit policy "reject *:*". Fixes bug 2366.
13299 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
13300 - Publish a router descriptor even if generating an extra-info
13301 descriptor fails. Previously we would not publish a router
13302 descriptor without an extra-info descriptor; this can cause fast
13303 exit relays collecting exit-port statistics to drop from the
13304 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
13305 - When we're trying to guess whether we know our IP address as
13306 a relay, we would log various ways that we failed to guess
13307 our address, but never log that we ended up guessing it
13308 successfully. Now add a log line to help confused and anxious
13309 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
13310 - For bandwidth accounting, calculate our expected bandwidth rate
13311 based on the time during which we were active and not in
13312 soft-hibernation during the last interval. Previously, we were
13313 also considering the time spent in soft-hibernation. If this
13314 was a long time, we would wind up underestimating our bandwidth
13315 by a lot, and skewing our wakeup time towards the start of the
13316 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
13317 - Demote a confusing TLS warning that relay operators might get when
13318 someone tries to talk to their ORPort. It is not the operator's
13319 fault, nor can they do anything about it. Fixes bug 1364; bugfix
13321 - Change "Application request when we're believed to be offline."
13322 notice to "Application request when we haven't used client
13323 functionality lately.", to clarify that it's not an error. Bugfix
13324 on 0.0.9.3; fixes bug 1222.
13326 o Minor bugfixes (bridges):
13327 - When a client starts or stops using bridges, never use a circuit
13328 that was built before the configuration change. This behavior could
13329 put at risk a user who uses bridges to ensure that her traffic
13330 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
13332 - Do not reset the bridge descriptor download status every time we
13333 re-parse our configuration or get a configuration change. Fixes
13334 bug 3019; bugfix on 0.2.0.3-alpha.
13335 - Users couldn't configure a regular relay to be their bridge. It
13336 didn't work because when Tor fetched the bridge descriptor, it found
13337 that it already had it, and didn't realize that the purpose of the
13338 descriptor had changed. Now we replace routers with a purpose other
13339 than bridge with bridge descriptors when fetching them. Bugfix on
13340 0.1.1.9-alpha. Fixes bug 1776.
13341 - In the special case where you configure a public exit relay as your
13342 bridge, Tor would be willing to use that exit relay as the last
13343 hop in your circuit as well. Now we fail that circuit instead.
13344 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
13346 o Minor bugfixes (clients):
13347 - We now ask the other side of a stream (the client or the exit)
13348 for more data on that stream when the amount of queued data on
13349 that stream dips low enough. Previously, we wouldn't ask the
13350 other side for more data until either it sent us more data (which
13351 it wasn't supposed to do if it had exhausted its window!) or we
13352 had completely flushed all our queued data. This flow control fix
13353 should improve throughput. Fixes bug 2756; bugfix on the earliest
13354 released versions of Tor (svn commit r152).
13355 - When a client finds that an origin circuit has run out of 16-bit
13356 stream IDs, we now mark it as unusable for new streams. Previously,
13357 we would try to close the entire circuit. Bugfix on 0.0.6.
13358 - Make it explicit that we don't cannibalize one-hop circuits. This
13359 happens in the wild, but doesn't turn out to be a problem because
13360 we fortunately don't use those circuits. Many thanks to outofwords
13361 for the initial analysis and to swissknife who confirmed that
13362 two-hop circuits are actually created.
13363 - Resolve an edge case in path weighting that could make us misweight
13364 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
13365 - Make the DNSPort option work with libevent 2.x. Don't alter the
13366 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
13368 o Minor bugfixes (directory authorities):
13369 - Make directory authorities more accurate at recording when
13370 relays that have failed several reachability tests became
13371 unreachable, so we can provide more accuracy at assigning Stable,
13372 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
13373 - Directory authorities are now more robust to hops back in time
13374 when calculating router stability. Previously, if a run of uptime
13375 or downtime appeared to be negative, the calculation could give
13376 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
13378 - Directory authorities will now attempt to download consensuses
13379 if their own efforts to make a live consensus have failed. This
13380 change means authorities that restart will fetch a valid
13381 consensus, and it means authorities that didn't agree with the
13382 current consensus will still fetch and serve it if it has enough
13383 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
13384 - Never vote for a server as "Running" if we have a descriptor for
13385 it claiming to be hibernating, and that descriptor was published
13386 more recently than our last contact with the server. Bugfix on
13387 0.2.0.3-alpha; fixes bug 911.
13388 - Directory authorities no longer change their opinion of, or vote on,
13389 whether a router is Running, unless they have themselves been
13390 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
13393 o Minor bugfixes (hidden services):
13394 - Log malformed requests for rendezvous descriptors as protocol
13395 warnings, not warnings. Also, use a more informative log message
13396 in case someone sees it at log level warning without prior
13397 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
13398 - Accept hidden service descriptors if we think we might be a hidden
13399 service directory, regardless of what our consensus says. This
13400 helps robustness, since clients and hidden services can sometimes
13401 have a more up-to-date view of the network consensus than we do,
13402 and if they think that the directory authorities list us a HSDir,
13403 we might actually be one. Related to bug 2732; bugfix on
13405 - Correct the warning displayed when a rendezvous descriptor exceeds
13406 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
13408 - Clients and hidden services now use HSDir-flagged relays for hidden
13409 service descriptor downloads and uploads even if the relays have no
13410 DirPort set and the client has disabled TunnelDirConns. This will
13411 eventually allow us to give the HSDir flag to relays with no
13412 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
13413 - Only limit the lengths of single HS descriptors, even when multiple
13414 HS descriptors are published to an HSDir relay in a single POST
13415 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
13417 o Minor bugfixes (controllers):
13418 - Allow GETINFO fingerprint to return a fingerprint even when
13419 we have not yet built a router descriptor. Fixes bug 3577;
13420 bugfix on 0.2.0.1-alpha.
13421 - Send a SUCCEEDED stream event to the controller when a reverse
13422 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
13423 discovered by katmagic.
13424 - Remove a trailing asterisk from "exit-policy/default" in the
13425 output of the control port command "GETINFO info/names". Bugfix
13427 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
13428 2917. Bugfix on 0.1.1.1-alpha.
13429 - When we restart our relay, we might get a successful connection
13430 from the outside before we've started our reachability tests,
13431 triggering a warning: "ORPort found reachable, but I have no
13432 routerinfo yet. Failing to inform controller of success." This
13433 bug was harmless unless Tor is running under a controller
13434 like Vidalia, in which case the controller would never get a
13435 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
13437 - When a controller changes TrackHostExits, remove mappings for
13438 hosts that should no longer have their exits tracked. Bugfix on
13440 - When a controller changes VirtualAddrNetwork, remove any mappings
13441 for hosts that were automapped to the old network. Bugfix on
13443 - When a controller changes one of the AutomapHosts* options, remove
13444 any mappings for hosts that should no longer be automapped. Bugfix
13446 - Fix an off-by-one error in calculating some controller command
13447 argument lengths. Fortunately, this mistake is harmless since
13448 the controller code does redundant NUL termination too. Found by
13449 boboper. Bugfix on 0.1.1.1-alpha.
13450 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
13451 would return "551 Internal error" rather than "552 Unrecognized key
13452 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
13453 - Don't spam the controller with events when we have no file
13454 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
13455 for log messages was already solved from bug 748.)
13456 - Emit a GUARD DROPPED controller event for a case we missed.
13457 - Ensure DNS requests launched by "RESOLVE" commands from the
13458 controller respect the __LeaveStreamsUnattached setconf options. The
13459 same goes for requests launched via DNSPort or transparent
13460 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
13462 o Minor bugfixes (config options):
13463 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
13464 Change the limit to 512 characters by removing base64 newlines.
13465 Fixes bug 2752. Fix by Michael Yakubovich.
13466 - Complain if PublishServerDescriptor is given multiple arguments that
13467 include 0 or 1. This configuration will be rejected in the future.
13468 Bugfix on 0.2.0.1-alpha; closes bug 1107.
13469 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
13470 Bugfix on 0.2.0.13-alpha; closes bug 928.
13472 o Minor bugfixes (log subsystem fixes):
13473 - When unable to format an address as a string, report its value
13474 as "???" rather than reusing the last formatted address. Bugfix
13476 - Be more consistent in our treatment of file system paths. "~" should
13477 get expanded to the user's home directory in the Log config option.
13478 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
13479 feature for the -f and --DataDirectory options.
13481 o Minor bugfixes (memory management):
13482 - Don't stack-allocate the list of supplementary GIDs when we're
13483 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13484 could take up to 256K, which is way too much stack. Found by
13485 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13486 - Save a couple bytes in memory allocation every time we escape
13487 certain characters in a string. Patch from Florian Zumbiehl.
13489 o Minor bugfixes (protocol correctness):
13490 - When checking for 1024-bit keys, check for 1024 bits, not 128
13491 bytes. This allows Tor to correctly discard keys of length 1017
13492 through 1023. Bugfix on 0.0.9pre5.
13493 - Require that introduction point keys and onion handshake keys
13494 have a public exponent of 65537. Starts to fix bug 3207; bugfix
13496 - Handle SOCKS messages longer than 128 bytes long correctly, rather
13497 than waiting forever for them to finish. Fixes bug 2330; bugfix
13498 on 0.2.0.16-alpha. Found by doorss.
13499 - Never relay a cell for a circuit we have already destroyed.
13500 Between marking a circuit as closeable and finally closing it,
13501 it may have been possible for a few queued cells to get relayed,
13502 even though they would have been immediately dropped by the next
13503 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
13504 - Never queue a cell for a circuit that's already been marked
13506 - Fix a spec conformance issue: the network-status-version token
13507 must be the first token in a v3 consensus or vote. Discovered by
13508 "parakeep". Bugfix on 0.2.0.3-alpha.
13509 - A networkstatus vote must contain exactly one signature. Spec
13510 conformance issue. Bugfix on 0.2.0.3-alpha.
13511 - When asked about a DNS record type we don't support via a
13512 client DNSPort, reply with NOTIMPL rather than an empty
13513 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
13514 - Make more fields in the controller protocol case-insensitive, since
13515 control-spec.txt said they were.
13517 o Minor bugfixes (log messages):
13518 - Fix a log message that said "bits" while displaying a value in
13519 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
13521 - Downgrade "no current certificates known for authority" message from
13522 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
13523 - Correctly describe errors that occur when generating a TLS object.
13524 Previously we would attribute them to a failure while generating a
13525 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
13527 - Fix an instance where a Tor directory mirror might accidentally
13528 log the IP address of a misbehaving Tor client. Bugfix on
13530 - Stop logging at severity 'warn' when some other Tor client tries
13531 to establish a circuit with us using weak DH keys. It's a protocol
13532 violation, but that doesn't mean ordinary users need to hear about
13533 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
13534 - If your relay can't keep up with the number of incoming create
13535 cells, it would log one warning per failure into your logs. Limit
13536 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
13538 o Minor bugfixes (build fixes):
13539 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13540 - When warning about missing zlib development packages during compile,
13541 give the correct package names. Bugfix on 0.2.0.1-alpha.
13542 - Fix warnings that newer versions of autoconf produce during
13543 ./autogen.sh. These warnings appear to be harmless in our case,
13544 but they were extremely verbose. Fixes bug 2020.
13545 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
13548 o Minor bugfixes (portability):
13549 - Write several files in text mode, on OSes that distinguish text
13550 mode from binary mode (namely, Windows). These files are:
13551 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13552 that collect those statistics; 'client_keys' and 'hostname' for
13553 hidden services that use authentication; and (in the tor-gencert
13554 utility) newly generated identity and signing keys. Previously,
13555 we wouldn't specify text mode or binary mode, leading to an
13556 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13557 the DirRecordUsageByCountry option which would have triggered
13558 the assertion failure was added), although this assertion failure
13559 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13560 - Selectively disable deprecation warnings on OS X because Lion
13561 started deprecating the shipped copy of openssl. Fixes bug 3643.
13562 - Use a wide type to hold sockets when built for 64-bit Windows.
13564 - Fix an issue that prevented static linking of libevent on
13565 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
13566 where we introduced the "--with-static-libevent" configure option.
13567 - Fix a bug with our locking implementation on Windows that couldn't
13568 correctly detect when a file was already locked. Fixes bug 2504,
13569 bugfix on 0.2.1.6-alpha.
13570 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
13572 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
13573 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
13576 o Minor bugfixes (code correctness):
13577 - Always NUL-terminate the sun_path field of a sockaddr_un before
13578 passing it to the kernel. (Not a security issue: kernels are
13579 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13580 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13581 - Make connection_printf_to_buf()'s behavior sane. Its callers
13582 expect it to emit a CRLF iff the format string ends with CRLF;
13583 it actually emitted a CRLF iff (a) the format string ended with
13584 CRLF or (b) the resulting string was over 1023 characters long or
13585 (c) the format string did not end with CRLF *and* the resulting
13586 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
13587 fixes part of bug 3407.
13588 - Make send_control_event_impl()'s behavior sane. Its callers
13589 expect it to always emit a CRLF at the end of the string; it
13590 might have emitted extra control characters as well. Bugfix on
13591 0.1.1.9-alpha; fixes another part of bug 3407.
13592 - Make crypto_rand_int() check the value of its input correctly.
13593 Previously, it accepted values up to UINT_MAX, but could return a
13594 negative number if given a value above INT_MAX+1. Found by George
13595 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
13596 - Fix a potential null-pointer dereference while computing a
13597 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
13599 - If we fail to compute the identity digest of a v3 legacy keypair,
13600 warn, and don't use a buffer-full of junk instead. Bugfix on
13601 0.2.1.1-alpha; fixes bug 3106.
13602 - Resolve an untriggerable issue in smartlist_string_num_isin(),
13603 where if the function had ever in the future been used to check
13604 for the presence of a too-large number, it would have given an
13605 incorrect result. (Fortunately, we only used it for 16-bit
13606 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
13607 - Be more careful about reporting the correct error from a failed
13608 connect() system call. Under some circumstances, it was possible to
13609 look at an incorrect value for errno when sending the end reason.
13610 Bugfix on 0.1.0.1-rc.
13611 - Correctly handle an "impossible" overflow cases in connection byte
13612 counting, where we write or read more than 4GB on an edge connection
13613 in a single second. Bugfix on 0.1.2.8-beta.
13614 - Avoid a double mark-for-free warning when failing to attach a
13615 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
13617 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
13618 found by "cypherpunks". This bug was introduced before the first
13619 Tor release, in svn commit r110.
13620 - Fix a bug in bandwidth history state parsing that could have been
13621 triggered if a future version of Tor ever changed the timing
13622 granularity at which bandwidth history is measured. Bugfix on
13623 Tor 0.1.1.11-alpha.
13624 - Add assertions to check for overflow in arguments to
13625 base32_encode() and base32_decode(); fix a signed-unsigned
13626 comparison there too. These bugs are not actually reachable in Tor,
13627 but it's good to prevent future errors too. Found by doorss.
13628 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
13630 - Set target port in get_interface_address6() correctly. Bugfix
13631 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
13632 - Fix an impossible-to-actually-trigger buffer overflow in relay
13633 descriptor generation. Bugfix on 0.1.0.15.
13634 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
13636 o Minor bugfixes (code improvements):
13637 - After we free an internal connection structure, overwrite it
13638 with a different memory value than we use for overwriting a freed
13639 internal circuit structure. Should help with debugging. Suggested
13641 - If OpenSSL fails to make a duplicate of a private or public key, log
13642 an error message and try to exit cleanly. May help with debugging
13643 if bug 1209 ever remanifests.
13644 - Some options used different conventions for uppercasing of acronyms
13645 when comparing manpage and source. Fix those in favor of the
13646 manpage, as it makes sense to capitalize acronyms.
13647 - Take a first step towards making or.h smaller by splitting out
13648 function definitions for all source files in src/or/. Leave
13649 structures and defines in or.h for now.
13650 - Remove a few dead assignments during router parsing. Found by
13652 - Don't use 1-bit wide signed bit fields. Found by coverity.
13653 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
13654 None of the cases where we did this before were wrong, but by making
13655 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
13656 - The memarea code now uses a sentinel value at the end of each area
13657 to make sure nothing writes beyond the end of an area. This might
13658 help debug some conceivable causes of bug 930.
13659 - Always treat failure to allocate an RSA key as an unrecoverable
13661 - Add some more defensive programming for architectures that can't
13662 handle unaligned integer accesses. We don't know of any actual bugs
13663 right now, but that's the best time to fix them. Fixes bug 1943.
13665 o Minor bugfixes (misc):
13666 - Fix a rare bug in rend_fn unit tests: we would fail a test when
13667 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
13668 on 0.2.0.10-alpha; fixes bug 1808.
13669 - Where available, use Libevent 2.0's periodic timers so that our
13670 once-per-second cleanup code gets called even more closely to
13671 once per second than it would otherwise. Fixes bug 943.
13672 - Ignore OutboundBindAddress when connecting to localhost.
13673 Connections to localhost need to come _from_ localhost, or else
13674 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
13676 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
13678 - If any of the v3 certs we download are unparseable, we should
13679 actually notice the failure so we don't retry indefinitely. Bugfix
13680 on 0.2.0.x; reported by "rotator".
13681 - When Tor fails to parse a descriptor of any kind, dump it to disk.
13682 Might help diagnosing bug 1051.
13683 - Make our 'torify' script more portable; if we have only one of
13684 'torsocks' or 'tsocks' installed, don't complain to the user;
13685 and explain our warning about tsocks better.
13686 - Fix some urls in the exit notice file and make it XHTML1.1 strict
13687 compliant. Based on a patch from Christian Kujau.
13689 o Documentation changes:
13690 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
13691 - Resolve all doxygen warnings except those for missing documentation.
13693 - Add doxygen documentation for more functions, fields, and types.
13694 - Convert the HACKING file to asciidoc, and add a few new sections
13695 to it, explaining how we use Git, how we make changelogs, and
13696 what should go in a patch.
13697 - Document the default socks host and port (127.0.0.1:9050) for
13699 - Removed some unnecessary files from the source distribution. The
13700 AUTHORS file has now been merged into the people page on the
13701 website. The roadmaps and design doc can now be found in the
13702 projects directory in svn.
13704 o Deprecated and removed features (config):
13705 - Remove the torrc.complete file. It hasn't been kept up to date
13706 and users will have better luck checking out the manpage.
13707 - Remove the HSAuthorityRecordStats option that version 0 hidden
13708 service authorities could use to track statistics of overall v0
13709 hidden service usage.
13710 - Remove the obsolete "NoPublish" option; it has been flagged
13711 as obsolete and has produced a warning since 0.1.1.18-rc.
13712 - Caches no longer download and serve v2 networkstatus documents
13713 unless FetchV2Networkstatus flag is set: these documents haven't
13714 haven't been used by clients or relays since 0.2.0.x. Resolves
13717 o Deprecated and removed features (controller):
13718 - The controller no longer accepts the old obsolete "addr-mappings/"
13719 or "unregistered-servers-" GETINFO values.
13720 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
13721 always on; using them is necessary for correct forward-compatible
13724 o Deprecated and removed features (misc):
13725 - Hidden services no longer publish version 0 descriptors, and clients
13726 do not request or use version 0 descriptors. However, the old hidden
13727 service authorities still accept and serve version 0 descriptors
13728 when contacted by older hidden services/clients.
13729 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13730 anything since 0.2.1.16-rc.
13731 - Remove everything related to building the expert bundle for OS X.
13732 It has confused many users, doesn't work right on OS X 10.6,
13733 and is hard to get rid of once installed. Resolves bug 1274.
13734 - Remove support for .noconnect style addresses. Nobody was using
13735 them, and they provided another avenue for detecting Tor users
13736 via application-level web tricks.
13737 - When we fixed bug 1038 we had to put in a restriction not to send
13738 RELAY_EARLY cells on rend circuits. This was necessary as long
13739 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
13740 active. Now remove this obsolete check. Resolves bug 2081.
13741 - Remove workaround code to handle directory responses from servers
13742 that had bug 539 (they would send HTTP status 503 responses _and_
13743 send a body too). Since only server versions before
13744 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
13745 keep the workaround in place.
13746 - Remove the old 'fuzzy time' logic. It was supposed to be used for
13747 handling calculations where we have a known amount of clock skew and
13748 an allowed amount of unknown skew. But we only used it in three
13749 places, and we never adjusted the known/unknown skew values. This is
13750 still something we might want to do someday, but if we do, we'll
13751 want to do it differently.
13752 - Remove the "--enable-iphone" option to ./configure. According to
13753 reports from Marco Bonetti, Tor builds fine without any special
13754 tweaking on recent iPhone SDK versions.
13757 Changes in version 0.2.1.30 - 2011-02-23
13758 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
13759 change is a slight tweak to Tor's TLS handshake that makes relays
13760 and bridges that run this new version reachable from Iran again.
13761 We don't expect this tweak will win the arms race long-term, but it
13762 buys us time until we roll out a better solution.
13765 - Stop sending a CLOCK_SKEW controller status event whenever
13766 we fetch directory information from a relay that has a wrong clock.
13767 Instead, only inform the controller when it's a trusted authority
13768 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
13769 the rest of bug 1074.
13770 - Fix a bounds-checking error that could allow an attacker to
13771 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
13772 Found by "piebeer".
13773 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
13774 Tor would ignore their RelayBandwidthBurst setting,
13775 potentially using more bandwidth than expected. Bugfix on
13776 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
13777 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
13778 hidserv" in her torrc. The 'hidserv' argument never controlled
13779 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
13782 - Adjust our TLS Diffie-Hellman parameters to match those used by
13784 - Update to the February 1 2011 Maxmind GeoLite Country database.
13787 - Check for and reject overly long directory certificates and
13788 directory tokens before they have a chance to hit any assertions.
13789 Bugfix on 0.2.1.28. Found by "doorss".
13790 - Bring the logic that gathers routerinfos and assesses the
13791 acceptability of circuits into line. This prevents a Tor OP from
13792 getting locked in a cycle of choosing its local OR as an exit for a
13793 path (due to a .exit request) and then rejecting the circuit because
13794 its OR is not listed yet. It also prevents Tor clients from using an
13795 OR running in the same instance as an exit (due to a .exit request)
13796 if the OR does not meet the same requirements expected of an OR
13797 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
13799 o Packaging changes:
13800 - Stop shipping the Tor specs files and development proposal documents
13801 in the tarball. They are now in a separate git repository at
13802 git://git.torproject.org/torspec.git
13803 - Do not include Git version tags as though they are SVN tags when
13804 generating a tarball from inside a repository that has switched
13805 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
13808 Changes in version 0.2.1.29 - 2011-01-15
13809 Tor 0.2.1.29 continues our recent code security audit work. The main
13810 fix resolves a remote heap overflow vulnerability that can allow remote
13811 code execution. Other fixes address a variety of assert and crash bugs,
13812 most of which we think are hard to exploit remotely.
13814 o Major bugfixes (security):
13815 - Fix a heap overflow bug where an adversary could cause heap
13816 corruption. This bug probably allows remote code execution
13817 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
13819 - Prevent a denial-of-service attack by disallowing any
13820 zlib-compressed data whose compression factor is implausibly
13821 high. Fixes part of bug 2324; reported by "doorss".
13822 - Zero out a few more keys in memory before freeing them. Fixes
13823 bug 2384 and part of bug 2385. These key instances found by
13824 "cypherpunks", based on Andrew Case's report about being able
13825 to find sensitive data in Tor's memory space if you have enough
13826 permissions. Bugfix on 0.0.2pre9.
13828 o Major bugfixes (crashes):
13829 - Prevent calls to Libevent from inside Libevent log handlers.
13830 This had potential to cause a nasty set of crashes, especially
13831 if running Libevent with debug logging enabled, and running
13832 Tor with a controller watching for low-severity log messages.
13833 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
13834 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
13835 underflow errors there too. Fixes the other part of bug 2324.
13836 - Fix a bug where we would assert if we ever had a
13837 cached-descriptors.new file (or another file read directly into
13838 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
13839 on 0.2.1.25. Found by doorss.
13840 - Fix some potential asserts and parsing issues with grossly
13841 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
13844 o Minor bugfixes (other):
13845 - Fix a bug with handling misformed replies to reverse DNS lookup
13846 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
13847 bug reported by doorss.
13848 - Fix compilation on mingw when a pthreads compatibility library
13849 has been installed. (We don't want to use it, so we shouldn't
13850 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
13851 - Fix a bug where we would declare that we had run out of virtual
13852 addresses when the address space was only half-exhausted. Bugfix
13854 - Correctly handle the case where AutomapHostsOnResolve is set but
13855 no virtual addresses are available. Fixes bug 2328; bugfix on
13856 0.1.2.1-alpha. Bug found by doorss.
13857 - Correctly handle wrapping around when we run out of virtual
13858 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
13861 - Update to the January 1 2011 Maxmind GeoLite Country database.
13862 - Introduce output size checks on all of our decryption functions.
13865 - Tor does not build packages correctly with Automake 1.6 and earlier;
13866 added a check to Makefile.am to make sure that we're building with
13867 Automake 1.7 or later.
13868 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
13869 because we built it with a too-old version of automake. Thus that
13870 release broke ./configure --enable-openbsd-malloc, which is popular
13871 among really fast exit relays on Linux.
13874 Changes in version 0.2.1.28 - 2010-12-17
13875 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
13876 exploitable bugs. We also took this opportunity to change the IP address
13877 for one of our directory authorities, and to update the geoip database
13881 - Fix a remotely exploitable bug that could be used to crash instances
13882 of Tor remotely by overflowing on the heap. Remote-code execution
13883 hasn't been confirmed, but can't be ruled out. Everyone should
13884 upgrade. Bugfix on the 0.1.1 series and later.
13886 o Directory authority changes:
13887 - Change IP address and ports for gabelmoo (v3 directory authority).
13890 - Update to the December 1 2010 Maxmind GeoLite Country database.
13893 Changes in version 0.2.1.27 - 2010-11-23
13894 Yet another OpenSSL security patch broke its compatibility with Tor:
13895 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
13896 also took this opportunity to fix several crash bugs, integrate a new
13897 directory authority, and update the bundled GeoIP database.
13900 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
13901 No longer set the tlsext_host_name extension on server SSL objects;
13902 but continue to set it on client SSL objects. Our goal in setting
13903 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
13904 bugfix on 0.2.1.1-alpha.
13905 - Do not log messages to the controller while shrinking buffer
13906 freelists. Doing so would sometimes make the controller connection
13907 try to allocate a buffer chunk, which would mess up the internals
13908 of the freelist and cause an assertion failure. Fixes bug 1125;
13909 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
13910 - Learn our external IP address when we're a relay or bridge, even if
13911 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
13912 where we introduced bridge relays that don't need to publish to
13913 be useful. Fixes bug 2050.
13914 - Do even more to reject (and not just ignore) annotations on
13915 router descriptors received anywhere but from the cache. Previously
13916 we would ignore such annotations at first, but cache them to disk
13917 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
13918 - When you're using bridges and your network goes away and your
13919 bridges get marked as down, recover when you attempt a new socks
13920 connection (if the network is back), rather than waiting up to an
13921 hour to try fetching new descriptors for your bridges. Bugfix on
13922 0.2.0.3-alpha; fixes bug 1981.
13925 - Move to the November 2010 Maxmind GeoLite country db (rather
13926 than the June 2009 ip-to-country GeoIP db) for our statistics that
13927 count how many users relays are seeing from each country. Now we'll
13928 have more accurate data, especially for many African countries.
13930 o New directory authorities:
13931 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
13935 - Fix an assertion failure that could occur in directory caches or
13936 bridge users when using a very short voting interval on a testing
13937 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
13939 - Enforce multiplicity rules when parsing annotations. Bugfix on
13940 0.2.0.8-alpha. Found by piebeer.
13941 - Allow handshaking OR connections to take a full KeepalivePeriod
13942 seconds to handshake. Previously, we would close them after
13943 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
13944 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
13946 - When building with --enable-gcc-warnings on OpenBSD, disable
13947 warnings in system headers. This makes --enable-gcc-warnings
13948 pass on OpenBSD 4.8.
13951 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
13952 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
13953 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
13954 Servers can start sending this code when enough clients recognize
13955 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
13956 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
13957 Patch from mingw-san.
13960 - Remove the old debian/ directory from the main Tor distribution.
13961 The official Tor-for-debian git repository lives at the URL
13962 https://git.torproject.org/debian/tor.git
13963 - Stop shipping the old doc/website/ directory in the tarball. We
13964 changed the website format in late 2010, and what we shipped in
13965 0.2.1.26 really wasn't that useful anyway.
13968 Changes in version 0.2.1.26 - 2010-05-02
13969 Tor 0.2.1.26 addresses the recent connection and memory overload
13970 problems we've been seeing on relays, especially relays with their
13971 DirPort open. If your relay has been crashing, or you turned it off
13972 because it used too many resources, give this release a try.
13974 This release also fixes yet another instance of broken OpenSSL libraries
13975 that was causing some relays to drop out of the consensus.
13978 - Teach relays to defend themselves from connection overload. Relays
13979 now close idle circuits early if it looks like they were intended
13980 for directory fetches. Relays are also more aggressive about closing
13981 TLS connections that have no circuits on them. Such circuits are
13982 unlikely to be re-used, and tens of thousands of them were piling
13983 up at the fast relays, causing the relays to run out of sockets
13984 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
13985 their directory fetches over TLS).
13986 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
13987 that claim to be earlier than 0.9.8m, but which have in reality
13988 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
13989 behavior. Possible fix for some cases of bug 1346.
13990 - Directory mirrors were fetching relay descriptors only from v2
13991 directory authorities, rather than v3 authorities like they should.
13992 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
13993 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
13996 - Finally get rid of the deprecated and now harmful notion of "clique
13997 mode", where directory authorities maintain TLS connections to
14001 - In the util/threads test, no longer free the test_mutex before all
14002 worker threads have finished. Bugfix on 0.2.1.6-alpha.
14003 - The master thread could starve the worker threads quite badly on
14004 certain systems, causing them to run only partially in the allowed
14005 window. This resulted in test failures. Now the master thread sleeps
14006 occasionally for a few microseconds while the two worker-threads
14007 compete for the mutex. Bugfix on 0.2.0.1-alpha.
14010 Changes in version 0.2.1.25 - 2010-03-16
14011 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
14012 prevent relays from guessing their IP address correctly. It also fixes
14013 several minor potential security bugs.
14016 - Fix a regression from our patch for bug 1244 that caused relays
14017 to guess their IP address incorrectly if they didn't set Address
14018 in their torrc and/or their address fails to resolve. Bugfix on
14019 0.2.1.23; fixes bug 1269.
14020 - When freeing a session key, zero it out completely. We only zeroed
14021 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
14022 patched by ekir. Fixes bug 1254.
14025 - Fix a dereference-then-NULL-check sequence when publishing
14026 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
14028 - Fix another dereference-then-NULL-check sequence. Bugfix on
14029 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
14030 - Make sure we treat potentially not NUL-terminated strings correctly.
14031 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
14034 Changes in version 0.2.1.24 - 2010-02-21
14035 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
14039 - Work correctly out-of-the-box with even more vendor-patched versions
14040 of OpenSSL. In particular, make it so Debian and OS X don't need
14041 customized patches to run/build.
14044 Changes in version 0.2.1.23 - 2010-02-13
14045 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
14046 again on the latest OS X, and updates the location of a directory
14049 o Major bugfixes (performance):
14050 - We were selecting our guards uniformly at random, and then weighting
14051 which of our guards we'd use uniformly at random. This imbalance
14052 meant that Tor clients were severely limited on throughput (and
14053 probably latency too) by the first hop in their circuit. Now we
14054 select guards weighted by currently advertised bandwidth. We also
14055 automatically discard guards picked using the old algorithm. Fixes
14056 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
14059 - Make Tor work again on the latest OS X: when deciding whether to
14060 use strange flags to turn TLS renegotiation on, detect the OpenSSL
14061 version at run-time, not compile time. We need to do this because
14062 Apple doesn't update its dev-tools headers when it updates its
14063 libraries in a security patch.
14064 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
14065 that could happen on 32-bit platforms with 64-bit time_t. Also fix
14066 a memory leak when requesting a hidden service descriptor we've
14067 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
14071 - Refactor resolve_my_address() to not use gethostbyname() anymore.
14072 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
14075 - Avoid a mad rush at the beginning of each month when each client
14076 rotates half of its guards. Instead we spread the rotation out
14077 throughout the month, but we still avoid leaving a precise timestamp
14078 in the state file about when we first picked the guard. Improves
14079 over the behavior introduced in 0.1.2.17.
14082 Changes in version 0.2.1.22 - 2010-01-19
14083 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
14084 authorities -- it would tell you its whole history of bridge descriptors
14085 if you make the right directory request. This stable update also
14086 rotates two of the seven v3 directory authority keys and locations.
14088 o Directory authority changes:
14089 - Rotate keys (both v3 identity and relay identity) for moria1
14093 - Stop bridge directory authorities from answering dbg-stability.txt
14094 directory queries, which would let people fetch a list of all
14095 bridge identities they track. Bugfix on 0.2.1.6-alpha.
14098 Changes in version 0.2.1.21 - 2009-12-21
14099 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
14100 library. If you use Tor on Linux / Unix and you're getting SSL
14101 renegotiation errors, upgrading should help. We also recommend an
14102 upgrade if you're an exit relay.
14105 - Work around a security feature in OpenSSL 0.9.8l that prevents our
14106 handshake from working unless we explicitly tell OpenSSL that we
14107 are using SSL renegotiation safely. We are, of course, but OpenSSL
14108 0.9.8l won't work unless we say we are.
14109 - Avoid crashing if the client is trying to upload many bytes and the
14110 circuit gets torn down at the same time, or if the flip side
14111 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
14114 - Do not refuse to learn about authority certs and v2 networkstatus
14115 documents that are older than the latest consensus. This bug might
14116 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
14117 Spotted and fixed by xmux.
14118 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
14119 trigger platform-specific option misparsing case found by Coverity
14121 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
14122 trigger assert. Fixes bug 1173.
14125 Changes in version 0.2.1.20 - 2009-10-15
14126 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
14127 services at once, prepares for more performance improvements, and
14128 fixes a bunch of smaller bugs.
14130 The Windows and OS X bundles also include a more recent Vidalia,
14131 and switch from Privoxy to Polipo.
14133 The OS X installers are now drag and drop. It's best to un-install
14134 Tor/Vidalia and then install this new bundle, rather than upgrade. If
14135 you want to upgrade, you'll need to update the paths for Tor and Polipo
14136 in the Vidalia Settings window.
14139 - Send circuit or stream sendme cells when our window has decreased
14140 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
14141 by Karsten when testing the "reduce circuit window" performance
14142 patch. Bugfix on the 54th commit on Tor -- from July 2002,
14143 before the release of Tor 0.0.0. This is the new winner of the
14145 - Fix a remotely triggerable memory leak when a consensus document
14146 contains more than one signature from the same voter. Bugfix on
14148 - Avoid segfault in rare cases when finishing an introduction circuit
14149 as a client and finding out that we don't have an introduction key
14150 for it. Fixes bug 1073. Reported by Aaron Swartz.
14153 - Tor now reads the "circwindow" parameter out of the consensus,
14154 and uses that value for its circuit package window rather than the
14155 default of 1000 cells. Begins the implementation of proposal 168.
14157 o New directory authorities:
14158 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
14160 - Move moria1 and tonga to alternate IP addresses.
14163 - Fix a signed/unsigned compile warning in 0.2.1.19.
14164 - Fix possible segmentation fault on directory authorities. Bugfix on
14166 - Fix an extremely rare infinite recursion bug that could occur if
14167 we tried to log a message after shutting down the log subsystem.
14168 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
14169 - Fix an obscure bug where hidden services on 64-bit big-endian
14170 systems might mis-read the timestamp in v3 introduce cells, and
14171 refuse to connect back to the client. Discovered by "rotor".
14172 Bugfix on 0.2.1.6-alpha.
14173 - We were triggering a CLOCK_SKEW controller status event whenever
14174 we connect via the v2 connection protocol to any relay that has
14175 a wrong clock. Instead, we should only inform the controller when
14176 it's a trusted authority that claims our clock is wrong. Bugfix
14177 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
14178 - We were telling the controller about CHECKING_REACHABILITY and
14179 REACHABILITY_FAILED status events whenever we launch a testing
14180 circuit or notice that one has failed. Instead, only tell the
14181 controller when we want to inform the user of overall success or
14182 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
14184 - Don't warn when we're using a circuit that ends with a node
14185 excluded in ExcludeExitNodes, but the circuit is not used to access
14186 the outside world. This should help fix bug 1090. Bugfix on
14188 - Work around a small memory leak in some versions of OpenSSL that
14189 stopped the memory used by the hostname TLS extension from being
14193 - Add a "getinfo status/accepted-server-descriptor" controller
14194 command, which is the recommended way for controllers to learn
14195 whether our server descriptor has been successfully received by at
14196 least on directory authority. Un-recommend good-server-descriptor
14197 getinfo and status events until we have a better design for them.
14200 Changes in version 0.2.1.19 - 2009-07-28
14201 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
14205 - Make accessing hidden services on 0.2.1.x work right again.
14206 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
14207 part of patch provided by "optimist".
14210 - When a relay/bridge is writing out its identity key fingerprint to
14211 the "fingerprint" file and to its logs, write it without spaces. Now
14212 it will look like the fingerprints in our bridges documentation,
14213 and confuse fewer users.
14216 - Relays no longer publish a new server descriptor if they change
14217 their MaxAdvertisedBandwidth config option but it doesn't end up
14218 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
14219 fixes bug 1026. Patch from Sebastian.
14220 - Avoid leaking memory every time we get a create cell but we have
14221 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
14222 fixes bug 1034. Reported by BarkerJr.
14225 Changes in version 0.2.1.18 - 2009-07-24
14226 Tor 0.2.1.18 lays the foundations for performance improvements,
14227 adds status events to help users diagnose bootstrap problems, adds
14228 optional authentication/authorization for hidden services, fixes a
14229 variety of potential anonymity problems, and includes a huge pile of
14230 other features and bug fixes.
14232 o Major features (clients):
14233 - Start sending "bootstrap phase" status events to the controller,
14234 so it can keep the user informed of progress fetching directory
14235 information and establishing circuits. Also inform the controller
14236 if we think we're stuck at a particular bootstrap phase. Implements
14238 - Clients replace entry guards that were chosen more than a few months
14239 ago. This change should significantly improve client performance,
14240 especially once more people upgrade, since relays that have been
14241 a guard for a long time are currently overloaded.
14242 - Network status consensus documents and votes now contain bandwidth
14243 information for each relay. Clients use the bandwidth values
14244 in the consensus, rather than the bandwidth values in each
14245 relay descriptor. This approach opens the door to more accurate
14246 bandwidth estimates once the directory authorities start doing
14247 active measurements. Implements part of proposal 141.
14249 o Major features (relays):
14250 - Disable and refactor some debugging checks that forced a linear scan
14251 over the whole server-side DNS cache. These accounted for over 50%
14252 of CPU time on a relatively busy exit node's gprof profile. Also,
14253 disable some debugging checks that appeared in exit node profile
14254 data. Found by Jacob.
14255 - New DirPortFrontPage option that takes an html file and publishes
14256 it as "/" on the DirPort. Now relay operators can provide a
14257 disclaimer without needing to set up a separate webserver. There's
14258 a sample disclaimer in contrib/tor-exit-notice.html.
14260 o Major features (hidden services):
14261 - Make it possible to build hidden services that only certain clients
14262 are allowed to connect to. This is enforced at several points,
14263 so that unauthorized clients are unable to send INTRODUCE cells
14264 to the service, or even (depending on the type of authentication)
14265 to learn introduction points. This feature raises the bar for
14266 certain kinds of active attacks against hidden services. Design
14267 and code by Karsten Loesing. Implements proposal 121.
14268 - Relays now store and serve v2 hidden service descriptors by default,
14269 i.e., the new default value for HidServDirectoryV2 is 1. This is
14270 the last step in proposal 114, which aims to make hidden service
14271 lookups more reliable.
14273 o Major features (path selection):
14274 - ExitNodes and Exclude*Nodes config options now allow you to restrict
14275 by country code ("{US}") or IP address or address pattern
14276 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
14277 refinement to decide what config options should take priority if
14278 you ask to both use a particular node and exclude it.
14280 o Major features (misc):
14281 - When building a consensus, do not include routers that are down.
14282 This cuts down 30% to 40% on consensus size. Implements proposal
14284 - New TestingTorNetwork config option to allow adjustment of
14285 previously constant values that could slow bootstrapping. Implements
14286 proposal 135. Patch from Karsten.
14287 - Convert many internal address representations to optionally hold
14288 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
14289 elements. Make resolver code handle nameservers located at IPv6
14291 - More work on making our TLS handshake blend in: modify the list
14292 of ciphers advertised by OpenSSL in client mode to even more
14293 closely resemble a common web browser. We cheat a little so that
14294 we can advertise ciphers that the locally installed OpenSSL doesn't
14296 - Use the TLS1 hostname extension to more closely resemble browser
14299 o Security fixes (anonymity/entropy):
14300 - Never use a connection with a mismatched address to extend a
14301 circuit, unless that connection is canonical. A canonical
14302 connection is one whose address is authenticated by the router's
14303 identity key, either in a NETINFO cell or in a router descriptor.
14304 - Implement most of proposal 110: The first K cells to be sent
14305 along a circuit are marked as special "early" cells; only K "early"
14306 cells will be allowed. Once this code is universal, we can block
14307 certain kinds of denial-of-service attack by requiring that EXTEND
14308 commands must be sent using an "early" cell.
14309 - Resume using OpenSSL's RAND_poll() for better (and more portable)
14310 cross-platform entropy collection again. We used to use it, then
14311 stopped using it because of a bug that could crash systems that
14312 called RAND_poll when they had a lot of fds open. It looks like the
14313 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
14314 at startup, and to call RAND_poll() when we reseed later only if
14315 we have a non-buggy OpenSSL version.
14316 - When the client is choosing entry guards, now it selects at most
14317 one guard from a given relay family. Otherwise we could end up with
14318 all of our entry points into the network run by the same operator.
14319 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
14320 - Do not use or believe expired v3 authority certificates. Patch
14321 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
14322 - Drop begin cells to a hidden service if they come from the middle
14323 of a circuit. Patch from lark.
14324 - When we erroneously receive two EXTEND cells for the same circuit
14325 ID on the same connection, drop the second. Patch from lark.
14326 - Authorities now vote for the Stable flag for any router whose
14327 weighted MTBF is at least 5 days, regardless of the mean MTBF.
14328 - Clients now never report any stream end reason except 'MISC'.
14329 Implements proposal 148.
14331 o Major bugfixes (crashes):
14332 - Parse dates and IPv4 addresses in a locale- and libc-independent
14333 manner, to avoid platform-dependent behavior on malformed input.
14334 - Fix a crash that occurs on exit nodes when a nameserver request
14335 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
14336 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
14338 - Do not assume that a stack-allocated character array will be
14339 64-bit aligned on platforms that demand that uint64_t access is
14340 aligned. Possible fix for bug 604.
14341 - Resolve a very rare crash bug that could occur when the user forced
14342 a nameserver reconfiguration during the middle of a nameserver
14343 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
14344 - Avoid a "0 divided by 0" calculation when calculating router uptime
14345 at directory authorities. Bugfix on 0.2.0.8-alpha.
14346 - Fix an assertion bug in parsing policy-related options; possible fix
14348 - Rate-limit too-many-sockets messages: when they happen, they happen
14349 a lot and end up filling up the disk. Resolves bug 748.
14350 - Fix a race condition that could cause crashes or memory corruption
14351 when running as a server with a controller listening for log
14353 - Avoid crashing when we have a policy specified in a DirPolicy or
14354 SocksPolicy or ReachableAddresses option with ports set on it,
14355 and we re-load the policy. May fix bug 996.
14356 - Fix an assertion failure on 64-bit platforms when we allocated
14357 memory right up to the end of a memarea, then realigned the memory
14358 one step beyond the end. Fixes a possible cause of bug 930.
14359 - Protect the count of open sockets with a mutex, so we can't
14360 corrupt it when two threads are closing or opening sockets at once.
14361 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
14363 o Major bugfixes (clients):
14364 - Discard router descriptors as we load them if they are more than
14365 five days old. Otherwise if Tor is off for a long time and then
14366 starts with cached descriptors, it will try to use the onion keys
14367 in those obsolete descriptors when building circuits. Fixes bug 887.
14368 - When we choose to abandon a new entry guard because we think our
14369 older ones might be better, close any circuits pending on that
14370 new entry guard connection. This fix should make us recover much
14371 faster when our network is down and then comes back. Bugfix on
14372 0.1.2.8-beta; found by lodger.
14373 - When Tor clients restart after 1-5 days, they discard all their
14374 cached descriptors as too old, but they still use the cached
14375 consensus document. This approach is good for robustness, but
14376 bad for performance: since they don't know any bandwidths, they
14377 end up choosing at random rather than weighting their choice by
14378 speed. Fixed by the above feature of putting bandwidths in the
14381 o Major bugfixes (relays):
14382 - Relays were falling out of the networkstatus consensus for
14383 part of a day if they changed their local config but the
14384 authorities discarded their new descriptor as "not sufficiently
14385 different". Now directory authorities accept a descriptor as changed
14386 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
14387 patch by Sebastian.
14388 - Ensure that two circuits can never exist on the same connection
14389 with the same circuit ID, even if one is marked for close. This
14390 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
14391 - Directory authorities were neglecting to mark relays down in their
14392 internal histories if the relays fall off the routerlist without
14393 ever being found unreachable. So there were relays in the histories
14394 that haven't been seen for eight months, and are listed as being
14395 up for eight months. This wreaked havoc on the "median wfu" and
14396 "median mtbf" calculations, in turn making Guard and Stable flags
14397 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
14400 o Major bugfixes (hidden services):
14401 - When establishing a hidden service, introduction points that
14402 originate from cannibalized circuits were completely ignored
14403 and not included in rendezvous service descriptors. This might
14404 have been another reason for delay in making a hidden service
14405 available. Bugfix from long ago (0.0.9.x?)
14407 o Major bugfixes (memory and resource management):
14408 - Fixed some memory leaks -- some quite frequent, some almost
14409 impossible to trigger -- based on results from Coverity.
14410 - Speed up parsing and cut down on memory fragmentation by using
14411 stack-style allocations for parsing directory objects. Previously,
14412 this accounted for over 40% of allocations from within Tor's code
14413 on a typical directory cache.
14414 - Use a Bloom filter rather than a digest-based set to track which
14415 descriptors we need to keep around when we're cleaning out old
14416 router descriptors. This speeds up the computation significantly,
14417 and may reduce fragmentation.
14419 o New/changed config options:
14420 - Now NodeFamily and MyFamily config options allow spaces in
14421 identity fingerprints, so it's easier to paste them in.
14422 Suggested by Lucky Green.
14423 - Allow ports 465 and 587 in the default exit policy again. We had
14424 rejected them in 0.1.0.15, because back in 2005 they were commonly
14425 misconfigured and ended up as spam targets. We hear they are better
14426 locked down these days.
14427 - Make TrackHostExit mappings expire a while after their last use, not
14428 after their creation. Patch from Robert Hogan.
14429 - Add an ExcludeExitNodes option so users can list a set of nodes
14430 that should be be excluded from the exit node position, but
14431 allowed elsewhere. Implements proposal 151.
14432 - New --hush command-line option similar to --quiet. While --quiet
14433 disables all logging to the console on startup, --hush limits the
14434 output to messages of warning and error severity.
14435 - New configure/torrc options (--enable-geoip-stats,
14436 DirRecordUsageByCountry) to record how many IPs we've served
14437 directory info to in each country code, how many status documents
14438 total we've sent to each country code, and what share of the total
14439 directory requests we should expect to see.
14440 - Make outbound DNS packets respect the OutboundBindAddress setting.
14441 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
14442 - Allow separate log levels to be configured for different logging
14443 domains. For example, this allows one to log all notices, warnings,
14444 or errors, plus all memory management messages of level debug or
14445 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
14446 - Update to the "June 3 2009" ip-to-country file.
14448 o Minor features (relays):
14449 - Raise the minimum rate limiting to be a relay from 20000 bytes
14450 to 20480 bytes (aka 20KB/s), to match our documentation. Also
14451 update directory authorities so they always assign the Fast flag
14452 to relays with 20KB/s of capacity. Now people running relays won't
14453 suddenly find themselves not seeing any use, if the network gets
14455 - If we're a relay and we change our IP address, be more verbose
14456 about the reason that made us change. Should help track down
14457 further bugs for relays on dynamic IP addresses.
14458 - Exit servers can now answer resolve requests for ip6.arpa addresses.
14459 - Implement most of Proposal 152: allow specialized servers to permit
14460 single-hop circuits, and clients to use those servers to build
14461 single-hop circuits when using a specialized controller. Patch
14462 from Josh Albrecht. Resolves feature request 768.
14463 - When relays do their initial bandwidth measurement, don't limit
14464 to just our entry guards for the test circuits. Otherwise we tend
14465 to have multiple test circuits going through a single entry guard,
14466 which makes our bandwidth test less accurate. Fixes part of bug 654;
14467 patch contributed by Josh Albrecht.
14469 o Minor features (directory authorities):
14470 - Try not to open more than one descriptor-downloading connection
14471 to an authority at once. This should reduce load on directory
14472 authorities. Fixes bug 366.
14473 - Add cross-certification to newly generated certificates, so that
14474 a signing key is enough information to look up a certificate. Start
14475 serving certificates by <identity digest, signing key digest>
14476 pairs. Implements proposal 157.
14477 - When a directory authority downloads a descriptor that it then
14478 immediately rejects, do not retry downloading it right away. Should
14479 save some bandwidth on authorities. Fix for bug 888. Patch by
14481 - Directory authorities now serve a /tor/dbg-stability.txt URL to
14482 help debug WFU and MTBF calculations.
14483 - In directory authorities' approved-routers files, allow
14484 fingerprints with or without space.
14486 o Minor features (directory mirrors):
14487 - When a download gets us zero good descriptors, do not notify
14488 Tor that new directory information has arrived.
14489 - Servers support a new URL scheme for consensus downloads that
14490 allows the client to specify which authorities are trusted.
14491 The server then only sends the consensus if the client will trust
14492 it. Otherwise a 404 error is sent back. Clients use this
14493 new scheme when the server supports it (meaning it's running
14494 0.2.1.1-alpha or later). Implements proposal 134.
14496 o Minor features (bridges):
14497 - If the bridge config line doesn't specify a port, assume 443.
14498 This makes bridge lines a bit smaller and easier for users to
14500 - If we're using bridges and our network goes away, be more willing
14501 to forgive our bridges and try again when we get an application
14504 o Minor features (hidden services):
14505 - When the client launches an introduction circuit, retry with a
14506 new circuit after 30 seconds rather than 60 seconds.
14507 - Launch a second client-side introduction circuit in parallel
14508 after a delay of 15 seconds (based on work by Christian Wilms).
14509 - Hidden services start out building five intro circuits rather
14510 than three, and when the first three finish they publish a service
14511 descriptor using those. Now we publish our service descriptor much
14512 faster after restart.
14513 - Drop the requirement to have an open dir port for storing and
14514 serving v2 hidden service descriptors.
14516 o Minor features (build and packaging):
14517 - On Linux, use the prctl call to re-enable core dumps when the User
14519 - Try to make sure that the version of Libevent we're running with
14520 is binary-compatible with the one we built with. May address bug
14522 - Add a new --enable-local-appdata configuration switch to change
14523 the default location of the datadir on win32 from APPDATA to
14524 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
14525 entirely. Patch from coderman.
14526 - Build correctly against versions of OpenSSL 0.9.8 or later that
14527 are built without support for deprecated functions.
14528 - On platforms with a maximum syslog string length, truncate syslog
14529 messages to that length ourselves, rather than relying on the
14530 system to do it for us.
14531 - Automatically detect MacOSX versions earlier than 10.4.0, and
14532 disable kqueue from inside Tor when running with these versions.
14533 We previously did this from the startup script, but that was no
14534 help to people who didn't use the startup script. Resolves bug 863.
14535 - Build correctly when configured to build outside the main source
14536 path. Patch from Michael Gold.
14537 - Disable GCC's strict alias optimization by default, to avoid the
14538 likelihood of its introducing subtle bugs whenever our code violates
14539 the letter of C99's alias rules.
14540 - Change the contrib/tor.logrotate script so it makes the new
14541 logs as "_tor:_tor" rather than the default, which is generally
14542 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
14543 - Change our header file guard macros to be less likely to conflict
14544 with system headers. Adam Langley noticed that we were conflicting
14545 with log.h on Android.
14546 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
14547 and stop using a warning that had become unfixably verbose under
14549 - Use a lockfile to make sure that two Tor processes are not
14550 simultaneously running with the same datadir.
14551 - Allow OpenSSL to use dynamic locks if it wants.
14552 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
14554 o Minor features (controllers):
14555 - When generating circuit events with verbose nicknames for
14556 controllers, try harder to look up nicknames for routers on a
14557 circuit. (Previously, we would look in the router descriptors we had
14558 for nicknames, but not in the consensus.) Partial fix for bug 941.
14559 - New controller event NEWCONSENSUS that lists the networkstatus
14560 lines for every recommended relay. Now controllers like Torflow
14561 can keep up-to-date on which relays they should be using.
14562 - New controller event "clients_seen" to report a geoip-based summary
14563 of which countries we've seen clients from recently. Now controllers
14564 like Vidalia can show bridge operators that they're actually making
14566 - Add a 'getinfo status/clients-seen' controller command, in case
14567 controllers want to hear clients_seen events but connect late.
14568 - New CONSENSUS_ARRIVED event to note when a new consensus has
14569 been fetched and validated.
14570 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
14571 controllers to prevent SIGHUP from reloading the configuration.
14573 - Return circuit purposes in response to GETINFO circuit-status.
14575 - Serve the latest v3 networkstatus consensus via the control
14576 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
14577 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
14578 controller can query our current bootstrap state in case it attaches
14579 partway through and wants to catch up.
14580 - Provide circuit purposes along with circuit events to the controller.
14582 o Minor features (tools):
14583 - Do not have tor-resolve automatically refuse all .onion addresses;
14584 if AutomapHostsOnResolve is set in your torrc, this will work fine.
14585 - Add a -p option to tor-resolve for specifying the SOCKS port: some
14586 people find host:port too confusing.
14587 - Print the SOCKS5 error message string as well as the error code
14588 when a tor-resolve request fails. Patch from Jacob.
14590 o Minor bugfixes (memory and resource management):
14591 - Clients no longer cache certificates for authorities they do not
14592 recognize. Bugfix on 0.2.0.9-alpha.
14593 - Do not use C's stdio library for writing to log files. This will
14594 improve logging performance by a minute amount, and will stop
14595 leaking fds when our disk is full. Fixes bug 861.
14596 - Stop erroneous use of O_APPEND in cases where we did not in fact
14597 want to re-seek to the end of a file before every last write().
14598 - Fix a small alignment and memory-wasting bug on buffer chunks.
14600 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
14601 to avoid unused RAM in buffer chunks and memory pools.
14602 - Reduce the default smartlist size from 32 to 16; it turns out that
14603 most smartlists hold around 8-12 elements tops.
14604 - Make dumpstats() log the fullness and size of openssl-internal
14606 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
14607 patch to their OpenSSL, turn it on to save memory on servers. This
14608 patch will (with any luck) get included in a mainline distribution
14610 - Fix a memory leak when v3 directory authorities load their keys
14611 and cert from disk. Bugfix on 0.2.0.1-alpha.
14612 - Stop using malloc_usable_size() to use more area than we had
14613 actually allocated: it was safe, but made valgrind really unhappy.
14614 - Make the assert_circuit_ok() function work correctly on circuits that
14615 have already been marked for close.
14616 - Fix uninitialized size field for memory area allocation: may improve
14617 memory performance during directory parsing.
14619 o Minor bugfixes (clients):
14620 - Stop reloading the router list from disk for no reason when we
14621 run out of reachable directory mirrors. Once upon a time reloading
14622 it would set the 'is_running' flag back to 1 for them. It hasn't
14623 done that for a long time.
14624 - When we had picked an exit node for a connection, but marked it as
14625 "optional", and it turned out we had no onion key for the exit,
14626 stop wanting that exit and try again. This situation may not
14627 be possible now, but will probably become feasible with proposal
14628 158. Spotted by rovv. Fixes another case of bug 752.
14629 - Fix a bug in address parsing that was preventing bridges or hidden
14630 service targets from being at IPv6 addresses.
14631 - Do not remove routers as too old if we do not have any consensus
14632 document. Bugfix on 0.2.0.7-alpha.
14633 - When an exit relay resolves a stream address to a local IP address,
14634 do not just keep retrying that same exit relay over and
14635 over. Instead, just close the stream. Addresses bug 872. Bugfix
14636 on 0.2.0.32. Patch from rovv.
14637 - Made Tor a little less aggressive about deleting expired
14638 certificates. Partial fix for bug 854.
14639 - Treat duplicate certificate fetches as failures, so that we do
14640 not try to re-fetch an expired certificate over and over and over.
14641 - Do not say we're fetching a certificate when we'll in fact skip it
14642 because of a pending download.
14643 - If we have correct permissions on $datadir, we complain to stdout
14644 and fail to start. But dangerous permissions on
14645 $datadir/cached-status/ would cause us to open a log and complain
14646 there. Now complain to stdout and fail to start in both cases. Fixes
14647 bug 820, reported by seeess.
14649 o Minor bugfixes (bridges):
14650 - When we made bridge authorities stop serving bridge descriptors over
14651 unencrypted links, we also broke DirPort reachability testing for
14652 bridges. So bridges with a non-zero DirPort were printing spurious
14653 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
14654 - Don't allow a bridge to publish its router descriptor to a
14655 non-bridge directory authority. Fixes part of bug 932.
14656 - When we change to or from being a bridge, reset our counts of
14657 client usage by country. Fixes bug 932.
14659 o Minor bugfixes (relays):
14660 - Log correct error messages for DNS-related network errors on
14662 - Actually return -1 in the error case for read_bandwidth_usage().
14663 Harmless bug, since we currently don't care about the return value
14664 anywhere. Bugfix on 0.2.0.9-alpha.
14665 - Provide a more useful log message if bug 977 (related to buffer
14666 freelists) ever reappears, and do not crash right away.
14667 - We were already rejecting relay begin cells with destination port
14668 of 0. Now also reject extend cells with destination port or address
14669 of 0. Suggested by lark.
14670 - When we can't transmit a DNS request due to a network error, retry
14671 it after a while, and eventually transmit a failing response to
14672 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
14673 - Solve a bug that kept hardware crypto acceleration from getting
14674 enabled when accounting was turned on. Fixes bug 907. Bugfix on
14676 - When a canonical connection appears later in our internal list
14677 than a noncanonical one for a given OR ID, always use the
14678 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
14680 - Avoid some nasty corner cases in the logic for marking connections
14681 as too old or obsolete or noncanonical for circuits. Partial
14683 - Fix another interesting corner-case of bug 891 spotted by rovv:
14684 Previously, if two hosts had different amounts of clock drift, and
14685 one of them created a new connection with just the wrong timing,
14686 the other might decide to deprecate the new connection erroneously.
14687 Bugfix on 0.1.1.13-alpha.
14688 - If one win32 nameserver fails to get added, continue adding the
14689 rest, and don't automatically fail.
14690 - Fix a bug where an unreachable relay would establish enough
14691 reachability testing circuits to do a bandwidth test -- if
14692 we already have a connection to the middle hop of the testing
14693 circuit, then it could establish the last hop by using the existing
14694 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
14695 circuits no longer use entry guards in 0.2.1.3-alpha.
14697 o Minor bugfixes (directory authorities):
14698 - Limit uploaded directory documents to be 16M rather than 500K.
14699 The directory authorities were refusing v3 consensus votes from
14700 other authorities, since the votes are now 504K. Fixes bug 959;
14701 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
14702 - Directory authorities should never send a 503 "busy" response to
14703 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
14705 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
14706 headers. Bugfix on 0.2.0.10-alpha.
14708 o Minor bugfixes (hidden services):
14709 - When we can't find an intro key for a v2 hidden service descriptor,
14710 fall back to the v0 hidden service descriptor and log a bug message.
14711 Workaround for bug 1024.
14712 - In very rare situations new hidden service descriptors were
14713 published earlier than 30 seconds after the last change to the
14714 service. (We currently think that a hidden service descriptor
14715 that's been stable for 30 seconds is worth publishing.)
14716 - If a hidden service sends us an END cell, do not consider
14717 retrying the connection; just close it. Patch from rovv.
14718 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
14719 service directories if they have no advertised dir port. Bugfix
14722 o Minor bugfixes (tools):
14723 - In the torify(1) manpage, mention that tsocks will leak your
14726 o Minor bugfixes (controllers):
14727 - If the controller claimed responsibility for a stream, but that
14728 stream never finished making its connection, it would live
14729 forever in circuit_wait state. Now we close it after SocksTimeout
14730 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
14731 - Make DNS resolved controller events into "CLOSED", not
14732 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
14734 - The control port would close the connection before flushing long
14735 replies, such as the network consensus, if a QUIT command was issued
14736 before the reply had completed. Now, the control port flushes all
14737 pending replies before closing the connection. Also fix a spurious
14738 warning when a QUIT command is issued after a malformed or rejected
14739 AUTHENTICATE command, but before the connection was closed. Patch
14740 by Marcus Griep. Fixes bugs 1015 and 1016.
14741 - Fix a bug that made stream bandwidth get misreported to the
14744 o Deprecated and removed features:
14745 - The old "tor --version --version" command, which would print out
14746 the subversion "Id" of most of the source files, is now removed. It
14747 turned out to be less useful than we'd expected, and harder to
14749 - RedirectExits has been removed. It was deprecated since
14751 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
14752 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
14753 - Cell pools are now always enabled; --disable-cell-pools is ignored.
14754 - Directory mirrors no longer fetch the v1 directory or
14755 running-routers files. They are obsolete, and nobody asks for them
14756 anymore. This is the first step to making v1 authorities obsolete.
14757 - Take out the TestVia config option, since it was a workaround for
14758 a bug that was fixed in Tor 0.1.1.21.
14759 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
14760 HiddenServiceExcludeNodes as obsolete: they never worked properly,
14761 and nobody seems to be using them. Fixes bug 754. Bugfix on
14762 0.1.0.1-rc. Patch from Christian Wilms.
14763 - Remove all backward-compatibility code for relays running
14764 versions of Tor so old that they no longer work at all on the
14767 o Code simplifications and refactoring:
14768 - Tool-assisted documentation cleanup. Nearly every function or
14769 static variable in Tor should have its own documentation now.
14770 - Rename the confusing or_is_obsolete field to the more appropriate
14771 is_bad_for_new_circs, and move it to or_connection_t where it
14773 - Move edge-only flags from connection_t to edge_connection_t: not
14774 only is this better coding, but on machines of plausible alignment,
14775 it should save 4-8 bytes per connection_t. "Every little bit helps."
14776 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
14777 for consistency; keep old option working for backward compatibility.
14778 - Simplify the code for finding connections to use for a circuit.
14779 - Revise the connection_new functions so that a more typesafe variant
14780 exists. This will work better with Coverity, and let us find any
14781 actual mistakes we're making here.
14782 - Refactor unit testing logic so that dmalloc can be used sensibly
14783 with unit tests to check for memory leaks.
14784 - Move all hidden-service related fields from connection and circuit
14785 structure to substructures: this way they won't eat so much memory.
14786 - Squeeze 2-5% out of client performance (according to oprofile) by
14787 improving the implementation of some policy-manipulation functions.
14788 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
14789 be more efficient. Formerly it was quadratic in the number of
14790 servers; now it should be linear. Fixes bug 509.
14791 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
14792 and n_conn_id_digest fields into a separate structure that's
14793 only needed when the circuit has not yet attached to an n_conn.
14794 - Optimize out calls to time(NULL) that occur for every IO operation,
14795 or for every cell. On systems like Windows where time() is a
14796 slow syscall, this fix will be slightly helpful.
14799 Changes in version 0.2.0.35 - 2009-06-24
14801 - Avoid crashing in the presence of certain malformed descriptors.
14802 Found by lark, and by automated fuzzing.
14803 - Fix an edge case where a malicious exit relay could convince a
14804 controller that the client's DNS question resolves to an internal IP
14805 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
14808 - Finally fix the bug where dynamic-IP relays disappear when their
14809 IP address changes: directory mirrors were mistakenly telling
14810 them their old address if they asked via begin_dir, so they
14811 never got an accurate answer about their new address, so they
14812 just vanished after a day. For belt-and-suspenders, relays that
14813 don't set Address in their config now avoid using begin_dir for
14814 all direct connections. Should fix bugs 827, 883, and 900.
14815 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
14816 that would occur on some exit nodes when DNS failures and timeouts
14817 occurred in certain patterns. Fix for bug 957.
14820 - When starting with a cache over a few days old, do not leak
14821 memory for the obsolete router descriptors in it. Bugfix on
14822 0.2.0.33; fixes bug 672.
14823 - Hidden service clients didn't use a cached service descriptor that
14824 was older than 15 minutes, but wouldn't fetch a new one either,
14825 because there was already one in the cache. Now, fetch a v2
14826 descriptor unless the same descriptor was added to the cache within
14827 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
14830 Changes in version 0.2.0.34 - 2009-02-08
14831 Tor 0.2.0.34 features several more security-related fixes. You should
14832 upgrade, especially if you run an exit relay (remote crash) or a
14833 directory authority (remote infinite loop), or you're on an older
14834 (pre-XP) or not-recently-patched Windows (remote exploit).
14836 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
14837 have many known flaws, and nobody should be using them. You should
14838 upgrade. If you're using a Linux or BSD and its packages are obsolete,
14839 stop using those packages and upgrade anyway.
14842 - Fix an infinite-loop bug on handling corrupt votes under certain
14843 circumstances. Bugfix on 0.2.0.8-alpha.
14844 - Fix a temporary DoS vulnerability that could be performed by
14845 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
14846 - Avoid a potential crash on exit nodes when processing malformed
14847 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
14848 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
14849 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
14852 - Fix compilation on systems where time_t is a 64-bit integer.
14853 Patch from Matthias Drochner.
14854 - Don't consider expiring already-closed client connections. Fixes
14855 bug 893. Bugfix on 0.0.2pre20.
14858 Changes in version 0.2.0.33 - 2009-01-21
14859 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
14860 useful to users. It also finally fixes a bug where a relay or client
14861 that's been off for many days would take a long time to bootstrap.
14863 This update also fixes an important security-related bug reported by
14864 Ilja van Sprundel. You should upgrade. (We'll send out more details
14865 about the bug once people have had some time to upgrade.)
14868 - Fix a heap-corruption bug that may be remotely triggerable on
14869 some platforms. Reported by Ilja van Sprundel.
14872 - When a stream at an exit relay is in state "resolving" or
14873 "connecting" and it receives an "end" relay cell, the exit relay
14874 would silently ignore the end cell and not close the stream. If
14875 the client never closes the circuit, then the exit relay never
14876 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
14877 reported by "wood".
14878 - When sending CREATED cells back for a given circuit, use a 64-bit
14879 connection ID to find the right connection, rather than an addr:port
14880 combination. Now that we can have multiple OR connections between
14881 the same ORs, it is no longer possible to use addr:port to uniquely
14882 identify a connection.
14883 - Bridge relays that had DirPort set to 0 would stop fetching
14884 descriptors shortly after startup, and then briefly resume
14885 after a new bandwidth test and/or after publishing a new bridge
14886 descriptor. Bridge users that try to bootstrap from them would
14887 get a recent networkstatus but would get descriptors from up to
14888 18 hours earlier, meaning most of the descriptors were obsolete
14889 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
14890 - Prevent bridge relays from serving their 'extrainfo' document
14891 to anybody who asks, now that extrainfo docs include potentially
14892 sensitive aggregated client geoip summaries. Bugfix on
14894 - If the cached networkstatus consensus is more than five days old,
14895 discard it rather than trying to use it. In theory it could be
14896 useful because it lists alternate directory mirrors, but in practice
14897 it just means we spend many minutes trying directory mirrors that
14898 are long gone from the network. Also discard router descriptors as
14899 we load them if they are more than five days old, since the onion
14900 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
14903 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
14904 could make gcc generate non-functional binary search code. Bugfix
14906 - Build correctly on platforms without socklen_t.
14907 - Compile without warnings on solaris.
14908 - Avoid potential crash on internal error during signature collection.
14909 Fixes bug 864. Patch from rovv.
14910 - Correct handling of possible malformed authority signing key
14911 certificates with internal signature types. Fixes bug 880.
14912 Bugfix on 0.2.0.3-alpha.
14913 - Fix a hard-to-trigger resource leak when logging credential status.
14915 - When we can't initialize DNS because the network is down, do not
14916 automatically stop Tor from starting. Instead, we retry failed
14917 dns_init() every 10 minutes, and change the exit policy to reject
14918 *:* until one succeeds. Fixes bug 691.
14919 - Use 64 bits instead of 32 bits for connection identifiers used with
14920 the controller protocol, to greatly reduce risk of identifier reuse.
14921 - When we're choosing an exit node for a circuit, and we have
14922 no pending streams, choose a good general exit rather than one that
14923 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
14924 - Fix another case of assuming, when a specific exit is requested,
14925 that we know more than the user about what hosts it allows.
14926 Fixes one case of bug 752. Patch from rovv.
14927 - Clip the MaxCircuitDirtiness config option to a minimum of 10
14928 seconds. Warn the user if lower values are given in the
14929 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
14930 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
14931 user if lower values are given in the configuration. Bugfix on
14932 0.1.1.17-rc. Patch by Sebastian.
14933 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
14934 the cache because we already had a v0 descriptor with the same ID.
14935 Bugfix on 0.2.0.18-alpha.
14936 - Fix a race condition when freeing keys shared between main thread
14937 and CPU workers that could result in a memory leak. Bugfix on
14938 0.1.0.1-rc. Fixes bug 889.
14939 - Send a valid END cell back when a client tries to connect to a
14940 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
14941 840. Patch from rovv.
14942 - Check which hops rendezvous stream cells are associated with to
14943 prevent possible guess-the-streamid injection attacks from
14944 intermediate hops. Fixes another case of bug 446. Based on patch
14946 - If a broken client asks a non-exit router to connect somewhere,
14947 do not even do the DNS lookup before rejecting the connection.
14948 Fixes another case of bug 619. Patch from rovv.
14949 - When a relay gets a create cell it can't decrypt (e.g. because it's
14950 using the wrong onion key), we were dropping it and letting the
14951 client time out. Now actually answer with a destroy cell. Fixes
14952 bug 904. Bugfix on 0.0.2pre8.
14954 o Minor bugfixes (hidden services):
14955 - Do not throw away existing introduction points on SIGHUP. Bugfix on
14956 0.0.6pre1. Patch by Karsten. Fixes bug 874.
14959 - Report the case where all signatures in a detached set are rejected
14960 differently than the case where there is an error handling the
14962 - When we realize that another process has modified our cached
14963 descriptors, print out a more useful error message rather than
14964 triggering an assertion. Fixes bug 885. Patch from Karsten.
14965 - Implement the 0x20 hack to better resist DNS poisoning: set the
14966 case on outgoing DNS requests randomly, and reject responses that do
14967 not match the case correctly. This logic can be disabled with the
14968 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
14969 of servers that do not reliably preserve case in replies. See
14970 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
14972 - Check DNS replies for more matching fields to better resist DNS
14974 - Never use OpenSSL compression: it wastes RAM and CPU trying to
14975 compress cells, which are basically all encrypted, compressed, or
14979 Changes in version 0.2.0.32 - 2008-11-20
14980 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
14981 packages (and maybe other packages) noticed by Theo de Raadt, fixes
14982 a smaller security flaw that might allow an attacker to access local
14983 services, further improves hidden service performance, and fixes a
14984 variety of other issues.
14987 - The "User" and "Group" config options did not clear the
14988 supplementary group entries for the Tor process. The "User" option
14989 is now more robust, and we now set the groups to the specified
14990 user's primary group. The "Group" option is now ignored. For more
14991 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
14992 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
14993 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
14994 - The "ClientDNSRejectInternalAddresses" config option wasn't being
14995 consistently obeyed: if an exit relay refuses a stream because its
14996 exit policy doesn't allow it, we would remember what IP address
14997 the relay said the destination address resolves to, even if it's
14998 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
15001 - Fix a DOS opportunity during the voting signature collection process
15002 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
15004 o Major bugfixes (hidden services):
15005 - When fetching v0 and v2 rendezvous service descriptors in parallel,
15006 we were failing the whole hidden service request when the v0
15007 descriptor fetch fails, even if the v2 fetch is still pending and
15008 might succeed. Similarly, if the last v2 fetch fails, we were
15009 failing the whole hidden service request even if a v0 fetch is
15010 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
15011 - When extending a circuit to a hidden service directory to upload a
15012 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
15013 requests failed, because the router descriptor has not been
15014 downloaded yet. In these cases, do not attempt to upload the
15015 rendezvous descriptor, but wait until the router descriptor is
15016 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
15017 descriptor from a hidden service directory for which the router
15018 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
15022 - Fix several infrequent memory leaks spotted by Coverity.
15023 - When testing for libevent functions, set the LDFLAGS variable
15024 correctly. Found by Riastradh.
15025 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
15026 bootstrapping with tunneled directory connections. Bugfix on
15027 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
15028 - When asked to connect to A.B.exit:80, if we don't know the IP for A
15029 and we know that server B rejects most-but-not all connections to
15030 port 80, we would previously reject the connection. Now, we assume
15031 the user knows what they were asking for. Fixes bug 752. Bugfix
15032 on 0.0.9rc5. Diagnosed by BarkerJr.
15033 - If we overrun our per-second write limits a little, count this as
15034 having used up our write allocation for the second, and choke
15035 outgoing directory writes. Previously, we had only counted this when
15036 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
15037 Bugfix on 0.2.0.x (??).
15038 - Remove the old v2 directory authority 'lefkada' from the default
15039 list. It has been gone for many months.
15040 - Stop doing unaligned memory access that generated bus errors on
15041 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
15042 - Make USR2 log-level switch take effect immediately. Bugfix on
15045 o Minor bugfixes (controller):
15046 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
15047 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
15050 Changes in version 0.2.0.31 - 2008-09-03
15051 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
15052 a big bug we're seeing where in rare cases traffic from one Tor stream
15053 gets mixed into another stream, and fixes a variety of smaller issues.
15056 - Make sure that two circuits can never exist on the same connection
15057 with the same circuit ID, even if one is marked for close. This
15058 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
15059 - Relays now reject risky extend cells: if the extend cell includes
15060 a digest of all zeroes, or asks to extend back to the relay that
15061 sent the extend cell, tear down the circuit. Ideas suggested
15063 - If not enough of our entry guards are available so we add a new
15064 one, we might use the new one even if it overlapped with the
15065 current circuit's exit relay (or its family). Anonymity bugfix
15066 pointed out by rovv.
15069 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
15070 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
15071 - Correctly detect the presence of the linux/netfilter_ipv4.h header
15072 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
15073 - Pick size of default geoip filename string correctly on windows.
15074 Fixes bug 806. Bugfix on 0.2.0.30.
15075 - Make the autoconf script accept the obsolete --with-ssl-dir
15076 option as an alias for the actually-working --with-openssl-dir
15077 option. Fix the help documentation to recommend --with-openssl-dir.
15078 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
15079 - When using the TransPort option on OpenBSD, and using the User
15080 option to change UID and drop privileges, make sure to open
15081 /dev/pf before dropping privileges. Fixes bug 782. Patch from
15082 Christopher Davis. Bugfix on 0.1.2.1-alpha.
15083 - Try to attach connections immediately upon receiving a RENDEZVOUS2
15084 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
15085 on the client side when connecting to a hidden service. Bugfix
15086 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
15087 - When closing an application-side connection because its circuit is
15088 getting torn down, generate the stream event correctly. Bugfix on
15089 0.1.2.x. Anonymous patch.
15092 Changes in version 0.2.0.30 - 2008-07-15
15093 This new stable release switches to a more efficient directory
15094 distribution design, adds features to make connections to the Tor
15095 network harder to block, allows Tor to act as a DNS proxy, adds separate
15096 rate limiting for relayed traffic to make it easier for clients to
15097 become relays, fixes a variety of potential anonymity problems, and
15098 includes the usual huge pile of other features and bug fixes.
15100 o New v3 directory design:
15101 - Tor now uses a new way to learn about and distribute information
15102 about the network: the directory authorities vote on a common
15103 network status document rather than each publishing their own
15104 opinion. Now clients and caches download only one networkstatus
15105 document to bootstrap, rather than downloading one for each
15106 authority. Clients only download router descriptors listed in
15107 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
15109 - Set up moria1, tor26, and dizum as v3 directory authorities
15110 in addition to being v2 authorities. Also add three new ones:
15111 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
15112 dannenberg (run by CCC).
15113 - Switch to multi-level keys for directory authorities: now their
15114 long-term identity key can be kept offline, and they periodically
15115 generate a new signing key. Clients fetch the "key certificates"
15116 to keep up to date on the right keys. Add a standalone tool
15117 "tor-gencert" to generate key certificates. Implements proposal 103.
15118 - Add a new V3AuthUseLegacyKey config option to make it easier for
15119 v3 authorities to change their identity keys if another bug like
15120 Debian's OpenSSL RNG flaw appears.
15121 - Authorities and caches fetch the v2 networkstatus documents
15122 less often, now that v3 is recommended.
15124 o Make Tor connections stand out less on the wire:
15125 - Use an improved TLS handshake designed by Steven Murdoch in proposal
15126 124, as revised in proposal 130. The new handshake is meant to
15127 be harder for censors to fingerprint, and it adds the ability
15128 to detect certain kinds of man-in-the-middle traffic analysis
15129 attacks. The new handshake format includes version negotiation for
15130 OR connections as described in proposal 105, which will allow us
15131 to improve Tor's link protocol more safely in the future.
15132 - Enable encrypted directory connections by default for non-relays,
15133 so censor tools that block Tor directory connections based on their
15134 plaintext patterns will no longer work. This means Tor works in
15135 certain censored countries by default again.
15136 - Stop including recognizeable strings in the commonname part of
15137 Tor's x509 certificates.
15139 o Implement bridge relays:
15140 - Bridge relays (or "bridges" for short) are Tor relays that aren't
15141 listed in the main Tor directory. Since there is no complete public
15142 list of them, even an ISP that is filtering connections to all the
15143 known Tor relays probably won't be able to block all the bridges.
15144 See doc/design-paper/blocking.pdf and proposal 125 for details.
15145 - New config option BridgeRelay that specifies you want to be a
15146 bridge relay rather than a normal relay. When BridgeRelay is set
15147 to 1, then a) you cache dir info even if your DirPort ins't on,
15148 and b) the default for PublishServerDescriptor is now "bridge"
15149 rather than "v2,v3".
15150 - New config option "UseBridges 1" for clients that want to use bridge
15151 relays instead of ordinary entry guards. Clients then specify
15152 bridge relays by adding "Bridge" lines to their config file. Users
15153 can learn about a bridge relay either manually through word of
15154 mouth, or by one of our rate-limited mechanisms for giving out
15155 bridge addresses without letting an attacker easily enumerate them
15156 all. See https://www.torproject.org/bridges for details.
15157 - Bridge relays behave like clients with respect to time intervals
15158 for downloading new v3 consensus documents -- otherwise they
15159 stand out. Bridge users now wait until the end of the interval,
15160 so their bridge relay will be sure to have a new consensus document.
15162 o Implement bridge directory authorities:
15163 - Bridge authorities are like normal directory authorities, except
15164 they don't serve a list of known bridges. Therefore users that know
15165 a bridge's fingerprint can fetch a relay descriptor for that bridge,
15166 including fetching updates e.g. if the bridge changes IP address,
15167 yet an attacker can't just fetch a list of all the bridges.
15168 - Set up Tonga as the default bridge directory authority.
15169 - Bridge authorities refuse to serve bridge descriptors or other
15170 bridge information over unencrypted connections (that is, when
15171 responding to direct DirPort requests rather than begin_dir cells.)
15172 - Bridge directory authorities do reachability testing on the
15173 bridges they know. They provide router status summaries to the
15174 controller via "getinfo ns/purpose/bridge", and also dump summaries
15175 to a file periodically, so we can keep internal stats about which
15176 bridges are functioning.
15177 - If bridge users set the UpdateBridgesFromAuthority config option,
15178 but the digest they ask for is a 404 on the bridge authority,
15179 they fall back to contacting the bridge directly.
15180 - Bridges always use begin_dir to publish their server descriptor to
15181 the bridge authority using an anonymous encrypted tunnel.
15182 - Early work on a "bridge community" design: if bridge authorities set
15183 the BridgePassword config option, they will serve a snapshot of
15184 known bridge routerstatuses from their DirPort to anybody who
15185 knows that password. Unset by default.
15186 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
15187 report sanitized aggregated summaries in their extra-info documents
15188 privately to the bridge authority, listing which countries are
15189 able to reach them. We hope this mechanism will let us learn when
15190 certain countries start trying to block bridges.
15191 - Bridge authorities write bridge descriptors to disk, so they can
15192 reload them after a reboot. They can also export the descriptors
15193 to other programs, so we can distribute them to blocked users via
15194 the BridgeDB interface, e.g. via https://bridges.torproject.org/
15195 and bridges@torproject.org.
15197 o Tor can be a DNS proxy:
15198 - The new client-side DNS proxy feature replaces the need for
15199 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15200 for DNS requests on port 9999, use the Tor network to resolve them
15201 anonymously, and send the reply back like a regular DNS server.
15202 The code still only implements a subset of DNS.
15203 - Add a new AutomapHostsOnResolve option: when it is enabled, any
15204 resolve request for hosts matching a given pattern causes Tor to
15205 generate an internal virtual address mapping for that host. This
15206 allows DNSPort to work sensibly with hidden service users. By
15207 default, .exit and .onion addresses are remapped; the list of
15208 patterns can be reconfigured with AutomapHostsSuffixes.
15209 - Add an "-F" option to tor-resolve to force a resolve for a .onion
15210 address. Thanks to the AutomapHostsOnResolve option, this is no
15211 longer a completely silly thing to do.
15213 o Major features (relay usability):
15214 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15215 a separate set of token buckets for relayed traffic. Right now
15216 relayed traffic is defined as answers to directory requests, and
15217 OR connections that don't have any local circuits on them. See
15218 proposal 111 for details.
15219 - Create listener connections before we setuid to the configured
15220 User and Group. Now non-Windows users can choose port values
15221 under 1024, start Tor as root, and have Tor bind those ports
15222 before it changes to another UID. (Windows users could already
15224 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15225 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15226 on "vserver" accounts. Patch from coderman.
15228 o Major features (directory authorities):
15229 - Directory authorities track weighted fractional uptime and weighted
15230 mean-time-between failures for relays. WFU is suitable for deciding
15231 whether a node is "usually up", while MTBF is suitable for deciding
15232 whether a node is "likely to stay up." We need both, because
15233 "usually up" is a good requirement for guards, while "likely to
15234 stay up" is a good requirement for long-lived connections.
15235 - Directory authorities use a new formula for selecting which relays
15236 to advertise as Guards: they must be in the top 7/8 in terms of
15237 how long we have known about them, and above the median of those
15238 nodes in terms of weighted fractional uptime.
15239 - Directory authorities use a new formula for selecting which relays
15240 to advertise as Stable: when we have 4 or more days of data, use
15241 median measured MTBF rather than median declared uptime. Implements
15243 - Directory authorities accept and serve "extra info" documents for
15244 routers. Routers now publish their bandwidth-history lines in the
15245 extra-info docs rather than the main descriptor. This step saves
15246 60% (!) on compressed router descriptor downloads. Servers upload
15247 extra-info docs to any authority that accepts them; directory
15248 authorities now allow multiple router descriptors and/or extra
15249 info documents to be uploaded in a single go. Authorities, and
15250 caches that have been configured to download extra-info documents,
15251 download them as needed. Implements proposal 104.
15252 - Authorities now list relays who have the same nickname as
15253 a different named relay, but list them with a new flag:
15254 "Unnamed". Now we can make use of relays that happen to pick the
15255 same nickname as a server that registered two years ago and then
15256 disappeared. Implements proposal 122.
15257 - Store routers in a file called cached-descriptors instead of in
15258 cached-routers. Initialize cached-descriptors from cached-routers
15259 if the old format is around. The new format allows us to store
15260 annotations along with descriptors, to record the time we received
15261 each descriptor, its source, and its purpose: currently one of
15262 general, controller, or bridge.
15264 o Major features (other):
15265 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
15266 Tor can warn and/or refuse connections to ports commonly used with
15267 vulnerable-plaintext protocols. Currently we warn on ports 23,
15268 109, 110, and 143, but we don't reject any. Based on proposal 129
15269 by Kevin Bauer and Damon McCoy.
15270 - Integrate Karsten Loesing's Google Summer of Code project to publish
15271 hidden service descriptors on a set of redundant relays that are a
15272 function of the hidden service address. Now we don't have to rely
15273 on three central hidden service authorities for publishing and
15274 fetching every hidden service descriptor. Implements proposal 114.
15275 - Allow tunnelled directory connections to ask for an encrypted
15276 "begin_dir" connection or an anonymized "uses a full Tor circuit"
15277 connection independently. Now we can make anonymized begin_dir
15278 connections for (e.g.) more secure hidden service posting and
15281 o Major bugfixes (crashes and assert failures):
15282 - Stop imposing an arbitrary maximum on the number of file descriptors
15283 used for busy servers. Bug reported by Olaf Selke; patch from
15285 - Avoid possible failures when generating a directory with routers
15286 with over-long versions strings, or too many flags set.
15287 - Fix a rare assert error when we're closing one of our threads:
15288 use a mutex to protect the list of logs, so we never write to the
15289 list as it's being freed. Fixes the very rare bug 575, which is
15290 kind of the revenge of bug 222.
15291 - Avoid segfault in the case where a badly behaved v2 versioning
15292 directory sends a signed networkstatus with missing client-versions.
15293 - When we hit an EOF on a log (probably because we're shutting down),
15294 don't try to remove the log from the list: just mark it as
15295 unusable. (Bulletproofs against bug 222.)
15297 o Major bugfixes (code security fixes):
15298 - Detect size overflow in zlib code. Reported by Justin Ferguson and
15300 - Rewrite directory tokenization code to never run off the end of
15301 a string. Fixes bug 455. Patch from croup.
15302 - Be more paranoid about overwriting sensitive memory on free(),
15303 as a defensive programming tactic to ensure forward secrecy.
15305 o Major bugfixes (anonymity fixes):
15306 - Reject requests for reverse-dns lookup of names that are in
15307 a private address space. Patch from lodger.
15308 - Never report that we've used more bandwidth than we're willing to
15309 relay: it leaks how much non-relay traffic we're using. Resolves
15311 - As a client, do not believe any server that tells us that an
15312 address maps to an internal address space.
15313 - Warn about unsafe ControlPort configurations.
15314 - Directory authorities now call routers Fast if their bandwidth is
15315 at least 100KB/s, and consider their bandwidth adequate to be a
15316 Guard if it is at least 250KB/s, no matter the medians. This fix
15317 complements proposal 107.
15318 - Directory authorities now never mark more than 2 servers per IP as
15319 Valid and Running (or 5 on addresses shared by authorities).
15320 Implements proposal 109, by Kevin Bauer and Damon McCoy.
15321 - If we're a relay, avoid picking ourselves as an introduction point,
15322 a rendezvous point, or as the final hop for internal circuits. Bug
15323 reported by taranis and lodger.
15324 - Exit relays that are used as a client can now reach themselves
15325 using the .exit notation, rather than just launching an infinite
15326 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
15327 - Fix a bug where, when we were choosing the 'end stream reason' to
15328 put in our relay end cell that we send to the exit relay, Tor
15329 clients on Windows were sometimes sending the wrong 'reason'. The
15330 anonymity problem is that exit relays may be able to guess whether
15331 the client is running Windows, thus helping partition the anonymity
15332 set. Down the road we should stop sending reasons to exit relays,
15333 or otherwise prevent future versions of this bug.
15334 - Only update guard status (usable / not usable) once we have
15335 enough directory information. This was causing us to discard all our
15336 guards on startup if we hadn't been running for a few weeks. Fixes
15338 - When our directory information has been expired for a while, stop
15339 being willing to build circuits using it. Fixes bug 401.
15341 o Major bugfixes (peace of mind for relay operators)
15342 - Non-exit relays no longer answer "resolve" relay cells, so they
15343 can't be induced to do arbitrary DNS requests. (Tor clients already
15344 avoid using non-exit relays for resolve cells, but now servers
15345 enforce this too.) Fixes bug 619. Patch from lodger.
15346 - When we setconf ClientOnly to 1, close any current OR and Dir
15347 listeners. Reported by mwenge.
15349 o Major bugfixes (other):
15350 - If we only ever used Tor for hidden service lookups or posts, we
15351 would stop building circuits and start refusing connections after
15352 24 hours, since we falsely believed that Tor was dormant. Reported
15354 - Add a new __HashedControlSessionPassword option for controllers
15355 to use for one-off session password hashes that shouldn't get
15356 saved to disk by SAVECONF --- Vidalia users were accumulating a
15357 pile of HashedControlPassword lines in their torrc files, one for
15358 each time they had restarted Tor and then clicked Save. Make Tor
15359 automatically convert "HashedControlPassword" to this new option but
15360 only when it's given on the command line. Partial fix for bug 586.
15361 - Patch from "Andrew S. Lists" to catch when we contact a directory
15362 mirror at IP address X and he says we look like we're coming from
15363 IP address X. Otherwise this would screw up our address detection.
15364 - Reject uploaded descriptors and extrainfo documents if they're
15365 huge. Otherwise we'll cache them all over the network and it'll
15366 clog everything up. Suggested by Aljosha Judmayer.
15367 - When a hidden service was trying to establish an introduction point,
15368 and Tor *did* manage to reuse one of the preemptively built
15369 circuits, it didn't correctly remember which one it used,
15370 so it asked for another one soon after, until there were no
15371 more preemptive circuits, at which point it launched one from
15372 scratch. Bugfix on 0.0.9.x.
15374 o Rate limiting and load balancing improvements:
15375 - When we add data to a write buffer in response to the data on that
15376 write buffer getting low because of a flush, do not consider the
15377 newly added data as a candidate for immediate flushing, but rather
15378 make it wait until the next round of writing. Otherwise, we flush
15379 and refill recursively, and a single greedy TLS connection can
15380 eat all of our bandwidth.
15381 - When counting the number of bytes written on a TLS connection,
15382 look at the BIO actually used for writing to the network, not
15383 at the BIO used (sometimes) to buffer data for the network.
15384 Looking at different BIOs could result in write counts on the
15385 order of ULONG_MAX. Fixes bug 614.
15386 - If we change our MaxAdvertisedBandwidth and then reload torrc,
15387 Tor won't realize it should publish a new relay descriptor. Fixes
15388 bug 688, reported by mfr.
15389 - Avoid using too little bandwidth when our clock skips a few seconds.
15390 - Choose which bridge to use proportional to its advertised bandwidth,
15391 rather than uniformly at random. This should speed up Tor for
15392 bridge users. Also do this for people who set StrictEntryNodes.
15394 o Bootstrapping faster and building circuits more intelligently:
15395 - Fix bug 660 that was preventing us from knowing that we should
15396 preemptively build circuits to handle expected directory requests.
15397 - When we're checking if we have enough dir info for each relay
15398 to begin establishing circuits, make sure that we actually have
15399 the descriptor listed in the consensus, not just any descriptor.
15400 - Correctly notify one-hop connections when a circuit build has
15401 failed. Possible fix for bug 669. Found by lodger.
15402 - Clients now hold circuitless TLS connections open for 1.5 times
15403 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
15404 rebuild a new circuit over them within that timeframe. Previously,
15405 they held them open only for KeepalivePeriod (5 minutes).
15407 o Performance improvements (memory):
15408 - Add OpenBSD malloc code from "phk" as an optional malloc
15409 replacement on Linux: some glibc libraries do very poorly with
15410 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
15411 ./configure to get the replacement malloc code.
15412 - Switch our old ring buffer implementation for one more like that
15413 used by free Unix kernels. The wasted space in a buffer with 1mb
15414 of data will now be more like 8k than 1mb. The new implementation
15415 also avoids realloc();realloc(); patterns that can contribute to
15416 memory fragmentation.
15417 - Change the way that Tor buffers data that it is waiting to write.
15418 Instead of queueing data cells in an enormous ring buffer for each
15419 client->OR or OR->OR connection, we now queue cells on a separate
15420 queue for each circuit. This lets us use less slack memory, and
15421 will eventually let us be smarter about prioritizing different kinds
15423 - Reference-count and share copies of address policy entries; only 5%
15424 of them were actually distinct.
15425 - Tune parameters for cell pool allocation to minimize amount of
15427 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15428 for every single inactive connection_t. Free items from the
15429 4k/16k-buffer free lists when they haven't been used for a while.
15430 - Make memory debugging information describe more about history
15431 of cell allocation, so we can help reduce our memory use.
15432 - Be even more aggressive about releasing RAM from small
15433 empty buffers. Thanks to our free-list code, this shouldn't be too
15434 performance-intensive.
15435 - Log malloc statistics from mallinfo() on platforms where it exists.
15436 - Use memory pools to allocate cells with better speed and memory
15437 efficiency, especially on platforms where malloc() is inefficient.
15438 - Add a --with-tcmalloc option to the configure script to link
15439 against tcmalloc (if present). Does not yet search for non-system
15442 o Performance improvements (socket management):
15443 - Count the number of open sockets separately from the number of
15444 active connection_t objects. This will let us avoid underusing
15445 our allocated connection limit.
15446 - We no longer use socket pairs to link an edge connection to an
15447 anonymous directory connection or a DirPort test connection.
15448 Instead, we track the link internally and transfer the data
15449 in-process. This saves two sockets per "linked" connection (at the
15450 client and at the server), and avoids the nasty Windows socketpair()
15452 - We were leaking a file descriptor if Tor started with a zero-length
15453 cached-descriptors file. Patch by "freddy77".
15455 o Performance improvements (CPU use):
15456 - Never walk through the list of logs if we know that no log target
15457 is interested in a given message.
15458 - Call routerlist_remove_old_routers() much less often. This should
15459 speed startup, especially on directory caches.
15460 - Base64 decoding was actually showing up on our profile when parsing
15461 the initial descriptor file; switch to an in-process all-at-once
15462 implementation that's about 3.5x times faster than calling out to
15464 - Use a slightly simpler string hashing algorithm (copying Python's
15465 instead of Java's) and optimize our digest hashing algorithm to take
15466 advantage of 64-bit platforms and to remove some possibly-costly
15468 - When implementing AES counter mode, update only the portions of the
15469 counter buffer that need to change, and don't keep separate
15470 network-order and host-order counters on big-endian hosts (where
15471 they are the same).
15472 - Add an in-place version of aes_crypt() so that we can avoid doing a
15473 needless memcpy() call on each cell payload.
15474 - Use Critical Sections rather than Mutexes for synchronizing threads
15475 on win32; Mutexes are heavier-weight, and designed for synchronizing
15478 o Performance improvements (bandwidth use):
15479 - Don't try to launch new descriptor downloads quite so often when we
15480 already have enough directory information to build circuits.
15481 - Version 1 directories are no longer generated in full. Instead,
15482 authorities generate and serve "stub" v1 directories that list
15483 no servers. This will stop Tor versions 0.1.0.x and earlier from
15484 working, but (for security reasons) nobody should be running those
15486 - Avoid going directly to the directory authorities even if you're a
15487 relay, if you haven't found yourself reachable yet or if you've
15488 decided not to advertise your dirport yet. Addresses bug 556.
15489 - If we've gone 12 hours since our last bandwidth check, and we
15490 estimate we have less than 50KB bandwidth capacity but we could
15491 handle more, do another bandwidth test.
15492 - Support "If-Modified-Since" when answering HTTP requests for
15493 directories, running-routers documents, and v2 and v3 networkstatus
15494 documents. (There's no need to support it for router descriptors,
15495 since those are downloaded by descriptor digest.)
15496 - Stop fetching directory info so aggressively if your DirPort is
15497 on but your ORPort is off; stop fetching v2 dir info entirely.
15498 You can override these choices with the new FetchDirInfoEarly
15501 o Changed config option behavior (features):
15502 - Configuration files now accept C-style strings as values. This
15503 helps encode characters not allowed in the current configuration
15504 file format, such as newline or #. Addresses bug 557.
15505 - Add hidden services and DNSPorts to the list of things that make
15506 Tor accept that it has running ports. Change starting Tor with no
15507 ports from a fatal error to a warning; we might change it back if
15508 this turns out to confuse anybody. Fixes bug 579.
15509 - Make PublishServerDescriptor default to 1, so the default doesn't
15510 have to change as we invent new directory protocol versions.
15511 - Allow people to say PreferTunnelledDirConns rather than
15512 PreferTunneledDirConns, for those alternate-spellers out there.
15513 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
15514 accommodate the growing number of servers that use the default
15515 and are reaching it.
15516 - Make it possible to enable HashedControlPassword and
15517 CookieAuthentication at the same time.
15518 - When a TrackHostExits-chosen exit fails too many times in a row,
15519 stop using it. Fixes bug 437.
15521 o Changed config option behavior (bugfixes):
15522 - Do not read the configuration file when we've only been told to
15523 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
15524 based on patch from Sebastian Hahn.
15525 - Actually validate the options passed to AuthDirReject,
15526 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
15527 - Make "ClientOnly 1" config option disable directory ports too.
15528 - Don't stop fetching descriptors when FetchUselessDescriptors is
15529 set, even if we stop asking for circuits. Bug reported by tup
15531 - Servers used to decline to publish their DirPort if their
15532 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
15533 they look only at BandwidthRate and RelayBandwidthRate.
15534 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15535 minus 1 byte: the actual maximum declared bandwidth.
15536 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
15537 - Make the NodeFamilies config option work. (Reported by
15538 lodger -- it has never actually worked, even though we added it
15540 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15541 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15543 o New config options:
15544 - New configuration options AuthDirMaxServersPerAddr and
15545 AuthDirMaxServersperAuthAddr to override default maximum number
15546 of servers allowed on a single IP address. This is important for
15547 running a test network on a single host.
15548 - Three new config options (AlternateDirAuthority,
15549 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
15550 user selectively replace the default directory authorities by type,
15551 rather than the all-or-nothing replacement that DirServer offers.
15552 - New config options AuthDirBadDir and AuthDirListBadDirs for
15553 authorities to mark certain relays as "bad directories" in the
15554 networkstatus documents. Also supports the "!baddir" directive in
15555 the approved-routers file.
15556 - New config option V2AuthoritativeDirectory that all v2 directory
15557 authorities must set. This lets v3 authorities choose not to serve
15558 v2 directory information.
15560 o Minor features (other):
15561 - When we're not serving v2 directory information, there is no reason
15562 to actually keep any around. Remove the obsolete files and directory
15563 on startup if they are very old and we aren't going to serve them.
15564 - When we negotiate a v2 link-layer connection (not yet implemented),
15565 accept RELAY_EARLY cells and turn them into RELAY cells if we've
15566 negotiated a v1 connection for their next step. Initial steps for
15568 - When we have no consensus, check FallbackNetworkstatusFile (defaults
15569 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
15570 we can start out knowing some directory caches. We don't ship with
15571 a fallback consensus by default though, because it was making
15572 bootstrapping take too long while we tried many down relays.
15573 - Authorities send back an X-Descriptor-Not-New header in response to
15574 an accepted-but-discarded descriptor upload. Partially implements
15576 - If we find a cached-routers file that's been sitting around for more
15577 than 28 days unmodified, then most likely it's a leftover from
15578 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15580 - When we (as a cache) download a descriptor because it was listed
15581 in a consensus, remember when the consensus was supposed to expire,
15582 and don't expire the descriptor until then.
15583 - Optionally (if built with -DEXPORTMALLINFO) export the output
15584 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15586 - Tag every guard node in our state file with the version that
15587 we believe added it, or with our own version if we add it. This way,
15588 if a user temporarily runs an old version of Tor and then switches
15589 back to a new one, she doesn't automatically lose her guards.
15590 - When somebody requests a list of statuses or servers, and we have
15591 none of those, return a 404 rather than an empty 200.
15592 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15594 - Add an HSAuthorityRecordStats option that hidden service authorities
15595 can use to track statistics of overall hidden service usage without
15596 logging information that would be as useful to an attacker.
15597 - Allow multiple HiddenServicePort directives with the same virtual
15598 port; when they occur, the user is sent round-robin to one
15599 of the target ports chosen at random. Partially fixes bug 393 by
15600 adding limited ad-hoc round-robining.
15601 - Revamp file-writing logic so we don't need to have the entire
15602 contents of a file in memory at once before we write to disk. Tor,
15605 o Minor bugfixes (other):
15606 - Alter the code that tries to recover from unhandled write
15607 errors, to not try to flush onto a socket that's given us
15609 - Directory mirrors no longer include a guess at the client's IP
15610 address if the connection appears to be coming from the same /24
15611 network; it was producing too many wrong guesses.
15612 - If we're trying to flush the last bytes on a connection (for
15613 example, when answering a directory request), reset the
15614 time-to-give-up timeout every time we manage to write something
15616 - Reject router descriptors with out-of-range bandwidthcapacity or
15617 bandwidthburst values.
15618 - If we can't expand our list of entry guards (e.g. because we're
15619 using bridges or we have StrictEntryNodes set), don't mark relays
15620 down when they fail a directory request. Otherwise we're too quick
15621 to mark all our entry points down.
15622 - Authorities no longer send back "400 you're unreachable please fix
15623 it" errors to Tor servers that aren't online all the time. We're
15624 supposed to tolerate these servers now.
15625 - Let directory authorities startup even when they can't generate
15626 a descriptor immediately, e.g. because they don't know their
15628 - Correctly enforce that elements of directory objects do not appear
15629 more often than they are allowed to appear.
15630 - Stop allowing hibernating servers to be "stable" or "fast".
15631 - On Windows, we were preventing other processes from reading
15632 cached-routers while Tor was running. (Reported by janbar)
15633 - Check return values from pthread_mutex functions.
15634 - When opening /dev/null in finish_daemonize(), do not pass the
15635 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
15636 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
15638 o Controller features:
15639 - The GETCONF command now escapes and quotes configuration values
15640 that don't otherwise fit into the torrc file.
15641 - The SETCONF command now handles quoted values correctly.
15642 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
15643 ask about source, timestamp of arrival, purpose, etc. We need
15644 something like this to help Vidalia not do GeoIP lookups on bridge
15646 - Allow multiple HashedControlPassword config lines, to support
15647 multiple controller passwords.
15648 - Accept LF instead of CRLF on controller, since some software has a
15649 hard time generating real Internet newlines.
15650 - Add GETINFO values for the server status events
15651 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15653 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15654 GETINFO for Torstat to use until it can switch to using extrainfos.
15655 - New config option CookieAuthFile to choose a new location for the
15656 cookie authentication file, and config option
15657 CookieAuthFileGroupReadable to make it group-readable.
15658 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15659 match requests to applications. Patch from Robert Hogan.
15660 - Add a RESOLVE command to launch hostname lookups. Original patch
15662 - Add GETINFO status/enough-dir-info to let controllers tell whether
15663 Tor has downloaded sufficient directory information. Patch from Tup.
15664 - You can now use the ControlSocket option to tell Tor to listen for
15665 controller connections on Unix domain sockets on systems that
15666 support them. Patch from Peter Palfrader.
15667 - New "GETINFO address-mappings/*" command to get address mappings
15668 with expiry information. "addr-mappings/*" is now deprecated.
15670 - Add a new config option __DisablePredictedCircuits designed for
15671 use by the controller, when we don't want Tor to build any circuits
15673 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15674 so we can exit from the middle of the circuit.
15675 - Implement "getinfo status/circuit-established".
15676 - Implement "getinfo status/version/..." so a controller can tell
15677 whether the current version is recommended, and whether any versions
15678 are good, and how many authorities agree. Patch from "shibz".
15679 - Controllers should now specify cache=no or cache=yes when using
15680 the +POSTDESCRIPTOR command.
15681 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
15682 Robert Hogan. Fixes the first part of bug 681.
15683 - When reporting clock skew, and we know that the clock is _at least
15684 as skewed_ as some value, but we don't know the actual value,
15685 report the value as a "minimum skew."
15687 o Controller bugfixes:
15688 - Generate "STATUS_SERVER" events rather than misspelled
15689 "STATUS_SEVER" events. Caught by mwenge.
15690 - Reject controller commands over 1MB in length, so rogue
15691 processes can't run us out of memory.
15692 - Change the behavior of "getinfo status/good-server-descriptor"
15693 so it doesn't return failure when any authority disappears.
15694 - Send NAMESERVER_STATUS messages for a single failed nameserver
15696 - When the DANGEROUS_VERSION controller status event told us we're
15697 running an obsolete version, it used the string "OLD" to describe
15698 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
15699 "OBSOLETE" in both cases.
15700 - Respond to INT and TERM SIGNAL commands before we execute the
15701 signal, in case the signal shuts us down. We had a patch in
15702 0.1.2.1-alpha that tried to do this by queueing the response on
15703 the connection's buffer before shutting down, but that really
15704 isn't the same thing at all. Bug located by Matt Edman.
15705 - Provide DNS expiry times in GMT, not in local time. For backward
15706 compatibility, ADDRMAP events only provide GMT expiry in an extended
15707 field. "GETINFO address-mappings" always does the right thing.
15708 - Use CRLF line endings properly in NS events.
15709 - Make 'getinfo fingerprint' return a 551 error if we're not a
15710 server, so we match what the control spec claims we do. Reported
15712 - Fix a typo in an error message when extendcircuit fails that
15713 caused us to not follow the \r\n-based delimiter protocol. Reported
15715 - When tunneling an encrypted directory connection, and its first
15716 circuit fails, do not leave it unattached and ask the controller
15717 to deal. Fixes the second part of bug 681.
15718 - Treat some 403 responses from directory servers as INFO rather than
15719 WARN-severity events.
15721 o Portability / building / compiling:
15722 - When building with --enable-gcc-warnings, check for whether Apple's
15723 warning "-Wshorten-64-to-32" is available.
15724 - Support compilation to target iPhone; patch from cjacker huang.
15725 To build for iPhone, pass the --enable-iphone option to configure.
15726 - Port Tor to build and run correctly on Windows CE systems, using
15727 the wcecompat library. Contributed by Valerio Lupi.
15728 - Detect non-ASCII platforms (if any still exist) and refuse to
15729 build there: some of our code assumes that 'A' is 65 and so on.
15730 - Clear up some MIPSPro compiler warnings.
15731 - Make autoconf search for libevent, openssl, and zlib consistently.
15732 - Update deprecated macros in configure.in.
15733 - When warning about missing headers, tell the user to let us
15734 know if the compile succeeds anyway, so we can downgrade the
15736 - Include the current subversion revision as part of the version
15737 string: either fetch it directly if we're in an SVN checkout, do
15738 some magic to guess it if we're in an SVK checkout, or use
15739 the last-detected version if we're building from a .tar.gz.
15740 Use this version consistently in log messages.
15741 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15742 - Read resolv.conf files correctly on platforms where read() returns
15743 partial results on small file reads.
15744 - Build without verbose warnings even on gcc 4.2 and 4.3.
15745 - On Windows, correctly detect errors when listing the contents of
15746 a directory. Fix from lodger.
15747 - Run 'make test' as part of 'make dist', so we stop releasing so
15748 many development snapshots that fail their unit tests.
15749 - Add support to detect Libevent versions in the 1.4.x series
15751 - Add command-line arguments to unit-test executable so that we can
15752 invoke any chosen test from the command line rather than having
15753 to run the whole test suite at once; and so that we can turn on
15754 logging for the unit tests.
15755 - Do not automatically run configure from autogen.sh. This
15756 non-standard behavior tended to annoy people who have built other
15758 - Fix a macro/CPP interaction that was confusing some compilers:
15759 some GCCs don't like #if/#endif pairs inside macro arguments.
15761 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
15762 Fixes bug 704; fix from Steven Murdoch.
15763 - Correctly detect transparent proxy support on Linux hosts that
15764 require in.h to be included before netfilter_ipv4.h. Patch
15767 o Logging improvements:
15768 - When we haven't had any application requests lately, don't bother
15769 logging that we have expired a bunch of descriptors.
15770 - When attempting to open a logfile fails, tell us why.
15771 - Only log guard node status when guard node status has changed.
15772 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
15773 make "INFO" 75% less verbose.
15774 - When SafeLogging is disabled, log addresses along with all TLS
15776 - Report TLS "zero return" case as a "clean close" and "IO error"
15777 as a "close". Stop calling closes "unexpected closes": existing
15778 Tors don't use SSL_close(), so having a connection close without
15779 the TLS shutdown handshake is hardly unexpected.
15780 - When we receive a consensus from the future, warn about skew.
15781 - Make "not enough dir info yet" warnings describe *why* Tor feels
15782 it doesn't have enough directory info yet.
15783 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
15784 consumers. (We already do this on HUP.)
15785 - Give more descriptive well-formedness errors for out-of-range
15786 hidden service descriptor/protocol versions.
15787 - Stop recommending that every server operator send mail to tor-ops.
15788 Resolves bug 597. Bugfix on 0.1.2.x.
15789 - Improve skew reporting: try to give the user a better log message
15790 about how skewed they are, and how much this matters.
15791 - New --quiet command-line option to suppress the default console log.
15792 Good in combination with --hash-password.
15793 - Don't complain that "your server has not managed to confirm that its
15794 ports are reachable" if we haven't been able to build any circuits
15796 - Detect the reason for failing to mmap a descriptor file we just
15797 wrote, and give a more useful log message. Fixes bug 533.
15798 - Always prepend "Bug: " to any log message about a bug.
15799 - When dumping memory usage, list bytes used in buffer memory
15801 - When running with dmalloc, dump more stats on hup and on exit.
15802 - Put a platform string (e.g. "Linux i686") in the startup log
15803 message, so when people paste just their logs, we know if it's
15804 OpenBSD or Windows or what.
15805 - When logging memory usage, break down memory used in buffers by
15807 - When we are reporting the DirServer line we just parsed, we were
15808 logging the second stanza of the key fingerprint, not the first.
15809 - Even though Windows is equally happy with / and \ as path separators,
15810 try to use \ consistently on Windows and / consistently on Unix: it
15811 makes the log messages nicer.
15812 - On OSX, stop warning the user that kqueue support in libevent is
15813 "experimental", since it seems to have worked fine for ages.
15815 o Contributed scripts and tools:
15816 - Update linux-tor-prio.sh script to allow QoS based on the uid of
15817 the Tor process. Patch from Marco Bonetti with tweaks from Mike
15819 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15820 Unix users an easy way to script their Tor process (e.g. by
15821 adjusting bandwidth based on the time of the day).
15822 - In the exitlist script, only consider the most recently published
15823 server descriptor for each server. Also, when the user requests
15824 a list of servers that _reject_ connections to a given address,
15825 explicitly exclude the IPs that also have servers that accept
15826 connections to that address. Resolves bug 405.
15827 - Include a new contrib/tor-exit-notice.html file that exit relay
15828 operators can put on their website to help reduce abuse queries.
15830 o Newly deprecated features:
15831 - The status/version/num-versioning and status/version/num-concurring
15832 GETINFO controller options are no longer useful in the v3 directory
15833 protocol: treat them as deprecated, and warn when they're used.
15834 - The RedirectExits config option is now deprecated.
15836 o Removed features:
15837 - Drop the old code to choke directory connections when the
15838 corresponding OR connections got full: thanks to the cell queue
15839 feature, OR conns don't get full any more.
15840 - Remove the old "dns worker" server DNS code: it hasn't been default
15841 since 0.1.2.2-alpha, and all the servers are using the new
15843 - Remove the code to generate the oldest (v1) directory format.
15844 - Remove support for the old bw_accounting file: we've been storing
15845 bandwidth accounting information in the state file since
15846 0.1.2.5-alpha. This may result in bandwidth accounting errors
15847 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15848 downgrade to 0.1.1.x or earlier.
15849 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
15850 it, it had no AES, and it hasn't seen any security patches since
15852 - Stop overloading the circuit_t.onionskin field for both "onionskin
15853 from a CREATE cell that we are waiting for a cpuworker to be
15854 assigned" and "onionskin from an EXTEND cell that we are going to
15855 send to an OR as soon as we are connected". Might help with bug 600.
15856 - Remove the tor_strpartition() function: its logic was confused,
15857 and it was only used for one thing that could be implemented far
15859 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15860 and TorControl.py, as they use the old v0 controller protocol,
15861 and are obsoleted by TorFlow anyway.
15862 - Drop support for v1 rendezvous descriptors, since we never used
15863 them anyway, and the code has probably rotted by now. Based on
15864 patch from Karsten Loesing.
15865 - Stop allowing address masks that do not correspond to bit prefixes.
15866 We have warned about these for a really long time; now it's time
15867 to reject them. (Patch from croup.)
15868 - Remove an optimization in the AES counter-mode code that assumed
15869 that the counter never exceeded 2^68. When the counter can be set
15870 arbitrarily as an IV (as it is by Karsten's new hidden services
15871 code), this assumption no longer holds.
15872 - Disable the SETROUTERPURPOSE controller command: it is now
15876 Changes in version 0.1.2.19 - 2008-01-17
15877 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
15878 exit policy a little bit more conservative so it's safer to run an
15879 exit relay on a home system, and fixes a variety of smaller issues.
15882 - Exit policies now reject connections that are addressed to a
15883 relay's public (external) IP address too, unless
15884 ExitPolicyRejectPrivate is turned off. We do this because too
15885 many relays are running nearby to services that trust them based
15886 on network address.
15889 - When the clock jumps forward a lot, do not allow the bandwidth
15890 buckets to become negative. Fixes bug 544.
15891 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
15892 on every successful resolve. Reported by Mike Perry.
15893 - Purge old entries from the "rephist" database and the hidden
15894 service descriptor database even when DirPort is zero.
15895 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
15896 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
15897 crashing or mis-answering these requests.
15898 - When we decide to send a 503 response to a request for servers, do
15899 not then also send the server descriptors: this defeats the whole
15900 purpose. Fixes bug 539.
15903 - Changing the ExitPolicyRejectPrivate setting should cause us to
15904 rebuild our server descriptor.
15905 - Fix handling of hex nicknames when answering controller requests for
15906 networkstatus by name, or when deciding whether to warn about
15907 unknown routers in a config option. (Patch from mwenge.)
15908 - Fix a couple of hard-to-trigger autoconf problems that could result
15909 in really weird results on platforms whose sys/types.h files define
15910 nonstandard integer types.
15911 - Don't try to create the datadir when running --verify-config or
15912 --hash-password. Resolves bug 540.
15913 - If we were having problems getting a particular descriptor from the
15914 directory caches, and then we learned about a new descriptor for
15915 that router, we weren't resetting our failure count. Reported
15917 - Although we fixed bug 539 (where servers would send HTTP status 503
15918 responses _and_ send a body too), there are still servers out there
15919 that haven't upgraded. Therefore, make clients parse such bodies
15920 when they receive them.
15921 - Run correctly on systems where rlim_t is larger than unsigned long.
15922 This includes some 64-bit systems.
15923 - Run correctly on platforms (like some versions of OS X 10.5) where
15924 the real limit for number of open files is OPEN_FILES, not rlim_max
15925 from getrlimit(RLIMIT_NOFILES).
15926 - Avoid a spurious free on base64 failure.
15927 - Avoid segfaults on certain complex invocations of
15928 router_get_by_hexdigest().
15929 - Fix rare bug on REDIRECTSTREAM control command when called with no
15930 port set: it could erroneously report an error when none had
15934 Changes in version 0.1.2.18 - 2007-10-28
15935 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
15936 hidden service introduction that were causing huge delays, and a big
15937 bug that was causing some servers to disappear from the network status
15938 lists for a few hours each day.
15940 o Major bugfixes (crashes):
15941 - If a connection is shut down abruptly because of something that
15942 happened inside connection_flushed_some(), do not call
15943 connection_finished_flushing(). Should fix bug 451:
15944 "connection_stop_writing: Assertion conn->write_event failed"
15945 Bugfix on 0.1.2.7-alpha.
15946 - Fix possible segfaults in functions called from
15947 rend_process_relay_cell().
15949 o Major bugfixes (hidden services):
15950 - Hidden services were choosing introduction points uniquely by
15951 hexdigest, but when constructing the hidden service descriptor
15952 they merely wrote the (potentially ambiguous) nickname.
15953 - Clients now use the v2 intro format for hidden service
15954 connections: they specify their chosen rendezvous point by identity
15955 digest rather than by (potentially ambiguous) nickname. These
15956 changes could speed up hidden service connections dramatically.
15958 o Major bugfixes (other):
15959 - Stop publishing a new server descriptor just because we get a
15960 HUP signal. This led (in a roundabout way) to some servers getting
15961 dropped from the networkstatus lists for a few hours each day.
15962 - When looking for a circuit to cannibalize, consider family as well
15963 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15964 circuit cannibalization).
15965 - When a router wasn't listed in a new networkstatus, we were leaving
15966 the flags for that router alone -- meaning it remained Named,
15967 Running, etc -- even though absence from the networkstatus means
15968 that it shouldn't be considered to exist at all anymore. Now we
15969 clear all the flags for routers that fall out of the networkstatus
15970 consensus. Fixes bug 529.
15973 - Don't try to access (or alter) the state file when running
15974 --list-fingerprint or --verify-config or --hash-password. Resolves
15976 - When generating information telling us how to extend to a given
15977 router, do not try to include the nickname if it is
15978 absent. Resolves bug 467.
15979 - Fix a user-triggerable segfault in expand_filename(). (There isn't
15980 a way to trigger this remotely.)
15981 - When sending a status event to the controller telling it that an
15982 OR address is reachable, set the port correctly. (Previously we
15983 were reporting the dir port.)
15984 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15985 command. Bugfix on 0.1.2.17.
15986 - When loading bandwidth history, do not believe any information in
15987 the future. Fixes bug 434.
15988 - When loading entry guard information, do not believe any information
15990 - When we have our clock set far in the future and generate an
15991 onion key, then re-set our clock to be correct, we should not stop
15992 the onion key from getting rotated.
15993 - On some platforms, accept() can return a broken address. Detect
15994 this more quietly, and deal accordingly. Fixes bug 483.
15995 - It's not actually an error to find a non-pending entry in the DNS
15996 cache when canceling a pending resolve. Don't log unless stuff
15997 is fishy. Resolves bug 463.
15998 - Don't reset trusted dir server list when we set a configuration
15999 option. Patch from Robert Hogan.
16002 Changes in version 0.1.2.17 - 2007-08-30
16003 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
16004 X bundles. Vidalia 0.0.14 makes authentication required for the
16005 ControlPort in the default configuration, which addresses important
16006 security risks. Everybody who uses Vidalia (or another controller)
16009 In addition, this Tor update fixes major load balancing problems with
16010 path selection, which should speed things up a lot once many people
16013 o Major bugfixes (security):
16014 - We removed support for the old (v0) control protocol. It has been
16015 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
16016 become more of a headache than it's worth.
16018 o Major bugfixes (load balancing):
16019 - When choosing nodes for non-guard positions, weight guards
16020 proportionally less, since they already have enough load. Patch
16022 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
16023 will allow fast Tor servers to get more attention.
16024 - When we're upgrading from an old Tor version, forget our current
16025 guards and pick new ones according to the new weightings. These
16026 three load balancing patches could raise effective network capacity
16027 by a factor of four. Thanks to Mike Perry for measurements.
16029 o Major bugfixes (stream expiration):
16030 - Expire not-yet-successful application streams in all cases if
16031 they've been around longer than SocksTimeout. Right now there are
16032 some cases where the stream will live forever, demanding a new
16033 circuit every 15 seconds. Fixes bug 454; reported by lodger.
16035 o Minor features (controller):
16036 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
16037 is valid before any authentication has been received. It tells
16038 a controller what kind of authentication is expected, and what
16039 protocol is spoken. Implements proposal 119.
16041 o Minor bugfixes (performance):
16042 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
16043 greatly speeding up loading cached-routers from disk on startup.
16044 - Disable sentinel-based debugging for buffer code: we squashed all
16045 the bugs that this was supposed to detect a long time ago, and now
16046 its only effect is to change our buffer sizes from nice powers of
16047 two (which platform mallocs tend to like) to values slightly over
16048 powers of two (which make some platform mallocs sad).
16050 o Minor bugfixes (misc):
16051 - If exit bandwidth ever exceeds one third of total bandwidth, then
16052 use the correct formula to weight exit nodes when choosing paths.
16053 Based on patch from Mike Perry.
16054 - Choose perfectly fairly among routers when choosing by bandwidth and
16055 weighting by fraction of bandwidth provided by exits. Previously, we
16056 would choose with only approximate fairness, and correct ourselves
16057 if we ran off the end of the list.
16058 - If we require CookieAuthentication but we fail to write the
16059 cookie file, we would warn but not exit, and end up in a state
16060 where no controller could authenticate. Now we exit.
16061 - If we require CookieAuthentication, stop generating a new cookie
16062 every time we change any piece of our config.
16063 - Refuse to start with certain directory authority keys, and
16064 encourage people using them to stop.
16065 - Terminate multi-line control events properly. Original patch
16067 - Fix a minor memory leak when we fail to find enough suitable
16068 servers to choose a circuit.
16069 - Stop leaking part of the descriptor when we run into a particularly
16070 unparseable piece of it.
16073 Changes in version 0.1.2.16 - 2007-08-01
16074 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
16075 remote attacker in certain situations to rewrite the user's torrc
16076 configuration file. This can completely compromise anonymity of users
16077 in most configurations, including those running the Vidalia bundles,
16078 TorK, etc. Or worse.
16080 o Major security fixes:
16081 - Close immediately after missing authentication on control port;
16082 do not allow multiple authentication attempts.
16085 Changes in version 0.1.2.15 - 2007-07-17
16086 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
16087 problems, fixes compilation on BSD, and fixes a variety of other
16088 bugs. Everybody should upgrade.
16090 o Major bugfixes (compilation):
16091 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
16093 o Major bugfixes (crashes):
16094 - Try even harder not to dereference the first character after
16095 an mmap(). Reported by lodger.
16096 - Fix a crash bug in directory authorities when we re-number the
16097 routerlist while inserting a new router.
16098 - When the cached-routers file is an even multiple of the page size,
16099 don't run off the end and crash. (Fixes bug 455; based on idea
16101 - Fix eventdns.c behavior on Solaris: It is critical to include
16102 orconfig.h _before_ sys/types.h, so that we can get the expected
16103 definition of _FILE_OFFSET_BITS.
16105 o Major bugfixes (security):
16106 - Fix a possible buffer overrun when using BSD natd support. Bug
16108 - When sending destroy cells from a circuit's origin, don't include
16109 the reason for tearing down the circuit. The spec says we didn't,
16110 and now we actually don't. Reported by lodger.
16111 - Keep streamids from different exits on a circuit separate. This
16112 bug may have allowed other routers on a given circuit to inject
16113 cells into streams. Reported by lodger; fixes bug 446.
16114 - If there's a never-before-connected-to guard node in our list,
16115 never choose any guards past it. This way we don't expand our
16116 guard list unless we need to.
16118 o Minor bugfixes (guard nodes):
16119 - Weight guard selection by bandwidth, so that low-bandwidth nodes
16120 don't get overused as guards.
16122 o Minor bugfixes (directory):
16123 - Correctly count the number of authorities that recommend each
16124 version. Previously, we were under-counting by 1.
16125 - Fix a potential crash bug when we load many server descriptors at
16126 once and some of them make others of them obsolete. Fixes bug 458.
16128 o Minor bugfixes (hidden services):
16129 - Stop tearing down the whole circuit when the user asks for a
16130 connection to a port that the hidden service didn't configure.
16133 o Minor bugfixes (misc):
16134 - On Windows, we were preventing other processes from reading
16135 cached-routers while Tor was running. Reported by janbar.
16136 - Fix a possible (but very unlikely) bug in picking routers by
16137 bandwidth. Add a log message to confirm that it is in fact
16138 unlikely. Patch from lodger.
16139 - Backport a couple of memory leak fixes.
16140 - Backport miscellaneous cosmetic bugfixes.
16143 Changes in version 0.1.2.14 - 2007-05-25
16144 Tor 0.1.2.14 changes the addresses of two directory authorities (this
16145 change especially affects those who serve or use hidden services),
16146 and fixes several other crash- and security-related bugs.
16148 o Directory authority changes:
16149 - Two directory authorities (moria1 and moria2) just moved to new
16150 IP addresses. This change will particularly affect those who serve
16151 or use hidden services.
16153 o Major bugfixes (crashes):
16154 - If a directory server runs out of space in the connection table
16155 as it's processing a begin_dir request, it will free the exit stream
16156 but leave it attached to the circuit, leading to unpredictable
16157 behavior. (Reported by seeess, fixes bug 425.)
16158 - Fix a bug in dirserv_remove_invalid() that would cause authorities
16159 to corrupt memory under some really unlikely scenarios.
16160 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
16161 - Avoid segfaults when reading from mmaped descriptor file. (Reported
16164 o Major bugfixes (security):
16165 - When choosing an entry guard for a circuit, avoid using guards
16166 that are in the same family as the chosen exit -- not just guards
16167 that are exactly the chosen exit. (Reported by lodger.)
16169 o Major bugfixes (resource management):
16170 - If a directory authority is down, skip it when deciding where to get
16171 networkstatus objects or descriptors. Otherwise we keep asking
16172 every 10 seconds forever. Fixes bug 384.
16173 - Count it as a failure if we fetch a valid network-status but we
16174 don't want to keep it. Otherwise we'll keep fetching it and keep
16175 not wanting to keep it. Fixes part of bug 422.
16176 - If all of our dirservers have given us bad or no networkstatuses
16177 lately, then stop hammering them once per minute even when we
16178 think they're failed. Fixes another part of bug 422.
16181 - Actually set the purpose correctly for descriptors inserted with
16182 purpose=controller.
16183 - When we have k non-v2 authorities in our DirServer config,
16184 we ignored the last k authorities in the list when updating our
16186 - Correctly back-off from requesting router descriptors that we are
16187 having a hard time downloading.
16188 - Read resolv.conf files correctly on platforms where read() returns
16189 partial results on small file reads.
16190 - Don't rebuild the entire router store every time we get 32K of
16191 routers: rebuild it when the journal gets very large, or when
16192 the gaps in the store get very large.
16195 - When routers publish SVN revisions in their router descriptors,
16196 authorities now include those versions correctly in networkstatus
16198 - Warn when using a version of libevent before 1.3b to run a server on
16199 OSX or BSD: these versions interact badly with userspace threads.
16202 Changes in version 0.1.2.13 - 2007-04-24
16203 This release features some major anonymity fixes, such as safer path
16204 selection; better client performance; faster bootstrapping, better
16205 address detection, and better DNS support for servers; write limiting as
16206 well as read limiting to make servers easier to run; and a huge pile of
16207 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
16209 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
16210 of the Freenode IRC network, remembering his patience and vision for
16211 free speech on the Internet.
16213 o Major features, client performance:
16214 - Weight directory requests by advertised bandwidth. Now we can
16215 let servers enable write limiting but still allow most clients to
16216 succeed at their directory requests. (We still ignore weights when
16217 choosing a directory authority; I hope this is a feature.)
16218 - Stop overloading exit nodes -- avoid choosing them for entry or
16219 middle hops when the total bandwidth available from non-exit nodes
16220 is much higher than the total bandwidth available from exit nodes.
16221 - Rather than waiting a fixed amount of time between retrying
16222 application connections, we wait only 10 seconds for the first,
16223 10 seconds for the second, and 15 seconds for each retry after
16224 that. Hopefully this will improve the expected user experience.
16225 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
16226 to open a stream fails; now we do in more cases. This should
16227 make clients able to find a good exit faster in some cases, since
16228 unhandleable requests will now get an error rather than timing out.
16230 o Major features, client functionality:
16231 - Implement BEGIN_DIR cells, so we can connect to a directory
16232 server via TLS to do encrypted directory requests rather than
16233 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
16234 config options if you like. For now, this feature only works if
16235 you already have a descriptor for the destination dirserver.
16236 - Add support for transparent application connections: this basically
16237 bundles the functionality of trans-proxy-tor into the Tor
16238 mainline. Now hosts with compliant pf/netfilter implementations
16239 can redirect TCP connections straight to Tor without diverting
16240 through SOCKS. (Based on patch from tup.)
16241 - Add support for using natd; this allows FreeBSDs earlier than
16242 5.1.2 to have ipfw send connections through Tor without using
16243 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16245 o Major features, servers:
16246 - Setting up a dyndns name for your server is now optional: servers
16247 with no hostname or IP address will learn their IP address by
16248 asking the directory authorities. This code only kicks in when you
16249 would normally have exited with a "no address" error. Nothing's
16250 authenticated, so use with care.
16251 - Directory servers now spool server descriptors, v1 directories,
16252 and v2 networkstatus objects to buffers as needed rather than en
16253 masse. They also mmap the cached-routers files. These steps save
16255 - Stop requiring clients to have well-formed certificates, and stop
16256 checking nicknames in certificates. (Clients have certificates so
16257 that they can look like Tor servers, but in the future we might want
16258 to allow them to look like regular TLS clients instead. Nicknames
16259 in certificates serve no purpose other than making our protocol
16260 easier to recognize on the wire.) Implements proposal 106.
16262 o Improvements on DNS support:
16263 - Add "eventdns" asynchronous dns library originally based on code
16264 from Adam Langley. Now we can discard the old rickety dnsworker
16265 concept, and support a wider variety of DNS functions. Allows
16266 multithreaded builds on NetBSD and OpenBSD again.
16267 - Add server-side support for "reverse" DNS lookups (using PTR
16268 records so clients can determine the canonical hostname for a given
16269 IPv4 address). Only supported by servers using eventdns; servers
16270 now announce in their descriptors if they don't support eventdns.
16271 - Workaround for name servers (like Earthlink's) that hijack failing
16272 DNS requests and replace the no-such-server answer with a "helpful"
16273 redirect to an advertising-driven search portal. Also work around
16274 DNS hijackers who "helpfully" decline to hijack known-invalid
16275 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16276 lets you turn it off.
16277 - Servers now check for the case when common DNS requests are going to
16278 wildcarded addresses (i.e. all getting the same answer), and change
16279 their exit policy to reject *:* if it's happening.
16280 - When asked to resolve a hostname, don't use non-exit servers unless
16281 requested to do so. This allows servers with broken DNS to be
16282 useful to the network.
16283 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16284 useless IPv6 DNS resolves.
16285 - Specify and implement client-side SOCKS5 interface for reverse DNS
16286 lookups (see doc/socks-extensions.txt). Also cache them.
16287 - When we change nameservers or IP addresses, reset and re-launch
16288 our tests for DNS hijacking.
16290 o Improvements on reachability testing:
16291 - Servers send out a burst of long-range padding cells once they've
16292 established that they're reachable. Spread them over 4 circuits,
16293 so hopefully a few will be fast. This exercises bandwidth and
16294 bootstraps them into the directory more quickly.
16295 - When we find our DirPort to be reachable, publish a new descriptor
16296 so we'll tell the world (reported by pnx).
16297 - Directory authorities now only decide that routers are reachable
16298 if their identity keys are as expected.
16299 - Do DirPort reachability tests less often, since a single test
16300 chews through many circuits before giving up.
16301 - Avoid some false positives during reachability testing: don't try
16302 to test via a server that's on the same /24 network as us.
16303 - Start publishing one minute or so after we find our ORPort
16304 to be reachable. This will help reduce the number of descriptors
16305 we have for ourselves floating around, since it's quite likely
16306 other things (e.g. DirPort) will change during that minute too.
16307 - Routers no longer try to rebuild long-term connections to directory
16308 authorities, and directory authorities no longer try to rebuild
16309 long-term connections to all servers. We still don't hang up
16310 connections in these two cases though -- we need to look at it
16311 more carefully to avoid flapping, and we likely need to wait til
16312 0.1.1.x is obsolete.
16314 o Improvements on rate limiting:
16315 - Enable write limiting as well as read limiting. Now we sacrifice
16316 capacity if we're pushing out lots of directory traffic, rather
16317 than overrunning the user's intended bandwidth limits.
16318 - Include TLS overhead when counting bandwidth usage; previously, we
16319 would count only the bytes sent over TLS, but not the bytes used
16321 - Servers decline directory requests much more aggressively when
16322 they're low on bandwidth. Otherwise they end up queueing more and
16323 more directory responses, which can't be good for latency.
16324 - But never refuse directory requests from local addresses.
16325 - Be willing to read or write on local connections (e.g. controller
16326 connections) even when the global rate limiting buckets are empty.
16327 - Flush local controller connection buffers periodically as we're
16328 writing to them, so we avoid queueing 4+ megabytes of data before
16330 - Revise and clean up the torrc.sample that we ship with; add
16331 a section for BandwidthRate and BandwidthBurst.
16333 o Major features, NT services:
16334 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16335 command-line flag so that admins can override the default by saying
16336 "tor --service install --user "SomeUser"". This will not affect
16337 existing installed services. Also, warn the user that the service
16338 will look for its configuration file in the service user's
16339 %appdata% directory. (We can't do the "hardwire the user's appdata
16340 directory" trick any more, since we may not have read access to that
16342 - Support running the Tor service with a torrc not in the same
16343 directory as tor.exe and default to using the torrc located in
16344 the %appdata%\Tor\ of the user who installed the service. Patch
16346 - Add an --ignore-missing-torrc command-line option so that we can
16347 get the "use sensible defaults if the configuration file doesn't
16348 exist" behavior even when specifying a torrc location on the
16350 - When stopping an NT service, wait up to 10 sec for it to actually
16351 stop. (Patch from Matt Edman; resolves bug 295.)
16353 o Directory authority improvements:
16354 - Stop letting hibernating or obsolete servers affect uptime and
16356 - Stop listing hibernating servers in the v1 directory.
16357 - Authorities no longer recommend exits as guards if this would shift
16358 too much load to the exit nodes.
16359 - Authorities now specify server versions in networkstatus. This adds
16360 about 2% to the size of compressed networkstatus docs, and allows
16361 clients to tell which servers support BEGIN_DIR and which don't.
16362 The implementation is forward-compatible with a proposed future
16363 protocol version scheme not tied to Tor versions.
16364 - DirServer configuration lines now have an orport= option so
16365 clients can open encrypted tunnels to the authorities without
16366 having downloaded their descriptors yet. Enabled for moria1,
16367 moria2, tor26, and lefkada now in the default configuration.
16368 - Add a BadDirectory flag to network status docs so that authorities
16369 can (eventually) tell clients about caches they believe to be
16370 broken. Not used yet.
16371 - Allow authorities to list nodes as bad exits in their
16372 approved-routers file by fingerprint or by address. If most
16373 authorities set a BadExit flag for a server, clients don't think
16374 of it as a general-purpose exit. Clients only consider authorities
16375 that advertise themselves as listing bad exits.
16376 - Patch from Steve Hildrey: Generate network status correctly on
16377 non-versioning dirservers.
16378 - Have directory authorities allow larger amounts of drift in uptime
16379 without replacing the server descriptor: previously, a server that
16380 restarted every 30 minutes could have 48 "interesting" descriptors
16382 - Reserve the nickname "Unnamed" for routers that can't pick
16383 a hostname: any router can call itself Unnamed; directory
16384 authorities will never allocate Unnamed to any particular router;
16385 clients won't believe that any router is the canonical Unnamed.
16387 o Directory mirrors and clients:
16388 - Discard any v1 directory info that's over 1 month old (for
16389 directories) or over 1 week old (for running-routers lists).
16390 - Clients track responses with status 503 from dirservers. After a
16391 dirserver has given us a 503, we try not to use it until an hour has
16392 gone by, or until we have no dirservers that haven't given us a 503.
16393 - When we get a 503 from a directory, and we're not a server, we no
16394 longer count the failure against the total number of failures
16395 allowed for the object we're trying to download.
16396 - Prepare for servers to publish descriptors less often: never
16397 discard a descriptor simply for being too old until either it is
16398 recommended by no authorities, or until we get a better one for
16399 the same router. Make caches consider retaining old recommended
16400 routers for even longer.
16401 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
16402 headers for content, so that we can work better in the presence of
16403 caching HTTP proxies.
16404 - Stop fetching descriptors if you're not a dir mirror and you
16405 haven't tried to establish any circuits lately. (This currently
16406 causes some dangerous behavior, because when you start up again
16407 you'll use your ancient server descriptors.)
16409 o Major fixes, crashes:
16410 - Stop crashing when the controller asks us to resetconf more than
16411 one config option at once. (Vidalia 0.0.11 does this.)
16412 - Fix a longstanding obscure crash bug that could occur when we run
16413 out of DNS worker processes, if we're not using eventdns. (Resolves
16415 - Fix an assert that could trigger if a controller quickly set then
16416 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
16417 - Avoid crash when telling controller about stream-status and a
16418 stream is detached.
16419 - Avoid sending junk to controllers or segfaulting when a controller
16420 uses EVENT_NEW_DESC with verbose nicknames.
16421 - Stop triggering asserts if the controller tries to extend hidden
16422 service circuits (reported by mwenge).
16423 - If we start a server with ClientOnly 1, then set ClientOnly to 0
16424 and hup, stop triggering an assert based on an empty onion_key.
16425 - Mask out all signals in sub-threads; only the libevent signal
16426 handler should be processing them. This should prevent some crashes
16427 on some machines using pthreads. (Patch from coderman.)
16428 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
16430 o Major fixes, anonymity/security:
16431 - Automatically avoid picking more than one node from the same
16432 /16 network when constructing a circuit. Add an
16433 "EnforceDistinctSubnets" option to let people disable it if they
16434 want to operate private test networks on a single subnet.
16435 - When generating bandwidth history, round down to the nearest
16436 1k. When storing accounting data, round up to the nearest 1k.
16437 - When we're running as a server, remember when we last rotated onion
16438 keys, so that we will rotate keys once they're a week old even if
16439 we never stay up for a week ourselves.
16440 - If a client asked for a server by name, and there's a named server
16441 in our network-status but we don't have its descriptor yet, we
16442 could return an unnamed server instead.
16443 - Reject (most) attempts to use Tor circuits with length one. (If
16444 many people start using Tor as a one-hop proxy, exit nodes become
16445 a more attractive target for compromise.)
16446 - Just because your DirPort is open doesn't mean people should be
16447 able to remotely teach you about hidden service descriptors. Now
16448 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16449 - Fix a potential race condition in the rpm installer. Found by
16451 - Do not log IPs with TLS failures for incoming TLS
16452 connections. (Fixes bug 382.)
16454 o Major fixes, other:
16455 - If our system clock jumps back in time, don't publish a negative
16456 uptime in the descriptor.
16457 - When we start during an accounting interval before it's time to wake
16458 up, remember to wake up at the correct time. (May fix bug 342.)
16459 - Previously, we would cache up to 16 old networkstatus documents
16460 indefinitely, if they came from nontrusted authorities. Now we
16461 discard them if they are more than 10 days old.
16462 - When we have a state file we cannot parse, tell the user and
16463 move it aside. Now we avoid situations where the user starts
16464 Tor in 1904, Tor writes a state file with that timestamp in it,
16465 the user fixes her clock, and Tor refuses to start.
16466 - Publish a new descriptor after we hup/reload. This is important
16467 if our config has changed such that we'll want to start advertising
16468 our DirPort now, etc.
16469 - If we are using an exit enclave and we can't connect, e.g. because
16470 its webserver is misconfigured to not listen on localhost, then
16471 back off and try connecting from somewhere else before we fail.
16473 o New config options or behaviors:
16474 - When EntryNodes are configured, rebuild the guard list to contain,
16475 in order: the EntryNodes that were guards before; the rest of the
16476 EntryNodes; the nodes that were guards before.
16477 - Do not warn when individual nodes in the configuration's EntryNodes,
16478 ExitNodes, etc are down: warn only when all possible nodes
16479 are down. (Fixes bug 348.)
16480 - Put a lower-bound on MaxAdvertisedBandwidth.
16481 - Start using the state file to store bandwidth accounting data:
16482 the bw_accounting file is now obsolete. We'll keep generating it
16483 for a while for people who are still using 0.1.2.4-alpha.
16484 - Try to batch changes to the state file so that we do as few
16485 disk writes as possible while still storing important things in
16487 - The state file and the bw_accounting file get saved less often when
16488 the AvoidDiskWrites config option is set.
16489 - Make PIDFile work on Windows.
16490 - Add internal descriptions for a bunch of configuration options:
16491 accessible via controller interface and in comments in saved
16493 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16494 NNTP by default, so this seems like a sensible addition.
16495 - Clients now reject hostnames with invalid characters. This should
16496 avoid some inadvertent info leaks. Add an option
16497 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16498 is running a private network with hosts called @, !, and #.
16499 - Check for addresses with invalid characters at the exit as well,
16500 and warn less verbosely when they fail. You can override this by
16501 setting ServerDNSAllowNonRFC953Addresses to 1.
16502 - Remove some options that have been deprecated since at least
16503 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16504 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16505 to set log options. Mark PathlenCoinWeight as obsolete.
16506 - Stop accepting certain malformed ports in configured exit policies.
16507 - When the user uses bad syntax in the Log config line, stop
16508 suggesting other bad syntax as a replacement.
16509 - Add new config option "ResolvConf" to let the server operator
16510 choose an alternate resolve.conf file when using eventdns.
16511 - If one of our entry guards is on the ExcludeNodes list, or the
16512 directory authorities don't think it's a good guard, treat it as
16513 if it were unlisted: stop using it as a guard, and throw it off
16514 the guards list if it stays that way for a long time.
16515 - Allow directory authorities to be marked separately as authorities
16516 for the v1 directory protocol, the v2 directory protocol, and
16517 as hidden service directories, to make it easier to retire old
16518 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16519 to continue being hidden service authorities too.
16520 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16521 - Make TrackExitHosts case-insensitive, and fix the behavior of
16522 ".suffix" TrackExitHosts items to avoid matching in the middle of
16524 - New DirPort behavior: if you have your dirport set, you download
16525 descriptors aggressively like a directory mirror, whether or not
16526 your ORPort is set.
16529 - Create a new file ReleaseNotes which was the old ChangeLog. The
16530 new ChangeLog file now includes the notes for all development
16532 - Add a new address-spec.txt document to describe our special-case
16533 addresses: .exit, .onion, and .noconnnect.
16534 - Fork the v1 directory protocol into its own spec document,
16535 and mark dir-spec.txt as the currently correct (v2) spec.
16537 o Packaging, porting, and contrib
16538 - "tor --verify-config" now exits with -1(255) or 0 depending on
16539 whether the config options are bad or good.
16540 - The Debian package now uses --verify-config when (re)starting,
16541 to distinguish configuration errors from other errors.
16542 - Adapt a patch from goodell to let the contrib/exitlist script
16543 take arguments rather than require direct editing.
16544 - Prevent the contrib/exitlist script from printing the same
16545 result more than once.
16546 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16547 - In the hidden service example in torrc.sample, stop recommending
16548 esoteric and discouraged hidden service options.
16549 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16550 values before failing, and always enables eventdns.
16551 - Try to detect Windows correctly when cross-compiling.
16552 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16553 Try to fix this in configure.in by checking for most functions
16554 before we check for libevent.
16555 - Update RPMs to require libevent 1.2.
16556 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16557 or later. Log when we are doing this, so we can diagnose it when
16558 it fails. (Also, recommend libevent 1.1b for kqueue and
16559 win32 methods; deprecate libevent 1.0b harder; make libevent
16560 recommendation system saner.)
16561 - Build with recent (1.3+) libevents on platforms that do not
16562 define the nonstandard types "u_int8_t" and friends.
16563 - Remove architecture from OS X builds. The official builds are
16564 now universal binaries.
16565 - Run correctly on OS X platforms with case-sensitive filesystems.
16566 - Correctly set maximum connection limit on Cygwin. (This time
16568 - Start compiling on MinGW on Windows (patches from Mike Chiussi
16570 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16571 - Finally fix the openssl warnings from newer gccs that believe that
16572 ignoring a return value is okay, but casting a return value and
16573 then ignoring it is a sign of madness.
16574 - On architectures where sizeof(int)>4, still clamp declarable
16575 bandwidth to INT32_MAX.
16577 o Minor features, controller:
16578 - Warn the user when an application uses the obsolete binary v0
16579 control protocol. We're planning to remove support for it during
16580 the next development series, so it's good to give people some
16582 - Add STREAM_BW events to report per-entry-stream bandwidth
16583 use. (Patch from Robert Hogan.)
16584 - Rate-limit SIGNEWNYM signals in response to controllers that
16585 impolitely generate them for every single stream. (Patch from
16586 mwenge; closes bug 394.)
16587 - Add a REMAP status to stream events to note that a stream's
16588 address has changed because of a cached address or a MapAddress
16590 - Make REMAP stream events have a SOURCE (cache or exit), and
16591 make them generated in every case where we get a successful
16592 connected or resolved cell.
16593 - Track reasons for OR connection failure; make these reasons
16594 available via the controller interface. (Patch from Mike Perry.)
16595 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16596 can learn when clients are sending malformed hostnames to Tor.
16597 - Specify and implement some of the controller status events.
16598 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16599 - Reimplement GETINFO so that info/names stays in sync with the
16601 - Implement "GETINFO fingerprint".
16602 - Implement "SETEVENTS GUARD" so controllers can get updates on
16603 entry guard status as it changes.
16604 - Make all connections to addresses of the form ".noconnect"
16605 immediately get closed. This lets application/controller combos
16606 successfully test whether they're talking to the same Tor by
16607 watching for STREAM events.
16608 - Add a REASON field to CIRC events; for backward compatibility, this
16609 field is sent only to controllers that have enabled the extended
16610 event format. Also, add additional reason codes to explain why
16611 a given circuit has been destroyed or truncated. (Patches from
16613 - Add a REMOTE_REASON field to extended CIRC events to tell the
16614 controller why a remote OR told us to close a circuit.
16615 - Stream events also now have REASON and REMOTE_REASON fields,
16616 working much like those for circuit events.
16617 - There's now a GETINFO ns/... field so that controllers can ask Tor
16618 about the current status of a router.
16619 - A new event type "NS" to inform a controller when our opinion of
16620 a router's status has changed.
16621 - Add a GETINFO events/names and GETINFO features/names so controllers
16622 can tell which events and features are supported.
16623 - A new CLEARDNSCACHE signal to allow controllers to clear the
16624 client-side DNS cache without expiring circuits.
16625 - Fix CIRC controller events so that controllers can learn the
16626 identity digests of non-Named servers used in circuit paths.
16627 - Let controllers ask for more useful identifiers for servers. Instead
16628 of learning identity digests for un-Named servers and nicknames
16629 for Named servers, the new identifiers include digest, nickname,
16630 and indication of Named status. Off by default; see control-spec.txt
16631 for more information.
16632 - Add a "getinfo address" controller command so it can display Tor's
16633 best guess to the user.
16634 - New controller event to alert the controller when our server
16635 descriptor has changed.
16636 - Give more meaningful errors on controller authentication failure.
16637 - Export the default exit policy via the control port, so controllers
16638 don't need to guess what it is / will be later.
16640 o Minor bugfixes, controller:
16641 - When creating a circuit via the controller, send a 'launched'
16642 event when we're done, so we follow the spec better.
16643 - Correct the control spec to match how the code actually responds
16644 to 'getinfo addr-mappings/*'. Reported by daejees.
16645 - The control spec described a GUARDS event, but the code
16646 implemented a GUARD event. Standardize on GUARD, but let people
16647 ask for GUARDS too. Reported by daejees.
16648 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16649 clear the corresponding on_circuit variable, and remember later
16650 that we don't need to send a redundant CLOSED event. (Resolves part
16652 - Report events where a resolve succeeded or where we got a socks
16653 protocol error correctly, rather than calling both of them
16655 - Change reported stream target addresses to IP consistently when
16656 we finally get the IP from an exit node.
16657 - Send log messages to the controller even if they happen to be very
16659 - Flush ERR-level controller status events just like we currently
16660 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16661 the controller from learning about current events.
16662 - Report the circuit number correctly in STREAM CLOSED events. Bug
16663 reported by Mike Perry.
16664 - Do not report bizarre values for results of accounting GETINFOs
16665 when the last second's write or read exceeds the allotted bandwidth.
16666 - Report "unrecognized key" rather than an empty string when the
16667 controller tries to fetch a networkstatus that doesn't exist.
16668 - When the controller does a "GETINFO network-status", tell it
16669 about even those routers whose descriptors are very old, and use
16670 long nicknames where appropriate.
16671 - Fix handling of verbose nicknames with ORCONN controller events:
16672 make them show up exactly when requested, rather than exactly when
16674 - Controller signals now work on non-Unix platforms that don't define
16675 SIGUSR1 and SIGUSR2 the way we expect.
16676 - Respond to SIGNAL command before we execute the signal, in case
16677 the signal shuts us down. Suggested by Karsten Loesing.
16678 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16680 o Minor features, code performance:
16681 - Major performance improvement on inserting descriptors: change
16682 algorithm from O(n^2) to O(n).
16683 - Do not rotate onion key immediately after setting it for the first
16685 - Call router_have_min_dir_info half as often. (This is showing up in
16686 some profiles, but not others.)
16687 - When using GCC, make log_debug never get called at all, and its
16688 arguments never get evaluated, when no debug logs are configured.
16689 (This is showing up in some profiles, but not others.)
16690 - Statistics dumped by -USR2 now include a breakdown of public key
16691 operations, for profiling.
16692 - Make the common memory allocation path faster on machines where
16693 malloc(0) returns a pointer.
16694 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16695 split connection_t into edge, or, dir, control, and base structs.
16696 These will save quite a bit of memory on busy servers, and they'll
16697 also help us track down bugs in the code and bugs in the spec.
16698 - Use OpenSSL's AES implementation on platforms where it's faster.
16699 This could save us as much as 10% CPU usage.
16701 o Minor features, descriptors and descriptor handling:
16702 - Avoid duplicate entries on MyFamily line in server descriptor.
16703 - When Tor receives a router descriptor that it asked for, but
16704 no longer wants (because it has received fresh networkstatuses
16705 in the meantime), do not warn the user. Cache the descriptor if
16706 we're a cache; drop it if we aren't.
16707 - Servers no longer ever list themselves in their "family" line,
16708 even if configured to do so. This makes it easier to configure
16709 family lists conveniently.
16711 o Minor fixes, confusing/misleading log messages:
16712 - Display correct results when reporting which versions are
16713 recommended, and how recommended they are. (Resolves bug 383.)
16714 - Inform the server operator when we decide not to advertise a
16715 DirPort due to AccountingMax enabled or a low BandwidthRate.
16716 - Only include function names in log messages for info/debug messages.
16717 For notice/warn/err, the content of the message should be clear on
16718 its own, and printing the function name only confuses users.
16719 - Remove even more protocol-related warnings from Tor server logs,
16720 such as bad TLS handshakes and malformed begin cells.
16721 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16722 when the IP address is mapped through MapAddress to a hostname.
16723 - Fix misleading log messages: an entry guard that is "unlisted",
16724 as well as not known to be "down" (because we've never heard
16725 of it), is not therefore "up".
16727 o Minor fixes, old/obsolete behavior:
16728 - Start assuming we can use a create_fast cell if we don't know
16729 what version a router is running.
16730 - We no longer look for identity and onion keys in "identity.key" and
16731 "onion.key" -- these were replaced by secret_id_key and
16732 secret_onion_key in 0.0.8pre1.
16733 - We no longer require unrecognized directory entries to be
16735 - Drop compatibility with obsolete Tors that permit create cells
16736 to have the wrong circ_id_type.
16737 - Remove code to special-case "-cvs" ending, since it has not
16738 actually mattered since 0.0.9.
16739 - Don't re-write the fingerprint file every restart, unless it has
16742 o Minor fixes, misc client-side behavior:
16743 - Always remove expired routers and networkstatus docs before checking
16744 whether we have enough information to build circuits. (Fixes
16746 - When computing clock skew from directory HTTP headers, consider what
16747 time it was when we finished asking for the directory, not what
16749 - Make our socks5 handling more robust to broken socks clients:
16750 throw out everything waiting on the buffer in between socks
16751 handshake phases, since they can't possibly (so the theory
16752 goes) have predicted what we plan to respond to them.
16753 - Expire socks connections if they spend too long waiting for the
16754 handshake to finish. Previously we would let them sit around for
16755 days, if the connecting application didn't close them either.
16756 - And if the socks handshake hasn't started, don't send a
16757 "DNS resolve socks failed" handshake reply; just close it.
16758 - If the user asks to use invalid exit nodes, be willing to use
16760 - Track unreachable entry guards correctly: don't conflate
16761 'unreachable by us right now' with 'listed as down by the directory
16762 authorities'. With the old code, if a guard was unreachable by us
16763 but listed as running, it would clog our guard list forever.
16764 - Behave correctly in case we ever have a network with more than
16765 2GB/s total advertised capacity.
16766 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16767 - Fix a memory leak when we ask for "all" networkstatuses and we
16768 get one we don't recognize.
16771 Changes in version 0.1.1.26 - 2006-12-14
16772 o Security bugfixes:
16773 - Stop sending the HttpProxyAuthenticator string to directory
16774 servers when directory connections are tunnelled through Tor.
16775 - Clients no longer store bandwidth history in the state file.
16776 - Do not log introduction points for hidden services if SafeLogging
16780 - Fix an assert failure when a directory authority sets
16781 AuthDirRejectUnlisted and then receives a descriptor from an
16782 unlisted router (reported by seeess).
16785 Changes in version 0.1.1.25 - 2006-11-04
16787 - When a client asks us to resolve (rather than connect to)
16788 an address, and we have a cached answer, give them the cached
16789 answer. Previously, we would give them no answer at all.
16790 - We were building exactly the wrong circuits when we predict
16791 hidden service requirements, meaning Tor would have to build all
16792 its circuits on demand.
16793 - If none of our live entry guards have a high uptime, but we
16794 require a guard with a high uptime, try adding a new guard before
16795 we give up on the requirement. This patch should make long-lived
16796 connections more stable on average.
16797 - When testing reachability of our DirPort, don't launch new
16798 tests when there's already one in progress -- unreachable
16799 servers were stacking up dozens of testing streams.
16801 o Security bugfixes:
16802 - When the user sends a NEWNYM signal, clear the client-side DNS
16803 cache too. Otherwise we continue to act on previous information.
16806 - Avoid a memory corruption bug when creating a hash table for
16808 - Avoid possibility of controller-triggered crash when misusing
16809 certain commands from a v0 controller on platforms that do not
16810 handle printf("%s",NULL) gracefully.
16811 - Avoid infinite loop on unexpected controller input.
16812 - Don't log spurious warnings when we see a circuit close reason we
16813 don't recognize; it's probably just from a newer version of Tor.
16814 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16815 Tor/Privoxy we also uninstall Vidalia.
16818 Changes in version 0.1.1.24 - 2006-09-29
16820 - Allow really slow clients to not hang up five minutes into their
16821 directory downloads (suggested by Adam J. Richter).
16822 - Fix major performance regression from 0.1.0.x: instead of checking
16823 whether we have enough directory information every time we want to
16824 do something, only check when the directory information has changed.
16825 This should improve client CPU usage by 25-50%.
16826 - Don't crash if, after a server has been running for a while,
16827 it can't resolve its hostname.
16828 - When a client asks us to resolve (not connect to) an address,
16829 and we have a cached answer, give them the cached answer.
16830 Previously, we would give them no answer at all.
16833 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16834 - Don't crash when the controller receives a third argument to an
16835 "extendcircuit" request.
16836 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16837 response; fix error code when "getinfo dir/status/" fails.
16838 - Fix configure.in to not produce broken configure files with
16839 more recent versions of autoconf. Thanks to Clint for his auto*
16841 - Fix security bug on NetBSD that could allow someone to force
16842 uninitialized RAM to be sent to a server's DNS resolver. This
16843 only affects NetBSD and other platforms that do not bounds-check
16845 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16846 methods: these are known to be buggy.
16847 - If we're a directory mirror and we ask for "all" network status
16848 documents, we would discard status documents from authorities
16849 we don't recognize.
16852 Changes in version 0.1.1.23 - 2006-07-30
16854 - Fast Tor servers, especially exit nodes, were triggering asserts
16855 due to a bug in handling the list of pending DNS resolves. Some
16856 bugs still remain here; we're hunting them.
16857 - Entry guards could crash clients by sending unexpected input.
16858 - More fixes on reachability testing: if you find yourself reachable,
16859 then don't ever make any client requests (so you stop predicting
16860 circuits), then hup or have your clock jump, then later your IP
16861 changes, you won't think circuits are working, so you won't try to
16862 test reachability, so you won't publish.
16865 - Avoid a crash if the controller does a resetconf firewallports
16866 and then a setconf fascistfirewall=1.
16867 - Avoid an integer underflow when the dir authority decides whether
16868 a router is stable: we might wrongly label it stable, and compute
16869 a slightly wrong median stability, when a descriptor is published
16871 - Fix a place where we might trigger an assert if we can't build our
16872 own server descriptor yet.
16875 Changes in version 0.1.1.22 - 2006-07-05
16877 - Fix a big bug that was causing servers to not find themselves
16878 reachable if they changed IP addresses. Since only 0.1.1.22+
16879 servers can do reachability testing correctly, now we automatically
16880 make sure to test via one of these.
16881 - Fix to allow clients and mirrors to learn directory info from
16882 descriptor downloads that get cut off partway through.
16883 - Directory authorities had a bug in deciding if a newly published
16884 descriptor was novel enough to make everybody want a copy -- a few
16885 servers seem to be publishing new descriptors many times a minute.
16887 - Fix a rare bug that was causing some servers to complain about
16888 "closing wedged cpuworkers" and skip some circuit create requests.
16889 - Make the Exit flag in directory status documents actually work.
16892 Changes in version 0.1.1.21 - 2006-06-10
16893 o Crash and assert fixes from 0.1.1.20:
16894 - Fix a rare crash on Tor servers that have enabled hibernation.
16895 - Fix a seg fault on startup for Tor networks that use only one
16896 directory authority.
16897 - Fix an assert from a race condition that occurs on Tor servers
16898 while exiting, where various threads are trying to log that they're
16899 exiting, and delete the logs, at the same time.
16900 - Make our unit tests pass again on certain obscure platforms.
16903 - Add support for building SUSE RPM packages.
16904 - Speed up initial bootstrapping for clients: if we are making our
16905 first ever connection to any entry guard, then don't mark it down
16907 - When only one Tor server in the network is labelled as a guard,
16908 and we've already picked him, we would cycle endlessly picking him
16909 again, being unhappy about it, etc. Now we specifically exclude
16910 current guards when picking a new guard.
16911 - Servers send create cells more reliably after the TLS connection
16912 is established: we were sometimes forgetting to send half of them
16913 when we had more than one pending.
16914 - If we get a create cell that asks us to extend somewhere, but the
16915 Tor server there doesn't match the expected digest, we now send
16916 a destroy cell back, rather than silently doing nothing.
16917 - Make options->RedirectExit work again.
16918 - Make cookie authentication for the controller work again.
16919 - Stop being picky about unusual characters in the arguments to
16920 mapaddress. It's none of our business.
16921 - Add a new config option "TestVia" that lets you specify preferred
16922 middle hops to use for test circuits. Perhaps this will let me
16923 debug the reachability problems better.
16925 o Log / documentation fixes:
16926 - If we're a server and some peer has a broken TLS certificate, don't
16927 log about it unless ProtocolWarnings is set, i.e., we want to hear
16928 about protocol violations by others.
16929 - Fix spelling of VirtualAddrNetwork in man page.
16930 - Add a better explanation at the top of the autogenerated torrc file
16931 about what happened to our old torrc.
16934 Changes in version 0.1.1.20 - 2006-05-23
16935 o Crash and assert fixes from 0.1.0.17:
16936 - Fix assert bug in close_logs() on exit: when we close and delete
16937 logs, remove them all from the global "logfiles" list.
16938 - Fix an assert error when we're out of space in the connection_list
16939 and we try to post a hidden service descriptor (reported by Peter
16941 - Fix a rare assert error when we've tried all intro points for
16942 a hidden service and we try fetching the service descriptor again:
16943 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
16944 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
16945 out and refuse the setconf if it would fail.
16946 - If you specify a relative torrc path and you set RunAsDaemon in
16947 your torrc, then it chdir()'s to the new directory. If you then
16948 HUP, it tries to load the new torrc location, fails, and exits.
16949 The fix: no longer allow a relative path to torrc when using -f.
16950 - Check for integer overflows in more places, when adding elements
16951 to smartlists. This could possibly prevent a buffer overflow
16952 on malicious huge inputs.
16954 o Security fixes, major:
16955 - When we're printing strings from the network, don't try to print
16956 non-printable characters. Now we're safer against shell escape
16957 sequence exploits, and also against attacks to fool users into
16958 misreading their logs.
16959 - Implement entry guards: automatically choose a handful of entry
16960 nodes and stick with them for all circuits. Only pick new guards
16961 when the ones you have are unsuitable, and if the old guards
16962 become suitable again, switch back. This will increase security
16963 dramatically against certain end-point attacks. The EntryNodes
16964 config option now provides some hints about which entry guards you
16965 want to use most; and StrictEntryNodes means to only use those.
16966 Fixes CVE-2006-0414.
16967 - Implement exit enclaves: if we know an IP address for the
16968 destination, and there's a running Tor server at that address
16969 which allows exit to the destination, then extend the circuit to
16970 that exit first. This provides end-to-end encryption and end-to-end
16971 authentication. Also, if the user wants a .exit address or enclave,
16972 use 4 hops rather than 3, and cannibalize a general circ for it
16974 - Obey our firewall options more faithfully:
16975 . If we can't get to a dirserver directly, try going via Tor.
16976 . Don't ever try to connect (as a client) to a place our
16977 firewall options forbid.
16978 . If we specify a proxy and also firewall options, obey the
16979 firewall options even when we're using the proxy: some proxies
16980 can only proxy to certain destinations.
16981 - Make clients regenerate their keys when their IP address changes.
16982 - For the OS X package's modified privoxy config file, comment
16983 out the "logfile" line so we don't log everything passed
16985 - Our TLS handshakes were generating a single public/private
16986 keypair for the TLS context, rather than making a new one for
16987 each new connection. Oops. (But we were still rotating them
16988 periodically, so it's not so bad.)
16989 - When we were cannibalizing a circuit with a particular exit
16990 node in mind, we weren't checking to see if that exit node was
16991 already present earlier in the circuit. Now we are.
16992 - Require server descriptors to list IPv4 addresses -- hostnames
16993 are no longer allowed. This also fixes potential vulnerabilities
16994 to servers providing hostnames as their address and then
16995 preferentially resolving them so they can partition users.
16996 - Our logic to decide if the OR we connected to was the right guy
16997 was brittle and maybe open to a mitm for invalid routers.
16999 o Security fixes, minor:
17000 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
17001 Ian Goldberg can prove things about our handshake protocol more
17003 - Make directory authorities generate a separate "guard" flag to
17004 mean "would make a good entry guard". Clients now honor the
17005 is_guard flag rather than looking at is_fast or is_stable.
17006 - Try to list MyFamily elements by key, not by nickname, and warn
17007 if we've not heard of a server.
17008 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17009 OpenSSL. Also, reseed our entropy every hour, not just at
17010 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
17011 - Refuse server descriptors where the fingerprint line doesn't match
17012 the included identity key. Tor doesn't care, but other apps (and
17013 humans) might actually be trusting the fingerprint line.
17014 - We used to kill the circuit when we receive a relay command we
17015 don't recognize. Now we just drop that cell.
17016 - Fix a bug found by Lasse Overlier: when we were making internal
17017 circuits (intended to be cannibalized later for rendezvous and
17018 introduction circuits), we were picking them so that they had
17019 useful exit nodes. There was no need for this, and it actually
17020 aids some statistical attacks.
17021 - Start treating internal circuits and exit circuits separately.
17022 It's important to keep them separate because internal circuits
17023 have their last hops picked like middle hops, rather than like
17024 exit hops. So exiting on them will break the user's expectations.
17025 - Fix a possible way to DoS dirservers.
17026 - When the client asked for a rendezvous port that the hidden
17027 service didn't want to provide, we were sending an IP address
17028 back along with the end cell. Fortunately, it was zero. But stop
17031 o Packaging improvements:
17032 - Implement --with-libevent-dir option to ./configure. Improve
17033 search techniques to find libevent, and use those for openssl too.
17034 - Fix a couple of bugs in OpenSSL detection. Deal better when
17035 there are multiple SSLs installed with different versions.
17036 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17037 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
17039 - Make unit tests (and other invocations that aren't the real Tor)
17040 run without launching listeners, creating subdirectories, and so on.
17041 - The OS X installer was adding a symlink for tor_resolve but
17042 the binary was called tor-resolve (reported by Thomas Hardly).
17043 - Now we can target arch and OS in rpm builds (contributed by
17044 Phobos). Also make the resulting dist-rpm filename match the
17046 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17047 if you log to syslog and want something other than LOG_DAEMON.
17048 - Fix the torify (tsocks) config file to not use Tor for localhost
17050 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17051 tor-doc-server.html, and stylesheet.css in the tarball.
17052 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
17053 They are useless now.
17054 - Add Peter Palfrader's contributed check-tor script. It lets you
17055 easily check whether a given server (referenced by nickname)
17056 is reachable by you.
17057 - Add BSD-style contributed startup script "rc.subr" from Peter
17060 o Directory improvements -- new directory protocol:
17061 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
17062 - Authorities and caches publish individual descriptors (by
17063 digest, by fingerprint, by "all", and by "tell me yours").
17064 - Clients don't download or use the old directory anymore. Now they
17065 download network-statuses from the directory authorities, and
17066 fetch individual server descriptors as needed from mirrors.
17067 - Clients don't download descriptors of non-running servers.
17068 - Download descriptors by digest, not by fingerprint. Caches try to
17069 download all listed digests from authorities; clients try to
17070 download "best" digests from caches. This avoids partitioning
17071 and isolating attacks better.
17072 - Only upload a new server descriptor when options change, 18
17073 hours have passed, uptime is reset, or bandwidth changes a lot.
17074 - Directory authorities silently throw away new descriptors that
17075 haven't changed much if the timestamps are similar. We do this to
17076 tolerate older Tor servers that upload a new descriptor every 15
17077 minutes. (It seemed like a good idea at the time.)
17078 - Clients choose directory servers from the network status lists,
17079 not from their internal list of router descriptors. Now they can
17080 go to caches directly rather than needing to go to authorities
17081 to bootstrap the first set of descriptors.
17082 - When picking a random directory, prefer non-authorities if any
17084 - Add a new flag to network-status indicating whether the server
17085 can answer v2 directory requests too.
17086 - Directory mirrors now cache up to 16 unrecognized network-status
17087 docs, so new directory authorities will be cached too.
17088 - Stop parsing, storing, or using running-routers output (but
17089 mirrors still cache and serve it).
17090 - Clients consider a threshold of "versioning" directory authorities
17091 before deciding whether to warn the user that he's obsolete.
17092 - Authorities publish separate sorted lists of recommended versions
17093 for clients and for servers.
17094 - Change DirServers config line to note which dirs are v1 authorities.
17095 - Put nicknames on the DirServer line, so we can refer to them
17096 without requiring all our users to memorize their IP addresses.
17097 - Remove option when getting directory cache to see whether they
17098 support running-routers; they all do now. Replace it with one
17099 to see whether caches support v2 stuff.
17100 - Stop listing down or invalid nodes in the v1 directory. This
17101 reduces its bulk by about 1/3, and reduces load on mirrors.
17102 - Mirrors no longer cache the v1 directory as often.
17103 - If we as a directory mirror don't know of any v1 directory
17104 authorities, then don't try to cache any v1 directories.
17106 o Other directory improvements:
17107 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
17108 fifth authoritative directory servers.
17109 - Directory authorities no longer require an open connection from
17110 a server to consider him "reachable". We need this change because
17111 when we add new directory authorities, old servers won't know not
17112 to hang up on them.
17113 - Dir authorities now do their own external reachability testing
17114 of each server, and only list as running the ones they found to
17115 be reachable. We also send back warnings to the server's logs if
17116 it uploads a descriptor that we already believe is unreachable.
17117 - Spread the directory authorities' reachability testing over the
17118 entire testing interval, so we don't try to do 500 TLS's at once
17120 - Make the "stable" router flag in network-status be the median of
17121 the uptimes of running valid servers, and make clients pay
17122 attention to the network-status flags. Thus the cutoff adapts
17123 to the stability of the network as a whole, making IRC, IM, etc
17124 connections more reliable.
17125 - Make the v2 dir's "Fast" flag based on relative capacity, just
17126 like "Stable" is based on median uptime. Name everything in the
17127 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17128 - Retry directory requests if we fail to get an answer we like
17129 from a given dirserver (we were retrying before, but only if
17130 we fail to connect).
17131 - Return a robots.txt on our dirport to discourage google indexing.
17133 o Controller protocol improvements:
17134 - Revised controller protocol (version 1) that uses ascii rather
17135 than binary: tor/doc/control-spec.txt. Add supporting libraries
17136 in python and java and c# so you can use the controller from your
17137 applications without caring how our protocol works.
17138 - Allow the DEBUG controller event to work again. Mark certain log
17139 entries as "don't tell this to controllers", so we avoid cycles.
17140 - New controller function "getinfo accounting", to ask how
17141 many bytes we've used in this time period.
17142 - Add a "resetconf" command so you can set config options like
17143 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17144 a config option in the torrc with no value, then it clears it
17145 entirely (rather than setting it to its default).
17146 - Add a "getinfo config-file" to tell us where torrc is. Also
17147 expose guard nodes, config options/names.
17148 - Add a "quit" command (when when using the controller manually).
17149 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
17150 stop using any currently-dirty circuits for new streams, so we
17151 don't link new actions to old actions. This also occurs on HUP
17152 or "signal reload".
17153 - If we would close a stream early (e.g. it asks for a .exit that
17154 we know would refuse it) but the LeaveStreamsUnattached config
17155 option is set by the controller, then don't close it.
17156 - Add a new controller event type "authdir_newdescs" that allows
17157 controllers to get all server descriptors that were uploaded to
17158 a router in its role as directory authority.
17159 - New controller option "getinfo desc/all-recent" to fetch the
17160 latest server descriptor for every router that Tor knows about.
17161 - Fix the controller's "attachstream 0" command to treat conn like
17162 it just connected, doing address remapping, handling .exit and
17163 .onion idioms, and so on. Now we're more uniform in making sure
17164 that the controller hears about new and closing connections.
17165 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
17166 the controller. Also, rotate dns and cpu workers if the controller
17167 changes options that will affect them; and initialize the dns
17168 worker cache tree whether or not we start out as a server.
17169 - Add a new circuit purpose 'controller' to let the controller ask
17170 for a circuit that Tor won't try to use. Extend the "extendcircuit"
17171 controller command to let you specify the purpose if you're starting
17172 a new circuit. Add a new "setcircuitpurpose" controller command to
17173 let you change a circuit's purpose after it's been created.
17174 - Let the controller ask for "getinfo dir/server/foo" so it can ask
17175 directly rather than connecting to the dir port. "getinfo
17176 dir/status/foo" also works, but currently only if your DirPort
17178 - Let the controller tell us about certain router descriptors
17179 that it doesn't want Tor to use in circuits. Implement
17180 "setrouterpurpose" and modify "+postdescriptor" to do this.
17181 - If the controller's *setconf commands fail, collect an error
17182 message in a string and hand it back to the controller -- don't
17183 just tell them to go read their logs.
17185 o Scalability, resource management, and performance:
17186 - Fix a major load balance bug: we were round-robin reading in 16 KB
17187 chunks, and servers with bandwidthrate of 20 KB, while downloading
17188 a 600 KB directory, would starve their other connections. Now we
17189 try to be a bit more fair.
17190 - Be more conservative about whether to advertise our DirPort.
17191 The main change is to not advertise if we're running at capacity
17192 and either a) we could hibernate ever or b) our capacity is low
17193 and we're using a default DirPort.
17194 - We weren't cannibalizing circuits correctly for
17195 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17196 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17197 build those from scratch. This should make hidden services faster.
17198 - Predict required circuits better, with an eye toward making hidden
17199 services faster on the service end.
17200 - Compress exit policies even more: look for duplicate lines and
17202 - Generate 18.0.0.0/8 address policy format in descs when we can;
17203 warn when the mask is not reducible to a bit-prefix.
17204 - There used to be two ways to specify your listening ports in a
17205 server descriptor: on the "router" line and with a separate "ports"
17206 line. Remove support for the "ports" line.
17207 - Reduce memory requirements in our structs by changing the order
17208 of fields. Replace balanced trees with hash tables. Inline
17209 bottleneck smartlist functions. Add a "Map from digest to void*"
17210 abstraction so we can do less hex encoding/decoding, and use it
17211 in router_get_by_digest(). Many other CPU and memory improvements.
17212 - Allow tor_gzip_uncompress to extract as much as possible from
17213 truncated compressed data. Try to extract as many
17214 descriptors as possible from truncated http responses (when
17215 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
17216 - Make circ->onionskin a pointer, not a static array. moria2 was using
17217 125000 circuit_t's after it had been up for a few weeks, which
17218 translates to 20+ megs of wasted space.
17219 - The private half of our EDH handshake keys are now chosen out
17220 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17221 - Stop doing the complex voodoo overkill checking for insecure
17222 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
17223 - Do round-robin writes for TLS of at most 16 kB per write. This
17224 might be more fair on loaded Tor servers.
17225 - Do not use unaligned memory access on alpha, mips, or mipsel.
17226 It *works*, but is very slow, so we treat them as if it doesn't.
17228 o Other bugfixes and improvements:
17229 - Start storing useful information to $DATADIR/state, so we can
17230 remember things across invocations of Tor. Retain unrecognized
17231 lines so we can be forward-compatible, and write a TorVersion line
17232 so we can be backward-compatible.
17233 - If ORPort is set, Address is not explicitly set, and our hostname
17234 resolves to a private IP address, try to use an interface address
17235 if it has a public address. Now Windows machines that think of
17236 themselves as localhost can guess their address.
17237 - Regenerate our local descriptor if it's dirty and we try to use
17238 it locally (e.g. if it changes during reachability detection).
17239 This was causing some Tor servers to keep publishing the same
17240 initial descriptor forever.
17241 - Tor servers with dynamic IP addresses were needing to wait 18
17242 hours before they could start doing reachability testing using
17243 the new IP address and ports. This is because they were using
17244 the internal descriptor to learn what to test, yet they were only
17245 rebuilding the descriptor once they decided they were reachable.
17246 - It turns out we couldn't bootstrap a network since we added
17247 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17248 has never gone down. Add an AssumeReachable config option to let
17249 servers and authorities bootstrap. When we're trying to build a
17250 high-uptime or high-bandwidth circuit but there aren't enough
17251 suitable servers, try being less picky rather than simply failing.
17252 - Newly bootstrapped Tor networks couldn't establish hidden service
17253 circuits until they had nodes with high uptime. Be more tolerant.
17254 - Really busy servers were keeping enough circuits open on stable
17255 connections that they were wrapping around the circuit_id
17256 space. (It's only two bytes.) This exposed a bug where we would
17257 feel free to reuse a circuit_id even if it still exists but has
17258 been marked for close. Try to fix this bug. Some bug remains.
17259 - When we fail to bind or listen on an incoming or outgoing
17260 socket, we now close it before refusing, rather than just
17261 leaking it. (Thanks to Peter Palfrader for finding.)
17262 - Fix a file descriptor leak in start_daemon().
17263 - On Windows, you can't always reopen a port right after you've
17264 closed it. So change retry_listeners() to only close and re-open
17265 ports that have changed.
17266 - Workaround a problem with some http proxies that refuse GET
17267 requests that specify "Content-Length: 0". Reported by Adrian.
17268 - Recover better from TCP connections to Tor servers that are
17269 broken but don't tell you (it happens!); and rotate TLS
17270 connections once a week.
17271 - Fix a scary-looking but apparently harmless bug where circuits
17272 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17273 servers, and never switch to state CIRCUIT_STATE_OPEN.
17274 - Check for even more Windows version flags when writing the platform
17275 string in server descriptors, and note any we don't recognize.
17276 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
17277 get a better idea of why their circuits failed. Not used yet.
17278 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17279 We don't use them yet, but maybe one day our DNS resolver will be
17280 able to discover them.
17281 - Let people type "tor --install" as well as "tor -install" when they
17282 want to make it an NT service.
17283 - Looks like we were never delivering deflated (i.e. compressed)
17284 running-routers lists, even when asked. Oops.
17285 - We were leaking some memory every time the client changed IPs.
17286 - Clean up more of the OpenSSL memory when exiting, so we can detect
17287 memory leaks better.
17288 - Never call free() on tor_malloc()d memory. This will help us
17289 use dmalloc to detect memory leaks.
17290 - Some Tor servers process billions of cells per day. These
17291 statistics are now uint64_t's.
17292 - Check [X-]Forwarded-For headers in HTTP requests when generating
17293 log messages. This lets people run dirservers (and caches) behind
17294 Apache but still know which IP addresses are causing warnings.
17295 - Fix minor integer overflow in calculating when we expect to use up
17296 our bandwidth allocation before hibernating.
17297 - Lower the minimum required number of file descriptors to 1000,
17298 so we can have some overhead for Valgrind on Linux, where the
17299 default ulimit -n is 1024.
17300 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17301 and its existence is confusing some users.
17303 o Config option fixes:
17304 - Add a new config option ExitPolicyRejectPrivate which defaults
17305 to on. Now all exit policies will begin with rejecting private
17306 addresses, unless the server operator explicitly turns it off.
17307 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
17308 - Add new ReachableORAddresses and ReachableDirAddresses options
17309 that understand address policies. FascistFirewall is now a synonym
17310 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
17311 - Start calling it FooListenAddress rather than FooBindAddress,
17312 since few of our users know what it means to bind an address
17314 - If the user gave Tor an odd number of command-line arguments,
17315 we were silently ignoring the last one. Now we complain and fail.
17316 This wins the oldest-bug prize -- this bug has been present since
17317 November 2002, as released in Tor 0.0.0.
17318 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17319 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17320 it would silently ignore the 6668.
17321 - If we get a linelist or linelist_s config option from the torrc,
17322 e.g. ExitPolicy, and it has no value, warn and skip rather than
17323 silently resetting it to its default.
17324 - Setconf was appending items to linelists, not clearing them.
17325 - Add MyFamily to torrc.sample in the server section, so operators
17326 will be more likely to learn that it exists.
17327 - Make ContactInfo mandatory for authoritative directory servers.
17328 - MaxConn has been obsolete for a while now. Document the ConnLimit
17329 config option, which is a *minimum* number of file descriptors
17330 that must be available else Tor refuses to start.
17331 - Get rid of IgnoreVersion undocumented config option, and make us
17332 only warn, never exit, when we're running an obsolete version.
17333 - Make MonthlyAccountingStart config option truly obsolete now.
17334 - Correct the man page entry on TrackHostExitsExpire.
17335 - Let directory authorities start even if they don't specify an
17336 Address config option.
17337 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
17338 reflect the updated flags in our v2 dir protocol.
17340 o Config option features:
17341 - Add a new config option FastFirstHopPK (on by default) so clients
17342 do a trivial crypto handshake for their first hop, since TLS has
17343 already taken care of confidentiality and authentication.
17344 - Let the user set ControlListenAddress in the torrc. This can be
17345 dangerous, but there are some cases (like a secured LAN) where it
17347 - New config options to help controllers: FetchServerDescriptors
17348 and FetchHidServDescriptors for whether to fetch server
17349 info and hidserv info or let the controller do it, and
17350 PublishServerDescriptor and PublishHidServDescriptors.
17351 - Also let the controller set the __AllDirActionsPrivate config
17352 option if you want all directory fetches/publishes to happen via
17353 Tor (it assumes your controller bootstraps your circuits).
17354 - Add "HardwareAccel" config option: support for crypto hardware
17355 accelerators via OpenSSL. Off by default, until we find somebody
17356 smart who can test it for us. (It appears to produce seg faults
17357 in at least some cases.)
17358 - New config option "AuthDirRejectUnlisted" for directory authorities
17359 as a panic button: if we get flooded with unusable servers we can
17360 revert to only listing servers in the approved-routers file.
17361 - Directory authorities can now reject/invalidate by key and IP,
17362 with the config options "AuthDirInvalid" and "AuthDirReject", or
17363 by marking a fingerprint as "!reject" or "!invalid" (as its
17364 nickname) in the approved-routers file. This is useful since
17365 currently we automatically list servers as running and usable
17366 even if we know they're jerks.
17367 - Add a new config option TestSocks so people can see whether their
17368 applications are using socks4, socks4a, socks5-with-ip, or
17369 socks5-with-fqdn. This way they don't have to keep mucking
17370 with tcpdump and wondering if something got cached somewhere.
17371 - Add "private:*" as an alias in configuration for policies. Now
17372 you can simplify your exit policy rather than needing to list
17373 every single internal or nonroutable network space.
17374 - Accept "private:*" in routerdesc exit policies; not generated yet
17375 because older Tors do not understand it.
17376 - Add configuration option "V1AuthoritativeDirectory 1" which
17377 moria1, moria2, and tor26 have set.
17378 - Implement an option, VirtualAddrMask, to set which addresses
17379 get handed out in response to mapaddress requests. This works
17380 around a bug in tsocks where 127.0.0.0/8 is never socksified.
17381 - Add a new config option FetchUselessDescriptors, off by default,
17382 for when you plan to run "exitlist" on your client and you want
17383 to know about even the non-running descriptors.
17384 - SocksTimeout: How long do we let a socks connection wait
17385 unattached before we fail it?
17386 - CircuitBuildTimeout: Cull non-open circuits that were born
17387 at least this many seconds ago.
17388 - CircuitIdleTimeout: Cull open clean circuits that were born
17389 at least this many seconds ago.
17390 - New config option SafeSocks to reject all application connections
17391 using unsafe socks protocols. Defaults to off.
17393 o Improved and clearer log messages:
17394 - Reduce clutter in server logs. We're going to try to make
17395 them actually usable now. New config option ProtocolWarnings that
17396 lets you hear about how _other Tors_ are breaking the protocol. Off
17398 - Divide log messages into logging domains. Once we put some sort
17399 of interface on this, it will let people looking at more verbose
17400 log levels specify the topics they want to hear more about.
17401 - Log server fingerprint on startup, so new server operators don't
17402 have to go hunting around their filesystem for it.
17403 - Provide dire warnings to any users who set DirServer manually;
17404 move it out of torrc.sample and into torrc.complete.
17405 - Make the log message less scary when all the dirservers are
17406 temporarily unreachable.
17407 - When tor_socketpair() fails in Windows, give a reasonable
17408 Windows-style errno back.
17409 - Improve tor_gettimeofday() granularity on windows.
17410 - We were printing the number of idle dns workers incorrectly when
17412 - Handle duplicate lines in approved-routers files without warning.
17413 - We were whining about using socks4 or socks5-with-local-lookup
17414 even when it's an IP address in the "virtual" range we designed
17415 exactly for this case.
17416 - Check for named servers when looking them up by nickname;
17417 warn when we're calling a non-named server by its nickname;
17418 don't warn twice about the same name.
17419 - Downgrade the dirserver log messages when whining about
17421 - Correct "your server is reachable" log entries to indicate that
17422 it was self-testing that told us so.
17423 - If we're trying to be a Tor server and running Windows 95/98/ME
17424 as a server, explain that we'll likely crash.
17425 - Provide a more useful warn message when our onion queue gets full:
17426 the CPU is too slow or the exit policy is too liberal.
17427 - Don't warn when we receive a 503 from a dirserver/cache -- this
17428 will pave the way for them being able to refuse if they're busy.
17429 - When we fail to bind a listener, try to provide a more useful
17430 log message: e.g., "Is Tor already running?"
17431 - Only start testing reachability once we've established a
17432 circuit. This will make startup on dir authorities less noisy.
17433 - Don't try to upload hidden service descriptors until we have
17434 established a circuit.
17435 - Tor didn't warn when it failed to open a log file.
17436 - Warn when listening on a public address for socks. We suspect a
17437 lot of people are setting themselves up as open socks proxies,
17438 and they have no idea that jerks on the Internet are using them,
17439 since they simply proxy the traffic into the Tor network.
17440 - Give a useful message when people run Tor as the wrong user,
17441 rather than telling them to start chowning random directories.
17442 - Fix a harmless bug that was causing Tor servers to log
17443 "Got an end because of misc error, but we're not an AP. Closing."
17444 - Fix wrong log message when you add a "HiddenServiceNodes" config
17445 line without any HiddenServiceDir line (reported by Chris Thomas).
17446 - Directory authorities now stop whining so loudly about bad
17447 descriptors that they fetch from other dirservers. So when there's
17448 a log complaint, it's for sure from a freshly uploaded descriptor.
17449 - When logging via syslog, include the pid whenever we provide
17450 a log entry. Suggested by Todd Fries.
17451 - When we're shutting down and we do something like try to post a
17452 server descriptor or rendezvous descriptor, don't complain that
17453 we seem to be unreachable. Of course we are, we're shutting down.
17454 - Change log line for unreachability to explicitly suggest /etc/hosts
17455 as the culprit. Also make it clearer what IP address and ports we're
17456 testing for reachability.
17457 - Put quotes around user-supplied strings when logging so users are
17458 more likely to realize if they add bad characters (like quotes)
17460 - NT service patch from Matt Edman to improve error messages on Win32.
17463 Changes in version 0.1.0.17 - 2006-02-17
17464 o Crash bugfixes on 0.1.0.x:
17465 - When servers with a non-zero DirPort came out of hibernation,
17466 sometimes they would trigger an assert.
17468 o Other important bugfixes:
17469 - On platforms that don't have getrlimit (like Windows), we were
17470 artificially constraining ourselves to a max of 1024
17471 connections. Now just assume that we can handle as many as 15000
17472 connections. Hopefully this won't cause other problems.
17474 o Backported features:
17475 - When we're a server, a client asks for an old-style directory,
17476 and our write bucket is empty, don't give it to him. This way
17477 small servers can continue to serve the directory *sometimes*,
17478 without getting overloaded.
17479 - Whenever you get a 503 in response to a directory fetch, try
17480 once more. This will become important once servers start sending
17481 503's whenever they feel busy.
17482 - Fetch a new directory every 120 minutes, not every 40 minutes.
17483 Now that we have hundreds of thousands of users running the old
17484 directory algorithm, it's starting to hurt a lot.
17485 - Bump up the period for forcing a hidden service descriptor upload
17486 from 20 minutes to 1 hour.
17489 Changes in version 0.1.0.16 - 2006-01-02
17490 o Crash bugfixes on 0.1.0.x:
17491 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17492 corrupting the heap, losing FDs, or crashing when we need to resize
17493 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17494 - It turns out sparc64 platforms crash on unaligned memory access
17495 too -- so detect and avoid this.
17496 - Handle truncated compressed data correctly (by detecting it and
17498 - Fix possible-but-unlikely free(NULL) in control.c.
17499 - When we were closing connections, there was a rare case that
17500 stomped on memory, triggering seg faults and asserts.
17501 - Avoid potential infinite recursion when building a descriptor. (We
17502 don't know that it ever happened, but better to fix it anyway.)
17503 - We were neglecting to unlink marked circuits from soon-to-close OR
17504 connections, which caused some rare scribbling on freed memory.
17505 - Fix a memory stomping race bug when closing the joining point of two
17506 rendezvous circuits.
17507 - Fix an assert in time parsing found by Steven Murdoch.
17509 o Other bugfixes on 0.1.0.x:
17510 - When we're doing reachability testing, provide more useful log
17511 messages so the operator knows what to expect.
17512 - Do not check whether DirPort is reachable when we are suppressing
17513 advertising it because of hibernation.
17514 - When building with -static or on Solaris, we sometimes needed -ldl.
17515 - One of the dirservers (tor26) changed its IP address.
17516 - When we're deciding whether a stream has enough circuits around
17517 that can handle it, count the freshly dirty ones and not the ones
17518 that are so dirty they won't be able to handle it.
17519 - When we're expiring old circuits, we had a logic error that caused
17520 us to close new rendezvous circuits rather than old ones.
17521 - Give a more helpful log message when you try to change ORPort via
17522 the controller: you should upgrade Tor if you want that to work.
17523 - We were failing to parse Tor versions that start with "Tor ".
17524 - Tolerate faulty streams better: when a stream fails for reason
17525 exitpolicy, stop assuming that the router is lying about his exit
17526 policy. When a stream fails for reason misc, allow it to retry just
17527 as if it was resolvefailed. When a stream has failed three times,
17528 reset its failure count so we can try again and get all three tries.
17531 Changes in version 0.1.0.15 - 2005-09-23
17532 o Bugfixes on 0.1.0.x:
17533 - Reject ports 465 and 587 (spam targets) in default exit policy.
17534 - Don't crash when we don't have any spare file descriptors and we
17535 try to spawn a dns or cpu worker.
17536 - Get rid of IgnoreVersion undocumented config option, and make us
17537 only warn, never exit, when we're running an obsolete version.
17538 - Don't try to print a null string when your server finds itself to
17539 be unreachable and the Address config option is empty.
17540 - Make the numbers in read-history and write-history into uint64s,
17541 so they don't overflow and publish negatives in the descriptor.
17542 - Fix a minor memory leak in smartlist_string_remove().
17543 - We were only allowing ourselves to upload a server descriptor at
17544 most every 20 minutes, even if it changed earlier than that.
17545 - Clean up log entries that pointed to old URLs.
17548 Changes in version 0.1.0.14 - 2005-08-08
17549 o Bugfixes on 0.1.0.x:
17550 - Fix the other half of the bug with crypto handshakes
17552 - Fix an assert trigger if you send a 'signal term' via the
17553 controller when it's listening for 'event info' messages.
17556 Changes in version 0.1.0.13 - 2005-08-04
17557 o Bugfixes on 0.1.0.x:
17558 - Fix a critical bug in the security of our crypto handshakes.
17559 - Fix a size_t underflow in smartlist_join_strings2() that made
17560 it do bad things when you hand it an empty smartlist.
17561 - Fix Windows installer to ship Tor license (thanks to Aphex for
17562 pointing out this oversight) and put a link to the doc directory
17564 - Explicitly set no-unaligned-access for sparc: it turns out the
17565 new gcc's let you compile broken code, but that doesn't make it
17569 Changes in version 0.1.0.12 - 2005-07-18
17570 o New directory servers:
17571 - tor26 has changed IP address.
17573 o Bugfixes on 0.1.0.x:
17574 - Fix a possible double-free in tor_gzip_uncompress().
17575 - When --disable-threads is set, do not search for or link against
17576 pthreads libraries.
17577 - Don't trigger an assert if an authoritative directory server
17578 claims its dirport is 0.
17579 - Fix bug with removing Tor as an NT service: some people were
17580 getting "The service did not return an error." Thanks to Matt
17584 Changes in version 0.1.0.11 - 2005-06-30
17585 o Bugfixes on 0.1.0.x:
17586 - Fix major security bug: servers were disregarding their
17587 exit policies if clients behaved unexpectedly.
17588 - Make OS X init script check for missing argument, so we don't
17589 confuse users who invoke it incorrectly.
17590 - Fix a seg fault in "tor --hash-password foo".
17591 - The MAPADDRESS control command was broken.
17594 Changes in version 0.1.0.10 - 2005-06-14
17596 - Make NT services work and start on startup on Win32 (based on
17597 patch by Matt Edman). See the FAQ entry for details.
17598 - Make 'platform' string in descriptor more accurate for Win32
17599 servers, so it's not just "unknown platform".
17600 - REUSEADDR on normal platforms means you can rebind to the port
17601 right after somebody else has let it go. But REUSEADDR on Win32
17602 means you can bind to the port _even when somebody else already
17603 has it bound_! So, don't do that on Win32.
17604 - Clean up the log messages when starting on Win32 with no config
17606 - Allow seeding the RNG on Win32 even when you're not running as
17607 Administrator. If seeding the RNG on Win32 fails, quit.
17609 o Assert / crash bugs:
17610 - Refuse relay cells that claim to have a length larger than the
17611 maximum allowed. This prevents a potential attack that could read
17612 arbitrary memory (e.g. keys) from an exit server's process
17614 - If unofficial Tor clients connect and send weird TLS certs, our
17615 Tor server triggers an assert. Stop asserting, and start handling
17616 TLS errors better in other situations too.
17617 - Fix a race condition that can trigger an assert when we have a
17618 pending create cell and an OR connection attempt fails.
17621 - Use pthreads for worker processes rather than forking. This was
17622 forced because when we forked, we ended up wasting a lot of
17623 duplicate ram over time.
17624 - Also switch to foo_r versions of some library calls to allow
17625 reentry and threadsafeness.
17626 - Implement --disable-threads configure option. Disable threads on
17627 netbsd and openbsd by default, because they have no reentrant
17628 resolver functions (!), and on solaris since it has other
17630 - Fix possible bug on threading platforms (e.g. win32) which was
17631 leaking a file descriptor whenever a cpuworker or dnsworker died.
17632 - Fix a minor memory leak when somebody establishes an introduction
17633 point at your Tor server.
17634 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
17636 - Add ./configure --with-dmalloc option, to track memory leaks.
17637 - And try to free all memory on closing, so we can detect what
17640 o Protocol correctness:
17641 - When we've connected to an OR and handshaked but didn't like
17642 the result, we were closing the conn without sending destroy
17643 cells back for pending circuits. Now send those destroys.
17644 - Start sending 'truncated' cells back rather than destroy cells
17645 if the circuit closes in front of you. This means we won't have
17646 to abandon partially built circuits.
17647 - Handle changed router status correctly when dirserver reloads
17648 fingerprint file. We used to be dropping all unverified descriptors
17649 right then. The bug was hidden because we would immediately
17650 fetch a directory from another dirserver, which would include the
17651 descriptors we just dropped.
17652 - Revise tor-spec to add more/better stream end reasons.
17653 - Revise all calls to connection_edge_end to avoid sending 'misc',
17654 and to take errno into account where possible.
17655 - Client now retries when streams end early for 'hibernating' or
17656 'resource limit' reasons, rather than failing them.
17657 - Try to be more zealous about calling connection_edge_end when
17658 things go bad with edge conns in connection.c.
17660 o Robustness improvements:
17661 - Better handling for heterogeneous / unreliable nodes:
17662 - Annotate circuits with whether they aim to contain high uptime
17663 nodes and/or high capacity nodes. When building circuits, choose
17665 - This means that every single node in an intro rend circuit,
17666 not just the last one, will have a minimum uptime.
17667 - New config option LongLivedPorts to indicate application streams
17668 that will want high uptime circuits.
17669 - Servers reset uptime when a dir fetch entirely fails. This
17670 hopefully reflects stability of the server's network connectivity.
17671 - If somebody starts his tor server in Jan 2004 and then fixes his
17672 clock, don't make his published uptime be a year.
17673 - Reset published uptime when we wake up from hibernation.
17674 - Introduce a notion of 'internal' circs, which are chosen without
17675 regard to the exit policy of the last hop. Intro and rendezvous
17676 circs must be internal circs, to avoid leaking information. Resolve
17677 and connect streams can use internal circs if they want.
17678 - New circuit pooling algorithm: keep track of what destination ports
17679 we've used recently (start out assuming we'll want to use 80), and
17680 make sure to have enough circs around to satisfy these ports. Also
17681 make sure to have 2 internal circs around if we've required internal
17682 circs lately (and with high uptime if we've seen that lately too).
17683 - Turn addr_policy_compare from a tristate to a quadstate; this should
17684 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17685 for google.com" problem.
17686 - When a client asks us for a dir mirror and we don't have one,
17687 launch an attempt to get a fresh one.
17688 - First cut at support for "create-fast" cells. Clients can use
17689 these when extending to their first hop, since the TLS already
17690 provides forward secrecy and authentication. Not enabled on
17693 o Reachability testing.
17694 - Your Tor server will automatically try to see if its ORPort and
17695 DirPort are reachable from the outside, and it won't upload its
17696 descriptor until it decides at least ORPort is reachable (when
17697 DirPort is not yet found reachable, publish it as zero).
17698 - When building testing circs for ORPort testing, use only
17699 high-bandwidth nodes, so fewer circuits fail.
17700 - Notice when our IP changes, and reset stats/uptime/reachability.
17701 - Authdirservers don't do ORPort reachability detection, since
17702 they're in clique mode, so it will be rare to find a server not
17703 already connected to them.
17704 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
17708 - Now we allow two unverified servers with the same nickname
17709 but different keys. But if a nickname is verified, only that
17710 nickname+key are allowed.
17711 - If you're an authdirserver connecting to an address:port,
17712 and it's not the OR you were expecting, forget about that
17713 descriptor. If he *was* the one you were expecting, then forget
17714 about all other descriptors for that address:port.
17715 - Allow servers to publish descriptors from 12 hours in the future.
17716 Corollary: only whine about clock skew from the dirserver if
17717 he's a trusted dirserver (since now even verified servers could
17718 have quite wrong clocks).
17719 - Require servers that use the default dirservers to have public IP
17720 addresses. We have too many servers that are configured with private
17721 IPs and their admins never notice the log entries complaining that
17722 their descriptors are being rejected.
17724 o Efficiency improvements:
17725 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
17726 and /dev/poll), and hopefully work better on Windows too.
17727 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
17728 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
17729 - Find libevent even if it's hiding in /usr/local/ and your
17730 CFLAGS and LDFLAGS don't tell you to look there.
17731 - Be able to link with libevent as a shared library (the default
17732 after 1.0d), even if it's hiding in /usr/local/lib and even
17733 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17734 assuming you're running gcc. Otherwise fail and give a useful
17736 - Switch to a new buffer management algorithm, which tries to avoid
17737 reallocing and copying quite as much. In first tests it looks like
17738 it uses *more* memory on average, but less cpu.
17739 - Switch our internal buffers implementation to use a ring buffer,
17740 to hopefully improve performance for fast servers a lot.
17741 - Reenable the part of the code that tries to flush as soon as an
17742 OR outbuf has a full TLS record available. Perhaps this will make
17743 OR outbufs not grow as huge except in rare cases, thus saving lots
17744 of CPU time plus memory.
17745 - Improve performance for dirservers: stop re-parsing the whole
17746 directory every time you regenerate it.
17747 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17748 it much faster to look up a circuit for each relay cell.
17749 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17750 since they're eating our cpu on exit nodes.
17751 - Stop wasting time doing a case insensitive comparison for every
17752 dns name every time we do any lookup. Canonicalize the names to
17753 lowercase when you first see them.
17756 - Handle unavailable hidden services better. Handle slow or busy
17757 hidden services better.
17758 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17759 circ as necessary, if there are any completed ones lying around
17760 when we try to launch one.
17761 - Make hidden services try to establish a rendezvous for 30 seconds
17762 after fetching the descriptor, rather than for n (where n=3)
17763 attempts to build a circuit.
17764 - Adjust maximum skew and age for rendezvous descriptors: let skew
17765 be 48 hours rather than 90 minutes.
17766 - Reject malformed .onion addresses rather then passing them on as
17767 normal web requests.
17770 - More Tor controller support. See
17771 http://tor.eff.org/doc/control-spec.txt for all the new features,
17772 including signals to emulate unix signals from any platform;
17773 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17774 closestream; closecircuit; etc.
17775 - Encode hashed controller passwords in hex instead of base64,
17776 to make it easier to write controllers.
17777 - Revise control spec and implementation to allow all log messages to
17778 be sent to controller with their severities intact (suggested by
17779 Matt Edman). Disable debug-level logs while delivering a debug-level
17780 log to the controller, to prevent loop. Update TorControl to handle
17781 new log event types.
17783 o New config options/defaults:
17784 - Begin scrubbing sensitive strings from logs by default. Turn off
17785 the config option SafeLogging if you need to do debugging.
17786 - New exit policy: accept most low-numbered ports, rather than
17787 rejecting most low-numbered ports.
17788 - Put a note in the torrc about abuse potential with the default
17790 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17792 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
17793 based on patch from Adam Langley (basic auth only).
17794 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17795 the fast servers that have been joining lately. (Clients are now
17796 willing to load balance over up to 2 MB of advertised bandwidth
17798 - New config option MaxAdvertisedBandwidth which lets you advertise
17799 a low bandwidthrate (to not attract as many circuits) while still
17800 allowing a higher bandwidthrate in reality.
17801 - Require BandwidthRate to be at least 20kB/s for servers.
17802 - Add a NoPublish config option, so you can be a server (e.g. for
17803 testing running Tor servers in other Tor networks) without
17804 publishing your descriptor to the primary dirservers.
17805 - Add a new AddressMap config directive to rewrite incoming socks
17806 addresses. This lets you, for example, declare an implicit
17807 required exit node for certain sites.
17808 - Add a new TrackHostExits config directive to trigger addressmaps
17809 for certain incoming socks addresses -- for sites that break when
17810 your exit keeps changing (based on patch from Mike Perry).
17811 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17812 which describes how often we retry making new circuits if current
17813 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17814 how long we're willing to make use of an already-dirty circuit.
17815 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
17816 a config option "ShutdownWaitLength" (when using kill -INT on
17818 - Fix an edge case in parsing config options: if they say "--"
17819 on the commandline, it's not a config option (thanks weasel).
17820 - New config option DirAllowPrivateAddresses for authdirservers.
17821 Now by default they refuse router descriptors that have non-IP or
17822 private-IP addresses.
17823 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17824 smart" default value: low for servers and high for clients.
17825 - Some people were putting "Address " in their torrc, and they had
17826 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17827 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17828 LOCALSTATEDIR/tor instead.
17829 - Implement --verify-config command-line option to check if your torrc
17830 is valid without actually launching Tor.
17832 o Logging improvements:
17833 - When dirservers refuse a server descriptor, we now log its
17834 contactinfo, platform, and the poster's IP address.
17835 - Only warn once per nickname from add_nickname_list_to_smartlist()
17836 per failure, so an entrynode or exitnode choice that's down won't
17838 - When we're connecting to an OR and he's got a different nickname/key
17839 than we were expecting, only complain loudly if we're an OP or a
17840 dirserver. Complaining loudly to the OR admins just confuses them.
17841 - Whine at you if you're a server and you don't set your contactinfo.
17842 - Warn when exit policy implicitly allows local addresses.
17843 - Give a better warning when some other server advertises an
17844 ORPort that is actually an apache running ssl.
17845 - If we get an incredibly skewed timestamp from a dirserver mirror
17846 that isn't a verified OR, don't warn -- it's probably him that's
17848 - When a dirserver causes you to give a warn, mention which dirserver
17850 - Initialize libevent later in the startup process, so the logs are
17851 already established by the time we start logging libevent warns.
17852 - Use correct errno on win32 if libevent fails.
17853 - Check and warn about known-bad/slow libevent versions.
17854 - Stop warning about sigpipes in the logs. We're going to
17855 pretend that getting these occasionally is normal and fine.
17857 o New contrib scripts:
17858 - New experimental script tor/contrib/exitlist: a simple python
17859 script to parse directories and find Tor nodes that exit to listed
17861 - New experimental script tor/contrib/ExerciseServer.py (needs more
17862 work) that uses the controller interface to build circuits and
17863 fetch pages over them. This will help us bootstrap servers that
17864 have lots of capacity but haven't noticed it yet.
17865 - New experimental script tor/contrib/PathDemo.py (needs more work)
17866 that uses the controller interface to let you choose whole paths
17868 "<hostname>.<path,separated by dots>.<length of path>.path"
17869 - New contributed script "privoxy-tor-toggle" to toggle whether
17870 Privoxy uses Tor. Seems to be configured for Debian by default.
17871 - Have torctl.in/tor.sh.in check for location of su binary (needed
17875 - chdir() to your datadirectory at the *end* of the daemonize process,
17876 not the beginning. This was a problem because the first time you
17877 run tor, if your datadir isn't there, and you have runasdaemon set
17878 to 1, it will try to chdir to it before it tries to create it. Oops.
17879 - Fix several double-mark-for-close bugs, e.g. where we were finding
17880 a conn for a cell even if that conn is already marked for close.
17881 - Stop most cases of hanging up on a socks connection without sending
17883 - Fix a bug in the RPM package: set home directory for _tor to
17884 something more reasonable when first installing.
17885 - Stop putting nodename in the Platform string in server descriptors.
17886 It doesn't actually help, and it is confusing/upsetting some people.
17887 - When using preferred entry or exit nodes, ignore whether the
17888 circuit wants uptime or capacity. They asked for the nodes, they
17890 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17891 artificially capped at 500kB.
17892 - Cache local dns resolves correctly even when they're .exit
17894 - If we're hibernating and we get a SIGINT, exit immediately.
17895 - tor-resolve requests were ignoring .exit if there was a working circuit
17896 they could use instead.
17897 - Pay more attention to the ClientOnly config option.
17898 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
17899 installer screens; and don't put stuff into StartupItems unless
17900 the user asks you to.
17903 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
17904 rather than just rejecting it.
17905 - If our clock jumps forward by 100 seconds or more, assume something
17906 has gone wrong with our network and abandon all not-yet-used circs.
17907 - When an application is using socks5, give him the whole variety of
17908 potential socks5 responses (connect refused, host unreachable, etc),
17909 rather than just "success" or "failure".
17910 - A more sane version numbering system. See
17911 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17912 - Change version parsing logic: a version is "obsolete" if it is not
17913 recommended and (1) there is a newer recommended version in the
17914 same series, or (2) there are no recommended versions in the same
17915 series, but there are some recommended versions in a newer series.
17916 A version is "new" if it is newer than any recommended version in
17918 - Report HTTP reasons to client when getting a response from directory
17919 servers -- so you can actually know what went wrong.
17920 - Reject odd-looking addresses at the client (e.g. addresses that
17921 contain a colon), rather than having the server drop them because
17923 - Stop publishing socksport in the directory, since it's not
17924 actually meant to be public. For compatibility, publish a 0 there
17926 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17927 cookies to disk and doesn't log each web request to disk. (Thanks
17928 to Brett Carrington for pointing this out.)
17929 - Add OSX uninstall instructions. An actual uninstall script will
17931 - Add "opt hibernating 1" to server descriptor to make it clearer
17932 whether the server is hibernating.
17935 Changes in version 0.0.9.10 - 2005-06-16
17936 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17937 - Refuse relay cells that claim to have a length larger than the
17938 maximum allowed. This prevents a potential attack that could read
17939 arbitrary memory (e.g. keys) from an exit server's process
17943 Changes in version 0.0.9.9 - 2005-04-23
17944 o Bugfixes on 0.0.9.x:
17945 - If unofficial Tor clients connect and send weird TLS certs, our
17946 Tor server triggers an assert. This release contains a minimal
17947 backport from the broader fix that we put into 0.1.0.4-rc.
17950 Changes in version 0.0.9.8 - 2005-04-07
17951 o Bugfixes on 0.0.9.x:
17952 - We have a bug that I haven't found yet. Sometimes, very rarely,
17953 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17954 thinks of itself as idle. This meant that no new circuits ever got
17955 established. Here's a workaround to kill any cpuworker that's been
17956 busy for more than 100 seconds.
17959 Changes in version 0.0.9.7 - 2005-04-01
17960 o Bugfixes on 0.0.9.x:
17961 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17962 - Compare identity to identity, not to nickname, when extending to
17963 a router not already in the directory. This was preventing us from
17964 extending to unknown routers. Oops.
17965 - Make sure to create OS X Tor user in <500 range, so we aren't
17966 creating actual system users.
17967 - Note where connection-that-hasn't-sent-end was marked, and fix
17968 a few really loud instances of this harmless bug (it's fixed more
17972 Changes in version 0.0.9.6 - 2005-03-24
17973 o Bugfixes on 0.0.9.x (crashes and asserts):
17974 - Add new end stream reasons to maintenance branch. Fix bug where
17975 reason (8) could trigger an assert. Prevent bug from recurring.
17976 - Apparently win32 stat wants paths to not end with a slash.
17977 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17978 blowing away the circuit that conn->cpath_layer points to, then
17979 checking to see if the circ is well-formed. Backport check to make
17980 sure we dont use the cpath on a closed connection.
17981 - Prevent circuit_resume_edge_reading_helper() from trying to package
17982 inbufs for marked-for-close streams.
17983 - Don't crash on hup if your options->address has become unresolvable.
17984 - Some systems (like OS X) sometimes accept() a connection and tell
17985 you the remote host is 0.0.0.0:0. If this happens, due to some
17986 other mis-features, we get confused; so refuse the conn for now.
17988 o Bugfixes on 0.0.9.x (other):
17989 - Fix harmless but scary "Unrecognized content encoding" warn message.
17990 - Add new stream error reason: TORPROTOCOL reason means "you are not
17991 speaking a version of Tor I understand; say bye-bye to your stream."
17992 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17993 into the future, now that we are more tolerant of skew. This
17994 resolves a bug where a Tor server would refuse to cache a directory
17995 because all the directories it gets are too far in the future;
17996 yet the Tor server never logs any complaints about clock skew.
17997 - Mac packaging magic: make man pages useable, and do not overwrite
17998 existing torrc files.
17999 - Make OS X log happily to /var/log/tor/tor.log
18002 Changes in version 0.0.9.5 - 2005-02-22
18003 o Bugfixes on 0.0.9.x:
18004 - Fix an assert race at exit nodes when resolve requests fail.
18005 - Stop picking unverified dir mirrors--it only leads to misery.
18006 - Patch from Matt Edman to make NT services work better. Service
18007 support is still not compiled into the executable by default.
18008 - Patch from Dmitri Bely so the Tor service runs better under
18009 the win32 SYSTEM account.
18010 - Make tor-resolve actually work (?) on Win32.
18011 - Fix a sign bug when getrlimit claims to have 4+ billion
18012 file descriptors available.
18013 - Stop refusing to start when bandwidthburst == bandwidthrate.
18014 - When create cells have been on the onion queue more than five
18015 seconds, just send back a destroy and take them off the list.
18018 Changes in version 0.0.9.4 - 2005-02-03
18019 o Bugfixes on 0.0.9:
18020 - Fix an assert bug that took down most of our servers: when
18021 a server claims to have 1 GB of bandwidthburst, don't
18023 - Don't crash as badly if we have spawned the max allowed number
18024 of dnsworkers, or we're out of file descriptors.
18025 - Block more file-sharing ports in the default exit policy.
18026 - MaxConn is now automatically set to the hard limit of max
18027 file descriptors we're allowed (ulimit -n), minus a few for
18029 - Give a clearer message when servers need to raise their
18030 ulimit -n when they start running out of file descriptors.
18031 - SGI Compatibility patches from Jan Schaumann.
18032 - Tolerate a corrupt cached directory better.
18033 - When a dirserver hasn't approved your server, list which one.
18034 - Go into soft hibernation after 95% of the bandwidth is used,
18035 not 99%. This is especially important for daily hibernators who
18036 have a small accounting max. Hopefully it will result in fewer
18037 cut connections when the hard hibernation starts.
18038 - Load-balance better when using servers that claim more than
18039 800kB/s of capacity.
18040 - Make NT services work (experimental, only used if compiled in).
18043 Changes in version 0.0.9.3 - 2005-01-21
18044 o Bugfixes on 0.0.9:
18045 - Backport the cpu use fixes from main branch, so busy servers won't
18046 need as much processor time.
18047 - Work better when we go offline and then come back, or when we
18048 run Tor at boot before the network is up. We do this by
18049 optimistically trying to fetch a new directory whenever an
18050 application request comes in and we think we're offline -- the
18051 human is hopefully a good measure of when the network is back.
18052 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18053 long as you keep using them; actually publish hidserv descriptors
18054 shortly after they change, rather than waiting 20-40 minutes.
18055 - Enable Mac startup script by default.
18056 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18057 - When you update AllowUnverifiedNodes or FirewallPorts via the
18058 controller's setconf feature, we were always appending, never
18060 - When you update HiddenServiceDir via setconf, it was screwing up
18061 the order of reading the lines, making it fail.
18062 - Do not rewrite a cached directory back to the cache; otherwise we
18063 will think it is recent and not fetch a newer one on startup.
18064 - Workaround for webservers that lie about Content-Encoding: Tor
18065 now tries to autodetect compressed directories and compression
18066 itself. This lets us Proxypass dir fetches through apache.
18069 Changes in version 0.0.9.2 - 2005-01-04
18070 o Bugfixes on 0.0.9 (crashes and asserts):
18071 - Fix an assert on startup when the disk is full and you're logging
18073 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18074 style address, then we'd crash.
18075 - Fix an assert trigger when the running-routers string we get from
18076 a dirserver is broken.
18077 - Make worker threads start and run on win32. Now win32 servers
18079 - Bandaid (not actually fix, but now it doesn't crash) an assert
18080 where the dns worker dies mysteriously and the main Tor process
18081 doesn't remember anything about the address it was resolving.
18083 o Bugfixes on 0.0.9 (Win32):
18084 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18085 name out of the warning/assert messages.
18086 - Fix a superficial "unhandled error on read" bug on win32.
18087 - The win32 installer no longer requires a click-through for our
18088 license, since our Free Software license grants rights but does not
18090 - Win32: When connecting to a dirserver fails, try another one
18091 immediately. (This was already working for non-win32 Tors.)
18092 - Stop trying to parse $HOME on win32 when hunting for default
18094 - Make tor-resolve.c work on win32 by calling network_init().
18096 o Bugfixes on 0.0.9 (other):
18097 - Make 0.0.9.x build on Solaris again.
18098 - Due to a fencepost error, we were blowing away the \n when reporting
18099 confvalue items in the controller. So asking for multiple config
18100 values at once couldn't work.
18101 - When listing circuits that are pending on an opening OR connection,
18102 if we're an OR we were listing circuits that *end* at us as
18103 being pending on every listener, dns/cpu worker, etc. Stop that.
18104 - Dirservers were failing to create 'running-routers' or 'directory'
18105 strings if we had more than some threshold of routers. Fix them so
18106 they can handle any number of routers.
18107 - Fix a superficial "Duplicate mark for close" bug.
18108 - Stop checking for clock skew for OR connections, even for servers.
18109 - Fix a fencepost error that was chopping off the last letter of any
18110 nickname that is the maximum allowed nickname length.
18111 - Update URLs in log messages so they point to the new website.
18112 - Fix a potential problem in mangling server private keys while
18113 writing to disk (not triggered yet, as far as we know).
18114 - Include the licenses for other free software we include in Tor,
18115 now that we're shipping binary distributions more regularly.
18118 Changes in version 0.0.9.1 - 2004-12-15
18119 o Bugfixes on 0.0.9:
18120 - Make hibernation actually work.
18121 - Make HashedControlPassword config option work.
18122 - When we're reporting event circuit status to a controller,
18123 don't use the stream status code.
18126 Changes in version 0.0.9 - 2004-12-12
18127 o Bugfixes on 0.0.8.1 (Crashes and asserts):
18128 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18129 write() call will fail and we handle it there.
18130 - When we run out of disk space, or other log writing error, don't
18131 crash. Just stop logging to that log and continue.
18132 - Fix isspace() and friends so they still make Solaris happy
18133 but also so they don't trigger asserts on win32.
18134 - Fix assert failure on malformed socks4a requests.
18135 - Fix an assert bug where a hidden service provider would fail if
18136 the first hop of his rendezvous circuit was down.
18137 - Better handling of size_t vs int, so we're more robust on 64
18140 o Bugfixes on 0.0.8.1 (Win32):
18141 - Make windows sockets actually non-blocking (oops), and handle
18142 win32 socket errors better.
18143 - Fix parse_iso_time on platforms without strptime (eg win32).
18144 - win32: when being multithreaded, leave parent fdarray open.
18145 - Better handling of winsock includes on non-MSV win32 compilers.
18146 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18148 - Make unit tests work on win32.
18150 o Bugfixes on 0.0.8.1 (Path selection and streams):
18151 - Calculate timeout for waiting for a connected cell from the time
18152 we sent the begin cell, not from the time the stream started. If
18153 it took a long time to establish the circuit, we would time out
18154 right after sending the begin cell.
18155 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18156 of * as always matching, so we were picking reject *:* nodes as
18157 exit nodes too. Oops.
18158 - When read() failed on a stream, we would close it without sending
18159 back an end. So 'connection refused' would simply be ignored and
18160 the user would get no response.
18161 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18162 we shouldn't hold-open-until-flush if the eof arrived first.
18163 - Let resolve conns retry/expire also, rather than sticking around
18165 - Fix more dns related bugs: send back resolve_failed and end cells
18166 more reliably when the resolve fails, rather than closing the
18167 circuit and then trying to send the cell. Also attach dummy resolve
18168 connections to a circuit *before* calling dns_resolve(), to fix
18169 a bug where cached answers would never be sent in RESOLVED cells.
18171 o Bugfixes on 0.0.8.1 (Circuits):
18172 - Finally fix a bug that's been plaguing us for a year:
18173 With high load, circuit package window was reaching 0. Whenever
18174 we got a circuit-level sendme, we were reading a lot on each
18175 socket, but only writing out a bit. So we would eventually reach
18176 eof. This would be noticed and acted on even when there were still
18177 bytes sitting in the inbuf.
18178 - Use identity comparison, not nickname comparison, to choose which
18179 half of circuit-ID-space each side gets to use. This is needed
18180 because sometimes we think of a router as a nickname, and sometimes
18181 as a hex ID, and we can't predict what the other side will do.
18183 o Bugfixes on 0.0.8.1 (Other):
18184 - Fix a whole slew of memory leaks.
18185 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18186 - If we are using select, make sure we stay within FD_SETSIZE.
18187 - When poll() is interrupted, we shouldn't believe the revents values.
18188 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18189 and smartlist_len, which are two major profiling offenders.
18190 - If do_hup fails, actually notice.
18191 - Flush the log file descriptor after we print "Tor opening log file",
18192 so we don't see those messages days later.
18193 - Hidden service operators now correctly handle version 1 style
18194 INTRODUCE1 cells (nobody generates them still, so not a critical
18196 - Handle more errnos from accept() without closing the listener.
18197 Some OpenBSD machines were closing their listeners because
18198 they ran out of file descriptors.
18199 - Some people had wrapped their tor client/server in a script
18200 that would restart it whenever it died. This did not play well
18201 with our "shut down if your version is obsolete" code. Now people
18202 don't fetch a new directory if their local cached version is
18204 - Make our autogen.sh work on ksh as well as bash.
18205 - Better torrc example lines for dirbindaddress and orbindaddress.
18206 - Improved bounds checking on parsed ints (e.g. config options and
18207 the ones we find in directories.)
18208 - Stop using separate defaults for no-config-file and
18209 empty-config-file. Now you have to explicitly turn off SocksPort,
18210 if you don't want it open.
18211 - We were starting to daemonize before we opened our logs, so if
18212 there were any problems opening logs, we would complain to stderr,
18213 which wouldn't work, and then mysteriously exit.
18214 - If a verified OR connects to us before he's uploaded his descriptor,
18215 or we verify him and hup but he still has the original TLS
18216 connection, then conn->nickname is still set like he's unverified.
18218 o Code security improvements, inspired by Ilja:
18219 - tor_snprintf wrapper over snprintf with consistent (though not C99)
18221 - Replace sprintf with tor_snprintf. (I think they were all safe, but
18223 - Replace strcpy/strncpy with strlcpy in more places.
18224 - Avoid strcat; use tor_snprintf or strlcat instead.
18226 o Features (circuits and streams):
18227 - New circuit building strategy: keep a list of ports that we've
18228 used in the past 6 hours, and always try to have 2 circuits open
18229 or on the way that will handle each such port. Seed us with port
18230 80 so web users won't complain that Tor is "slow to start up".
18231 - Make kill -USR1 dump more useful stats about circuits.
18232 - When warning about retrying or giving up, print the address, so
18233 the user knows which one it's talking about.
18234 - If you haven't used a clean circuit in an hour, throw it away,
18235 just to be on the safe side. (This means after 6 hours a totally
18236 unused Tor client will have no circuits open.)
18237 - Support "foo.nickname.exit" addresses, to let Alice request the
18238 address "foo" as viewed by exit node "nickname". Based on a patch
18239 from Geoff Goodell.
18240 - If your requested entry or exit node has advertised bandwidth 0,
18242 - Be more greedy about filling up relay cells -- we try reading again
18243 once we've processed the stuff we read, in case enough has arrived
18244 to fill the last cell completely.
18245 - Refuse application socks connections to port 0.
18246 - Use only 0.0.9pre1 and later servers for resolve cells.
18248 o Features (bandwidth):
18249 - Hibernation: New config option "AccountingMax" lets you
18250 set how many bytes per month (in each direction) you want to
18251 allow your server to consume. Rather than spreading those
18252 bytes out evenly over the month, we instead hibernate for some
18253 of the month and pop up at a deterministic time, work until
18254 the bytes are consumed, then hibernate again. Config option
18255 "MonthlyAccountingStart" lets you specify which day of the month
18256 your billing cycle starts on.
18257 - Implement weekly/monthly/daily accounting: now you specify your
18258 hibernation properties by
18259 AccountingMax N bytes|KB|MB|GB|TB
18260 AccountingStart day|week|month [day] HH:MM
18261 Defaults to "month 1 0:00".
18262 - Let bandwidth and interval config options be specified as 5 bytes,
18263 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18265 o Features (directories):
18266 - New "router-status" line in directory, to better bind each verified
18267 nickname to its identity key.
18268 - Clients can ask dirservers for /dir.z to get a compressed version
18269 of the directory. Only works for servers running 0.0.9, of course.
18270 - Make clients cache directories and use them to seed their router
18271 lists at startup. This means clients have a datadir again.
18272 - Respond to content-encoding headers by trying to uncompress as
18274 - Clients and servers now fetch running-routers; cache
18275 running-routers; compress running-routers; serve compressed
18277 - Make moria2 advertise a dirport of 80, so people behind firewalls
18278 will be able to get a directory.
18279 - Http proxy support
18280 - Dirservers translate requests for http://%s:%d/x to /x
18281 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18282 be routed through this host.
18283 - Clients ask for /tor/x rather than /x for new enough dirservers.
18284 This way we can one day coexist peacefully with apache.
18285 - Clients specify a "Host: %s%d" http header, to be compatible
18286 with more proxies, and so running squid on an exit node can work.
18287 - Protect dirservers from overzealous descriptor uploading -- wait
18288 10 seconds after directory gets dirty, before regenerating.
18290 o Features (packages and install):
18291 - Add NSI installer contributed by J Doe.
18292 - Apply NT service patch from Osamu Fujino. Still needs more work.
18293 - Commit VC6 and VC7 workspace/project files.
18294 - Commit a tor.spec for making RPM files, with help from jbash.
18295 - Add contrib/torctl.in contributed by Glenn Fink.
18296 - Make expand_filename handle ~ and ~username.
18297 - Use autoconf to enable largefile support where necessary. Use
18298 ftello where available, since ftell can fail at 2GB.
18299 - Ship src/win32/ in the tarball, so people can use it to build.
18300 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
18303 o Features (ui controller):
18304 - Control interface: a separate program can now talk to your
18305 client/server over a socket, and get/set config options, receive
18306 notifications of circuits and streams starting/finishing/dying,
18307 bandwidth used, etc. The next step is to get some GUIs working.
18308 Let us know if you want to help out. See doc/control-spec.txt .
18309 - Ship a contrib/tor-control.py as an example script to interact
18310 with the control port.
18311 - "tor --hash-password zzyxz" will output a salted password for
18312 use in authenticating to the control interface.
18313 - Implement the control-spec's SAVECONF command, to write your
18314 configuration to torrc.
18315 - Get cookie authentication for the controller closer to working.
18316 - When set_conf changes our server descriptor, upload a new copy.
18317 But don't upload it too often if there are frequent changes.
18319 o Features (config and command-line):
18320 - Deprecate unofficial config option abbreviations, and abbreviations
18321 not on the command line.
18322 - Configuration infrastructure support for warning on obsolete
18324 - Give a slightly more useful output for "tor -h".
18325 - Break DirFetchPostPeriod into:
18326 - DirFetchPeriod for fetching full directory,
18327 - StatusFetchPeriod for fetching running-routers,
18328 - DirPostPeriod for posting server descriptor,
18329 - RendPostPeriod for posting hidden service descriptors.
18330 - New log format in config:
18331 "Log minsev[-maxsev] stdout|stderr|syslog" or
18332 "Log minsev[-maxsev] file /var/foo"
18333 - DirPolicy config option, to let people reject incoming addresses
18334 from their dirserver.
18335 - "tor --list-fingerprint" will list your identity key fingerprint
18337 - Make tor --version --version dump the cvs Id of every file.
18338 - New 'MyFamily nick1,...' config option for a server to
18339 specify other servers that shouldn't be used in the same circuit
18340 with it. Only believed if nick1 also specifies us.
18341 - New 'NodeFamily nick1,nick2,...' config option for a client to
18342 specify nodes that it doesn't want to use in the same circuit.
18343 - New 'Redirectexit pattern address:port' config option for a
18344 server to redirect exit connections, e.g. to a local squid.
18345 - Add "pass" target for RedirectExit, to make it easier to break
18346 out of a sequence of RedirectExit rules.
18347 - Make the dirservers file obsolete.
18348 - Include a dir-signing-key token in directories to tell the
18349 parsing entity which key is being used to sign.
18350 - Remove the built-in bulky default dirservers string.
18351 - New config option "Dirserver %s:%d [fingerprint]", which can be
18352 repeated as many times as needed. If no dirservers specified,
18353 default to moria1,moria2,tor26.
18354 - Make 'Routerfile' config option obsolete.
18355 - Discourage people from setting their dirfetchpostperiod more often
18356 than once per minute.
18358 o Features (other):
18359 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18360 get back to normal.)
18361 - Accept *:706 (silc) in default exit policy.
18362 - Implement new versioning format for post 0.1.
18363 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18364 log more informatively.
18365 - Check clock skew for verified servers, but allow unverified
18366 servers and clients to have any clock skew.
18367 - Make sure the hidden service descriptors are at a random offset
18368 from each other, to hinder linkability.
18369 - Clients now generate a TLS cert too, in preparation for having
18370 them act more like real nodes.
18371 - Add a pure-C tor-resolve implementation.
18372 - Use getrlimit and friends to ensure we can reach MaxConn (currently
18373 1024) file descriptors.
18374 - Raise the max dns workers from 50 to 100.
18377 Changes in version 0.0.8.1 - 2004-10-13
18379 - Fix a seg fault that can be triggered remotely for Tor
18380 clients/servers with an open dirport.
18381 - Fix a rare assert trigger, where routerinfos for entries in
18382 our cpath would expire while we're building the path.
18383 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18384 - Fix a rare seg fault for people running hidden services on
18385 intermittent connections.
18386 - Fix a bug in parsing opt keywords with objects.
18387 - Fix a stale pointer assert bug when a stream detaches and
18389 - Fix a string format vulnerability (probably not exploitable)
18390 in reporting stats locally.
18391 - Fix an assert trigger: sometimes launching circuits can fail
18392 immediately, e.g. because too many circuits have failed recently.
18393 - Fix a compile warning on 64 bit platforms.
18396 Changes in version 0.0.8 - 2004-08-25
18398 - Made our unit tests compile again on OpenBSD 3.5, and tor
18399 itself compile again on OpenBSD on a sparc64.
18400 - We were neglecting milliseconds when logging on win32, so
18401 everything appeared to happen at the beginning of each second.
18402 - Check directory signature _before_ you decide whether you're
18403 you're running an obsolete version and should exit.
18404 - Check directory signature _before_ you parse the running-routers
18405 list to decide who's running.
18406 - Check return value of fclose while writing to disk, so we don't
18407 end up with broken files when servers run out of disk space.
18408 - Port it to SunOS 5.9 / Athena
18409 - Fix two bugs in saving onion keys to disk when rotating, so
18410 hopefully we'll get fewer people using old onion keys.
18411 - Remove our mostly unused -- and broken -- hex_encode()
18412 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18413 for pointing out this bug.)
18414 - Only pick and establish intro points after we've gotten a
18416 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18417 don't put it into the client dns cache.
18418 - If a begin failed due to exit policy, but we believe the IP
18419 address should have been allowed, switch that router to exitpolicy
18420 reject *:* until we get our next directory.
18422 o Protocol changes:
18423 - 'Extend' relay cell payloads now include the digest of the
18424 intended next hop's identity key. Now we can verify that we're
18425 extending to the right router, and also extend to routers we
18426 hadn't heard of before.
18429 - Tor nodes can now act as relays (with an advertised ORPort)
18430 without being manually verified by the dirserver operators.
18431 - Uploaded descriptors of unverified routers are now accepted
18432 by the dirservers, and included in the directory.
18433 - Verified routers are listed by nickname in the running-routers
18434 list; unverified routers are listed as "$<fingerprint>".
18435 - We now use hash-of-identity-key in most places rather than
18436 nickname or addr:port, for improved security/flexibility.
18437 - AllowUnverifiedNodes config option to let circuits choose no-name
18438 routers in entry,middle,exit,introduction,rendezvous positions.
18439 Allow middle and rendezvous positions by default.
18440 - When picking unverified routers, skip those with low uptime and/or
18441 low bandwidth, depending on what properties you care about.
18442 - ClientOnly option for nodes that never want to become servers.
18443 - Directory caching.
18444 - "AuthoritativeDir 1" option for the official dirservers.
18445 - Now other nodes (clients and servers) will cache the latest
18446 directory they've pulled down.
18447 - They can enable their DirPort to serve it to others.
18448 - Clients will pull down a directory from any node with an open
18449 DirPort, and check the signature/timestamp correctly.
18450 - Authoritative dirservers now fetch directories from other
18451 authdirservers, to stay better synced.
18452 - Running-routers list tells who's down also, along with noting
18453 if they're verified (listed by nickname) or unverified (listed
18455 - Allow dirservers to serve running-router list separately.
18456 This isn't used yet.
18457 - You can now fetch $DIRURL/running-routers to get just the
18458 running-routers line, not the whole descriptor list. (But
18459 clients don't use this yet.)
18460 - Clients choose nodes proportional to advertised bandwidth.
18461 - Clients avoid using nodes with low uptime as introduction points.
18462 - Handle servers with dynamic IP addresses: don't just replace
18463 options->Address with the resolved one at startup, and
18464 detect our address right before we make a routerinfo each time.
18465 - 'FascistFirewall' option to pick dirservers and ORs on specific
18466 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18467 which ports are open. (Defaults to 80,443)
18468 - Try other dirservers immediately if the one you try is down. This
18469 should tolerate down dirservers better now.
18470 - ORs connect-on-demand to other ORs
18471 - If you get an extend cell to an OR you're not connected to,
18472 connect, handshake, and forward the create cell.
18473 - The authoritative dirservers stay connected to everybody,
18474 and everybody stays connected to 0.0.7 servers, but otherwise
18475 clients/servers expire unused connections after 5 minutes.
18476 - When servers get a sigint, they delay 30 seconds (refusing new
18477 connections) then exit. A second sigint causes immediate exit.
18478 - File and name management:
18479 - Look for .torrc if no CONFDIR "torrc" is found.
18480 - If no datadir is defined, then choose, make, and secure ~/.tor
18482 - If torrc not found, exitpolicy reject *:*.
18483 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18484 - If no nickname is defined, derive default from hostname.
18485 - Rename secret key files, e.g. identity.key -> secret_id_key,
18486 to discourage people from mailing their identity key to tor-ops.
18487 - Refuse to build a circuit before the directory has arrived --
18488 it won't work anyway, since you won't know the right onion keys
18490 - Parse tor version numbers so we can do an is-newer-than check
18491 rather than an is-in-the-list check.
18492 - New socks command 'resolve', to let us shim gethostbyname()
18494 - A 'tor_resolve' script to access the socks resolve functionality.
18495 - A new socks-extensions.txt doc file to describe our
18496 interpretation and extensions to the socks protocols.
18497 - Add a ContactInfo option, which gets published in descriptor.
18498 - Write tor version at the top of each log file
18499 - New docs in the tarball:
18501 - Document that you should proxy your SSL traffic too.
18502 - Log a warning if the user uses an unsafe socks variant, so people
18503 are more likely to learn about privoxy or socat.
18504 - Log a warning if you're running an unverified server, to let you
18505 know you might want to get it verified.
18506 - Change the default exit policy to reject the default edonkey,
18507 kazaa, gnutella ports.
18508 - Add replace_file() to util.[ch] to handle win32's rename().
18509 - Publish OR uptime in descriptor (and thus in directory) too.
18510 - Remember used bandwidth (both in and out), and publish 15-minute
18511 snapshots for the past day into our descriptor.
18512 - Be more aggressive about trying to make circuits when the network
18513 has changed (e.g. when you unsuspend your laptop).
18514 - Check for time skew on http headers; report date in response to
18516 - If the entrynode config line has only one node, don't pick it as
18518 - Add strict{entry|exit}nodes config options. If set to 1, then
18519 we refuse to build circuits that don't include the specified entry
18521 - OutboundBindAddress config option, to bind to a specific
18522 IP address for outgoing connect()s.
18523 - End truncated log entries (e.g. directories) with "[truncated]".
18526 Changes in version 0.0.7.3 - 2004-08-12
18527 o Stop dnsworkers from triggering an assert failure when you
18528 ask them to resolve the host "".
18531 Changes in version 0.0.7.2 - 2004-07-07
18532 o A better fix for the 0.0.0.0 problem, that will hopefully
18533 eliminate the remaining related assertion failures.
18536 Changes in version 0.0.7.1 - 2004-07-04
18537 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18538 since internally we use 0.0.0.0 to signify "not yet resolved".
18541 Changes in version 0.0.7 - 2004-06-07
18542 o Fixes for crashes and other obnoxious bugs:
18543 - Fix an epipe bug: sometimes when directory connections failed
18544 to connect, we would give them a chance to flush before closing
18546 - When we detached from a circuit because of resolvefailed, we
18547 would immediately try the same circuit twice more, and then
18548 give up on the resolve thinking we'd tried three different
18550 - Limit the number of intro circuits we'll attempt to build for a
18551 hidden service per 15-minute period.
18552 - Check recommended-software string *early*, before actually parsing
18553 the directory. Thus we can detect an obsolete version and exit,
18554 even if the new directory format doesn't parse.
18555 o Fixes for security bugs:
18556 - Remember which nodes are dirservers when you startup, and if a
18557 random OR enables his dirport, don't automatically assume he's
18558 a trusted dirserver.
18560 - Directory connections were asking the wrong poll socket to
18561 start writing, and not asking themselves to start writing.
18562 - When we detached from a circuit because we sent a begin but
18563 didn't get a connected, we would use it again the first time;
18564 but after that we would correctly switch to a different one.
18565 - Stop warning when the first onion decrypt attempt fails; they
18566 will sometimes legitimately fail now that we rotate keys.
18567 - Override unaligned-access-ok check when $host_cpu is ia64 or
18568 arm. Apparently they allow it but the kernel whines.
18569 - Dirservers try to reconnect periodically too, in case connections
18571 - Fix some memory leaks in directory servers.
18572 - Allow backslash in Win32 filenames.
18573 - Made Tor build complain-free on FreeBSD, hopefully without
18574 breaking other BSD builds. We'll see.
18575 - Check directory signatures based on name of signer, not on whom
18576 we got the directory from. This will let us cache directories more
18578 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18581 - Doxygen markup on all functions and global variables.
18582 - Make directory functions update routerlist, not replace it. So
18583 now directory disagreements are not so critical a problem.
18584 - Remove the upper limit on number of descriptors in a dirserver's
18585 directory (not that we were anywhere close).
18586 - Allow multiple logfiles at different severity ranges.
18587 - Allow *BindAddress to specify ":port" rather than setting *Port
18588 separately. Allow multiple instances of each BindAddress config
18589 option, so you can bind to multiple interfaces if you want.
18590 - Allow multiple exit policy lines, which are processed in order.
18591 Now we don't need that huge line with all the commas in it.
18592 - Enable accept/reject policies on SOCKS connections, so you can bind
18593 to 0.0.0.0 but still control who can use your OP.
18594 - Updated the man page to reflect these features.
18597 Changes in version 0.0.6.2 - 2004-05-16
18598 o Our integrity-checking digest was checking only the most recent cell,
18599 not the previous cells like we'd thought.
18600 Thanks to Stefan Mark for finding the flaw!
18603 Changes in version 0.0.6.1 - 2004-05-06
18604 o Fix two bugs in our AES counter-mode implementation (this affected
18605 onion-level stream encryption, but not TLS-level). It turns
18606 out we were doing something much more akin to a 16-character
18607 polyalphabetic cipher. Oops.
18608 Thanks to Stefan Mark for finding the flaw!
18609 o Retire moria3 as a directory server, and add tor26 as a directory
18613 Changes in version 0.0.6 - 2004-05-02
18615 - Hidden services and rendezvous points are implemented. Go to
18616 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18617 hidden services. (This only works via a socks4a proxy such as
18618 Privoxy, and currently it's quite slow.)
18619 - We now rotate link (tls context) keys and onion keys.
18620 - CREATE cells now include oaep padding, so you can tell
18621 if you decrypted them correctly.
18622 - Retry stream correctly when we fail to connect because of
18623 exit-policy-reject (should try another) or can't-resolve-address.
18624 - When we hup a dirserver and we've *removed* a server from the
18625 approved-routers list, now we remove that server from the
18626 in-memory directories too.
18627 - Add bandwidthburst to server descriptor.
18628 - Directories now say which dirserver signed them.
18629 - Use a tor_assert macro that logs failed assertions too.
18630 - Since we don't support truncateds much, don't bother sending them;
18631 just close the circ.
18632 - Fetch randomness from /dev/urandom better (not via fopen/fread)
18633 - Better debugging for tls errors
18634 - Set Content-Type on the directory and hidserv descriptor.
18635 - Remove IVs from cipher code, since AES-ctr has none.
18637 - Fix an assert trigger for exit nodes that's been plaguing us since
18638 the days of 0.0.2prexx (thanks weasel!)
18639 - Fix a bug where we were closing tls connections intermittently.
18640 It turns out openssl keeps its errors around -- so if an error
18641 happens, and you don't ask about it, and then another openssl
18642 operation happens and succeeds, and you ask if there was an error,
18643 it tells you about the first error.
18644 - Fix a bug that's been lurking since 27 may 03 (!)
18645 When passing back a destroy cell, we would use the wrong circ id.
18646 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
18647 - Some versions of openssl have an SSL_pending function that erroneously
18648 returns bytes when there is a non-application record pending.
18649 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18650 o We were using an array of length zero in a few places.
18651 o Win32's gethostbyname can't resolve an IP to an IP.
18652 o Win32's close can't close a socket.
18653 o Handle windows socket errors correctly.
18655 - check for <sys/limits.h> so we build on FreeBSD again, and
18656 <machine/limits.h> for NetBSD.
18659 Changes in version 0.0.5 - 2004-03-30
18660 o Install torrc as torrc.sample -- we no longer clobber your
18662 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18663 o Only build circuits after we've fetched the directory: clients were
18664 using only the directory servers before they'd fetched a directory.
18665 This also means longer startup time; so it goes.
18666 o Fix an assert trigger where an OP would fail to handshake, and we'd
18667 expect it to have a nickname.
18668 o Work around a tsocks bug: do a socks reject when AP connection dies
18669 early, else tsocks goes into an infinite loop.
18670 o Hold socks connection open until reply is flushed (if possible)
18671 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18672 the dns farm to do it.
18673 o Fix c99 aliasing warnings in rephist.c
18674 o Don't include server descriptors that are older than 24 hours in the
18676 o Give socks 'reject' replies their whole 15s to attempt to flush,
18677 rather than seeing the 60s timeout and assuming the flush had failed.
18678 o Clean automake droppings from the cvs repository
18679 o Add in a 'notice' log level for things the operator should hear
18680 but that aren't warnings
18683 Changes in version 0.0.4 - 2004-03-26
18684 o When connecting to a dirserver or OR and the network is down,
18688 Changes in version 0.0.3 - 2004-03-26
18689 o Warn and fail if server chose a nickname with illegal characters
18690 o Port to Solaris and Sparc:
18691 - include missing header fcntl.h
18692 - have autoconf find -lsocket -lnsl automatically
18693 - deal with hardware word alignment
18694 - make uname() work (solaris has a different return convention)
18695 - switch from using signal() to sigaction()
18696 o Preliminary work on reputation system:
18697 - Keep statistics on success/fail of connect attempts; they're published
18698 by kill -USR1 currently.
18699 - Add a RunTesting option to try to learn link state by creating test
18700 circuits, even when SocksPort is off.
18701 - Remove unused open circuits when there are too many.
18704 Changes in version 0.0.2 - 2004-03-19
18705 - Include strlcpy and strlcat for safer string ops
18706 - define INADDR_NONE so we compile (but still not run) on solaris
18709 Changes in version 0.0.2pre27 - 2004-03-14
18711 - Allow internal tor networks (we were rejecting internal IPs,
18712 now we allow them if they're set explicitly).
18713 - And fix a few endian issues.
18716 Changes in version 0.0.2pre26 - 2004-03-14
18718 - If a stream times out after 15s without a connected cell, don't
18719 try that circuit again: try a new one.
18720 - Retry streams at most 4 times. Then give up.
18721 - When a dirserver gets a descriptor from an unknown router, it
18722 logs its fingerprint (so the dirserver operator can choose to
18723 accept it even without mail from the server operator).
18724 - Inform unapproved servers when we reject their descriptors.
18725 - Make tor build on Windows again. It works as a client, who knows
18727 - Clearer instructions in the torrc for how to set up a server.
18728 - Be more efficient about reading fd's when our global token bucket
18729 (used for rate limiting) becomes empty.
18731 - Stop asserting that computers always go forward in time. It's
18733 - When we sent a cell (e.g. destroy) and then marked an OR connection
18734 expired, we might close it before finishing a flush if the other
18735 side isn't reading right then.
18736 - Don't allow dirservers to start if they haven't defined
18737 RecommendedVersions
18738 - We were caching transient dns failures. Oops.
18739 - Prevent servers from publishing an internal IP as their address.
18740 - Address a strcat vulnerability in circuit.c
18743 Changes in version 0.0.2pre25 - 2004-03-04
18745 - Put the OR's IP in its router descriptor, not its fqdn. That way
18746 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18749 - If the user typed in an address that didn't resolve, the server
18753 Changes in version 0.0.2pre24 - 2004-03-03
18755 - Fix an assertion failure in dns.c, where we were trying to dequeue
18756 a pending dns resolve even if it wasn't pending
18757 - Fix a spurious socks5 warning about still trying to write after the
18758 connection is finished.
18759 - Hold certain marked_for_close connections open until they're finished
18760 flushing, rather than losing bytes by closing them too early.
18761 - Correctly report the reason for ending a stream
18762 - Remove some duplicate calls to connection_mark_for_close
18763 - Put switch_id and start_daemon earlier in the boot sequence, so it
18764 will actually try to chdir() to options.DataDirectory
18765 - Make 'make test' exit(1) if a test fails; fix some unit tests
18766 - Make tor fail when you use a config option it doesn't know about,
18767 rather than warn and continue.
18768 - Make --version work
18769 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18772 Changes in version 0.0.2pre23 - 2004-02-29
18774 - Print a statement when the first circ is finished, so the user
18775 knows it's working.
18776 - If a relay cell is unrecognized at the end of the circuit,
18777 send back a destroy. (So attacks to mutate cells are more
18779 - New config option 'excludenodes' to avoid certain nodes for circuits.
18780 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18781 so you can collect coredumps there.
18783 - Fix a bug in tls flushing where sometimes data got wedged and
18784 didn't flush until more data got sent. Hopefully this bug was
18785 a big factor in the random delays we were seeing.
18786 - Make 'connected' cells include the resolved IP, so the client
18787 dns cache actually gets populated.
18788 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18789 - When we time-out on a stream and detach from the circuit, send an
18790 end cell down it first.
18791 - Only warn about an unknown router (in exitnodes, entrynodes,
18792 excludenodes) after we've fetched a directory.
18795 Changes in version 0.0.2pre22 - 2004-02-26
18797 - Servers publish less revealing uname information in descriptors.
18798 - More memory tracking and assertions, to crash more usefully when
18800 - If the default torrc isn't there, just use some default defaults.
18801 Plus provide an internal dirservers file if they don't have one.
18802 - When the user tries to use Tor as an http proxy, give them an http
18803 501 failure explaining that we're a socks proxy.
18804 - Dump a new router.desc on hup, to help confused people who change
18805 their exit policies and then wonder why router.desc doesn't reflect
18807 - Clean up the generic tor.sh init script that we ship with.
18809 - If the exit stream is pending on the resolve, and a destroy arrives,
18810 then the stream wasn't getting removed from the pending list. I
18811 think this was the one causing recent server crashes.
18812 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18813 - When it couldn't resolve any dirservers, it was useless from then on.
18814 Now it reloads the RouterFile (or default dirservers) if it has no
18816 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18817 many users don't even *have* a /usr/local/sbin/.
18820 Changes in version 0.0.2pre21 - 2004-02-18
18822 - There's a ChangeLog file that actually reflects the changelog.
18823 - There's a 'torify' wrapper script, with an accompanying
18824 tor-tsocks.conf, that simplifies the process of using tsocks for
18825 tor. It even has a man page.
18826 - The tor binary gets installed to sbin rather than bin now.
18827 - Retry streams where the connected cell hasn't arrived in 15 seconds
18828 - Clean up exit policy handling -- get the default out of the torrc,
18829 so we can update it without forcing each server operator to fix
18831 - Allow imaps and pop3s in default exit policy
18833 - Prevent picking middleman nodes as the last node in the circuit
18836 Changes in version 0.0.2pre20 - 2004-01-30
18838 - We now have a deb package, and it's in debian unstable. Go to
18839 it, apt-getters. :)
18840 - I've split the TotalBandwidth option into BandwidthRate (how many
18841 bytes per second you want to allow, long-term) and
18842 BandwidthBurst (how many bytes you will allow at once before the cap
18843 kicks in). This better token bucket approach lets you, say, set
18844 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18845 performance while not exceeding your monthly bandwidth quota.
18846 - Push out a tls record's worth of data once you've got it, rather
18847 than waiting until you've read everything waiting to be read. This
18848 may improve performance by pipelining better. We'll see.
18849 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18850 from failed circuits (if they haven't been connected yet) and attach
18852 - Expire old streams that haven't managed to connect. Some day we'll
18853 have them reattach to new circuits instead.
18856 - Fix several memory leaks that were causing servers to become bloated
18858 - Fix a few very rare assert triggers. A few more remain.
18859 - Setuid to User _before_ complaining about running as root.
18862 Changes in version 0.0.2pre19 - 2004-01-07
18864 - Fix deadlock condition in dns farm. We were telling a child to die by
18865 closing the parent's file descriptor to him. But newer children were
18866 inheriting the open file descriptor from the parent, and since they
18867 weren't closing it, the socket never closed, so the child never read
18868 eof, so he never knew to exit. Similarly, dns workers were holding
18869 open other sockets, leading to all sorts of chaos.
18870 - New cleaner daemon() code for forking and backgrounding.
18871 - If you log to a file, it now prints an entry at the top of the
18872 logfile so you know it's working.
18873 - The onionskin challenge length was 30 bytes longer than necessary.
18874 - Started to patch up the spec so it's not quite so out of date.
18877 Changes in version 0.0.2pre18 - 2004-01-02
18879 - Fix endian issues with the 'integrity' field in the relay header.
18880 - Fix a potential bug where connections in state
18881 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18884 Changes in version 0.0.2pre17 - 2003-12-30
18886 - Made --debuglogfile (or any second log file, actually) work.
18887 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18888 adversary could force us into an infinite loop.
18891 - Each onionskin handshake now includes a hash of the computed key,
18892 to prove the server's identity and help perfect forward secrecy.
18893 - Changed cell size from 256 to 512 bytes (working toward compatibility
18895 - Changed cell length to 2 bytes, and moved it to the relay header.
18896 - Implemented end-to-end integrity checking for the payloads of
18898 - Separated streamid from 'recognized' (otherwise circuits will get
18899 messed up when we try to have streams exit from the middle). We
18900 use the integrity-checking to confirm that a cell is addressed to
18902 - Randomize the initial circid and streamid values, so an adversary who
18903 breaks into a node can't learn how many circuits or streams have
18907 Changes in version 0.0.2pre16 - 2003-12-14
18909 - Fixed a bug that made HUP trigger an assert
18910 - Fixed a bug where a circuit that immediately failed wasn't being
18911 counted as a failed circuit in counting retries.
18914 - Now we close the circuit when we get a truncated cell: otherwise we're
18915 open to an anonymity attack where a bad node in the path truncates
18916 the circuit and then we open streams at him.
18917 - Add port ranges to exit policies
18918 - Add a conservative default exit policy
18919 - Warn if you're running tor as root
18920 - on HUP, retry OR connections and close/rebind listeners
18921 - options.EntryNodes: try these nodes first when picking the first node
18922 - options.ExitNodes: if your best choices happen to include any of
18923 your preferred exit nodes, you choose among just those preferred
18925 - options.ExcludedNodes: nodes that are never picked in path building
18928 Changes in version 0.0.2pre15 - 2003-12-03
18929 o Robustness and bugfixes:
18930 - Sometimes clients would cache incorrect DNS resolves, which would
18931 really screw things up.
18932 - An OP that goes offline would slowly leak all its sockets and stop
18934 - A wide variety of bugfixes in exit node selection, exit policy
18935 handling, and processing pending streams when a new circuit is
18937 - Pick nodes for a path only from those the directory says are up
18938 - Choose randomly from all running dirservers, not always the first one
18939 - Increase allowed http header size for directory fetch.
18940 - Stop writing to stderr (if we're daemonized it will be closed).
18941 - Enable -g always, so cores will be more useful to me.
18942 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18945 - Wrote a man page. It lists commonly used options.
18948 - Change default loglevel to warn.
18949 - Make PidFile default to null rather than littering in your CWD.
18950 - OnionRouter config option is now obsolete. Instead it just checks
18952 - Moved to a single unified torrc file for both clients and servers.
18955 Changes in version 0.0.2pre14 - 2003-11-29
18956 o Robustness and bugfixes:
18957 - Force the admin to make the DataDirectory himself
18958 - to get ownership/permissions right
18959 - so clients no longer make a DataDirectory and then never use it
18960 - fix bug where a client who was offline for 45 minutes would never
18961 pull down a directory again
18962 - fix (or at least hide really well) the dns assert bug that was
18963 causing server crashes
18964 - warnings and improved robustness wrt clockskew for certs
18965 - use the native daemon(3) to daemonize, when available
18966 - exit if bind() fails
18967 - exit if neither socksport nor orport is defined
18968 - include our own tor_timegm (Win32 doesn't have its own)
18969 - bugfix for win32 with lots of connections
18970 - fix minor bias in PRNG
18971 - make dirserver more robust to corrupt cached directory
18974 - Wrote the design document (woo)
18976 o Circuit building and exit policies:
18977 - Circuits no longer try to use nodes that the directory has told them
18979 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18980 bitcounts (18.0.0.0/8).
18981 - Make AP connections standby for a circuit if no suitable circuit
18982 exists, rather than failing
18983 - Circuits choose exit node based on addr/port, exit policies, and
18984 which AP connections are standing by
18985 - Bump min pathlen from 2 to 3
18986 - Relay end cells have a payload to describe why the stream ended.
18987 - If the stream failed because of exit policy, try again with a new
18989 - Clients have a dns cache to remember resolved addresses.
18990 - Notice more quickly when we have no working circuits
18993 - APPort is now called SocksPort
18994 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18996 - RecommendedVersions is now a config variable rather than
18997 hardcoded (for dirservers)
18998 - Reloads config on HUP
18999 - Usage info on -h or --help
19000 - If you set User and Group config vars, it'll setu/gid to them.
19002 Changes in version 0.0.2pre13 - 2003-10-19
19003 o General stability:
19004 - SSL_write no longer fails when it returns WANTWRITE and the number
19005 of bytes in the buf has changed by the next SSL_write call.
19006 - Fix segfault fetching directory when network is down
19007 - Fix a variety of minor memory leaks
19008 - Dirservers reload the fingerprints file on HUP, so I don't have
19009 to take down the network when I approve a new router
19010 - Default server config file has explicit Address line to specify fqdn
19013 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19014 - Make listener connections not ever alloc bufs
19016 o Autoconf improvements:
19017 - don't clobber an external CFLAGS in ./configure
19018 - Make install now works
19019 - create var/lib/tor on make install
19020 - autocreate a tor.sh initscript to help distribs
19021 - autocreate the torrc and sample-server-torrc with correct paths
19023 o Log files and Daemonizing now work:
19024 - If --DebugLogFile is specified, log to it at -l debug
19025 - If --LogFile is specified, use it instead of commandline
19026 - If --RunAsDaemon is set, tor forks and backgrounds on startup