1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
5 Changes in version 0.3.3.6 - 2018-05-22
6 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
7 backports several important fixes from the 0.3.4.1-alpha.
9 The Tor 0.3.3 series includes controller support and other improvements
10 for v3 onion services, official support for embedding Tor within
11 other applications, and our first non-trivial module written in the
12 Rust programming language. (Rust is still not enabled by default when
13 building Tor.) And as usual, there are numerous other smaller bugfixes,
14 features, and improvements.
16 Below are the changes since 0.3.2.10. For a list of only the changes
17 since 0.3.3.5-rc, see the ChangeLog file.
19 o New system requirements:
20 - When built with Rust, Tor now depends on version 0.2.39 of the
21 libc crate. Closes tickets 25310 and 25664.
23 o Major bugfixes (security, directory authority, denial-of-service):
24 - Fix a bug that could have allowed an attacker to force a
25 directory authority to use up all its RAM by passing it a
26 maliciously crafted protocol versions string. Fixes bug 25517;
27 bugfix on 0.2.9.4-alpha. This issue is also tracked as
30 o Major features (embedding):
31 - There is now a documented stable API for programs that need to
32 embed Tor. See tor_api.h for full documentation and known bugs.
34 - Tor now has support for restarting in the same process.
35 Controllers that run Tor using the "tor_api.h" interface can now
36 restart Tor after Tor has exited. This support is incomplete,
37 however: we fixed crash bugs that prevented it from working at
38 all, but many bugs probably remain, including a possibility of
39 security issues. Implements ticket 24581.
41 o Major features (IPv6, directory documents):
42 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
43 consensus. This information makes it easier for IPv6 clients to
44 bootstrap and choose reachable entry guards. Implements ticket 23826.
45 - Add consensus method 28, which removes IPv6 ORPorts from
46 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
47 are redundant in microdescs. This change will be used by Tor clients
48 on 0.2.8.x and later. (That is to say, with all Tor clients that
49 have IPv6 bootstrap and guard support.) Implements ticket 23828.
50 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
51 set by different numbers of authorities. Fixes 23870
54 o Major features (onion service v3, control port):
55 - The control port now supports commands and events for v3 onion
56 services. It is now possible to create ephemeral v3 services using
57 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
58 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
59 DEL_ONION) have been extended to support v3 onion services. Closes
60 ticket 20699; implements proposal 284.
62 o Major features (onion services):
63 - Provide torrc options to pin the second and third hops of onion
64 service circuits to a list of nodes. The option HSLayer2Guards
65 pins the second hop, and the option HSLayer3Guards pins the third
66 hop. These options are for use in conjunction with experiments
67 with "vanguards" for preventing guard enumeration attacks. Closes
69 - When v3 onion service clients send introduce cells, they now
70 include the IPv6 address of the rendezvous point, if it has one.
71 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
72 in future Tor versions, IPv6-only v3 single onion services will be
73 able to use IPv6 addresses to connect directly to the rendezvous
74 point. Closes ticket 23577. Patch by Neel Chauhan.
76 o Major features (rust, portability, experimental):
77 - Tor now ships with an optional implementation of one of its
78 smaller modules (protover.c) in the Rust programming language. To
79 try it out, install a Rust build environment, and configure Tor
80 with "--enable-rust --enable-cargo-online-mode". This should not
81 cause any user-visible changes, but should help us gain more
82 experience with Rust, and plan future Rust integration work.
83 Implementation by Chelsea Komlo. Closes ticket 22840.
85 o Minor features (storage, configuration):
86 - Users can store cached directory documents somewhere other than
87 the DataDirectory by using the CacheDirectory option. Similarly,
88 the storage location for relay's keys can be overridden with the
89 KeyDirectory option. Closes ticket 22703.
91 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
92 - When directory authorities read a zero-byte bandwidth file, they
93 would previously log a warning with the contents of an
94 uninitialised buffer. They now log a warning about the empty file
95 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
97 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
98 - Avoid a rare assertion failure in the circuit build timeout code
99 if we fail to allow any circuits to actually complete. Fixes bug
100 25733; bugfix on 0.2.2.2-alpha.
102 o Major bugfixes (netflow padding):
103 - Stop adding unneeded channel padding right after we finish
104 flushing to a connection that has been trying to flush for many
105 seconds. Instead, treat all partial or complete flushes as
106 activity on the channel, which will defer the time until we need
107 to add padding. This fix should resolve confusing and scary log
108 messages like "Channel padding timeout scheduled 221453ms in the
109 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
111 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
112 - Correctly detect when onion services get disabled after HUP.
113 Fixes bug 25761; bugfix on 0.3.2.1.
115 o Major bugfixes (performance, load balancing):
116 - Directory authorities no longer vote in favor of the Guard flag
117 for relays without directory support. Starting in Tor
118 0.3.0.1-alpha, clients have been avoiding using such relays in the
119 Guard position, leading to increasingly broken load balancing for
120 the 5%-or-so of Guards that don't advertise directory support.
121 Fixes bug 22310; bugfix on 0.3.0.6.
123 o Major bugfixes (relay):
124 - If we have failed to connect to a relay and received a connection
125 refused, timeout, or similar error (at the TCP level), do not try
126 that same address/port again for 60 seconds after the failure has
127 occurred. Fixes bug 24767; bugfix on 0.0.6.
129 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
130 - Impose a limit on circuit cell queue size. The limit can be
131 controlled by a consensus parameter. Fixes bug 25226; bugfix on
134 o Minor features (cleanup):
135 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
136 when it stops. Closes ticket 23271.
138 o Minor features (compatibility, backport from 0.3.4.1-alpha):
139 - Avoid some compilation warnings with recent versions
140 of LibreSSL. Closes ticket 26006.
142 o Minor features (config options):
143 - Change the way the default value for MaxMemInQueues is calculated.
144 We now use 40% of the hardware RAM if the system has 8 GB RAM or
145 more. Otherwise we use the former value of 75%. Closes
148 o Minor features (continuous integration):
149 - Update the Travis CI configuration to use the stable Rust channel,
150 now that we have decided to require that. Closes ticket 25714.
152 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
153 - Our .travis.yml configuration now includes support for testing
154 the results of "make distcheck". (It's not uncommon for "make check" to
155 pass but "make distcheck" to fail.) Closes ticket 25814.
156 - Our Travis CI configuration now integrates with the Coveralls coverage
157 analysis tool. Closes ticket 25818.
159 o Minor features (defensive programming):
160 - Most of the functions in Tor that free objects have been replaced
161 with macros that free the objects and set the corresponding
162 pointers to NULL. This change should help prevent a large class of
163 dangling pointer bugs. Closes ticket 24337.
164 - Where possible, the tor_free() macro now only evaluates its input
165 once. Part of ticket 24337.
166 - Check that microdesc ed25519 ids are non-zero in
167 node_get_ed25519_id() before returning them. Implements ticket
168 24001, patch by "aruna1234".
170 o Minor features (directory authority):
171 - When directory authorities are unable to add signatures to a
172 pending consensus, log the reason why. Closes ticket 24849.
174 o Minor features (embedding):
175 - Tor can now start with a preauthenticated control connection
176 created by the process that launched it. This feature is meant for
177 use by programs that want to launch and manage a Tor process
178 without allowing other programs to manage it as well. For more
179 information, see the __OwningControllerFD option documented in
180 control-spec.txt. Closes ticket 23900.
181 - On most errors that would cause Tor to exit, it now tries to
182 return from the tor_main() function, rather than calling the
183 system exit() function. Most users won't notice a difference here,
184 but it should be significant for programs that run Tor inside
185 a separate thread: they should now be able to survive Tor's exit
186 conditions rather than having Tor shut down the entire process.
188 - Applications that want to embed Tor can now tell Tor not to
189 register any of its own POSIX signal handlers, using the
190 __DisableSignalHandlers option. Closes ticket 24588.
192 o Minor features (fallback directory list):
193 - Avoid selecting fallbacks that change their IP addresses too
194 often. Select more fallbacks by ignoring the Guard flag, and
195 allowing lower cutoffs for the Running and V2Dir flags. Also allow
196 a lower bandwidth, and a higher number of fallbacks per operator
197 (5% of the list). Implements ticket 24785.
198 - Update the fallback whitelist and blacklist based on opt-ins and
199 relay changes. Closes tickets 22321, 24678, 22527, 24135,
202 o Minor features (fallback directory mirror configuration):
203 - Add a nickname to each fallback in a C comment. This makes it
204 easier for operators to find their relays, and allows stem to use
205 nicknames to identify fallbacks. Implements ticket 24600.
206 - Add a type and version header to the fallback directory mirror
207 file. Also add a delimiter to the end of each fallback entry. This
208 helps external parsers like stem and Relay Search. Implements
210 - Add an extrainfo cache flag for each fallback in a C comment. This
211 allows stem to use fallbacks to fetch extra-info documents, rather
212 than using authorities. Implements ticket 22759.
213 - Add the generateFallbackDirLine.py script for automatically
214 generating fallback directory mirror lines from relay fingerprints.
215 No more typos! Add the lookupFallbackDirContact.py script for
216 automatically looking up operator contact info from relay
217 fingerprints. Implements ticket 24706, patch by teor and atagar.
218 - Reject any fallback directory mirror that serves an expired
219 consensus. Implements ticket 20942, patch by "minik".
220 - Remove commas and equals signs from external string inputs to the
221 fallback list. This avoids format confusion attacks. Implements
223 - Remove the "weight=10" line from fallback directory mirror
224 entries. Ticket 24681 will maintain the current fallback weights
225 by changing Tor's default fallback weight to 10. Implements
227 - Stop logging excessive information about fallback netblocks.
228 Implements ticket 24791.
230 o Minor features (forward-compatibility):
231 - If a relay supports some link authentication protocol that we do
232 not recognize, then include that relay's ed25519 key when telling
233 other relays to extend to it. Previously, we treated future
234 versions as if they were too old to support ed25519 link
235 authentication. Closes ticket 20895.
237 o Minor features (geoip):
238 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2
239 Country database. Closes ticket 26104.
241 o Minor features (heartbeat):
242 - Add onion service information to our heartbeat logs, displaying
243 stats about the activity of configured onion services. Closes
246 o Minor features (instrumentation, development):
247 - Add the MainloopStats option to allow developers to get
248 instrumentation information from the main event loop via the
249 heartbeat messages. We hope to use this to improve Tor's behavior
250 when it's trying to sleep. Closes ticket 24605.
252 o Minor features (IPv6):
253 - Make IPv6-only clients wait for microdescs for relays, even if we
254 were previously using descriptors (or were using them as a bridge)
255 and have a cached descriptor for them. Implements ticket 23827.
256 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
257 them, rather than waiting to download microdescriptors.
258 Implements ticket 23827.
260 o Minor features (log messages):
261 - Improve log message in the out-of-memory handler to include
262 information about memory usage from the different compression
263 backends. Closes ticket 25372.
264 - Improve a warning message that happens when we fail to re-parse an
265 old router because of an expired certificate. Closes ticket 20020.
266 - Make the log more quantitative when we hit MaxMemInQueues
267 threshold exposing some values. Closes ticket 24501.
269 o Minor features (logging):
270 - Clarify the log messages produced when getrandom() or a related
271 entropy-generation mechanism gives an error. Closes ticket 25120.
272 - Added support for the Android logging subsystem. Closes
275 o Minor features (performance):
276 - Support predictive circuit building for onion service circuits
277 with multiple layers of guards. Closes ticket 23101.
278 - Use stdatomic.h where available, rather than mutexes, to implement
279 atomic_counter_t. Closes ticket 23953.
281 o Minor features (performance, 32-bit):
282 - Improve performance on 32-bit systems by avoiding 64-bit division
283 when calculating the timestamp in milliseconds for channel padding
284 computations. Implements ticket 24613.
285 - Improve performance on 32-bit systems by avoiding 64-bit division
286 when timestamping cells and buffer chunks for OOM calculations.
287 Implements ticket 24374.
289 o Minor features (performance, OSX, iOS):
290 - Use the mach_approximate_time() function (when available) to
291 implement coarse monotonic time. Having a coarse time function
292 should avoid a large number of system calls, and improve
293 performance slightly, especially under load. Closes ticket 24427.
295 o Minor features (performance, windows):
296 - Improve performance on Windows Vista and Windows 7 by adjusting
297 TCP send window size according to the recommendation from
298 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
301 o Major features (relay):
302 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
303 operator to use a more reasonable ("reduced") exit policy, rather
304 than the default one. If you want to run an exit node without
305 thinking too hard about which ports to allow, this one is for you.
306 Closes ticket 13605. Patch from Neel Chauhan.
308 o Minor features (sandbox):
309 - Explicitly permit the poll() system call when the Linux
310 seccomp2-based sandbox is enabled: apparently, some versions of
311 libc use poll() when calling getpwnam(). Closes ticket 25313.
313 o Minor features (testing):
314 - Add a "make test-rust" target to run the rust tests only. Closes
317 o Minor features (testing, debugging, embedding):
318 - For development purposes, Tor now has a mode in which it runs for
319 a few seconds, then stops, and starts again without exiting the
320 process. This mode is meant to help us debug various issues with
321 ticket 23847. To use this feature, compile with
322 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
323 environment variable. This is expected to crash a lot, and is
324 really meant for developers only. It will likely be removed in a
325 future release. Implements ticket 24583.
327 o Minor bugfixes (build, rust):
328 - Fix output of autoconf checks to display success messages for Rust
329 dependencies and a suitable rustc compiler version. Fixes bug
330 24612; bugfix on 0.3.1.3-alpha.
331 - Don't pass the --quiet option to cargo: it seems to suppress some
332 errors, which is not what we want to do when building. Fixes bug
333 24518; bugfix on 0.3.1.7.
334 - Build correctly when building from outside Tor's source tree with
335 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
338 o Minor bugfixes (C correctness):
339 - Fix a very unlikely (impossible, we believe) null pointer
340 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
341 Coverity; this is CID 1430932.
343 o Minor bugfixes (channel, client):
344 - Better identify client connection when reporting to the geoip
345 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
347 o Minor bugfixes (circuit, cannibalization):
348 - Don't cannibalize preemptively-built circuits if we no longer
349 recognize their first hop. This situation can happen if our Guard
350 relay went off the consensus after the circuit was created. Fixes
351 bug 24469; bugfix on 0.0.6.
353 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
354 - Don't consider Tor running as a client if the ControlPort is open,
355 but no actual client ports are open. Fixes bug 26062; bugfix
358 o Minor bugfixes (compilation):
359 - Fix a C99 compliance issue in our configuration script that caused
360 compilation issues when compiling Tor with certain versions of
361 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
363 o Minor bugfixes (controller):
364 - Restore the correct operation of the RESOLVE command, which had
365 been broken since we added the ability to enable/disable DNS on
366 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
367 - Avoid a (nonfatal) assertion failure when extending a one-hop
368 circuit from the controller to become a multihop circuit. Fixes
369 bug 24903; bugfix on 0.2.5.2-alpha.
371 o Minor bugfixes (correctness):
372 - Remove a nonworking, unnecessary check to see whether a circuit
373 hop's identity digest was set when the circuit failed. Fixes bug
374 24927; bugfix on 0.2.4.4-alpha.
376 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
377 - Upon receiving a malformed connected cell, stop processing the cell
378 immediately. Previously we would mark the connection for close, but
379 continue processing the cell as if the connection were open. Fixes bug
380 26072; bugfix on 0.2.4.7-alpha.
382 o Minor bugfixes (directory authorities, IPv6):
383 - When creating a routerstatus (vote) from a routerinfo (descriptor),
384 set the IPv6 address to the unspecified IPv6 address, and
385 explicitly initialize the port to zero. Fixes bug 24488; bugfix
388 o Minor bugfixes (documentation):
389 - Document that the PerConnBW{Rate,Burst} options will fall back to
390 their corresponding consensus parameters only if those parameters
391 are set. Previously we had claimed that these values would always
392 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
394 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
395 - Stop saying in the manual that clients cache ipv4 dns answers
396 from exit relays. We haven't used them since 0.2.6.3-alpha, and
397 in ticket 24050 we stopped even caching them as of 0.3.2.6-alpha,
398 but we forgot to say so in the man page. Fixes bug 26052; bugfix
401 o Minor bugfixes (exit relay DNS retries):
402 - Re-attempt timed-out DNS queries 3 times before failure, since our
403 timeout is 5 seconds for them, but clients wait 10-15. Also allow
404 slightly more timeouts per resolver when an exit has multiple
405 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
407 o Minor bugfixes (fallback directory mirrors):
408 - Make updateFallbackDirs.py search harder for python. (Some OSs
409 don't put it in /usr/bin.) Fixes bug 24708; bugfix
412 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
413 - When hibernating, close connections normally and allow them to
414 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
416 - Do not attempt to launch self-reachability tests when entering
417 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
418 - Resolve several bugs related to descriptor fetching on bridge
419 clients with bandwidth accounting enabled. (This combination is
420 not recommended!) Fixes a case of bug 12062; bugfix
422 - When hibernating, do not attempt to launch DNS checks. Fixes a
423 case of bug 12062; bugfix on 0.1.2.2-alpha.
424 - When hibernating, do not try to upload or download descriptors.
425 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
427 o Minor bugfixes (IPv6, bridges):
428 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
429 bugfix on 0.2.8.2-alpha.
430 - Tor now sets IPv6 address in the routerstatus as well as in the
431 router descriptors when updating addresses for a bridge. Closes
432 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
434 o Minor bugfixes (Linux seccomp2 sandbox):
435 - When running with the sandbox enabled, reload configuration files
436 correctly even when %include was used. Previously we would crash.
437 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
439 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
440 - Allow the nanosleep() system call, which glibc uses to implement
441 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
443 o Minor bugfixes (logging):
444 - Fix a (mostly harmless) race condition when invoking
445 LOG_PROTOCOL_WARN message from a subthread while the torrc options
446 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
448 o Minor bugfixes (man page, SocksPort):
449 - Remove dead code from the old "SocksSocket" option, and rename
450 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
451 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
453 o Minor bugfixes (memory leaks):
454 - Avoid possible at-exit memory leaks related to use of Libevent's
455 event_base_once() function. (This function tends to leak memory if
456 the event_base is closed before the event fires.) Fixes bug 24584;
457 bugfix on 0.2.8.1-alpha.
458 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
461 o Minor bugfixes (network IPv6 test):
462 - Tor's test scripts now check if "ping -6 ::1" works when the user
463 runs "make test-network-all". Fixes bug 24677; bugfix on
464 0.2.9.3-alpha. Patch by "ffmancera".
466 o Major bugfixes (networking):
467 - Tor will no longer reject IPv6 address strings from Tor Browser
468 when they are passed as hostnames in SOCKS5 requests. Fixes bug
469 25036, bugfix on Tor 0.3.1.2.
471 o Minor bugfixes (networking):
472 - string_is_valid_hostname() will not consider IP strings to be
473 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
475 o Minor bugfixes (onion service v3):
476 - Avoid an assertion failure when the next onion service
477 descriptor rotation type is out of sync with the consensus's
478 valid-after time. Instead, log a warning message with extra
479 information, so we can better hunt down the cause of this
480 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
482 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
483 - Fix a memory leak when a v3 onion service is configured and gets a
484 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
485 - When parsing the descriptor signature, look for the token plus an
486 extra white-space at the end. This is more correct but also will
487 allow us to support new fields that might start with "signature".
488 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
490 o Minor bugfixes (onion services):
491 - If we are configured to offer a single onion service, don't log
492 long-term established one hop rendezvous points in the heartbeat.
493 Fixes bug 25116; bugfix on 0.2.9.6-rc.
495 o Minor bugfixes (performance):
496 - Reduce the number of circuits that will be opened at once during
497 the circuit build timeout phase. This is done by increasing the
498 idle timeout to 3 minutes, and lowering the maximum number of
499 concurrent learning circuits to 10. Fixes bug 24769; bugfix
501 - Avoid calling protocol_list_supports_protocol() from inside tight
502 loops when running with cached routerinfo_t objects. Instead,
503 summarize the relevant protocols as flags in the routerinfo_t, as
504 we do for routerstatus_t objects. This change simplifies our code
505 a little, and saves a large amount of short-term memory allocation
506 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
508 o Minor bugfixes (performance, timeouts):
509 - Consider circuits for timeout as soon as they complete a hop. This
510 is more accurate than applying the timeout in
511 circuit_expire_building() because that function is only called
512 once per second, which is now too slow for typical timeouts on the
513 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
514 - Use onion service circuits (and other circuits longer than 3 hops)
515 to calculate a circuit build timeout. Previously, Tor only
516 calculated its build timeout based on circuits that planned to be
517 exactly 3 hops long. With this change, we include measurements
518 from all circuits at the point where they complete their third
519 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
521 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
522 - Avoid a crash when running with DirPort set but ORPort tuned off.
523 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
525 o Minor bugfixes (Rust FFI):
526 - Fix a minor memory leak which would happen whenever the C code
527 would call the Rust implementation of
528 protover_get_supported_protocols(). This was due to the C version
529 returning a static string, whereas the Rust version newly allocated
530 a CString to pass accross the FFI boundary. Consequently, the C
531 code was not expecting to need to free() what it was given. Fixes
532 bug 25127; bugfix on 0.3.2.1-alpha.
534 o Minor bugfixes (spelling):
535 - Use the "misspell" tool to detect and fix typos throughout the
536 source code. Fixes bug 23650; bugfix on various versions of Tor.
537 Patch from Deepesh Pathak.
539 o Minor bugfixes (testing):
540 - Avoid intermittent test failures due to a test that had relied on
541 onion service introduction point creation finishing within 5
542 seconds of real clock time. Fixes bug 25450; bugfix
544 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
545 bugfix on 0.2.3.1-alpha.
547 o Minor bugfixes (unit test, monotonic time):
548 - Increase a constant (1msec to 10msec) in the monotonic time test
549 that makes sure the nsec/usec/msec times read are synchronized.
550 This change was needed to accommodate slow systems like armel or
551 when the clock_gettime() is not a VDSO on the running kernel.
552 Fixes bug 25113; bugfix on 0.2.9.1.
554 o Code simplification and refactoring:
555 - Move the list of default directory authorities to its own file.
556 Closes ticket 24854. Patch by "beastr0".
557 - Remove the old (deterministic) directory retry logic entirely:
558 We've used exponential backoff exclusively for some time. Closes
560 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
562 - Remove a series of counters used to track circuit extend attempts
563 and connection status but that in reality we aren't using for
564 anything other than stats logged by a SIGUSR1 signal. Closes
566 - Remove /usr/athena from search path in configure.ac. Closes
568 - Remove duplicate code in node_has_curve25519_onion_key() and
569 node_get_curve25519_onion_key(), and add a check for a zero
570 microdesc curve25519 onion key. Closes ticket 23966, patch by
571 "aruna1234" and teor.
572 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
573 memory allocations with large numbers of OR connections (e.g.
574 relays). Closes ticket 24119.
575 - Separate the function that deletes ephemeral files when Tor
577 - Small changes to Tor's buf_t API to make it suitable for use as a
578 general-purpose safe string constructor. Closes ticket 22342.
579 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
580 avoid source code identifier confusion. Closes ticket 24467.
581 - The tor_git_revision[] constant no longer needs to be redeclared
582 by everything that links against the rest of Tor. Done as part of
583 ticket 23845, to simplify our external API.
584 - We make extend_info_from_node() use node_get_curve25519_onion_key()
585 introduced in ticket 23577 to access the curve25519 public keys
586 rather than accessing it directly. Closes ticket 23760. Patch by
588 - Add a function to log channels' scheduler state changes to aid
589 debugging efforts. Closes ticket 24531.
592 - Improved the documentation of AccountingStart parameter. Closes
594 - Update the documentation for "Log" to include the current list of
595 logging domains. Closes ticket 25378.
596 - Add documentation on how to build tor with Rust dependencies
597 without having to be online. Closes ticket 22907; bugfix
599 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
600 traffic. Closes ticket 24318.
601 - Document that OutboundBindAddress doesn't apply to DNS requests.
602 Closes ticket 22145. Patch from Aruna Maurya.
604 o Code simplification and refactoring (channels):
605 - Remove the incoming and outgoing channel queues. These were never
606 used, but still took up a step in our fast path.
607 - The majority of the channel unit tests have been rewritten and the
608 code coverage has now been raised to 83.6% for channel.c. Closes
610 - Remove other dead code from the channel subsystem: All together,
611 this cleanup has removed more than 1500 lines of code overall and
612 adding very little except for unit test.
614 o Code simplification and refactoring (circuit rendezvous):
615 - Split the client-side rendezvous circuit lookup into two
616 functions: one that returns only established circuits and another
617 that returns all kinds of circuits. Closes ticket 23459.
619 o Code simplification and refactoring (controller):
620 - Make most of the variables in networkstatus_getinfo_by_purpose()
621 const. Implements ticket 24489.
623 o Documentation (backport from 0.3.4.1-alpha):
624 - Correct an IPv6 error in the documentation for ExitPolicy.
625 Closes ticket 25857. Patch from "CTassisF".
627 o Documentation (man page):
628 - The HiddenServiceVersion torrc option accepts only one number:
629 either version 2 or 3. Closes ticket 25026; bugfix
632 o Documentation (manpage, denial of service):
633 - Provide more detail about the denial-of-service options, by
634 listing each mitigation and explaining how they relate. Closes
638 Changes in version 0.3.2.10 - 2018-03-03
639 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
640 backports a number of bugfixes, including important fixes for security
643 It includes an important security fix for a remote crash attack
644 against directory authorities, tracked as TROVE-2018-001.
646 Additionally, it backports a fix for a bug whose severity we have
647 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
648 triggered in order to crash relays with a use-after-free pattern. As
649 such, we are now tracking that bug as TROVE-2018-002 and
650 CVE-2018-0491, and backporting it to earlier releases. This bug
651 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
654 This release also backports our new system for improved resistance to
655 denial-of-service attacks against relays.
657 This release also fixes several minor bugs and annoyances from
660 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
661 today, for the fix to TROVE-2018-002. Directory authorities should
662 also upgrade. (Relays on earlier versions might want to update too for
663 the DoS mitigations.)
665 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
666 - Fix a protocol-list handling bug that could be used to remotely crash
667 directory authorities with a null-pointer exception. Fixes bug 25074;
668 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
671 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
672 - Avoid adding the same channel twice in the KIST scheduler pending
673 list, which could lead to remote denial-of-service use-after-free
674 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
676 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
677 - Give relays some defenses against the recent network overload. We
678 start with three defenses (default parameters in parentheses).
679 First: if a single client address makes too many concurrent
680 connections (>100), hang up on further connections. Second: if a
681 single client address makes circuits too quickly (more than 3 per
682 second, with an allowed burst of 90) while also having too many
683 connections open (3), refuse new create cells for the next while
684 (1-2 hours). Third: if a client asks to establish a rendezvous
685 point to you directly, ignore the request. These defenses can be
686 manually controlled by new torrc options, but relays will also
687 take guidance from consensus parameters, so there's no need to
688 configure anything manually. Implements ticket 24902.
690 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
691 - Fix an "off by 2" error in counting rendezvous failures on the
692 onion service side. While we thought we would stop the rendezvous
693 attempt after one failed circuit, we were actually making three
694 circuit attempts before giving up. Now switch to a default of 2,
695 and allow the consensus parameter "hs_service_max_rdv_failures" to
696 override. Fixes bug 24895; bugfix on 0.0.6.
697 - New-style (v3) onion services now obey the "max rendezvous circuit
698 attempts" logic. Previously they would make as many rendezvous
699 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
700 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
702 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
703 - Add Link protocol version 5 to the supported protocols list. Fixes
704 bug 25070; bugfix on 0.3.1.1-alpha.
706 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
707 - Fix a set of false positives where relays would consider
708 connections to other relays as being client-only connections (and
709 thus e.g. deserving different link padding schemes) if those
710 relays fell out of the consensus briefly. Now we look only at the
711 initial handshake and whether the connection authenticated as a
712 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
714 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
715 - The scheduler subsystem was failing to promptly notice changes in
716 consensus parameters, making it harder to switch schedulers
717 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
719 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
720 - Make our OOM handler aware of the geoip client history cache so it
721 doesn't fill up the memory. This check is important for IPv6 and
722 our DoS mitigation subsystem. Closes ticket 25122.
724 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
725 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
726 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
727 since they neither disabled TLS 1.3 nor enabled any of the
728 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
731 o Minor features (geoip):
732 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
735 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
736 - When logging a failure to create an onion service's descriptor,
737 also log what the problem with the descriptor was. Diagnostic
740 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
741 - Use the actual observed address of an incoming relay connection,
742 not the canonical address of the relay from its descriptor, when
743 making decisions about how to handle the incoming connection.
744 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
746 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
747 - Fix a possible crash on malformed consensus. If a consensus had
748 contained an unparseable protocol line, it could have made clients
749 and relays crash with a null-pointer exception. To exploit this
750 issue, however, an attacker would need to be able to subvert the
751 directory authority system. Fixes bug 25251; bugfix on
752 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
754 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
755 - Directory authorities, when refusing a descriptor from a rejected
756 relay, now explicitly tell the relay (in its logs) to set a valid
757 ContactInfo address and contact the bad-relays@ mailing list.
758 Fixes bug 25170; bugfix on 0.2.9.1.
760 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
761 - When building with Rust on OSX, link against libresolv, to work
762 around the issue at https://github.com/rust-lang/rust/issues/46797.
763 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
765 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
766 - Remove a BUG() statement when a client fetches an onion descriptor
767 that has a lower revision counter than the one in its cache. This
768 can happen in normal circumstances due to HSDir desync. Fixes bug
769 24976; bugfix on 0.3.2.1-alpha.
771 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
772 - Don't treat inability to store a cached consensus object as a bug:
773 it can happen normally when we are out of disk space. Fixes bug
774 24859; bugfix on 0.3.1.1-alpha.
776 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
777 - Improve the performance of our consensus-diff application code
778 when Tor is built with the --enable-fragile-hardening option set.
779 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
781 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
782 - Don't exit the Tor process if setrlimit() fails to change the file
783 limit (which can happen sometimes on some versions of OSX). Fixes
784 bug 21074; bugfix on 0.0.9pre5.
786 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
787 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
789 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
790 bugfix on 0.2.9.4-alpha.
792 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
793 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
794 25005; bugfix on 0.3.2.7-rc.
796 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
797 - Look at the "HSRend" protocol version, not the "HSDir" protocol
798 version, when deciding whether a consensus entry can support the
799 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
800 bugfix on 0.3.2.1-alpha.
802 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
803 - Update the "rust dependencies" submodule to be a project-level
804 repository, rather than a user repository. Closes ticket 25323.
806 o Documentation (backport from 0.3.3.1-alpha)
807 - Document that operators who run more than one relay or bridge are
808 expected to set MyFamily and ContactInfo correctly. Closes
812 Changes in version 0.3.2.9 - 2018-01-09
813 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
815 The 0.3.2 series includes our long-anticipated new onion service
816 design, with numerous security features. (For more information, see
817 our blog post at https://blog.torproject.org/fall-harvest.) We also
818 have a new circuit scheduler algorithm for improved performance on
819 relays everywhere (see https://blog.torproject.org/kist-and-tell),
820 along with many smaller features and bugfixes.
822 Per our stable release policy, we plan to support each stable release
823 series for at least the next nine months, or for three months after
824 the first stable release of the next series: whichever is longer. If
825 you need a release with long-term support, we recommend that you stay
826 with the 0.2.9 series.
828 Below is a list of the changes since 0.3.1.7. For a list of all
829 changes since 0.3.2.8-rc, see the ChangeLog file.
831 o Directory authority changes:
832 - Add "Bastet" as a ninth directory authority to the default list.
834 - The directory authority "Longclaw" has changed its IP address.
836 - Remove longclaw's IPv6 address, as it will soon change. Authority
837 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
838 3/8 directory authorities with IPv6 addresses, but there are also
839 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
840 - Add an IPv6 address for the "bastet" directory authority. Closes
843 o Major features (next-generation onion services):
844 - Tor now supports the next-generation onion services protocol for
845 clients and services! As part of this release, the core of
846 proposal 224 has been implemented and is available for
847 experimentation and testing by our users. This newer version of
848 onion services ("v3") features many improvements over the legacy
851 a) Better crypto (replaced SHA1/DH/RSA1024
852 with SHA3/ed25519/curve25519)
854 b) Improved directory protocol, leaking much less information to
857 c) Improved directory protocol, with smaller surface for
860 d) Better onion address security against impersonation.
862 e) More extensible introduction/rendezvous protocol.
864 f) A cleaner and more modular codebase.
866 You can identify a next-generation onion address by its length:
867 they are 56 characters long, as in
868 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
870 In the future, we will release more options and features for v3
871 onion services, but we first need a testing period, so that the
872 current codebase matures and becomes more robust. Planned features
873 include: offline keys, advanced client authorization, improved
874 guard algorithms, and statistics. For full details, see
877 Legacy ("v2") onion services will still work for the foreseeable
878 future, and will remain the default until this new codebase gets
879 tested and hardened. Service operators who want to experiment with
880 the new system can use the 'HiddenServiceVersion 3' torrc
881 directive along with the regular onion service configuration
882 options. For more information, see our blog post at
883 "https://blog.torproject.org/fall-harvest". Enjoy!
885 o Major feature (scheduler, channel):
886 - Tor now uses new schedulers to decide which circuits should
887 deliver cells first, in order to improve congestion at relays. The
888 first type is called "KIST" ("Kernel Informed Socket Transport"),
889 and is only available on Linux-like systems: it uses feedback from
890 the kernel to prevent the kernel's TCP buffers from growing too
891 full. The second new scheduler type is called "KISTLite": it
892 behaves the same as KIST, but runs on systems without kernel
893 support for inspecting TCP implementation details. The old
894 scheduler is still available, under the name "Vanilla". To change
895 the default scheduler preference order, use the new "Schedulers"
896 option. (The default preference order is "KIST,KISTLite,Vanilla".)
898 Matt Traudt implemented KIST, based on research by Rob Jansen,
899 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
900 more information, see the design paper at
901 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
902 followup implementation paper at https://arxiv.org/abs/1709.01044.
903 Closes ticket 12541. For more information, see our blog post at
904 "https://blog.torproject.org/kist-and-tell".
906 o Major bugfixes (security, general):
907 - Fix a denial of service bug where an attacker could use a
908 malformed directory object to cause a Tor instance to pause while
909 OpenSSL would try to read a passphrase from the terminal. (Tor
910 instances run without a terminal, which is the case for most Tor
911 packages, are not impacted.) Fixes bug 24246; bugfix on every
912 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
913 Found by OSS-Fuzz as testcase 6360145429790720.
915 o Major bugfixes (security, directory authority):
916 - Fix a denial of service issue where an attacker could crash a
917 directory authority using a malformed router descriptor. Fixes bug
918 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
921 o Major bugfixes (security, onion service v2):
922 - Fix a use-after-free error that could crash v2 Tor onion services
923 when they failed to open circuits while expiring introduction
924 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
925 also tracked as TROVE-2017-013 and CVE-2017-8823.
926 - When checking for replays in the INTRODUCE1 cell data for a
927 (legacy) onion service, correctly detect replays in the RSA-
928 encrypted part of the cell. We were previously checking for
929 replays on the entire cell, but those can be circumvented due to
930 the malleability of Tor's legacy hybrid encryption. This fix helps
931 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
932 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
935 o Major bugfixes (security, relay):
936 - When running as a relay, make sure that we never build a path
937 through ourselves, even in the case where we have somehow lost the
938 version of our descriptor appearing in the consensus. Fixes part
939 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
940 as TROVE-2017-012 and CVE-2017-8822.
941 - When running as a relay, make sure that we never choose ourselves
942 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
943 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
945 o Major bugfixes (bootstrapping):
946 - Fetch descriptors aggressively whenever we lack enough to build
947 circuits, regardless of how many descriptors we are missing.
948 Previously, we would delay launching the fetch when we had fewer
949 than 15 missing descriptors, even if some of those descriptors
950 were blocking circuits from building. Fixes bug 23985; bugfix on
951 0.1.1.11-alpha. The effects of this bug became worse in
952 0.3.0.3-alpha, when we began treating missing descriptors from our
953 primary guards as a reason to delay circuits.
954 - Don't try fetching microdescriptors from relays that have failed
955 to deliver them in the past. Fixes bug 23817; bugfix
958 o Major bugfixes (circuit prediction):
959 - Fix circuit prediction logic so that a client doesn't treat a port
960 as being "handled" by a circuit if that circuit already has
961 isolation settings on it. This change should make Tor clients more
962 responsive by improving their chances of having a pre-created
963 circuit ready for use when a request arrives. Fixes bug 18859;
964 bugfix on 0.2.3.3-alpha.
966 o Major bugfixes (exit relays, DNS):
967 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
968 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
969 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
970 identifying and finding a workaround to this bug and to Moritz,
971 Arthur Edelstein, and Roger for helping to track it down and
974 o Major bugfixes (relay, crash, assertion failure):
975 - Fix a timing-based assertion failure that could occur when the
976 circuit out-of-memory handler freed a connection's output buffer.
977 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
979 o Major bugfixes (usability, control port):
980 - Report trusted clock skew indications as bootstrap errors, so
981 controllers can more easily alert users when their clocks are
982 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
984 o Minor features (bridge):
985 - Bridge relays can now set the BridgeDistribution config option to
986 add a "bridge-distribution-request" line to their bridge
987 descriptor, which tells BridgeDB how they'd like their bridge
988 address to be given out. (Note that as of Oct 2017, BridgeDB does
989 not yet implement this feature.) As a side benefit, this feature
990 provides a way to distinguish bridge descriptors from non-bridge
991 descriptors. Implements tickets 18329.
992 - When handling the USERADDR command on an ExtOrPort, warn when the
993 transports provides a USERADDR with no port. In a future version,
994 USERADDR commands of this format may be rejected. Detects problems
995 related to ticket 23080.
997 o Minor features (bug detection):
998 - Log a warning message with a stack trace for any attempt to call
999 get_options() during option validation. This pattern has caused
1000 subtle bugs in the past. Closes ticket 22281.
1002 o Minor features (build, compilation):
1003 - The "check-changes" feature is now part of the "make check" tests;
1004 we'll use it to try to prevent misformed changes files from
1005 accumulating. Closes ticket 23564.
1006 - Tor builds should now fail if there are any mismatches between the
1007 C type representing a configuration variable and the C type the
1008 data-driven parser uses to store a value there. Previously, we
1009 needed to check these by hand, which sometimes led to mistakes.
1010 Closes ticket 23643.
1012 o Minor features (client):
1013 - You can now use Tor as a tunneled HTTP proxy: use the new
1014 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
1015 requests. Closes ticket 22407.
1016 - Add an extra check to make sure that we always use the newer guard
1017 selection code for picking our guards. Closes ticket 22779.
1018 - When downloading (micro)descriptors, don't split the list into
1019 multiple requests unless we want at least 32 descriptors.
1020 Previously, we split at 4, not 32, which led to significant
1021 overhead in HTTP request size and degradation in compression
1022 performance. Closes ticket 23220.
1023 - Improve log messages when missing descriptors for primary guards.
1024 Resolves ticket 23670.
1026 o Minor features (command line):
1027 - Add a new commandline option, --key-expiration, which prints when
1028 the current signing key is going to expire. Implements ticket
1029 17639; patch by Isis Lovecruft.
1031 o Minor features (control port):
1032 - If an application tries to use the control port as an HTTP proxy,
1033 respond with a meaningful "This is the Tor control port" message,
1034 and log the event. Closes ticket 1667. Patch from Ravi
1036 - Provide better error message for GETINFO desc/(id|name) when not
1037 fetching router descriptors. Closes ticket 5847. Patch by
1039 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
1040 whether Tor will try to download router descriptors and
1041 microdescriptors respectively. Closes ticket 22684.
1042 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
1043 so controllers can tell whether the geoip databases are loaded.
1044 Closes ticket 23237.
1045 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
1046 events. Closes ticket 19254. Patch by "DonnchaC".
1048 o Minor features (development support):
1049 - Developers can now generate a call-graph for Tor using the
1050 "calltool" python program, which post-processes object dumps. It
1051 should work okay on many Linux and OSX platforms, and might work
1052 elsewhere too. To run it, install calltool from
1053 https://gitweb.torproject.org/user/nickm/calltool.git and run
1054 "make callgraph". Closes ticket 19307.
1056 o Minor features (directory authority):
1057 - Make the "Exit" flag assignment only depend on whether the exit
1058 policy allows connections to ports 80 and 443. Previously relays
1059 would get the Exit flag if they allowed connections to one of
1060 these ports and also port 6667. Resolves ticket 23637.
1062 o Minor features (ed25519):
1063 - Add validation function to checks for torsion components in
1064 ed25519 public keys, used by prop224 client-side code. Closes
1065 ticket 22006. Math help by Ian Goldberg.
1067 o Minor features (exit relay, DNS):
1068 - Improve the clarity and safety of the log message from evdns when
1069 receiving an apparently spoofed DNS reply. Closes ticket 3056.
1071 o Minor features (fallback directory mirrors):
1072 - The fallback directory list has been re-generated based on the
1073 current status of the network. Tor uses fallback directories to
1074 bootstrap when it doesn't yet have up-to-date directory
1075 information. Closes ticket 24801.
1076 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1077 prefer to bootstrap from fallback directory mirrors. This is a
1078 follow-up to 24679, which removed weights from the default
1079 fallbacks. Implements ticket 24681.
1081 o Minor features (geoip):
1082 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
1085 o Minor features (integration, hardening):
1086 - Add a new NoExec option to prevent Tor from running other
1087 programs. When this option is set to 1, Tor will never try to run
1088 another program, regardless of the settings of
1089 PortForwardingHelper, ClientTransportPlugin, or
1090 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
1091 without restarting Tor. Closes ticket 22976.
1093 o Minor features (linux seccomp2 sandbox):
1094 - Update the sandbox rules so that they should now work correctly
1095 with Glibc 2.26. Closes ticket 24315.
1097 o Minor features (logging):
1098 - Provide better warnings when the getrandom() syscall fails. Closes
1100 - Downgrade a pair of log messages that could occur when an exit's
1101 resolver gave us an unusual (but not forbidden) response. Closes
1103 - Improve the message we log when re-enabling circuit build timeouts
1104 after having received a consensus. Closes ticket 20963.
1105 - Log more circuit information whenever we are about to try to
1106 package a relay cell on a circuit with a nonexistent n_chan.
1107 Attempt to diagnose ticket 8185.
1108 - Improve info-level log identification of particular circuits, to
1109 help with debugging. Closes ticket 23645.
1110 - Improve the warning message for specifying a relay by nickname.
1111 The previous message implied that nickname registration was still
1112 part of the Tor network design, which it isn't. Closes
1114 - If the sandbox filter fails to load, suggest to the user that
1115 their kernel might not support seccomp2. Closes ticket 23090.
1117 o Minor features (onion service, circuit, logging):
1118 - Improve logging of many callsite in the circuit subsystem to print
1119 the circuit identifier(s).
1120 - Log when we cleanup an intro point from a service so we know when
1121 and for what reason it happened. Closes ticket 23604.
1123 o Minor features (portability):
1124 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
1125 (It doesn't yet work with the sandbox enabled.) Closes
1127 - Check at configure time whether uint8_t is the same type as
1128 unsigned char. Lots of existing code already makes this
1129 assumption, and there could be strict aliasing issues if the
1130 assumption is violated. Closes ticket 22410.
1132 o Minor features (relay):
1133 - When choosing which circuits can be expired as unused, consider
1134 circuits from clients even if those clients used regular CREATE
1135 cells to make them; and do not consider circuits from relays even
1136 if they were made with CREATE_FAST. Part of ticket 22805.
1137 - Reject attempts to use relative file paths when RunAsDaemon is
1138 set. Previously, Tor would accept these, but the directory-
1139 changing step of RunAsDaemon would give strange and/or confusing
1140 results. Closes ticket 22731.
1142 o Minor features (relay statistics):
1143 - Change relay bandwidth reporting stats interval from 4 hours to 24
1144 hours in order to reduce the efficiency of guard discovery
1145 attacks. Fixes ticket 23856.
1147 o Minor features (reverted deprecations):
1148 - The ClientDNSRejectInternalAddresses flag can once again be set in
1149 non-testing Tor networks, so long as they do not use the default
1150 directory authorities. This change also removes the deprecation of
1151 this flag from 0.2.9.2-alpha. Closes ticket 21031.
1153 o Minor features (robustness):
1154 - Change several fatal assertions when flushing buffers into non-
1155 fatal assertions, to prevent any recurrence of 23690.
1157 o Minor features (startup, safety):
1158 - When configured to write a PID file, Tor now exits if it is unable
1159 to do so. Previously, it would warn and continue. Closes
1162 o Minor features (static analysis):
1163 - The BUG() macro has been changed slightly so that Coverity no
1164 longer complains about dead code if the bug is impossible. Closes
1167 o Minor features (testing):
1168 - Our fuzzing tests now test the encrypted portions of v3 onion
1169 service descriptors. Implements more of 21509.
1170 - Add a unit test to make sure that our own generated platform
1171 string will be accepted by directory authorities. Closes
1173 - The default chutney network tests now include tests for the v3
1174 onion service design. Make sure you have the latest version of
1175 chutney if you want to run these. Closes ticket 22437.
1176 - Add a unit test to verify that we can parse a hardcoded v2 onion
1177 service descriptor. Closes ticket 15554.
1179 o Minor bugfixes (address selection):
1180 - When the fascist_firewall_choose_address_ functions don't find a
1181 reachable address, set the returned address to the null address
1182 and port. This is a precautionary measure, because some callers do
1183 not check the return value. Fixes bug 24736; bugfix
1186 o Minor bugfixes (bootstrapping):
1187 - When warning about state file clock skew, report the correct
1188 direction for the detected skew. Fixes bug 23606; bugfix
1191 o Minor bugfixes (bridge clients, bootstrap):
1192 - Retry directory downloads when we get our first bridge descriptor
1193 during bootstrap or while reconnecting to the network. Keep
1194 retrying every time we get a bridge descriptor, until we have a
1195 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
1196 - Stop delaying bridge descriptor fetches when we have cached bridge
1197 descriptors. Instead, only delay bridge descriptor fetches when we
1198 have at least one reachable bridge. Fixes part of bug 24367;
1199 bugfix on 0.2.0.3-alpha.
1200 - Stop delaying directory fetches when we have cached bridge
1201 descriptors. Instead, only delay bridge descriptor fetches when
1202 all our bridges are definitely unreachable. Fixes part of bug
1203 24367; bugfix on 0.2.0.3-alpha.
1205 o Minor bugfixes (bridge):
1206 - Overwrite the bridge address earlier in the process of retrieving
1207 its descriptor, to make sure we reach it on the configured
1208 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
1210 o Minor bugfixes (build, compilation):
1211 - Fix a compilation warning when building with zstd support on
1212 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1213 and fixed by Andreas Stieger.
1214 - When searching for OpenSSL, don't accept any OpenSSL library that
1215 lacks TLSv1_1_method(): Tor doesn't build with those versions.
1216 Additionally, look in /usr/local/opt/openssl, if it's present.
1217 These changes together repair the default build on OSX systems
1218 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
1219 - Fix a signed/unsigned comparison warning introduced by our fix to
1220 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1221 - Fix a memory leak warning in one of the libevent-related
1222 configuration tests that could occur when manually specifying
1223 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
1224 Found and patched by Alex Xu.
1225 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
1226 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1228 o Minor bugfixes (certificate handling):
1229 - Fix a time handling bug in Tor certificates set to expire after
1230 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
1231 Coverity as CID 1415728.
1233 o Minor bugfixes (client):
1234 - By default, do not enable storage of client-side DNS values. These
1235 values were unused by default previously, but they should not have
1236 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
1238 o Minor bugfixes (client, usability):
1239 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
1240 SOCKS4a requests that contain IP address strings, even when
1241 SafeSocks in enabled, as this prevents user from connecting to
1242 known IP addresses without relying on DNS for resolving. SafeSocks
1243 still rejects SOCKS connections that connect to IP addresses when
1244 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
1245 bugfix on Tor 0.2.6.2-alpha.
1247 o Minor bugfixes (code correctness):
1248 - Call htons() in extend_cell_format() for encoding a 16-bit value.
1249 Previously we used ntohs(), which happens to behave the same on
1250 all the platforms we support, but which isn't really correct.
1251 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
1252 - For defense-in-depth, make the controller's write_escaped_data()
1253 function robust to extremely long inputs. Fixes bug 19281; bugfix
1254 on 0.1.1.1-alpha. Reported by Guido Vranken.
1255 - Fix several places in our codebase where a C compiler would be
1256 likely to eliminate a check, based on assuming that undefined
1257 behavior had not happened elsewhere in the code. These cases are
1258 usually a sign of redundant checking or dubious arithmetic. Found
1259 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
1260 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
1263 o Minor bugfixes (compression):
1264 - Handle a pathological case when decompressing Zstandard data when
1265 the output buffer size is zero. Fixes bug 23551; bugfix
1268 o Minor bugfixes (consensus expiry):
1269 - Check for adequate directory information correctly. Previously, Tor
1270 would reconsider whether it had sufficient directory information
1271 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
1273 o Minor bugfixes (control port, linux seccomp2 sandbox):
1274 - Avoid a crash when attempting to use the seccomp2 sandbox together
1275 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1278 o Minor bugfixes (control port, onion services):
1279 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
1280 HS_DESC event when a service is not able to upload a descriptor.
1281 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
1283 o Minor bugfixes (directory cache):
1284 - Recover better from empty or corrupt files in the consensus cache
1285 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1286 - When a consensus diff calculation is only partially successful,
1287 only record the successful parts as having succeeded. Partial
1288 success can happen if (for example) one compression method fails
1289 but the others succeed. Previously we misrecorded all the
1290 calculations as having succeeded, which would later cause a
1291 nonfatal assertion failure. Fixes bug 24086; bugfix
1294 o Minor bugfixes (directory client):
1295 - On failure to download directory information, delay retry attempts
1296 by a random amount based on the "decorrelated jitter" algorithm.
1297 Our previous delay algorithm tended to produce extra-long delays
1298 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
1300 o Minor bugfixes (directory protocol):
1301 - Directory servers now include a "Date:" http header for response
1302 codes other than 200. Clients starting with a skewed clock and a
1303 recent consensus were getting "304 Not modified" responses from
1304 directory authorities, so without the Date header, the client
1305 would never hear about a wrong clock. Fixes bug 23499; bugfix
1307 - Make clients wait for 6 seconds before trying to download a
1308 consensus from an authority. Fixes bug 17750; bugfix
1311 o Minor bugfixes (documentation):
1312 - Document better how to read gcov, and what our gcov postprocessing
1313 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
1314 - Fix manpage to not refer to the obsolete (and misspelled)
1315 UseEntryGuardsAsDirectoryGuards parameter in the description of
1316 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
1318 o Minor bugfixes (DoS-resistance):
1319 - If future code asks if there are any running bridges, without
1320 checking if bridges are enabled, log a BUG warning rather than
1321 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
1323 o Minor bugfixes (entry guards):
1324 - Tor now updates its guard state when it reads a consensus
1325 regardless of whether it's missing descriptors. That makes tor use
1326 its primary guards to fetch descriptors in some edge cases where
1327 it would previously have used fallback directories. Fixes bug
1328 23862; bugfix on 0.3.0.1-alpha.
1330 o Minor bugfixes (format strictness):
1331 - Restrict several data formats to decimal. Previously, the
1332 BuildTimeHistogram entries in the state file, the "bw=" entries in
1333 the bandwidth authority file, and the process IDs passed to the
1334 __OwningControllerProcess option could all be specified in hex or
1335 octal as well as in decimal. This was not an intentional feature.
1336 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
1339 o Minor bugfixes (heartbeat):
1340 - If we fail to write a heartbeat message, schedule a retry for the
1341 minimum heartbeat interval number of seconds in the future. Fixes
1342 bug 19476; bugfix on 0.2.3.1-alpha.
1344 o Minor bugfixes (logging):
1345 - Suppress a log notice when relay descriptors arrive. We already
1346 have a bootstrap progress for this so no need to log notice
1347 everytime tor receives relay descriptors. Microdescriptors behave
1348 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
1349 - Remove duplicate log messages regarding opening non-local
1350 SocksPorts upon parsing config and opening listeners at startup.
1351 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
1352 - Use a more comprehensible log message when telling the user
1353 they've excluded every running exit node. Fixes bug 7890; bugfix
1355 - When logging the number of descriptors we intend to download per
1356 directory request, do not log a number higher than then the number
1357 of descriptors we're fetching in total. Fixes bug 19648; bugfix
1359 - When warning about a directory owned by the wrong user, log the
1360 actual name of the user owning the directory. Previously, we'd log
1361 the name of the process owner twice. Fixes bug 23487; bugfix
1363 - Fix some messages on unexpected errors from the seccomp2 library.
1364 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
1365 - The tor specification says hop counts are 1-based, so fix two log
1366 messages that mistakenly logged 0-based hop counts. Fixes bug
1367 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
1368 Credit to Xiaofan Li for reporting this issue.
1370 o Minor bugfixes (logging, relay shutdown, annoyance):
1371 - When a circuit is marked for close, do not attempt to package any
1372 cells for channels on that circuit. Previously, we would detect
1373 this condition lower in the call stack, when we noticed that the
1374 circuit had no attached channel, and log an annoying message.
1375 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1377 o Minor bugfixes (memory safety, defensive programming):
1378 - Clear the target address when node_get_prim_orport() returns
1379 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1381 o Minor bugfixes (memory usage):
1382 - When queuing DESTROY cells on a channel, only queue the circuit-id
1383 and reason fields: not the entire 514-byte cell. This fix should
1384 help mitigate any bugs or attacks that fill up these queues, and
1385 free more RAM for other uses. Fixes bug 24666; bugfix
1388 o Minor bugfixes (network layer):
1389 - When closing a connection via close_connection_immediately(), we
1390 mark it as "not blocked on bandwidth", to prevent later calls from
1391 trying to unblock it, and give it permission to read. This fixes a
1392 backtrace warning that can happen on relays under various
1393 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1395 o Minor bugfixes (onion services):
1396 - The introduction circuit was being timed out too quickly while
1397 waiting for the rendezvous circuit to complete. Keep the intro
1398 circuit around longer instead of timing out and reopening new ones
1399 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
1400 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1401 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1403 - When handling multiple SOCKS request for the same .onion address,
1404 only fetch the service descriptor once.
1405 - Avoid a possible double close of a circuit by the intro point on
1406 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1407 bugfix on 0.3.0.1-alpha.
1408 - When reloading configured onion services, copy all information
1409 from the old service object. Previously, some data was omitted,
1410 causing delays in descriptor upload, and other bugs. Fixes bug
1411 23790; bugfix on 0.2.1.9-alpha.
1413 o Minor bugfixes (path selection):
1414 - When selecting relays by bandwidth, avoid a rounding error that
1415 could sometimes cause load to be imbalanced incorrectly.
1416 Previously, we would always round upwards; now, we round towards
1417 the nearest integer. This had the biggest effect when a relay's
1418 weight adjustments should have given it weight 0, but it got
1419 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1420 - When calculating the fraction of nodes that have descriptors, and
1421 all nodes in the network have zero bandwidths, count the number of
1422 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1423 - Actually log the total bandwidth in compute_weighted_bandwidths().
1424 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1426 o Minor bugfixes (portability):
1427 - Stop using the PATH_MAX variable, which is not defined on GNU
1428 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
1429 - Fix a bug in the bit-counting parts of our timing-wheel code on
1430 MSVC. (Note that MSVC is still not a supported build platform, due
1431 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1434 o Minor bugfixes (relay):
1435 - When uploading our descriptor for the first time after startup,
1436 report the reason for uploading as "Tor just started" rather than
1437 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
1438 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1439 relays, to prevent spurious address resolutions and descriptor
1440 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1441 bugfix on in 0.2.8.1-alpha.
1442 - Avoid a crash when transitioning from client mode to bridge mode.
1443 Previously, we would launch the worker threads whenever our
1444 "public server" mode changed, but not when our "server" mode
1445 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1447 o Minor bugfixes (testing):
1448 - Fix a spurious fuzzing-only use of an uninitialized value. Found
1449 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
1450 - Test that IPv6-only clients can use microdescriptors when running
1451 "make test-network-all". Requires chutney master 61c28b9 or later.
1452 Closes ticket 24109.
1453 - Prevent scripts/test/coverage from attempting to move gcov output
1454 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
1455 - Capture and detect several "Result does not fit" warnings in unit
1456 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
1458 - Fix additional channelpadding unit test failures by using mocked
1459 time instead of actual time for all tests. Fixes bug 23608; bugfix
1461 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
1462 to correctly handle cases where a caller gives it an RSA key of
1463 under 160 bits. (This is not actually a bug in Tor itself, but
1464 rather in our fuzzing code.) Fixes bug 24247; bugfix on
1465 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
1466 - Fix a broken unit test for the OutboundAddress option: the parsing
1467 function was never returning an error on failure. Fixes bug 23366;
1468 bugfix on 0.3.0.3-alpha.
1469 - Fix a signed-integer overflow in the unit tests for
1470 dir/download_status_random_backoff, which was untriggered until we
1471 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
1473 o Minor bugfixes (usability, control port):
1474 - Stop making an unnecessary routerlist check in NETINFO clock skew
1475 detection; this was preventing clients from reporting NETINFO clock
1476 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
1478 o Code simplification and refactoring:
1479 - Remove various ways of testing circuits and connections for
1480 "clientness"; instead, favor channel_is_client(). Part of
1482 - Extract the code for handling newly-open channels into a separate
1483 function from the general code to handle channel state
1484 transitions. This change simplifies our callgraph, reducing the
1485 size of the largest strongly connected component by roughly a
1486 factor of two. Closes ticket 22608.
1487 - Remove dead code for largely unused statistics on the number of
1488 times we've attempted various public key operations. Fixes bug
1489 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
1490 - Remove several now-obsolete functions for asking about old
1491 variants directory authority status. Closes ticket 22311; patch
1493 - Remove some of the code that once supported "Named" and "Unnamed"
1494 routers. Authorities no longer vote for these flags. Closes
1496 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
1497 and old hidden services, to indicate that they aren't suitable for
1498 new protocols or formats. Closes ticket 23026.
1499 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
1500 22521. Patch from Neel Chauhan.
1501 - Split the enormous circuit_send_next_onion_skin() function into
1502 multiple subfunctions. Closes ticket 22804.
1503 - Split the portions of the buffer.c module that handle particular
1504 protocols into separate modules. Part of ticket 23149.
1505 - Use our test macros more consistently, to produce more useful
1506 error messages when our unit tests fail. Add coccinelle patches to
1507 allow us to re-check for test macro uses. Closes ticket 22497.
1509 o Deprecated features:
1510 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
1511 now deprecated; they do not apply to relays, and they have had no
1512 effect on clients since 0.2.8.x. Closes ticket 19704.
1513 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
1514 only applies to direct unencrypted HTTP connections to your
1515 directory server, which your Tor probably isn't using. Closes
1519 - Add notes in man page regarding OS support for the various
1520 scheduler types. Attempt to use less jargon in the scheduler
1521 section. Closes ticket 24254.
1522 - Clarify that the Address option is entirely about setting an
1523 advertised IPv4 address. Closes ticket 18891.
1524 - Clarify the manpage's use of the term "address" to clarify what
1525 kind of address is intended. Closes ticket 21405.
1526 - Document that onion service subdomains are allowed, and ignored.
1527 Closes ticket 18736.
1528 - Clarify in the manual that "Sandbox 1" is only supported on Linux
1529 kernels. Closes ticket 22677.
1530 - Document all values of PublishServerDescriptor in the manpage.
1531 Closes ticket 15645.
1532 - Improve the documentation for the directory port part of the
1533 DirAuthority line. Closes ticket 20152.
1534 - Restore documentation for the authorities' "approved-routers"
1535 file. Closes ticket 21148.
1538 - The AllowDotExit option has been removed as unsafe. It has been
1539 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
1540 - The ClientDNSRejectInternalAddresses flag can no longer be set on
1541 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
1542 Closes ticket 21031.
1543 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
1544 nobody was using it any longer. Closes ticket 22377.
1547 Changes in version 0.3.1.9 - 2017-12-01:
1548 Tor 0.3.1.9 backports important security and stability fixes from the
1549 0.3.2 development series. All Tor users should upgrade to this
1550 release, or to another of the releases coming out today.
1552 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1553 - Fix a denial of service bug where an attacker could use a
1554 malformed directory object to cause a Tor instance to pause while
1555 OpenSSL would try to read a passphrase from the terminal. (Tor
1556 instances run without a terminal, which is the case for most Tor
1557 packages, are not impacted.) Fixes bug 24246; bugfix on every
1558 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1559 Found by OSS-Fuzz as testcase 6360145429790720.
1560 - Fix a denial of service issue where an attacker could crash a
1561 directory authority using a malformed router descriptor. Fixes bug
1562 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1564 - When checking for replays in the INTRODUCE1 cell data for a
1565 (legacy) onion service, correctly detect replays in the RSA-
1566 encrypted part of the cell. We were previously checking for
1567 replays on the entire cell, but those can be circumvented due to
1568 the malleability of Tor's legacy hybrid encryption. This fix helps
1569 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1570 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1573 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1574 - Fix a use-after-free error that could crash v2 Tor onion services
1575 when they failed to open circuits while expiring introduction
1576 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1577 also tracked as TROVE-2017-013 and CVE-2017-8823.
1579 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1580 - When running as a relay, make sure that we never build a path
1581 through ourselves, even in the case where we have somehow lost the
1582 version of our descriptor appearing in the consensus. Fixes part
1583 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1584 as TROVE-2017-012 and CVE-2017-8822.
1585 - When running as a relay, make sure that we never choose ourselves
1586 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1587 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1589 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1590 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1591 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1592 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1593 identifying and finding a workaround to this bug and to Moritz,
1594 Arthur Edelstein, and Roger for helping to track it down and
1597 o Minor features (bridge):
1598 - Bridges now include notice in their descriptors that they are
1599 bridges, and notice of their distribution status, based on their
1600 publication settings. Implements ticket 18329. For more fine-
1601 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1604 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1605 - Add an IPv6 address for the "bastet" directory authority. Closes
1608 o Minor features (geoip):
1609 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1612 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1613 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1614 relays, to prevent spurious address resolutions and descriptor
1615 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1616 bugfix on in 0.2.8.1-alpha.
1618 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1619 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1620 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1622 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1623 - When a circuit is marked for close, do not attempt to package any
1624 cells for channels on that circuit. Previously, we would detect
1625 this condition lower in the call stack, when we noticed that the
1626 circuit had no attached channel, and log an annoying message.
1627 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1629 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
1630 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
1631 so it matches dir-spec.txt. Fixes bug 24262; bugfix
1634 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1635 - Avoid a crash when transitioning from client mode to bridge mode.
1636 Previously, we would launch the worker threads whenever our
1637 "public server" mode changed, but not when our "server" mode
1638 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1641 Changes in version 0.3.0.13 - 2017-12-01
1642 Tor 0.3.0.13 backports important security and stability bugfixes from
1643 later Tor releases. All Tor users should upgrade to this release, or
1644 to another of the releases coming out today.
1646 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1647 2018. If you need a release with long-term support, please stick with
1648 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1650 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1651 - Fix a denial of service bug where an attacker could use a
1652 malformed directory object to cause a Tor instance to pause while
1653 OpenSSL would try to read a passphrase from the terminal. (Tor
1654 instances run without a terminal, which is the case for most Tor
1655 packages, are not impacted.) Fixes bug 24246; bugfix on every
1656 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1657 Found by OSS-Fuzz as testcase 6360145429790720.
1658 - Fix a denial of service issue where an attacker could crash a
1659 directory authority using a malformed router descriptor. Fixes bug
1660 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1662 - When checking for replays in the INTRODUCE1 cell data for a
1663 (legacy) onion service, correctly detect replays in the RSA-
1664 encrypted part of the cell. We were previously checking for
1665 replays on the entire cell, but those can be circumvented due to
1666 the malleability of Tor's legacy hybrid encryption. This fix helps
1667 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1668 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1671 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1672 - Fix a use-after-free error that could crash v2 Tor onion services
1673 when they failed to open circuits while expiring introduction
1674 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1675 also tracked as TROVE-2017-013 and CVE-2017-8823.
1677 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1678 - When running as a relay, make sure that we never build a path
1679 through ourselves, even in the case where we have somehow lost the
1680 version of our descriptor appearing in the consensus. Fixes part
1681 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1682 as TROVE-2017-012 and CVE-2017-8822.
1683 - When running as a relay, make sure that we never choose ourselves
1684 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1685 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1687 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1688 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1689 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1690 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1691 identifying and finding a workaround to this bug and to Moritz,
1692 Arthur Edelstein, and Roger for helping to track it down and
1695 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1696 - Enable a couple of pieces of Windows hardening: one
1697 (HeapEnableTerminationOnCorruption) that has been on-by-default
1698 since Windows 8, and unavailable before Windows 7; and one
1699 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1700 affect us, but shouldn't do any harm. Closes ticket 21953.
1702 o Minor features (bridge, backport from 0.3.1.9):
1703 - Bridges now include notice in their descriptors that they are
1704 bridges, and notice of their distribution status, based on their
1705 publication settings. Implements ticket 18329. For more fine-
1706 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1709 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1710 - Add an IPv6 address for the "bastet" directory authority. Closes
1713 o Minor features (geoip):
1714 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1717 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1718 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1719 relays, to prevent spurious address resolutions and descriptor
1720 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1721 bugfix on in 0.2.8.1-alpha.
1723 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1724 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1725 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1727 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1728 - When a circuit is marked for close, do not attempt to package any
1729 cells for channels on that circuit. Previously, we would detect
1730 this condition lower in the call stack, when we noticed that the
1731 circuit had no attached channel, and log an annoying message.
1732 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1734 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1735 - Avoid a crash when transitioning from client mode to bridge mode.
1736 Previously, we would launch the worker threads whenever our
1737 "public server" mode changed, but not when our "server" mode
1738 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1740 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1741 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1742 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1745 Changes in version 0.2.9.14 - 2017-12-01
1746 Tor 0.3.0.13 backports important security and stability bugfixes from
1747 later Tor releases. All Tor users should upgrade to this release, or
1748 to another of the releases coming out today.
1750 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
1751 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1752 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1753 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1754 identifying and finding a workaround to this bug and to Moritz,
1755 Arthur Edelstein, and Roger for helping to track it down and
1758 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1759 - Fix a denial of service bug where an attacker could use a
1760 malformed directory object to cause a Tor instance to pause while
1761 OpenSSL would try to read a passphrase from the terminal. (Tor
1762 instances run without a terminal, which is the case for most Tor
1763 packages, are not impacted.) Fixes bug 24246; bugfix on every
1764 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1765 Found by OSS-Fuzz as testcase 6360145429790720.
1766 - Fix a denial of service issue where an attacker could crash a
1767 directory authority using a malformed router descriptor. Fixes bug
1768 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1770 - When checking for replays in the INTRODUCE1 cell data for a
1771 (legacy) onion service, correctly detect replays in the RSA-
1772 encrypted part of the cell. We were previously checking for
1773 replays on the entire cell, but those can be circumvented due to
1774 the malleability of Tor's legacy hybrid encryption. This fix helps
1775 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1776 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1779 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1780 - Fix a use-after-free error that could crash v2 Tor onion services
1781 when they failed to open circuits while expiring introduction
1782 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1783 also tracked as TROVE-2017-013 and CVE-2017-8823.
1785 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1786 - When running as a relay, make sure that we never build a path
1787 through ourselves, even in the case where we have somehow lost the
1788 version of our descriptor appearing in the consensus. Fixes part
1789 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1790 as TROVE-2017-012 and CVE-2017-8822.
1792 o Minor features (bridge, backport from 0.3.1.9):
1793 - Bridges now include notice in their descriptors that they are
1794 bridges, and notice of their distribution status, based on their
1795 publication settings. Implements ticket 18329. For more fine-
1796 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1799 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1800 - Add an IPv6 address for the "bastet" directory authority. Closes
1803 o Minor features (geoip):
1804 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1807 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1808 - Enable a couple of pieces of Windows hardening: one
1809 (HeapEnableTerminationOnCorruption) that has been on-by-default
1810 since Windows 8, and unavailable before Windows 7; and one
1811 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1812 affect us, but shouldn't do any harm. Closes ticket 21953.
1814 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1815 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1816 relays, to prevent spurious address resolutions and descriptor
1817 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1818 bugfix on in 0.2.8.1-alpha.
1820 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1821 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1822 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1824 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1825 - When a circuit is marked for close, do not attempt to package any
1826 cells for channels on that circuit. Previously, we would detect
1827 this condition lower in the call stack, when we noticed that the
1828 circuit had no attached channel, and log an annoying message.
1829 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1831 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1832 - Avoid a crash when transitioning from client mode to bridge mode.
1833 Previously, we would launch the worker threads whenever our
1834 "public server" mode changed, but not when our "server" mode
1835 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1837 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1838 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1839 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1842 Changes in version 0.2.8.17 - 2017-12-01
1843 Tor 0.2.8.17 backports important security and stability bugfixes from
1844 later Tor releases. All Tor users should upgrade to this release, or
1845 to another of the releases coming out today.
1847 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1848 2018. If you need a release with long-term support, please upgrade with
1849 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1851 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1852 - Fix a denial of service bug where an attacker could use a
1853 malformed directory object to cause a Tor instance to pause while
1854 OpenSSL would try to read a passphrase from the terminal. (Tor
1855 instances run without a terminal, which is the case for most Tor
1856 packages, are not impacted.) Fixes bug 24246; bugfix on every
1857 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1858 Found by OSS-Fuzz as testcase 6360145429790720.
1859 - When checking for replays in the INTRODUCE1 cell data for a
1860 (legacy) onion service, correctly detect replays in the RSA-
1861 encrypted part of the cell. We were previously checking for
1862 replays on the entire cell, but those can be circumvented due to
1863 the malleability of Tor's legacy hybrid encryption. This fix helps
1864 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1865 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1868 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1869 - Fix a use-after-free error that could crash v2 Tor onion services
1870 when they failed to open circuits while expiring introduction
1871 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1872 also tracked as TROVE-2017-013 and CVE-2017-8823.
1874 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1875 - When running as a relay, make sure that we never build a path through
1876 ourselves, even in the case where we have somehow lost the version of
1877 our descriptor appearing in the consensus. Fixes part of bug 21534;
1878 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
1881 o Minor features (bridge, backport from 0.3.1.9):
1882 - Bridges now include notice in their descriptors that they are
1883 bridges, and notice of their distribution status, based on their
1884 publication settings. Implements ticket 18329. For more fine-
1885 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1888 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1889 - Add an IPv6 address for the "bastet" directory authority. Closes
1892 o Minor features (geoip):
1893 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1896 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1897 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1898 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1901 Changes in version 0.2.5.16 - 2017-12-01
1902 Tor 0.2.5.13 backports important security and stability bugfixes from
1903 later Tor releases. All Tor users should upgrade to this release, or
1904 to another of the releases coming out today.
1906 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1907 2018. If you need a release with long-term support, please upgrade to
1908 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1910 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1911 - Fix a denial of service bug where an attacker could use a
1912 malformed directory object to cause a Tor instance to pause while
1913 OpenSSL would try to read a passphrase from the terminal. (Tor
1914 instances run without a terminal, which is the case for most Tor
1915 packages, are not impacted.) Fixes bug 24246; bugfix on every
1916 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1917 Found by OSS-Fuzz as testcase 6360145429790720.
1918 - When checking for replays in the INTRODUCE1 cell data for a
1919 (legacy) onion service, correctly detect replays in the RSA-
1920 encrypted part of the cell. We were previously checking for
1921 replays on the entire cell, but those can be circumvented due to
1922 the malleability of Tor's legacy hybrid encryption. This fix helps
1923 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1924 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1927 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1928 - When running as a relay, make sure that we never build a path
1929 through ourselves, even in the case where we have somehow lost the
1930 version of our descriptor appearing in the consensus. Fixes part
1931 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1932 as TROVE-2017-012 and CVE-2017-8822.
1934 o Minor features (bridge, backport from 0.3.1.9):
1935 - Bridges now include notice in their descriptors that they are
1936 bridges, and notice of their distribution status, based on their
1937 publication settings. Implements ticket 18329. For more fine-
1938 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1941 o Minor features (geoip):
1942 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1946 Changes in version 0.2.5.15 - 2017-10-25
1947 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
1948 series. It also adds a new directory authority, Bastet.
1950 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1951 2018. If you need a release with long-term support, please upgrade to
1952 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1954 o Directory authority changes:
1955 - Add "Bastet" as a ninth directory authority to the default list.
1956 Closes ticket 23910.
1957 - The directory authority "Longclaw" has changed its IP address.
1958 Closes ticket 23592.
1960 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1961 - Avoid an assertion failure bug affecting our implementation of
1962 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1963 handling of "0xx" differs from what we had expected. Fixes bug
1964 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1966 o Minor features (geoip):
1967 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1970 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1971 - Fix a memset() off the end of an array when packing cells. This
1972 bug should be harmless in practice, since the corrupted bytes are
1973 still in the same structure, and are always padding bytes,
1974 ignored, or immediately overwritten, depending on compiler
1975 behavior. Nevertheless, because the memset()'s purpose is to make
1976 sure that any other cell-handling bugs can't expose bytes to the
1977 network, we need to fix it. Fixes bug 22737; bugfix on
1978 0.2.4.11-alpha. Fixes CID 1401591.
1980 o Build features (backport from 0.3.1.5-alpha):
1981 - Tor's repository now includes a Travis Continuous Integration (CI)
1982 configuration file (.travis.yml). This is meant to help new
1983 developers and contributors who fork Tor to a Github repository be
1984 better able to test their changes, and understand what we expect
1985 to pass. To use this new build feature, you must fork Tor to your
1986 Github account, then go into the "Integrations" menu in the
1987 repository settings for your fork and enable Travis, then push
1988 your changes. Closes ticket 22636.
1991 Changes in version 0.2.8.16 - 2017-10-25
1992 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
1993 series, including a bugfix for a crash issue that had affected relays
1994 under memory pressure. It also adds a new directory authority, Bastet.
1996 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1997 2018. If you need a release with long-term support, please stick with
1998 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2000 o Directory authority changes:
2001 - Add "Bastet" as a ninth directory authority to the default list.
2002 Closes ticket 23910.
2003 - The directory authority "Longclaw" has changed its IP address.
2004 Closes ticket 23592.
2006 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2007 - Fix a timing-based assertion failure that could occur when the
2008 circuit out-of-memory handler freed a connection's output buffer.
2009 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2011 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2012 - Remove longclaw's IPv6 address, as it will soon change. Authority
2013 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2014 3/8 directory authorities with IPv6 addresses, but there are also
2015 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2017 o Minor features (geoip):
2018 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2022 Changes in version 0.2.9.13 - 2017-10-25
2023 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
2024 series, including a bugfix for a crash issue that had affected relays
2025 under memory pressure. It also adds a new directory authority, Bastet.
2027 o Directory authority changes:
2028 - Add "Bastet" as a ninth directory authority to the default list.
2029 Closes ticket 23910.
2030 - The directory authority "Longclaw" has changed its IP address.
2031 Closes ticket 23592.
2033 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2034 - Fix a timing-based assertion failure that could occur when the
2035 circuit out-of-memory handler freed a connection's output buffer.
2036 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2038 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2039 - Remove longclaw's IPv6 address, as it will soon change. Authority
2040 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2041 3/8 directory authorities with IPv6 addresses, but there are also
2042 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2044 o Minor features (geoip):
2045 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2048 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2049 - When a directory authority rejects a descriptor or extrainfo with
2050 a given digest, mark that digest as undownloadable, so that we do
2051 not attempt to download it again over and over. We previously
2052 tried to avoid downloading such descriptors by other means, but we
2053 didn't notice if we accidentally downloaded one anyway. This
2054 behavior became problematic in 0.2.7.2-alpha, when authorities
2055 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2058 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2059 - Clear the address when node_get_prim_orport() returns early.
2060 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2062 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2063 - When running as a Windows service, set the ID of the main thread
2064 correctly. Failure to do so made us fail to send log messages to
2065 the controller in 0.2.1.16-rc, slowed down controller event
2066 delivery in 0.2.7.3-rc and later, and crash with an assertion
2067 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2068 Patch and diagnosis from "Vort".
2071 Changes in version 0.3.0.12 - 2017-10-25
2072 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
2073 series, including a bugfix for a crash issue that had affected relays
2074 under memory pressure. It also adds a new directory authority, Bastet.
2076 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2077 2018. If you need a release with long-term support, please stick with
2078 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2080 o Directory authority changes:
2081 - Add "Bastet" as a ninth directory authority to the default list.
2082 Closes ticket 23910.
2083 - The directory authority "Longclaw" has changed its IP address.
2084 Closes ticket 23592.
2086 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2087 - Fix a timing-based assertion failure that could occur when the
2088 circuit out-of-memory handler freed a connection's output buffer.
2089 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2091 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2092 - Remove longclaw's IPv6 address, as it will soon change. Authority
2093 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2094 3/8 directory authorities with IPv6 addresses, but there are also
2095 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2097 o Minor features (geoip):
2098 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2101 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2102 - When a directory authority rejects a descriptor or extrainfo with
2103 a given digest, mark that digest as undownloadable, so that we do
2104 not attempt to download it again over and over. We previously
2105 tried to avoid downloading such descriptors by other means, but we
2106 didn't notice if we accidentally downloaded one anyway. This
2107 behavior became problematic in 0.2.7.2-alpha, when authorities
2108 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2111 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2112 - Avoid a possible double close of a circuit by the intro point on
2113 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2114 bugfix on 0.3.0.1-alpha.
2116 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2117 - Clear the address when node_get_prim_orport() returns early.
2118 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2120 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2121 - When running as a Windows service, set the ID of the main thread
2122 correctly. Failure to do so made us fail to send log messages to
2123 the controller in 0.2.1.16-rc, slowed down controller event
2124 delivery in 0.2.7.3-rc and later, and crash with an assertion
2125 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2126 Patch and diagnosis from "Vort".
2129 Changes in version 0.3.1.8 - 2017-10-25
2130 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
2131 It includes several bugfixes, including a bugfix for a crash issue
2132 that had affected relays under memory pressure. It also adds
2133 a new directory authority, Bastet.
2135 o Directory authority changes:
2136 - Add "Bastet" as a ninth directory authority to the default list.
2137 Closes ticket 23910.
2138 - The directory authority "Longclaw" has changed its IP address.
2139 Closes ticket 23592.
2141 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2142 - Fix a timing-based assertion failure that could occur when the
2143 circuit out-of-memory handler freed a connection's output buffer.
2144 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2146 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2147 - Remove longclaw's IPv6 address, as it will soon change. Authority
2148 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2149 3/8 directory authorities with IPv6 addresses, but there are also
2150 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2152 o Minor features (geoip):
2153 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2156 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
2157 - Fix a compilation warning when building with zstd support on
2158 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2159 and fixed by Andreas Stieger.
2161 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
2162 - Handle a pathological case when decompressing Zstandard data when
2163 the output buffer size is zero. Fixes bug 23551; bugfix
2166 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
2167 - Remove the length limit on HTTP status lines that authorities can
2168 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
2170 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2171 - Avoid a possible double close of a circuit by the intro point on
2172 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2173 bugfix on 0.3.0.1-alpha.
2175 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2176 - Clear the address when node_get_prim_orport() returns early.
2177 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2179 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
2180 - Fix additional channelpadding unit test failures by using mocked
2181 time instead of actual time for all tests. Fixes bug 23608; bugfix
2185 Changes in version 0.2.8.15 - 2017-09-18
2186 Tor 0.2.8.15 backports a collection of bugfixes from later
2189 Most significantly, it includes a fix for TROVE-2017-008, a
2190 security bug that affects hidden services running with the
2191 SafeLogging option disabled. For more information, see
2192 https://trac.torproject.org/projects/tor/ticket/23490
2194 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
2195 2018. We suggest that you upgrade to the latest stable release if
2196 possible. If you can't, we recommend that you upgrade at least to
2197 0.2.9, which will be supported until 2020.
2199 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2200 - Avoid an assertion failure bug affecting our implementation of
2201 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2202 handling of "0xx" differs from what we had expected. Fixes bug
2203 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2206 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2209 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2210 - Backport a fix for an "unused variable" warning that appeared
2211 in some versions of mingw. Fixes bug 22838; bugfix on
2214 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2215 - Fix a memset() off the end of an array when packing cells. This
2216 bug should be harmless in practice, since the corrupted bytes are
2217 still in the same structure, and are always padding bytes,
2218 ignored, or immediately overwritten, depending on compiler
2219 behavior. Nevertheless, because the memset()'s purpose is to make
2220 sure that any other cell-handling bugs can't expose bytes to the
2221 network, we need to fix it. Fixes bug 22737; bugfix on
2222 0.2.4.11-alpha. Fixes CID 1401591.
2224 o Build features (backport from 0.3.1.5-alpha):
2225 - Tor's repository now includes a Travis Continuous Integration (CI)
2226 configuration file (.travis.yml). This is meant to help new
2227 developers and contributors who fork Tor to a Github repository be
2228 better able to test their changes, and understand what we expect
2229 to pass. To use this new build feature, you must fork Tor to your
2230 Github account, then go into the "Integrations" menu in the
2231 repository settings for your fork and enable Travis, then push
2232 your changes. Closes ticket 22636.
2235 Changes in version 0.2.9.12 - 2017-09-18
2236 Tor 0.2.9.12 backports a collection of bugfixes from later
2239 Most significantly, it includes a fix for TROVE-2017-008, a
2240 security bug that affects hidden services running with the
2241 SafeLogging option disabled. For more information, see
2242 https://trac.torproject.org/projects/tor/ticket/23490
2244 o Major features (security, backport from 0.3.0.2-alpha):
2245 - Change the algorithm used to decide DNS TTLs on client and server
2246 side, to better resist DNS-based correlation attacks like the
2247 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2248 Feamster. Now relays only return one of two possible DNS TTL
2249 values, and clients are willing to believe DNS TTL values up to 3
2250 hours long. Closes ticket 19769.
2252 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
2253 - Fix a rare crash when sending a begin cell on a circuit whose
2254 linked directory connection had already been closed. Fixes bug
2255 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
2257 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
2258 - Fix a bug that prevented exit nodes from caching DNS records for
2259 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2261 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2262 - Fix a typo that had prevented TPROXY-based transparent proxying
2263 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2264 Patch from "d4fq0fQAgoJ".
2266 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2267 - Avoid an assertion failure bug affecting our implementation of
2268 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2269 handling of "0xx" differs from what we had expected. Fixes bug
2270 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2272 o Minor features (code style, backport from 0.3.1.3-alpha):
2273 - Add "Falls through" comments to our codebase, in order to silence
2274 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2275 Stieger. Closes ticket 22446.
2277 o Minor features (geoip):
2278 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2281 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
2282 - Roll over monthly accounting at the configured hour and minute,
2283 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2284 Found by Andrey Karpov with PVS-Studio.
2286 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
2287 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2288 bugfix on 0.2.8.1-alpha.
2289 - Fix warnings when building with libscrypt and openssl scrypt support
2290 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2291 - When building with certain versions the mingw C header files, avoid
2292 float-conversion warnings when calling the C functions isfinite(),
2293 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
2295 o Minor bugfixes (compilation, backport from 0.3.1.7):
2296 - Avoid compiler warnings in the unit tests for running tor_sscanf()
2297 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2299 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2300 - Backport a fix for an "unused variable" warning that appeared
2301 in some versions of mingw. Fixes bug 22838; bugfix on
2304 o Minor bugfixes (controller, backport from 0.3.1.7):
2305 - Do not crash when receiving a HSPOST command with an empty body.
2306 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2307 - Do not crash when receiving a POSTDESCRIPTOR command with an
2308 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2310 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2311 - Avoid Coverity build warnings related to our BUG() macro. By
2312 default, Coverity treats BUG() as the Linux kernel does: an
2313 instant abort(). We need to override that so our BUG() macro
2314 doesn't prevent Coverity from analyzing functions that use it.
2315 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2317 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2318 - Fix a memset() off the end of an array when packing cells. This
2319 bug should be harmless in practice, since the corrupted bytes are
2320 still in the same structure, and are always padding bytes,
2321 ignored, or immediately overwritten, depending on compiler
2322 behavior. Nevertheless, because the memset()'s purpose is to make
2323 sure that any other cell-handling bugs can't expose bytes to the
2324 network, we need to fix it. Fixes bug 22737; bugfix on
2325 0.2.4.11-alpha. Fixes CID 1401591.
2327 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2328 - When setting the maximum number of connections allowed by the OS,
2329 always allow some extra file descriptors for other files. Fixes
2330 bug 22797; bugfix on 0.2.0.10-alpha.
2332 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2333 - Avoid a sandbox failure when trying to re-bind to a socket and
2334 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2336 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2337 - Permit the fchmod system call, to avoid crashing on startup when
2338 starting with the seccomp2 sandbox and an unexpected set of
2339 permissions on the data directory or its contents. Fixes bug
2340 22516; bugfix on 0.2.5.4-alpha.
2342 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
2343 - Avoid a double-marked-circuit warning that could happen when we
2344 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
2347 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2348 - Reject version numbers with non-numeric prefixes (such as +, -, or
2349 whitespace). Disallowing whitespace prevents differential version
2350 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2351 and part of 21508; bugfix on 0.0.8pre1.
2353 o Build features (backport from 0.3.1.5-alpha):
2354 - Tor's repository now includes a Travis Continuous Integration (CI)
2355 configuration file (.travis.yml). This is meant to help new
2356 developers and contributors who fork Tor to a Github repository be
2357 better able to test their changes, and understand what we expect
2358 to pass. To use this new build feature, you must fork Tor to your
2359 Github account, then go into the "Integrations" menu in the
2360 repository settings for your fork and enable Travis, then push
2361 your changes. Closes ticket 22636.
2364 Changes in version 0.3.0.11 - 2017-09-18
2365 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
2368 Most significantly, it includes a fix for TROVE-2017-008, a
2369 security bug that affects hidden services running with the
2370 SafeLogging option disabled. For more information, see
2371 https://trac.torproject.org/projects/tor/ticket/23490
2373 o Minor features (code style, backport from 0.3.1.7):
2374 - Add "Falls through" comments to our codebase, in order to silence
2375 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2376 Stieger. Closes ticket 22446.
2379 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2382 o Minor bugfixes (compilation, backport from 0.3.1.7):
2383 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2384 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2386 o Minor bugfixes (controller, backport from 0.3.1.7):
2387 - Do not crash when receiving a HSPOST command with an empty body.
2388 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2389 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2390 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2392 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
2393 - When setting the maximum number of connections allowed by the OS,
2394 always allow some extra file descriptors for other files. Fixes
2395 bug 22797; bugfix on 0.2.0.10-alpha.
2397 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
2398 - Remove a forgotten debugging message when an introduction point
2399 successfully establishes a hidden service prop224 circuit with
2401 - Change three other log_warn() for an introduction point to
2402 protocol warnings, because they can be failure from the network
2403 and are not relevant to the operator. Fixes bug 23078; bugfix on
2404 0.3.0.1-alpha and 0.3.0.2-alpha.
2407 Changes in version 0.3.1.7 - 2017-09-18
2408 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
2410 With the 0.3.1 series, Tor now serves and downloads directory
2411 information in more compact formats, to save on bandwidth overhead. It
2412 also contains a new padding system to resist netflow-based traffic
2413 analysis, and experimental support for building parts of Tor in Rust
2414 (though no parts of Tor are in Rust yet). There are also numerous
2415 small features, bugfixes on earlier release series, and groundwork for
2416 the hidden services revamp of 0.3.2.
2418 This release also includes a fix for TROVE-2017-008, a security bug
2419 that affects hidden services running with the SafeLogging option
2420 disabled. For more information, see
2421 https://trac.torproject.org/projects/tor/ticket/23490
2423 Per our stable release policy, we plan to support each stable release
2424 series for at least the next nine months, or for three months after
2425 the first stable release of the next series: whichever is longer. If
2426 you need a release with long-term support, we recommend that you stay
2427 with the 0.2.9 series.
2429 Below is a list of the changes since 0.3.0. For a list of all
2430 changes since 0.3.1.6-rc, see the ChangeLog file.
2433 - To build with zstd and lzma support, Tor now requires the
2434 pkg-config tool at build time.
2436 o Major bugfixes (security, hidden services, loggging):
2437 - Fix a bug where we could log uninitialized stack when a certain
2438 hidden service error occurred while SafeLogging was disabled.
2439 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
2440 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
2442 o Major features (build system, continuous integration):
2443 - Tor's repository now includes a Travis Continuous Integration (CI)
2444 configuration file (.travis.yml). This is meant to help new
2445 developers and contributors who fork Tor to a Github repository be
2446 better able to test their changes, and understand what we expect
2447 to pass. To use this new build feature, you must fork Tor to your
2448 Github account, then go into the "Integrations" menu in the
2449 repository settings for your fork and enable Travis, then push
2450 your changes. Closes ticket 22636.
2452 o Major features (directory protocol):
2453 - Tor relays and authorities can now serve clients an abbreviated
2454 version of the consensus document, containing only the changes
2455 since an older consensus document that the client holds. Clients
2456 now request these documents when available. When both client and
2457 server use this new protocol, they will use far less bandwidth (up
2458 to 94% less) to keep the client's consensus up-to-date. Implements
2459 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
2460 - Tor can now compress directory traffic with lzma or with zstd
2461 compression algorithms, which can deliver better bandwidth
2462 performance. Because lzma is computationally expensive, it's only
2463 used for documents that can be compressed once and served many
2464 times. Support for these algorithms requires that tor is built
2465 with the libzstd and/or liblzma libraries available. Implements
2466 proposal 278; closes ticket 21662.
2467 - Relays now perform the more expensive compression operations, and
2468 consensus diff generation, in worker threads. This separation
2469 avoids delaying the main thread when a new consensus arrives.
2471 o Major features (experimental):
2472 - Tor can now build modules written in Rust. To turn this on, pass
2473 the "--enable-rust" flag to the configure script. It's not time to
2474 get excited yet: currently, there is no actual Rust functionality
2475 beyond some simple glue code, and a notice at startup to tell you
2476 that Rust is running. Still, we hope that programmers and
2477 packagers will try building Tor with Rust support, so that we can
2478 find issues and solve portability problems. Closes ticket 22106.
2480 o Major features (traffic analysis resistance):
2481 - Connections between clients and relays now send a padding cell in
2482 each direction every 1.5 to 9.5 seconds (tunable via consensus
2483 parameters). This padding will not resist specialized
2484 eavesdroppers, but it should be enough to make many ISPs' routine
2485 network flow logging less useful in traffic analysis against
2488 Padding is negotiated using Tor's link protocol, so both relays
2489 and clients must upgrade for this to take effect. Clients may
2490 still send padding despite the relay's version by setting
2491 ConnectionPadding 1 in torrc, and may disable padding by setting
2492 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
2493 users with the torrc option ReducedConnectionPadding. Implements
2494 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
2495 - Relays will publish 24 hour totals of padding and non-padding cell
2496 counts to their extra-info descriptors, unless PaddingStatistics 0
2497 is set in torrc. These 24 hour totals are also rounded to
2500 o Major bugfixes (hidden service, relay, security):
2501 - Fix a remotely triggerable assertion failure when a hidden service
2502 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2503 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2504 - Fix a remotely triggerable assertion failure caused by receiving a
2505 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2506 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2509 o Major bugfixes (path selection, security):
2510 - When choosing which guard to use for a circuit, avoid the exit's
2511 family along with the exit itself. Previously, the new guard
2512 selection logic avoided the exit, but did not consider its family.
2513 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2514 006 and CVE-2017-0377.
2516 o Major bugfixes (connection usage):
2517 - We use NETINFO cells to try to determine if both relays involved
2518 in a connection will agree on the canonical status of that
2519 connection. We prefer the connections where this is the case for
2520 extend cells, and try to close connections where relays disagree
2521 on their canonical status early. Also, we now prefer the oldest
2522 valid connection for extend cells. These two changes should reduce
2523 the number of long-term connections that are kept open between
2524 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
2525 - Relays now log hourly statistics (look for
2526 "channel_check_for_duplicates" lines) on the total number of
2527 connections to other relays. If the number of connections per
2528 relay is unexpectedly large, this log message is at notice level.
2529 Otherwise it is at info.
2531 o Major bugfixes (entry guards):
2532 - When starting with an old consensus, do not add new entry guards
2533 unless the consensus is "reasonably live" (under 1 day old). Fixes
2534 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2535 - Don't block bootstrapping when a primary bridge is offline and we
2536 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2537 21969; bugfix on 0.3.0.3-alpha.
2539 o Major bugfixes (linux TPROXY support):
2540 - Fix a typo that had prevented TPROXY-based transparent proxying
2541 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2542 Patch from "d4fq0fQAgoJ".
2544 o Major bugfixes (openbsd, denial-of-service):
2545 - Avoid an assertion failure bug affecting our implementation of
2546 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2547 handling of "0xx" differs from what we had expected. Fixes bug
2548 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2550 o Major bugfixes (relay, link handshake):
2551 - When performing the v3 link handshake on a TLS connection, report
2552 that we have the x509 certificate that we actually used on that
2553 connection, even if we have changed certificates since that
2554 connection was first opened. Previously, we would claim to have
2555 used our most recent x509 link certificate, which would sometimes
2556 make the link handshake fail. Fixes one case of bug 22460; bugfix
2559 o Major bugfixes (relays, key management):
2560 - Regenerate link and authentication certificates whenever the key
2561 that signs them changes; also, regenerate link certificates
2562 whenever the signed key changes. Previously, these processes were
2563 only weakly coupled, and we relays could (for minutes to hours)
2564 wind up with an inconsistent set of keys and certificates, which
2565 other relays would not accept. Fixes two cases of bug 22460;
2566 bugfix on 0.3.0.1-alpha.
2567 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2568 send the certificate that matches the x509 certificate that we
2569 used on the TLS connection. Previously, there was a race condition
2570 if the TLS context rotated after we began the TLS handshake but
2571 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2574 o Minor features (security, windows):
2575 - Enable a couple of pieces of Windows hardening: one
2576 (HeapEnableTerminationOnCorruption) that has been on-by-default
2577 since Windows 8, and unavailable before Windows 7; and one
2578 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2579 affect us, but shouldn't do any harm. Closes ticket 21953.
2581 o Minor features (bridge authority):
2582 - Add "fingerprint" lines to the networkstatus-bridges file produced
2583 by bridge authorities. Closes ticket 22207.
2585 o Minor features (code style):
2586 - Add "Falls through" comments to our codebase, in order to silence
2587 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
2588 Stieger. Closes ticket 22446.
2590 o Minor features (config options):
2591 - Allow "%include" directives in torrc configuration files. These
2592 directives import the settings from other files, or from all the
2593 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
2594 - Make SAVECONF return an error when overwriting a torrc that has
2595 includes. Using SAVECONF with the FORCE option will allow it to
2596 overwrite torrc even if includes are used. Related to ticket 1922.
2597 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
2598 will work without the FORCE option. Related to ticket 1922.
2600 o Minor features (controller):
2601 - Warn the first time that a controller requests data in the long-
2602 deprecated 'GETINFO network-status' format. Closes ticket 21703.
2604 o Minor features (defaults):
2605 - The default value for UseCreateFast is now 0: clients which
2606 haven't yet received a consensus document will now use a proper
2607 ntor handshake to talk to their directory servers whenever they
2608 can. Closes ticket 21407.
2609 - Onion key rotation and expiry intervals are now defined as a
2610 network consensus parameter, per proposal 274. The default
2611 lifetime of an onion key is increased from 7 to 28 days. Old onion
2612 keys will expire after 7 days by default. This change will make
2613 consensus diffs much smaller, and save significant bandwidth.
2614 Closes ticket 21641.
2616 o Minor features (defensive programming):
2617 - Create a pair of consensus parameters, nf_pad_tor2web and
2618 nf_pad_single_onion, to disable netflow padding in the consensus
2619 for non-anonymous connections in case the overhead is high. Closes
2622 o Minor features (diagnostic):
2623 - Add a stack trace to the bug warnings that can be logged when
2624 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
2625 attempt for bug 23105.
2626 - Add logging messages to try to diagnose a rare bug that seems to
2627 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
2628 think this is happening because of incorrect system clocks, but
2629 we'd like to know for certain. Diagnostic for bug 22466.
2630 - Avoid an assertion failure, and log a better error message, when
2631 unable to remove a file from the consensus cache on Windows.
2632 Attempts to mitigate and diagnose bug 22752.
2634 o Minor features (directory authority):
2635 - Improve the message that authorities report to relays that present
2636 RSA/Ed25519 keypairs that conflict with previously pinned keys.
2637 Closes ticket 22348.
2639 o Minor features (directory cache, consensus diff):
2640 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
2641 operators with low-resource environments to adjust the number of
2642 consensuses they'll store and generate diffs from. Most cache
2643 operators should leave it unchanged. Helps to work around
2646 o Minor features (fallback directory list):
2647 - Update the fallback directory mirror whitelist and blacklist based
2648 on operator emails. Closes task 21121.
2649 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2650 December 2016 (of which ~126 were still functional) with a list of
2651 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2652 2017. Resolves ticket 21564.
2654 o Minor features (geoip):
2655 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2658 o Minor features (hidden services, logging):
2659 - Log a message when a hidden service descriptor has fewer
2660 introduction points than specified in
2661 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
2662 - Log a message when a hidden service reaches its introduction point
2663 circuit limit, and when that limit is reset. Follow up to ticket
2664 21594; closes ticket 21622.
2665 - Warn user if multiple entries in EntryNodes and at least one
2666 HiddenService are used together. Pinning EntryNodes along with a
2667 hidden service can be possibly harmful; for instance see ticket
2668 14917 or 21155. Closes ticket 21155.
2670 o Minor features (linux seccomp2 sandbox):
2671 - We now have a document storage backend compatible with the Linux
2672 seccomp2 sandbox. This backend is used for consensus documents and
2673 diffs between them; in the long term, we'd like to use it for
2674 unparseable directory material too. Closes ticket 21645
2675 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
2676 from 1MB to 16MB. This was necessary with the glibc allocator in
2677 order to allow worker threads to allocate more memory -- which in
2678 turn is necessary because of our new use of worker threads for
2679 compression. Closes ticket 22096.
2681 o Minor features (logging):
2682 - Log files are no longer created world-readable by default.
2683 (Previously, most distributors would store the logs in a non-
2684 world-readable location to prevent inappropriate access. This
2685 change is an extra precaution.) Closes ticket 21729; patch
2688 o Minor features (performance):
2689 - Our Keccak (SHA-3) implementation now accesses memory more
2690 efficiently, especially on little-endian systems. Closes
2692 - Add an O(1) implementation of channel_find_by_global_id(), to
2693 speed some controller functions.
2695 o Minor features (relay, configuration):
2696 - The MyFamily option may now be repeated as many times as desired,
2697 for relays that want to configure large families. Closes ticket
2698 4998; patch by Daniel Pinto.
2700 o Minor features (relay, performance):
2701 - Always start relays with at least two worker threads, to prevent
2702 priority inversion on slow tasks. Part of the fix for bug 22883.
2703 - Allow background work to be queued with different priorities, so
2704 that a big pile of slow low-priority jobs will not starve out
2705 higher priority jobs. This lays the groundwork for a fix for
2708 o Minor features (safety):
2709 - Add an explicit check to extrainfo_parse_entry_from_string() for
2710 NULL inputs. We don't believe this can actually happen, but it may
2711 help silence a warning from the Clang analyzer. Closes
2714 o Minor features (testing):
2715 - Add more tests for compression backend initialization. Closes
2717 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
2718 When Tor is compiled with this option, we disable a number of
2719 redundant memory-safety failsafes that are intended to stop bugs
2720 from becoming security issues. This makes it easier to hunt for
2721 bugs that would be security issues without the failsafes turned
2722 on. Closes ticket 21439.
2723 - Add a general event-tracing instrumentation support to Tor. This
2724 subsystem will enable developers and researchers to add fine-
2725 grained instrumentation to their Tor instances, for use when
2726 examining Tor network performance issues. There are no trace
2727 events yet, and event-tracing is off by default unless enabled at
2728 compile time. Implements ticket 13802.
2729 - Improve our version parsing tests: add tests for typical version
2730 components, add tests for invalid versions, including numeric
2731 range and non-numeric prefixes. Unit tests 21278, 21450, and
2732 21507. Partially implements 21470.
2734 o Minor bugfixes (bandwidth accounting):
2735 - Roll over monthly accounting at the configured hour and minute,
2736 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2737 Found by Andrey Karpov with PVS-Studio.
2739 o Minor bugfixes (code correctness):
2740 - Accurately identify client connections by their lack of peer
2741 authentication. This means that we bail out earlier if asked to
2742 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
2745 o Minor bugfixes (compilation warnings):
2746 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
2747 22915; bugfix on 0.2.8.1-alpha.
2748 - Fix warnings when building with libscrypt and openssl scrypt
2749 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2750 - When building with certain versions of the mingw C header files,
2751 avoid float-conversion warnings when calling the C functions
2752 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2755 o Minor bugfixes (compilation):
2756 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
2757 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
2759 o Minor bugfixes (compression):
2760 - When spooling compressed data to an output buffer, don't try to
2761 spool more data when there is no more data to spool and we are not
2762 trying to flush the input. Previously, we would sometimes launch
2763 compression requests with nothing to do, which interferes with our
2764 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
2766 o Minor bugfixes (configuration):
2767 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2768 bug 22252; bugfix on 0.2.9.3-alpha.
2770 o Minor bugfixes (connection lifespan):
2771 - Allow more control over how long TLS connections are kept open:
2772 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
2773 single option called CircuitsAvailableTimeout. Also, allow the
2774 consensus to control the default values for both this preference
2775 and the lifespan of relay-to-relay connections. Fixes bug 17592;
2776 bugfix on 0.2.5.5-alpha.
2777 - Increase the initial circuit build timeout testing frequency, to
2778 help ensure that ReducedConnectionPadding clients finish learning
2779 a timeout before their orconn would expire. The initial testing
2780 rate was set back in the days of TAP and before the Tor Browser
2781 updater, when we had to be much more careful about new clients
2782 making lots of circuits. With this change, a circuit build timeout
2783 is learned in about 15-20 minutes, instead of 100-120 minutes.
2785 o Minor bugfixes (controller):
2786 - Do not crash when receiving a HSPOST command with an empty body.
2787 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
2788 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
2789 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
2790 - GETINFO onions/current and onions/detached no longer respond with
2791 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
2792 - Trigger HS descriptor events on the control port when the client
2793 fails to pick a hidden service directory for a hidden service.
2794 This can happen if all the hidden service directories are in
2795 ExcludeNodes, or they have all been queried within the last 15
2796 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
2798 o Minor bugfixes (correctness):
2799 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2800 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2802 o Minor bugfixes (coverity build support):
2803 - Avoid Coverity build warnings related to our BUG() macro. By
2804 default, Coverity treats BUG() as the Linux kernel does: an
2805 instant abort(). We need to override that so our BUG() macro
2806 doesn't prevent Coverity from analyzing functions that use it.
2807 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2809 o Minor bugfixes (defensive programming):
2810 - Detect and break out of infinite loops in our compression code. We
2811 don't think that any such loops exist now, but it's best to be
2812 safe. Closes ticket 22672.
2813 - Fix a memset() off the end of an array when packing cells. This
2814 bug should be harmless in practice, since the corrupted bytes are
2815 still in the same structure, and are always padding bytes,
2816 ignored, or immediately overwritten, depending on compiler
2817 behavior. Nevertheless, because the memset()'s purpose is to make
2818 sure that any other cell-handling bugs can't expose bytes to the
2819 network, we need to fix it. Fixes bug 22737; bugfix on
2820 0.2.4.11-alpha. Fixes CID 1401591.
2822 o Minor bugfixes (directory authority):
2823 - When a directory authority rejects a descriptor or extrainfo with
2824 a given digest, mark that digest as undownloadable, so that we do
2825 not attempt to download it again over and over. We previously
2826 tried to avoid downloading such descriptors by other means, but we
2827 didn't notice if we accidentally downloaded one anyway. This
2828 behavior became problematic in 0.2.7.2-alpha, when authorities
2829 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2831 - When rejecting a router descriptor for running an obsolete version
2832 of Tor without ntor support, warn about the obsolete tor version,
2833 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2834 - Prevent the shared randomness subsystem from asserting when
2835 initialized by a bridge authority with an incomplete configuration
2836 file. Fixes bug 21586; bugfix on 0.2.9.8.
2838 o Minor bugfixes (error reporting, windows):
2839 - When formatting Windows error messages, use the English format to
2840 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2843 o Minor bugfixes (exit-side DNS):
2844 - Fix an untriggerable assertion that checked the output of a
2845 libevent DNS error, so that the assertion actually behaves as
2846 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
2847 Karpov using PVS-Studio.
2849 o Minor bugfixes (fallback directories):
2850 - Make the usage example in updateFallbackDirs.py actually work, and
2851 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
2852 - Decrease the guard flag average required to be a fallback. This
2853 allows us to keep relays that have their guard flag removed when
2854 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2855 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
2856 bugfix on 0.2.8.1-alpha.
2857 - Make sure fallback directory mirrors have the same address, port,
2858 and relay identity key for at least 30 days before they are
2859 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2861 o Minor bugfixes (file limits, osx):
2862 - When setting the maximum number of connections allowed by the OS,
2863 always allow some extra file descriptors for other files. Fixes
2864 bug 22797; bugfix on 0.2.0.10-alpha.
2866 o Minor bugfixes (hidden services):
2867 - Increase the number of circuits that a service is allowed to
2868 open over a specific period of time. The value was lower than it
2869 should be (8 vs 12) in the normal case of 3 introduction points.
2870 Fixes bug 22159; bugfix on 0.3.0.5-rc.
2871 - Fix a BUG warning during HSv3 descriptor decoding that could be
2872 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
2873 on 0.3.0.1-alpha. Bug found by "haxxpop".
2874 - Stop printing a cryptic warning when a hidden service gets a
2875 request to connect to a virtual port that it hasn't configured.
2876 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
2877 - Simplify hidden service descriptor creation by using an existing
2878 flag to check if an introduction point is established. Fixes bug
2879 21599; bugfix on 0.2.7.2-alpha.
2881 o Minor bugfixes (link handshake):
2882 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2883 months, and regenerate it when it is within one month of expiring.
2884 Previously, we had generated this certificate at startup with a
2885 ten-year lifetime, but that could lead to weird behavior when Tor
2886 was started with a grossly inaccurate clock. Mitigates bug 22466;
2887 mitigation on 0.3.0.1-alpha.
2889 o Minor bugfixes (linux seccomp2 sandbox):
2890 - Avoid a sandbox failure when trying to re-bind to a socket and
2891 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2892 - Permit the fchmod system call, to avoid crashing on startup when
2893 starting with the seccomp2 sandbox and an unexpected set of
2894 permissions on the data directory or its contents. Fixes bug
2895 22516; bugfix on 0.2.5.4-alpha.
2897 o Minor bugfixes (logging):
2898 - When decompressing, do not warn if we fail to decompress using a
2899 compression method that we merely guessed. Fixes part of bug
2900 22670; bugfix on 0.1.1.14-alpha.
2901 - When decompressing, treat mismatch between content-encoding and
2902 actual compression type as a protocol warning. Fixes part of bug
2903 22670; bugfix on 0.1.1.9-alpha.
2904 - Downgrade "assigned_to_cpuworker failed" message to info-level
2905 severity. In every case that can reach it, either a better warning
2906 has already been logged, or no warning is warranted. Fixes bug
2907 22356; bugfix on 0.2.6.3-alpha.
2908 - Log a better message when a directory authority replies to an
2909 upload with an unexpected status code. Fixes bug 11121; bugfix
2911 - Downgrade a log statement about unexpected relay cells from "bug"
2912 to "protocol warning", because there is at least one use case
2913 where it can be triggered by a buggy tor implementation. Fixes bug
2914 21293; bugfix on 0.1.1.14-alpha.
2916 o Minor bugfixes (logging, relay):
2917 - Remove a forgotten debugging message when an introduction point
2918 successfully establishes a hidden service prop224 circuit with
2920 - Change three other log_warn() for an introduction point to
2921 protocol warnings, because they can be failure from the network
2922 and are not relevant to the operator. Fixes bug 23078; bugfix on
2923 0.3.0.1-alpha and 0.3.0.2-alpha.
2925 o Minor bugfixes (relay):
2926 - Inform the geoip and rephist modules about all requests, even on
2927 relays that are only fetching microdescriptors. Fixes a bug
2928 related to 21585; bugfix on 0.3.0.1-alpha.
2930 o Minor bugfixes (memory leaks):
2931 - Fix a small memory leak at exit from the backtrace handler code.
2932 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
2933 - When directory authorities reject a router descriptor due to
2934 keypinning, free the router descriptor rather than leaking the
2935 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2936 - Fix a small memory leak when validating a configuration that uses
2937 two or more AF_UNIX sockets for the same port type. Fixes bug
2938 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2940 o Minor bugfixes (process behavior):
2941 - When exiting because of an error, always exit with a nonzero exit
2942 status. Previously, we would fail to report an error in our exit
2943 status in cases related to __OwningControllerProcess failure,
2944 lockfile contention, and Ed25519 key initialization. Fixes bug
2945 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
2946 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
2949 o Minor bugfixes (robustness, error handling):
2950 - Improve our handling of the cases where OpenSSL encounters a
2951 memory error while encoding keys and certificates. We haven't
2952 observed these errors in the wild, but if they do happen, we now
2953 detect and respond better. Fixes bug 19418; bugfix on all versions
2954 of Tor. Reported by Guido Vranken.
2956 o Minor bugfixes (testing):
2957 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2958 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2959 - Use unbuffered I/O for utility functions around the
2960 process_handle_t type. This fixes unit test failures reported on
2961 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
2962 - Make display of captured unit test log messages consistent. Fixes
2963 bug 21510; bugfix on 0.2.9.3-alpha.
2964 - Make test-network.sh always call chutney's test-network.sh.
2965 Previously, this only worked on systems which had bash installed,
2966 due to some bash-specific code in the script. Fixes bug 19699;
2967 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
2968 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2969 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2970 - The unit tests now pass on systems where localhost is misconfigured
2971 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
2974 o Minor bugfixes (voting consistency):
2975 - Reject version numbers with non-numeric prefixes (such as +, -, or
2976 whitespace). Disallowing whitespace prevents differential version
2977 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2978 and part of 21508; bugfix on 0.0.8pre1.
2980 o Minor bugfixes (Windows service):
2981 - When running as a Windows service, set the ID of the main thread
2982 correctly. Failure to do so made us fail to send log messages to
2983 the controller in 0.2.1.16-rc, slowed down controller event
2984 delivery in 0.2.7.3-rc and later, and crash with an assertion
2985 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2986 Patch and diagnosis from "Vort".
2988 o Minor bugfixes (windows, relay):
2989 - Resolve "Failure from drain_fd: No error" warnings on Windows
2990 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
2992 o Code simplification and refactoring:
2993 - Break up the 630-line function connection_dir_client_reached_eof()
2994 into a dozen smaller functions. This change should help
2995 maintainability and readability of the client directory code.
2996 - Isolate our use of the openssl headers so that they are only
2997 included from our crypto wrapper modules, and from tests that
2998 examine those modules' internals. Closes ticket 21841.
2999 - Simplify our API to launch directory requests, making it more
3000 extensible and less error-prone. Now it's easier to add extra
3001 headers to directory requests. Closes ticket 21646.
3002 - Our base64 decoding functions no longer overestimate the output
3003 space that they need when parsing unpadded inputs. Closes
3005 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
3006 Resolves ticket 22213.
3007 - The logic that directory caches use to spool request to clients,
3008 serving them one part at a time so as not to allocate too much
3009 memory, has been refactored for consistency. Previously there was
3010 a separate spooling implementation per type of spoolable data. Now
3011 there is one common spooling implementation, with extensible data
3012 types. Closes ticket 21651.
3013 - Tor's compression module now supports multiple backends. Part of
3014 the implementation for proposal 278; closes ticket 21663.
3017 - Add a manpage description for the key-pinning-journal file. Closes
3019 - Correctly note that bandwidth accounting values are stored in the
3020 state file, and the bw_accounting file is now obsolete. Closes
3022 - Document more of the files in the Tor data directory, including
3023 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
3024 approved-routers, sr-random, and diff-cache. Found while fixing
3026 - Clarify the manpage for the (deprecated) torify script. Closes
3028 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
3029 Closes ticket 21873.
3030 - Correct documentation about the default DataDirectory value.
3031 Closes ticket 21151.
3032 - Document the default behavior of NumEntryGuards and
3033 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
3035 - Document key=value pluggable transport arguments for Bridge lines
3036 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
3037 - Note that bandwidth-limiting options don't affect TCP headers or
3038 DNS. Closes ticket 17170.
3040 o Removed features (configuration options, all in ticket 22060):
3041 - These configuration options are now marked Obsolete, and no longer
3042 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3043 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3044 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3045 in 0.2.9.2-alpha and have now been removed. The previous default
3046 behavior is now always chosen; the previous (less secure) non-
3047 default behavior is now unavailable.
3048 - CloseHSClientCircuitsImmediatelyOnTimeout and
3049 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3050 0.2.9.2-alpha and now have been removed. HS circuits never close
3051 on circuit build timeout; they have a longer timeout period.
3052 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3053 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3054 (and others) to configure listen-only and advertise-only addresses.
3056 o Removed features (tools):
3057 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3058 used it to help people detect RSA keys that were generated by
3059 versions of Debian affected by CVE-2008-0166. But those keys have
3060 been out of circulation for ages, and this tool is no longer
3061 required. Closes ticket 21842.
3064 Changes in version 0.3.0.10 - 2017-08-02
3065 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
3066 from the current Tor alpha series. OpenBSD users and TPROXY users
3067 should upgrade; others are probably okay sticking with 0.3.0.9.
3069 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
3070 - Tor's repository now includes a Travis Continuous Integration (CI)
3071 configuration file (.travis.yml). This is meant to help new
3072 developers and contributors who fork Tor to a Github repository be
3073 better able to test their changes, and understand what we expect
3074 to pass. To use this new build feature, you must fork Tor to your
3075 Github account, then go into the "Integrations" menu in the
3076 repository settings for your fork and enable Travis, then push
3077 your changes. Closes ticket 22636.
3079 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3080 - Fix a typo that had prevented TPROXY-based transparent proxying
3081 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3082 Patch from "d4fq0fQAgoJ".
3084 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3085 - Avoid an assertion failure bug affecting our implementation of
3086 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3087 handling of "0xbar" differs from what we had expected. Fixes bug
3088 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3090 o Minor features (backport from 0.3.1.5-alpha):
3091 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
3094 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
3095 - Roll over monthly accounting at the configured hour and minute,
3096 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3097 Found by Andrey Karpov with PVS-Studio.
3099 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
3100 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3101 bugfix on 0.2.8.1-alpha.
3102 - Fix warnings when building with libscrypt and openssl scrypt
3103 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3104 - When building with certain versions of the mingw C header files,
3105 avoid float-conversion warnings when calling the C functions
3106 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3109 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3110 - Backport a fix for an "unused variable" warning that appeared
3111 in some versions of mingw. Fixes bug 22838; bugfix on
3114 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3115 - Avoid Coverity build warnings related to our BUG() macro. By
3116 default, Coverity treats BUG() as the Linux kernel does: an
3117 instant abort(). We need to override that so our BUG() macro
3118 doesn't prevent Coverity from analyzing functions that use it.
3119 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3121 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
3122 - When rejecting a router descriptor for running an obsolete version
3123 of Tor without ntor support, warn about the obsolete tor version,
3124 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3126 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3127 - Avoid a sandbox failure when trying to re-bind to a socket and
3128 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3130 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
3131 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3132 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3135 Changes in version 0.3.0.9 - 2017-06-29
3136 Tor 0.3.0.9 fixes a path selection bug that would allow a client
3137 to use a guard that was in the same network family as a chosen exit
3138 relay. This is a security regression; all clients running earlier
3139 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
3142 This release also backports several other bugfixes from the 0.3.1.x
3145 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
3146 - When choosing which guard to use for a circuit, avoid the exit's
3147 family along with the exit itself. Previously, the new guard
3148 selection logic avoided the exit, but did not consider its family.
3149 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3150 006 and CVE-2017-0377.
3152 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
3153 - Don't block bootstrapping when a primary bridge is offline and we
3154 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3155 21969; bugfix on 0.3.0.3-alpha.
3157 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
3158 - When starting with an old consensus, do not add new entry guards
3159 unless the consensus is "reasonably live" (under 1 day old). Fixes
3160 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3162 o Minor features (geoip):
3163 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3166 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3167 - Reject version numbers with non-numeric prefixes (such as +, -, or
3168 whitespace). Disallowing whitespace prevents differential version
3169 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3170 and part of 21508; bugfix on 0.0.8pre1.
3172 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3173 - Permit the fchmod system call, to avoid crashing on startup when
3174 starting with the seccomp2 sandbox and an unexpected set of
3175 permissions on the data directory or its contents. Fixes bug
3176 22516; bugfix on 0.2.5.4-alpha.
3178 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
3179 - Fix a memset() off the end of an array when packing cells. This
3180 bug should be harmless in practice, since the corrupted bytes are
3181 still in the same structure, and are always padding bytes,
3182 ignored, or immediately overwritten, depending on compiler
3183 behavior. Nevertheless, because the memset()'s purpose is to make
3184 sure that any other cell-handling bugs can't expose bytes to the
3185 network, we need to fix it. Fixes bug 22737; bugfix on
3186 0.2.4.11-alpha. Fixes CID 1401591.
3189 Changes in version 0.3.0.8 - 2017-06-08
3190 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
3191 remotely crash a hidden service with an assertion failure. Anyone
3192 running a hidden service should upgrade to this version, or to some
3193 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3195 Tor 0.3.0.8 also includes fixes for several key management bugs
3196 that sometimes made relays unreliable, as well as several other
3197 bugfixes described below.
3199 o Major bugfixes (hidden service, relay, security, backport
3200 from 0.3.1.3-alpha):
3201 - Fix a remotely triggerable assertion failure when a hidden service
3202 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3203 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3204 - Fix a remotely triggerable assertion failure caused by receiving a
3205 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3206 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3209 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3210 - When performing the v3 link handshake on a TLS connection, report
3211 that we have the x509 certificate that we actually used on that
3212 connection, even if we have changed certificates since that
3213 connection was first opened. Previously, we would claim to have
3214 used our most recent x509 link certificate, which would sometimes
3215 make the link handshake fail. Fixes one case of bug 22460; bugfix
3218 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
3219 - Regenerate link and authentication certificates whenever the key
3220 that signs them changes; also, regenerate link certificates
3221 whenever the signed key changes. Previously, these processes were
3222 only weakly coupled, and we relays could (for minutes to hours)
3223 wind up with an inconsistent set of keys and certificates, which
3224 other relays would not accept. Fixes two cases of bug 22460;
3225 bugfix on 0.3.0.1-alpha.
3226 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3227 send the certificate that matches the x509 certificate that we
3228 used on the TLS connection. Previously, there was a race condition
3229 if the TLS context rotated after we began the TLS handshake but
3230 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3233 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
3234 - Stop rejecting v3 hidden service descriptors because their size
3235 did not match an old padding rule. Fixes bug 22447; bugfix on
3238 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3239 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3240 December 2016 (of which ~126 were still functional) with a list of
3241 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3242 2017. Resolves ticket 21564.
3244 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
3245 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3246 bug 22252; bugfix on 0.2.9.3-alpha.
3248 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
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 (link handshake, backport from 0.3.1.3-alpha):
3253 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3254 months, and regenerate it when it is within one month of expiring.
3255 Previously, we had generated this certificate at startup with a
3256 ten-year lifetime, but that could lead to weird behavior when Tor
3257 was started with a grossly inaccurate clock. Mitigates bug 22466;
3258 mitigation on 0.3.0.1-alpha.
3260 o Minor bugfixes (memory leak, directory authority, backport from
3262 - When directory authorities reject a router descriptor due to
3263 keypinning, free the router descriptor rather than leaking the
3264 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3267 Changes in version 0.2.9.11 - 2017-06-08
3268 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
3269 remotely crash a hidden service with an assertion failure. Anyone
3270 running a hidden service should upgrade to this version, or to some
3271 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3272 are not affected by TROVE-2017-004.)
3274 Tor 0.2.9.11 also backports fixes for several key management bugs
3275 that sometimes made relays unreliable, as well as several other
3276 bugfixes described below.
3278 o Major bugfixes (hidden service, relay, security, backport
3279 from 0.3.1.3-alpha):
3280 - Fix a remotely triggerable assertion failure caused by receiving a
3281 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3282 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3285 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3286 - When performing the v3 link handshake on a TLS connection, report
3287 that we have the x509 certificate that we actually used on that
3288 connection, even if we have changed certificates since that
3289 connection was first opened. Previously, we would claim to have
3290 used our most recent x509 link certificate, which would sometimes
3291 make the link handshake fail. Fixes one case of bug 22460; bugfix
3294 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3295 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3296 December 2016 (of which ~126 were still functional) with a list of
3297 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3298 2017. Resolves ticket 21564.
3300 o Minor features (future-proofing, backport from 0.3.0.7):
3301 - Tor no longer refuses to download microdescriptors or descriptors if
3302 they are listed as "published in the future". This change will
3303 eventually allow us to stop listing meaningful "published" dates
3304 in microdescriptor consensuses, and thereby allow us to reduce the
3305 resources required to download consensus diffs by over 50%.
3306 Implements part of ticket 21642; implements part of proposal 275.
3308 o Minor features (directory authorities, backport from 0.3.0.4-rc)
3309 - Directory authorities now reject relays running versions
3310 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
3311 suffer from bug 20499 and don't keep their consensus cache
3312 up-to-date. Resolves ticket 20509.
3314 o Minor features (geoip):
3315 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3318 o Minor bugfixes (control port, backport from 0.3.0.6):
3319 - The GETINFO extra-info/digest/<digest> command was broken because
3320 of a wrong base16 decode return value check, introduced when
3321 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3323 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
3324 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3325 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3327 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
3328 - The getpid() system call is now permitted under the Linux seccomp2
3329 sandbox, to avoid crashing with versions of OpenSSL (and other
3330 libraries) that attempt to learn the process's PID by using the
3331 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3334 o Minor bugfixes (memory leak, directory authority, backport
3335 from 0.3.1.2-alpha):
3336 - When directory authorities reject a router descriptor due to
3337 keypinning, free the router descriptor rather than leaking the
3338 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3340 Changes in version 0.2.8.14 - 2017-06-08
3341 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3342 remotely crash a hidden service with an assertion failure. Anyone
3343 running a hidden service should upgrade to this version, or to some
3344 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3345 are not affected by TROVE-2017-004.)
3347 o Major bugfixes (hidden service, relay, security):
3348 - Fix a remotely triggerable assertion failure caused by receiving a
3349 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3350 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3353 o Minor features (geoip):
3354 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3357 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
3358 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3359 December 2016 (of which ~126 were still functional) with a list of
3360 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3361 2017. Resolves ticket 21564.
3363 o Minor bugfixes (correctness):
3364 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3365 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3367 Changes in version 0.2.7.8 - 2017-06-08
3368 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
3369 remotely crash a hidden service with an assertion failure. Anyone
3370 running a hidden service should upgrade to this version, or to some
3371 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3372 are not affected by TROVE-2017-004.)
3374 o Major bugfixes (hidden service, relay, security):
3375 - Fix a remotely triggerable assertion failure caused by receiving a
3376 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3377 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3380 o Minor features (geoip):
3381 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3384 o Minor bugfixes (correctness):
3385 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3386 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3389 Changes in version 0.2.6.12 - 2017-06-08
3390 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
3391 remotely crash a hidden service with an assertion failure. Anyone
3392 running a hidden service should upgrade to this version, or to some
3393 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3394 are not affected by TROVE-2017-004.)
3396 o Major bugfixes (hidden service, relay, security):
3397 - Fix a remotely triggerable assertion failure caused by receiving a
3398 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3399 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3402 o Minor features (geoip):
3403 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3406 o Minor bugfixes (correctness):
3407 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3408 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3410 Changes in version 0.2.5.14 - 2017-06-08
3411 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
3412 remotely crash a hidden service with an assertion failure. Anyone
3413 running a hidden service should upgrade to this version, or to some
3414 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3415 are not affected by TROVE-2017-004.)
3417 o Major bugfixes (hidden service, relay, security):
3418 - Fix a remotely triggerable assertion failure caused by receiving a
3419 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3420 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3423 o Minor features (geoip):
3424 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3427 o Minor bugfixes (correctness):
3428 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3429 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3431 Changes in version 0.2.4.29 - 2017-06-08
3432 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
3433 remotely crash a hidden service with an assertion failure. Anyone
3434 running a hidden service should upgrade to this version, or to some
3435 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
3436 are not affected by TROVE-2017-004.)
3438 o Major bugfixes (hidden service, relay, security):
3439 - Fix a remotely triggerable assertion failure caused by receiving a
3440 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3441 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3444 o Minor features (geoip):
3445 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3448 o Minor bugfixes (correctness):
3449 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3450 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3453 Changes in version 0.3.0.7 - 2017-05-15
3454 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
3455 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
3456 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
3457 clients are not affected.
3459 o Major bugfixes (hidden service directory, security):
3460 - Fix an assertion failure in the hidden service directory code, which
3461 could be used by an attacker to remotely cause a Tor relay process to
3462 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
3463 should upgrade. This security issue is tracked as TROVE-2017-002.
3464 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
3467 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
3470 o Minor features (future-proofing):
3471 - Tor no longer refuses to download microdescriptors or descriptors
3472 if they are listed as "published in the future". This change will
3473 eventually allow us to stop listing meaningful "published" dates
3474 in microdescriptor consensuses, and thereby allow us to reduce the
3475 resources required to download consensus diffs by over 50%.
3476 Implements part of ticket 21642; implements part of proposal 275.
3478 o Minor bugfixes (Linux seccomp2 sandbox):
3479 - The getpid() system call is now permitted under the Linux seccomp2
3480 sandbox, to avoid crashing with versions of OpenSSL (and other
3481 libraries) that attempt to learn the process's PID by using the
3482 syscall rather than the VDSO code. Fixes bug 21943; bugfix
3486 Changes in version 0.3.0.6 - 2017-04-26
3487 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
3489 With the 0.3.0 series, clients and relays now use Ed25519 keys to
3490 authenticate their link connections to relays, rather than the old
3491 RSA1024 keys that they used before. (Circuit crypto has been
3492 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
3493 the guard selection and replacement algorithm to behave more robustly
3494 in the presence of unreliable networks, and to resist guard-
3497 This series also includes numerous other small features and bugfixes,
3498 along with more groundwork for the upcoming hidden-services revamp.
3500 Per our stable release policy, we plan to support the Tor 0.3.0
3501 release series for at least the next nine months, or for three months
3502 after the first stable release of the 0.3.1 series: whichever is
3503 longer. If you need a release with long-term support, we recommend
3504 that you stay with the 0.2.9 series.
3506 Below are the changes since 0.2.9.10. For a list of only the changes
3507 since 0.3.0.5-rc, see the ChangeLog file.
3509 o Major features (directory authority, security):
3510 - The default for AuthDirPinKeys is now 1: directory authorities
3511 will reject relays where the RSA identity key matches a previously
3512 seen value, but the Ed25519 key has changed. Closes ticket 18319.
3514 o Major features (guard selection algorithm):
3515 - Tor's guard selection algorithm has been redesigned from the
3516 ground up, to better support unreliable networks and restrictive
3517 sets of entry nodes, and to better resist guard-capture attacks by
3518 hostile local networks. Implements proposal 271; closes
3521 o Major features (next-generation hidden services):
3522 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
3523 prop224 aka "Next Generation Hidden Services". Service and clients
3524 don't use this functionality yet. Closes ticket 19043. Based on
3525 initial code by Alec Heifetz.
3526 - Relays now support the HSDir version 3 protocol, so that they can
3527 can store and serve v3 descriptors. This is part of the next-
3528 generation onion service work detailed in proposal 224. Closes
3531 o Major features (protocol, ed25519 identity keys):
3532 - Clients now support including Ed25519 identity keys in the EXTEND2
3533 cells they generate. By default, this is controlled by a consensus
3534 parameter, currently disabled. You can turn this feature on for
3535 testing by setting ExtendByEd25519ID in your configuration. This
3536 might make your traffic appear different than the traffic
3537 generated by other users, however. Implements part of ticket
3538 15056; part of proposal 220.
3539 - Relays now understand requests to extend to other relays by their
3540 Ed25519 identity keys. When an Ed25519 identity key is included in
3541 an EXTEND2 cell, the relay will only extend the circuit if the
3542 other relay can prove ownership of that identity. Implements part
3543 of ticket 15056; part of proposal 220.
3544 - Relays now use Ed25519 to prove their Ed25519 identities and to
3545 one another, and to clients. This algorithm is faster and more
3546 secure than the RSA-based handshake we've been doing until now.
3547 Implements the second big part of proposal 220; Closes
3550 o Major features (security):
3551 - Change the algorithm used to decide DNS TTLs on client and server
3552 side, to better resist DNS-based correlation attacks like the
3553 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3554 Feamster. Now relays only return one of two possible DNS TTL
3555 values, and clients are willing to believe DNS TTL values up to 3
3556 hours long. Closes ticket 19769.
3558 o Major bugfixes (client, onion service, also in 0.2.9.9):
3559 - Fix a client-side onion service reachability bug, where multiple
3560 socks requests to an onion service (or a single slow request)
3561 could cause us to mistakenly mark some of the service's
3562 introduction points as failed, and we cache that failure so
3563 eventually we run out and can't reach the service. Also resolves a
3564 mysterious "Remote server sent bogus reason code 65021" log
3565 warning. The bug was introduced in ticket 17218, where we tried to
3566 remember the circuit end reason as a uint16_t, which mangled
3567 negative values. Partially fixes bug 21056 and fixes bug 20307;
3568 bugfix on 0.2.8.1-alpha.
3570 o Major bugfixes (crash, directory connections):
3571 - Fix a rare crash when sending a begin cell on a circuit whose
3572 linked directory connection had already been closed. Fixes bug
3573 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3575 o Major bugfixes (directory authority):
3576 - During voting, when marking a relay as a probable sybil, do not
3577 clear its BadExit flag: sybils can still be bad in other ways
3578 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3581 o Major bugfixes (DNS):
3582 - Fix a bug that prevented exit nodes from caching DNS records for
3583 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3585 o Major bugfixes (IPv6 Exits):
3586 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3587 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3588 exit policy rejects that port on more than an IPv6 /16 of
3589 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3590 which rejected a relay's own IPv6 address by default. Fixes bug
3591 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3593 o Major bugfixes (parsing):
3594 - Fix an integer underflow bug when comparing malformed Tor
3595 versions. This bug could crash Tor when built with
3596 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3597 0.2.9.8, which were built with -ftrapv by default. In other cases
3598 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3599 on 0.0.8pre1. Found by OSS-Fuzz.
3600 - When parsing a malformed content-length field from an HTTP
3601 message, do not read off the end of the buffer. This bug was a
3602 potential remote denial-of-service attack against Tor clients and
3603 relays. A workaround was released in October 2016, to prevent this
3604 bug from crashing Tor. This is a fix for the underlying issue,
3605 which should no longer matter (if you applied the earlier patch).
3606 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
3607 using AFL (http://lcamtuf.coredump.cx/afl/).
3609 o Major bugfixes (scheduler):
3610 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
3611 caused the channel scheduler to behave more or less randomly,
3612 rather than preferring channels with higher-priority circuits.
3613 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
3615 o Major bugfixes (security, also in 0.2.9.9):
3616 - Downgrade the "-ftrapv" option from "always on" to "only on when
3617 --enable-expensive-hardening is provided." This hardening option,
3618 like others, can turn survivable bugs into crashes--and having it
3619 on by default made a (relatively harmless) integer overflow bug
3620 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
3621 bugfix on 0.2.9.1-alpha.
3623 o Minor feature (client):
3624 - Enable IPv6 traffic on the SocksPort by default. To disable this,
3625 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
3627 o Minor feature (fallback scripts):
3628 - Add a check_existing mode to updateFallbackDirs.py, which checks
3629 if fallbacks in the hard-coded list are working. Closes ticket
3630 20174. Patch by haxxpop.
3632 o Minor feature (protocol versioning):
3633 - Add new protocol version for proposal 224. HSIntro now advertises
3634 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
3636 o Minor features (ciphersuite selection):
3637 - Allow relays to accept a wider range of ciphersuites, including
3638 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
3639 - Clients now advertise a list of ciphersuites closer to the ones
3640 preferred by Firefox. Closes part of ticket 15426.
3642 o Minor features (controller):
3643 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
3644 shared-random values to the controller. Closes ticket 19925.
3645 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
3646 rather than "unrecognized." Closes ticket 20389; patch from
3649 o Minor features (controller, configuration):
3650 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
3651 and so on, now comes with a __*Port variant that will not be saved
3652 to the torrc file by the controller's SAVECONF command. This
3653 change allows TorBrowser to set up a single-use domain socket for
3654 each time it launches Tor. Closes ticket 20956.
3655 - The GETCONF command can now query options that may only be
3656 meaningful in context-sensitive lists. This allows the controller
3657 to query the mixed SocksPort/__SocksPort style options introduced
3658 in feature 20956. Implements ticket 21300.
3660 o Minor features (diagnostic, directory client):
3661 - Warn when we find an unexpected inconsistency in directory
3662 download status objects. Prevents some negative consequences of
3665 o Minor features (directory authorities):
3666 - Directory authorities now reject descriptors that claim to be
3667 malformed versions of Tor. Helps prevent exploitation of
3669 - Reject version numbers with components that exceed INT32_MAX.
3670 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3671 Fixes bug 21450; bugfix on 0.0.8pre1.
3673 o Minor features (directory authority):
3674 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
3675 default) to control whether authorities should try to probe relays
3676 by their Ed25519 link keys. This option will go away in a few
3677 releases--unless we encounter major trouble in our ed25519 link
3678 protocol rollout, in which case it will serve as a safety option.
3680 o Minor features (directory cache):
3681 - Relays and bridges will now refuse to serve the consensus they
3682 have if they know it is too old for a client to use. Closes
3685 o Minor features (ed25519 link handshake):
3686 - Advertise support for the ed25519 link handshake using the
3687 subprotocol-versions mechanism, so that clients can tell which
3688 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
3690 o Minor features (entry guards):
3691 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
3692 break regression tests.
3693 - Require UseEntryGuards when UseBridges is set, in order to make
3694 sure bridges aren't bypassed. Resolves ticket 20502.
3696 o Minor features (fallback directories):
3697 - Allow 3 fallback relays per operator, which is safe now that we
3698 are choosing 200 fallback relays. Closes ticket 20912.
3699 - Annotate updateFallbackDirs.py with the bandwidth and consensus
3700 weight for each candidate fallback. Closes ticket 20878.
3701 - Display the relay fingerprint when downloading consensuses from
3702 fallbacks. Closes ticket 20908.
3703 - Exclude relays affected by bug 20499 from the fallback list.
3704 Exclude relays from the fallback list if they are running versions
3705 known to be affected by bug 20499, or if in our tests they deliver
3706 a stale consensus (i.e. one that expired more than 24 hours ago).
3707 Closes ticket 20539.
3708 - Make it easier to change the output sort order of fallbacks.
3709 Closes ticket 20822.
3710 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
3712 - Require fallback directories to have the same address and port for
3713 7 days (now that we have enough relays with this stability).
3714 Relays whose OnionOO stability timer is reset on restart by bug
3715 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
3716 this issue. Closes ticket 20880; maintains short-term fix
3718 - Require fallbacks to have flags for 90% of the time (weighted
3719 decaying average), rather than 95%. This allows at least 73% of
3720 clients to bootstrap in the first 5 seconds without contacting an
3721 authority. Part of ticket 18828.
3722 - Select 200 fallback directories for each release. Closes
3725 o Minor features (fingerprinting resistance, authentication):
3726 - Extend the length of RSA keys used for TLS link authentication to
3727 2048 bits. (These weren't used for forward secrecy; for forward
3728 secrecy, we used P256.) Closes ticket 13752.
3730 o Minor features (geoip):
3731 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
3734 o Minor features (geoip, also in 0.2.9.9):
3735 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
3738 o Minor features (infrastructure):
3739 - Implement smartlist_add_strdup() function. Replaces the use of
3740 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
3742 o Minor features (linting):
3743 - Enhance the changes file linter to warn on Tor versions that are
3744 prefixed with "tor-". Closes ticket 21096.
3746 o Minor features (logging):
3747 - In several places, describe unset ed25519 keys as "<unset>",
3748 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
3750 o Minor features (portability, compilation):
3751 - Autoconf now checks to determine if OpenSSL structures are opaque,
3752 instead of explicitly checking for OpenSSL version numbers. Part
3754 - Support building with recent LibreSSL code that uses opaque
3755 structures. Closes ticket 21359.
3757 o Minor features (relay):
3758 - We now allow separation of exit and relay traffic to different
3759 source IP addresses, using the OutboundBindAddressExit and
3760 OutboundBindAddressOR options respectively. Closes ticket 17975.
3761 Written by Michael Sonntag.
3763 o Minor features (reliability, crash):
3764 - Try better to detect problems in buffers where they might grow (or
3765 think they have grown) over 2 GB in size. Diagnostic for
3768 o Minor features (testing):
3769 - During 'make test-network-all', if tor logs any warnings, ask
3770 chutney to output them. Requires a recent version of chutney with
3771 the 21572 patch. Implements 21570.
3773 o Minor bugfix (control protocol):
3774 - The reply to a "GETINFO config/names" request via the control
3775 protocol now spells the type "Dependent" correctly. This is a
3776 breaking change in the control protocol. (The field seems to be
3777 ignored by the most common known controllers.) Fixes bug 18146;
3778 bugfix on 0.1.1.4-alpha.
3779 - The GETINFO extra-info/digest/<digest> command was broken because
3780 of a wrong base16 decode return value check, introduced when
3781 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
3783 o Minor bugfix (logging):
3784 - Don't recommend the use of Tor2web in non-anonymous mode.
3785 Recommending Tor2web is a bad idea because the client loses all
3786 anonymity. Tor2web should only be used in specific cases by users
3787 who *know* and understand the issues. Fixes bug 21294; bugfix
3790 o Minor bugfixes (bug resilience):
3791 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
3792 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
3793 Hans Jerry Illikainen.
3795 o Minor bugfixes (build):
3796 - Replace obsolete Autoconf macros with their modern equivalent and
3797 prevent similar issues in the future. Fixes bug 20990; bugfix
3800 o Minor bugfixes (certificate expiration time):
3801 - Avoid using link certificates that don't become valid till some
3802 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
3804 o Minor bugfixes (client):
3805 - Always recover from failures in extend_info_from_node(), in an
3806 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
3807 bugfix on 0.2.3.1-alpha.
3808 - When clients that use bridges start up with a cached consensus on
3809 disk, they were ignoring it and downloading a new one. Now they
3810 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
3812 o Minor bugfixes (code correctness):
3813 - Repair a couple of (unreachable or harmless) cases of the risky
3814 comparison-by-subtraction pattern that caused bug 21278.
3816 o Minor bugfixes (config):
3817 - Don't assert on startup when trying to get the options list and
3818 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
3819 options so of course they aren't ready yet. Fixes bug 21062;
3820 bugfix on 0.2.9.3-alpha.
3822 o Minor bugfixes (configuration):
3823 - Accept non-space whitespace characters after the severity level in
3824 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
3825 - Support "TByte" and "TBytes" units in options given in bytes.
3826 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
3827 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
3829 o Minor bugfixes (configure, autoconf):
3830 - Rename the configure option --enable-expensive-hardening to
3831 --enable-fragile-hardening. Expensive hardening makes the tor
3832 daemon abort when some kinds of issues are detected. Thus, it
3833 makes tor more at risk of remote crashes but safer against RCE or
3834 heartbleed bug category. We now try to explain this issue in a
3835 message from the configure script. Fixes bug 21290; bugfix
3838 o Minor bugfixes (consensus weight):
3839 - Add new consensus method that initializes bw weights to 1 instead
3840 of 0. This prevents a zero weight from making it all the way to
3841 the end (happens in small testing networks) and causing an error.
3842 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
3844 o Minor bugfixes (crash prevention):
3845 - Fix an (currently untriggerable, but potentially dangerous) crash
3846 bug when base32-encoding inputs whose sizes are not a multiple of
3847 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3849 o Minor bugfixes (dead code):
3850 - Remove a redundant check for PidFile changes at runtime in
3851 options_transition_allowed(): this check is already performed
3852 regardless of whether the sandbox is active. Fixes bug 21123;
3853 bugfix on 0.2.5.4-alpha.
3855 o Minor bugfixes (descriptors):
3856 - Correctly recognise downloaded full descriptors as valid, even
3857 when using microdescriptors as circuits. This affects clients with
3858 FetchUselessDescriptors set, and may affect directory authorities.
3859 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
3861 o Minor bugfixes (directory mirrors):
3862 - Allow relays to use directory mirrors without a DirPort: these
3863 relays need to be contacted over their ORPorts using a begindir
3864 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3865 - Clarify the message logged when a remote relay is unexpectedly
3866 missing an ORPort or DirPort: users were confusing this with a
3867 local port. Fixes another case of bug 20711; bugfix
3870 o Minor bugfixes (directory system):
3871 - Bridges and relays now use microdescriptors (like clients do)
3872 rather than old-style router descriptors. Now bridges will blend
3873 in with clients in terms of the circuits they build. Fixes bug
3874 6769; bugfix on 0.2.3.2-alpha.
3875 - Download all consensus flavors, descriptors, and authority
3876 certificates when FetchUselessDescriptors is set, regardless of
3877 whether tor is a directory cache or not. Fixes bug 20667; bugfix
3878 on all recent tor versions.
3880 o Minor bugfixes (documentation):
3881 - Update the tor manual page to document every option that can not
3882 be changed while tor is running. Fixes bug 21122.
3884 o Minor bugfixes (ed25519 certificates):
3885 - Correctly interpret ed25519 certificates that would expire some
3886 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
3888 o Minor bugfixes (fallback directories):
3889 - Avoid checking fallback candidates' DirPorts if they are down in
3890 OnionOO. When a relay operator has multiple relays, this
3891 prioritizes relays that are up over relays that are down. Fixes
3892 bug 20926; bugfix on 0.2.8.3-alpha.
3893 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
3894 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
3895 - Stop failing when a relay has no uptime data in
3896 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
3898 o Minor bugfixes (hidden service):
3899 - Clean up the code for expiring intro points with no associated
3900 circuits. It was causing, rarely, a service with some expiring
3901 introduction points to not open enough additional introduction
3902 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
3903 - Resolve two possible underflows which could lead to creating and
3904 closing a lot of introduction point circuits in a non-stop loop.
3905 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
3906 - Stop setting the torrc option HiddenServiceStatistics to "0" just
3907 because we're not a bridge or relay. Instead, we preserve whatever
3908 value the user set (or didn't set). Fixes bug 21150; bugfix
3911 o Minor bugfixes (hidden services):
3912 - Make hidden services check for failed intro point connections,
3913 even when they have exceeded their intro point creation limit.
3914 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
3915 - Make hidden services with 8 to 10 introduction points check for
3916 failed circuits immediately after startup. Previously, they would
3917 wait for 5 minutes before performing their first checks. Fixes bug
3918 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
3919 - Stop ignoring misconfigured hidden services. Instead, refuse to
3920 start tor until the misconfigurations have been corrected. Fixes
3921 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
3924 o Minor bugfixes (IPv6):
3925 - Make IPv6-using clients try harder to find an IPv6 directory
3926 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
3927 - When IPv6 addresses have not been downloaded yet (microdesc
3928 consensus documents don't list relay IPv6 addresses), use hard-
3929 coded addresses for authorities, fallbacks, and configured
3930 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
3931 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
3933 o Minor bugfixes (memory leak at exit):
3934 - Fix a small harmless memory leak at exit of the previously unused
3935 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
3938 o Minor bugfixes (onion services):
3939 - Allow the number of introduction points to be as low as 0, rather
3940 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
3942 o Minor bugfixes (portability):
3943 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
3944 It is supported by OpenBSD itself, and also by most OpenBSD
3945 variants (such as Bitrig). Fixes bug 20980; bugfix
3948 o Minor bugfixes (portability, also in 0.2.9.9):
3949 - Avoid crashing when Tor is built using headers that contain
3950 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3951 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3953 - Fix Libevent detection on platforms without Libevent 1 headers
3954 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3956 o Minor bugfixes (relay):
3957 - Avoid a double-marked-circuit warning that could happen when we
3958 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3960 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
3961 initializing the keys would reset the DataDirectory to 0700
3962 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
3963 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
3965 o Minor bugfixes (testing):
3966 - Fix Raspbian build issues related to missing socket errno in
3967 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
3968 - Remove undefined behavior from the backtrace generator by removing
3969 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
3970 - Use bash in src/test/test-network.sh. This ensures we reliably
3971 call chutney's newer tools/test-network.sh when available. Fixes
3972 bug 21562; bugfix on 0.2.9.1-alpha.
3974 o Minor bugfixes (tor-resolve):
3975 - The tor-resolve command line tool now rejects hostnames over 255
3976 characters in length. Previously, it would silently truncate them,
3977 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3978 Patch by "junglefowl".
3980 o Minor bugfixes (unit tests):
3981 - Allow the unit tests to pass even when DNS lookups of bogus
3982 addresses do not fail as expected. Fixes bug 20862 and 20863;
3983 bugfix on unit tests introduced in 0.2.8.1-alpha
3984 through 0.2.9.4-alpha.
3986 o Minor bugfixes (util):
3987 - When finishing writing a file to disk, if we were about to replace
3988 the file with the temporary file created before and we fail to
3989 replace it, remove the temporary file so it doesn't stay on disk.
3990 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
3992 o Minor bugfixes (Windows services):
3993 - Be sure to initialize the monotonic time subsystem before using
3994 it, even when running as an NT service. Fixes bug 21356; bugfix
3997 o Minor bugfixes (Windows):
3998 - Check for getpagesize before using it to mmap files. This fixes
3999 compilation in some MinGW environments. Fixes bug 20530; bugfix on
4000 0.1.2.1-alpha. Reported by "ice".
4002 o Code simplification and refactoring:
4003 - Abolish all global guard context in entrynodes.c; replace with new
4004 guard_selection_t structure as preparation for proposal 271.
4005 Closes ticket 19858.
4006 - Extract magic numbers in circuituse.c into defined variables.
4007 - Introduce rend_service_is_ephemeral() that tells if given onion
4008 service is ephemeral. Replace unclear NULL-checkings for service
4009 directory with this function. Closes ticket 20526.
4010 - Refactor circuit_is_available_for_use to remove unnecessary check.
4011 - Refactor circuit_predict_and_launch_new for readability and
4012 testability. Closes ticket 18873.
4013 - Refactor code to manipulate global_origin_circuit_list into
4014 separate functions. Closes ticket 20921.
4015 - Refactor large if statement in purpose_needs_anonymity to use
4016 switch statement instead. Closes part of ticket 20077.
4017 - Refactor the hashing API to return negative values for errors, as
4018 is done as throughout the codebase. Closes ticket 20717.
4019 - Remove data structures that were used to index or_connection
4020 objects by their RSA identity digests. These structures are fully
4021 redundant with the similar structures used in the
4022 channel abstraction.
4023 - Remove duplicate code in the channel_write_*cell() functions.
4024 Closes ticket 13827; patch from Pingl.
4025 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
4026 use only purpose_needs_anonymity. Closes part of ticket 20077.
4027 - The code to generate and parse EXTEND and EXTEND2 cells has been
4028 replaced with code automatically generated by the
4031 o Documentation (formatting):
4032 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
4033 blocks were incorrectly appearing. Closes ticket 20885.
4035 o Documentation (man page):
4036 - Clarify many options in tor.1 and add some min/max values for
4037 HiddenService options. Closes ticket 21058.
4040 - Change '1' to 'weight_scale' in consensus bw weights calculation
4041 comments, as that is reality. Closes ticket 20273. Patch
4043 - Clarify that when ClientRejectInternalAddresses is enabled (which
4044 is the default), multicast DNS hostnames for machines on the local
4045 network (of the form *.local) are also rejected. Closes
4047 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
4048 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
4049 - Include the "TBits" unit in Tor's man page. Fixes part of bug
4050 20622; bugfix on 0.2.5.1-alpha.
4051 - Small fixes to the fuzzing documentation. Closes ticket 21472.
4052 - Stop the man page from incorrectly stating that HiddenServiceDir
4053 must already exist. Fixes 20486.
4054 - Update the description of the directory server options in the
4055 manual page, to clarify that a relay no longer needs to set
4056 DirPort in order to be a directory cache. Closes ticket 21720.
4059 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
4060 limit for relays running on a single IP applies to authority IP
4061 addresses as well as to non-authority IP addresses. Closes
4063 - The UseDirectoryGuards torrc option no longer exists: all users
4064 that use entry guards will also use directory guards. Related to
4065 proposal 271; implements part of ticket 20831.
4068 - Add tests for networkstatus_compute_bw_weights_v10.
4069 - Add unit tests circuit_predict_and_launch_new.
4070 - Extract dummy_origin_circuit_new so it can be used by other
4072 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
4073 from "overcaffeinated".
4074 - Perform the coding style checks when running the tests and fail
4075 when coding style violations are found. Closes ticket 5500.
4078 Changes in version 0.2.8.13 - 2017-03-03
4079 Tor 0.2.8.13 backports a security fix from later Tor
4080 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
4081 this release, if for some reason they cannot upgrade to a later
4082 release series, and if they build Tor with the --enable-expensive-hardening
4085 Note that support for Tor 0.2.8.x is ending next year: we will not issue
4086 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
4087 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4089 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4090 - Fix an integer underflow bug when comparing malformed Tor
4091 versions. This bug could crash Tor when built with
4092 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4093 0.2.9.8, which were built with -ftrapv by default. In other cases
4094 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4095 on 0.0.8pre1. Found by OSS-Fuzz.
4097 o Minor features (geoip):
4098 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4102 Changes in version 0.2.7.7 - 2017-03-03
4103 Tor 0.2.7.7 backports a number of security fixes from later Tor
4104 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
4105 this release, if for some reason they cannot upgrade to a later
4108 Note that support for Tor 0.2.7.x is ending this year: we will not issue
4109 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
4110 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4112 o Directory authority changes (backport from 0.2.8.5-rc):
4113 - Urras is no longer a directory authority. Closes ticket 19271.
4115 o Directory authority changes (backport from 0.2.9.2-alpha):
4116 - The "Tonga" bridge authority has been retired; the new bridge
4117 authority is "Bifroest". Closes tickets 19728 and 19690.
4119 o Directory authority key updates (backport from 0.2.8.1-alpha):
4120 - Update the V3 identity key for the dannenberg directory authority:
4121 it was changed on 18 November 2015. Closes task 17906. Patch
4124 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4125 - Fix a bug in parsing that could cause clients to read a single
4126 byte past the end of an allocated region. This bug could be used
4127 to cause hardened clients (built with --enable-expensive-hardening)
4128 to crash if they tried to visit a hostile hidden service. Non-
4129 hardened clients are only affected depending on the details of
4130 their platform's memory allocator. Fixes bug 21018; bugfix on
4131 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4132 2016-12-002 and as CVE-2016-1254.
4134 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4135 - Stop a crash that could occur when a client running with DNSPort
4136 received a query with multiple address types, and the first
4137 address type was not supported. Found and fixed by Scott Dial.
4138 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4139 - Prevent a class of security bugs caused by treating the contents
4140 of a buffer chunk as if they were a NUL-terminated string. At
4141 least one such bug seems to be present in all currently used
4142 versions of Tor, and would allow an attacker to remotely crash
4143 most Tor instances, especially those compiled with extra compiler
4144 hardening. With this defense in place, such bugs can't crash Tor,
4145 though we should still fix them as they occur. Closes ticket
4146 20384 (TROVE-2016-10-001).
4148 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4149 - Avoid a difficult-to-trigger heap corruption attack when extending
4150 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4151 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4152 Reported by Guido Vranken.
4154 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4155 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4156 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4158 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4159 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4160 pointer to the previous (uninitialized) key value. The impact here
4161 should be limited to a difficult-to-trigger crash, if OpenSSL is
4162 running an engine that makes key generation failures possible, or
4163 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4164 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4167 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4168 - Fix an integer underflow bug when comparing malformed Tor
4169 versions. This bug could crash Tor when built with
4170 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4171 0.2.9.8, which were built with -ftrapv by default. In other cases
4172 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4173 on 0.0.8pre1. Found by OSS-Fuzz.
4175 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4176 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4177 zero size. Check size argument to memwipe() for underflow. Fixes
4178 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4181 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4182 - Make Tor survive errors involving connections without a
4183 corresponding event object. Previously we'd fail with an
4184 assertion; now we produce a log message. Related to bug 16248.
4186 o Minor features (geoip):
4187 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4191 Changes in version 0.2.6.11 - 2017-03-03
4192 Tor 0.2.6.11 backports a number of security fixes from later Tor
4193 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
4194 this release, if for some reason they cannot upgrade to a later
4197 Note that support for Tor 0.2.6.x is ending this year: we will not issue
4198 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
4199 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4201 o Directory authority changes (backport from 0.2.8.5-rc):
4202 - Urras is no longer a directory authority. Closes ticket 19271.
4204 o Directory authority changes (backport from 0.2.9.2-alpha):
4205 - The "Tonga" bridge authority has been retired; the new bridge
4206 authority is "Bifroest". Closes tickets 19728 and 19690.
4208 o Directory authority key updates (backport from 0.2.8.1-alpha):
4209 - Update the V3 identity key for the dannenberg directory authority:
4210 it was changed on 18 November 2015. Closes task 17906. Patch
4213 o Major features (security fixes, backport from 0.2.9.4-alpha):
4214 - Prevent a class of security bugs caused by treating the contents
4215 of a buffer chunk as if they were a NUL-terminated string. At
4216 least one such bug seems to be present in all currently used
4217 versions of Tor, and would allow an attacker to remotely crash
4218 most Tor instances, especially those compiled with extra compiler
4219 hardening. With this defense in place, such bugs can't crash Tor,
4220 though we should still fix them as they occur. Closes ticket
4221 20384 (TROVE-2016-10-001).
4223 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4224 - Fix a bug in parsing that could cause clients to read a single
4225 byte past the end of an allocated region. This bug could be used
4226 to cause hardened clients (built with --enable-expensive-hardening)
4227 to crash if they tried to visit a hostile hidden service. Non-
4228 hardened clients are only affected depending on the details of
4229 their platform's memory allocator. Fixes bug 21018; bugfix on
4230 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4231 2016-12-002 and as CVE-2016-1254.
4233 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4234 - Stop a crash that could occur when a client running with DNSPort
4235 received a query with multiple address types, and the first
4236 address type was not supported. Found and fixed by Scott Dial.
4237 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4239 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4240 - Fix an error that could cause us to read 4 bytes before the
4241 beginning of an openssl string. This bug could be used to cause
4242 Tor to crash on systems with unusual malloc implementations, or
4243 systems with unusual hardening installed. Fixes bug 17404; bugfix
4246 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4247 - Avoid a difficult-to-trigger heap corruption attack when extending
4248 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4249 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4250 Reported by Guido Vranken.
4252 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4253 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4254 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4256 o Major bugfixes (guard selection, backport from 0.2.7.6):
4257 - Actually look at the Guard flag when selecting a new directory
4258 guard. When we implemented the directory guard design, we
4259 accidentally started treating all relays as if they have the Guard
4260 flag during guard selection, leading to weaker anonymity and worse
4261 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4264 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4265 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4266 pointer to the previous (uninitialized) key value. The impact here
4267 should be limited to a difficult-to-trigger crash, if OpenSSL is
4268 running an engine that makes key generation failures possible, or
4269 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4270 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4273 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4274 - Fix an integer underflow bug when comparing malformed Tor
4275 versions. This bug could crash Tor when built with
4276 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4277 0.2.9.8, which were built with -ftrapv by default. In other cases
4278 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4279 on 0.0.8pre1. Found by OSS-Fuzz.
4281 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4282 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4283 zero size. Check size argument to memwipe() for underflow. Fixes
4284 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4287 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4288 - Make Tor survive errors involving connections without a
4289 corresponding event object. Previously we'd fail with an
4290 assertion; now we produce a log message. Related to bug 16248.
4292 o Minor features (geoip):
4293 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4296 o Minor bugfixes (compilation, backport from 0.2.7.6):
4297 - Fix a compilation warning with Clang 3.6: Do not check the
4298 presence of an address which can never be NULL. Fixes bug 17781.
4301 Changes in version 0.2.5.13 - 2017-03-03
4302 Tor 0.2.5.13 backports a number of security fixes from later Tor
4303 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
4304 this release, if for some reason they cannot upgrade to a later
4307 Note that support for Tor 0.2.5.x is ending next year: we will not issue
4308 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
4309 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4311 o Directory authority changes (backport from 0.2.8.5-rc):
4312 - Urras is no longer a directory authority. Closes ticket 19271.
4314 o Directory authority changes (backport from 0.2.9.2-alpha):
4315 - The "Tonga" bridge authority has been retired; the new bridge
4316 authority is "Bifroest". Closes tickets 19728 and 19690.
4318 o Directory authority key updates (backport from 0.2.8.1-alpha):
4319 - Update the V3 identity key for the dannenberg directory authority:
4320 it was changed on 18 November 2015. Closes task 17906. Patch
4323 o Major features (security fixes, backport from 0.2.9.4-alpha):
4324 - Prevent a class of security bugs caused by treating the contents
4325 of a buffer chunk as if they were a NUL-terminated string. At
4326 least one such bug seems to be present in all currently used
4327 versions of Tor, and would allow an attacker to remotely crash
4328 most Tor instances, especially those compiled with extra compiler
4329 hardening. With this defense in place, such bugs can't crash Tor,
4330 though we should still fix them as they occur. Closes ticket
4331 20384 (TROVE-2016-10-001).
4333 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4334 - Fix a bug in parsing that could cause clients to read a single
4335 byte past the end of an allocated region. This bug could be used
4336 to cause hardened clients (built with --enable-expensive-hardening)
4337 to crash if they tried to visit a hostile hidden service. Non-
4338 hardened clients are only affected depending on the details of
4339 their platform's memory allocator. Fixes bug 21018; bugfix on
4340 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4341 2016-12-002 and as CVE-2016-1254.
4343 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4344 - Stop a crash that could occur when a client running with DNSPort
4345 received a query with multiple address types, and the first
4346 address type was not supported. Found and fixed by Scott Dial.
4347 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4349 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4350 - Fix an error that could cause us to read 4 bytes before the
4351 beginning of an openssl string. This bug could be used to cause
4352 Tor to crash on systems with unusual malloc implementations, or
4353 systems with unusual hardening installed. Fixes bug 17404; bugfix
4356 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4357 - Avoid a difficult-to-trigger heap corruption attack when extending
4358 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4359 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4360 Reported by Guido Vranken.
4362 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4363 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4364 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4366 o Major bugfixes (guard selection, backport from 0.2.7.6):
4367 - Actually look at the Guard flag when selecting a new directory
4368 guard. When we implemented the directory guard design, we
4369 accidentally started treating all relays as if they have the Guard
4370 flag during guard selection, leading to weaker anonymity and worse
4371 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4374 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4375 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4376 pointer to the previous (uninitialized) key value. The impact here
4377 should be limited to a difficult-to-trigger crash, if OpenSSL is
4378 running an engine that makes key generation failures possible, or
4379 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4380 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4383 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4384 - Fix an integer underflow bug when comparing malformed Tor
4385 versions. This bug could crash Tor when built with
4386 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4387 0.2.9.8, which were built with -ftrapv by default. In other cases
4388 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4389 on 0.0.8pre1. Found by OSS-Fuzz.
4391 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4392 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4393 zero size. Check size argument to memwipe() for underflow. Fixes
4394 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4397 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4398 - Make Tor survive errors involving connections without a
4399 corresponding event object. Previously we'd fail with an
4400 assertion; now we produce a log message. Related to bug 16248.
4402 o Minor features (geoip):
4403 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4406 o Minor bugfixes (compilation, backport from 0.2.7.6):
4407 - Fix a compilation warning with Clang 3.6: Do not check the
4408 presence of an address which can never be NULL. Fixes bug 17781.
4410 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
4411 - Check for failures from crypto_early_init, and refuse to continue.
4412 A previous typo meant that we could keep going with an
4413 uninitialized crypto library, and would have OpenSSL initialize
4414 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4415 when implementing ticket 4900. Patch by "teor".
4417 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4418 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4419 a client authorized hidden service. Fixes bug 15823; bugfix
4423 Changes in version 0.2.4.28 - 2017-03-03
4424 Tor 0.2.4.28 backports a number of security fixes from later Tor
4425 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
4426 this release, if for some reason they cannot upgrade to a later
4429 Note that support for Tor 0.2.4.x is ending soon: we will not issue
4430 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
4431 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
4433 o Directory authority changes (backport from 0.2.8.5-rc):
4434 - Urras is no longer a directory authority. Closes ticket 19271.
4436 o Directory authority changes (backport from 0.2.9.2-alpha):
4437 - The "Tonga" bridge authority has been retired; the new bridge
4438 authority is "Bifroest". Closes tickets 19728 and 19690.
4440 o Directory authority key updates (backport from 0.2.8.1-alpha):
4441 - Update the V3 identity key for the dannenberg directory authority:
4442 it was changed on 18 November 2015. Closes task 17906. Patch
4445 o Major features (security fixes, backport from 0.2.9.4-alpha):
4446 - Prevent a class of security bugs caused by treating the contents
4447 of a buffer chunk as if they were a NUL-terminated string. At
4448 least one such bug seems to be present in all currently used
4449 versions of Tor, and would allow an attacker to remotely crash
4450 most Tor instances, especially those compiled with extra compiler
4451 hardening. With this defense in place, such bugs can't crash Tor,
4452 though we should still fix them as they occur. Closes ticket
4453 20384 (TROVE-2016-10-001).
4455 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4456 - Fix a bug in parsing that could cause clients to read a single
4457 byte past the end of an allocated region. This bug could be used
4458 to cause hardened clients (built with --enable-expensive-hardening)
4459 to crash if they tried to visit a hostile hidden service. Non-
4460 hardened clients are only affected depending on the details of
4461 their platform's memory allocator. Fixes bug 21018; bugfix on
4462 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4463 2016-12-002 and as CVE-2016-1254.
4465 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
4466 - Fix an error that could cause us to read 4 bytes before the
4467 beginning of an openssl string. This bug could be used to cause
4468 Tor to crash on systems with unusual malloc implementations, or
4469 systems with unusual hardening installed. Fixes bug 17404; bugfix
4472 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4473 - Avoid a difficult-to-trigger heap corruption attack when extending
4474 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4475 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4476 Reported by Guido Vranken.
4478 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4479 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4480 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4482 o Major bugfixes (guard selection, backport from 0.2.7.6):
4483 - Actually look at the Guard flag when selecting a new directory
4484 guard. When we implemented the directory guard design, we
4485 accidentally started treating all relays as if they have the Guard
4486 flag during guard selection, leading to weaker anonymity and worse
4487 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4490 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4491 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4492 pointer to the previous (uninitialized) key value. The impact here
4493 should be limited to a difficult-to-trigger crash, if OpenSSL is
4494 running an engine that makes key generation failures possible, or
4495 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4496 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4499 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4500 - Fix an integer underflow bug when comparing malformed Tor
4501 versions. This bug could crash Tor when built with
4502 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4503 0.2.9.8, which were built with -ftrapv by default. In other cases
4504 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4505 on 0.0.8pre1. Found by OSS-Fuzz.
4507 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4508 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4509 zero size. Check size argument to memwipe() for underflow. Fixes
4510 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4513 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4514 - Make Tor survive errors involving connections without a
4515 corresponding event object. Previously we'd fail with an
4516 assertion; now we produce a log message. Related to bug 16248.
4518 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
4519 - Make it harder for attackers to overload hidden services with
4520 introductions, by blocking multiple introduction requests on the
4521 same circuit. Resolves ticket 15515.
4523 o Minor features (geoip):
4524 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4527 o Minor bugfixes (compilation, backport from 0.2.7.6):
4528 - Fix a compilation warning with Clang 3.6: Do not check the
4529 presence of an address which can never be NULL. Fixes bug 17781.
4531 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4532 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4533 a client authorized hidden service. Fixes bug 15823; bugfix
4537 Changes in version 0.2.9.10 - 2017-03-01
4538 Tor 0.2.9.10 backports a security fix from later Tor release. It also
4539 includes fixes for some major issues affecting directory authorities,
4540 LibreSSL compatibility, and IPv6 correctness.
4542 The Tor 0.2.9.x release series is now marked as a long-term-support
4543 series. We intend to backport security fixes to 0.2.9.x until at
4544 least January of 2020.
4546 o Major bugfixes (directory authority, 0.3.0.3-alpha):
4547 - During voting, when marking a relay as a probable sybil, do not
4548 clear its BadExit flag: sybils can still be bad in other ways
4549 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4552 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
4553 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4554 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4555 exit policy rejects that port on more than an IPv6 /16 of
4556 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4557 which rejected a relay's own IPv6 address by default. Fixes bug
4558 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4560 o Major bugfixes (parsing, also in 0.3.0.4-rc):
4561 - Fix an integer underflow bug when comparing malformed Tor
4562 versions. This bug could crash Tor when built with
4563 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4564 0.2.9.8, which were built with -ftrapv by default. In other cases
4565 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4566 on 0.0.8pre1. Found by OSS-Fuzz.
4568 o Minor features (directory authorities, also in 0.3.0.4-rc):
4569 - Directory authorities now reject descriptors that claim to be
4570 malformed versions of Tor. Helps prevent exploitation of
4572 - Reject version numbers with components that exceed INT32_MAX.
4573 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
4574 Fixes bug 21450; bugfix on 0.0.8pre1.
4576 o Minor features (geoip):
4577 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4580 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
4581 - Autoconf now checks to determine if OpenSSL structures are opaque,
4582 instead of explicitly checking for OpenSSL version numbers. Part
4584 - Support building with recent LibreSSL code that uses opaque
4585 structures. Closes ticket 21359.
4587 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
4588 - Repair a couple of (unreachable or harmless) cases of the risky
4589 comparison-by-subtraction pattern that caused bug 21278.
4591 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
4592 - The tor-resolve command line tool now rejects hostnames over 255
4593 characters in length. Previously, it would silently truncate them,
4594 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4595 Patch by "junglefowl".
4598 Changes in version 0.2.9.9 - 2017-01-23
4599 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
4600 cause relays and clients to crash, even if they were not built with
4601 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
4602 versions, and also affects 0.3.0.1-alpha: all relays running an affected
4603 version should upgrade.
4605 This release also resolves a client-side onion service reachability
4606 bug, and resolves a pair of small portability issues.
4608 o Major bugfixes (security):
4609 - Downgrade the "-ftrapv" option from "always on" to "only on when
4610 --enable-expensive-hardening is provided." This hardening option,
4611 like others, can turn survivable bugs into crashes -- and having
4612 it on by default made a (relatively harmless) integer overflow bug
4613 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4614 bugfix on 0.2.9.1-alpha.
4616 o Major bugfixes (client, onion service):
4617 - Fix a client-side onion service reachability bug, where multiple
4618 socks requests to an onion service (or a single slow request)
4619 could cause us to mistakenly mark some of the service's
4620 introduction points as failed, and we cache that failure so
4621 eventually we run out and can't reach the service. Also resolves a
4622 mysterious "Remote server sent bogus reason code 65021" log
4623 warning. The bug was introduced in ticket 17218, where we tried to
4624 remember the circuit end reason as a uint16_t, which mangled
4625 negative values. Partially fixes bug 21056 and fixes bug 20307;
4626 bugfix on 0.2.8.1-alpha.
4628 o Minor features (geoip):
4629 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4632 o Minor bugfixes (portability):
4633 - Avoid crashing when Tor is built using headers that contain
4634 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4635 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4637 - Fix Libevent detection on platforms without Libevent 1 headers
4638 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4641 Changes in version 0.2.8.12 - 2016-12-19
4642 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
4643 below) where Tor clients could crash when attempting to visit a
4644 hostile hidden service. Clients are recommended to upgrade as packages
4645 become available for their systems.
4647 It also includes an updated list of fallback directories, backported
4650 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
4651 backported to 0.2.8 in the future.
4653 o Major bugfixes (parsing, security, backported from 0.2.9.8):
4654 - Fix a bug in parsing that could cause clients to read a single
4655 byte past the end of an allocated region. This bug could be used
4656 to cause hardened clients (built with --enable-expensive-hardening)
4657 to crash if they tried to visit a hostile hidden service. Non-
4658 hardened clients are only affected depending on the details of
4659 their platform's memory allocator. Fixes bug 21018; bugfix on
4660 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4661 2016-12-002 and as CVE-2016-1254.
4663 o Minor features (fallback directory list, backported from 0.2.9.8):
4664 - Replace the 81 remaining fallbacks of the 100 originally
4665 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4666 fallbacks (123 new, 54 existing, 27 removed) generated in December
4667 2016. Resolves ticket 20170.
4669 o Minor features (geoip, backported from 0.2.9.7-rc):
4670 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
4674 Changes in version 0.2.9.8 - 2016-12-19
4675 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
4677 The Tor 0.2.9 series makes mandatory a number of security features
4678 that were formerly optional. It includes support for a new shared-
4679 randomness protocol that will form the basis for next generation
4680 hidden services, includes a single-hop hidden service mode for
4681 optimizing .onion services that don't actually want to be hidden,
4682 tries harder not to overload the directory authorities with excessive
4683 downloads, and supports a better protocol versioning scheme for
4684 improved compatibility with other implementations of the Tor protocol.
4686 And of course, there are numerous other bugfixes and improvements.
4688 This release also includes a fix for a medium-severity issue (bug
4689 21018 below) where Tor clients could crash when attempting to visit a
4690 hostile hidden service. Clients are recommended to upgrade as packages
4691 become available for their systems.
4693 Below are listed the changes since Tor 0.2.8.11. For a list of
4694 changes since 0.2.9.7-rc, see the ChangeLog file.
4696 o New system requirements:
4697 - When building with OpenSSL, Tor now requires version 1.0.1 or
4698 later. OpenSSL 1.0.0 and earlier are no longer supported by the
4699 OpenSSL team, and should not be used. Closes ticket 20303.
4700 - Tor now requires Libevent version 2.0.10-stable or later. Older
4701 versions of Libevent have less efficient backends for several
4702 platforms, and lack the DNS code that we use for our server-side
4703 DNS support. This implements ticket 19554.
4704 - Tor now requires zlib version 1.2 or later, for security,
4705 efficiency, and (eventually) gzip support. (Back when we started,
4706 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
4707 released in 2003. We recommend the latest version.)
4709 o Deprecated features:
4710 - A number of DNS-cache-related sub-options for client ports are now
4711 deprecated for security reasons, and may be removed in a future
4712 version of Tor. (We believe that client-side DNS caching is a bad
4713 idea for anonymity, and you should not turn it on.) The options
4714 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
4715 UseIPv4Cache, and UseIPv6Cache.
4716 - A number of options are deprecated for security reasons, and may
4717 be removed in a future version of Tor. The options are:
4718 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
4719 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
4720 CloseHSClientCircuitsImmediatelyOnTimeout,
4721 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
4722 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
4723 UseNTorHandshake, and WarnUnsafeSocks.
4724 - The *ListenAddress options are now deprecated as unnecessary: the
4725 corresponding *Port options should be used instead. These options
4726 may someday be removed. The affected options are:
4727 ControlListenAddress, DNSListenAddress, DirListenAddress,
4728 NATDListenAddress, ORListenAddress, SocksListenAddress,
4729 and TransListenAddress.
4731 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
4732 - Fix a bug in parsing that could cause clients to read a single
4733 byte past the end of an allocated region. This bug could be used
4734 to cause hardened clients (built with --enable-expensive-hardening)
4735 to crash if they tried to visit a hostile hidden service. Non-
4736 hardened clients are only affected depending on the details of
4737 their platform's memory allocator. Fixes bug 21018; bugfix on
4738 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4739 2016-12-002 and as CVE-2016-1254.
4741 o Major features (build, hardening):
4742 - Tor now builds with -ftrapv by default on compilers that support
4743 it. This option detects signed integer overflow (which C forbids),
4744 and turns it into a hard-failure. We do not apply this option to
4745 code that needs to run in constant time to avoid side-channels;
4746 instead, we use -fwrapv in that code. Closes ticket 17983.
4747 - When --enable-expensive-hardening is selected, stop applying the
4748 clang/gcc sanitizers to code that needs to run in constant time.
4749 Although we are aware of no introduced side-channels, we are not
4750 able to prove that there are none. Related to ticket 17983.
4752 o Major features (circuit building, security):
4753 - Authorities, relays, and clients now require ntor keys in all
4754 descriptors, for all hops (except for rare hidden service protocol
4755 cases), for all circuits, and for all other roles. Part of
4757 - Authorities, relays, and clients only use ntor, except for
4758 rare cases in the hidden service protocol. Part of ticket 19163.
4760 o Major features (compilation):
4761 - Our big list of extra GCC warnings is now enabled by default when
4762 building with GCC (or with anything like Clang that claims to be
4763 GCC-compatible). To make all warnings into fatal compilation
4764 errors, pass --enable-fatal-warnings to configure. Closes
4766 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
4767 turn on C and POSIX extensions. (Previously, we attempted to do
4768 this on an ad hoc basis.) Closes ticket 19139.
4770 o Major features (directory authorities, hidden services):
4771 - Directory authorities can now perform the shared randomness
4772 protocol specified by proposal 250. Using this protocol, directory
4773 authorities generate a global fresh random value every day. In the
4774 future, this value will be used by hidden services to select
4775 HSDirs. This release implements the directory authority feature;
4776 the hidden service side will be implemented in the future as part
4777 of proposal 224. Resolves ticket 16943; implements proposal 250.
4779 o Major features (downloading, random exponential backoff):
4780 - When we fail to download an object from a directory service, wait
4781 for an (exponentially increasing) randomized amount of time before
4782 retrying, rather than a fixed interval as we did before. This
4783 prevents a group of Tor instances from becoming too synchronized,
4784 or a single Tor instance from becoming too predictable, in its
4785 download schedule. Closes ticket 15942.
4787 o Major features (resource management):
4788 - Tor can now notice it is about to run out of sockets, and
4789 preemptively close connections of lower priority. (This feature is
4790 off by default for now, since the current prioritizing method is
4791 yet not mature enough. You can enable it by setting
4792 "DisableOOSCheck 0", but watch out: it might close some sockets
4793 you would rather have it keep.) Closes ticket 18640.
4795 o Major features (single-hop "hidden" services):
4796 - Add experimental HiddenServiceSingleHopMode and
4797 HiddenServiceNonAnonymousMode options. When both are set to 1,
4798 every hidden service on that Tor instance becomes a non-anonymous
4799 Single Onion Service. Single Onions make one-hop (direct)
4800 connections to their introduction and rendezvous points. One-hop
4801 circuits make Single Onion servers easily locatable, but clients
4802 remain location-anonymous. This is compatible with the existing
4803 hidden service implementation, and works on the current Tor
4804 network without any changes to older relays or clients. Implements
4805 proposal 260, completes ticket 17178. Patch by teor and asn.
4807 o Major features (subprotocol versions):
4808 - Tor directory authorities now vote on a set of recommended
4809 "subprotocol versions", and on a set of required subprotocol
4810 versions. Clients and relays that lack support for a _required_
4811 subprotocol version will not start; those that lack support for a
4812 _recommended_ subprotocol version will warn the user to upgrade.
4813 This change allows compatible implementations of the Tor protocol(s)
4814 to exist without pretending to be 100% bug-compatible with
4815 particular releases of Tor itself. Closes ticket 19958; implements
4816 part of proposal 264.
4818 o Major bugfixes (circuit building):
4819 - Hidden service client-to-intro-point and service-to-rendezvous-
4820 point circuits use the TAP key supplied by the protocol, to avoid
4821 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
4823 o Major bugfixes (download scheduling):
4824 - Avoid resetting download status for consensuses hourly, since we
4825 already have another, smarter retry mechanism. Fixes bug 8625;
4826 bugfix on 0.2.0.9-alpha.
4827 - If a consensus expires while we are waiting for certificates to
4828 download, stop waiting for certificates.
4829 - If we stop waiting for certificates less than a minute after we
4830 started downloading them, do not consider the certificate download
4831 failure a separate failure. Fixes bug 20533; bugfix
4833 - When using exponential backoff in test networks, use a lower
4834 exponent, so the delays do not vary as much. This helps test
4835 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4837 o Major bugfixes (exit policies):
4838 - Avoid disclosing exit outbound bind addresses, configured port
4839 bind addresses, and local interface addresses in relay descriptors
4840 by default under ExitPolicyRejectPrivate. Instead, only reject
4841 these (otherwise unlisted) addresses if
4842 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
4843 0.2.7.2-alpha. Patch by teor.
4845 o Major bugfixes (hidden services):
4846 - Allow Tor clients with appropriate controllers to work with
4847 FetchHidServDescriptors set to 0. Previously, this option also
4848 disabled descriptor cache lookup, thus breaking hidden services
4849 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
4850 - Clients now require hidden services to include the TAP keys for
4851 their intro points in the hidden service descriptor. This prevents
4852 an inadvertent upgrade to ntor, which a malicious hidden service
4853 could use to distinguish clients by consensus version. Fixes bug
4854 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
4856 o Major bugfixes (relay, resolver, logging):
4857 - For relays that don't know their own address, avoid attempting a
4858 local hostname resolve for each descriptor we download. This
4859 will cut down on the number of "Success: chose address 'x.x.x.x'"
4860 log lines, and also avoid confusing clock jumps if the resolver
4861 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4863 o Minor features (port flags):
4864 - Add new flags to the *Port options to give finer control over which
4865 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
4866 and the synthetic flag OnionTrafficOnly, which is equivalent to
4867 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
4868 18693; patch by "teor".
4870 o Minor features (build, hardening):
4871 - Detect and work around a libclang_rt problem that would prevent
4872 clang from finding __mulodi4() on some 32-bit platforms, and thus
4873 keep -ftrapv from linking on those systems. Closes ticket 19079.
4874 - When building on a system without runtime support for the runtime
4875 hardening options, try to log a useful warning at configuration
4876 time, rather than an incomprehensible warning at link time. If
4877 expensive hardening was requested, this warning becomes an error.
4878 Closes ticket 18895.
4880 o Minor features (client, directory):
4881 - Since authorities now omit all routers that lack the Running and
4882 Valid flags, we assume that any relay listed in the consensus must
4883 have those flags. Closes ticket 20001; implements part of
4886 o Minor features (code safety):
4887 - In our integer-parsing functions, ensure that the maximum value we
4888 allow is no smaller than the minimum value. Closes ticket 19063;
4889 patch from "U+039b".
4891 o Minor features (compilation, portability):
4892 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4895 o Minor features (config):
4896 - Warn users when descriptor and port addresses are inconsistent.
4897 Mitigates bug 13953; patch by teor.
4899 o Minor features (controller):
4900 - Allow controllers to configure basic client authorization on
4901 hidden services when they create them with the ADD_ONION controller
4902 command. Implements ticket 15588. Patch by "special".
4903 - Fire a STATUS_SERVER controller event whenever the hibernation
4904 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
4905 - Implement new GETINFO queries for all downloads that use
4906 download_status_t to schedule retries. This allows controllers to
4907 examine the schedule for pending downloads. Closes ticket 19323.
4909 o Minor features (development tools, etags):
4910 - Teach the "make tags" Makefile target how to correctly find
4911 "MOCK_IMPL" function definitions. Patch from nherring; closes
4914 o Minor features (directory authority):
4915 - After voting, if the authorities decide that a relay is not
4916 "Valid", they no longer include it in the consensus at all. Closes
4917 ticket 20002; implements part of proposal 272.
4918 - Directory authorities now only give the Guard flag to a relay if
4919 they are also giving it the Stable flag. This change allows us to
4920 simplify path selection for clients. It should have minimal effect
4921 in practice, since >99% of Guards already have the Stable flag.
4922 Implements ticket 18624.
4923 - Directory authorities now write their v3-status-votes file out to
4924 disk earlier in the consensus process, so we have a record of the
4925 votes even if we abort the consensus process. Resolves
4928 o Minor features (fallback directory list, new since 0.2.9.7-rc):
4929 - Replace the 81 remaining fallbacks of the 100 originally
4930 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4931 fallbacks (123 new, 54 existing, 27 removed) generated in December
4932 2016. Resolves ticket 20170.
4934 o Minor features (hidden service):
4935 - Stop being so strict about the payload length of "rendezvous1"
4936 cells. We used to be locked in to the "TAP" handshake length, and
4937 now we can handle better handshakes like "ntor". Resolves
4940 o Minor features (infrastructure, time):
4941 - Tor now includes an improved timer backend, so that we can
4942 efficiently support tens or hundreds of thousands of concurrent
4943 timers, as will be needed for some of our planned anti-traffic-
4944 analysis work. This code is based on William Ahern's "timeout.c"
4945 project, which implements a "tickless hierarchical timing wheel".
4946 Closes ticket 18365.
4947 - Tor now uses the operating system's monotonic timers (where
4948 available) for internal fine-grained timing. Previously we would
4949 look at the system clock, and then attempt to compensate for the
4950 clock running backwards. Closes ticket 18908.
4952 o Minor features (logging):
4953 - Add a set of macros to check nonfatal assertions, for internal
4954 use. Migrating more of our checks to these should help us avoid
4955 needless crash bugs. Closes ticket 18613.
4956 - Provide a more useful warning message when configured with an
4957 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
4958 - When dumping unparseable router descriptors, optionally store them
4959 in separate files, named by digest, up to a configurable size
4960 limit. You can change the size limit by setting the
4961 MaxUnparseableDescSizeToLog option, and disable this feature by
4962 setting that option to 0. Closes ticket 18322.
4964 o Minor features (performance):
4965 - Change the "optimistic data" extension from "off by default" to
4966 "on by default". The default was ordinarily overridden by a
4967 consensus option, but when clients were bootstrapping for the
4968 first time, they would not have a consensus to get the option
4969 from. Changing this default saves a round-trip during startup.
4970 Closes ticket 18815.
4972 o Minor features (relay, usability):
4973 - When the directory authorities refuse a bad relay's descriptor,
4974 encourage the relay operator to contact us. Many relay operators
4975 won't notice this line in their logs, but it's a win if even a few
4976 learn why we don't like what their relay was doing. Resolves
4979 o Minor features (security, TLS):
4980 - Servers no longer support clients that lack AES ciphersuites.
4981 (3DES is no longer considered an acceptable cipher.) We believe
4982 that no such Tor clients currently exist, since Tor has required
4983 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
4985 o Minor features (testing):
4986 - Disable memory protections on OpenBSD when performing our unit
4987 tests for memwipe(). The test deliberately invokes undefined
4988 behavior, and the OpenBSD protections interfere with this. Patch
4989 from "rubiate". Closes ticket 20066.
4990 - Move the test-network.sh script to chutney, and modify tor's test-
4991 network.sh to call the (newer) chutney version when available.
4992 Resolves ticket 19116. Patch by teor.
4993 - Use the lcov convention for marking lines as unreachable, so that
4994 we don't count them when we're generating test coverage data.
4995 Update our coverage tools to understand this convention. Closes
4997 - Our link-handshake unit tests now check that when invalid
4998 handshakes fail, they fail with the error messages we expected.
4999 - Our unit testing code that captures log messages no longer
5000 prevents them from being written out if the user asked for them
5001 (by passing --debug or --info or --notice or --warn to the "test"
5002 binary). This change prevents us from missing unexpected log
5003 messages simply because we were looking for others. Related to
5005 - The unit tests now log all warning messages with the "BUG" flag.
5006 Previously, they only logged errors by default. This change will
5007 help us make our testing code more correct, and make sure that we
5008 only hit this code when we mean to. In the meantime, however,
5009 there will be more warnings in the unit test logs than before.
5010 This is preparatory work for ticket 19999.
5011 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5012 assertion as a test failure.
5013 - We've done significant work to make the unit tests run faster.
5015 o Minor features (testing, ipv6):
5016 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5017 tests. Remove bridges+hs, as it's somewhat redundant. This
5018 requires a recent chutney version that supports IPv6 clients,
5019 relays, and authorities. Closes ticket 20069; patch by teor.
5020 - Add the single-onion and single-onion-ipv6 chutney targets to
5021 "make test-network-all". This requires a recent chutney version
5022 with the single onion network flavors (git c72a652 or later).
5023 Closes ticket 20072; patch by teor.
5025 o Minor features (Tor2web):
5026 - Make Tor2web clients respect ReachableAddresses. This feature was
5027 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5028 0.2.8.7. Implements feature 20034. Patch by teor.
5030 o Minor features (unix domain sockets):
5031 - When configuring a unix domain socket for a SocksPort,
5032 ControlPort, or Hidden service, you can now wrap the address in
5033 quotes, using C-style escapes inside the quotes. This allows unix
5034 domain socket paths to contain spaces. Resolves ticket 18753.
5036 o Minor features (user interface):
5037 - Tor now supports the ability to declare options deprecated, so
5038 that we can recommend that people stop using them. Previously, this
5039 was done in an ad-hoc way. There is a new --list-deprecated-options
5040 command-line option to list all of the deprecated options. Closes
5043 o Minor features (virtual addresses):
5044 - Increase the maximum number of bits for the IPv6 virtual network
5045 prefix from 16 to 104. In this way, the condition for address
5046 allocation is less restrictive. Closes ticket 20151; feature
5049 o Minor bug fixes (circuits):
5050 - Use the CircuitBuildTimeout option whenever
5051 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5052 the option when a user disabled it, but not when it was disabled
5053 because some other option was set. Fixes bug 20073; bugfix on
5054 0.2.4.12-alpha. Patch by teor.
5056 o Minor bugfixes (build):
5057 - The current Git revision when building from a local repository is
5058 now detected correctly when using git worktrees. Fixes bug 20492;
5059 bugfix on 0.2.3.9-alpha.
5061 o Minor bugfixes (relay address discovery):
5062 - Stop reordering IP addresses returned by the OS. This makes it
5063 more likely that Tor will guess the same relay IP address every
5064 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
5065 Reported by René Mayrhofer, patch by "cypherpunks".
5067 o Minor bugfixes (memory allocation):
5068 - Change how we allocate memory for large chunks on buffers, to
5069 avoid a (currently impossible) integer overflow, and to waste less
5070 space when allocating unusually large chunks. Fixes bug 20081;
5071 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5073 o Minor bugfixes (bootstrap):
5074 - Remember the directory server we fetched the consensus or previous
5075 certificates from, and use it to fetch future authority
5076 certificates. This change improves bootstrapping performance.
5077 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
5079 o Minor bugfixes (circuits):
5080 - Make sure extend_info_from_router() is only called on servers.
5081 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5083 o Minor bugfixes (client, fascistfirewall):
5084 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
5085 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
5087 o Minor bugfixes (client, unix domain sockets):
5088 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
5089 the client address is meaningless. Fixes bug 20261; bugfix
5092 o Minor bugfixes (code style):
5093 - Fix an integer signedness conversion issue in the case conversion
5094 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
5096 o Minor bugfixes (compilation):
5097 - Build correctly on versions of libevent2 without support for
5098 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
5100 - When building with Clang, use a full set of GCC warnings.
5101 (Previously, we included only a subset, because of the way we
5102 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5103 - Detect Libevent2 functions correctly on systems that provide
5104 libevent2, but where libevent1 is linked with -levent. Fixes bug
5105 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
5106 - Run correctly when built on Windows build environments that
5107 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
5109 o Minor bugfixes (configuration):
5110 - When parsing quoted configuration values from the torrc file,
5111 handle Windows line endings correctly. Fixes bug 19167; bugfix on
5112 0.2.0.16-alpha. Patch from "Pingl".
5114 o Minor bugfixes (directory authority):
5115 - Authorities now sort the "package" lines in their votes, for ease
5116 of debugging. (They are already sorted in consensus documents.)
5117 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5118 - Die with a more useful error when the operator forgets to place
5119 the authority_signing_key file into the keys directory. This
5120 avoids an uninformative assert & traceback about having an invalid
5121 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5122 - When allowing private addresses, mark Exits that only exit to
5123 private locations as such. Fixes bug 20064; bugfix
5125 - When parsing a detached signature, make sure we use the length of
5126 the digest algorithm instead of a hardcoded DIGEST256_LEN in
5127 order to avoid comparing bytes out-of-bounds with a smaller digest
5128 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5130 o Minor bugfixes (getpass):
5131 - Defensively fix a non-triggerable heap corruption at do_getpass()
5132 to protect ourselves from mistakes in the future. Fixes bug
5133 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
5136 o Minor bugfixes (guard selection):
5137 - Don't mark guards as unreachable if connection_connect() fails.
5138 That function fails for local reasons, so it shouldn't reveal
5139 anything about the status of the guard. Fixes bug 14334; bugfix
5141 - Use a single entry guard even if the NumEntryGuards consensus
5142 parameter is not provided. Fixes bug 17688; bugfix
5145 o Minor bugfixes (hidden services):
5146 - Increase the minimum number of internal circuits we preemptively
5147 build from 2 to 3, so a circuit is available when a client
5148 connects to another onion service. Fixes bug 13239; bugfix
5150 - Allow hidden services to run on IPv6 addresses even when the
5151 IPv6Exit option is not set. Fixes bug 18357; bugfix
5153 - Stop logging intro point details to the client log on certain
5154 error conditions. Fixed as part of bug 20012; bugfix on
5155 0.2.4.8-alpha. Patch by teor.
5156 - When deleting an ephemeral hidden service, close its intro points
5157 even if they are not completely open. Fixes bug 18604; bugfix
5159 - When configuring hidden services, check every hidden service
5160 directory's permissions. Previously, we only checked the last
5161 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
5163 o Minor bugfixes (IPv6, testing):
5164 - Check for IPv6 correctly on Linux when running test networks.
5165 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5167 o Minor bugfixes (Linux seccomp2 sandbox):
5168 - Add permission to run the sched_yield() and sigaltstack() system
5169 calls, in order to support versions of Tor compiled with asan or
5170 ubsan code that use these calls. Now "sandbox 1" and
5171 "--enable-expensive-hardening" should be compatible on more
5172 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5174 o Minor bugfixes (logging):
5175 - Downgrade a harmless log message about the
5176 pending_entry_connections list from "warn" to "info". Mitigates
5178 - Log a more accurate message when we fail to dump a microdescriptor.
5179 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
5180 - When logging a directory ownership mismatch, log the owning
5181 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5182 - When we are unable to remove the bw_accounting file, do not warn
5183 if the reason we couldn't remove it was that it didn't exist.
5184 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
5186 o Minor bugfixes (memory leak):
5187 - Fix a series of slow memory leaks related to parsing torrc files
5188 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
5189 - Avoid a small memory leak when informing worker threads about
5190 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
5191 - Fix a small memory leak when receiving AF_UNIX connections on a
5192 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
5193 - When moving a signed descriptor object from a source to an
5194 existing destination, free the allocated memory inside that
5195 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
5196 - Fix a memory leak and use-after-free error when removing entries
5197 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
5198 0.2.5.5-alpha. Patch from "cypherpunks".
5199 - Fix a small, uncommon memory leak that could occur when reading a
5200 truncated ed25519 key file. Fixes bug 18956; bugfix
5203 o Minor bugfixes (option parsing):
5204 - Count unix sockets when counting client listeners (SOCKS, Trans,
5205 NATD, and DNS). This has no user-visible behavior changes: these
5206 options are set once, and never read. Required for correct
5207 behavior in ticket 17178. Fixes bug 19677; bugfix on
5208 0.2.6.3-alpha. Patch by teor.
5210 o Minor bugfixes (options):
5211 - Check the consistency of UseEntryGuards and EntryNodes more
5212 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
5214 - Stop changing the configured value of UseEntryGuards on
5215 authorities and Tor2web clients. Fixes bug 20074; bugfix on
5216 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
5219 o Minor bugfixes (relay):
5220 - Ensure relays don't make multiple connections during bootstrap.
5221 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
5222 - Do not try to parallelize workers more than 16x without the user
5223 explicitly configuring us to do so, even if we do detect more than
5224 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5226 o Minor bugfixes (testing):
5227 - The test-stem and test-network makefile targets now depend only on
5228 the tor binary that they are testing. Previously, they depended on
5229 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
5230 patch from "cypherpunks".
5231 - Allow clients to retry HSDirs much faster in test networks. Fixes
5232 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
5233 - Avoid a unit test failure on systems with over 16 detectable CPU
5234 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
5235 - Let backtrace tests work correctly under AddressSanitizer:
5236 disable ASAN's detection of segmentation faults while running
5237 test_bt.sh, so that we can make sure that our own backtrace
5238 generation code works. Fixes bug 18934; bugfix
5239 on 0.2.5.2-alpha. Patch from "cypherpunks".
5240 - Fix the test-network-all target on out-of-tree builds by using the
5241 correct path to the test driver script. Fixes bug 19421; bugfix
5243 - Stop spurious failures in the local interface address discovery
5244 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
5246 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
5247 removed the ECDH ciphers which caused the tests to fail on
5248 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
5249 - The tor_tls_server_info_callback unit test no longer crashes when
5250 debug-level logging is turned on. Fixes bug 20041; bugfix
5253 o Minor bugfixes (time):
5254 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
5255 bugfix on all released tor versions.
5256 - When computing the difference between two times in milliseconds,
5257 we now round to the nearest millisecond correctly. Previously, we
5258 could sometimes round in the wrong direction. Fixes bug 19428;
5259 bugfix on 0.2.2.2-alpha.
5261 o Minor bugfixes (Tor2web):
5262 - Prevent Tor2web clients from running hidden services: these services
5263 are not anonymous due to the one-hop client paths. Fixes bug
5264 19678. Patch by teor.
5266 o Minor bugfixes (user interface):
5267 - Display a more accurate number of suppressed messages in the log
5268 rate-limiter. Previously, there was a potential integer overflow
5269 in the counter. Now, if the number of messages hits a maximum, the
5270 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
5272 - Fix a typo in the passphrase prompt for the ed25519 identity key.
5273 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
5275 o Code simplification and refactoring:
5276 - Remove redundant declarations of the MIN macro. Closes
5278 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
5279 Closes ticket 18462; patch from "icanhasaccount".
5280 - Split the 600-line directory_handle_command_get function into
5281 separate functions for different URL types. Closes ticket 16698.
5284 - Add module-level internal documentation for 36 C files that
5285 previously didn't have a high-level overview. Closes ticket 20385.
5286 - Correct the IPv6 syntax in our documentation for the
5287 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
5288 - Correct the minimum bandwidth value in torrc.sample, and queue a
5289 corresponding change for torrc.minimal. Closes ticket 20085.
5290 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
5291 ticket 19153. Patch from "U+039b".
5292 - Module-level documentation for several more modules. Closes
5293 tickets 19287 and 19290.
5294 - Document the --passphrase-fd option in the tor manpage. Fixes bug
5295 19504; bugfix on 0.2.7.3-rc.
5296 - Document the default PathsNeededToBuildCircuits value that's used
5297 by clients when the directory authorities don't set
5298 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
5299 Patch by teor, reported by Jesse V.
5300 - Fix manual for the User option: it takes a username, not a UID.
5301 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
5303 - Fix the description of the --passphrase-fd option in the
5304 tor-gencert manpage. The option is used to pass the number of a
5305 file descriptor to read the passphrase from, not to read the file
5306 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
5309 - We no longer include the (dead, deprecated) bufferevent code in
5310 Tor. Closes ticket 19450. Based on a patch from "U+039b".
5313 - Remove support for "GET /tor/bytes.txt" DirPort request, and
5314 "GETINFO dir-usage" controller request, which were only available
5315 via a compile-time option in Tor anyway. Feature was added in
5316 0.2.2.1-alpha. Resolves ticket 19035.
5317 - There is no longer a compile-time option to disable support for
5318 TransPort. (If you don't want TransPort, just don't use it.) Patch
5319 from "U+039b". Closes ticket 19449.
5322 - Run more workqueue tests as part of "make check". These had
5323 previously been implemented, but you needed to know special
5324 command-line options to enable them.
5325 - We now have unit tests for our code to reject zlib "compression
5326 bombs". (Fortunately, the code works fine.)
5329 Changes in version 0.2.8.11 - 2016-12-08
5330 Tor 0.2.8.11 backports fixes for additional portability issues that
5331 could prevent Tor from building correctly on OSX Sierra, or with
5332 OpenSSL 1.1. Affected users should upgrade; others can safely stay
5335 o Minor bugfixes (portability):
5336 - Avoid compilation errors when building on OSX Sierra. Sierra began
5337 to support the getentropy() and clock_gettime() APIs, but created
5338 a few problems in doing so. Tor 0.2.9 has a more thorough set of
5339 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
5340 monotonic time interfaces. Fixes bug 20865. Bugfix
5343 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5344 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
5345 architectures. Closes ticket 20588.
5348 Changes in version 0.2.8.10 - 2016-12-02
5349 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
5350 unusable after they left standby mode. It also backports fixes for
5351 a few portability issues and a small but problematic memory leak.
5353 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
5354 - When Tor leaves standby because of a new application request, open
5355 circuits as needed to serve that request. Previously, we would
5356 potentially wait a very long time. Fixes part of bug 19969; bugfix
5359 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
5360 - Clients now respond to new application stream requests immediately
5361 when they arrive, rather than waiting up to one second before
5362 starting to handle them. Fixes part of bug 19969; bugfix
5365 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
5366 - Work around a bug in the OSX 10.12 SDK that would prevent us from
5367 successfully targeting earlier versions of OSX. Resolves
5370 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
5371 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
5372 20551; bugfix on 0.2.1.1-alpha.
5374 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
5375 - Work around a memory leak in OpenSSL 1.1 when encoding public
5376 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
5378 o Minor features (geoip):
5379 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
5383 Changes in version 0.2.8.9 - 2016-10-17
5384 Tor 0.2.8.9 backports a fix for a security hole in previous versions
5385 of Tor that would allow a remote attacker to crash a Tor client,
5386 hidden service, relay, or authority. All Tor users should upgrade to
5387 this version, or to 0.2.9.4-alpha. Patches will be released for older
5390 o Major features (security fixes, also in 0.2.9.4-alpha):
5391 - Prevent a class of security bugs caused by treating the contents
5392 of a buffer chunk as if they were a NUL-terminated string. At
5393 least one such bug seems to be present in all currently used
5394 versions of Tor, and would allow an attacker to remotely crash
5395 most Tor instances, especially those compiled with extra compiler
5396 hardening. With this defense in place, such bugs can't crash Tor,
5397 though we should still fix them as they occur. Closes ticket
5398 20384 (TROVE-2016-10-001).
5400 o Minor features (geoip):
5401 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
5405 Changes in version 0.2.8.8 - 2016-09-23
5406 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
5407 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
5408 who select public relays as their bridges.
5410 o Major bugfixes (crash):
5411 - Fix a complicated crash bug that could affect Tor clients
5412 configured to use bridges when replacing a networkstatus consensus
5413 in which one of their bridges was mentioned. OpenBSD users saw
5414 more crashes here, but all platforms were potentially affected.
5415 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
5417 o Major bugfixes (relay, OOM handler):
5418 - Fix a timing-dependent assertion failure that could occur when we
5419 tried to flush from a circuit after having freed its cells because
5420 of an out-of-memory condition. Fixes bug 20203; bugfix on
5421 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
5424 o Minor feature (fallback directories):
5425 - Remove broken fallbacks from the hard-coded fallback directory
5426 list. Closes ticket 20190; patch by teor.
5428 o Minor features (geoip):
5429 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
5433 Changes in version 0.2.8.7 - 2016-08-24
5434 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
5435 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
5436 who sets the ReachableAddresses option, and all bridges, are strongly
5437 encouraged to upgrade.
5439 o Directory authority changes:
5440 - The "Tonga" bridge authority has been retired; the new bridge
5441 authority is "Bifroest". Closes tickets 19728 and 19690.
5443 o Major bugfixes (client, security):
5444 - Only use the ReachableAddresses option to restrict the first hop
5445 in a path. In earlier versions of 0.2.8.x, it would apply to
5446 every hop in the path, with a possible degradation in anonymity
5447 for anyone using an uncommon ReachableAddress setting. Fixes bug
5448 19973; bugfix on 0.2.8.2-alpha.
5450 o Minor features (geoip):
5451 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
5454 o Minor bugfixes (compilation):
5455 - Remove an inappropriate "inline" in tortls.c that was causing
5456 warnings on older versions of GCC. Fixes bug 19903; bugfix
5459 o Minor bugfixes (fallback directories):
5460 - Avoid logging a NULL string pointer when loading fallback
5461 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
5462 and 0.2.8.1-alpha. Report and patch by "rubiate".
5465 Changes in version 0.2.8.6 - 2016-08-02
5467 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
5469 The Tor 0.2.8 series improves client bootstrapping performance,
5470 completes the authority-side implementation of improved identity
5471 keys for relays, and includes numerous bugfixes and performance
5472 improvements throughout the program. This release continues to
5473 improve the coverage of Tor's test suite. For a full list of
5474 changes since Tor 0.2.7, see the ReleaseNotes file.
5476 Below is a list of the changes since Tor 0.2.7.
5478 o New system requirements:
5479 - Tor no longer attempts to support platforms where the "time_t"
5480 type is unsigned. (To the best of our knowledge, only OpenVMS does
5481 this, and Tor has never actually built on OpenVMS.) Closes
5483 - Tor no longer supports versions of OpenSSL with a broken
5484 implementation of counter mode. (This bug was present in OpenSSL
5485 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
5486 longer runs with, these versions.
5487 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
5488 later (released in 2008 and 2009 respectively). If you are
5489 building Tor from the git repository instead of from the source
5490 distribution, and your tools are older than this, you will need to
5491 upgrade. Closes ticket 17732.
5493 o Directory authority changes:
5494 - Update the V3 identity key for the dannenberg directory authority:
5495 it was changed on 18 November 2015. Closes task 17906. Patch
5497 - Urras is no longer a directory authority. Closes ticket 19271.
5499 o Major features (directory system):
5500 - Include a trial list of default fallback directories, based on an
5501 opt-in survey of suitable relays. Doing this should make clients
5502 bootstrap more quickly and reliably, and reduce the load on the
5503 directory authorities. Closes ticket 15775. Patch by teor.
5504 Candidates identified using an OnionOO script by weasel, teor,
5505 gsathya, and karsten.
5506 - Previously only relays that explicitly opened a directory port
5507 (DirPort) accepted directory requests from clients. Now all
5508 relays, with and without a DirPort, accept and serve tunneled
5509 directory requests that they receive through their ORPort. You can
5510 disable this behavior using the new DirCache option. Closes
5512 - When bootstrapping multiple consensus downloads at a time, use the
5513 first one that starts downloading, and close the rest. This
5514 reduces failures when authorities or fallback directories are slow
5515 or down. Together with the code for feature 15775, this feature
5516 should reduces failures due to fallback churn. Implements ticket
5517 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
5520 o Major features (security, Linux):
5521 - When Tor starts as root on Linux and is told to switch user ID, it
5522 can now retain the capability to bind to low ports. By default,
5523 Tor will do this only when it's switching user ID and some low
5524 ports have been configured. You can change this behavior with the
5525 new option KeepBindCapabilities. Closes ticket 8195.
5527 o Major bugfixes (client, bootstrapping):
5528 - Check if bootstrap consensus downloads are still needed when the
5529 linked connection attaches. This prevents tor making unnecessary
5530 begindir-style connections, which are the only directory
5531 connections tor clients make since the fix for 18483 was merged.
5532 - Fix some edge cases where consensus download connections may not
5533 have been closed, even though they were not needed. Related to fix
5535 - Make relays retry consensus downloads the correct number of times,
5536 rather than the more aggressive client retry count. Fixes part of
5539 o Major bugfixes (dns proxy mode, crash):
5540 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5541 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5543 o Major bugfixes (ed25519, voting):
5544 - Actually enable support for authorities to match routers by their
5545 Ed25519 identities. Previously, the code had been written, but
5546 some debugging code that had accidentally been left in the
5547 codebase made it stay turned off. Fixes bug 17702; bugfix
5549 - When collating votes by Ed25519 identities, authorities now
5550 include a "NoEdConsensus" flag if the ed25519 value (or lack
5551 thereof) for a server does not reflect the majority consensus.
5552 Related to bug 17668; bugfix on 0.2.7.2-alpha.
5553 - When generating a vote with keypinning disabled, never include two
5554 entries for the same ed25519 identity. This bug was causing
5555 authorities to generate votes that they could not parse when a
5556 router violated key pinning by changing its RSA identity but
5557 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
5558 18318. Bugfix on 0.2.7.2-alpha.
5560 o Major bugfixes (key management):
5561 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5562 pointer to the previous (uninitialized) key value. The impact here
5563 should be limited to a difficult-to-trigger crash, if OpenSSL is
5564 running an engine that makes key generation failures possible, or
5565 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5566 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5569 o Major bugfixes (security, client, DNS proxy):
5570 - Stop a crash that could occur when a client running with DNSPort
5571 received a query with multiple address types, and the first
5572 address type was not supported. Found and fixed by Scott Dial.
5573 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5575 o Major bugfixes (security, compilation):
5576 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
5577 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
5578 cause a compiler warning, thereby making other checks fail, and
5579 needlessly disabling compiler-hardening support. Fixes one case of
5580 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
5581 - Repair hardened builds under the clang compiler. Previously, our
5582 use of _FORTIFY_SOURCE would conflict with clang's address
5583 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
5585 o Major bugfixes (security, pointers):
5586 - Avoid a difficult-to-trigger heap corruption attack when extending
5587 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5588 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5589 Reported by Guido Vranken.
5591 o Major bugfixes (testing):
5592 - Fix a bug that would block 'make test-network-all' on systems where
5593 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
5595 o Major bugfixes (user interface):
5596 - Correctly give a warning in the cases where a relay is specified
5597 by nickname, and one such relay is found, but it is not officially
5598 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
5600 o Minor features (accounting):
5601 - Added two modes to the AccountingRule option: One for limiting
5602 only the number of bytes sent ("AccountingRule out"), and one for
5603 limiting only the number of bytes received ("AccountingRule in").
5604 Closes ticket 15989; patch from "unixninja92".
5606 o Minor features (bug-resistance):
5607 - Make Tor survive errors involving connections without a
5608 corresponding event object. Previously we'd fail with an
5609 assertion; now we produce a log message. Related to bug 16248.
5610 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
5611 level code, to harden against accidental failures to NUL-
5612 terminate. Part of ticket 17852. Patch from jsturgix. Found
5615 o Minor features (build):
5616 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
5617 as having possible IPFW support. Closes ticket 18448. Patch from
5619 - Since our build process now uses "make distcheck", we no longer
5620 force "make dist" to depend on "make check". Closes ticket 17893;
5621 patch from "cypherpunks".
5622 - Tor now builds once again with the recent OpenSSL 1.1 development
5623 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
5624 tracking OpenSSL 1.1 development as it has progressed, and fixing
5625 numerous compatibility issues as they arose. See tickets
5626 17549, 17921, 17984, 19499, and 18286.
5627 - When building manual pages, set the timezone to "UTC", so that the
5628 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
5629 Patch from intrigeri.
5631 o Minor features (clients):
5632 - Make clients, onion services, and bridge relays always use an
5633 encrypted begindir connection for directory requests. Resolves
5634 ticket 18483. Patch by teor.
5636 o Minor features (controller):
5637 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
5638 controllers can examine the the reject rules added by
5639 ExitPolicyRejectPrivate. This makes it easier for stem to display
5641 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
5642 tickets 16774 and 17817. Patch by George Tankersley.
5643 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
5644 service descriptor from a service's local hidden service
5645 descriptor cache. Closes ticket 14846.
5647 o Minor features (crypto):
5648 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
5649 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
5651 - Improve performance when hashing non-multiple of 8 sized buffers,
5652 based on Andrew Moon's public domain SipHash-2-4 implementation.
5653 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
5654 - Validate the hard-coded Diffie-Hellman parameters and ensure that
5655 p is a safe prime, and g is a suitable generator. Closes
5657 - When allocating a digest state object, allocate no more space than
5658 we actually need. Previously, we would allocate as much space as
5659 the state for the largest algorithm would need. This change saves
5660 up to 672 bytes per circuit. Closes ticket 17796.
5662 o Minor features (directory downloads):
5663 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
5664 directory mirrors. The default is 1; set it to 0 to disable
5665 fallbacks. Implements ticket 17576. Patch by teor.
5666 - Wait for busy authorities and fallback directories to become non-
5667 busy when bootstrapping. (A similar change was made in 6c443e987d
5668 for directory caches chosen from the consensus.) Closes ticket
5669 17864; patch by teor.
5671 o Minor features (geoip):
5672 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
5675 o Minor features (hidden service directory):
5676 - Streamline relay-side hsdir handling: when relays consider whether
5677 to accept an uploaded hidden service descriptor, they no longer
5678 check whether they are one of the relays in the network that is
5679 "supposed" to handle that descriptor. Implements ticket 18332.
5681 o Minor features (IPv6):
5682 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
5683 to 1, tor prefers IPv6 directory addresses.
5684 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
5685 avoids using IPv4 for client OR and directory connections.
5686 - Add address policy assume_action support for IPv6 addresses.
5687 - Add an argument 'ipv6=address:orport' to the DirAuthority and
5688 FallbackDir torrc options, to specify an IPv6 address for an
5689 authority or fallback directory. Add hard-coded ipv6 addresses for
5690 directory authorities that have them. Closes ticket 17327; patch
5691 from Nick Mathewson and teor.
5692 - Allow users to configure directory authorities and fallback
5693 directory servers with IPv6 addresses and ORPorts. Resolves
5695 - Limit IPv6 mask bits to 128.
5696 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
5697 17638; bugfix on 0.0.2pre8. Patch by teor.
5698 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
5699 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
5700 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
5701 - Warn when comparing against an AF_UNSPEC address in a policy, it's
5702 almost always a bug. Closes ticket 17863; patch by teor.
5703 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
5704 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
5706 o Minor features (Linux seccomp2 sandbox):
5707 - Reject attempts to change our Address with "Sandbox 1" enabled.
5708 Changing Address with Sandbox turned on would never actually work,
5709 but previously it would fail in strange and confusing ways. Found
5712 o Minor features (logging):
5713 - When logging to syslog, allow a tag to be added to the syslog
5714 identity (the string prepended to every log message). The tag can
5715 be configured with SyslogIdentityTag and defaults to none. Setting
5716 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
5719 o Minor features (portability):
5720 - Use timingsafe_memcmp() where available. Closes ticket 17944;
5721 patch from <logan@hackers.mu>.
5723 o Minor features (relay, address discovery):
5724 - Add a family argument to get_interface_addresses_raw() and
5725 subfunctions to make network interface address interogation more
5726 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
5727 types of interfaces from the operating system. Resolves
5729 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
5730 fails to enumerate interface addresses using the platform-specific
5731 API, have it rely on the UDP socket fallback technique to try and
5732 find out what IP addresses (both IPv4 and IPv6) our machine has.
5733 Resolves ticket 17951.
5735 o Minor features (replay cache):
5736 - The replay cache now uses SHA256 instead of SHA1. Implements
5737 feature 8961. Patch by teor, issue reported by rransom.
5739 o Minor features (robustness):
5740 - Exit immediately with an error message if the code attempts to use
5741 Libevent without having initialized it. This should resolve some
5742 frequently-made mistakes in our unit tests. Closes ticket 18241.
5744 o Minor features (security, clock):
5745 - Warn when the system clock appears to move back in time (when the
5746 state file was last written in the future). Tor doesn't know that
5747 consensuses have expired if the clock is in the past. Patch by
5748 teor. Implements ticket 17188.
5750 o Minor features (security, exit policies):
5751 - ExitPolicyRejectPrivate now rejects more private addresses by
5752 default. Specifically, it now rejects the relay's outbound bind
5753 addresses (if configured), and the relay's configured port
5754 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
5755 0.2.0.11-alpha. Patch by teor.
5757 o Minor features (security, memory erasure):
5758 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5759 zero size. Check size argument to memwipe() for underflow. Fixes
5760 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5762 - Set the unused entries in a smartlist to NULL. This helped catch
5763 a (harmless) bug, and shouldn't affect performance too much.
5764 Implements ticket 17026.
5765 - Use SecureMemoryWipe() function to securely clean memory on
5766 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
5767 Implements feature 17986.
5768 - Use explicit_bzero or memset_s when present. Previously, we'd use
5769 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
5770 from <logan@hackers.mu> and <selven@hackers.mu>.
5772 o Minor features (security, RNG):
5773 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
5774 positively are not allowed to fail. Previously we depended on
5775 internal details of OpenSSL's behavior. Closes ticket 17686.
5776 - Never use the system entropy output directly for anything besides
5777 seeding the PRNG. When we want to generate important keys, instead
5778 of using system entropy directly, we now hash it with the PRNG
5779 stream. This may help resist certain attacks based on broken OS
5780 entropy implementations. Closes part of ticket 17694.
5781 - Use modern system calls (like getentropy() or getrandom()) to
5782 generate strong entropy on platforms that have them. Closes
5785 o Minor features (security, win32):
5786 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
5787 attack. Fixes bug 18123; bugfix on all tor versions. Patch
5790 o Minor features (unix domain sockets):
5791 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
5792 Unix domain sockets without checking the permissions on the parent
5793 directory. (Tor checks permissions by default because some
5794 operating systems only check permissions on the parent directory.
5795 However, some operating systems do look at permissions on the
5796 socket, and tor's default check is unneeded.) Closes ticket 18458.
5799 o Minor features (unix file permissions):
5800 - Defer creation of Unix sockets until after setuid. This avoids
5801 needing CAP_CHOWN and CAP_FOWNER when using systemd's
5802 CapabilityBoundingSet, or chown and fowner when using SELinux.
5803 Implements part of ticket 17562. Patch from Jamie Nguyen.
5804 - If any directory created by Tor is marked as group readable, the
5805 filesystem group is allowed to be either the default GID or the
5806 root user. Allowing root to read the DataDirectory prevents the
5807 need for CAP_READ_SEARCH when using systemd's
5808 CapabilityBoundingSet, or dac_read_search when using SELinux.
5809 Implements part of ticket 17562. Patch from Jamie Nguyen.
5810 - Introduce a new DataDirectoryGroupReadable option. If it is set to
5811 1, the DataDirectory will be made readable by the default GID.
5812 Implements part of ticket 17562. Patch from Jamie Nguyen.
5814 o Minor bugfixes (accounting):
5815 - The max bandwidth when using 'AccountRule sum' is now correctly
5816 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
5819 o Minor bugfixes (assert, portability):
5820 - Fix an assertion failure in memarea.c on systems where "long" is
5821 shorter than the size of a pointer. Fixes bug 18716; bugfix
5824 o Minor bugfixes (bootstrap):
5825 - Consistently use the consensus download schedule for authority
5826 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5828 o Minor bugfixes (build):
5829 - Avoid spurious failures from configure files related to calling
5830 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
5831 0.2.0.1-alpha. Patch from "cypherpunks".
5832 - Do not link the unit tests against both the testing and non-
5833 testing versions of the static libraries. Fixes bug 18490; bugfix
5835 - Resolve warnings when building on systems that are concerned with
5836 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5838 - Silence spurious clang-scan warnings in the ed25519_donna code by
5839 explicitly initializing some objects. Fixes bug 18384; bugfix on
5840 0.2.7.2-alpha. Patch by teor.
5841 - When libscrypt.h is found, but no libscrypt library can be linked,
5842 treat libscrypt as absent. Fixes bug 19161; bugfix
5844 - Cause the unit tests to compile correctly on mingw64 versions that
5845 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5846 - Don't try to use the pthread_condattr_setclock() function unless
5847 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
5848 17819; bugfix on 0.2.6.3-alpha.
5849 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
5851 - Fix search for libevent libraries on OpenBSD (and other systems
5852 that install libevent 1 and libevent 2 in parallel). Fixes bug
5853 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
5854 - Isolate environment variables meant for tests from the rest of the
5855 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
5856 - Mark all object files that include micro-revision.i as depending
5857 on it, so as to make parallel builds more reliable. Fixes bug
5858 17826; bugfix on 0.2.5.1-alpha.
5859 - Remove config.log only from make distclean, not from make clean.
5860 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
5861 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
5863 - Remove an #endif from configure.ac so that we correctly detect the
5864 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
5867 o Minor bugfixes (client, bootstrap):
5868 - Count receipt of new microdescriptors as progress towards
5869 bootstrapping. Previously, with EntryNodes set, Tor might not
5870 successfully repopulate the guard set on bootstrapping. Fixes bug
5871 16825; bugfix on 0.2.3.1-alpha.
5873 o Minor bugfixes (code correctness):
5874 - Fix a bad memory handling bug that would occur if we had queued a
5875 cell on a channel's incoming queue. Fortunately, we can't actually
5876 queue a cell like that as our code is constructed today, but it's
5877 best to avoid this kind of error, even if there isn't any code
5878 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
5879 - Assert that allocated memory held by the reputation code is freed
5880 according to its internal counters. Fixes bug 17753; bugfix
5882 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
5884 - Update to the latest version of Trunnel, which tries harder to
5885 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
5886 by clang address sanitizer. Fixes bug 18373; bugfix
5888 - When closing an entry connection, generate a warning if we should
5889 have sent an end cell for it but we haven't. Fixes bug 17876;
5890 bugfix on 0.2.3.2-alpha.
5892 o Minor bugfixes (configuration):
5893 - Fix a tiny memory leak when parsing a port configuration ending in
5894 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
5896 o Minor bugfixes (containers):
5897 - If we somehow attempt to construct a heap with more than
5898 1073741822 elements, avoid an integer overflow when maintaining
5899 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
5901 o Minor bugfixes (controller, microdescriptors):
5902 - Make GETINFO dir/status-vote/current/consensus conform to the
5903 control specification by returning "551 Could not open cached
5904 consensus..." when not caching consensuses. Fixes bug 18920;
5905 bugfix on 0.2.2.6-alpha.
5907 o Minor bugfixes (crypto):
5908 - Check the return value of HMAC() and assert on failure. Fixes bug
5909 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
5911 o Minor bugfixes (directories):
5912 - When fetching extrainfo documents, compare their SHA256 digests
5913 and Ed25519 signing key certificates with the routerinfo that led
5914 us to fetch them, rather than with the most recent routerinfo.
5915 Otherwise we generate many spurious warnings about mismatches.
5916 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
5917 - When generating a URL for a directory server on an IPv6 address,
5918 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
5919 on 0.2.3.9-alpha. Patch from Malek.
5921 o Minor bugfixes (downloading):
5922 - Predict more correctly whether we'll be downloading over HTTP when
5923 we determine the maximum length of a URL. This should avoid a
5924 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5927 o Minor bugfixes (exit policies, security):
5928 - Refresh an exit relay's exit policy when interface addresses
5929 change. Previously, tor only refreshed the exit policy when the
5930 configured external address changed. Fixes bug 18208; bugfix on
5931 0.2.7.3-rc. Patch by teor.
5933 o Minor bugfixes (fallback directories):
5934 - Mark fallbacks as "too busy" when they return a 503 response,
5935 rather than just marking authorities. Fixes bug 17572; bugfix on
5936 0.2.4.7-alpha. Patch by teor.
5937 - When requesting extrainfo descriptors from a trusted directory
5938 server, check whether it is an authority or a fallback directory
5939 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
5940 0.2.4.7-alpha. Reported by atagar, patch by teor.
5942 o Minor bugfixes (hidden service, client):
5943 - Handle the case where the user makes several fast consecutive
5944 requests to the same .onion address. Previously, the first six
5945 requests would each trigger a descriptor fetch, each picking a
5946 directory (there are 6 overall) and the seventh one would fail
5947 because no directories were left, thereby triggering a close on
5948 all current directory connections asking for the hidden service.
5949 The solution here is to not close the connections if we have
5950 pending directory fetches. Fixes bug 15937; bugfix
5953 o Minor bugfixes (hidden service, control port):
5954 - Add the onion address to the HS_DESC event for the UPLOADED action
5955 both on success or failure. It was previously hardcoded with
5956 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
5958 o Minor bugfixes (hidden service, directory):
5959 - Bridges now refuse "rendezvous2" (hidden service descriptor)
5960 publish attempts. Suggested by ticket 18332.
5962 o Minor bugfixes (IPv6):
5963 - Update the limits in max_dl_per_request for IPv6 address length.
5964 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
5966 o Minor bugfixes (Linux seccomp2 sandbox):
5967 - Allow more syscalls when running with "Sandbox 1" enabled:
5968 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5969 some systems, these are required for Tor to start. Fixes bug
5970 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5971 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5972 so that get_interface_address6_via_udp_socket_hack() can work.
5973 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5974 - Allow the setrlimit syscall, and the prlimit and prlimit64
5975 syscalls, which some libc implementations use under the hood.
5976 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
5977 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
5978 enabled and no DNS resolvers configured. This should help TAILS
5979 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
5980 - Fix a crash when using offline master ed25519 keys with the Linux
5981 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
5982 - Allow statistics to be written to disk when "Sandbox 1" is
5983 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5984 0.2.6.1-alpha respectively.
5986 o Minor bugfixes (logging):
5987 - In log messages that include a function name, use __FUNCTION__
5988 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
5989 with clang __PRETTY_FUNCTION__ has extra information we don't
5990 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
5992 - Remove needless quotes from a log message about unparseable
5993 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
5994 - Scrub service name in "unrecognized service ID" log messages.
5995 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
5996 - When logging information about an unparsable networkstatus vote or
5997 consensus, do not say "vote" when we mean consensus. Fixes bug
5998 18368; bugfix on 0.2.0.8-alpha.
5999 - When we can't generate a signing key because OfflineMasterKey is
6000 set, do not imply that we should have been able to load it. Fixes
6001 bug 18133; bugfix on 0.2.7.2-alpha.
6002 - When logging a malformed hostname received through socks4, scrub
6003 it if SafeLogging says we should. Fixes bug 17419; bugfix
6006 o Minor bugfixes (memory safety):
6007 - Avoid freeing an uninitialized pointer when opening a socket fails
6008 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
6009 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
6011 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
6012 18672; bugfix on 0.2.5.1-alpha.
6013 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
6016 o Minor bugfixes (pluggable transports):
6017 - Avoid reporting a spurious error when we decide that we don't need
6018 to terminate a pluggable transport because it has already exited.
6019 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
6021 o Minor bugfixes (pointer arithmetic):
6022 - Fix a bug in memarea_alloc() that could have resulted in remote
6023 heap write access, if Tor had ever passed an unchecked size to
6024 memarea_alloc(). Fortunately, all the sizes we pass to
6025 memarea_alloc() are pre-checked to be less than 128 kilobytes.
6026 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
6029 o Minor bugfixes (private directory):
6030 - Prevent a race condition when creating private directories. Fixes
6031 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
6032 Patch from jsturgix. Found with Flawfinder.
6034 o Minor bugfixes (relays):
6035 - Check that both the ORPort and DirPort (if present) are reachable
6036 before publishing a relay descriptor. Otherwise, relays publish a
6037 descriptor with DirPort 0 when the DirPort reachability test takes
6038 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6039 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
6040 - Resolve some edge cases where we might launch an ORPort
6041 reachability check even when DisableNetwork is set. Noticed while
6042 fixing bug 18616; bugfix on 0.2.3.9-alpha.
6044 o Minor bugfixes (relays, hidden services):
6045 - Refuse connection requests to private OR addresses unless
6046 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6047 then refuse to send any cells to a private address. Fixes bugs
6048 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
6050 o Minor bugfixes (security, hidden services):
6051 - Prevent hidden services connecting to client-supplied rendezvous
6052 addresses that are reserved as internal or multicast. Fixes bug
6053 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6055 o Minor bugfixes (statistics):
6056 - Consistently check for overflow in round_*_to_next_multiple_of
6057 functions, and add unit tests with additional and maximal values.
6058 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6059 - Handle edge cases in the laplace functions: avoid division by
6060 zero, avoid taking the log of zero, and silence clang type
6061 conversion warnings using round and trunc. Add unit tests for edge
6062 cases with maximal values. Fixes part of bug 13192; bugfix
6064 - We now include consensus downloads via IPv6 in our directory-
6065 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
6067 o Minor bugfixes (test networks, IPv6):
6068 - Allow internal IPv6 addresses in descriptors in test networks.
6069 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
6072 o Minor bugfixes (testing):
6073 - Check the full results of SHA256 and SHA512 digests in the unit
6074 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
6075 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6077 - Fix a small memory leak that would occur when the
6078 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
6079 bugfix on 0.2.5.2-alpha.
6080 - Make unit tests pass on IPv6-only systems, and systems without
6081 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6082 bugfix on 0.2.7.3-rc. Patch by teor.
6083 - The test for log_heartbeat was incorrectly failing in timezones
6084 with non-integer offsets. Instead of comparing the end of the time
6085 string against a constant, compare it to the output of
6086 format_local_iso_time when given the correct input. Fixes bug
6087 18039; bugfix on 0.2.5.4-alpha.
6088 - We no longer disable assertions in the unit tests when coverage is
6089 enabled. Instead, we require you to say --disable-asserts-in-tests
6090 to the configure script if you need assertions disabled in the
6091 unit tests (for example, if you want to perform branch coverage).
6092 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
6094 o Minor bugfixes (time handling):
6095 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
6096 field. Otherwise, our unit tests crash on Windows. Fixes bug
6097 18977; bugfix on 0.2.2.25-alpha.
6098 - Avoid overflow in tor_timegm when parsing dates in and after 2038
6099 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
6100 0.0.2pre14. Patch by teor.
6102 o Minor bugfixes (tor-gencert):
6103 - Correctly handle the case where an authority operator enters a
6104 passphrase but sends an EOF before sending a newline. Fixes bug
6105 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
6107 o Code simplification and refactoring:
6108 - Clean up a little duplicated code in
6109 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6111 - Decouple the list of streams waiting to be attached to circuits
6112 from the overall connection list. This change makes it possible to
6113 attach streams quickly while simplifying Tor's callgraph and
6114 avoiding O(N) scans of the entire connection list. Closes
6116 - Extract the more complicated parts of circuit_mark_for_close()
6117 into a new function that we run periodically before circuits are
6118 freed. This change removes more than half of the functions
6119 currently in the "blob". Closes ticket 17218.
6120 - Move logging of redundant policy entries in
6121 policies_parse_exit_policy_internal into its own function. Closes
6122 ticket 17608; patch from "juce".
6123 - Quote all the string interpolations in configure.ac -- even those
6124 which we are pretty sure can't contain spaces. Closes ticket
6125 17744. Patch from zerosion.
6126 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6127 use them. Closes ticket 17926.
6128 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
6129 inplace, so there's no need to have a separate implementation for
6130 the non-inplace code. Closes ticket 18258. Patch from Malek.
6131 - Simplify return types for some crypto functions that can't
6132 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
6133 - When a direct directory request fails immediately on launch,
6134 instead of relaunching that request from inside the code that
6135 launches it, instead mark the connection for teardown. This change
6136 simplifies Tor's callback and prevents the directory-request
6137 launching code from invoking itself recursively. Closes
6141 - Add a description of the correct use of the '--keygen' command-
6142 line option. Closes ticket 17583; based on text by 's7r'.
6143 - Change build messages to refer to "Fedora" instead of "Fedora
6144 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
6145 Patches from "icanhasaccount" and "cypherpunks".
6146 - Document the contents of the 'datadir/keys' subdirectory in the
6147 manual page. Closes ticket 17621.
6148 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6149 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6150 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6151 - Mention torspec URL in the manpage and point the reader to it
6152 whenever we mention a document that belongs in torspce. Fixes
6154 - Stop recommending use of nicknames to identify relays in our
6155 MapAddress documentation. Closes ticket 18312.
6158 - Remove client-side support for connecting to Tor relays running
6159 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6160 the v3 TLS handshake protocol, and are no longer allowed on the
6161 Tor network. Implements the client side of ticket 11150. Based on
6162 patches by Tom van der Woerdt.
6163 - We no longer maintain an internal freelist in memarea.c.
6164 Allocators should be good enough to make this code unnecessary,
6165 and it's doubtful that it ever had any performance benefit.
6168 - Add unit tests to check for common RNG failure modes, such as
6169 returning all zeroes, identical values, or incrementing values
6170 (OpenSSL's rand_predictable feature). Patch by teor.
6171 - Always test both ed25519 backends, so that we can be sure that our
6172 batch-open replacement code works. Part of ticket 16794.
6173 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6174 portion of ticket 16831.
6175 - Fix several warnings from clang's address sanitizer produced in
6177 - Log more information when the backtrace tests fail. Closes ticket
6178 17892. Patch from "cypherpunks."
6179 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6180 util_format.c, directory.c, and options_validate.c. Closes tickets
6181 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6183 - Treat backtrace test failures as expected on FreeBSD until we
6184 solve bug 17808. Closes ticket 18204.
6185 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6186 Patch from Reinaldo de Souza Jr.
6189 Changes in version 0.2.7.6 - 2015-12-10
6190 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6191 well as a minor bug in hidden service reliability.
6193 o Major bugfixes (guard selection):
6194 - Actually look at the Guard flag when selecting a new directory
6195 guard. When we implemented the directory guard design, we
6196 accidentally started treating all relays as if they have the Guard
6197 flag during guard selection, leading to weaker anonymity and worse
6198 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6201 o Minor features (geoip):
6202 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6205 o Minor bugfixes (compilation):
6206 - When checking for net/pfvar.h, include netinet/in.h if possible.
6207 This fixes transparent proxy detection on OpenBSD. Fixes bug
6208 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6209 - Fix a compilation warning with Clang 3.6: Do not check the
6210 presence of an address which can never be NULL. Fixes bug 17781.
6212 o Minor bugfixes (correctness):
6213 - When displaying an IPv6 exit policy, include the mask bits
6214 correctly even when the number is greater than 31. Fixes bug
6215 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6216 - The wrong list was used when looking up expired intro points in a
6217 rend service object, causing what we think could be reachability
6218 issues for hidden services, and triggering a BUG log. Fixes bug
6219 16702; bugfix on 0.2.7.2-alpha.
6220 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6221 bug 17722; bugfix on 0.2.7.2-alpha.
6224 Changes in version 0.2.7.5 - 2015-11-20
6225 The Tor 0.2.7 release series is dedicated to the memory of Tor user
6226 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
6227 tirelessly to advocate human rights regardless of national borders,
6228 and oppose the encroachments of mass surveillance. He opposed national
6229 exceptionalism, he brought clarity to legal and policy debates, he
6230 understood and predicted the impact of mass surveillance on the world,
6231 and he laid the groundwork for resisting it. While serving on the Tor
6232 Project's board of directors, he brought us his uncompromising focus
6233 on technical excellence in the service of humankind. Caspar was an
6234 inimitable force for good and a wonderful friend. He was kind,
6235 humorous, generous, gallant, and believed we should protect one
6236 another without exception. We honor him here for his ideals, his
6237 efforts, and his accomplishments. Please honor his memory with works
6238 that would make him proud.
6240 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
6242 The 0.2.7 series adds a more secure identity key type for relays,
6243 improves cryptography performance, resolves several longstanding
6244 hidden-service performance issues, improves controller support for
6245 hidden services, and includes small bugfixes and performance
6246 improvements throughout the program. This release series also includes
6247 more tests than before, and significant simplifications to which parts
6248 of Tor invoke which others. For a full list of changes, see below.
6250 o New system requirements:
6251 - Tor no longer includes workarounds to support Libevent versions
6252 before 1.3e. Libevent 2.0 or later is recommended. Closes
6254 - Tor no longer supports copies of OpenSSL that are missing support
6255 for Elliptic Curve Cryptography. (We began using ECC when
6256 available in 0.2.4.8-alpha, for more safe and efficient key
6257 negotiation.) In particular, support for at least one of P256 or
6258 P224 is now required, with manual configuration needed if only
6259 P224 is available. Resolves ticket 16140.
6260 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
6261 on an operating system that has not upgraded to OpenSSL 1.0 or
6262 later, and you compile Tor from source, you will need to install a
6263 more recent OpenSSL to link Tor against.) These versions of
6264 OpenSSL are still supported by the OpenSSL, but the numerous
6265 cryptographic improvements in later OpenSSL releases makes them a
6266 clear choice. Resolves ticket 16034.
6268 o Major features (controller):
6269 - Add the ADD_ONION and DEL_ONION commands that allow the creation
6270 and management of hidden services via the controller. Closes
6272 - New "GETINFO onions/current" and "GETINFO onions/detached"
6273 commands to get information about hidden services created via the
6274 controller. Part of ticket 6411.
6275 - New HSFETCH command to launch a request for a hidden service
6276 descriptor. Closes ticket 14847.
6277 - New HSPOST command to upload a hidden service descriptor. Closes
6278 ticket 3523. Patch by "DonnchaC".
6280 o Major features (Ed25519 identity keys, Proposal 220):
6281 - Add support for offline encrypted Ed25519 master keys. To use this
6282 feature on your tor relay, run "tor --keygen" to make a new master
6283 key (or to make a new signing key if you already have a master
6284 key). Closes ticket 13642.
6285 - All relays now maintain a stronger identity key, using the Ed25519
6286 elliptic curve signature format. This master key is designed so
6287 that it can be kept offline. Relays also generate an online
6288 signing key, and a set of other Ed25519 keys and certificates.
6289 These are all automatically regenerated and rotated as needed.
6290 Implements part of ticket 12498.
6291 - Directory authorities now vote on Ed25519 identity keys along with
6292 RSA1024 keys. Implements part of ticket 12498.
6293 - Directory authorities track which Ed25519 identity keys have been
6294 used with which RSA1024 identity keys, and do not allow them to
6295 vary freely. Implements part of ticket 12498.
6296 - Microdescriptors now include Ed25519 identity keys. Implements
6297 part of ticket 12498.
6298 - Add a --newpass option to allow changing or removing the
6299 passphrase of an encrypted key with tor --keygen. Implements part
6301 - Add a new OfflineMasterKey option to tell Tor never to try loading
6302 or generating a secret Ed25519 identity key. You can use this in
6303 combination with tor --keygen to manage offline and/or encrypted
6304 Ed25519 keys. Implements ticket 16944.
6305 - On receiving a HUP signal, check to see whether the Ed25519
6306 signing key has changed, and reload it if so. Closes ticket 16790.
6307 - Significant usability improvements for Ed25519 key management. Log
6308 messages are better, and the code can recover from far more
6309 failure conditions. Thanks to "s7r" for reporting and diagnosing
6312 o Major features (ECC performance):
6313 - Improve the runtime speed of Ed25519 signature verification by
6314 using Ed25519-donna's batch verification support. Implements
6316 - Improve the speed of Ed25519 operations and Curve25519 keypair
6317 generation when built targeting 32 bit x86 platforms with SSE2
6318 available. Implements ticket 16535.
6319 - Improve the runtime speed of Ed25519 operations by using the
6320 public-domain Ed25519-donna by Andrew M. ("floodyberry").
6321 Implements ticket 16467.
6322 - Improve the runtime speed of the ntor handshake by using an
6323 optimized curve25519 basepoint scalarmult implementation from the
6324 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
6325 ideas by Adam Langley. Implements ticket 9663.
6327 o Major features (Hidden services):
6328 - Hidden services, if using the EntryNodes option, are required to
6329 use more than one EntryNode, in order to avoid a guard discovery
6330 attack. (This would only affect people who had configured hidden
6331 services and manually specified the EntryNodes option with a
6332 single entry-node. The impact was that it would be easy to
6333 remotely identify the guard node used by such a hidden service.
6334 See ticket for more information.) Fixes ticket 14917.
6335 - Add the torrc option HiddenServiceNumIntroductionPoints, to
6336 specify a fixed number of introduction points. Its maximum value
6337 is 10 and default is 3. Using this option can increase a hidden
6338 service's reliability under load, at the cost of making it more
6339 visible that the hidden service is facing extra load. Closes
6341 - Remove the adaptive algorithm for choosing the number of
6342 introduction points, which used to change the number of
6343 introduction points (poorly) depending on the number of
6344 connections the HS sees. Closes ticket 4862.
6346 o Major features (onion key cross-certification):
6347 - Relay descriptors now include signatures of their own identity
6348 keys, made using the TAP and ntor onion keys. These signatures
6349 allow relays to prove ownership of their own onion keys. Because
6350 of this change, microdescriptors will no longer need to include
6351 RSA identity keys. Implements proposal 228; closes ticket 12499.
6353 o Major bugfixes (client-side privacy, also in 0.2.6.9):
6354 - Properly separate out each SOCKSPort when applying stream
6355 isolation. The error occurred because each port's session group
6356 was being overwritten by a default value when the listener
6357 connection was initialized. Fixes bug 16247; bugfix on
6358 0.2.6.3-alpha. Patch by "jojelino".
6360 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
6361 - Stop refusing to store updated hidden service descriptors on a
6362 client. This reverts commit 9407040c59218 (which indeed fixed bug
6363 14219, but introduced a major hidden service reachability
6364 regression detailed in bug 16381). This is a temporary fix since
6365 we can live with the minor issue in bug 14219 (it just results in
6366 some load on the network) but the regression of 16381 is too much
6367 of a setback. First-round fix for bug 16381; bugfix
6370 o Major bugfixes (hidden services):
6371 - Revert commit that made directory authorities assign the HSDir
6372 flag to relays without a DirPort; this was bad because such relays
6373 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6375 - When cannibalizing a circuit for an introduction point, always
6376 extend to the chosen exit node (creating a 4 hop circuit).
6377 Previously Tor would use the current circuit exit node, which
6378 changed the original choice of introduction point, and could cause
6379 the hidden service to skip excluded introduction points or
6380 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
6383 o Major bugfixes (memory leaks):
6384 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
6385 17398; bugfix on 0.2.6.1-alpha.
6387 o Major bugfixes (open file limit):
6388 - The open file limit wasn't checked before calling
6389 tor_accept_socket_nonblocking(), which would make Tor exceed the
6390 limit. Now, before opening a new socket, Tor validates the open
6391 file limit just before, and if the max has been reached, return an
6392 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
6394 o Major bugfixes (security, correctness):
6395 - Fix an error that could cause us to read 4 bytes before the
6396 beginning of an openssl string. This bug could be used to cause
6397 Tor to crash on systems with unusual malloc implementations, or
6398 systems with unusual hardening installed. Fixes bug 17404; bugfix
6401 o Major bugfixes (stability, also in 0.2.6.10):
6402 - Stop crashing with an assertion failure when parsing certain kinds
6403 of malformed or truncated microdescriptors. Fixes bug 16400;
6404 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6405 by "cypherpunks_backup".
6406 - Stop random client-side assertion failures that could occur when
6407 connecting to a busy hidden service, or connecting to a hidden
6408 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6411 o Minor features (client, SOCKS):
6412 - Add GroupWritable and WorldWritable options to unix-socket based
6413 SocksPort and ControlPort options. These options apply to a single
6414 socket, and override {Control,Socks}SocketsGroupWritable. Closes
6416 - Relax the validation done to hostnames in SOCKS5 requests, and
6417 allow a single trailing '.' to cope with clients that pass FQDNs
6418 using that syntax to explicitly indicate that the domain name is
6419 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
6420 - Relax the validation of hostnames in SOCKS5 requests, allowing the
6421 character '_' to appear, in order to cope with domains observed in
6422 the wild that are serving non-RFC compliant records. Resolves
6425 o Minor features (client-side privacy):
6426 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
6427 lifespan when IsolateSOCKSAuth and streams with SOCKS
6428 authentication are attached to the circuit. This allows
6429 applications like TorBrowser to manage circuit lifetime on their
6430 own. Implements feature 15482.
6431 - When logging malformed hostnames from SOCKS5 requests, respect
6432 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
6434 o Minor features (clock-jump tolerance):
6435 - Recover better when our clock jumps back many hours, like might
6436 happen for Tails or Whonix users who start with a very wrong
6437 hardware clock, use Tor to discover a more accurate time, and then
6438 fix their clock. Resolves part of ticket 8766.
6440 o Minor features (command-line interface):
6441 - Make --hash-password imply --hush to prevent unnecessary noise.
6442 Closes ticket 15542. Patch from "cypherpunks".
6443 - Print a warning whenever we find a relative file path being used
6444 as torrc option. Resolves issue 14018.
6446 o Minor features (compilation):
6447 - Give a warning as early as possible when trying to build with an
6448 unsupported OpenSSL version. Closes ticket 16901.
6449 - Use C99 variadic macros when the compiler is not GCC. This avoids
6450 failing compilations on MSVC, and fixes a log-file-based race
6451 condition in our old workarounds. Original patch from Gisle Vanem.
6453 o Minor features (control protocol):
6454 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
6455 the control protocol. Resolves ticket 15358.
6457 o Minor features (controller):
6458 - Add DirAuthority lines for default directory authorities to the
6459 output of the "GETINFO config/defaults" command if not already
6460 present. Implements ticket 14840.
6461 - Controllers can now use "GETINFO hs/client/desc/id/..." to
6462 retrieve items from the client's hidden service descriptor cache.
6463 Closes ticket 14845.
6464 - Implement a new controller command "GETINFO status/fresh-relay-
6465 descs" to fetch a descriptor/extrainfo pair that was generated on
6466 demand just for the controller's use. Implements ticket 14784.
6468 o Minor features (directory authorities):
6469 - Directory authorities no longer vote against the "Fast", "Stable",
6470 and "HSDir" flags just because they were going to vote against
6471 "Running": if the consensus turns out to be that the router was
6472 running, then the authority's vote should count. Patch from Peter
6473 Retzlaff; closes issue 8712.
6475 o Minor features (directory authorities, security, also in 0.2.6.9):
6476 - The HSDir flag given by authorities now requires the Stable flag.
6477 For the current network, this results in going from 2887 to 2806
6478 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6479 attack by raising the effort for a relay to become Stable to
6480 require at the very least 7 days, while maintaining the 96 hours
6481 uptime requirement for HSDir. Implements ticket 8243.
6483 o Minor features (DoS-resistance):
6484 - Make it harder for attackers to overload hidden services with
6485 introductions, by blocking multiple introduction requests on the
6486 same circuit. Resolves ticket 15515.
6488 o Minor features (geoip):
6489 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
6492 o Minor features (hidden services):
6493 - Add the new options "HiddenServiceMaxStreams" and
6494 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
6495 limit the maximum number of simultaneous streams per circuit, and
6496 optionally tear down the circuit when the limit is exceeded. Part
6498 - Client now uses an introduction point failure cache to know when
6499 to fetch or keep a descriptor in their cache. Previously, failures
6500 were recorded implicitly, but not explicitly remembered. Closes
6502 - Relays need to have the Fast flag to get the HSDir flag. As this
6503 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
6504 drop. This change should make some attacks against the hidden
6505 service directory system harder. Fixes ticket 15963.
6506 - Turn on hidden service statistics collection by setting the torrc
6507 option HiddenServiceStatistics to "1" by default. (This keeps
6508 track only of the fraction of traffic used by hidden services, and
6509 the total number of hidden services in existence.) Closes
6511 - To avoid leaking HS popularity, don't cycle the introduction point
6512 when we've handled a fixed number of INTRODUCE2 cells but instead
6513 cycle it when a random number of introductions is reached, thus
6514 making it more difficult for an attacker to find out the amount of
6515 clients that have used the introduction point for a specific HS.
6516 Closes ticket 15745.
6518 o Minor features (logging):
6519 - Include the Tor version in all LD_BUG log messages, since people
6520 tend to cut and paste those into the bugtracker. Implements
6523 o Minor features (pluggable transports):
6524 - When launching managed pluggable transports on Linux systems,
6525 attempt to have the kernel deliver a SIGTERM on tor exit if the
6526 pluggable transport process is still running. Resolves
6528 - When launching managed pluggable transports, setup a valid open
6529 stdin in the child process that can be used to detect if tor has
6530 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
6531 can be used by implementations to detect this new behavior.
6532 Resolves ticket 15435.
6534 o Minor bugfixes (torrc exit policies):
6535 - In each instance above, usage advice is provided to avoid the
6536 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
6537 16069; bugfix on 0.2.4.7-alpha.
6538 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
6539 produce IPv6 wildcard addresses. Previously they would produce
6540 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
6541 of bug 16069; bugfix on 0.2.4.7-alpha.
6542 - When parsing torrc ExitPolicies, we now issue an info-level
6543 message when expanding an "accept/reject *" line to include both
6544 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
6545 - When parsing torrc ExitPolicies, we now warn for a number of cases
6546 where the user's intent is likely to differ from Tor's actual
6547 behavior. These include: using an IPv4 address with an accept6 or
6548 reject6 line; using "private" on an accept6 or reject6 line; and
6549 including any ExitPolicy lines after accept *:* or reject *:*.
6550 Related to ticket 16069.
6552 o Minor bugfixes (command-line interface):
6553 - When "--quiet" is provided along with "--validate-config", do not
6554 write anything to stdout on success. Fixes bug 14994; bugfix
6556 - When complaining about bad arguments to "--dump-config", use
6558 - Print usage information for --dump-config when it is used without
6559 an argument. Also, fix the error message to use different wording
6560 and add newline at the end. Fixes bug 15541; bugfix
6563 o Minor bugfixes (compilation):
6564 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
6565 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
6566 - Repair compilation with the most recent (unreleased, alpha)
6567 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
6569 o Minor bugfixes (compilation, also in 0.2.6.9):
6570 - Build with --enable-systemd correctly when libsystemd is
6571 installed, but systemd is not. Fixes bug 16164; bugfix on
6572 0.2.6.3-alpha. Patch from Peter Palfrader.
6574 o Minor bugfixes (configuration, unit tests):
6575 - Only add the default fallback directories when the DirAuthorities,
6576 AlternateDirAuthority, and FallbackDir directory config options
6577 are set to their defaults. The default fallback directory list is
6578 currently empty, this fix will only change tor's behavior when it
6579 has default fallback directories. Includes unit tests for
6580 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
6581 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
6583 o Minor bugfixes (controller):
6584 - Add the descriptor ID in each HS_DESC control event. It was
6585 missing, but specified in control-spec.txt. Fixes bug 15881;
6586 bugfix on 0.2.5.2-alpha.
6588 o Minor bugfixes (correctness):
6589 - For correctness, avoid modifying a constant string in
6590 handle_control_postdescriptor. Fixes bug 15546; bugfix
6592 - Remove side-effects from tor_assert() calls. This was harmless,
6593 because we never disable assertions, but it is bad style and
6594 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
6596 - When calling channel_free_list(), avoid calling smartlist_remove()
6597 while inside a FOREACH loop. This partially reverts commit
6598 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
6599 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
6601 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
6602 - Check for failures from crypto_early_init, and refuse to continue.
6603 A previous typo meant that we could keep going with an
6604 uninitialized crypto library, and would have OpenSSL initialize
6605 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6606 when implementing ticket 4900. Patch by "teor".
6608 o Minor bugfixes (hidden service):
6609 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6610 a client authorized hidden service. Fixes bug 15823; bugfix
6612 - Remove an extraneous newline character from the end of hidden
6613 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
6615 o Minor bugfixes (Linux seccomp2 sandbox):
6616 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
6617 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
6618 - Allow bridge authorities to run correctly under the seccomp2
6619 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
6620 - Add the "hidserv-stats" filename to our sandbox filter for the
6621 HiddenServiceStatistics option to work properly. Fixes bug 17354;
6622 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
6624 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
6625 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6626 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6627 on 0.2.6.3-alpha. Patch from "teor".
6629 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
6630 - Allow systemd connections to work with the Linux seccomp2 sandbox
6631 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6633 - Fix sandboxing to work when running as a relay, by allowing the
6634 renaming of secret_id_key, and allowing the eventfd2 and futex
6635 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
6638 o Minor bugfixes (logging):
6639 - When building Tor under Clang, do not include an extra set of
6640 parentheses in log messages that include function names. Fixes bug
6641 15269; bugfix on every released version of Tor when compiled with
6642 recent enough Clang.
6644 o Minor bugfixes (network):
6645 - When attempting to use fallback technique for network interface
6646 lookup, disregard loopback and multicast addresses since they are
6647 unsuitable for public communications.
6649 o Minor bugfixes (open file limit):
6650 - Fix set_max_file_descriptors() to set by default the max open file
6651 limit to the current limit when setrlimit() fails. Fixes bug
6652 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
6654 o Minor bugfixes (portability):
6655 - Check correctly for Windows socket errors in the workqueue
6656 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
6657 - Try harder to normalize the exit status of the Tor process to the
6658 standard-provided range. Fixes bug 16975; bugfix on every version
6660 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
6661 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
6663 o Minor bugfixes (relay):
6664 - Ensure that worker threads actually exit when a fatal error or
6665 shutdown is indicated. This fix doesn't currently affect the
6666 behavior of Tor, because Tor workers never indicates fatal error
6667 or shutdown except in the unit tests. Fixes bug 16868; bugfix
6669 - Fix a rarely-encountered memory leak when failing to initialize
6670 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
6672 - Unblock threads before releasing the work queue mutex to ensure
6673 predictable scheduling behavior. Fixes bug 16644; bugfix
6676 o Minor bugfixes (security, exit policies):
6677 - ExitPolicyRejectPrivate now also rejects the relay's published
6678 IPv6 address (if any), and any publicly routable IPv4 or IPv6
6679 addresses on any local interfaces. ticket 17027. Patch by "teor".
6680 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
6682 o Minor bugfixes (statistics):
6683 - Disregard the ConnDirectionStatistics torrc options when Tor is
6684 not a relay since in that mode of operation no sensible data is
6685 being collected and because Tor might run into measurement hiccups
6686 when running as a client for some time, then becoming a relay.
6687 Fixes bug 15604; bugfix on 0.2.2.35.
6689 o Minor bugfixes (systemd):
6690 - Tor's systemd unit file no longer contains extraneous spaces.
6691 These spaces would sometimes confuse tools like deb-systemd-
6692 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
6694 o Minor bugfixes (test networks):
6695 - When self-testing reachability, use ExtendAllowPrivateAddresses to
6696 determine if local/private addresses imply reachability. The
6697 previous fix used TestingTorNetwork, which implies
6698 ExtendAllowPrivateAddresses, but this excluded rare configurations
6699 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
6700 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
6701 issue discovered by CJ Ess.
6703 o Minor bugfixes (tests, also in 0.2.6.9):
6704 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6705 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6707 o Code simplification and refactoring:
6708 - Change the function that's called when we need to retry all
6709 downloads so that it only reschedules the downloads to happen
6710 immediately, rather than launching them all at once itself. This
6711 further simplifies Tor's callgraph.
6712 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
6713 to ensure they remain consistent and visible everywhere.
6714 - Move some format-parsing functions out of crypto.c and
6715 crypto_curve25519.c into crypto_format.c and/or util_format.c.
6716 - Move the client-only parts of init_keys() into a separate
6717 function. Closes ticket 16763.
6718 - Move the hacky fallback code out of get_interface_address6() into
6719 separate function and get it covered with unit-tests. Resolves
6721 - Refactor hidden service client-side cache lookup to intelligently
6722 report its various failure cases, and disentangle failure cases
6723 involving a lack of introduction points. Closes ticket 14391.
6724 - Remove some vestigial workarounds for the MSVC6 compiler. We
6725 haven't supported that in ages.
6726 - Remove the unused "nulterminate" argument from buf_pullup().
6727 - Simplify the microdesc_free() implementation so that it no longer
6728 appears (to code analysis tools) to potentially invoke a huge
6729 suite of other microdesc functions.
6730 - Simply the control graph further by deferring the inner body of
6731 directory_all_unreachable() into a callback. Closes ticket 16762.
6732 - The link authentication code has been refactored for better
6733 testability and reliability. It now uses code generated with the
6734 "trunnel" binary encoding generator, to reduce the risk of bugs
6735 due to programmer error. Done as part of ticket 12498.
6736 - Treat the loss of an owning controller as equivalent to a SIGTERM
6737 signal. This removes a tiny amount of duplicated code, and
6738 simplifies our callgraph. Closes ticket 16788.
6739 - Use our own Base64 encoder instead of OpenSSL's, to allow more
6740 control over the output. Part of ticket 15652.
6741 - When generating an event to send to the controller, we no longer
6742 put the event over the network immediately. Instead, we queue
6743 these events, and use a Libevent callback to deliver them. This
6744 change simplifies Tor's callgraph by reducing the number of
6745 functions from which all other Tor functions are reachable. Closes
6747 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
6748 that try to scan or compile every file on Unix won't decide that
6752 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
6753 - Improve the descriptions of statistics-related torrc options in
6754 the manpage to describe rationale and possible uses cases. Fixes
6756 - Improve the layout and formatting of ./configure --help messages.
6757 Closes ticket 15024. Patch from "cypherpunks".
6758 - Include a specific and (hopefully) accurate documentation of the
6759 torrc file's meta-format in doc/torrc_format.txt. This is mainly
6760 of interest to people writing programs to parse or generate torrc
6761 files. This document is not a commitment to long-term
6762 compatibility; some aspects of the current format are a bit
6763 ridiculous. Closes ticket 2325.
6764 - Include the TUNING document in our source tarball. It is referred
6765 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
6767 - Note that HiddenServicePorts can take a unix domain socket. Closes
6769 - Recommend a 40 GB example AccountingMax in torrc.sample rather
6770 than a 4 GB max. Closes ticket 16742.
6771 - Standardize on the term "server descriptor" in the manual page.
6772 Previously, we had used "router descriptor", "server descriptor",
6773 and "relay descriptor" interchangeably. Part of ticket 14987.
6774 - Advise users on how to configure separate IPv4 and IPv6 exit
6775 policies in the manpage and sample torrcs. Related to ticket 16069.
6776 - Fix an error in the manual page and comments for
6777 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
6778 required "ORPort connectivity". While this is true, it is in no
6779 way unique to the HSDir flag. Of all the flags, only HSDirs need a
6780 DirPort configured in order for the authorities to assign that
6781 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
6783 - Fix the usage message of tor-resolve(1) so that it no longer lists
6784 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
6787 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
6788 and always use the internal Base64 decoder. The internal decoder
6789 has been part of tor since 0.2.0.10-alpha, and no one should
6790 be using the OpenSSL one. Part of ticket 15652.
6791 - Remove the 'tor_strclear()' function; use memwipe() instead.
6792 Closes ticket 14922.
6793 - Remove the code that would try to aggressively flush controller
6794 connections while writing to them. This code was introduced in
6795 0.1.2.7-alpha, in order to keep output buffers from exceeding
6796 their limits. But there is no longer a maximum output buffer size,
6797 and flushing data in this way caused some undesirable recursions
6798 in our call graph. Closes ticket 16480.
6799 - The internal pure-C tor-fw-helper tool is now removed from the Tor
6800 distribution, in favor of the pure-Go clone available from
6801 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
6802 used by the C tor-fw-helper are not, in our opinion, very
6803 confidence- inspiring in their secure-programming techniques.
6804 Closes ticket 13338.
6807 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
6808 fingerprinting we now recommend pluggable transports; for forward-
6809 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
6810 - Remove the HidServDirectoryV2 option. Now all relays offer to
6811 store hidden service descriptors. Related to 16543.
6812 - Remove the VoteOnHidServDirectoriesV2 option, since all
6813 authorities have long set it to 1. Closes ticket 16543.
6814 - Remove the undocumented "--digests" command-line option. It
6815 complicated our build process, caused subtle build issues on
6816 multiple platforms, and is now redundant since we started
6817 including git version identifiers. Closes ticket 14742.
6818 - Tor no longer contains checks for ancient directory cache versions
6819 that didn't know about microdescriptors.
6820 - Tor no longer contains workarounds for stat files generated by
6821 super-old versions of Tor that didn't choose guards sensibly.
6824 - The test-network.sh script now supports performance testing.
6825 Requires corresponding chutney performance testing changes. Patch
6826 by "teor". Closes ticket 14175.
6827 - Add a new set of callgraph analysis scripts that use clang to
6828 produce a list of which Tor functions are reachable from which
6829 other Tor functions. We're planning to use these to help simplify
6830 our code structure by identifying illogical dependencies.
6831 - Add new 'test-full' and 'test-full-online' targets to run all
6832 tests, including integration tests with stem and chutney.
6833 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
6834 by-side in the same parent directory. Closes ticket 16903. Patch
6836 - Document use of coverity, clang static analyzer, and clang dynamic
6837 undefined behavior and address sanitizers in doc/HACKING. Include
6838 detailed usage instructions in the blacklist. Patch by "teor".
6839 Closes ticket 15817.
6840 - Make "bridges+hs" the default test network. This tests almost all
6841 tor functionality during make test-network, while allowing tests
6842 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
6843 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
6844 (chutney). Patches by "teor".
6845 - Make the test-workqueue test work on Windows by initializing the
6846 network before we begin.
6847 - New make target (make test-network-all) to run multiple applicable
6848 chutney test cases. Patch from Teor; closes 16953.
6849 - Now that OpenSSL has its own scrypt implementation, add an unit
6850 test that checks for interoperability between libscrypt_scrypt()
6851 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
6852 and rely on EVP_PBE_scrypt() whenever possible. Resolves
6854 - The link authentication protocol code now has extensive tests.
6855 - The relay descriptor signature testing code now has
6857 - The test_workqueue program now runs faster, and is enabled by
6858 default as a part of "make check".
6859 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
6860 functions in dns.c. Implements a portion of ticket 16831.
6861 - Use environment variables rather than autoconf substitutions to
6862 send variables from the build system to the test scripts. This
6863 change should be easier to maintain, and cause 'make distcheck' to
6864 work better than before. Fixes bug 17148.
6865 - When building Tor with testing coverage enabled, run Chutney tests
6866 (if any) using the 'tor-cov' coverage binary.
6867 - When running test-network or test-stem, check for the absence of
6868 stem/chutney before doing any build operations.
6869 - Add a test to verify that the compiler does not eliminate our
6870 memwipe() implementation. Closes ticket 15377.
6871 - Add make rule `check-changes` to verify the format of changes
6872 files. Closes ticket 15180.
6873 - Add unit tests for control_event_is_interesting(). Add a compile-
6874 time check that the number of events doesn't exceed the capacity
6875 of control_event_t.event_mask. Closes ticket 15431, checks for
6876 bugs similar to 13085. Patch by "teor".
6877 - Command-line argument tests moved to Stem. Resolves ticket 14806.
6878 - Integrate the ntor, backtrace, and zero-length keys tests into the
6879 automake test suite. Closes ticket 15344.
6880 - Remove assertions during builds to determine Tor's test coverage.
6881 We don't want to trigger these even in assertions, so including
6882 them artificially makes our branch coverage look worse than it is.
6883 This patch provides the new test-stem-full and coverage-html-full
6884 configure options. Implements ticket 15400.
6885 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6886 explicitly manage consensus flags in testing networks. Patch by
6887 "robgjansen", modified by "teor". Implements part of ticket 14882.
6888 - Check for matching value in server response in ntor_ref.py. Fixes
6889 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
6891 - Set the severity correctly when testing
6892 get_interface_addresses_ifaddrs() and
6893 get_interface_addresses_win32(), so that the tests fail gracefully
6894 instead of triggering an assertion. Fixes bug 15759; bugfix on
6895 0.2.6.3-alpha. Reported by Nicolas Derive.
6897 Changes in version 0.2.6.10 - 2015-07-12
6898 Tor version 0.2.6.10 fixes some significant stability and hidden
6899 service client bugs, bulletproofs the cryptography init process, and
6900 fixes a bug when using the sandbox code with some older versions of
6901 Linux. Everyone running an older version, especially an older version
6902 of 0.2.6, should upgrade.
6904 o Major bugfixes (hidden service clients, stability):
6905 - Stop refusing to store updated hidden service descriptors on a
6906 client. This reverts commit 9407040c59218 (which indeed fixed bug
6907 14219, but introduced a major hidden service reachability
6908 regression detailed in bug 16381). This is a temporary fix since
6909 we can live with the minor issue in bug 14219 (it just results in
6910 some load on the network) but the regression of 16381 is too much
6911 of a setback. First-round fix for bug 16381; bugfix
6914 o Major bugfixes (stability):
6915 - Stop crashing with an assertion failure when parsing certain kinds
6916 of malformed or truncated microdescriptors. Fixes bug 16400;
6917 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6918 by "cypherpunks_backup".
6919 - Stop random client-side assertion failures that could occur when
6920 connecting to a busy hidden service, or connecting to a hidden
6921 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6924 o Minor features (geoip):
6925 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
6926 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
6928 o Minor bugfixes (crypto error-handling):
6929 - Check for failures from crypto_early_init, and refuse to continue.
6930 A previous typo meant that we could keep going with an
6931 uninitialized crypto library, and would have OpenSSL initialize
6932 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6933 when implementing ticket 4900. Patch by "teor".
6935 o Minor bugfixes (Linux seccomp2 sandbox):
6936 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6937 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6938 on 0.2.6.3-alpha. Patch from "teor".
6941 Changes in version 0.2.6.9 - 2015-06-11
6942 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
6943 requirements for receiving an HSDir flag, and addresses some other small
6944 bugs in the systemd and sandbox code. Clients using circuit isolation
6945 should upgrade; all directory authorities should upgrade.
6947 o Major bugfixes (client-side privacy):
6948 - Properly separate out each SOCKSPort when applying stream
6949 isolation. The error occurred because each port's session group was
6950 being overwritten by a default value when the listener connection
6951 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
6954 o Minor feature (directory authorities, security):
6955 - The HSDir flag given by authorities now requires the Stable flag.
6956 For the current network, this results in going from 2887 to 2806
6957 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6958 attack by raising the effort for a relay to become Stable which
6959 takes at the very least 7 days to do so and by keeping the 96
6960 hours uptime requirement for HSDir. Implements ticket 8243.
6962 o Minor bugfixes (compilation):
6963 - Build with --enable-systemd correctly when libsystemd is
6964 installed, but systemd is not. Fixes bug 16164; bugfix on
6965 0.2.6.3-alpha. Patch from Peter Palfrader.
6967 o Minor bugfixes (Linux seccomp2 sandbox):
6968 - Fix sandboxing to work when running as a relaymby renaming of
6969 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
6970 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
6971 - Allow systemd connections to work with the Linux seccomp2 sandbox
6972 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6975 o Minor bugfixes (tests):
6976 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6977 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6980 Changes in version 0.2.6.8 - 2015-05-21
6981 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
6982 fixes an authority-side bug in assigning the HSDir flag. All directory
6983 authorities should upgrade.
6985 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
6986 - Revert commit that made directory authorities assign the HSDir
6987 flag to relays without a DirPort; this was bad because such relays
6988 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6991 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
6992 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6993 a client authorized hidden service. Fixes bug 15823; bugfix
6996 o Minor features (geoip):
6997 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6998 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7002 Changes in version 0.2.6.7 - 2015-04-06
7003 Tor 0.2.6.7 fixes two security issues that could be used by an
7004 attacker to crash hidden services, or crash clients visiting hidden
7005 services. Hidden services should upgrade as soon as possible; clients
7006 should upgrade whenever packages become available.
7008 This release also contains two simple improvements to make hidden
7009 services a bit less vulnerable to denial-of-service attacks.
7011 o Major bugfixes (security, hidden service):
7012 - Fix an issue that would allow a malicious client to trigger an
7013 assertion failure and halt a hidden service. Fixes bug 15600;
7014 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7015 - Fix a bug that could cause a client to crash with an assertion
7016 failure when parsing a malformed hidden service descriptor. Fixes
7017 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7019 o Minor features (DoS-resistance, hidden service):
7020 - Introduction points no longer allow multiple INTRODUCE1 cells to
7021 arrive on the same circuit. This should make it more expensive for
7022 attackers to overwhelm hidden services with introductions.
7023 Resolves ticket 15515.
7024 - Decrease the amount of reattempts that a hidden service performs
7025 when its rendezvous circuits fail. This reduces the computational
7026 cost for running a hidden service under heavy load. Resolves
7030 Changes in version 0.2.5.12 - 2015-04-06
7031 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7032 could be used by an attacker to crash hidden services, or crash clients
7033 visiting hidden services. Hidden services should upgrade as soon as
7034 possible; clients should upgrade whenever packages become available.
7036 This release also backports a simple improvement to make hidden
7037 services a bit less vulnerable to denial-of-service attacks.
7039 o Major bugfixes (security, hidden service):
7040 - Fix an issue that would allow a malicious client to trigger an
7041 assertion failure and halt a hidden service. Fixes bug 15600;
7042 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7043 - Fix a bug that could cause a client to crash with an assertion
7044 failure when parsing a malformed hidden service descriptor. Fixes
7045 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7047 o Minor features (DoS-resistance, hidden service):
7048 - Introduction points no longer allow multiple INTRODUCE1 cells to
7049 arrive on the same circuit. This should make it more expensive for
7050 attackers to overwhelm hidden services with introductions.
7051 Resolves ticket 15515.
7054 Changes in version 0.2.4.27 - 2015-04-06
7055 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7056 could be used by an attacker to crash hidden services, or crash clients
7057 visiting hidden services. Hidden services should upgrade as soon as
7058 possible; clients should upgrade whenever packages become available.
7060 This release also backports a simple improvement to make hidden
7061 services a bit less vulnerable to denial-of-service attacks.
7063 o Major bugfixes (security, hidden service):
7064 - Fix an issue that would allow a malicious client to trigger an
7065 assertion failure and halt a hidden service. Fixes bug 15600;
7066 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7067 - Fix a bug that could cause a client to crash with an assertion
7068 failure when parsing a malformed hidden service descriptor. Fixes
7069 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7071 o Minor features (DoS-resistance, hidden service):
7072 - Introduction points no longer allow multiple INTRODUCE1 cells to
7073 arrive on the same circuit. This should make it more expensive for
7074 attackers to overwhelm hidden services with introductions.
7075 Resolves ticket 15515.
7078 Changes in version 0.2.6.6 - 2015-03-24
7079 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7081 It adds numerous safety, security, correctness, and performance
7082 improvements. Client programs can be configured to use more kinds of
7083 sockets, AutomapHosts works better, the multithreading backend is
7084 improved, cell transmission is refactored, test coverage is much
7085 higher, more denial-of-service attacks are handled, guard selection is
7086 improved to handle long-term guards better, pluggable transports
7087 should work a bit better, and some annoying hidden service performance
7088 bugs should be addressed.
7090 o New compiler and system requirements:
7091 - Tor 0.2.6.x requires that your compiler support more of the C99
7092 language standard than before. The 'configure' script now detects
7093 whether your compiler supports C99 mid-block declarations and
7094 designated initializers. If it does not, Tor will not compile.
7096 We may revisit this requirement if it turns out that a significant
7097 number of people need to build Tor with compilers that don't
7098 bother implementing a 15-year-old standard. Closes ticket 13233.
7099 - Tor no longer supports systems without threading support. When we
7100 began working on Tor, there were several systems that didn't have
7101 threads, or where the thread support wasn't able to run the
7102 threads of a single process on multiple CPUs. That no longer
7103 holds: every system where Tor needs to run well now has threading
7104 support. Resolves ticket 12439.
7106 o Deprecated versions and removed support:
7107 - Tor relays older than 0.2.4.18-rc are no longer allowed to
7108 advertise themselves on the network. Closes ticket 13555.
7109 - Tor clients no longer support connecting to hidden services
7110 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
7111 option has been removed. (There shouldn't be any hidden services
7112 running these versions on the network.) Closes ticket 7803.
7114 o Directory authority changes:
7115 - The directory authority Faravahar has a new IP address. This
7116 closes ticket 14487.
7117 - Remove turtles as a directory authority.
7118 - Add longclaw as a new (v3) directory authority. This implements
7119 ticket 13296. This keeps the directory authority count at 9.
7121 o Major features (bridges):
7122 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
7123 transports if they are configured via the "TOR_PT_PROXY"
7124 environment variable. Implements proposal 232. Resolves
7127 o Major features (changed defaults):
7128 - Prevent relay operators from unintentionally running exits: When a
7129 relay is configured as an exit node, we now warn the user unless
7130 the "ExitRelay" option is set to 1. We warn even more loudly if
7131 the relay is configured with the default exit policy, since this
7132 can indicate accidental misconfiguration. Setting "ExitRelay 0"
7133 stops Tor from running as an exit relay. Closes ticket 10067.
7135 o Major features (client performance, hidden services):
7136 - Allow clients to use optimistic data when connecting to a hidden
7137 service, which should remove a round-trip from hidden service
7138 initialization. See proposal 181 for details. Implements
7141 o Major features (directory system):
7142 - Upon receiving an unparseable directory object, if its digest
7143 matches what we expected, then don't try to download it again.
7144 Previously, when we got a descriptor we didn't like, we would keep
7145 trying to download it over and over. Closes ticket 11243.
7146 - When downloading server- or microdescriptors from a directory
7147 server, we no longer launch multiple simultaneous requests to the
7148 same server. This reduces load on the directory servers,
7149 especially when directory guards are in use. Closes ticket 9969.
7150 - When downloading server- or microdescriptors over a tunneled
7151 connection, do not limit the length of our requests to what the
7152 Squid proxy is willing to handle. Part of ticket 9969.
7153 - Authorities can now vote on the correct digests and latest
7154 versions for different software packages. This allows packages
7155 that include Tor to use the Tor authority system as a way to get
7156 notified of updates and their correct digests. Implements proposal
7157 227. Closes ticket 10395.
7159 o Major features (guards):
7160 - Introduce the Guardfraction feature to improves load balancing on
7161 guard nodes. Specifically, it aims to reduce the traffic gap that
7162 guard nodes experience when they first get the Guard flag. This is
7163 a required step if we want to increase the guard lifetime to 9
7164 months or greater. Closes ticket 9321.
7166 o Major features (hidden services):
7167 - Make HS port scanning more difficult by immediately closing the
7168 circuit when a user attempts to connect to a nonexistent port.
7169 Closes ticket 13667.
7170 - Add a HiddenServiceStatistics option that allows Tor relays to
7171 gather and publish statistics about the overall size and volume of
7172 hidden service usage. Specifically, when this option is turned on,
7173 an HSDir will publish an approximate number of hidden services
7174 that have published descriptors to it the past 24 hours. Also, if
7175 a relay has acted as a hidden service rendezvous point, it will
7176 publish the approximate amount of rendezvous cells it has relayed
7177 the past 24 hours. The statistics themselves are obfuscated so
7178 that the exact values cannot be derived. For more details see
7179 proposal 238, "Better hidden service stats from Tor relays". This
7180 feature is currently disabled by default. Implements feature 13192.
7182 o Major features (performance):
7183 - Make the CPU worker implementation more efficient by avoiding the
7184 kernel and lengthening pipelines. The original implementation used
7185 sockets to transfer data from the main thread to the workers, and
7186 didn't allow any thread to be assigned more than a single piece of
7187 work at once. The new implementation avoids communications
7188 overhead by making requests in shared memory, avoiding kernel IO
7189 where possible, and keeping more requests in flight at once.
7190 Implements ticket 9682.
7192 o Major features (relay):
7193 - Raise the minimum acceptable configured bandwidth rate for bridges
7194 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
7195 20 KiB/sec.) Closes ticket 13822.
7196 - Complete revision of the code that relays use to decide which cell
7197 to send next. Formerly, we selected the best circuit to write on
7198 each channel, but we didn't select among channels in any
7199 sophisticated way. Now, we choose the best circuits globally from
7200 among those whose channels are ready to deliver traffic.
7202 This patch implements a new inter-cmux comparison API, a global
7203 high/low watermark mechanism and a global scheduler loop for
7204 transmission prioritization across all channels as well as among
7205 circuits on one channel. This schedule is currently tuned to
7206 (tolerantly) avoid making changes in network performance, but it
7207 should form the basis for major circuit performance increases in
7208 the future. Code by Andrea; tuning by Rob Jansen; implements
7211 o Major features (sample torrc):
7212 - Add a new, infrequently-changed "torrc.minimal". This file is
7213 similar to torrc.sample, but it will change as infrequently as
7214 possible, for the benefit of users whose systems prompt them for
7215 intervention whenever a default configuration file is changed.
7216 Making this change allows us to update torrc.sample to be a more
7217 generally useful "sample torrc".
7219 o Major features (security, unix domain sockets):
7220 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
7221 applications can reach Tor without having to create AF_INET or
7222 AF_INET6 sockets, meaning they can completely disable their
7223 ability to make non-Tor network connections. To create a socket of
7224 this type, use "SocksPort unix:/path/to/socket". Implements
7226 - Support mapping hidden service virtual ports to AF_UNIX sockets.
7227 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
7228 Implements ticket 11485.
7230 o Major bugfixes (client, automap):
7231 - Repair automapping with IPv6 addresses. This automapping should
7232 have worked previously, but one piece of debugging code that we
7233 inserted to detect a regression actually caused the regression to
7234 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
7235 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
7238 o Major bugfixes (crash, OSX, security):
7239 - Fix a remote denial-of-service opportunity caused by a bug in
7240 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7243 o Major bugfixes (directory authorities):
7244 - Do not assign the HSDir flag to relays if they are not Valid, or
7245 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
7247 o Major bugfixes (directory bandwidth performance):
7248 - Don't flush the zlib buffer aggressively when compressing
7249 directory information for clients. This should save about 7% of
7250 the bandwidth currently used for compressed descriptors and
7251 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
7253 o Major bugfixes (exit node stability):
7254 - Fix an assertion failure that could occur under high DNS load.
7255 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7256 diagnosed and fixed by "cypherpunks".
7258 o Major bugfixes (FreeBSD IPFW transparent proxy):
7259 - Fix address detection with FreeBSD transparent proxies, when
7260 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
7263 o Major bugfixes (hidden services):
7264 - When closing an introduction circuit that was opened in parallel
7265 with others, don't mark the introduction point as unreachable.
7266 Previously, the first successful connection to an introduction
7267 point would make the other introduction points get marked as
7268 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
7270 o Major bugfixes (Linux seccomp2 sandbox):
7271 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7272 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7273 0.2.5.1-alpha. Patch from "sanic".
7275 o Major bugfixes (mixed relay-client operation):
7276 - When running as a relay and client at the same time (not
7277 recommended), if we decide not to use a new guard because we want
7278 to retry older guards, only close the locally-originating circuits
7279 passing through that guard. Previously we would close all the
7280 circuits through that guard. Fixes bug 9819; bugfix on
7281 0.2.1.1-alpha. Reported by "skruffy".
7283 o Major bugfixes (pluggable transports):
7284 - Initialize the extended OR Port authentication cookie before
7285 launching pluggable transports. This prevents a race condition
7286 that occurred when server-side pluggable transports would cache the
7287 authentication cookie before it has been (re)generated. Fixes bug
7288 15240; bugfix on 0.2.5.1-alpha.
7290 o Major bugfixes (relay, stability, possible security):
7291 - Fix a bug that could lead to a relay crashing with an assertion
7292 failure if a buffer of exactly the wrong layout is passed to
7293 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7294 0.2.0.10-alpha. Patch from "cypherpunks".
7295 - Do not assert if the 'data' pointer on a buffer is advanced to the
7296 very end of the buffer; log a BUG message instead. Only assert if
7297 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7299 o Minor features (build):
7300 - New --disable-system-torrc compile-time option to prevent Tor from
7301 looking for the system-wide torrc or torrc-defaults files.
7302 Resolves ticket 13037.
7304 o Minor features (client):
7305 - Clients are now willing to send optimistic data (before they
7306 receive a 'connected' cell) to relays of any version. (Relays
7307 without support for optimistic data are no longer supported on the
7308 Tor network.) Resolves ticket 13153.
7310 o Minor features (client):
7311 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
7312 is enabled, reject requests with IP addresses as hostnames.
7313 Resolves ticket 13315.
7315 o Minor features (controller):
7316 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
7317 write an unscheduled heartbeat message to the log. Implements
7319 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
7320 events so controllers can observe circuit isolation inputs. Closes
7322 - ControlPort now supports the unix:/path/to/socket syntax as an
7323 alternative to the ControlSocket option, for consistency with
7324 SocksPort and HiddenServicePort. Closes ticket 14451.
7325 - New "GETINFO bw-event-cache" to get information about recent
7326 bandwidth events. Closes ticket 14128. Useful for controllers to
7327 get recent bandwidth history after the fix for ticket 13988.
7328 - Messages about problems in the bootstrap process now include
7329 information about the server we were trying to connect to when we
7330 noticed the problem. Closes ticket 15006.
7332 o Minor features (Denial of service resistance):
7333 - Count the total number of bytes used storing hidden service
7334 descriptors against the value of MaxMemInQueues. If we're low on
7335 memory, and more than 20% of our memory is used holding hidden
7336 service descriptors, free them until no more than 10% of our
7337 memory holds hidden service descriptors. Free the least recently
7338 fetched descriptors first. Resolves ticket 13806.
7339 - When we have recently been under memory pressure (over 3/4 of
7340 MaxMemInQueues is allocated), then allocate smaller zlib objects
7341 for small requests. Closes ticket 11791.
7343 o Minor features (directory authorities):
7344 - Don't list relays with a bandwidth estimate of 0 in the consensus.
7345 Implements a feature proposed during discussion of bug 13000.
7346 - In tor-gencert, report an error if the user provides the same
7347 argument more than once.
7348 - If a directory authority can't find a best consensus method in the
7349 votes that it holds, it now falls back to its favorite consensus
7350 method. Previously, it fell back to method 1. Neither of these is
7351 likely to get enough signatures, but "fall back to favorite"
7352 doesn't require us to maintain support an obsolete consensus
7353 method. Implements part of proposal 215.
7355 o Minor features (geoip):
7356 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7357 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7360 o Minor features (guard nodes):
7361 - Reduce the time delay before saving guard status to disk from 10
7362 minutes to 30 seconds (or from one hour to 10 minutes if
7363 AvoidDiskWrites is set). Closes ticket 12485.
7365 o Minor features (heartbeat):
7366 - On relays, report how many connections we negotiated using each
7367 version of the Tor link protocols. This information will let us
7368 know if removing support for very old versions of the Tor
7369 protocols is harming the network. Closes ticket 15212.
7371 o Minor features (hidden service):
7372 - Make Sybil attacks against hidden services harder by changing the
7373 minimum time required to get the HSDir flag from 25 hours up to 96
7374 hours. Addresses ticket 14149.
7375 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
7376 services to disable the anti-scanning feature introduced in
7377 0.2.6.2-alpha. With this option not set, a connection to an
7378 unlisted port closes the circuit. With this option set, only a
7379 RELAY_DONE cell is sent. Closes ticket 14084.
7380 - When re-enabling the network, don't try to build introduction
7381 circuits until we have successfully built a circuit. This makes
7382 hidden services come up faster when the network is re-enabled.
7383 Patch from "akwizgran". Closes ticket 13447.
7384 - When we fail to retrieve a hidden service descriptor, send the
7385 controller an "HS_DESC FAILED" controller event. Implements
7387 - New HiddenServiceDirGroupReadable option to cause hidden service
7388 directories and hostname files to be created group-readable. Patch
7389 from "anon", David Stainton, and "meejah". Closes ticket 11291.
7391 o Minor features (interface):
7392 - Implement "-f -" command-line option to read torrc configuration
7393 from standard input, if you don't want to store the torrc file in
7394 the file system. Implements feature 13865.
7396 o Minor features (logging):
7397 - Add a count of unique clients to the bridge heartbeat message.
7398 Resolves ticket 6852.
7399 - Suppress "router info incompatible with extra info" message when
7400 reading extrainfo documents from cache. (This message got loud
7401 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
7403 - Elevate hidden service authorized-client message from DEBUG to
7404 INFO. Closes ticket 14015.
7405 - On Unix-like systems, you can now use named pipes as the target of
7406 the Log option, and other options that try to append to files.
7407 Closes ticket 12061. Patch from "carlo von lynX".
7408 - When opening a log file at startup, send it every log message that
7409 we generated between startup and opening it. Previously, log
7410 messages that were generated before opening the log file were only
7411 logged to stdout. Closes ticket 6938.
7412 - Add a TruncateLogFile option to overwrite logs instead of
7413 appending to them. Closes ticket 5583.
7414 - Quiet some log messages in the heartbeat and at startup. Closes
7417 o Minor features (portability, Solaris):
7418 - Threads are no longer disabled by default on Solaris; we believe
7419 that the versions of Solaris with broken threading support are all
7420 obsolete by now. Resolves ticket 9495.
7422 o Minor features (relay):
7423 - Re-check our address after we detect a changed IP address from
7424 getsockname(). This ensures that the controller command "GETINFO
7425 address" will report the correct value. Resolves ticket 11582.
7427 - A new AccountingRule option lets Relays set whether they'd like
7428 AccountingMax to be applied separately to inbound and outbound
7429 traffic, or applied to the sum of inbound and outbound traffic.
7430 Resolves ticket 961. Patch by "chobe".
7431 - When identity keypair is generated for first time, log a
7432 congratulatory message that links to the new relay lifecycle
7433 document. Implements feature 10427.
7435 o Minor features (security, memory wiping):
7436 - Ensure we securely wipe keys from memory after
7437 crypto_digest_get_digest and init_curve25519_keypair_from_file
7438 have finished using them. Resolves ticket 13477.
7440 o Minor features (security, out-of-memory handling):
7441 - When handling an out-of-memory condition, allocate less memory for
7442 temporary data structures. Fixes issue 10115.
7443 - When handling an out-of-memory condition, consider more types of
7444 buffers, including those on directory connections, and zlib
7445 buffers. Resolves ticket 11792.
7447 o Minor features (stability):
7448 - Add assertions in our hash-table iteration code to check for
7449 corrupted values that could cause infinite loops. Closes
7452 o Minor features (systemd):
7453 - Various improvements and modernizations in systemd hardening
7454 support. Closes ticket 13805. Patch from Craig Andrews.
7455 - Where supported, when running with systemd, report successful
7456 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
7457 - When running with systemd, support systemd watchdog messages. Part
7458 of ticket 11016. Patch by Michael Scherer.
7460 o Minor features (testing networks):
7461 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
7462 the "Exit" flag regardless of their uptime, bandwidth, or exit
7463 policy. TestingTorNetwork must be set for this option to have any
7464 effect. Previously, authorities would take up to 35 minutes to
7465 give nodes the Exit flag in a test network. Partially implements
7467 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
7468 and the default on a testing network to 2 minutes. Drop the
7469 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
7470 keep the default on a testing network at 30 seconds. This reduces
7471 HS bootstrap time to around 25 seconds. Also, change the default
7472 time in test-network.sh to match. Closes ticket 13401. Patch
7474 - Create TestingDirAuthVoteHSDir to correspond to
7475 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
7476 HSDir flag for the listed relays regardless of uptime or ORPort
7477 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
7478 Partial implementation for ticket 14067. Patch by "teor".
7480 o Minor features (tor2web mode):
7481 - Introduce the config option Tor2webRendezvousPoints, which allows
7482 clients in Tor2webMode to select a specific Rendezvous Point to be
7483 used in HS circuits. This might allow better performance for
7484 Tor2Web nodes. Implements ticket 12844.
7486 o Minor features (transparent proxy):
7487 - Update the transparent proxy option checks to allow for both ipfw
7488 and pf on OS X. Closes ticket 14002.
7489 - Use the correct option when using IPv6 with transparent proxy
7490 support on Linux. Resolves 13808. Patch by Francisco Blas
7493 o Minor features (validation):
7494 - Check all date/time values passed to tor_timegm and
7495 parse_rfc1123_time for validity, taking leap years into account.
7496 Improves HTTP header validation. Implemented with bug 13476.
7497 - In correct_tm(), limit the range of values returned by system
7498 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
7499 This means we don't have to deal with negative or too large dates,
7500 even if a clock is wrong. Otherwise we might fail to read a file
7501 written by us which includes such a date. Fixes bug 13476.
7502 - Stop allowing invalid address patterns like "*/24" that contain
7503 both a wildcard address and a bit prefix length. This affects all
7504 our address-range parsing code. Fixes bug 7484; bugfix
7507 o Minor bugfixes (bridge clients):
7508 - When configured to use a bridge without an identity digest (not
7509 recommended), avoid launching an extra channel to it when
7510 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
7512 o Minor bugfixes (bridges):
7513 - When DisableNetwork is set, do not launch pluggable transport
7514 plugins, and if any are running, terminate them. Fixes bug 13213;
7515 bugfix on 0.2.3.6-alpha.
7517 o Minor bugfixes (C correctness):
7518 - Fix several instances of possible integer overflow/underflow/NaN.
7519 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
7521 - In circuit_build_times_calculate_timeout() in circuitstats.c,
7522 avoid dividing by zero in the pareto calculations. This traps
7523 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
7525 - Fix an integer overflow in format_time_interval(). Fixes bug
7526 13393; bugfix on 0.2.0.10-alpha.
7527 - Set the correct day of year value when the system's localtime(_r)
7528 or gmtime(_r) functions fail to set struct tm. Not externally
7529 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
7530 - Avoid unlikely signed integer overflow in tor_timegm on systems
7531 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
7533 o Minor bugfixes (certificate handling):
7534 - If an authority operator accidentally makes a signing certificate
7535 with a future publication time, do not discard its real signing
7536 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
7537 - Remove any old authority certificates that have been superseded
7538 for at least two days. Previously, we would keep superseded
7539 certificates until they expired, if they were published close in
7540 time to the certificate that superseded them. Fixes bug 11454;
7541 bugfix on 0.2.1.8-alpha.
7543 o Minor bugfixes (client):
7544 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
7545 BadExit flag are not considered worthy candidates. Fixes bug
7546 13066; bugfix on 0.1.2.3-alpha.
7547 - Use the consensus schedule for downloading consensuses, and not
7548 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
7549 - Handle unsupported or malformed SOCKS5 requests properly by
7550 responding with the appropriate error message before closing the
7551 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
7553 o Minor bugfixes (client, automapping):
7554 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7555 no value follows the option. Fixes bug 14142; bugfix on
7556 0.2.4.7-alpha. Patch by "teor".
7557 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7558 14195; bugfix on 0.1.0.1-rc.
7559 - Prevent changes to other options from removing the wildcard value
7560 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
7562 - Allow MapAddress and AutomapHostsOnResolve to work together when
7563 an address is mapped into another address type (like .onion) that
7564 must be automapped at resolve time. Fixes bug 7555; bugfix
7567 o Minor bugfixes (client, bridges):
7568 - When we are using bridges and we had a network connectivity
7569 problem, only retry connecting to our currently configured
7570 bridges, not all bridges we know about and remember using. Fixes
7571 bug 14216; bugfix on 0.2.2.17-alpha.
7573 o Minor bugfixes (client, DNS):
7574 - Report the correct cached DNS expiration times on SOCKS port or in
7575 DNS replies. Previously, we would report everything as "never
7576 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
7577 - Avoid a small memory leak when we find a cached answer for a
7578 reverse DNS lookup in a client-side DNS cache. (Remember, client-
7579 side DNS caching is off by default, and is not recommended.) Fixes
7580 bug 14259; bugfix on 0.2.0.1-alpha.
7582 o Minor bugfixes (client, IPv6):
7583 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
7584 flag is not set; and not because the NoIPv4Traffic flag was set.
7585 Previously we'd looked at the NoIPv4Traffic flag for both types of
7586 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
7588 o Minor bugfixes (client, microdescriptors):
7589 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
7590 computing which microdescriptors to download. This keeps us from
7591 erroneous download behavior if two microdescriptor digests ever
7592 have the same first 160 bits. Fixes part of bug 13399; bugfix
7594 - Reset a router's status if its microdescriptor digest changes,
7595 even if the first 160 bits remain the same. Fixes part of bug
7596 13399; bugfix on 0.2.3.1-alpha.
7598 o Minor bugfixes (client, torrc):
7599 - Stop modifying the value of our DirReqStatistics torrc option just
7600 because we're not a bridge or relay. This bug was causing Tor
7601 Browser users to write "DirReqStatistics 0" in their torrc files
7602 as if they had chosen to change the config. Fixes bug 4244; bugfix
7604 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
7605 that our options have changed every time we SIGHUP. Fixes bug
7606 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
7608 o Minor bugfixes (compilation):
7609 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
7611 - Silence clang warnings under --enable-expensive-hardening,
7612 including implicit truncation of 64 bit values to 32 bit, const
7613 char assignment to self, tautological compare, and additional
7614 parentheses around equality tests. Fixes bug 13577; bugfix
7616 - Fix a clang warning about checking whether an address in the
7617 middle of a structure is NULL. Fixes bug 14001; bugfix
7619 - The address of an array in the middle of a structure will always
7620 be non-NULL. clang recognises this and complains. Disable the
7621 tautologous and redundant check to silence this warning. Fixes bug
7622 14001; bugfix on 0.2.1.2-alpha.
7623 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
7624 Addresses ticket 14188.
7625 - Build without warnings with the stock OpenSSL srtp.h header, which
7626 has a duplicate declaration of SSL_get_selected_srtp_profile().
7627 Fixes bug 14220; this is OpenSSL's bug, not ours.
7628 - Do not compile any code related to Tor2Web mode when Tor2Web mode
7629 is not enabled at compile time. Previously, this code was included
7630 in a disabled state. See discussion on ticket 12844.
7631 - Allow our configure script to build correctly with autoconf 2.62
7632 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
7633 - Improve the error message from ./configure to make it clear that
7634 when asciidoc has not been found, the user will have to either add
7635 --disable-asciidoc argument or install asciidoc. Resolves
7638 o Minor bugfixes (controller):
7639 - Report "down" in response to the "GETINFO entry-guards" command
7640 when relays are down with an unreachable_since value. Previously,
7641 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
7642 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
7643 14116; bugfix on 0.2.2.9-alpha.
7645 o Minor bugfixes (controller):
7646 - Return an error when the second or later arguments of the
7647 "setevents" controller command are invalid events. Previously we
7648 would return success while silently skipping invalid events. Fixes
7649 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
7651 o Minor bugfixes (directory authority):
7652 - Allow directory authorities to fetch more data from one another if
7653 they find themselves missing lots of votes. Previously, they had
7654 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7655 bugfix on 0.1.2.5-alpha.
7656 - Do not attempt to download extrainfo documents which we will be
7657 unable to validate with a matching server descriptor. Fixes bug
7658 13762; bugfix on 0.2.0.1-alpha.
7659 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
7660 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
7661 - Enlarge the buffer to read bwauth generated files to avoid an
7662 issue when parsing the file in dirserv_read_measured_bandwidths().
7663 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7664 - When running as a v3 directory authority, advertise that you serve
7665 extra-info documents so that clients who want them can find them
7666 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
7668 o Minor bugfixes (directory system):
7669 - Always believe that v3 directory authorities serve extra-info
7670 documents, whether they advertise "caches-extra-info" or not.
7671 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
7672 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
7673 Previously, directories offering BRIDGE_DIRINFO and some other
7674 flag (i.e. microdescriptors or extrainfo) would be ignored when
7675 looking for bridges. Partially fixes bug 13163; bugfix
7678 o Minor bugfixes (file handling):
7679 - Stop failing when key files are zero-length. Instead, generate new
7680 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
7681 on all versions of Tor. Patch by "teor".
7682 - Stop generating a fresh .old RSA onion key file when the .old file
7683 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
7684 - Avoid overwriting .old key files with empty key files.
7685 - Skip loading zero-length extrainfo store, router store, stats,
7686 state, and key files.
7687 - Avoid crashing when trying to reload a torrc specified as a
7688 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
7691 o Minor bugfixes (hidden services):
7692 - Close the introduction circuit when we have no more usable intro
7693 points, instead of waiting for it to time out. This also ensures
7694 that no follow-up HS descriptor fetch is triggered when the
7695 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
7696 - When fetching a hidden service descriptor for a down service that
7697 was recently up, do not keep refetching until we try the same
7698 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
7699 - Correctly send a controller event when we find that a rendezvous
7700 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
7701 - Pre-check directory permissions for new hidden-services to avoid
7702 at least one case of "Bug: Acting on config options left us in a
7703 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
7704 - When fetching hidden service descriptors, we now check not only
7705 for whether we got the hidden service we had in mind, but also
7706 whether we got the particular descriptors we wanted. This prevents
7707 a class of inefficient but annoying DoS attacks by hidden service
7708 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
7711 o Minor bugfixes (Linux seccomp2 sandbox):
7712 - Make transparent proxy support work along with the seccomp2
7713 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
7714 by Francisco Blas Izquierdo Riera.
7715 - Fix a memory leak in tor-resolve when running with the sandbox
7716 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
7717 - Allow glibc fatal errors to be sent to stderr before Tor exits.
7718 Previously, glibc would try to write them to /dev/tty, and the
7719 sandbox would trap the call and make Tor exit prematurely. Fixes
7720 bug 14759; bugfix on 0.2.5.1-alpha.
7722 o Minor bugfixes (logging):
7723 - Avoid crashing when there are more log domains than entries in
7724 domain_list. Bugfix on 0.2.3.1-alpha.
7725 - Downgrade warnings about RSA signature failures to info log level.
7726 Emit a warning when an extra info document is found incompatible
7727 with a corresponding router descriptor. Fixes bug 9812; bugfix
7729 - Make connection_ap_handshake_attach_circuit() log the circuit ID
7730 correctly. Fixes bug 13701; bugfix on 0.0.6.
7732 o Minor bugfixes (networking):
7733 - Check for orconns and use connection_or_close_for_error() rather
7734 than connection_mark_for_close() directly in the getsockopt()
7735 failure case of connection_handle_write_impl(). Fixes bug 11302;
7736 bugfix on 0.2.4.4-alpha.
7738 o Minor bugfixes (parsing):
7739 - Stop accepting milliseconds (or other junk) at the end of
7740 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
7741 - Support two-number and three-number version numbers correctly, in
7742 case we change the Tor versioning system in the future. Fixes bug
7743 13661; bugfix on 0.0.8pre1.
7745 o Minor bugfixes (portability):
7746 - Fix the ioctl()-based network interface lookup code so that it
7747 will work on systems that have variable-length struct ifreq, for
7749 - Use the correct datatype in the SipHash-2-4 function to prevent
7750 compilers from assuming any sort of alignment. Fixes bug 15436;
7751 bugfix on 0.2.5.3-alpha.
7753 o Minor bugfixes (preventative security, C safety):
7754 - When reading a hexadecimal, base-32, or base-64 encoded value from
7755 a string, always overwrite the whole output buffer. This prevents
7756 some bugs where we would look at (but fortunately, not reveal)
7757 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7759 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
7760 just the part that's used. This makes it harder for data leak bugs
7761 to occur in the event of other programming failures. Resolves
7764 o Minor bugfixes (relay):
7765 - When generating our family list, remove spaces from around the
7766 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
7767 - If our previous bandwidth estimate was 0 bytes, allow publishing a
7768 new relay descriptor immediately. Fixes bug 13000; bugfix
7771 o Minor bugfixes (shutdown):
7772 - When shutting down, always call event_del() on lingering read or
7773 write events before freeing them. Otherwise, we risk double-frees
7774 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
7777 o Minor bugfixes (small memory leaks):
7778 - Avoid leaking memory when using IPv6 virtual address mappings.
7779 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
7782 o Minor bugfixes (statistics):
7783 - Increase period over which bandwidth observations are aggregated
7784 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7786 o Minor bugfixes (systemd support):
7787 - Run correctly under systemd with the RunAsDaemon option set. Fixes
7788 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
7789 - Inform the systemd supervisor about more changes in the Tor
7790 process status. Implements part of ticket 14141. Patch from
7793 o Minor bugfixes (testing networks):
7794 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
7795 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
7796 - Stop using the default authorities in networks which provide both
7797 AlternateDirAuthority and AlternateBridgeAuthority. Partially
7798 fixes bug 13163; bugfix on 0.2.0.13-alpha.
7800 o Minor bugfixes (testing networks, fast startup):
7801 - Allow Tor to build circuits using a consensus with no exits. If
7802 the consensus has no exits (typical of a bootstrapping test
7803 network), allow Tor to build circuits once enough descriptors have
7804 been downloaded. This assists in bootstrapping a testing Tor
7805 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
7807 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
7808 header to directory servers. This allows us to obtain consensuses
7809 promptly when the consensus interval is very short. This assists
7810 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
7811 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
7812 - Stop assuming that private addresses are local when checking
7813 reachability in a TestingTorNetwork. Instead, when testing, assume
7814 all OR connections are remote. (This is necessary due to many test
7815 scenarios running all relays on localhost.) This assists in
7816 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
7817 0.1.0.1-rc. Patch by "teor".
7818 - Avoid building exit circuits from a consensus with no exits. Now
7819 thanks to our fix for 13718, we accept a no-exit network as not
7820 wholly lost, but we need to remember not to try to build exit
7821 circuits on it. Closes ticket 13814; patch by "teor".
7822 - Stop requiring exits to have non-zero bandwithcapacity in a
7823 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
7824 ignore exit bandwidthcapacity. This assists in bootstrapping a
7825 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
7826 on 0.2.0.3-alpha. Patch by "teor".
7827 - Add "internal" to some bootstrap statuses when no exits are
7828 available. If the consensus does not contain Exits, Tor will only
7829 build internal circuits. In this case, relevant statuses will
7830 contain the word "internal" as indicated in the Tor control-
7831 spec.txt. When bootstrap completes, Tor will be ready to build
7832 internal circuits. If a future consensus contains Exits, exit
7833 circuits may become available. Fixes part of bug 13718; bugfix on
7834 0.2.4.10-alpha. Patch by "teor".
7835 - Decrease minimum consensus interval to 10 seconds when
7836 TestingTorNetwork is set, or 5 seconds for the first consensus.
7837 Fix assumptions throughout the code that assume larger intervals.
7838 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
7840 - Avoid excluding guards from path building in minimal test
7841 networks, when we're in a test network and excluding guards would
7842 exclude all relays. This typically occurs in incredibly small tor
7843 networks, and those using "TestingAuthVoteGuard *". Fixes part of
7844 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
7846 o Minor bugfixes (testing):
7847 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
7848 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
7849 - Stop spawn test failures due to a race condition between the
7850 SIGCHLD handler updating the process status, and the test reading
7851 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
7852 - Avoid passing an extra backslash when creating a temporary
7853 directory for running the unit tests on Windows. Fixes bug 12392;
7854 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
7856 o Minor bugfixes (TLS):
7857 - Check more thoroughly throughout the TLS code for possible
7858 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
7860 o Minor bugfixes (transparent proxy):
7861 - Use getsockname, not getsockopt, to retrieve the address for a
7862 TPROXY-redirected connection. Fixes bug 13796; bugfix
7865 o Minor bugfixes (windows):
7866 - Remove code to special-case handling of NTE_BAD_KEYSET when
7867 acquiring windows CryptoAPI context. This error can't actually
7868 occur for the parameters we're providing. Fixes bug 10816; bugfix
7871 o Minor bugfixes (zlib):
7872 - Avoid truncating a zlib stream when trying to finalize it with an
7873 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
7875 o Code simplification and refactoring:
7876 - Change the entry_is_live() function to take named bitfield
7877 elements instead of an unnamed list of booleans. Closes
7879 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
7880 Resolves ticket 12205.
7881 - Use calloc and reallocarray functions instead of multiply-
7882 then-malloc. This makes it less likely for us to fall victim to an
7883 integer overflow attack when allocating. Resolves ticket 12855.
7884 - Use the standard macro name SIZE_MAX, instead of our
7886 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
7887 functions which take them as arguments. Replace 0 with NO_DIRINFO
7888 in a function call for clarity. Seeks to prevent future issues
7890 - Avoid 4 null pointer errors under clang static analysis by using
7891 tor_assert() to prove that the pointers aren't null. Fixes
7893 - Rework the API of policies_parse_exit_policy() to use a bitmask to
7894 represent parsing options, instead of a confusing mess of
7895 booleans. Resolves ticket 8197.
7896 - Introduce a helper function to parse ExitPolicy in
7897 or_options_t structure.
7898 - Move fields related to isolating and configuring client ports into
7899 a shared structure. Previously, they were duplicated across
7900 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
7901 to copy them correctly had been the cause of at least one bug in
7902 the past. Closes ticket 8546.
7903 - Refactor the get_interface_addresses_raw() doom-function into
7904 multiple smaller and simpler subfunctions. Cover the resulting
7905 subfunctions with unit-tests. Fixes a significant portion of
7907 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
7908 only for version <= 0.2.2.24 which is now deprecated. Closes
7910 - Remove a test for a long-defunct broken version-one
7912 - Refactor main loop to extract the 'loop' part. This makes it
7913 easier to run Tor under Shadow. Closes ticket 15176.
7914 - Stop using can_complete_circuits as a global variable; access it
7915 with a function instead.
7916 - Avoid using operators directly as macro arguments: this lets us
7917 apply coccinelle transformations to our codebase more directly.
7918 Closes ticket 13172.
7919 - Combine the functions used to parse ClientTransportPlugin and
7920 ServerTransportPlugin into a single function. Closes ticket 6456.
7921 - Add inline functions and convenience macros for inspecting channel
7922 state. Refactor the code to use convenience macros instead of
7923 checking channel state directly. Fixes issue 7356.
7924 - Document all members of was_router_added_t and rename
7925 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
7926 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
7927 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
7928 constant instead of hardcoded value. Fixes issue 13840.
7929 - Refactor our generic strmap and digestmap types into a single
7930 implementation, so that we can add a new digest256map
7934 - Add a doc/TUNING document with tips for handling large numbers of
7935 TCP connections when running busy Tor relay. Update the warning
7936 message to point to this file when running out of sockets
7937 operating system is allowing to use simultaneously. Resolves
7939 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
7940 for writing the OpenBSD-specific tips. Resolves ticket 13702.
7941 - Make the tor-resolve documentation match its help string and its
7942 options. Resolves part of ticket 14325.
7943 - Log a more useful error message from tor-resolve when failing to
7944 look up a hidden service address. Resolves part of ticket 14325.
7945 - Document the bridge-authority-only 'networkstatus-bridges' file.
7946 Closes ticket 13713; patch from "tom".
7947 - Fix typo in PredictedPortsRelevanceTime option description in
7948 manpage. Resolves issue 13707.
7949 - Stop suggesting that users specify relays by nickname: it isn't a
7950 good idea. Also, properly cross-reference how to specify relays in
7951 all parts of manual documenting options that take a list of
7952 relays. Closes ticket 13381.
7953 - Clarify the HiddenServiceDir option description in manpage to make
7954 it clear that relative paths are taken with respect to the current
7955 working directory. Also clarify that this behavior is not
7956 guaranteed to remain indefinitely. Fixes issue 13913.
7958 o Distribution (systemd):
7959 - systemd unit file: only allow tor to write to /var/lib/tor and
7960 /var/log/tor. The rest of the filesystem is accessible for reading
7961 only. Patch by intrigeri; resolves ticket 12751.
7962 - systemd unit file: ensure that the process and all its children
7963 can never gain new privileges. Patch by intrigeri; resolves
7965 - systemd unit file: set up /var/run/tor as writable for the Tor
7966 service. Patch by intrigeri; resolves ticket 13196.
7968 o Downgraded warnings:
7969 - Don't warn when we've attempted to contact a relay using the wrong
7970 ntor onion key. Closes ticket 9635.
7973 - Remove some lingering dead code that once supported mempools.
7974 Mempools were disabled by default in 0.2.5, and removed entirely
7975 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
7978 o Removed features (directory authorities):
7979 - Remove code that prevented authorities from listing Tor relays
7980 affected by CVE-2011-2769 as guards. These relays are already
7981 rejected altogether due to the minimum version requirement of
7982 0.2.3.16-alpha. Closes ticket 13152.
7983 - The "AuthDirRejectUnlisted" option no longer has any effect, as
7984 the fingerprints file (approved-routers) has been deprecated.
7985 - Directory authorities do not support being Naming dirauths anymore.
7986 The "NamingAuthoritativeDir" config option is now obsolete.
7987 - Directory authorities do not support giving out the BadDirectory
7989 - Directory authorities no longer advertise or support consensus
7990 methods 1 through 12 inclusive. These consensus methods were
7991 obsolete and/or insecure: maintaining the ability to support them
7992 served no good purpose. Implements part of proposal 215; closes
7996 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
7997 longer silently accepted as an alias for "ExitNodes".
7998 - The --enable-mempool and --enable-buf-freelists options, which
7999 were originally created to work around bad malloc implementations,
8000 no longer exist. They were off-by-default in 0.2.5. Closes
8002 - We no longer remind the user about configuration options that have
8003 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
8004 - Remove our old, non-weighted bandwidth-based node selection code.
8005 Previously, we used it as a fallback when we couldn't perform
8006 weighted bandwidth-based node selection. But that would only
8007 happen in the cases where we had no consensus, or when we had a
8008 consensus generated by buggy or ancient directory authorities. In
8009 either case, it's better to use the more modern, better maintained
8010 algorithm, with reasonable defaults for the weights. Closes
8012 - Remove the --disable-curve25519 configure option. Relays and
8013 clients now are required to support curve25519 and the
8015 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
8016 used to be deprecated synonyms for "StrictNodes", are now marked
8017 obsolete. Resolves ticket 12226.
8018 - Clients don't understand the BadDirectory flag in the consensus
8019 anymore, and ignore it.
8021 o Removed platform support:
8022 - We no longer include special code to build on Windows CE; as far
8023 as we know, nobody has used Tor on Windows CE in a very long time.
8024 Closes ticket 11446.
8026 o Testing (test-network.sh):
8027 - Stop using "echo -n", as some shells' built-in echo doesn't
8028 support "-n". Instead, use "/bin/echo -n". Partially fixes
8030 - Stop an apparent test-network hang when used with make -j2. Fixes
8032 - Add a --delay option to test-network.sh, which configures the
8033 delay before the chutney network tests for data transmission.
8034 Partially implements ticket 13161.
8037 - Test that tor does not fail when key files are zero-length. Check
8038 that tor generates new keys, and overwrites the empty key files.
8039 - Test that tor generates new keys when keys are missing
8040 (existing behavior).
8041 - Test that tor does not overwrite key files that already contain
8042 data (existing behavior). Tests bug 13111. Patch by "teor".
8043 - New "make test-stem" target to run stem integration tests.
8044 Requires that the "STEM_SOURCE_DIR" environment variable be set.
8045 Closes ticket 14107.
8046 - Make the test_cmdline_args.py script work correctly on Windows.
8047 Patch from Gisle Vanem.
8048 - Move the slower unit tests into a new "./src/test/test-slow"
8049 binary that can be run independently of the other tests. Closes
8051 - New tests for many parts of channel, relay, and circuitmux
8052 functionality. Code by Andrea; part of 9262.
8053 - New tests for parse_transport_line(). Part of ticket 6456.
8054 - In the unit tests, use chgrp() to change the group of the unit
8055 test temporary directory to the current user, so that the sticky
8056 bit doesn't interfere with tests that check directory groups.
8058 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8060 - Refactor the function that chooses guard nodes so that it can more
8061 easily be tested; write some tests for it.
8062 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
8063 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
8064 - Create unit tests for format_time_interval(). With bug 13393.
8065 - Add unit tests for tor_timegm signed overflow, tor_timegm and
8066 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
8067 tests (visible) fixes in bug 13476.
8068 - Add a "coverage-html" make target to generate HTML-visualized
8069 coverage results when building with --enable-coverage. (Requires
8070 lcov.) Patch from Kevin Murray.
8071 - Enable the backtrace handler (where supported) when running the
8073 - Revise all unit tests that used the legacy test_* macros to
8074 instead use the recommended tt_* macros. This patch was generated
8075 with coccinelle, to avoid manual errors. Closes ticket 13119.
8077 Changes in version 0.2.5.11 - 2015-03-17
8078 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
8080 It backports several bugfixes from the 0.2.6 branch, including a
8081 couple of medium-level security fixes for relays and exit nodes.
8082 It also updates the list of directory authorities.
8084 o Directory authority changes:
8085 - Remove turtles as a directory authority.
8086 - Add longclaw as a new (v3) directory authority. This implements
8087 ticket 13296. This keeps the directory authority count at 9.
8088 - The directory authority Faravahar has a new IP address. This
8089 closes ticket 14487.
8091 o Major bugfixes (crash, OSX, security):
8092 - Fix a remote denial-of-service opportunity caused by a bug in
8093 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8096 o Major bugfixes (relay, stability, possible security):
8097 - Fix a bug that could lead to a relay crashing with an assertion
8098 failure if a buffer of exactly the wrong layout was passed to
8099 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8100 0.2.0.10-alpha. Patch from 'cypherpunks'.
8101 - Do not assert if the 'data' pointer on a buffer is advanced to the
8102 very end of the buffer; log a BUG message instead. Only assert if
8103 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8105 o Major bugfixes (exit node stability):
8106 - Fix an assertion failure that could occur under high DNS load.
8107 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8108 diagnosed and fixed by "cypherpunks".
8110 o Major bugfixes (Linux seccomp2 sandbox):
8111 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8112 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8113 0.2.5.1-alpha. Patch from "sanic".
8115 o Minor features (controller):
8116 - New "GETINFO bw-event-cache" to get information about recent
8117 bandwidth events. Closes ticket 14128. Useful for controllers to
8118 get recent bandwidth history after the fix for ticket 13988.
8120 o Minor features (geoip):
8121 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8122 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8125 o Minor bugfixes (client, automapping):
8126 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8127 no value follows the option. Fixes bug 14142; bugfix on
8128 0.2.4.7-alpha. Patch by "teor".
8129 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8130 14195; bugfix on 0.1.0.1-rc.
8132 o Minor bugfixes (compilation):
8133 - Build without warnings with the stock OpenSSL srtp.h header, which
8134 has a duplicate declaration of SSL_get_selected_srtp_profile().
8135 Fixes bug 14220; this is OpenSSL's bug, not ours.
8137 o Minor bugfixes (directory authority):
8138 - Allow directory authorities to fetch more data from one another if
8139 they find themselves missing lots of votes. Previously, they had
8140 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8141 bugfix on 0.1.2.5-alpha.
8142 - Enlarge the buffer to read bwauth generated files to avoid an
8143 issue when parsing the file in dirserv_read_measured_bandwidths().
8144 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8146 o Minor bugfixes (statistics):
8147 - Increase period over which bandwidth observations are aggregated
8148 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8150 o Minor bugfixes (preventative security, C safety):
8151 - When reading a hexadecimal, base-32, or base-64 encoded value from
8152 a string, always overwrite the whole output buffer. This prevents
8153 some bugs where we would look at (but fortunately, not reveal)
8154 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8158 Changes in version 0.2.4.26 - 2015-03-17
8159 Tor 0.2.4.26 includes an updated list of directory authorities. It
8160 also backports a couple of stability and security bugfixes from 0.2.5
8163 o Directory authority changes:
8164 - Remove turtles as a directory authority.
8165 - Add longclaw as a new (v3) directory authority. This implements
8166 ticket 13296. This keeps the directory authority count at 9.
8167 - The directory authority Faravahar has a new IP address. This
8168 closes ticket 14487.
8170 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
8171 - Fix an assertion failure that could occur under high DNS load.
8172 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8173 diagnosed and fixed by "cypherpunks".
8175 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
8176 - Fix a bug that could lead to a relay crashing with an assertion
8177 failure if a buffer of exactly the wrong layout was passed to
8178 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8179 0.2.0.10-alpha. Patch from 'cypherpunks'.
8180 - Do not assert if the 'data' pointer on a buffer is advanced to the
8181 very end of the buffer; log a BUG message instead. Only assert if
8182 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8184 o Minor features (geoip):
8185 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8186 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8189 Changes in version 0.2.5.10 - 2014-10-24
8190 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
8192 It adds several new security features, including improved
8193 denial-of-service resistance for relays, new compiler hardening
8194 options, and a system-call sandbox for hardened installations on Linux
8195 (requires seccomp2). The controller protocol has several new features,
8196 resolving IPv6 addresses should work better than before, and relays
8197 should be a little more CPU-efficient. We've added support for more
8198 OpenBSD and FreeBSD transparent proxy types. We've improved the build
8199 system and testing infrastructure to allow unit testing of more parts
8200 of the Tor codebase. Finally, we've addressed several nagging pluggable
8201 transport usability issues, and included numerous other small bugfixes
8202 and features mentioned below.
8204 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
8205 have accumulated many known flaws; everyone should upgrade.
8207 o Major features (security):
8208 - The ntor handshake is now on-by-default, no matter what the
8209 directory authorities recommend. Implements ticket 8561.
8210 - Make the "tor-gencert" tool used by directory authority operators
8211 create 2048-bit signing keys by default (rather than 1024-bit, since
8212 1024-bit is uncomfortably small these days). Addresses ticket 10324.
8213 - Warn about attempts to run hidden services and relays in the same
8214 process: that's probably not a good idea. Closes ticket 12908.
8215 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8216 today support TLS 1.0 or later, so we can safely turn off support
8217 for this old (and insecure) protocol. Fixes bug 13426.
8219 o Major features (relay security, DoS-resistance):
8220 - When deciding whether we have run out of memory and we need to
8221 close circuits, also consider memory allocated in buffers for
8222 streams attached to each circuit.
8224 This change, which extends an anti-DoS feature introduced in
8225 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
8226 better resist more memory-based DoS attacks than before. Since the
8227 MaxMemInCellQueues option now applies to all queues, it is renamed
8228 to MaxMemInQueues. This feature fixes bug 10169.
8229 - Avoid hash-flooding denial-of-service attacks by using the secure
8230 SipHash-2-4 hash function for our hashtables. Without this
8231 feature, an attacker could degrade performance of a targeted
8232 client or server by flooding their data structures with a large
8233 number of entries to be stored at the same hash table position,
8234 thereby slowing down the Tor instance. With this feature, hash
8235 table positions are derived from a randomized cryptographic key,
8236 and an attacker cannot predict which entries will collide. Closes
8238 - If you don't specify MaxMemInQueues yourself, Tor now tries to
8239 pick a good value based on your total system memory. Previously,
8240 the default was always 8 GB. You can still override the default by
8241 setting MaxMemInQueues yourself. Resolves ticket 11396.
8243 o Major features (bridges and pluggable transports):
8244 - Add support for passing arguments to managed pluggable transport
8245 proxies. Implements ticket 3594.
8246 - Bridges now track GeoIP information and the number of their users
8247 even when pluggable transports are in use, and report usage
8248 statistics in their extra-info descriptors. Resolves tickets 4773
8250 - Don't launch pluggable transport proxies if we don't have any
8251 bridges configured that would use them. Now we can list many
8252 pluggable transports, and Tor will dynamically start one when it
8253 hears a bridge address that needs it. Resolves ticket 5018.
8254 - The bridge directory authority now assigns status flags (Stable,
8255 Guard, etc) to bridges based on thresholds calculated over all
8256 Running bridges. Now bridgedb can finally make use of its features
8257 to e.g. include at least one Stable bridge in its answers. Fixes
8260 o Major features (controller):
8261 - Extend ORCONN controller event to include an "ID" parameter,
8262 and add four new controller event types CONN_BW, CIRC_BW,
8263 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
8264 The new events are emitted in private Tor networks only, with the
8265 goal of being able to better track performance and load during
8266 full-network simulations. Implements proposal 218 and ticket 7359.
8268 o Major features (relay performance):
8269 - Speed up server-side lookups of rendezvous and introduction point
8270 circuits by using hashtables instead of linear searches. These
8271 functions previously accounted between 3 and 7% of CPU usage on
8272 some busy relays. Resolves ticket 9841.
8273 - Avoid wasting CPU when extending a circuit over a channel that is
8274 nearly out of circuit IDs. Previously, we would do a linear scan
8275 over possible circuit IDs before finding one or deciding that we
8276 had exhausted our possibilities. Now, we try at most 64 random
8277 circuit IDs before deciding that we probably won't succeed. Fixes
8278 a possible root cause of ticket 11553.
8280 o Major features (seccomp2 sandbox, Linux only):
8281 - Use the seccomp2 syscall filtering facility on Linux to limit
8282 which system calls Tor can invoke. This is an experimental,
8283 Linux-only feature to provide defense-in-depth against unknown
8284 attacks. To try turning it on, set "Sandbox 1" in your torrc
8285 file. Please be ready to report bugs. We hope to add support
8286 for better sandboxing in the future, including more fine-grained
8287 filters, better division of responsibility, and support for more
8288 platforms. This work has been done by Cristian-Matei Toader for
8289 Google Summer of Code. Resolves tickets 11351 and 11465.
8291 o Major features (testing networks):
8292 - Make testing Tor networks bootstrap better: lower directory fetch
8293 retry schedules and maximum interval without directory requests,
8294 and raise maximum download tries. Implements ticket 6752.
8295 - Add make target 'test-network' to run tests on a Chutney network.
8296 Implements ticket 8530.
8298 o Major features (other):
8299 - On some platforms (currently: recent OSX versions, glibc-based
8300 platforms that support the ELF format, and a few other
8301 Unix-like operating systems), Tor can now dump stack traces
8302 when a crash occurs or an assertion fails. By default, traces
8303 are dumped to stderr (if possible) and to any logs that are
8304 reporting errors. Implements ticket 9299.
8306 o Deprecated versions:
8307 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
8308 attention for some while.
8310 o Major bugfixes (security, directory authorities):
8311 - Directory authorities now include a digest of each relay's
8312 identity key as a part of its microdescriptor.
8314 This is a workaround for bug 11743 (reported by "cypherpunks"),
8315 where Tor clients do not support receiving multiple
8316 microdescriptors with the same SHA256 digest in the same
8317 consensus. When clients receive a consensus like this, they only
8318 use one of the relays. Without this fix, a hostile relay could
8319 selectively disable some client use of target relays by
8320 constructing a router descriptor with a different identity and the
8321 same microdescriptor parameters and getting the authorities to
8322 list it in a microdescriptor consensus. This fix prevents an
8323 attacker from causing a microdescriptor collision, because the
8324 router's identity is not forgeable.
8326 o Major bugfixes (openssl bug workaround):
8327 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8328 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
8329 bug 13471. This is a workaround for an OpenSSL bug.
8331 o Major bugfixes (client):
8332 - Perform circuit cleanup operations even when circuit
8333 construction operations are disabled (because the network is
8334 disabled, or because there isn't enough directory information).
8335 Previously, when we were not building predictive circuits, we
8336 were not closing expired circuits either. Fixes bug 8387; bugfix on
8337 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
8338 became more strict about when we have "enough directory information
8341 o Major bugfixes (client, pluggable transports):
8342 - When managing pluggable transports, use OS notification facilities
8343 to learn if they have crashed, and don't attempt to kill any
8344 process that has already exited. Fixes bug 8746; bugfix
8347 o Major bugfixes (relay denial of service):
8348 - Instead of writing destroy cells directly to outgoing connection
8349 buffers, queue them and intersperse them with other outgoing cells.
8350 This can prevent a set of resource starvation conditions where too
8351 many pending destroy cells prevent data cells from actually getting
8352 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
8353 bugfix on 0.2.0.1-alpha.
8355 o Major bugfixes (relay):
8356 - Avoid queuing or sending destroy cells for circuit ID zero when we
8357 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
8358 Found and fixed by "cypherpunks".
8359 - Fix ORPort reachability detection on relays running behind a
8360 proxy, by correctly updating the "local" mark on the controlling
8361 channel when changing the address of an or_connection_t after the
8362 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
8363 - Use a direct dirport connection when uploading non-anonymous
8364 descriptors to the directory authorities. Previously, relays would
8365 incorrectly use tunnel connections under a fairly wide variety of
8366 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
8367 - When a circuit accidentally has the same circuit ID for its
8368 forward and reverse direction, correctly detect the direction of
8369 cells using that circuit. Previously, this bug made roughly one
8370 circuit in a million non-functional. Fixes bug 12195; this is a
8371 bugfix on every version of Tor.
8373 o Minor features (security):
8374 - New --enable-expensive-hardening option to enable security
8375 hardening options that consume nontrivial amounts of CPU and
8376 memory. Right now, this includes AddressSanitizer and UbSan, which
8377 are supported in newer versions of GCC and Clang. Closes ticket
8379 - Authorities now assign the Guard flag to the fastest 25% of the
8380 network (it used to be the fastest 50%). Also raise the consensus
8381 weight that guarantees the Guard flag from 250 to 2000. For the
8382 current network, this results in about 1100 guards, down from 2500.
8383 This step paves the way for moving the number of entry guards
8384 down to 1 (proposal 236) while still providing reasonable expected
8385 performance for most users. Implements ticket 12690.
8387 o Minor features (security, memory management):
8388 - Memory allocation tricks (mempools and buffer freelists) are now
8389 disabled by default. You can turn them back on with
8390 --enable-mempools and --enable-buf-freelists respectively. We're
8391 disabling these features because malloc performance is good enough
8392 on most platforms, and a similar feature in OpenSSL exacerbated
8393 exploitation of the Heartbleed attack. Resolves ticket 11476.
8395 o Minor features (bridge client):
8396 - Report a more useful failure message when we can't connect to a
8397 bridge because we don't have the right pluggable transport
8398 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
8400 o Minor features (bridge):
8401 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
8402 cookie file for the ExtORPort g+r by default.
8404 o Minor features (bridges, pluggable transports):
8405 - Bridges now write the SHA1 digest of their identity key
8406 fingerprint (that is, a hash of a hash of their public key) to
8407 notice-level logs, and to a new hashed-fingerprint file. This
8408 information will help bridge operators look up their bridge in
8409 Globe and similar tools. Resolves ticket 10884.
8410 - Improve the message that Tor displays when running as a bridge
8411 using pluggable transports without an Extended ORPort listener.
8412 Also, log the message in the log file too. Resolves ticket 11043.
8413 - Add threshold cutoffs to the networkstatus document created by
8414 the Bridge Authority. Fixes bug 1117.
8415 - On Windows, spawn background processes using the CREATE_NO_WINDOW
8416 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
8417 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
8418 Vidalia set this option for us.) Implements ticket 10297.
8420 o Minor features (build):
8421 - The configure script has a --disable-seccomp option to turn off
8422 support for libseccomp on systems that have it, in case it (or
8423 Tor's use of it) is broken. Resolves ticket 11628.
8424 - Assume that a user using ./configure --host wants to cross-compile,
8425 and give an error if we cannot find a properly named
8426 tool-chain. Add a --disable-tool-name-check option to proceed
8427 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
8428 - If we run ./configure and the compiler recognizes -fstack-protector
8429 but the linker rejects it, warn the user about a potentially missing
8430 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
8431 - Add support for `--library-versions` flag. Implements ticket 6384.
8432 - Return the "unexpected sendme" warnings to a warn severity, but make
8433 them rate limited, to help diagnose ticket 8093.
8434 - Detect a missing asciidoc, and warn the user about it, during
8435 configure rather than at build time. Fixes issue 6506. Patch from
8438 o Minor features (client):
8439 - Add a new option, PredictedPortsRelevanceTime, to control how long
8440 after having received a request to connect to a given port Tor
8441 will try to keep circuits ready in anticipation of future requests
8442 for that port. Patch from "unixninja92"; implements ticket 9176.
8444 o Minor features (config options and command line):
8445 - Add an --allow-missing-torrc commandline option that tells Tor to
8446 run even if the configuration file specified by -f is not available.
8447 Implements ticket 10060.
8448 - Add support for the TPROXY transparent proxying facility on Linux.
8449 See documentation for the new TransProxyType option for more
8450 details. Implementation by "thomo". Closes ticket 10582.
8452 o Minor features (config options):
8453 - Config (torrc) lines now handle fingerprints which are missing
8454 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
8455 - Support a --dump-config option to print some or all of the
8456 configured options. Mainly useful for debugging the command-line
8457 option parsing code. Helps resolve ticket 4647.
8458 - Raise awareness of safer logging: notify user of potentially
8459 unsafe config options, like logging more verbosely than severity
8460 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
8461 - Add a new configuration option TestingV3AuthVotingStartOffset
8462 that bootstraps a network faster by changing the timing for
8463 consensus votes. Addresses ticket 8532.
8464 - Add a new torrc option "ServerTransportOptions" that allows
8465 bridge operators to pass configuration parameters to their
8466 pluggable transports. Resolves ticket 8929.
8467 - The config (torrc) file now accepts bandwidth and space limits in
8468 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
8469 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
8472 o Minor features (controller):
8473 - Make the entire exit policy available from the control port via
8474 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
8476 - Because of the fix for ticket 11396, the real limit for memory
8477 usage may no longer match the configured MaxMemInQueues value. The
8478 real limit is now exposed via GETINFO limits/max-mem-in-queues.
8479 - Add a new "HS_DESC" controller event that reports activities
8480 related to hidden service descriptors. Resolves ticket 8510.
8481 - New "DROPGUARDS" controller command to forget all current entry
8482 guards. Not recommended for ordinary use, since replacing guards
8483 too frequently makes several attacks easier. Resolves ticket 9934;
8485 - Implement the TRANSPORT_LAUNCHED control port event that
8486 notifies controllers about new launched pluggable
8487 transports. Resolves ticket 5609.
8489 o Minor features (diagnostic):
8490 - When logging a warning because of bug 7164, additionally check the
8491 hash table for consistency (as proposed on ticket 11737). This may
8492 help diagnose bug 7164.
8493 - When we log a heartbeat, log how many one-hop circuits we have
8494 that are at least 30 minutes old, and log status information about
8495 a few of them. This is an attempt to track down bug 8387.
8496 - When encountering an unexpected CR while writing text to a file on
8497 Windows, log the name of the file. Should help diagnosing
8499 - Give more specific warnings when a client notices that an onion
8500 handshake has failed. Fixes ticket 9635.
8501 - Add significant new logging code to attempt to diagnose bug 12184,
8502 where relays seem to run out of available circuit IDs.
8503 - Improve the diagnostic log message for bug 8387 even further to
8504 try to improve our odds of figuring out why one-hop directory
8505 circuits sometimes do not get closed.
8506 - Add more log messages to diagnose bug 7164, which causes
8507 intermittent "microdesc_free() called but md was still referenced"
8508 warnings. We now include more information, to figure out why we
8509 might be cleaning a microdescriptor for being too old if it's
8510 still referenced by a live node_t object.
8511 - Log current accounting state (bytes sent and received + remaining
8512 time for the current accounting period) in the relay's heartbeat
8513 message. Implements ticket 5526; patch from Peter Retzlaff.
8515 o Minor features (geoip):
8516 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8519 o Minor features (interface):
8520 - Generate a warning if any ports are listed in the SocksPolicy,
8521 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
8522 AuthDirBadExit options. (These options only support address
8523 ranges.) Fixes part of ticket 11108.
8525 o Minor features (kernel API usage):
8526 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
8527 sockets in a single system call. Implements ticket 5129.
8529 o Minor features (log messages):
8530 - When ServerTransportPlugin is set on a bridge, Tor can write more
8531 useful statistics about bridge use in its extrainfo descriptors,
8532 but only if the Extended ORPort ("ExtORPort") is set too. Add a
8533 log message to inform the user in this case. Resolves ticket 9651.
8534 - When receiving a new controller connection, log the origin address.
8535 Resolves ticket 9698; patch from "sigpipe".
8536 - When logging OpenSSL engine status at startup, log the status of
8537 more engines. Fixes ticket 10043; patch from Joshua Datko.
8539 o Minor features (log verbosity):
8540 - Demote the message that we give when a flushing connection times
8541 out for too long from NOTICE to INFO. It was usually meaningless.
8542 Resolves ticket 5286.
8543 - Don't log so many notice-level bootstrapping messages at startup
8544 about downloading descriptors. Previously, we'd log a notice
8545 whenever we learned about more routers. Now, we only log a notice
8546 at every 5% of progress. Fixes bug 9963.
8547 - Warn less verbosely when receiving a malformed
8548 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
8550 o Minor features (performance):
8551 - If we're using the pure-C 32-bit curve25519_donna implementation
8552 of curve25519, build it with the -fomit-frame-pointer option to
8553 make it go faster on register-starved hosts. This improves our
8554 handshake performance by about 6% on i386 hosts without nacl.
8557 o Minor features (relay):
8558 - If a circuit timed out for at least 3 minutes, check if we have a
8559 new external IP address, and publish a new descriptor with the new
8560 IP address if it changed. Resolves ticket 2454.
8562 o Minor features (testing):
8563 - If Python is installed, "make check" now runs extra tests beyond
8564 the unit test scripts.
8565 - When bootstrapping a test network, sometimes very few relays get
8566 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
8567 specify a set of relays which should be voted Guard regardless of
8568 their uptime or bandwidth. Addresses ticket 9206.
8570 o Minor features (transparent proxy, *BSD):
8571 - Support FreeBSD's ipfw firewall interface for TransPort ports on
8572 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
8573 10267; patch from "yurivict".
8574 - Support OpenBSD's divert-to rules with the pf firewall for
8575 transparent proxy ports. To enable it, set "TransProxyType
8576 pf-divert". This allows Tor to run a TransPort transparent proxy
8577 port on OpenBSD 4.4 or later without root privileges. See the
8578 pf.conf(5) manual page for information on configuring pf to use
8579 divert-to rules. Closes ticket 10896; patch from Dana Koch.
8581 o Minor bugfixes (bridge client):
8582 - Stop accepting bridge lines containing hostnames. Doing so would
8583 cause clients to perform DNS requests on the hostnames, which was
8584 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
8586 o Minor bugfixes (bridges):
8587 - Avoid potential crashes or bad behavior when launching a
8588 server-side managed proxy with ORPort or ExtORPort temporarily
8589 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
8590 - Fix a bug where the first connection works to a bridge that uses a
8591 pluggable transport with client-side parameters, but we don't send
8592 the client-side parameters on subsequent connections. (We don't
8593 use any pluggable transports with client-side parameters yet,
8594 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
8595 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
8597 o Minor bugfixes (build, auxiliary programs):
8598 - Stop preprocessing the "torify" script with autoconf, since
8599 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
8601 - The tor-fw-helper program now follows the standard convention and
8602 exits with status code "0" on success. Fixes bug 9030; bugfix on
8603 0.2.3.1-alpha. Patch by Arlo Breault.
8604 - Corrected ./configure advice for what openssl dev package you should
8605 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
8607 o Minor bugfixes (client):
8608 - Avoid "Tried to open a socket with DisableNetwork set" warnings
8609 when starting a client with bridges configured and DisableNetwork
8610 set. (Tor launcher starts Tor with DisableNetwork set the first
8611 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
8612 - Improve the log message when we can't connect to a hidden service
8613 because all of the hidden service directory nodes hosting its
8614 descriptor are excluded. Improves on our fix for bug 10722, which
8615 was a bugfix on 0.2.0.10-alpha.
8616 - Raise a control port warning when we fail to connect to all of
8617 our bridges. Previously, we didn't inform the controller, and
8618 the bootstrap process would stall. Fixes bug 11069; bugfix on
8620 - Exit immediately when a process-owning controller exits.
8621 Previously, tor relays would wait for a little while after their
8622 controller exited, as if they had gotten an INT signal -- but this
8623 was problematic, since there was no feedback for the user. To do a
8624 clean shutdown, controllers should send an INT signal and give Tor
8625 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
8626 - Stop attempting to connect to bridges before our pluggable
8627 transports are configured (harmless but resulted in some erroneous
8628 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
8629 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
8630 generating incorrect SOCKS5 responses, and confusing client
8631 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
8633 o Minor bugfixes (client, DNSPort):
8634 - When using DNSPort, try to respond to AAAA requests with AAAA
8635 answers. Previously, we hadn't looked at the request type when
8636 deciding which answer type to prefer. Fixes bug 10468; bugfix on
8638 - When receiving a DNS query for an unsupported record type, reply
8639 with no answer rather than with a NOTIMPL error. This behavior
8640 isn't correct either, but it will break fewer client programs, we
8641 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
8644 o Minor bugfixes (client, logging during bootstrap):
8645 - Only report the first fatal bootstrap error on a given OR
8646 connection. This stops us from telling the controller bogus error
8647 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
8648 - Avoid generating spurious warnings when starting with
8649 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
8652 o Minor bugfixes (closing OR connections):
8653 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
8654 check if it's an or_connection_t and correctly call
8655 connection_or_close_for_error() rather than
8656 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
8658 - When closing all connections on setting DisableNetwork to 1, use
8659 connection_or_close_normally() rather than closing OR connections
8660 out from under the channel layer. Fixes bug 11306; bugfix on
8663 o Minor bugfixes (code correctness):
8664 - Previously we used two temporary files when writing descriptors to
8665 disk; now we only use one. Fixes bug 1376.
8666 - Remove an erroneous (but impossible and thus harmless) pointer
8667 comparison that would have allowed compilers to skip a bounds
8668 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
8669 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
8670 - Fix an always-true assertion in pluggable transports code so it
8671 actually checks what it was trying to check. Fixes bug 10046;
8672 bugfix on 0.2.3.9-alpha. Found by "dcb".
8674 o Minor bugfixes (command line):
8675 - Use a single command-line parser for parsing torrc options on the
8676 command line and for finding special command-line options to avoid
8677 inconsistent behavior for torrc option arguments that have the same
8678 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
8680 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
8681 9573; bugfix on 0.0.9pre5.
8683 o Minor bugfixes (compilation):
8684 - Compile correctly with builds and forks of OpenSSL (such as
8685 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
8686 0.2.1.1-alpha. Patch from "dhill".
8687 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
8688 turned off (that is, without support for v2 link handshakes). Fixes
8689 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
8690 - In routerlist_assert_ok(), don't take the address of a
8691 routerinfo's cache_info member unless that routerinfo is non-NULL.
8692 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
8693 - Fix a large number of false positive warnings from the clang
8694 analyzer static analysis tool. This should make real warnings
8695 easier for clang analyzer to find. Patch from "teor". Closes
8697 - Resolve GCC complaints on OpenBSD about discarding constness in
8698 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
8699 on 0.1.1.23. Patch from Dana Koch.
8700 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
8701 treatment of long and time_t as comparable types. Fixes part of
8702 bug 11633. Patch from Dana Koch.
8703 - When deciding whether to build the 64-bit curve25519
8704 implementation, detect platforms where we can compile 128-bit
8705 arithmetic but cannot link it. Fixes bug 11729; bugfix on
8706 0.2.4.8-alpha. Patch from "conradev".
8707 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
8708 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
8709 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
8711 - Build and run correctly on systems like OpenBSD-current that have
8712 patched OpenSSL to remove get_cipher_by_char and/or its
8713 implementations. Fixes issue 13325.
8715 o Minor bugfixes (controller and command-line):
8716 - If changing a config option via "setconf" fails in a recoverable
8717 way, we used to nonetheless write our new control ports to the
8718 file described by the "ControlPortWriteToFile" option. Now we only
8719 write out that file if we successfully switch to the new config
8720 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
8722 o Minor bugfixes (directory server):
8723 - No longer accept malformed http headers when parsing urls from
8724 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
8725 bugfix on 0.0.6pre1.
8726 - When sending a compressed set of descriptors or microdescriptors,
8727 make sure to finalize the zlib stream. Previously, we would write
8728 all the compressed data, but if the last descriptor we wanted to
8729 send was missing or too old, we would not mark the stream as
8730 finished. This caused problems for decompression tools. Fixes bug
8731 11648; bugfix on 0.1.1.23.
8733 o Minor bugfixes (hidden service):
8734 - Only retry attempts to connect to a chosen rendezvous point 8
8735 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
8737 o Minor bugfixes (interface):
8738 - Reject relative control socket paths and emit a warning. Previously,
8739 single-component control socket paths would be rejected, but Tor
8740 would not log why it could not validate the config. Fixes bug 9258;
8741 bugfix on 0.2.3.16-alpha.
8743 o Minor bugfixes (log messages):
8744 - Fix a bug where clients using bridges would report themselves
8745 as 50% bootstrapped even without a live consensus document.
8746 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
8747 - Suppress a warning where, if there's only one directory authority
8748 in the network, we would complain that votes and signatures cannot
8749 be uploaded to other directory authorities. Fixes bug 10842;
8750 bugfix on 0.2.2.26-beta.
8751 - Report bootstrapping progress correctly when we're downloading
8752 microdescriptors. We had updated our "do we have enough microdescs
8753 to begin building circuits?" logic most recently in 0.2.4.10-alpha
8754 (see bug 5956), but we left the bootstrap status event logic at
8755 "how far through getting 1/4 of them are we?" Fixes bug 9958;
8756 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
8758 o Minor bugfixes (logging):
8759 - Downgrade "Unexpected onionskin length after decryption" warning
8760 to a protocol-warn, since there's nothing relay operators can do
8761 about a client that sends them a malformed create cell. Resolves
8762 bug 12996; bugfix on 0.0.6rc1.
8763 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
8764 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
8765 - When logging information about an EXTEND2 or EXTENDED2 cell, log
8766 their names correctly. Fixes part of bug 12700; bugfix
8768 - When logging information about a relay cell whose command we don't
8769 recognize, log its command as an integer. Fixes part of bug 12700;
8770 bugfix on 0.2.1.10-alpha.
8771 - Escape all strings from the directory connection before logging
8772 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
8773 - Squelch a spurious LD_BUG message "No origin circuit for
8774 successful SOCKS stream" in certain hidden service failure cases;
8776 - Downgrade the severity of the 'unexpected sendme cell from client'
8777 from 'warn' to 'protocol warning'. Closes ticket 8093.
8779 o Minor bugfixes (misc code correctness):
8780 - In munge_extrainfo_into_routerinfo(), check the return value of
8781 memchr(). This would have been a serious issue if we ever passed
8782 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
8784 - On the chance that somebody manages to build Tor on a
8785 platform where time_t is unsigned, correct the way that
8786 microdesc_add_to_cache() handles negative time arguments.
8787 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
8788 - Fix various instances of undefined behavior in channeltls.c,
8789 tor_memmem(), and eventdns.c that would cause us to construct
8790 pointers to memory outside an allocated object. (These invalid
8791 pointers were not accessed, but C does not even allow them to
8792 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
8793 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
8794 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
8795 fix some miscellaneous errors in our tests and codebase. Fixes bug
8796 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
8797 - Always check return values for unlink, munmap, UnmapViewOfFile;
8798 check strftime return values more often. In some cases all we can
8799 do is report a warning, but this may help prevent deeper bugs from
8800 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
8802 - Fix numerous warnings from the clang "scan-build" static analyzer.
8803 Some of these are programming style issues; some of them are false
8804 positives that indicated awkward code; some are undefined behavior
8805 cases related to constructing (but not using) invalid pointers;
8806 some are assumptions about API behavior; some are (harmlessly)
8807 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
8808 correct; and one or two are genuine bugs that weren't reachable
8809 from the rest of the program. Fixes bug 8793; bugfixes on many,
8812 o Minor bugfixes (node selection):
8813 - If ExcludeNodes is set, consider non-excluded hidden service
8814 directory servers before excluded ones. Do not consider excluded
8815 hidden service directory servers at all if StrictNodes is
8816 set. (Previously, we would sometimes decide to connect to those
8817 servers, and then realize before we initiated a connection that
8818 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
8820 - If we set the ExitNodes option but it doesn't include any nodes
8821 that have the Exit flag, we would choose not to bootstrap. Now we
8822 bootstrap so long as ExitNodes includes nodes which can exit to
8823 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
8825 o Minor bugfixes (performance):
8826 - Avoid a bug where every successful connection made us recompute
8827 the flag telling us whether we have sufficient information to
8828 build circuits. Previously, we would forget our cached value
8829 whenever we successfully opened a channel (or marked a router as
8830 running or not running for any other reason), regardless of
8831 whether we had previously believed the router to be running. This
8832 forced us to run an expensive update operation far too often.
8833 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
8834 - Avoid using tor_memeq() for checking relay cell integrity. This
8835 removes a possible performance bottleneck. Fixes part of bug
8836 12169; bugfix on 0.2.1.31.
8838 o Minor bugfixes (platform-specific):
8839 - When dumping a malformed directory object to disk, save it in
8840 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
8842 - Don't report failures from make_socket_reuseable() on incoming
8843 sockets on OSX: this can happen when incoming connections close
8844 early. Fixes bug 10081.
8846 o Minor bugfixes (pluggable transports):
8847 - Avoid another 60-second delay when starting Tor in a pluggable-
8848 transport-using configuration when we already have cached
8849 descriptors for our bridges. Fixes bug 11965; bugfix
8852 o Minor bugfixes (protocol correctness):
8853 - When receiving a VERSIONS cell with an odd number of bytes, close
8854 the connection immediately since the cell is malformed. Fixes bug
8855 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
8858 o Minor bugfixes (relay, other):
8859 - We now drop CREATE cells for already-existent circuit IDs and for
8860 zero-valued circuit IDs, regardless of other factors that might
8861 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
8863 - When rejecting DATA cells for stream_id zero, still count them
8864 against the circuit's deliver window so that we don't fail to send
8865 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
8867 o Minor bugfixes (relay, threading):
8868 - Check return code on spawn_func() in cpuworker code, so that we
8869 don't think we've spawned a nonworking cpuworker and write junk to
8870 it forever. Fix related to bug 4345; bugfix on all released Tor
8871 versions. Found by "skruffy".
8872 - Use a pthread_attr to make sure that spawn_func() cannot return an
8873 error while at the same time launching a thread. Fix related to
8874 bug 4345; bugfix on all released Tor versions. Reported
8877 o Minor bugfixes (relays and bridges):
8878 - Avoid crashing on a malformed resolv.conf file when running a
8879 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
8880 - Non-exit relays no longer launch mock DNS requests to check for
8881 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
8882 non-exit relays stopped servicing DNS requests. Fixes bug 965;
8883 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
8884 - Bridges now report complete directory request statistics. Related
8885 to bug 5824; bugfix on 0.2.2.1-alpha.
8886 - Bridges now never collect statistics that were designed for
8887 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
8889 o Minor bugfixes (testing):
8890 - Fix all valgrind warnings produced by the unit tests. There were
8891 over a thousand memory leak warnings previously, mostly produced
8892 by forgetting to free things in the unit test code. Fixes bug
8893 11618, bugfixes on many versions of Tor.
8895 o Minor bugfixes (tor-fw-helper):
8896 - Give a correct log message when tor-fw-helper fails to launch.
8897 (Previously, we would say something like "tor-fw-helper sent us a
8898 string we could not parse".) Fixes bug 9781; bugfix
8901 o Minor bugfixes (trivial memory leaks):
8902 - Fix a small memory leak when signing a directory object. Fixes bug
8903 11275; bugfix on 0.2.4.13-alpha.
8904 - Resolve some memory leaks found by coverity in the unit tests, on
8905 exit in tor-gencert, and on a failure to compute digests for our
8906 own keys when generating a v3 networkstatus vote. These leaks
8907 should never have affected anyone in practice.
8909 o Code simplification and refactoring:
8910 - Remove some old fallback code designed to keep Tor clients working
8911 in a network with only two working relays. Elsewhere in the code we
8912 have long since stopped supporting such networks, so there wasn't
8913 much point in keeping it around. Addresses ticket 9926.
8914 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
8915 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
8916 - Extract the common duplicated code for creating a subdirectory
8917 of the data directory and writing to a file in it. Fixes ticket
8918 4282; patch from Peter Retzlaff.
8919 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
8920 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
8921 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
8922 - Add a set of accessor functions for the circuit timeout data
8923 structure. Fixes ticket 6153; patch from "piet".
8924 - Clean up exit paths from connection_listener_new(). Closes ticket
8925 8789. Patch from Arlo Breault.
8926 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
8927 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
8928 - Use a doubly-linked list to implement the global circuit list.
8929 Resolves ticket 9108. Patch from Marek Majkowski.
8930 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
8931 - Remove constants and tests for PKCS1 padding; it's insecure and
8932 shouldn't be used for anything new. Fixes bug 8792; patch
8934 - Remove instances of strcpy() from the unit tests. They weren't
8935 hurting anything, since they were only in the unit tests, but it's
8936 embarrassing to have strcpy() in the code at all, and some analysis
8937 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
8938 0.2.3.8-alpha. Patch from Arlo Breault.
8939 - Remove is_internal_IP() function. Resolves ticket 4645.
8940 - Remove unused function circuit_dump_by_chan from circuitlist.c.
8941 Closes issue 9107; patch from "marek".
8942 - Change our use of the ENUM_BF macro to avoid declarations that
8944 - Get rid of router->address, since in all cases it was just the
8945 string representation of router->addr. Resolves ticket 5528.
8948 - Adjust the URLs in the README to refer to the new locations of
8949 several documents on the website. Fixes bug 12830. Patch from
8951 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
8953 - Update manpage to describe some of the files you can expect to
8954 find in Tor's DataDirectory. Addresses ticket 9839.
8955 - Clean up several option names in the manpage to match their real
8956 names, add the missing documentation for a couple of testing and
8957 directory authority options, remove the documentation for a
8958 V2-directory fetching option that no longer exists. Resolves
8960 - Correct the documentation so that it lists the correct directory
8961 for the stats files. (They are in a subdirectory called "stats",
8963 - In the manpage, move more authority-only options into the
8964 directory authority section so that operators of regular directory
8965 caches don't get confused.
8966 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
8967 11061; bugfix on 0.2.4.7-alpha.
8968 - Resolve warnings from Doxygen.
8969 - Document in the manpage that "KBytes" may also be written as
8970 "kilobytes" or "KB", that "Kbits" may also be written as
8971 "kilobits", and so forth. Closes ticket 9222.
8972 - Document that the ClientOnly config option overrides ORPort.
8973 Our old explanation made ClientOnly sound as though it did
8974 nothing at all. Resolves bug 9059.
8975 - Explain that SocksPolicy, DirPolicy, and similar options don't
8976 take port arguments. Fixes the other part of ticket 11108.
8977 - Fix a comment about the rend_server_descriptor_t.protocols field
8978 to more accurately describe its range. Also, make that field
8979 unsigned, to more accurately reflect its usage. Fixes bug 9099;
8980 bugfix on 0.2.1.5-alpha.
8981 - Fix the manpage's description of HiddenServiceAuthorizeClient:
8982 the maximum client name length is 16, not 19. Fixes bug 11118;
8983 bugfix on 0.2.1.6-alpha.
8986 - The contrib directory has been sorted and tidied. Before, it was
8987 an unsorted dumping ground for useful and not-so-useful things.
8988 Now, it is divided based on functionality, and the items which
8989 seemed to be nonfunctional or useless have been removed. Resolves
8990 ticket 8966; based on patches from "rl1987".
8992 o Removed code and features:
8993 - Clients now reject any directory authority certificates lacking
8994 a dir-key-crosscert element. These have been included since
8995 0.2.1.9-alpha, so there's no real reason for them to be optional
8996 any longer. Completes proposal 157. Resolves ticket 10162.
8997 - Remove all code that existed to support the v2 directory system,
8998 since there are no longer any v2 directory authorities. Resolves
9000 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
9001 options, which were used for designating authorities as "Hidden
9002 service authorities". There has been no use of hidden service
9003 authorities since 0.2.2.1-alpha, when we stopped uploading or
9004 downloading v0 hidden service descriptors. Fixes bug 10881; also
9005 part of a fix for bug 10841.
9006 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9007 and MTBF calculations, but that nobody was using. Fixes bug 11742.
9008 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9009 exist; tunneled directory connections have been available since
9010 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9011 brute-force fix for 10849, where "TunnelDirConns 0" would break
9013 - Remove all code for the long unused v1 directory protocol.
9014 Resolves ticket 11070.
9015 - Remove all remaining code related to version-0 hidden service
9016 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
9017 the rest of bug 10841.
9018 - Remove migration code from when we renamed the "cached-routers"
9019 file to "cached-descriptors" back in 0.2.0.8-alpha. This
9020 incidentally resolves ticket 6502 by cleaning up the related code
9021 a bit. Patch from Akshay Hebbar.
9023 o Test infrastructure:
9024 - Tor now builds each source file in two modes: a mode that avoids
9025 exposing identifiers needlessly, and another mode that exposes
9026 more identifiers for testing. This lets the compiler do better at
9027 optimizing the production code, while enabling us to take more
9028 radical measures to let the unit tests test things.
9029 - The production builds no longer include functions used only in
9030 the unit tests; all functions exposed from a module only for
9031 unit-testing are now static in production builds.
9032 - Add an --enable-coverage configuration option to make the unit
9033 tests (and a new src/or/tor-cov target) to build with gcov test
9035 - Update to the latest version of tinytest.
9036 - Improve the tinytest implementation of string operation tests so
9037 that comparisons with NULL strings no longer crash the tests; they
9038 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
9039 - New macros in test.h to simplify writing mock-functions for unit
9040 tests. Part of ticket 11507. Patch from Dana Koch.
9041 - We now have rudimentary function mocking support that our unit
9042 tests can use to test functions in isolation. Function mocking
9043 lets the tests temporarily replace a function's dependencies with
9044 stub functions, so that the tests can check the function without
9045 invoking the other functions it calls.
9048 - Complete tests for the status.c module. Resolves ticket 11507.
9049 Patch from Dana Koch.
9050 - Add more unit tests for the <circid,channel>->circuit map, and
9051 the destroy-cell-tracking code to fix bug 7912.
9052 - Unit tests for failing cases of the TAP onion handshake.
9053 - More unit tests for address-manipulation functions.
9055 o Distribution (systemd):
9056 - Include a tor.service file in contrib/dist for use with systemd.
9057 Some distributions will be able to use this file unmodified;
9058 others will need to tweak it, or write their own. Patch from Jamie
9059 Nguyen; resolves ticket 8368.
9060 - Verify configuration file via ExecStartPre in the systemd unit
9061 file. Patch from intrigeri; resolves ticket 12730.
9062 - Explicitly disable RunAsDaemon in the systemd unit file. Our
9063 current systemd unit uses "Type = simple", so systemd does not
9064 expect tor to fork. If the user has "RunAsDaemon 1" in their
9065 torrc, then things won't work as expected. This is e.g. the case
9066 on Debian (and derivatives), since there we pass "--defaults-torrc
9067 /usr/share/tor/tor-service-defaults-torrc" (that contains
9068 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
9072 Changes in version 0.2.4.25 - 2014-10-20
9073 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9074 (even though POODLE does not affect Tor). It also works around a crash
9075 bug caused by some operating systems' response to the "POODLE" attack
9076 (which does affect Tor).
9078 o Major security fixes (also in 0.2.5.9-rc):
9079 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9080 today support TLS 1.0 or later, so we can safely turn off support
9081 for this old (and insecure) protocol. Fixes bug 13426.
9083 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9084 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9085 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9086 13471. This is a workaround for an OpenSSL bug.
9089 Changes in version 0.2.4.24 - 2014-09-22
9090 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9091 connecting to hidden services, and it updates the location of one of
9092 the directory authorities.
9095 - Clients now send the correct address for their chosen rendezvous
9096 point when trying to access a hidden service. They used to send
9097 the wrong address, which would still work some of the time because
9098 they also sent the identity digest of the rendezvous point, and if
9099 the hidden service happened to try connecting to the rendezvous
9100 point from a relay that already had a connection open to it,
9101 the relay would reuse that connection. Now connections to hidden
9102 services should be more robust and faster. Also, this bug meant
9103 that clients were leaking to the hidden service whether they were
9104 on a little-endian (common) or big-endian (rare) system, which for
9105 some users might have reduced their anonymity. Fixes bug 13151;
9106 bugfix on 0.2.1.5-alpha.
9108 o Directory authority changes:
9109 - Change IP address for gabelmoo (v3 directory authority).
9111 o Minor features (geoip):
9112 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9116 Changes in version 0.2.4.23 - 2014-07-28
9117 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
9118 guard rotation, and also backports several important fixes from the
9119 Tor 0.2.5 alpha release series.
9122 - Clients now look at the "usecreatefast" consensus parameter to
9123 decide whether to use CREATE_FAST or CREATE cells for the first hop
9124 of their circuit. This approach can improve security on connections
9125 where Tor's circuit handshake is stronger than the available TLS
9126 connection security levels, but the tradeoff is more computational
9127 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9128 - Make the number of entry guards configurable via a new
9129 NumEntryGuards consensus parameter, and the number of directory
9130 guards configurable via a new NumDirectoryGuards consensus
9131 parameter. Implements ticket 12688.
9134 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9135 implementation that caused incorrect results on 32-bit
9136 implementations when certain malformed inputs were used along with
9137 a small class of private ntor keys. This bug does not currently
9138 appear to allow an attacker to learn private keys or impersonate a
9139 Tor server, but it could provide a means to distinguish 32-bit Tor
9140 implementations from 64-bit Tor implementations. Fixes bug 12694;
9141 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9145 - Warn and drop the circuit if we receive an inbound 'relay early'
9146 cell. Those used to be normal to receive on hidden service circuits
9147 due to bug 1038, but the buggy Tor versions are long gone from
9148 the network so we can afford to resume watching for them. Resolves
9149 the rest of bug 1038; bugfix on 0.2.1.19.
9150 - Correct a confusing error message when trying to extend a circuit
9151 via the control protocol but we don't know a descriptor or
9152 microdescriptor for one of the specified relays. Fixes bug 12718;
9153 bugfix on 0.2.3.1-alpha.
9154 - Avoid an illegal read from stack when initializing the TLS
9155 module using a version of OpenSSL without all of the ciphers
9156 used by the v2 link handshake. Fixes bug 12227; bugfix on
9157 0.2.4.8-alpha. Found by "starlight".
9160 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9164 Changes in version 0.2.4.22 - 2014-05-16
9165 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9166 alpha release series. These include blocking all authority signing
9167 keys that may have been affected by the OpenSSL "heartbleed" bug,
9168 choosing a far more secure set of TLS ciphersuites by default, closing
9169 a couple of memory leaks that could be used to run a target relay out
9170 of RAM, and several others.
9172 o Major features (security, backport from 0.2.5.4-alpha):
9173 - Block authority signing keys that were used on authorities
9174 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9175 don't have any evidence that these keys _were_ compromised; we're
9176 doing this to be prudent.) Resolves ticket 11464.
9178 o Major bugfixes (security, OOM):
9179 - Fix a memory leak that could occur if a microdescriptor parse
9180 fails during the tokenizing step. This bug could enable a memory
9181 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9184 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9185 - The relay ciphersuite list is now generated automatically based on
9186 uniform criteria, and includes all OpenSSL ciphersuites with
9187 acceptable strength and forward secrecy. Previously, we had left
9188 some perfectly fine ciphersuites unsupported due to omission or
9189 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9190 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9191 - Relays now trust themselves to have a better view than clients of
9192 which TLS ciphersuites are better than others. (Thanks to bug
9193 11513, the relay list is now well-considered, whereas the client
9194 list has been chosen mainly for anti-fingerprinting purposes.)
9195 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9196 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9197 AES128. Resolves ticket 11528.
9198 - Clients now try to advertise the same list of ciphersuites as
9199 Firefox 28. This change enables selection of (fast) GCM
9200 ciphersuites, disables some strange old ciphers, and stops
9201 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9202 Resolves ticket 11438.
9204 o Minor bugfixes (configuration, security):
9205 - When running a hidden service, do not allow TunneledDirConns 0:
9206 trying to set that option together with a hidden service would
9207 otherwise prevent the hidden service from running, and also make
9208 it publish its descriptors directly over HTTP. Fixes bug 10849;
9209 bugfix on 0.2.1.1-alpha.
9211 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9212 - Avoid sending a garbage value to the controller when a circuit is
9213 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9215 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9216 - Stop leaking memory when we successfully resolve a PTR record.
9217 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9219 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9220 - Avoid 60-second delays in the bootstrapping process when Tor is
9221 launching for a second time while using bridges. Fixes bug 9229;
9222 bugfix on 0.2.0.3-alpha.
9224 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9225 - Give the correct URL in the warning message when trying to run a
9226 relay on an ancient version of Windows. Fixes bug 9393.
9228 o Minor bugfixes (compilation):
9229 - Fix a compilation error when compiling with --disable-curve25519.
9230 Fixes bug 9700; bugfix on 0.2.4.17-rc.
9233 - Downgrade the warning severity for the the "md was still
9234 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
9235 for trying to diagnose this bug, and the current warning in
9236 earlier versions of tor achieves nothing useful. Addresses warning
9239 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
9240 - When we run out of usable circuit IDs on a channel, log only one
9241 warning for the whole channel, and describe how many circuits
9242 there were on the channel. Fixes part of ticket 11553.
9244 o Minor features (security, backport from 0.2.5.4-alpha):
9245 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
9246 leave the default at 8GBytes), to better support Raspberry Pi
9247 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
9249 o Documentation (backport from 0.2.5.4-alpha):
9250 - Correctly document that we search for a system torrc file before
9251 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
9255 Changes in version 0.2.4.21 - 2014-02-28
9256 Tor 0.2.4.21 further improves security against potential adversaries who
9257 find breaking 1024-bit crypto doable, and backports several stability
9258 and robustness patches from the 0.2.5 branch.
9260 o Major features (client security):
9261 - When we choose a path for a 3-hop circuit, make sure it contains
9262 at least one relay that supports the NTor circuit extension
9263 handshake. Otherwise, there is a chance that we're building
9264 a circuit that's worth attacking by an adversary who finds
9265 breaking 1024-bit crypto doable, and that chance changes the game
9266 theory. Implements ticket 9777.
9269 - Do not treat streams that fail with reason
9270 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
9271 since it could also indicate an ENETUNREACH connection error. Fixes
9272 part of bug 10777; bugfix on 0.2.4.8-alpha.
9274 o Code simplification and refactoring:
9275 - Remove data structures which were introduced to implement the
9276 CellStatistics option: they are now redundant with the new timestamp
9277 field in the regular packed_cell_t data structure, which we did
9278 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
9281 - Always clear OpenSSL bignums before freeing them -- even bignums
9282 that don't contain secrets. Resolves ticket 10793. Patch by
9284 - Build without warnings under clang 3.4. (We have some macros that
9285 define static functions only some of which will get used later in
9286 the module. Starting with clang 3.4, these give a warning unless the
9287 unused attribute is set on them.) Resolves ticket 10904.
9288 - Update geoip and geoip6 files to the February 7 2014 Maxmind
9289 GeoLite2 Country database.
9292 - Set the listen() backlog limit to the largest actually supported
9293 on the system, not to the value in a header file. Fixes bug 9716;
9294 bugfix on every released Tor.
9295 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
9296 exit node as a NOROUTE error, not an INTERNAL error, since they
9297 can apparently happen when trying to connect to the wrong sort
9298 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
9299 - Fix build warnings about missing "a2x" comment when building the
9300 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
9301 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
9302 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
9303 not entirely remove it from the connection lists. Fixes bug 9602;
9304 bugfix on 0.2.4.4-alpha.
9305 - Fix a segmentation fault in our benchmark code when running with
9306 Fedora's OpenSSL package, or any other OpenSSL that provides
9307 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
9308 - Turn "circuit handshake stats since last time" log messages into a
9309 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
9311 o Documentation fixes:
9312 - Document that all but one DirPort entry must have the NoAdvertise
9313 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
9316 Changes in version 0.2.4.20 - 2013-12-22
9317 Tor 0.2.4.20 fixes potentially poor random number generation for users
9318 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
9319 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
9320 and 4) have no state file in their DataDirectory (as would happen on
9321 first start). Users who generated relay or hidden service identity
9322 keys in such a situation should discard them and generate new ones.
9324 This release also fixes a logic error that caused Tor clients to build
9325 many more preemptive circuits than they actually need.
9328 - Do not allow OpenSSL engines to replace the PRNG, even when
9329 HardwareAccel is set. The only default builtin PRNG engine uses
9330 the Intel RDRAND instruction to replace the entire PRNG, and
9331 ignores all attempts to seed it with more entropy. That's
9332 cryptographically stupid: the right response to a new alleged
9333 entropy source is never to discard all previously used entropy
9334 sources. Fixes bug 10402; works around behavior introduced in
9335 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
9337 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
9338 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
9339 - Avoid launching spurious extra circuits when a stream is pending.
9340 This fixes a bug where any circuit that _wasn't_ unusable for new
9341 streams would be treated as if it were, causing extra circuits to
9342 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
9345 - Avoid a crash bug when starting with a corrupted microdescriptor
9346 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
9347 - If we fail to dump a previously cached microdescriptor to disk, avoid
9348 freeing duplicate data later on. Fixes bug 10423; bugfix on
9349 0.2.4.13-alpha. Spotted by "bobnomnom".
9352 Changes in version 0.2.4.19 - 2013-12-11
9353 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
9354 (1986-2013). Aaron worked on diverse projects including helping to guide
9355 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
9356 transparency to the U.S government's PACER documents, and contributing
9357 design and development for Tor and Tor2Web. Aaron was one of the latest
9358 martyrs in our collective fight for civil liberties and human rights,
9359 and his death is all the more painful because he was one of us.
9361 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
9362 a new circuit handshake and link encryption that use ECC to provide
9363 better security and efficiency; makes relays better manage circuit
9364 creation requests; uses "directory guards" to reduce client enumeration
9365 risks; makes bridges collect and report statistics about the pluggable
9366 transports they support; cleans up and improves our geoip database;
9367 gets much closer to IPv6 support for clients, bridges, and relays; makes
9368 directory authorities use measured bandwidths rather than advertised
9369 ones when computing flags and thresholds; disables client-side DNS
9370 caching to reduce tracking risks; and fixes a big bug in bridge
9371 reachability testing. This release introduces two new design
9372 abstractions in the code: a new "channel" abstraction between circuits
9373 and or_connections to allow for implementing alternate relay-to-relay
9374 transports, and a new "circuitmux" abstraction storing the queue of
9375 circuits for a channel. The release also includes many stability,
9376 security, and privacy fixes.
9378 o Major features (new circuit handshake):
9379 - Tor now supports a new circuit extension handshake designed by Ian
9380 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
9381 circuit extension handshake, later called "TAP", was a bit slow
9382 (especially on the relay side), had a fragile security proof, and
9383 used weaker keys than we'd now prefer. The new circuit handshake
9384 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
9385 function, making it significantly more secure than the older
9386 handshake, and significantly faster. Tor can use one of two built-in
9387 pure-C curve25519-donna implementations by Adam Langley, or it
9388 can link against the "nacl" library for a tuned version if present.
9390 The built-in version is very fast for 64-bit systems when building
9391 with GCC. The built-in 32-bit version is still faster than the
9392 old TAP protocol, but using libnacl is better on most such hosts.
9394 Implements proposal 216; closes ticket 7202.
9396 o Major features (better link encryption):
9397 - Relays can now enable the ECDHE TLS ciphersuites when available
9398 and appropriate. These ciphersuites let us negotiate forward-secure
9399 TLS secret keys more safely and more efficiently than with our
9400 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
9401 public relays prefer the (faster) P224 group, and bridges prefer
9402 the (more common) P256 group; you can override this with the
9405 This feature requires clients running 0.2.3.17-beta or later,
9406 and requires both sides to be running OpenSSL 1.0.0 or later
9407 with ECC support. OpenSSL 1.0.1, with the compile-time option
9408 "enable-ec_nistp_64_gcc_128", is highly recommended.
9410 Implements the relay side of proposal 198; closes ticket 7200.
9412 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
9413 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
9414 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
9415 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
9416 them to solve bug 6033.)
9418 o Major features (relay performance):
9419 - Instead of limiting the number of queued onionskins (aka circuit
9420 create requests) to a fixed, hard-to-configure number, we limit
9421 the size of the queue based on how many we expect to be able to
9422 process in a given amount of time. We estimate the time it will
9423 take to process an onionskin based on average processing time
9424 of previous onionskins. Closes ticket 7291. You'll never have to
9425 configure MaxOnionsPending again.
9426 - Relays process the new "NTor" circuit-level handshake requests
9427 with higher priority than the old "TAP" circuit-level handshake
9428 requests. We still process some TAP requests to not totally starve
9429 0.2.3 clients when NTor becomes popular. A new consensus parameter
9430 "NumNTorsPerTAP" lets us tune the balance later if we need to.
9431 Implements ticket 9574.
9433 o Major features (client bootstrapping resilience):
9434 - Add a new "FallbackDir" torrc option to use when we can't use
9435 a directory mirror from the consensus (either because we lack a
9436 consensus, or because they're all down). Currently, all authorities
9437 are fallbacks by default, and there are no other default fallbacks,
9438 but that will change. This option will allow us to give clients a
9439 longer list of servers to try to get a consensus from when first
9440 connecting to the Tor network, and thereby reduce load on the
9441 directory authorities. Implements proposal 206, "Preconfigured
9442 directory sources for bootstrapping". We also removed the old
9443 "FallbackNetworkstatus" option, since we never got it working well
9444 enough to use it. Closes bug 572.
9445 - If we have no circuits open, use a relaxed timeout (the
9446 95th-percentile cutoff) until a circuit succeeds. This heuristic
9447 should allow Tor to succeed at building circuits even when the
9448 network connection drastically changes. Should help with bug 3443.
9450 o Major features (use of guards):
9451 - Support directory guards (proposal 207): when possible, clients now
9452 use their entry guards for non-anonymous directory requests. This
9453 can help prevent client enumeration. Note that this behavior only
9454 works when we have a usable consensus directory, and when options
9455 about what to download are more or less standard. In the future we
9456 should re-bootstrap from our guards, rather than re-bootstrapping
9457 from the preconfigured list of directory sources that ships with
9458 Tor. Resolves ticket 6526.
9459 - Raise the default time that a client keeps an entry guard from
9460 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
9461 2012 paper. (We would make it even longer, but we need better client
9462 load balancing first.) Also, make the guard lifetime controllable
9463 via a new GuardLifetime torrc option and a GuardLifetime consensus
9464 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9466 o Major features (bridges with pluggable transports):
9467 - Bridges now report the pluggable transports they support to the
9468 bridge authority, so it can pass the supported transports on to
9469 bridgedb and/or eventually do reachability testing. Implements
9471 - Automatically forward the TCP ports of pluggable transport
9472 proxies using tor-fw-helper if PortForwarding is enabled. Implements
9475 o Major features (geoip database):
9476 - Maxmind began labelling Tor relays as being in country "A1",
9477 which breaks by-country node selection inside Tor. Now we use a
9478 script to replace "A1" ("Anonymous Proxy") entries in our geoip
9479 file with real country codes. This script fixes about 90% of "A1"
9480 entries automatically and uses manual country code assignments to
9481 fix the remaining 10%. See src/config/README.geoip for details.
9483 - Add GeoIP database for IPv6 addresses. The new config option
9485 - Update to the October 2 2013 Maxmind GeoLite Country database.
9487 o Major features (IPv6):
9488 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
9489 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
9490 to happen. Implements ticket 5535.
9491 - All kind of relays, not just bridges, can now advertise an IPv6
9492 OR port. Implements ticket 6362.
9493 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
9494 connectivity, then set the IPv6Exit flag to 1. Also make sure your
9495 exit policy reads as you would like: the address * applies to all
9496 address families, whereas *4 is IPv4 address only, and *6 is IPv6
9497 addresses only. On the client side, you'll need to wait for enough
9498 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
9499 and use Socks5. Closes ticket 5547, implements proposal 117 as
9500 revised in proposal 208.
9501 - Bridge authorities now accept IPv6 bridge addresses and include
9502 them in network status documents. Implements ticket 5534.
9503 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
9505 o Major features (directory authorities):
9506 - Directory authorities now prefer using measured bandwidths to
9507 advertised ones when computing flags and thresholds. Resolves
9509 - Directory authorities that vote measured bandwidths about more
9510 than a threshold number of relays now treat relays with
9511 unmeasured bandwidths as having bandwidth 0 when computing their
9512 flags. Resolves ticket 8435.
9513 - Directory authorities now support a new consensus method (17)
9514 where they cap the published bandwidth of relays for which
9515 insufficient bandwidth measurements exist. Fixes part of bug 2286.
9516 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
9517 serve any v2 directory information. Now we can test disabling the
9518 old deprecated v2 directory format, and see whether doing so has
9519 any effect on network load. Begins to fix bug 6783.
9521 o Major features (build and portability):
9522 - Switch to a nonrecursive Makefile structure. Now instead of each
9523 Makefile.am invoking other Makefile.am's, there is a master
9524 Makefile.am that includes the others. This change makes our build
9525 process slightly more maintainable, and improves parallelism for
9526 building with make -j. Original patch by Stewart Smith; various
9527 fixes by Jim Meyering.
9528 - Where available, we now use automake's "silent" make rules by
9529 default, so that warnings are easier to spot. You can get the old
9530 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
9531 - Resume building correctly with MSVC and Makefile.nmake. This patch
9532 resolves numerous bugs and fixes reported by ultramage, including
9533 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
9535 o Security features:
9536 - Switch to a completely time-invariant approach for picking nodes
9537 weighted by bandwidth. Our old approach would run through the
9538 part of the loop after it had made its choice slightly slower
9539 than it ran through the part of the loop before it had made its
9540 choice. Addresses ticket 6538.
9541 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
9542 by tor2web clients allows hidden services to identify tor2web
9543 clients through their repeated selection of the same rendezvous
9544 and introduction point circuit endpoints (their guards). Resolves
9547 o Major bugfixes (relay denial of service):
9548 - When we have too much memory queued in circuits (according to a new
9549 MaxMemInCellQueues option), close the circuits that have the oldest
9550 queued cells, on the theory that those are most responsible for
9551 us running low on memory. This prevents us from running out of
9552 memory as a relay if circuits fill up faster than they can be
9553 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
9554 Tor. This bug is a further fix beyond bug 6252, whose fix was
9555 merged into 0.2.3.21-rc.
9556 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
9557 ID: these could be used to create unexpected streams and circuits
9558 which would count as "present" to some parts of Tor but "absent"
9559 to others, leading to zombie circuits and streams or to a bandwidth
9560 denial-of-service. Fixes bug 7889; bugfix on every released version
9561 of Tor. Reported by "oftc_must_be_destroyed".
9562 - Avoid a bug where our response to TLS renegotiation under certain
9563 network conditions could lead to a busy-loop, with 100% CPU
9564 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
9566 o Major bugfixes (asserts, crashes, leaks):
9567 - Prevent the get_freelists() function from running off the end of
9568 the list of freelists if it somehow gets an unrecognized
9569 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
9571 - Avoid a memory leak where we would leak a consensus body when we
9572 find that a consensus which we couldn't previously verify due to
9573 missing certificates is now verifiable. Fixes bug 8719; bugfix
9575 - If we are unable to save a microdescriptor to the journal, do not
9576 drop it from memory and then reattempt downloading it. Fixes bug
9577 9645; bugfix on 0.2.2.6-alpha.
9578 - Fix an assertion failure that would occur when disabling the
9579 ORPort setting on a running Tor process while accounting was
9580 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
9581 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
9582 when an exit connection with optimistic data succeeds immediately
9583 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
9585 - Fix a memory leak that would occur whenever a configuration
9586 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
9588 o Major bugfixes (relay rate limiting):
9589 - When a TLS write is partially successful but incomplete, remember
9590 that the flushed part has been flushed, and notice that bytes were
9591 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
9592 bugfix on Tor 0.1.0.5-rc.
9593 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
9594 to 1GB/1GB. The previous defaults were intended to be "basically
9595 infinite", but it turns out they're now limiting our 100mbit+
9596 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
9597 last time we raised it).
9598 - No longer stop reading or writing on cpuworker connections when
9599 our rate limiting buckets go empty. Now we should handle circuit
9600 handshake requests more promptly. Resolves bug 9731.
9602 o Major bugfixes (client-side privacy):
9603 - When we mark a circuit as unusable for new circuits, have it
9604 continue to be unusable for new circuits even if MaxCircuitDirtiness
9605 is increased too much at the wrong time, or the system clock jumps
9606 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
9607 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
9608 which have resolved to internal addresses") is set, apply that
9609 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
9610 - When an exit relay rejects a stream with reason "exit policy", but
9611 we only know an exit policy summary (e.g. from the microdesc
9612 consensus) for it, do not mark the relay as useless for all exiting.
9613 Instead, mark just the circuit as unsuitable for that particular
9614 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
9616 o Major bugfixes (stream isolation):
9617 - Allow applications to get proper stream isolation with
9618 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
9619 username/password authentication also offer "no authentication". Tor
9620 had previously preferred "no authentication", so the applications
9621 never actually sent Tor their auth details. Now Tor selects
9622 username/password authentication if it's offered. You can disable
9623 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
9624 bug 8117; bugfix on 0.2.3.3-alpha.
9625 - Follow the socks5 protocol when offering username/password
9626 authentication. The fix for bug 8117 exposed this bug, and it
9627 turns out real-world applications like Pidgin do care. Bugfix on
9628 0.2.3.2-alpha; fixes bug 8879.
9630 o Major bugfixes (client circuit building):
9631 - Alter circuit build timeout measurement to start at the point
9632 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
9633 initialization). This should make our timeout measurements more
9634 uniform. Previously, we were sometimes including ORconn setup time
9635 in our circuit build time measurements. Should resolve bug 3443.
9636 - If the circuit build timeout logic is disabled (via the consensus,
9637 or because we are an authority), then don't build testing circuits.
9638 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
9640 o Major bugfixes (client-side DNS):
9641 - Turn off the client-side DNS cache by default. Updating and using
9642 the DNS cache is now configurable on a per-client-port
9643 level. SOCKSPort, DNSPort, etc lines may now contain
9644 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
9645 cache these types of DNS answers when we receive them from an
9646 exit node in response to an application request on this port, and
9647 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
9648 cached DNS answers of these types, we shouldn't use them. It's
9649 potentially risky to use cached DNS answers at the client, since
9650 doing so can indicate to one exit what answers we've gotten
9651 for DNS lookups in the past. With IPv6, this becomes especially
9652 problematic. Using cached DNS answers for requests on the same
9653 circuit would present less linkability risk, since all traffic
9654 on a circuit is already linkable, but it would also provide
9655 little performance benefit: the exit node caches DNS replies
9656 too. Implements a simplified version of Proposal 205. Implements
9659 o Major bugfixes (hidden service privacy):
9660 - Limit hidden service descriptors to at most ten introduction
9661 points, to slow one kind of guard enumeration. Fixes bug 9002;
9662 bugfix on 0.1.1.11-alpha.
9664 o Major bugfixes (directory fetching):
9665 - If the time to download the next old-style networkstatus is in
9666 the future, do not decline to consider whether to download the
9667 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
9669 - We used to always request authority certificates by identity digest,
9670 meaning we'd get the newest one even when we wanted one with a
9671 different signing key. Then we would complain about being given
9672 a certificate we already had, and never get the one we really
9673 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
9674 resource to request the one we want. Fixes bug 5595; bugfix on
9677 o Major bugfixes (bridge reachability):
9678 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
9679 previously they did not, which prevented them from receiving
9680 successful connections from relays for self-test or bandwidth
9681 testing. Also, when a relay is extending a circuit to a bridge,
9682 it needs to send a NETINFO cell, even when the bridge hasn't sent
9683 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
9685 o Major bugfixes (control interface):
9686 - When receiving a new configuration file via the control port's
9687 LOADCONF command, do not treat the defaults file as absent.
9688 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
9690 o Major bugfixes (directory authorities):
9691 - Stop marking every relay as having been down for one hour every
9692 time we restart a directory authority. These artificial downtimes
9693 were messing with our Stable and Guard flag calculations. Fixes
9694 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
9695 - When computing directory thresholds, ignore any rejected-as-sybil
9696 nodes during the computation so that they can't influence Fast,
9697 Guard, etc. (We should have done this for proposal 109.) Fixes
9699 - When marking a node as a likely sybil, reset its uptime metrics
9700 to zero, so that it cannot time towards getting marked as Guard,
9701 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
9703 - Fix a bug in the voting algorithm that could yield incorrect results
9704 when a non-naming authority declared too many flags. Fixes bug 9200;
9705 bugfix on 0.2.0.3-alpha.
9707 o Internal abstraction features:
9708 - Introduce new channel_t abstraction between circuits and
9709 or_connection_t to allow for implementing alternate OR-to-OR
9710 transports. A channel_t is an abstract object which can either be a
9711 cell-bearing channel, which is responsible for authenticating and
9712 handshaking with the remote OR and transmitting cells to and from
9713 it, or a listening channel, which spawns new cell-bearing channels
9714 at the request of remote ORs. Implements part of ticket 6465.
9715 - Make a channel_tls_t subclass of channel_t, adapting it to the
9716 existing or_connection_t code. The V2/V3 protocol handshaking
9717 code which formerly resided in command.c has been moved below the
9718 channel_t abstraction layer and may be found in channeltls.c now.
9719 Implements the rest of ticket 6465.
9720 - Introduce new circuitmux_t storing the queue of circuits for
9721 a channel; this encapsulates and abstracts the queue logic and
9722 circuit selection policy, and allows the latter to be overridden
9723 easily by switching out a policy object. The existing EWMA behavior
9724 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
9726 o New build requirements:
9727 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
9728 strongly recommended.
9729 - Tor maintainers now require Automake version 1.9 or later to build
9730 Tor from the Git repository. (Automake is not required when building
9731 from a source distribution.)
9733 o Minor features (protocol):
9734 - No longer include the "opt" prefix when generating routerinfos
9735 or v2 directories: it has been needless since Tor 0.1.2. Closes
9737 - Reject EXTEND cells sent to nonexistent streams. According to the
9738 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
9739 we were only checking for stream IDs that were currently in use.
9740 Found while hunting for more instances of bug 6271. Bugfix on
9741 0.0.2pre8, which introduced incremental circuit construction.
9742 - Tor relays and clients now support a better CREATE/EXTEND cell
9743 format, allowing the sender to specify multiple address, identity,
9744 and handshake types. Implements Robert Ransom's proposal 200;
9746 - Reject as invalid most directory objects containing a NUL.
9747 Belt-and-suspender fix for bug 8037.
9749 o Minor features (security):
9750 - Clear keys and key-derived material left on the stack in
9751 rendservice.c and rendclient.c. Check return value of
9752 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
9753 These fixes should make us more forward-secure against cold-boot
9754 attacks and the like. Fixes bug 2385.
9755 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
9756 Irix's random() only return 15 bits; Solaris's random() returns more
9757 bits but its RAND_MAX says it only returns 15, and so on. Motivated
9758 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
9760 o Minor features (control protocol):
9761 - Add a "GETINFO signal/names" control port command. Implements
9763 - Provide default values for all options via "GETINFO config/defaults".
9764 Implements ticket 4971.
9765 - Allow an optional $ before the node identity digest in the
9766 controller command GETINFO ns/id/<identity>, for consistency with
9767 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
9768 - Add CACHED keyword to ADDRMAP events in the control protocol
9769 to indicate whether a DNS result will be cached or not. Resolves
9771 - Generate bootstrapping status update events correctly when fetching
9772 microdescriptors. Fixes bug 9927.
9774 o Minor features (path selection):
9775 - When deciding whether we have enough descriptors to build circuits,
9776 instead of looking at raw relay counts, look at which fraction
9777 of (bandwidth-weighted) paths we're able to build. This approach
9778 keeps clients from building circuits if their paths are likely to
9779 stand out statistically. The default fraction of paths needed is
9780 taken from the consensus directory; you can override it with the
9781 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
9782 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
9783 and we have GeoIP information, also exclude all nodes with unknown
9784 countries "??" and "A1". This behavior is controlled by the
9785 new GeoIPExcludeUnknown option: you can make such nodes always
9786 excluded with "GeoIPExcludeUnknown 1", and disable the feature
9787 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
9788 gets you the default behavior. Implements feature 7706.
9790 o Minor features (hidden services):
9791 - Improve circuit build timeout handling for hidden services.
9792 In particular: adjust build timeouts more accurately depending
9793 upon the number of hop-RTTs that a particular circuit type
9794 undergoes. Additionally, launch intro circuits in parallel
9795 if they timeout, and take the first one to reply as valid.
9796 - The Tor client now ignores sub-domain components of a .onion
9797 address. This change makes HTTP "virtual" hosting
9798 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
9799 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
9800 hosted on the same hidden service. Implements proposal 204.
9801 - Enable Tor to read configuration, state, and key information from
9802 a FIFO. Previously Tor would only read from files with a positive
9803 stat.st_size. Code from meejah; fixes bug 6044.
9805 o Minor features (clients):
9806 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
9807 microdescriptor-related dir requests, and only fall back to normal
9808 descriptors if none of their bridges can handle microdescriptors
9809 (as opposed to the fix in ticket 4013, which caused them to fall
9810 back to normal descriptors if *any* of their bridges preferred
9811 them). Resolves ticket 4994.
9812 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
9813 TCP ports to forward. In the past it only accepted two ports:
9814 the ORPort and the DirPort.
9816 o Minor features (protecting client timestamps):
9817 - Clients no longer send timestamps in their NETINFO cells. These were
9818 not used for anything, and they provided one small way for clients
9819 to be distinguished from each other as they moved from network to
9820 network or behind NAT. Implements part of proposal 222.
9821 - Clients now round timestamps in INTRODUCE cells down to the nearest
9822 10 minutes. If a new Support022HiddenServices option is set to 0, or
9823 if it's set to "auto" and the feature is disabled in the consensus,
9824 the timestamp is sent as 0 instead. Implements part of proposal 222.
9825 - Stop sending timestamps in AUTHENTICATE cells. This is not such
9826 a big deal from a security point of view, but it achieves no actual
9827 good purpose, and isn't needed. Implements part of proposal 222.
9828 - Reduce down accuracy of timestamps in hidden service descriptors.
9829 Implements part of proposal 222.
9831 o Minor features (bridges):
9832 - Make bridge relays check once a minute for whether their IP
9833 address has changed, rather than only every 15 minutes. Resolves
9835 - Bridge statistics now count bridge clients connecting over IPv6:
9836 bridge statistics files now list "bridge-ip-versions" and
9837 extra-info documents list "geoip6-db-digest". The control protocol
9838 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
9839 implementation by "shkoo", addressing ticket 5055.
9840 - Add a new torrc option "ServerTransportListenAddr" to let bridge
9841 operators select the address where their pluggable transports will
9842 listen for connections. Resolves ticket 7013.
9843 - Randomize the lifetime of our SSL link certificate, so censors can't
9844 use the static value for filtering Tor flows. Resolves ticket 8443;
9845 related to ticket 4014 which was included in 0.2.2.33.
9847 o Minor features (relays):
9848 - Option OutboundBindAddress can be specified multiple times and
9849 accepts IPv6 addresses. Resolves ticket 6876.
9851 o Minor features (IPv6, client side):
9852 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
9853 prefer to hand out virtual IPv6 addresses, since there are more of
9854 them and we can't run out. To override this behavior and make IPv4
9855 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
9856 or DNSPort you're using for resolving. Implements ticket 7571.
9857 - AutomapHostsOnResolve responses are now randomized, to avoid
9858 annoying situations where Tor is restarted and applications
9859 connect to the wrong addresses.
9860 - Never try more than 1000 times to pick a new virtual address when
9861 AutomapHostsOnResolve is set. That's good enough so long as we
9862 aren't close to handing out our entire virtual address space;
9863 if you're getting there, it's best to switch to IPv6 virtual
9866 o Minor features (IPv6, relay/authority side):
9867 - New config option "AuthDirHasIPv6Connectivity 1" that directory
9868 authorities should set if they have IPv6 connectivity and want to
9869 do reachability tests for IPv6 relays. Implements feature 5974.
9870 - A relay with an IPv6 OR port now sends that address in NETINFO
9871 cells (in addition to its other address). Implements ticket 6364.
9873 o Minor features (directory authorities):
9874 - Directory authorities no long accept descriptors for any version of
9875 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
9876 These versions are insecure, unsupported, or both. Implements
9878 - When directory authorities are computing thresholds for flags,
9879 never let the threshold for the Fast flag fall below 4096
9880 bytes. Also, do not consider nodes with extremely low bandwidths
9881 when deciding thresholds for various directory flags. This change
9882 should raise our threshold for Fast relays, possibly in turn
9883 improving overall network performance; see ticket 1854. Resolves
9885 - Directory authorities now include inside each vote a statement of
9886 the performance thresholds they used when assigning flags.
9887 Implements ticket 8151.
9888 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
9889 in directory authority votes to describe whether they have enough
9890 measured bandwidths to ignore advertised (relay descriptor)
9891 bandwidth claims. Resolves ticket 8711.
9893 o Minor features (path bias detection):
9894 - Path Use Bias: Perform separate accounting for successful circuit
9895 use. Keep separate statistics on stream attempt rates versus stream
9896 success rates for each guard. Provide configurable thresholds to
9897 determine when to emit log messages or disable use of guards that
9898 fail too many stream attempts. Resolves ticket 7802.
9899 - Create three levels of Path Bias log messages, as opposed to just
9900 two. These are configurable via consensus as well as via the torrc
9901 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
9902 The default values are 0.70, 0.50, and 0.30 respectively.
9903 - Separate the log message levels from the decision to drop guards,
9904 which also is available via torrc option PathBiasDropGuards.
9905 PathBiasDropGuards still defaults to 0 (off).
9906 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
9907 in combination with PathBiasExtremeRate.
9908 - Increase the default values for PathBiasScaleThreshold and
9909 PathBiasCircThreshold from (200, 20) to (300, 150).
9910 - Add in circuit usage accounting to path bias. If we try to use a
9911 built circuit but fail for any reason, it counts as path bias.
9912 Certain classes of circuits where the adversary gets to pick your
9913 destination node are exempt from this accounting. Usage accounting
9914 can be specifically disabled via consensus parameter or torrc.
9915 - Convert all internal path bias state to double-precision floating
9916 point, to avoid roundoff error and other issues.
9917 - Only record path bias information for circuits that have completed
9918 *two* hops. Assuming end-to-end tagging is the attack vector, this
9919 makes us more resilient to ambient circuit failure without any
9920 detection capability loss.
9922 o Minor features (build):
9923 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
9924 dhill. Resolves ticket 6982.
9925 - Compile on win64 using mingw64. Fixes bug 7260; patches from
9927 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
9928 separate error codes; or at least, don't break for that reason.
9929 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
9931 o Build improvements (autotools):
9932 - Warn if building on a platform with an unsigned time_t: there
9933 are too many places where Tor currently assumes that time_t can
9934 hold negative values. We'd like to fix them all, but probably
9936 - Do not report status verbosely from autogen.sh unless the -v flag
9937 is specified. Fixes issue 4664. Patch from Onizuka.
9938 - Detect and reject attempts to build Tor with threading support
9939 when OpenSSL has been compiled without threading support.
9941 - Try to detect if we are ever building on a platform where
9942 memset(...,0,...) does not set the value of a double to 0.0. Such
9943 platforms are permitted by the C standard, though in practice
9944 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
9945 currently support them, but it's better to detect them and fail
9946 than to perform erroneously.
9947 - We no longer warn so much when generating manpages from their
9949 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
9950 the signs of types during autoconf. This is better than our old
9951 approach, which didn't work when cross-compiling.
9953 o Minor features (log messages, warnings):
9954 - Detect when we're running with a version of OpenSSL other than the
9955 one we compiled with. This conflict has occasionally given people
9956 hard-to-track-down errors.
9957 - Warn users who run hidden services on a Tor client with
9958 UseEntryGuards disabled that their hidden services will be
9959 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
9960 attack which motivated Tor to support entry guards in the first
9961 place). Resolves ticket 6889.
9962 - Warn when we are binding low ports when hibernation is enabled;
9963 previously we had warned when we were _advertising_ low ports with
9964 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
9965 - Issue a warning when running with the bufferevents backend enabled.
9966 It's still not stable, and people should know that they're likely
9967 to hit unexpected problems. Closes ticket 9147.
9969 o Minor features (log messages, notices):
9970 - Refactor resolve_my_address() so it returns the method by which we
9971 decided our public IP address (explicitly configured, resolved from
9972 explicit hostname, guessed from interfaces, learned by gethostname).
9973 Now we can provide more helpful log messages when a relay guesses
9974 its IP address incorrectly (e.g. due to unexpected lines in
9975 /etc/hosts). Resolves ticket 2267.
9976 - Track how many "TAP" and "NTor" circuit handshake requests we get,
9977 and how many we complete, and log it every hour to help relay
9978 operators follow trends in network load. Addresses ticket 9658.
9980 o Minor features (log messages, diagnostics):
9981 - If we fail to free a microdescriptor because of bug 7164, log
9982 the filename and line number from which we tried to free it.
9983 - We compute the overhead from passing onionskins back and forth to
9984 cpuworkers, and report it when dumping statistics in response to
9985 SIGUSR1. Supports ticket 7291.
9986 - Add another diagnostic to the heartbeat message: track and log
9987 overhead that TLS is adding to the data we write. If this is
9988 high, we are sending too little data to SSL_write at a time.
9989 Diagnostic for bug 7707.
9990 - Log packaged cell fullness as part of the heartbeat message.
9991 Diagnosis to try to determine the extent of bug 7743.
9992 - Add more detail to a log message about relaxed timeouts, to help
9994 - When learning a fingerprint for a bridge, log its corresponding
9995 transport type. Implements ticket 7896.
9996 - Warn more aggressively when flushing microdescriptors to a
9997 microdescriptor cache fails, in an attempt to mitigate bug 8031,
9998 or at least make it more diagnosable.
9999 - Improve the log message when "Bug/attack: unexpected sendme cell
10000 from client" occurs, to help us track bug 8093.
10001 - Improve debugging output to help track down bug 8185 ("Bug:
10002 outgoing relay cell has n_chan==NULL. Dropping.")
10004 o Minor features (log messages, quieter bootstrapping):
10005 - Log fewer lines at level "notice" about our OpenSSL and Libevent
10006 versions and capabilities when everything is going right. Resolves
10007 part of ticket 6736.
10008 - Omit the first heartbeat log message, because it never has anything
10009 useful to say, and it clutters up the bootstrapping messages.
10010 Resolves ticket 6758.
10011 - Don't log about reloading the microdescriptor cache at startup. Our
10012 bootstrap warnings are supposed to tell the user when there's a
10013 problem, and our bootstrap notices say when there isn't. Resolves
10014 ticket 6759; bugfix on 0.2.2.6-alpha.
10015 - Don't log "I learned some more directory information" when we're
10016 reading cached directory information. Reserve it for when new
10017 directory information arrives in response to a fetch. Resolves
10019 - Don't complain about bootstrapping problems while hibernating.
10020 These complaints reflect a general code problem, but not one
10021 with any problematic effects (no connections are actually
10022 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
10024 o Minor features (testing):
10025 - In our testsuite, create temporary directories with a bit more
10026 entropy in their name to make name collisions less likely. Fixes
10028 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
10029 (P-256) Diffie-Hellman handshakes to src/or/bench.
10030 - Add benchmark functions to test onion handshake performance.
10033 - The DirServer option is now DirAuthority, for consistency with
10034 current naming patterns. You can still use the old DirServer form.
10036 o Minor bugfixes (protocol):
10037 - Fix the handling of a TRUNCATE cell when it arrives while the
10038 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
10039 - When a Tor client gets a "truncated" relay cell, the first byte of
10040 its payload specifies why the circuit was truncated. We were
10041 ignoring this 'reason' byte when tearing down the circuit, resulting
10042 in the controller not being told why the circuit closed. Now we
10043 pass the reason from the truncated cell to the controller. Bugfix
10044 on 0.1.2.3-alpha; fixes bug 7039.
10045 - Fix a misframing issue when reading the version numbers in a
10046 VERSIONS cell. Previously we would recognize [00 01 00 02] as
10047 'version 1, version 2, and version 0x100', when it should have
10048 only included versions 1 and 2. Fixes bug 8059; bugfix on
10049 0.2.0.10-alpha. Reported pseudonymously.
10050 - Make the format and order of STREAM events for DNS lookups
10051 consistent among the various ways to launch DNS lookups. Fixes
10052 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
10054 o Minor bugfixes (syscalls and disk interaction):
10055 - Always check the return values of functions fcntl() and
10056 setsockopt(). We don't believe these are ever actually failing in
10057 practice, but better safe than sorry. Also, checking these return
10058 values should please analysis tools like Coverity. Patch from
10059 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
10060 - Avoid double-closing the listener socket in our socketpair()
10061 replacement (used on Windows) in the case where the addresses on
10062 our opened sockets don't match what we expected. Fixes bug 9400;
10063 bugfix on 0.0.2pre7. Found by Coverity.
10064 - Correctly store microdescriptors and extrainfo descriptors that
10065 include an internal NUL byte. Fixes bug 8037; bugfix on
10066 0.2.0.1-alpha. Bug reported by "cypherpunks".
10067 - If for some reason we fail to write a microdescriptor while
10068 rebuilding the cache, do not let the annotations from that
10069 microdescriptor linger in the cache file, and do not let the
10070 microdescriptor stay recorded as present in its old location.
10071 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
10072 - Use direct writes rather than stdio when building microdescriptor
10073 caches, in an attempt to mitigate bug 8031, or at least make it
10076 o Minor fixes (config options):
10077 - Warn and fail if a server is configured not to advertise any
10078 ORPorts at all. (We need *something* to put in our descriptor,
10079 or we just won't work.)
10080 - Behave correctly when the user disables LearnCircuitBuildTimeout
10081 but doesn't tell us what they would like the timeout to be. Fixes
10082 bug 6304; bugfix on 0.2.2.14-alpha.
10083 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
10084 to start with a triple-underscore so the controller won't touch it.
10085 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
10086 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
10087 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
10088 - When autodetecting the number of CPUs, use the number of available
10089 CPUs in preference to the number of configured CPUs. Inform the
10090 user if this reduces the number of available CPUs. Fixes bug 8002;
10091 bugfix on 0.2.3.1-alpha.
10092 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
10093 - Make it an error when you set EntryNodes but disable UseGuardNodes,
10094 since it will (surprisingly to some users) ignore EntryNodes. Fixes
10095 bug 8180; bugfix on 0.2.3.11-alpha.
10096 - Avoid overflows when the user sets MaxCircuitDirtiness to a
10097 ridiculously high value, by imposing a (ridiculously high) 30-day
10098 maximum on MaxCircuitDirtiness.
10100 o Minor bugfixes (control protocol):
10101 - Stop sending a stray "(null)" in some cases for the server status
10102 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
10104 - The ADDRMAP command can no longer generate an ill-formed error
10105 code on a failed MAPADDRESS. It now says "internal" rather than
10106 an English sentence fragment with spaces in the middle. Bugfix on
10107 Tor 0.2.0.19-alpha.
10109 o Minor bugfixes (clients / edges):
10110 - When we receive a RELAY_END cell with the reason DONE, or with no
10111 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
10112 status as "connection refused". Previously we reported these cases
10113 as success but then immediately closed the connection. Fixes bug
10114 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
10115 - If the guard we choose first doesn't answer, we would try the
10116 second guard, but once we connected to the second guard we would
10117 abandon it and retry the first one, slowing down bootstrapping.
10118 The fix is to treat all our initially chosen guards as acceptable
10119 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10120 - When choosing which stream on a formerly stalled circuit to wake
10121 first, make better use of the platform's weak RNG. Previously,
10122 we had been using the % ("modulo") operator to try to generate a
10123 1/N chance of picking each stream, but this behaves badly with
10124 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
10127 o Minor bugfixes (path bias detection):
10128 - If the state file's path bias counts are invalid (presumably from a
10129 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
10130 additional checks and log messages to the scaling of Path Bias
10131 counts, in case there still are remaining issues with scaling.
10132 Should help resolve bug 8235.
10133 - Prevent rounding error in path bias counts when scaling
10134 them down, and use the correct scale factor default. Also demote
10135 some path bias related log messages down a level and make others
10136 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
10137 - Remove a source of rounding error during path bias count scaling;
10138 don't count cannibalized circuits as used for path bias until we
10139 actually try to use them; and fix a circuit_package_relay_cell()
10140 warning message about n_chan==NULL. Fixes bug 7802.
10141 - Paste the description for PathBias parameters from the man
10142 page into or.h, so the code documents them too. Fixes bug 7982;
10143 bugfix on 0.2.3.17-beta.
10145 o Minor bugfixes (relays):
10146 - Stop trying to resolve our hostname so often (e.g. every time we
10147 think about doing a directory fetch). Now we reuse the cached
10148 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
10149 and 2410 (bugfix on 0.1.2.2-alpha).
10150 - When examining the list of network interfaces to find our address,
10151 do not consider non-running or disabled network interfaces. Fixes
10152 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10154 o Minor bugfixes (blocking resistance):
10155 - Only disable TLS session ticket support when running as a TLS
10156 server. Now clients will blend better with regular Firefox
10157 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
10159 o Minor bugfixes (IPv6):
10160 - Use square brackets around IPv6 addresses in numerous places
10161 that needed them, including log messages, HTTPS CONNECT proxy
10162 requests, TransportProxy statefile entries, and pluggable transport
10163 extra-info lines. Fixes bug 7011; patch by David Fifield.
10165 o Minor bugfixes (directory authorities):
10166 - Reject consensus votes with more than 64 known-flags. We aren't even
10167 close to that limit yet, and our code doesn't handle it correctly.
10168 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
10169 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
10170 bugfix on 0.2.0.3-alpha.
10172 o Minor bugfixes (memory leaks):
10173 - Avoid leaking memory if we fail to compute a consensus signature
10174 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
10175 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
10176 on 0.2.1.1-alpha; fixes bug 7816.
10177 - Fix a memory leak during safe-cookie controller authentication.
10178 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
10179 - Free some more still-in-use memory at exit, to make hunting for
10180 memory leaks easier. Resolves bug 7029.
10182 o Minor bugfixes (code correctness):
10183 - Increase the width of the field used to remember a connection's
10184 link protocol version to two bytes. Harmless for now, since the
10185 only currently recognized versions are one byte long. Reported
10186 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
10187 - Fix a crash when debugging unit tests on Windows: deallocate a
10188 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
10189 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
10190 - When detecting the largest possible file descriptor (in order to
10191 close all file descriptors when launching a new program), actually
10192 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
10193 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
10195 - Avoid a crash if we fail to generate an extrainfo descriptor.
10196 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
10197 this is CID 718634.
10198 - Avoid an off-by-one error when checking buffer boundaries when
10199 formatting the exit status of a pluggable transport helper.
10200 This is probably not an exploitable bug, but better safe than
10201 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10203 - Get rid of a couple of harmless clang warnings, where we compared
10204 enums to ints. These warnings are newly introduced in clang 3.2.
10206 o Minor bugfixes (code cleanliness):
10207 - Avoid use of reserved identifiers in our C code. The C standard
10208 doesn't like us declaring anything that starts with an
10209 underscore, so let's knock it off before we get in trouble. Fix
10210 for bug 1031; bugfix on the first Tor commit.
10211 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
10212 with large values. This situation was untriggered, but nevertheless
10213 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
10214 - Fix an impossible buffer overrun in the AES unit tests. Fixes
10215 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
10216 - Fix handling of rendezvous client authorization types over 8.
10217 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
10218 - Remove a couple of extraneous semicolons that were upsetting the
10219 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
10220 bugfix on 0.2.2.1-alpha.
10221 - When complaining about a client port on a public address, log
10222 which address we're complaining about. Fixes bug 4020; bugfix on
10223 0.2.3.3-alpha. Patch by Tom Fitzhenry.
10225 o Minor bugfixes (log messages, warnings):
10226 - If we encounter a write failure on a SOCKS connection before we
10227 finish our SOCKS handshake, don't warn that we closed the
10228 connection before we could send a SOCKS reply. Fixes bug 8427;
10229 bugfix on 0.1.0.1-rc.
10230 - Fix a directory authority warn caused when we have a large amount
10231 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
10232 - Downgrade "Failed to hand off onionskin" messages to "debug"
10233 severity, since they're typically redundant with the "Your computer
10234 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
10235 - Avoid spurious warnings when configuring multiple client ports of
10236 which only some are nonlocal. Previously, we had claimed that some
10237 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
10240 o Minor bugfixes (log messages, other):
10241 - Fix log messages and comments to avoid saying "GMT" when we mean
10242 "UTC". Fixes bug 6113.
10243 - When rejecting a configuration because we were unable to parse a
10244 quoted string, log an actual error message. Fixes bug 7950; bugfix
10246 - Correctly recognize that [::1] is a loopback address. Fixes
10247 bug 8377; bugfix on 0.2.1.3-alpha.
10248 - Don't log inappropriate heartbeat messages when hibernating: a
10249 hibernating node is _expected_ to drop out of the consensus,
10250 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
10251 bugfix on 0.2.3.1-alpha.
10252 - Eliminate several instances where we use "Nickname=ID" to refer to
10253 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
10254 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
10257 o Minor bugfixes (build):
10258 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
10259 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
10260 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
10262 o Documentation fixes:
10263 - Make the torify manpage no longer refer to tsocks; torify hasn't
10264 supported tsocks since 0.2.3.14-alpha.
10265 - Make the tor manpage no longer reference tsocks.
10266 - Fix the GeoIPExcludeUnknown documentation to refer to
10267 ExcludeExitNodes rather than the currently nonexistent
10268 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
10269 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
10271 - Say "KBytes" rather than "KB" in the man page (for various values
10272 of K), to further reduce confusion about whether Tor counts in
10273 units of memory or fractions of units of memory. Resolves ticket 7054.
10274 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
10275 names match. Fixes bug 7768.
10276 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
10277 message is logged at notice, not at info.
10278 - Clarify the usage and risks of setting the ContactInfo torrc line
10279 for your relay or bridge. Resolves ticket 9854.
10280 - Add anchors to the manpage so we can link to the html version of
10281 the documentation for specific options. Resolves ticket 9866.
10282 - Replace remaining references to DirServer in man page and
10283 log entries. Resolves ticket 10124.
10285 o Removed features:
10286 - Stop exporting estimates of v2 and v3 directory traffic shares
10287 in extrainfo documents. They were unneeded and sometimes inaccurate.
10288 Also stop exporting any v2 directory request statistics. Resolves
10290 - Drop support for detecting and warning about versions of Libevent
10291 before 1.3e. Nothing reasonable ships with them any longer; warning
10292 the user about them shouldn't be needed. Resolves ticket 6826.
10293 - Now that all versions before 0.2.2.x are disallowed, we no longer
10294 need to work around their missing features. Remove a bunch of
10295 compatibility code.
10298 - The tor-tsocks.conf is no longer distributed or installed. We
10299 recommend that tsocks users use torsocks instead. Resolves
10301 - Remove some of the older contents of doc/ as obsolete; move others
10302 to torspec.git. Fixes bug 8965.
10304 o Code simplification:
10305 - Avoid using character buffers when constructing most directory
10306 objects: this approach was unwieldy and error-prone. Instead,
10307 build smartlists of strings, and concatenate them when done.
10308 - Rename "isin" functions to "contains", for grammar. Resolves
10310 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
10311 with the natural logarithm function from the system libm. Resolves
10313 - Start using OpenBSD's implementation of queue.h, so that we don't
10314 need to hand-roll our own pointer and list structures whenever we
10315 need them. (We can't rely on a sys/queue.h, since some operating
10316 systems don't have them, and the ones that do have them don't all
10317 present the same extensions.)
10318 - Start using OpenBSD's implementation of queue.h (originally by
10320 - Enhance our internal sscanf replacement so that we can eliminate
10321 the last remaining uses of the system sscanf. (Though those uses
10322 of sscanf were safe, sscanf itself is generally error prone, so
10323 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
10325 - Replace all calls to snprintf() outside of src/ext with
10326 tor_snprintf(). Also remove the #define to replace snprintf with
10327 _snprintf on Windows; they have different semantics, and all of
10328 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
10331 - Add a wrapper function for the common "log a message with a
10333 - Split the onion.c file into separate modules for the onion queue
10334 and the different handshakes it supports.
10335 - Move the client-side address-map/virtual-address/DNS-cache code
10336 out of connection_edge.c into a new addressmap.c module.
10337 - Move the entry node code from circuitbuild.c to its own file.
10338 - Move the circuit build timeout tracking code from circuitbuild.c
10340 - Source files taken from other packages now reside in src/ext;
10341 previously they were scattered around the rest of Tor.
10342 - Move the generic "config" code into a new file, and have "config.c"
10343 hold only torrc- and state-related code. Resolves ticket 6823.
10344 - Move the core of our "choose a weighted element at random" logic
10345 into its own function, and give it unit tests. Now the logic is
10346 testable, and a little less fragile too.
10347 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
10348 - Move last_reachable and testing_since from routerinfo_t to node_t.
10349 Implements ticket 5529.
10350 - Add replaycache_t structure, functions and unit tests, then refactor
10351 rend_service_introduce() to be more clear to read, improve, debug,
10352 and test. Resolves bug 6177.
10355 - Remove some now-needless code that tried to aggressively flush
10356 OR connections as data was added to them. Since 0.2.0.1-alpha, our
10357 cell queue logic has saved us from the failure mode that this code
10358 was supposed to prevent. Removing this code will limit the number
10359 of baroque control flow paths through Tor's network logic. Reported
10360 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
10361 - Remove unused code for parsing v1 directories and "running routers"
10362 documents. Fixes bug 6887.
10363 - Remove the marshalling/unmarshalling code for sending requests to
10364 cpuworkers over a socket, and instead just send structs. The
10365 recipient will always be the same Tor binary as the sender, so
10366 any encoding is overkill.
10367 - Remove the testing_since field of node_t, which hasn't been used
10368 for anything since 0.2.0.9-alpha.
10369 - Finally remove support for malloc_good_size and malloc_usable_size.
10370 We had hoped that these functions would let us eke a little more
10371 memory out of our malloc implementation. Unfortunately, the only
10372 implementations that provided these functions are also ones that
10373 are already efficient about not overallocation: they never got us
10374 more than 7 or so bytes per allocation. Removing them saves us a
10375 little code complexity and a nontrivial amount of build complexity.
10378 Changes in version 0.2.3.25 - 2012-11-19
10379 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
10380 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
10381 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
10382 programmer, and friend. Unstinting in his dedication to the cause of
10383 freedom, he inspired and helped many of us as we began our work on
10384 anonymity, and inspires us still. Please honor his memory by writing
10385 software to protect people's freedoms, and by helping others to do so.
10387 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
10388 significantly reduced directory overhead (via microdescriptors),
10389 enormous crypto performance improvements for fast relays on new
10390 enough hardware, a new v3 TLS handshake protocol that can better
10391 resist fingerprinting, support for protocol obfuscation plugins (aka
10392 pluggable transports), better scalability for hidden services, IPv6
10393 support for bridges, performance improvements like allowing clients
10394 to skip the first round-trip on the circuit ("optimistic data") and
10395 refilling token buckets more often, a new "stream isolation" design
10396 to isolate different applications on different circuits, and many
10397 stability, security, and privacy fixes.
10399 Major features (v3 directory protocol):
10400 - Clients now use microdescriptors instead of regular descriptors
10401 to build circuits. Microdescriptors are authority-generated
10402 summaries of regular descriptors' contents, designed to change very
10403 rarely (see proposal 158 for details). This feature is designed
10404 to save bandwidth, especially for clients on slow internet
10405 connections. Use "UseMicrodescriptors 0" to disable it.
10406 - Caches now download, cache, and serve microdescriptors, as well
10407 as multiple "flavors" of the consensus, including a flavor that
10408 describes microdescriptors.
10410 o Major features (build hardening):
10411 - Enable gcc and ld hardening by default. Resolves ticket 5210.
10413 o Major features (relay scaling):
10414 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
10415 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
10416 vectorized AES implementations as appropriate. These can be much,
10417 much faster than other AES implementations.
10418 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
10419 implementation. It makes AES_CTR about 7% faster than our old one
10420 (which was about 10% faster than the one OpenSSL used to provide).
10421 Resolves ticket 4526.
10422 - Use OpenSSL's EVP interface for AES encryption, so that all AES
10423 operations can use hardware acceleration (if present). Resolves
10425 - Unconditionally use OpenSSL's AES implementation instead of our
10426 old built-in one. OpenSSL's AES has been better for a while, and
10427 relatively few servers should still be on any version of OpenSSL
10428 that doesn't have good optimized assembly AES.
10430 o Major features (blocking resistance):
10431 - Update TLS cipher list to match Firefox 8 and later. Resolves
10433 - Remove support for clients falsely claiming to support standard
10434 ciphersuites that they can actually provide. As of modern OpenSSL
10435 versions, it's not necessary to fake any standard ciphersuite,
10436 and doing so prevents us from using better ciphersuites in the
10437 future, since servers can't know whether an advertised ciphersuite
10438 is really supported or not. Some hosts -- notably, ones with very
10439 old versions of OpenSSL or where OpenSSL has been built with ECC
10440 disabled -- will stand out because of this change; TBB users should
10441 not be affected. Implements the client side of proposal 198.
10442 - Implement a new handshake protocol (v3) for authenticating Tors to
10443 each other over TLS. It should be more resistant to fingerprinting
10444 than previous protocols, and should require less TLS hacking for
10445 future Tor implementations. Implements proposal 176.
10446 - Allow variable-length padding cells, to disguise the length of
10447 Tor's TLS records. Implements part of proposal 184.
10448 - While we're trying to bootstrap, record how many TLS connections
10449 fail in each state, and report which states saw the most failures
10450 in response to any bootstrap failures. This feature may speed up
10451 diagnosis of censorship events. Implements ticket 3116.
10453 o Major features (pluggable transports):
10454 - Clients and bridges can now be configured to use a separate
10455 "transport" proxy. This approach makes the censorship arms race
10456 easier by allowing bridges to use protocol obfuscation plugins.
10457 Implements proposal 180 (tickets 2841 and 3472).
10459 o Major features (DoS resistance):
10460 - Now that Tor 0.2.0.x is completely deprecated, enable the final
10461 part of "Proposal 110: Avoiding infinite length circuits" by
10462 refusing all circuit-extend requests that do not use a relay_early
10463 cell. This change helps Tor resist a class of denial-of-service
10464 attacks by limiting the maximum circuit length.
10465 - Tear down the circuit if we get an unexpected SENDME cell. Clients
10466 could use this trick to make their circuits receive cells faster
10467 than our flow control would have allowed, or to gum up the network,
10468 or possibly to do targeted memory denial-of-service attacks on
10469 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
10470 from July 2002, before the release of Tor 0.0.0.
10472 o Major features (hidden services):
10473 - Adjust the number of introduction points that a hidden service
10474 will try to maintain based on how long its introduction points
10475 remain in use and how many introductions they handle. Fixes
10477 - Add a "tor2web mode" for clients that want to connect to hidden
10478 services non-anonymously (and possibly more quickly). As a safety
10479 measure to try to keep users from turning this on without knowing
10480 what they are doing, tor2web mode must be explicitly enabled at
10481 compile time, and a copy of Tor compiled to run in tor2web mode
10482 cannot be used as a normal Tor client. Implements feature 2553.
10484 o Major features (IPv6):
10485 - Clients can now connect to private bridges over IPv6. Bridges
10486 still need at least one IPv4 address in order to connect to
10487 other relays. Note that we don't yet handle the case where the
10488 user has two bridge lines for the same bridge (one IPv4, one
10489 IPv6). Implements parts of proposal 186.
10491 o Major features (directory authorities):
10492 - Use a more secure consensus parameter voting algorithm. Now at
10493 least three directory authorities or a majority of them must
10494 vote on a given parameter before it will be included in the
10495 consensus. Implements proposal 178.
10496 - Remove the artificially low cutoff of 20KB to guarantee the Fast
10497 flag. In the past few years the average relay speed has picked
10498 up, and while the "top 7/8 of the network get the Fast flag" and
10499 "all relays with 20KB or more of capacity get the Fast flag" rules
10500 used to have the same result, now the top 7/8 of the network has
10501 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
10503 o Major features (performance):
10504 - Exit nodes now accept and queue data on not-yet-connected streams.
10505 Previously, the client wasn't allowed to send data until the
10506 stream was connected, which slowed down all connections. This
10507 change will enable clients to perform a "fast-start" on streams
10508 and send data without having to wait for a confirmation that the
10509 stream has opened. Patch from Ian Goldberg; implements the server
10510 side of Proposal 174.
10511 - When using an exit relay running 0.2.3.x, clients can now
10512 "optimistically" send data before the exit relay reports that
10513 the stream has opened. This saves a round trip when starting
10514 connections where the client speaks first (such as web browsing).
10515 This behavior is controlled by a consensus parameter (currently
10516 disabled). To turn it on or off manually, use the "OptimisticData"
10517 torrc option. Implements proposal 181; code by Ian Goldberg.
10518 - Add a new TokenBucketRefillInterval option to refill token buckets
10519 more frequently than once per second. This should improve network
10520 performance, alleviate queueing problems, and make traffic less
10521 bursty. Implements proposal 183; closes ticket 3630. Design by
10522 Florian Tschorsch and Björn Scheuermann; implementation by
10524 - Raise the threshold of server descriptors needed (75%) and exit
10525 server descriptors needed (50%) before we will declare ourselves
10526 bootstrapped. This will make clients start building circuits a
10527 little later, but makes the initially constructed circuits less
10528 skewed and less in conflict with further directory fetches. Fixes
10531 o Major features (relays):
10532 - Relays now try regenerating and uploading their descriptor more
10533 frequently if they are not listed in the consensus, or if the
10534 version of their descriptor listed in the consensus is too
10535 old. This fix should prevent situations where a server declines
10536 to re-publish itself because it has done so too recently, even
10537 though the authorities decided not to list its recent-enough
10538 descriptor. Fix for bug 3327.
10540 o Major features (stream isolation):
10541 - You can now configure Tor so that streams from different
10542 applications are isolated on different circuits, to prevent an
10543 attacker who sees your streams as they leave an exit node from
10544 linking your sessions to one another. To do this, choose some way
10545 to distinguish the applications: have them connect to different
10546 SocksPorts, or have one of them use SOCKS4 while the other uses
10547 SOCKS5, or have them pass different authentication strings to the
10548 SOCKS proxy. Then, use the new SocksPort syntax to configure the
10549 degree of isolation you need. This implements Proposal 171.
10550 - There's a new syntax for specifying multiple client ports (such as
10551 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
10552 multiple *Port entries with full addr:port syntax on each.
10553 The old *ListenAddress format is still supported, but you can't
10554 mix it with the new *Port syntax.
10556 o Major features (bufferevents):
10557 - Tor can now optionally build with the "bufferevents" buffered IO
10558 backend provided by Libevent 2. To use this feature, make sure you
10559 have the latest possible version of Libevent, and pass the
10560 --enable-bufferevents flag to configure when building Tor from
10561 source. This feature will make our networking code more flexible,
10562 let us stack layers on each other, and let us use more efficient
10563 zero-copy transports where available.
10564 - Add experimental support for running on Windows with IOCP and no
10565 kernel-space socket buffers. This feature is controlled by a new
10566 "UserspaceIOCPBuffers" config option (off by default), which has
10567 no effect unless Tor has been built with bufferevents enabled,
10568 you're running on Windows, and you've set "DisableIOCP 0". In the
10569 long run, this may help solve or mitigate bug 98.
10571 o Major features (path selection):
10572 - The EntryNodes option can now include country codes like {de} or IP
10573 addresses or network masks. Previously we had disallowed these
10574 options because we didn't have an efficient way to keep the list up
10575 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
10578 o Major features (port forwarding):
10579 - Add support for automatic port mapping on the many home routers
10580 that support NAT-PMP or UPnP. To build the support code, you'll
10581 need to have the libnatpnp library and/or the libminiupnpc library,
10582 and you'll need to enable the feature specifically by passing
10583 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
10584 it on, use the new PortForwarding option.
10586 o Major features (logging):
10587 - Add a new 'Heartbeat' log message type to periodically log a message
10588 describing Tor's status at level Notice. This feature is meant for
10589 operators who log at notice, and want to make sure that their Tor
10590 server is still working. Implementation by George Kadianakis.
10591 - Make logging resolution configurable with a new LogTimeGranularity
10592 option, and change the default from 1 millisecond to 1 second.
10593 Implements enhancement 1668.
10595 o Major features (other):
10596 - New "DisableNetwork" config option to prevent Tor from launching any
10597 connections or accepting any connections except on a control port.
10598 Bundles and controllers can set this option before letting Tor talk
10599 to the rest of the network, for example to prevent any connections
10600 to a non-bridge address. Packages like Orbot can also use this
10601 option to instruct Tor to save power when the network is off.
10602 - Try to use system facilities for enumerating local interface
10603 addresses, before falling back to our old approach (which was
10604 binding a UDP socket, and calling getsockname() on it). That
10605 approach was scaring OS X users whose draconian firewall
10606 software warned about binding to UDP sockets regardless of
10607 whether packets were sent. Now we try to use getifaddrs(),
10608 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
10609 system supports. Resolves ticket 1827.
10610 - Add experimental support for a "defaults" torrc file to be parsed
10611 before the regular torrc. Torrc options override the defaults file's
10612 options in the same way that the command line overrides the torrc.
10613 The SAVECONF controller command saves only those options which
10614 differ between the current configuration and the defaults file. HUP
10615 reloads both files. Implements task 4552.
10617 o New directory authorities:
10618 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
10619 authority. Closes ticket 5749.
10621 o Security/privacy fixes:
10622 - Avoid read-from-freed-memory and double-free bugs that could occur
10623 when a DNS request fails while launching it. Fixes bug 6480;
10624 bugfix on 0.2.0.1-alpha.
10625 - Reject any attempt to extend to an internal address. Without
10626 this fix, a router could be used to probe addresses on an internal
10627 network to see whether they were accepting connections. Fixes bug
10628 6710; bugfix on 0.0.8pre1.
10629 - Close any connection that sends unrecognized junk before the TLS
10630 handshake. Solves an issue noted in bug 4369.
10631 - The advertised platform of a relay now includes only its operating
10632 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
10633 its service pack level (for Windows) or its CPU architecture
10634 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
10635 can insert an extra string in the platform line by setting the
10636 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
10637 - Disable TLS session tickets. OpenSSL's implementation was giving
10638 our TLS session keys the lifetime of our TLS context objects, when
10639 perfect forward secrecy would want us to discard anything that
10640 could decrypt a link connection as soon as the link connection
10641 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10642 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10643 - Tor tries to wipe potentially sensitive data after using it, so
10644 that if some subsequent security failure exposes Tor's memory,
10645 the damage will be limited. But we had a bug where the compiler
10646 was eliminating these wipe operations when it decided that the
10647 memory was no longer visible to a (correctly running) program,
10648 hence defeating our attempt at defense in depth. We fix that
10649 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
10650 is unlikely to optimize away. Future versions of Tor may use
10651 a less ridiculously heavy approach for this. Fixes bug 7352.
10652 Reported in an article by Andrey Karpov.
10654 o Major bugfixes (crashes and asserts):
10655 - Avoid a pair of double-free and use-after-mark bugs that can
10656 occur with certain timings in canceled and re-received DNS
10657 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
10658 - Fix a denial of service attack by which any directory authority
10659 could crash all the others, or by which a single v2 directory
10660 authority could crash everybody downloading v2 directory
10661 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
10662 - Fix an assert that directory authorities could trigger on sighup
10663 during some configuration state transitions. We now don't treat
10664 it as a fatal error when the new descriptor we just generated in
10665 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
10666 - Avoid segfault when starting up having run with an extremely old
10667 version of Tor and parsing its state file. Fixes bug 6801; bugfix
10670 o Major bugfixes (clients):
10671 - If we are unable to find any exit that supports our predicted ports,
10672 stop calling them predicted, so that we don't loop and build
10673 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
10674 which introduced predicted ports.
10675 - Check at each new consensus whether our entry guards were picked
10676 long enough ago that we should rotate them. Previously, we only
10677 did this check at startup, which could lead to us holding a guard
10678 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
10679 - When fetching a bridge descriptor from a bridge authority,
10680 always do so anonymously, whether we have been able to open
10681 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
10682 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
10683 but we'll need to wait for bug 6010 before it's actually usable.
10685 o Major bugfixes (directory voting):
10686 - Check more thoroughly to prevent a rogue authority from
10687 double-voting on any consensus directory parameter. Previously,
10688 authorities would crash in this case if the total number of
10689 votes for any parameter exceeded the number of active voters,
10690 but would let it pass otherwise. Partially fixes bug 5786; bugfix
10692 - When computing weight parameters, behave more robustly in the
10693 presence of a bad bwweightscale value. Previously, the authorities
10694 would crash if they agreed on a sufficiently broken weight_scale
10695 value; now, they use a reasonable default and carry on. Fixes the
10696 rest of bug 5786; bugfix on 0.2.2.17-alpha.
10697 - If authorities are unable to get a v2 consensus document from other
10698 directory authorities, they no longer fall back to fetching
10699 them from regular directory caches. Fixes bug 5635; bugfix on
10700 0.2.2.26-beta, where routers stopped downloading v2 consensus
10701 documents entirely.
10703 o Major bugfixes (relays):
10704 - Fix a bug handling SENDME cells on nonexistent streams that could
10705 result in bizarre window values. Report and patch contributed
10706 pseudonymously. Fixes part of bug 6271. This bug was introduced
10707 before the first Tor release, in svn commit r152.
10708 - Don't update the AccountingSoftLimitHitAt state file entry whenever
10709 tor gets started. This prevents a wrong average bandwidth
10710 estimate, which would cause relays to always start a new accounting
10711 interval at the earliest possible moment. Fixes bug 2003; bugfix
10712 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
10713 immensely in tracking this bug down.
10714 - Fix a possible crash bug when checking for deactivated circuits
10715 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10716 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
10717 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
10718 connections. This change should allow busy exit relays to stop
10719 running out of available sockets as quickly. Fixes bug 4950;
10720 bugfix on 0.2.2.26-beta.
10722 o Major bugfixes (blocking resistance):
10723 - Bridges no longer include their address in NETINFO cells on outgoing
10724 OR connections, to allow them to blend in better with clients.
10725 Removes another avenue for enumerating bridges. Reported by
10726 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
10727 cells were introduced.
10728 - Warn the user when HTTPProxy, but no other proxy type, is
10729 configured. This can cause surprising behavior: it doesn't send
10730 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
10731 directory traffic only. Resolves ticket 4663.
10733 o Major bugfixes (hidden services):
10734 - Improve hidden service robustness: when an attempt to connect to
10735 a hidden service ends, be willing to refetch its hidden service
10736 descriptors from each of the HSDir relays responsible for them
10737 immediately. Previously, we would not consider refetching the
10738 service's descriptors from each HSDir for 15 minutes after the last
10739 fetch, which was inconvenient if the hidden service was not running
10740 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
10741 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
10742 They used to check that the timestamp was within 30 minutes
10743 of their system clock, so they could cap the size of their
10744 replay-detection cache, but that approach unnecessarily refused
10745 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
10746 the v3 intro-point protocol (the first one which sent a timestamp
10747 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
10748 - When one of a hidden service's introduction points appears to be
10749 unreachable, stop trying it. Previously, we would keep trying
10750 to build circuits to the introduction point until we lost the
10751 descriptor, usually because the user gave up and restarted Tor.
10752 Fixes part of bug 3825.
10754 o Changes to default torrc file:
10755 - Stop listing "socksport 9050" in torrc.sample. We open a socks
10756 port on 9050 by default anyway, so this should not change anything
10758 - Stop mentioning the deprecated *ListenAddress options in
10759 torrc.sample. Fixes bug 5438.
10760 - Document unit of bandwidth-related options in sample torrc.
10762 - Fix broken URLs in the sample torrc file, and tell readers about
10763 the OutboundBindAddress, ExitPolicyRejectPrivate, and
10764 PublishServerDescriptor options. Addresses bug 4652.
10766 o Minor features (directory authorities):
10767 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
10768 change when the authority is deciding whether to accept a newly
10769 uploaded descriptor. Implements ticket 6423.
10770 - Directory authorities are now a little more lenient at accepting
10771 older router descriptors, or newer router descriptors that don't
10772 make big changes. This should help ameliorate past and future
10773 issues where routers think they have uploaded valid descriptors,
10774 but the authorities don't think so. Fix for ticket 2479.
10775 - Authority operators can now vote for all relays in a given
10776 set of countries to be BadDir/BadExit/Invalid/Rejected.
10777 - Provide two consensus parameters (FastFlagMinThreshold and
10778 FastFlagMaxThreshold) to control the range of allowable bandwidths
10779 for the Fast directory flag. These allow authorities to run
10780 experiments on appropriate requirements for being a "Fast" node.
10781 The AuthDirFastGuarantee config value still applies. Implements
10784 o Minor features (bridges / bridge authorities):
10785 - Make bridge SSL certificates a bit more stealthy by using random
10786 serial numbers, in the same fashion as OpenSSL when generating
10787 self-signed certificates. Implements ticket 4584.
10788 - Tag a bridge's descriptor as "never to be sent unencrypted".
10789 This shouldn't matter, since bridges don't open non-anonymous
10790 connections to the bridge authority and don't allow unencrypted
10791 directory connections from clients, but we might as well make
10792 sure. Closes bug 5139.
10793 - The Bridge Authority now writes statistics on how many bridge
10794 descriptors it gave out in total, and how many unique descriptors
10795 it gave out. It also lists how often the most and least commonly
10796 fetched descriptors were given out, as well as the median and
10797 25th/75th percentile. Implements tickets 4200 and 4294.
10799 o Minor features (IPv6):
10800 - Make the code that clients use to detect an address change be
10801 IPv6-aware, so that it won't fill clients' logs with error
10802 messages when trying to get the IPv4 address of an IPv6
10803 connection. Implements ticket 5537.
10804 - Relays now understand an IPv6 address when they get one from a
10805 directory server. Resolves ticket 4875.
10807 o Minor features (hidden services):
10808 - Expire old or over-used hidden service introduction points.
10809 Required by fix for bug 3460.
10810 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
10811 public key replay-detection cache from 60 minutes to 5 minutes. This
10812 replay-detection cache is now used only to detect multiple
10813 INTRODUCE2 cells specifying the same rendezvous point, so we can
10814 avoid launching multiple simultaneous attempts to connect to it.
10815 - When a hidden service's introduction point times out, consider
10816 trying it again during the next attempt to connect to the
10817 HS. Previously, we would not try it again unless a newly fetched
10818 descriptor contained it. Required by fixes for bugs 1297 and 3825.
10820 o Minor features (relays):
10821 - Relays now include a reason for regenerating their descriptors
10822 in an HTTP header when uploading to the authorities. This will
10823 make it easier to debug descriptor-upload issues in the future.
10824 - Turn on directory request statistics by default and include them in
10825 extra-info descriptors. Don't break if we have no GeoIP database.
10826 - Replace files in stats/ rather than appending to them. Now that we
10827 include statistics in extra-info descriptors, it makes no sense to
10828 keep old statistics forever. Implements ticket 2930.
10829 - Relays that set "ConnDirectionStatistics 1" write statistics on the
10830 bidirectional use of connections to disk every 24 hours.
10831 - Add a GeoIP file digest to the extra-info descriptor. Implements
10834 o Minor features (new config options):
10835 - New config option "DynamicDHGroups" (disabled by default) provides
10836 each bridge with a unique prime DH modulus to be used during
10837 SSL handshakes. This option attempts to help against censors
10838 who might use the Apache DH modulus as a static identifier for
10839 bridges. Addresses ticket 4548.
10840 - New config option "DisableDebuggerAttachment" (on by default)
10841 to prevent basic debugging attachment attempts by other processes.
10842 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
10843 - Ordinarily, Tor does not count traffic from private addresses (like
10844 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
10845 There is now a new option, CountPrivateBandwidth, to disable this
10846 behavior. Patch from Daniel Cagara.
10848 o Minor features (different behavior for old config options):
10849 - Allow MapAddress directives to specify matches against super-domains,
10850 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
10851 Implements issue 933.
10852 - Don't disable the DirPort when we cannot exceed our AccountingMax
10853 limit during this interval because the effective bandwidthrate is
10854 low enough. This is useful in a situation where AccountMax is only
10855 used as an additional safeguard or to provide statistics.
10856 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
10857 implements ticket 3439.
10858 - When configuring a large set of nodes in EntryNodes, and there are
10859 enough of them listed as Guard so that we don't need to consider
10860 the non-guard entries, prefer the ones listed with the Guard flag.
10861 - If you set the NumCPUs option to 0, Tor will now try to detect how
10862 many CPUs you have. This is the new default behavior.
10863 - The NodeFamily option -- which let you declare that you want to
10864 consider nodes to be part of a family whether they list themselves
10865 that way or not -- now allows IP address ranges and country codes.
10867 o Minor features (new command-line config behavior):
10868 - Slightly change behavior of "list" options (that is, config
10869 options that can appear more than once) when they appear both in
10870 torrc and on the command line. Previously, the command-line options
10871 would be appended to the ones from torrc. Now, the command-line
10872 options override the torrc options entirely. This new behavior
10873 allows the user to override list options (like exit policies and
10874 ports to listen on) from the command line, rather than simply
10875 appending to the list.
10876 - You can get the old (appending) command-line behavior for "list"
10877 options by prefixing the option name with a "+".
10878 - You can remove all the values for a "list" option from the command
10879 line without adding any new ones by prefixing the option name
10882 o Minor features (controller, new events):
10883 - Extend the control protocol to report flags that control a circuit's
10884 path selection in CIRC events and in replies to 'GETINFO
10885 circuit-status'. Implements part of ticket 2411.
10886 - Extend the control protocol to report the hidden service address
10887 and current state of a hidden-service-related circuit in CIRC
10888 events and in replies to 'GETINFO circuit-status'. Implements part
10890 - Include the creation time of a circuit in CIRC and CIRC2
10891 control-port events and the list produced by the 'GETINFO
10892 circuit-status' control-port command.
10893 - Add a new CONF_CHANGED event so that controllers can be notified
10894 of any configuration changes made by other controllers, or by the
10895 user. Implements ticket 1692.
10896 - Add a new SIGNAL event to the controller interface so that
10897 controllers can be notified when Tor handles a signal. Resolves
10898 issue 1955. Patch by John Brooks.
10900 o Minor features (controller, new getinfo options):
10901 - Expose our view of whether we have gone dormant to the controller,
10902 via a new "GETINFO dormant" value. Torbutton and other controllers
10903 can use this to avoid doing periodic requests through Tor while
10904 it's dormant (bug 4718). Resolves ticket 5954.
10905 - Add a new GETINFO option to get total bytes read and written. Patch
10906 from pipe, revised by atagar. Resolves ticket 2345.
10907 - Implement new GETINFO controller fields to provide information about
10908 the Tor process's pid, euid, username, and resource limits.
10910 o Minor features (controller, other):
10911 - Allow controllers to request an event notification whenever a
10912 circuit is cannibalized or its purpose is changed. Implements
10913 part of ticket 3457.
10914 - Use absolute path names when reporting the torrc filename in the
10915 control protocol, so a controller can more easily find the torrc
10916 file. Resolves bug 1101.
10917 - When reporting the path to the cookie file to the controller,
10918 give an absolute path. Resolves ticket 4881.
10920 o Minor features (log messages):
10921 - Add more information to a log statement that might help track down
10922 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
10923 non-IP address" messages (or any Bug messages, for that matter!),
10924 please let us know about it.
10925 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
10926 EntryNodes will have no effect. Resolves issue 2571.
10927 - Try to make the introductory warning message that Tor prints on
10928 startup more useful for actually finding help and information.
10929 Resolves ticket 2474.
10930 - When the system call to create a listener socket fails, log the
10931 error message explaining why. This may help diagnose bug 4027.
10933 o Minor features (other):
10934 - When we fail to initialize Libevent, retry with IOCP disabled so we
10935 don't need to turn on multi-threading support in Libevent, which in
10936 turn requires a working socketpair(). This is a workaround for bug
10937 4457, which affects Libevent versions from 2.0.1-alpha through
10939 - When starting as root and then changing our UID via the User
10940 control option, and we have a ControlSocket configured, make sure
10941 that the ControlSocket is owned by the same account that Tor will
10942 run under. Implements ticket 3421; fix by Jérémy Bobbio.
10943 - Accept attempts to include a password authenticator in the
10944 handshake, as supported by SOCKS5. This handles SOCKS clients that
10945 don't know how to omit a password when authenticating. Resolves
10947 - Check for and recover from inconsistency in the microdescriptor
10948 cache. This will make it harder for us to accidentally free a
10949 microdescriptor without removing it from the appropriate data
10950 structures. Fixes issue 3135; issue noted by "wanoskarnet".
10951 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
10953 o Minor bugfixes (code security):
10954 - Prevent a null-pointer dereference when receiving a data cell
10955 for a nonexistent stream when the circuit in question has an
10956 empty deliver window. We don't believe this is triggerable,
10957 since we don't currently allow deliver windows to become empty,
10958 but the logic is tricky enough that it's better to make the code
10959 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
10960 - Fix a (harmless) integer overflow in cell statistics reported by
10961 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
10962 - Fix our implementation of crypto_random_hostname() so it can't
10963 overflow on ridiculously large inputs. (No Tor version has ever
10964 provided this kind of bad inputs, but let's be correct in depth.)
10965 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
10966 - Add a (probably redundant) memory clear between iterations of
10967 the router status voting loop, to prevent future coding errors
10968 where data might leak between iterations of the loop. Resolves
10971 o Minor bugfixes (wrapper functions):
10972 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
10973 utility function used in the control-port code). This shouldn't
10974 ever happen unless Tor is completely out of memory, but if it did
10975 happen and Tor somehow recovered from it, Tor could have sent a log
10976 message to a control port in the middle of a reply to a controller
10977 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
10978 - Fix some (not actually triggerable) buffer size checks in usage of
10979 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
10981 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
10982 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
10983 - Enforce correct return behavior of tor_vsscanf() when the '%%'
10984 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
10985 - Make our replacement implementation of strtok_r() compatible with
10986 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
10987 bugfix on 0.2.2.1-alpha.
10988 - Find more places in the code that should have been testing for
10989 invalid sockets using the SOCKET_OK macro. Required for a fix
10990 for bug 4533. Bugfix on 0.2.2.28-beta.
10992 o Minor bugfixes (code correctness):
10993 - Check return value of fputs() when writing authority certificate
10994 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
10995 - When building Tor on Windows with -DUNICODE (not default), ensure
10996 that error messages, filenames, and DNS server names are always
10997 NUL-terminated when we convert them to a single-byte encoding.
10998 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
10999 - Fix a memory leak when trying to launch a DNS request when the
11000 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
11002 - Correct file sizes when reading binary files on Cygwin, to avoid
11003 a bug where Tor would fail to read its state file. Fixes bug 6844;
11004 bugfix on 0.1.2.7-alpha.
11005 - Make sure to set *socket_error in all error cases in
11006 connection_connect(), so it can't produce a warning about
11007 errno being zero from errno_to_orconn_end_reason(). Bugfix on
11008 0.2.1.1-alpha; resolves ticket 6028.
11009 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
11010 bug 4532; found by "troll_un".
11012 o Minor bugfixes (clients):
11013 - Allow one-hop directory-fetching circuits the full "circuit build
11014 timeout" period, rather than just half of it, before failing them
11015 and marking the relay down. This fix should help reduce cases where
11016 clients declare relays (or worse, bridges) unreachable because
11017 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
11018 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
11020 - Ensure we don't cannibalize circuits that are longer than three hops
11021 already, so we don't end up making circuits with 5 or more
11022 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
11023 0.1.0.1-rc which introduced cannibalization.
11025 o Minor bugfixes (relays):
11026 - Don't publish a new relay descriptor when we reload our onion key,
11027 unless the onion key has actually changed. Fixes bug 3263 and
11028 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
11029 - When relays refuse a "create" cell because their queue of pending
11030 create cells is too big (typically because their cpu can't keep up
11031 with the arrival rate), send back reason "resource limit" rather
11032 than reason "internal", so network measurement scripts can get a
11033 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
11034 - Exit nodes don't need to fetch certificates for authorities that
11035 they don't recognize; only directory authorities, bridges,
11036 and caches need to do that. Fixes part of bug 2297; bugfix on
11039 o Minor bugfixes (directory authority / mirrors):
11040 - Avoid O(n^2) performance characteristics when parsing a large
11041 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
11042 - Authorities no longer include any router in their microdescriptor
11043 consensuses for which they couldn't generate or agree on a
11044 microdescriptor. Fixes the second piece of bug 6404; fix on
11046 - When checking for requested signatures on the latest consensus
11047 before serving it to a client, make sure to check the right
11048 consensus flavor. Bugfix on 0.2.2.6-alpha.
11049 - Fix an edge case where TestingTorNetwork is set but the authorities
11050 and relays all have an uptime of zero, so the private Tor network
11051 could briefly lack support for hidden services. Fixes bug 3886;
11052 bugfix on 0.2.2.18-alpha.
11053 - Directory caches no longer refuse to clean out descriptors because
11054 of missing v2 networkstatus documents, unless they're configured
11055 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
11056 0.2.2.26-beta. Patch by Daniel Bryg.
11057 - Don't serve or accept v2 hidden service descriptors over a relay's
11058 DirPort. It's never correct to do so, and disabling it might
11059 make it more annoying to exploit any bugs that turn up in the
11060 descriptor-parsing code. Fixes bug 7149.
11062 o Minor bugfixes (hidden services, client-side):
11063 - Assert that hidden-service-related operations are not performed
11064 using single-hop circuits. Previously, Tor would assert that
11065 client-side streams are not attached to single-hop circuits,
11066 but not that other sensitive operations on the client and service
11067 side are not performed using single-hop circuits. Fixes bug 3332;
11069 - Avoid undefined behavior when parsing the list of supported
11070 rendezvous/introduction protocols in a hidden service descriptor.
11071 Previously, Tor would have confused (as-yet-unused) protocol version
11072 numbers greater than 32 with lower ones on many platforms. Fixes
11073 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11074 - Don't close hidden service client circuits which have almost
11075 finished connecting to their destination when they reach
11076 the normal circuit-build timeout. Previously, we would close
11077 introduction circuits which are waiting for an acknowledgement
11078 from the introduction point, and rendezvous circuits which have
11079 been specified in an INTRODUCE1 cell sent to a hidden service,
11080 after the normal CBT. Now, we mark them as 'timed out', and launch
11081 another rendezvous attempt in parallel. This behavior change can
11082 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
11083 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
11085 o Minor bugfixes (hidden services, service-side):
11086 - Don't close hidden-service-side rendezvous circuits when they
11087 reach the normal circuit-build timeout. This behavior change can
11088 be disabled using the new
11089 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
11090 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
11091 - Don't launch more than 10 service-side introduction-point circuits
11092 for a hidden service in five minutes. Previously, we would consider
11093 launching more introduction-point circuits if at least one second
11094 had passed without any introduction-point circuits failing. Fixes
11095 bug 4607; bugfix on 0.0.7pre1.
11097 o Minor bugfixes (config option behavior):
11098 - If the user tries to set MyFamily on a bridge, refuse to
11099 do so, and warn about the security implications. Fixes bug 4657;
11100 bugfix on 0.2.0.3-alpha.
11101 - The "--quiet" and "--hush" options now apply not only to Tor's
11102 behavior before logs are configured, but also to Tor's behavior in
11103 the absence of configured logs. Fixes bug 3550; bugfix on
11105 - Change the AllowDotExit rules so they should actually work.
11106 We now enforce AllowDotExit only immediately after receiving an
11107 address via SOCKS or DNSPort: other sources are free to provide
11108 .exit addresses after the resolution occurs. Fixes bug 3940;
11109 bugfix on 0.2.2.1-alpha.
11110 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
11111 don't depend on the consensus parameters or compute adaptive
11112 timeouts when it is disabled. Fixes bug 5049; bugfix on
11114 - After we pick a directory mirror, we would refuse to use it if
11115 it's in our ExcludeExitNodes list, resulting in mysterious failures
11116 to bootstrap for people who just wanted to avoid exiting from
11117 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
11118 - When told to add a bridge with the same digest as a preexisting
11119 bridge but a different addr:port, change the addr:port as
11120 requested. Previously we would not notice the change. Fixes half
11121 of bug 5603; fix on 0.2.2.26-beta.
11123 o Minor bugfixes (controller):
11124 - Allow manual 'authenticate' commands to the controller interface
11125 from netcat (nc) as well as telnet. We were rejecting them because
11126 they didn't come with the expected whitespace at the end of the
11127 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
11128 - Report a real bootstrap problem to the controller on router
11129 identity mismatch. Previously we just said "foo", which probably
11130 made a lot of sense at the time. Fixes bug 4169; bugfix on
11132 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
11133 option is set to 0 (which Vidalia version 0.2.16 now does when
11134 a SAVECONF attempt fails), perform other actions that SIGHUP
11135 usually causes (like reopening the logs). Fixes bug 5095; bugfix
11137 - Correctly handle checking the permissions on the parent
11138 directory of a control socket in the root directory. Bug found
11139 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
11141 - End AUTHCHALLENGE error messages (in the control protocol) with
11142 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
11144 o Minor bugfixes (network reading/writing):
11145 - Disable writing on marked-for-close connections when they are
11146 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
11147 bug 5263; bugfix on 0.0.2pre13, where we first added a special
11148 case for flushing marked connections.
11149 - Make sure that there are no unhandled pending TLS errors before
11150 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
11151 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
11152 Bugfix on 0.1.0.5-rc; fixes bug 4528.
11153 - Detect SSL handshake even when the initial attempt to write the
11154 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
11155 - If the client fails to set a reasonable set of ciphersuites
11156 during its v2 handshake renegotiation, allow the renegotiation to
11157 continue nevertheless (i.e. send all the required certificates).
11158 Fixes bug 4591; bugfix on 0.2.0.20-rc.
11160 o Minor bugfixes (other):
11161 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
11162 resource exhaustion, so that clients can adjust their load to
11163 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
11164 started using END_STREAM_REASON_RESOURCELIMIT.
11165 - Don't check for whether the address we're using for outbound
11166 connections has changed until after the outbound connection has
11167 completed. On Windows, getsockname() doesn't succeed until the
11168 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
11169 - Don't hold a Windows file handle open for every file mapping;
11170 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
11172 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
11173 bugfix on 0.2.1.10-alpha.
11174 - If we fail to write a microdescriptor to the disk cache, do not
11175 continue replacing the old microdescriptor file. Fixes bug 2954;
11176 bugfix on 0.2.2.6-alpha.
11178 o Minor bugfixes (log messages, path selection):
11179 - Downgrade "set buildtimeout to low value" messages to "info"
11180 severity; they were never an actual problem, there was never
11181 anything reasonable to do about them, and they tended to spam logs
11182 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
11183 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
11184 more information to it, so that we can track it down in case it
11185 returns again. Mitigates bug 5235.
11186 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
11187 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
11188 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
11189 - Issue a log message if a guard completes less than 40% of your
11190 circuits. Threshold is configurable by torrc option
11191 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
11192 additional, off-by-default code to disable guards which fail too
11193 many circuits. Addresses ticket 5458.
11195 o Minor bugfixes (log messages, client):
11196 - Downgrade "Got a certificate, but we already have it" log messages
11197 from warning to info, except when we're a dirauth. Fixes bug 5238;
11198 bugfix on 0.2.1.7-alpha.
11199 - Fix the log message describing how we work around discovering
11200 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
11201 4837; bugfix on 0.2.2.9-alpha.
11202 - When logging about a disallowed .exit name, do not also call it
11203 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
11204 - Fix a log message suggesting that people contact a non-existent
11205 email address. Fixes bug 3448.
11206 - Rephrase the log message emitted if the TestSocks check is
11207 successful. Patch from Fabian Keil; fixes bug 4094.
11208 - Log (at debug level) whenever a circuit's purpose is changed.
11209 - Log SSL state transitions at log level DEBUG, log domain
11210 HANDSHAKE. This can be useful for debugging censorship events.
11211 Implements ticket 3264.
11212 - We now log which torrc file we're using on startup. Implements
11214 - Rate-limit log messages when asked to connect anonymously to
11215 a private address. When these hit, they tended to hit fast and
11216 often. Also, don't bother trying to connect to addresses that we
11217 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
11218 reply makes us think we have been lied to, even when the address the
11219 client tried to connect to was "localhost." Resolves ticket 2822.
11221 o Minor bugfixes (log messages, non-client):
11222 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
11223 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
11224 - Don't log that we have "decided to publish new relay descriptor"
11225 unless we are actually publishing a descriptor. Fixes bug 3942;
11226 bugfix on 0.2.2.28-beta.
11227 - Log which authority we're missing votes from when we go to fetch
11228 them from the other auths.
11229 - Replace "Sending publish request" log messages with "Launching
11230 upload", so that they no longer confusingly imply that we're
11231 sending something to a directory we might not even be connected
11232 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
11233 - Warn when Tor is configured to use accounting in a way that can
11234 link a hidden service to some other hidden service or public
11235 address. Resolves ticket 6490.
11236 - Fix a minor formatting issue in one of tor-gencert's error messages.
11240 - Update to the latest version of the tinytest unit testing framework.
11241 This includes a couple of bugfixes that can be relevant for
11242 running forked unit tests on Windows, and removes all reserved
11244 - Avoid a false positive in the util/threads unit test by increasing
11245 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
11246 - Make it possible to set the TestingTorNetwork configuration
11247 option using AlternateDirAuthority and AlternateBridgeAuthority
11248 as an alternative to setting DirServer. Addresses ticket 6377.
11249 - Add a unit test for the environment_variable_names_equal() function.
11250 - A wide variety of new unit tests by Esteban Manchado Velázquez.
11251 - Numerous new unit tests for functions in util.c and address.c by
11253 - The long-disabled benchmark tests are now split into their own
11254 ./src/test/bench binary.
11255 - The benchmark tests can now use more accurate timers than
11256 gettimeofday() when such timers are available.
11257 - Use tt_assert(), not tor_assert(), for checking for test failures.
11258 This makes the unit tests more able to go on in the event that
11261 o Build improvements:
11262 - Use the dead_strip option when building Tor on OS X. This reduces
11263 binary size by almost 19% when linking openssl and libevent
11264 statically, which we do for Tor Browser Bundle.
11265 - Provide a better error message about possible OSX Asciidoc failure
11266 reasons. Fixes bug 6436.
11267 - Detect attempts to build Tor on (as yet hypothetical) versions
11268 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
11269 fix for bug 4533. Bugfix on 0.2.2.28-beta.
11270 - On Windows, we now define the _WIN32_WINNT macros only if they
11271 are not already defined. This lets the person building Tor decide,
11272 if they want, to require a later version of Windows.
11273 - Our autogen.sh script now uses autoreconf to launch autoconf,
11274 automake, and so on. This is more robust against some of the failure
11275 modes associated with running the autotools pieces on their own.
11276 - Running "make version" now displays the version of Tor that
11277 we're about to build. Idea from katmagic; resolves issue 4400.
11278 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
11279 on 0.2.2.4-alpha; fixes bug 3427.
11280 - New --enable-static-tor configure option for building Tor as
11281 statically as possible. Idea, general hackery and thoughts from
11282 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
11284 - Limited, experimental support for building with nmake and MSVC.
11286 o Build requirements:
11287 - Building Tor with bufferevent support now requires Libevent
11288 2.0.13-stable or later. Previous versions of Libevent had bugs in
11289 SSL-related bufferevents and related issues that would make Tor
11290 work badly with bufferevents. Requiring 2.0.13-stable also allows
11291 Tor with bufferevents to take advantage of Libevent APIs
11292 introduced after 2.0.8-rc.
11293 - Our build system requires automake 1.6 or later to create the
11294 Makefile.in files. Previously, you could have used 1.4.
11295 This only affects developers and people building Tor from git;
11296 people who build Tor from the source distribution without changing
11297 the Makefile.am files should be fine.
11298 - Detect when we try to build on a platform that doesn't define
11299 AF_UNSPEC to 0. We don't work there, so refuse to compile.
11301 o Build fixes (compile/link):
11302 - Format more doubles with %f, not %lf. Patch from grarpamp to make
11303 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
11305 - When building with --enable-static-tor on OpenBSD, do not
11306 erroneously attempt to link -lrt. Fixes bug 5103.
11307 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
11308 that IPv6 stuff will compile on MSVC, and compilation issues
11309 will be easier to track down. Fixes bug 5861.
11310 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
11311 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
11312 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
11313 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
11315 o Build fixes (other):
11316 - Use the _WIN32 macro throughout our code to detect Windows.
11317 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
11319 - Properly handle the case where the build-tree is not the same
11320 as the source tree when generating src/common/common_sha1.i,
11321 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
11322 bugfix on 0.2.0.1-alpha.
11323 - During configure, search for library containing cos function as
11324 libm lives in libcore on some platforms (BeOS/Haiku). Linking
11325 against libm was hard-coded before. Fixes the first part of bug
11326 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
11328 - Prevent a false positive from the check-spaces script, by disabling
11329 the "whitespace between function name and (" check for functions
11332 o Packaging (RPM) changes:
11333 - Update our default RPM spec files to work with mock and rpmbuild
11334 on RHEL/Fedora. They have an updated set of dependencies and
11335 conflicts, a fix for an ancient typo when creating the "_tor"
11336 user, and better instructions. Thanks to Ondrej Mikle for the
11337 patch series. Fixes bug 6043.
11338 - On OpenSUSE, create the /var/run/tor directory on startup if it
11339 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
11341 o Code refactoring (safety):
11342 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
11343 10 lines. Also, don't nest them. Doing so in the past has
11344 led to hard-to-debug code. The new style is to use the
11345 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
11346 - Use macros to indicate OpenSSL versions, so we don't need to worry
11347 about accidental hexadecimal bit shifts.
11348 - Use tor_sscanf() in place of scanf() in more places through the
11349 code. This makes us a little more locale-independent, and
11350 should help shut up code-analysis tools that can't tell
11351 a safe sscanf string from a dangerous one.
11352 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
11353 - Use the smartlist_add_asprintf() alias more consistently.
11355 o Code refactoring (consolidate):
11356 - A major revision to our internal node-selecting and listing logic.
11357 Tor already had at least two major ways to look at the question of
11358 "which Tor servers do we know about": a list of router descriptors,
11359 and a list of entries in the current consensus. With
11360 microdescriptors, we're adding a third. Having so many systems
11361 without an abstraction layer over them was hurting the codebase.
11362 Now, we have a new "node_t" abstraction that presents a consistent
11363 interface to a client's view of a Tor node, and holds (nearly) all
11364 of the mutable state formerly in routerinfo_t and routerstatus_t.
11365 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
11366 Libevent's notion of cached time when possible.
11367 - Remove duplicate code for invoking getrlimit() from control.c.
11368 - Use OpenSSL's built-in SSL_state_string_long() instead of our
11369 own homebrewed ssl_state_to_string() replacement. Patch from
11370 Emile Snyder. Fixes bug 4653.
11371 - Change the symmetric cipher interface so that creating and
11372 initializing a stream cipher are no longer separate functions.
11374 o Code refactoring (separate):
11375 - Make a new "entry connection" struct as an internal subtype of "edge
11376 connection", to simplify the code and make exit connections smaller.
11377 - Split connection_about_to_close() into separate functions for each
11379 - Rewrite the listener-selection logic so that parsing which ports
11380 we want to listen on is now separate from binding to the ports
11383 o Code refactoring (name changes):
11384 - Rename a handful of old identifiers, mostly related to crypto
11385 structures and crypto functions. By convention, our "create an
11386 object" functions are called "type_new()", our "free an object"
11387 functions are called "type_free()", and our types indicate that
11388 they are types only with a final "_t". But a handful of older
11389 types and functions broke these rules, with function names like
11390 "type_create" or "subsystem_op_type", or with type names like
11392 - Rename Tor functions that turn strings into addresses, so that
11393 "parse" indicates that no hostname resolution occurs, and
11394 "lookup" indicates that hostname resolution may occur. This
11395 should help prevent mistakes in the future. Fixes bug 3512.
11396 - Use the name "CERTS" consistently to refer to the new cell type;
11397 we were calling it CERT in some places and CERTS in others.
11398 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
11399 invalid value, rather than just -1.
11400 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
11401 can pick them up when the tests aren't disabled. Bugfix on
11402 0.2.2.4-alpha which introduced tinytest.
11404 o Code refactoring (other):
11405 - Defensively refactor rend_mid_rendezvous() so that protocol
11406 violations and length checks happen in the beginning. Fixes
11408 - Remove the pure attribute from all functions that used it
11409 previously. In many cases we assigned it incorrectly, because the
11410 functions might assert or call impure functions, and we don't have
11411 evidence that keeping the pure attribute is worthwhile. Implements
11412 changes suggested in ticket 4421.
11413 - Move the replay-detection cache for the RSA-encrypted parts of
11414 INTRODUCE2 cells to the introduction point data structures.
11415 Previously, we would use one replay-detection cache per hidden
11416 service. Required by fix for bug 3460.
11417 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
11418 no longer link against Libevent: they never used it, but
11419 our library structure used to force them to link it.
11421 o Removed features and files:
11422 - Remove all internal support for unpadded RSA. We never used it, and
11423 it would be a bad idea to start.
11424 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
11426 - Remove some redundant #include directives throughout the code.
11427 Patch from Andrea Gelmini.
11428 - Remove some old code to remember statistics about which descriptors
11429 we've served as a directory mirror. The feature wasn't used and
11430 is outdated now that microdescriptors are around.
11431 - Remove some old code to work around even older versions of Tor that
11432 used forked processes to handle DNS requests. Such versions of Tor
11433 are no longer in use as relays.
11434 - The "torify" script no longer supports the "tsocks" socksifier
11435 tool, since tsocks doesn't support DNS and UDP right for Tor.
11436 Everyone should be using torsocks instead. Fixes bugs 3530 and
11437 5180. Based on a patch by "ugh".
11438 - Remove the torrc.bridge file: we don't use it for anything, and
11439 it had become badly desynchronized from torrc.sample. Resolves
11443 - Begin a doc/state-contents.txt file to explain the contents of
11444 the Tor state file. Fixes bug 2987.
11445 - Clarify the documentation for the Alternate*Authority options.
11447 - Document the --defaults-torrc option, and the new semantics for
11448 overriding, extending, and clearing lists of options. Closes
11450 - Add missing man page documentation for consensus and microdesc
11451 files. Resolves ticket 6732.
11452 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
11454 o Documentation fixes:
11455 - Improve the manual's documentation for the NT Service command-line
11456 options. Addresses ticket 3964.
11457 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
11458 - Document the changes to the ORPort and DirPort options, and the
11459 fact that {OR/Dir}ListenAddress is now unnecessary (and
11460 therefore deprecated). Resolves ticket 5597.
11461 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
11462 - Clarify that hidden services are TCP only. Fixes bug 6024.
11465 Changes in version 0.2.2.39 - 2012-09-11
11466 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
11470 - Fix an assertion failure in tor_timegm() that could be triggered
11471 by a badly formatted directory object. Bug found by fuzzing with
11472 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11473 - Do not crash when comparing an address with port value 0 to an
11474 address policy. This bug could have been used to cause a remote
11475 assertion failure by or against directory authorities, or to
11476 allow some applications to crash clients. Fixes bug 6690; bugfix
11480 Changes in version 0.2.2.38 - 2012-08-12
11481 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
11482 attack that could in theory leak path information.
11485 - Avoid an uninitialized memory read when reading a vote or consensus
11486 document that has an unrecognized flavor name. This read could
11487 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
11488 - Try to leak less information about what relays a client is
11489 choosing to a side-channel attacker. Previously, a Tor client would
11490 stop iterating through the list of available relays as soon as it
11491 had chosen one, thus finishing a little earlier when it picked
11492 a router earlier in the list. If an attacker can recover this
11493 timing information (nontrivial but not proven to be impossible),
11494 they could learn some coarse-grained information about which relays
11495 a client was picking (middle nodes in particular are likelier to
11496 be affected than exits). The timing attack might be mitigated by
11497 other factors (see bug 6537 for some discussion), but it's best
11498 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
11501 Changes in version 0.2.2.37 - 2012-06-06
11502 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
11503 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11507 - Work around a bug in OpenSSL that broke renegotiation with TLS
11508 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11509 the v2 Tor connection protocol when both sides were using OpenSSL
11510 1.0.1 would fail. Resolves ticket 6033.
11511 - When waiting for a client to renegotiate, don't allow it to add
11512 any bytes to the input buffer. This fixes a potential DoS issue.
11513 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11514 - Fix an edge case where if we fetch or publish a hidden service
11515 descriptor, we might build a 4-hop circuit and then use that circuit
11516 for exiting afterwards -- even if the new last hop doesn't obey our
11517 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11520 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11521 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11524 - Tell GCC and Clang to check for any errors in format strings passed
11525 to the tor_v*(print|scan)f functions.
11528 Changes in version 0.2.2.36 - 2012-05-24
11529 Tor 0.2.2.36 updates the addresses for two of the eight directory
11530 authorities, fixes some potential anonymity and security issues,
11531 and fixes several crash bugs.
11533 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
11534 known flaws, and nobody should be using them. You should upgrade. If
11535 you're using a Linux or BSD and its packages are obsolete, stop using
11536 those packages and upgrade anyway.
11538 o Directory authority changes:
11539 - Change IP address for maatuska (v3 directory authority).
11540 - Change IP address for ides (v3 directory authority), and rename
11544 - When building or running with any version of OpenSSL earlier
11545 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11546 versions have a bug (CVE-2011-4576) in which their block cipher
11547 padding includes uninitialized data, potentially leaking sensitive
11548 information to any peer with whom they make a SSLv3 connection. Tor
11549 does not use SSL v3 by default, but a hostile client or server
11550 could force an SSLv3 connection in order to gain information that
11551 they shouldn't have been able to get. The best solution here is to
11552 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
11553 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
11554 to make sure that the bug can't happen.
11555 - Never use a bridge or a controller-supplied node as an exit, even
11556 if its exit policy allows it. Found by wanoskarnet. Fixes bug
11557 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
11558 and 0.2.0.3-alpha (for bridge-purpose descriptors).
11559 - Only build circuits if we have a sufficient threshold of the total
11560 descriptors that are marked in the consensus with the "Exit"
11561 flag. This mitigates an attack proposed by wanoskarnet, in which
11562 all of a client's bridges collude to restrict the exit nodes that
11563 the client knows about. Fixes bug 5343.
11564 - Provide controllers with a safer way to implement the cookie
11565 authentication mechanism. With the old method, if another locally
11566 running program could convince a controller that it was the Tor
11567 process, then that program could trick the controller into telling
11568 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
11569 authentication method uses a challenge-response approach to prevent
11570 this attack. Fixes bug 5185; implements proposal 193.
11573 - Avoid logging uninitialized data when unable to decode a hidden
11574 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
11575 - Avoid a client-side assertion failure when receiving an INTRODUCE2
11576 cell on a general purpose circuit. Fixes bug 5644; bugfix on
11578 - Fix builds when the path to sed, openssl, or sha1sum contains
11579 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
11581 - Correct our replacements for the timeradd() and timersub() functions
11582 on platforms that lack them (for example, Windows). The timersub()
11583 function is used when expiring circuits, while timeradd() is
11584 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
11585 bugfix on 0.2.2.24-alpha.
11586 - Fix the SOCKET_OK test that we use to tell when socket
11587 creation fails so that it works on Win64. Fixes part of bug 4533;
11588 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
11591 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
11592 Fixes bug 5346; bugfix on 0.0.8pre3.
11593 - Make our number-parsing functions always treat too-large values
11594 as an error, even when those values exceed the width of the
11595 underlying type. Previously, if the caller provided these
11596 functions with minima or maxima set to the extreme values of the
11597 underlying integer type, these functions would return those
11598 values on overflow rather than treating overflow as an error.
11599 Fixes part of bug 5786; bugfix on 0.0.9.
11600 - Older Linux kernels erroneously respond to strange nmap behavior
11601 by having accept() return successfully with a zero-length
11602 socket. When this happens, just close the connection. Previously,
11603 we would try harder to learn the remote address: but there was
11604 no such remote address to learn, and our method for trying to
11605 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
11606 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
11607 - Correct parsing of certain date types in parse_http_time().
11608 Without this patch, If-Modified-Since would behave
11609 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
11610 Esteban Manchado Velázques.
11611 - Change the BridgePassword feature (part of the "bridge community"
11612 design, which is not yet implemented) to use a time-independent
11613 comparison. The old behavior might have allowed an adversary
11614 to use timing to guess the BridgePassword value. Fixes bug 5543;
11615 bugfix on 0.2.0.14-alpha.
11616 - Detect and reject certain misformed escape sequences in
11617 configuration values. Previously, these values would cause us
11618 to crash if received in a torrc file or over an authenticated
11619 control port. Bug found by Esteban Manchado Velázquez, and
11620 independently by Robert Connolly from Matta Consulting who further
11621 noted that it allows a post-authentication heap overflow. Patch
11622 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
11623 bugfix on 0.2.0.16-alpha.
11624 - Fix a compile warning when using the --enable-openbsd-malloc
11625 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
11626 - During configure, detect when we're building with clang version
11627 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
11628 CFLAGS. clang doesn't support them yet.
11629 - When sending an HTTP/1.1 proxy request, include a Host header.
11630 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
11631 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
11632 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
11633 - If we hit the error case where routerlist_insert() replaces an
11634 existing (old) server descriptor, make sure to remove that
11635 server descriptor from the old_routers list. Fix related to bug
11636 1776. Bugfix on 0.2.2.18-alpha.
11638 o Minor bugfixes (documentation and log messages):
11639 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
11640 Fixes bug 4856; bugfix on Tor 0.0.6.
11641 - Update "ClientOnly" man page entry to explain that there isn't
11642 really any point to messing with it. Resolves ticket 5005.
11643 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
11644 directory authority option (introduced in Tor 0.2.2.34).
11645 - Downgrade the "We're missing a certificate" message from notice
11646 to info: people kept mistaking it for a real problem, whereas it
11647 is seldom the problem even when we are failing to bootstrap. Fixes
11648 bug 5067; bugfix on 0.2.0.10-alpha.
11649 - Correctly spell "connect" in a log message on failure to create a
11650 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
11651 - Clarify the behavior of MaxCircuitDirtiness with hidden service
11652 circuits. Fixes issue 5259.
11655 - Directory authorities now reject versions of Tor older than
11656 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
11657 inclusive. These versions accounted for only a small fraction of
11658 the Tor network, and have numerous known security issues. Resolves
11660 - Update to the May 1 2012 Maxmind GeoLite Country database.
11663 - When sending or relaying a RELAY_EARLY cell, we used to convert
11664 it to a RELAY cell if the connection was using the v1 link
11665 protocol. This was a workaround for older versions of Tor, which
11666 didn't handle RELAY_EARLY cells properly. Now that all supported
11667 versions can handle RELAY_EARLY cells, and now that we're enforcing
11668 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
11669 remove this workaround. Addresses bug 4786.
11672 Changes in version 0.2.2.35 - 2011-12-16
11673 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
11674 buffers code. Absolutely everybody should upgrade.
11676 The bug relied on an incorrect calculation when making data continuous
11677 in one of our IO buffers, if the first chunk of the buffer was
11678 misaligned by just the wrong amount. The miscalculation would allow an
11679 attacker to overflow a piece of heap-allocated memory. To mount this
11680 attack, the attacker would need to either open a SOCKS connection to
11681 Tor's SocksPort (usually restricted to localhost), or target a Tor
11682 instance configured to make its connections through a SOCKS proxy
11683 (which Tor does not do by default).
11685 Good security practice requires that all heap-overflow bugs should be
11686 presumed to be exploitable until proven otherwise, so we are treating
11687 this as a potential code execution attack. Please upgrade immediately!
11688 This bug does not affect bufferevents-based builds of Tor. Special
11689 thanks to "Vektor" for reporting this issue to us!
11691 Tor 0.2.2.35 also fixes several bugs in previous versions, including
11692 crash bugs for unusual configurations, and a long-term bug that
11693 would prevent Tor from starting on Windows machines with draconian
11696 With this release, we remind everyone that 0.2.0.x has reached its
11697 formal end-of-life. Those Tor versions have many known flaws, and
11698 nobody should be using them. You should upgrade -- ideally to the
11699 0.2.2.x series. If you're using a Linux or BSD and its packages are
11700 obsolete, stop using those packages and upgrade anyway.
11702 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
11703 longer receive support after some time in early 2012.
11706 - Fix a heap overflow bug that could occur when trying to pull
11707 data into the first chunk of a buffer, when that chunk had
11708 already had some data drained from it. Fixes CVE-2011-2778;
11709 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11710 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
11711 that it doesn't attempt to allocate a socketpair. This could cause
11712 some problems on Windows systems with overzealous firewalls. Fix for
11713 bug 4457; workaround for Libevent versions 2.0.1-alpha through
11715 - If we mark an OR connection for close based on a cell we process,
11716 don't process any further cells on it. We already avoid further
11717 reads on marked-for-close connections, but now we also discard the
11718 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
11719 which was the first version where we might mark a connection for
11720 close based on processing a cell on it.
11721 - Correctly sanity-check that we don't underflow on a memory
11722 allocation (and then assert) for hidden service introduction
11723 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11724 bugfix on 0.2.1.5-alpha.
11725 - Fix a memory leak when we check whether a hidden service
11726 descriptor has any usable introduction points left. Fixes bug
11727 4424. Bugfix on 0.2.2.25-alpha.
11728 - Don't crash when we're running as a relay and don't have a GeoIP
11729 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
11730 we've had in the 0.2.3.x branch already.
11731 - When running as a client, do not print a misleading (and plain
11732 wrong) log message that we're collecting "directory request"
11733 statistics: clients don't collect statistics. Also don't create a
11734 useless (because empty) stats file in the stats/ directory. Fixes
11735 bug 4353; bugfix on 0.2.2.34.
11738 - Detect failure to initialize Libevent. This fix provides better
11739 detection for future instances of bug 4457.
11740 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
11741 function. This was eating up hideously large amounts of time on some
11742 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
11743 - Resolve an integer overflow bug in smartlist_ensure_capacity().
11744 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
11746 - Don't warn about unused log_mutex in log.c when building with
11747 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
11748 0.1.0.6-rc which introduced --disable-threads.
11749 - When configuring, starting, or stopping an NT service, stop
11750 immediately after the service configuration attempt has succeeded
11751 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
11752 - When sending a NETINFO cell, include the original address
11753 received for the other side, not its canonical address. Found
11754 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
11755 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
11756 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
11757 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
11758 occurred when a client tried to fetch a descriptor for a bridge
11759 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
11760 - Backport fixes for a pair of compilation warnings on Windows.
11761 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
11762 - If we had ever tried to call tor_addr_to_str on an address of
11763 unknown type, we would have done a strdup on an uninitialized
11764 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
11765 Reported by "troll_un".
11766 - Correctly detect and handle transient lookup failures from
11767 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
11768 Reported by "troll_un".
11769 - Fix null-pointer access that could occur if TLS allocation failed.
11770 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
11771 - Use tor_socket_t type for listener argument to accept(). Fixes bug
11772 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
11775 - Add two new config options for directory authorities:
11776 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
11777 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
11778 that is always sufficient to satisfy the bandwidth requirement for
11779 the Guard flag. Now it will be easier for researchers to simulate
11780 Tor networks with different values. Resolves ticket 4484.
11781 - When Tor ignores a hidden service specified in its configuration,
11782 include the hidden service's directory in the warning message.
11783 Previously, we would only tell the user that some hidden service
11784 was ignored. Bugfix on 0.0.6; fixes bug 4426.
11785 - Update to the December 6 2011 Maxmind GeoLite Country database.
11787 o Packaging changes:
11788 - Make it easier to automate expert package builds on Windows,
11789 by removing an absolute path from makensis.exe command.
11792 Changes in version 0.2.1.32 - 2011-12-16
11793 Tor 0.2.1.32 backports important security and privacy fixes for
11794 oldstable. This release is intended only for package maintainers and
11795 others who cannot use the 0.2.2 stable series. All others should be
11796 using Tor 0.2.2.x or newer.
11798 The Tor 0.2.1.x series will reach formal end-of-life some time in
11799 early 2012; we will stop releasing patches for it then.
11801 o Major bugfixes (also included in 0.2.2.x):
11802 - Correctly sanity-check that we don't underflow on a memory
11803 allocation (and then assert) for hidden service introduction
11804 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11805 bugfix on 0.2.1.5-alpha.
11806 - Fix a heap overflow bug that could occur when trying to pull
11807 data into the first chunk of a buffer, when that chunk had
11808 already had some data drained from it. Fixes CVE-2011-2778;
11809 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11812 - Update to the December 6 2011 Maxmind GeoLite Country database.
11815 Changes in version 0.2.2.34 - 2011-10-26
11816 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
11817 can deanonymize Tor users. Everybody should upgrade.
11819 The attack relies on four components: 1) Clients reuse their TLS cert
11820 when talking to different relays, so relays can recognize a user by
11821 the identity key in her cert. 2) An attacker who knows the client's
11822 identity key can probe each guard relay to see if that identity key
11823 is connected to that guard relay right now. 3) A variety of active
11824 attacks in the literature (starting from "Low-Cost Traffic Analysis
11825 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
11826 discover the guard relays that a Tor user visiting the website is using.
11827 4) Clients typically pick three guards at random, so the set of guards
11828 for a given user could well be a unique fingerprint for her. This
11829 release fixes components #1 and #2, which is enough to block the attack;
11830 the other two remain as open research problems. Special thanks to
11831 "frosty_un" for reporting the issue to us!
11833 Clients should upgrade so they are no longer recognizable by the TLS
11834 certs they present. Relays should upgrade so they no longer allow a
11835 remote attacker to probe them to test whether unpatched clients are
11836 currently connected to them.
11838 This release also fixes several vulnerabilities that allow an attacker
11839 to enumerate bridge relays. Some bridge enumeration attacks still
11840 remain; see for example proposal 188.
11842 o Privacy/anonymity fixes (clients):
11843 - Clients and bridges no longer send TLS certificate chains on
11844 outgoing OR connections. Previously, each client or bridge would
11845 use the same cert chain for all outgoing OR connections until
11846 its IP address changes, which allowed any relay that the client
11847 or bridge contacted to determine which entry guards it is using.
11848 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11849 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11850 no longer considers that connection as suitable for satisfying a
11851 circuit EXTEND request. Now relays can protect clients from the
11852 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11853 - Directory authorities no longer assign the Guard flag to relays
11854 that haven't upgraded to the above "refuse EXTEND requests
11855 to client connections" fix. Now directory authorities can
11856 protect clients from the CVE-2011-2768 issue even if neither
11857 the clients nor the relays have upgraded yet. There's a new
11858 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
11859 to let us transition smoothly, else tomorrow there would be no
11862 o Privacy/anonymity fixes (bridge enumeration):
11863 - Bridge relays now do their directory fetches inside Tor TLS
11864 connections, like all the other clients do, rather than connecting
11865 directly to the DirPort like public relays do. Removes another
11866 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
11867 - Bridges relays now build circuits for themselves in a more similar
11868 way to how clients build them. Removes another avenue for
11869 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
11870 when bridges were introduced.
11871 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11872 that they initiated. Relays could distinguish incoming bridge
11873 connections from client connections, creating another avenue for
11874 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11875 Found by "frosty_un".
11878 - Fix a crash bug when changing node restrictions while a DNS lookup
11879 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
11881 - Don't launch a useless circuit after failing to use one of a
11882 hidden service's introduction points. Previously, we would
11883 launch a new introduction circuit, but not set the hidden service
11884 which that circuit was intended to connect to, so it would never
11885 actually be used. A different piece of code would then create a
11886 new introduction circuit correctly. Bug reported by katmagic and
11887 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
11890 - Change an integer overflow check in the OpenBSD_Malloc code so
11891 that GCC is less likely to eliminate it as impossible. Patch
11892 from Mansour Moufid. Fixes bug 4059.
11893 - When a hidden service turns an extra service-side introduction
11894 circuit into a general-purpose circuit, free the rend_data and
11895 intro_key fields first, so we won't leak memory if the circuit
11896 is cannibalized for use as another service-side introduction
11897 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
11898 - Bridges now skip DNS self-tests, to act a little more stealthily.
11899 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
11900 bridges. Patch by "warms0x".
11901 - Fix internal bug-checking logic that was supposed to catch
11902 failures in digest generation so that it will fail more robustly
11903 if we ask for a nonexistent algorithm. Found by Coverity Scan.
11904 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
11905 - Report any failure in init_keys() calls launched because our
11906 IP address has changed. Spotted by Coverity Scan. Bugfix on
11907 0.1.1.4-alpha; fixes CID 484.
11909 o Minor bugfixes (log messages and documentation):
11910 - Remove a confusing dollar sign from the example fingerprint in the
11911 man page, and also make the example fingerprint a valid one. Fixes
11912 bug 4309; bugfix on 0.2.1.3-alpha.
11913 - The next version of Windows will be called Windows 8, and it has
11914 a major version of 6, minor version of 2. Correctly identify that
11915 version instead of calling it "Very recent version". Resolves
11916 ticket 4153; reported by funkstar.
11917 - Downgrade log messages about circuit timeout calibration from
11918 "notice" to "info": they don't require or suggest any human
11919 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
11920 bugfix on 0.2.2.14-alpha.
11923 - Turn on directory request statistics by default and include them in
11924 extra-info descriptors. Don't break if we have no GeoIP database.
11925 Backported from 0.2.3.1-alpha; implements ticket 3951.
11926 - Update to the October 4 2011 Maxmind GeoLite Country database.
11929 Changes in version 0.2.1.31 - 2011-10-26
11930 Tor 0.2.1.31 backports important security and privacy fixes for
11931 oldstable. This release is intended only for package maintainers and
11932 others who cannot use the 0.2.2 stable series. All others should be
11933 using Tor 0.2.2.x or newer.
11935 o Security fixes (also included in 0.2.2.x):
11936 - Replace all potentially sensitive memory comparison operations
11937 with versions whose runtime does not depend on the data being
11938 compared. This will help resist a class of attacks where an
11939 adversary can use variations in timing information to learn
11940 sensitive data. Fix for one case of bug 3122. (Safe memcmp
11941 implementation by Robert Ransom based partially on code by DJB.)
11942 - Fix an assert in parsing router descriptors containing IPv6
11943 addresses. This one took down the directory authorities when
11944 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
11946 o Privacy/anonymity fixes (also included in 0.2.2.x):
11947 - Clients and bridges no longer send TLS certificate chains on
11948 outgoing OR connections. Previously, each client or bridge would
11949 use the same cert chain for all outgoing OR connections until
11950 its IP address changes, which allowed any relay that the client
11951 or bridge contacted to determine which entry guards it is using.
11952 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11953 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11954 no longer considers that connection as suitable for satisfying a
11955 circuit EXTEND request. Now relays can protect clients from the
11956 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11957 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11958 that they initiated. Relays could distinguish incoming bridge
11959 connections from client connections, creating another avenue for
11960 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11961 Found by "frosty_un".
11962 - When receiving a hidden service descriptor, check that it is for
11963 the hidden service we wanted. Previously, Tor would store any
11964 hidden service descriptors that a directory gave it, whether it
11965 wanted them or not. This wouldn't have let an attacker impersonate
11966 a hidden service, but it did let directories pre-seed a client
11967 with descriptors that it didn't want. Bugfix on 0.0.6.
11968 - Avoid linkability based on cached hidden service descriptors: forget
11969 all hidden service descriptors cached as a client when processing a
11970 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
11971 - Make the bridge directory authority refuse to answer directory
11972 requests for "all" descriptors. It used to include bridge
11973 descriptors in its answer, which was a major information leak.
11974 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
11975 - Don't attach new streams to old rendezvous circuits after SIGNAL
11976 NEWNYM. Previously, we would keep using an existing rendezvous
11977 circuit if it remained open (i.e. if it were kept open by a
11978 long-lived stream, or if a new stream were attached to it before
11979 Tor could notice that it was old and no longer in use). Bugfix on
11980 0.1.1.15-rc; fixes bug 3375.
11982 o Minor bugfixes (also included in 0.2.2.x):
11983 - When we restart our relay, we might get a successful connection
11984 from the outside before we've started our reachability tests,
11985 triggering a warning: "ORPort found reachable, but I have no
11986 routerinfo yet. Failing to inform controller of success." This
11987 bug was harmless unless Tor is running under a controller
11988 like Vidalia, in which case the controller would never get a
11989 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
11991 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11992 enabled. Fixes bug 1526.
11993 - Remove undocumented option "-F" from tor-resolve: it hasn't done
11994 anything since 0.2.1.16-rc.
11995 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
11996 None of the cases where we did this before were wrong, but by making
11997 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
11998 - Fix a rare crash bug that could occur when a client was configured
11999 with a large number of bridges. Fixes bug 2629; bugfix on
12000 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12001 - Correct the warning displayed when a rendezvous descriptor exceeds
12002 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12004 - Fix an uncommon assertion failure when running with DNSPort under
12005 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12006 - When warning about missing zlib development packages during compile,
12007 give the correct package names. Bugfix on 0.2.0.1-alpha.
12008 - Require that introduction point keys and onion keys have public
12009 exponent 65537. Bugfix on 0.2.0.10-alpha.
12010 - Do not crash when our configuration file becomes unreadable, for
12011 example due to a permissions change, between when we start up
12012 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12014 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12016 - Always NUL-terminate the sun_path field of a sockaddr_un before
12017 passing it to the kernel. (Not a security issue: kernels are
12018 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12019 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12020 - Don't stack-allocate the list of supplementary GIDs when we're
12021 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12022 could take up to 256K, which is way too much stack. Found by
12023 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12025 o Minor bugfixes (only in 0.2.1.x):
12026 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
12027 rely on them. Bugfix on 0.2.1.30.
12028 - Use git revisions instead of svn revisions when generating our
12029 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
12031 o Minor features (also included in 0.2.2.x):
12032 - Adjust the expiration time on our SSL session certificates to
12033 better match SSL certs seen in the wild. Resolves ticket 4014.
12034 - Allow nameservers with IPv6 address. Resolves bug 2574.
12035 - Update to the October 4 2011 Maxmind GeoLite Country database.
12038 Changes in version 0.2.2.33 - 2011-09-13
12039 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
12040 TLS handshake that makes relays and bridges that run this new version
12041 reachable from Iran again.
12044 - Avoid an assertion failure when reloading a configuration with
12045 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
12046 3923; bugfix on 0.2.2.25-alpha.
12048 o Minor features (security):
12049 - Check for replays of the public-key encrypted portion of an
12050 INTRODUCE1 cell, in addition to the current check for replays of
12051 the g^x value. This prevents a possible class of active attacks
12052 by an attacker who controls both an introduction point and a
12053 rendezvous point, and who uses the malleability of AES-CTR to
12054 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
12055 that these attacks are infeasible (requiring the attacker to send
12056 on the order of zettabytes of altered cells in a short interval),
12057 but we'd rather block them off in case there are any classes of
12058 this attack that we missed. Reported by Willem Pinckaers.
12061 - Adjust the expiration time on our SSL session certificates to
12062 better match SSL certs seen in the wild. Resolves ticket 4014.
12063 - Change the default required uptime for a relay to be accepted as
12064 a HSDir (hidden service directory) from 24 hours to 25 hours.
12065 Improves on 0.2.0.10-alpha; resolves ticket 2649.
12066 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
12067 authorities to abstain from voting on assignment of the HSDir
12068 consensus flag. Related to bug 2649.
12069 - Update to the September 6 2011 Maxmind GeoLite Country database.
12071 o Minor bugfixes (documentation and log messages):
12072 - Correct the man page to explain that HashedControlPassword and
12073 CookieAuthentication can both be set, in which case either method
12074 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
12075 when we decided to allow these config options to both be set. Issue
12076 raised by bug 3898.
12077 - Demote the 'replay detected' log message emitted when a hidden
12078 service receives the same Diffie-Hellman public key in two different
12079 INTRODUCE2 cells to info level. A normal Tor client can cause that
12080 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
12081 fixes part of bug 2442.
12082 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
12083 level. There is nothing that a hidden service's operator can do
12084 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
12086 - Clarify a log message specifying the characters permitted in
12087 HiddenServiceAuthorizeClient client names. Previously, the log
12088 message said that "[A-Za-z0-9+-_]" were permitted; that could have
12089 given the impression that every ASCII character between "+" and "_"
12090 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
12093 - Provide a substitute implementation of lround() for MSVC, which
12094 apparently lacks it. Patch from Gisle Vanem.
12095 - Clean up some code issues that prevented Tor from building on older
12096 BSDs. Fixes bug 3894; reported by "grarpamp".
12097 - Search for a platform-specific version of "ar" when cross-compiling.
12098 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
12101 Changes in version 0.2.2.32 - 2011-08-27
12102 The Tor 0.2.2 release series is dedicated to the memory of Andreas
12103 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
12104 a founder of the PETS community, a leader in our field, a mentor,
12105 and a friend. He left us with these words: "I had the possibility
12106 to contribute to this world that is not as it should be. I hope I
12107 could help in some areas to make the world a better place, and that
12108 I could also encourage other people to be engaged in improving the
12109 world. Please, stay engaged. This world needs you, your love, your
12110 initiative -- now I cannot be part of that anymore."
12112 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
12113 ready. More than two years in the making, this release features improved
12114 client performance and hidden service reliability, better compatibility
12115 for Android, correct behavior for bridges that listen on more than
12116 one address, more extensible and flexible directory object handling,
12117 better reporting of network statistics, improved code security, and
12118 many many other features and bugfixes.
12120 o Major features (client performance):
12121 - When choosing which cells to relay first, relays now favor circuits
12122 that have been quiet recently, to provide lower latency for
12123 low-volume circuits. By default, relays enable or disable this
12124 feature based on a setting in the consensus. They can override
12125 this default by using the new "CircuitPriorityHalflife" config
12126 option. Design and code by Ian Goldberg, Can Tang, and Chris
12128 - Directory authorities now compute consensus weightings that instruct
12129 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
12130 and no flag. Clients use these weightings to distribute network load
12131 more evenly across these different relay types. The weightings are
12132 in the consensus so we can change them globally in the future. Extra
12133 thanks to "outofwords" for finding some nasty security bugs in
12134 the first implementation of this feature.
12136 o Major features (client performance, circuit build timeout):
12137 - Tor now tracks how long it takes to build client-side circuits
12138 over time, and adapts its timeout to local network performance.
12139 Since a circuit that takes a long time to build will also provide
12140 bad performance, we get significant latency improvements by
12141 discarding the slowest 20% of circuits. Specifically, Tor creates
12142 circuits more aggressively than usual until it has enough data
12143 points for a good timeout estimate. Implements proposal 151.
12144 - Circuit build timeout constants can be controlled by consensus
12145 parameters. We set good defaults for these parameters based on
12146 experimentation on broadband and simulated high-latency links.
12147 - Circuit build time learning can be disabled via consensus parameter
12148 or by the client via a LearnCircuitBuildTimeout config option. We
12149 also automatically disable circuit build time calculation if either
12150 AuthoritativeDirectory is set, or if we fail to write our state
12151 file. Implements ticket 1296.
12153 o Major features (relays use their capacity better):
12154 - Set SO_REUSEADDR socket option on all sockets, not just
12155 listeners. This should help busy exit nodes avoid running out of
12156 useable ports just because all the ports have been used in the
12157 near past. Resolves issue 2850.
12158 - Relays now save observed peak bandwidth throughput rates to their
12159 state file (along with total usage, which was already saved),
12160 so that they can determine their correct estimated bandwidth on
12161 restart. Resolves bug 1863, where Tor relays would reset their
12162 estimated bandwidth to 0 after restarting.
12163 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
12164 should give us approximately 40-50% more Guard-flagged nodes,
12165 improving the anonymity the Tor network can provide and also
12166 decreasing the dropoff in throughput that relays experience when
12167 they first get the Guard flag.
12168 - Directory authorities now take changes in router IP address and
12169 ORPort into account when determining router stability. Previously,
12170 if a router changed its IP or ORPort, the authorities would not
12171 treat it as having any downtime for the purposes of stability
12172 calculation, whereas clients would experience downtime since the
12173 change would take a while to propagate to them. Resolves issue 1035.
12174 - New AccelName and AccelDir options add support for dynamic OpenSSL
12175 hardware crypto acceleration engines.
12177 o Major features (relays control their load better):
12178 - Exit relays now try harder to block exit attempts from unknown
12179 relays, to make it harder for people to use them as one-hop proxies
12180 a la tortunnel. Controlled by the refuseunknownexits consensus
12181 parameter (currently enabled), or you can override it on your
12182 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
12183 based on a variant of proposal 163.
12184 - Add separate per-conn write limiting to go with the per-conn read
12185 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
12186 but never per-conn write limits.
12187 - New consensus params "bwconnrate" and "bwconnburst" to let us
12188 rate-limit client connections as they enter the network. It's
12189 controlled in the consensus so we can turn it on and off for
12190 experiments. It's starting out off. Based on proposal 163.
12192 o Major features (controllers):
12193 - Export GeoIP information on bridge usage to controllers even if we
12194 have not yet been running for 24 hours. Now Vidalia bridge operators
12195 can get more accurate and immediate feedback about their
12196 contributions to the network.
12197 - Add an __OwningControllerProcess configuration option and a
12198 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
12199 that when it exits, Tor will shut down. Implements feature 3049.
12201 o Major features (directory authorities):
12202 - Directory authorities now create, vote on, and serve multiple
12203 parallel formats of directory data as part of their voting process.
12204 Partially implements Proposal 162: "Publish the consensus in
12206 - Directory authorities now agree on and publish small summaries
12207 of router information that clients can use in place of regular
12208 server descriptors. This transition will allow Tor 0.2.3 clients
12209 to use far less bandwidth for downloading information about the
12210 network. Begins the implementation of Proposal 158: "Clients
12211 download consensus + microdescriptors".
12212 - The directory voting system is now extensible to use multiple hash
12213 algorithms for signatures and resource selection. Newer formats
12214 are signed with SHA256, with a possibility for moving to a better
12215 hash algorithm in the future.
12216 - Directory authorities can now vote on arbitrary integer values as
12217 part of the consensus process. This is designed to help set
12218 network-wide parameters. Implements proposal 167.
12220 o Major features and bugfixes (node selection):
12221 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
12222 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
12223 options. Previously, we had been ambiguous in describing what
12224 counted as an "exit" node, and what operations exactly "StrictNodes
12225 0" would permit. This created confusion when people saw nodes built
12226 through unexpected circuits, and made it hard to tell real bugs from
12227 surprises. Now the intended behavior is:
12228 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
12229 a node that delivers user traffic outside the Tor network.
12230 . "Entry", in the context of EntryNodes, means a node used as the
12231 first hop of a multihop circuit. It doesn't include direct
12232 connections to directory servers.
12233 . "ExcludeNodes" applies to all nodes.
12234 . "StrictNodes" changes the behavior of ExcludeNodes only. When
12235 StrictNodes is set, Tor should avoid all nodes listed in
12236 ExcludeNodes, even when it will make user requests fail. When
12237 StrictNodes is *not* set, then Tor should follow ExcludeNodes
12238 whenever it can, except when it must use an excluded node to
12239 perform self-tests, connect to a hidden service, provide a
12240 hidden service, fulfill a .exit request, upload directory
12241 information, or fetch directory information.
12242 Collectively, the changes to implement the behavior fix bug 1090.
12243 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
12244 change during a config reload, mark and discard all our origin
12245 circuits. This fix should address edge cases where we change the
12246 config options and but then choose a circuit that we created before
12248 - Make EntryNodes config option much more aggressive even when
12249 StrictNodes is not set. Before it would prepend your requested
12250 entrynodes to your list of guard nodes, but feel free to use others
12251 after that. Now it chooses only from your EntryNodes if any of
12252 those are available, and only falls back to others if a) they're
12253 all down and b) StrictNodes is not set.
12254 - Now we refresh your entry guards from EntryNodes at each consensus
12255 fetch -- rather than just at startup and then they slowly rot as
12256 the network changes.
12257 - Add support for the country code "{??}" in torrc options like
12258 ExcludeNodes, to indicate all routers of unknown country. Closes
12260 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
12261 a node is listed in both, it's treated as excluded.
12262 - ExcludeNodes now applies to directory nodes -- as a preference if
12263 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
12264 Don't exclude all the directory authorities and set StrictNodes to 1
12265 unless you really want your Tor to break.
12266 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
12267 - ExcludeExitNodes now overrides .exit requests.
12268 - We don't use bridges listed in ExcludeNodes.
12269 - When StrictNodes is 1:
12270 . We now apply ExcludeNodes to hidden service introduction points
12271 and to rendezvous points selected by hidden service users. This
12272 can make your hidden service less reliable: use it with caution!
12273 . If we have used ExcludeNodes on ourself, do not try relay
12274 reachability self-tests.
12275 . If we have excluded all the directory authorities, we will not
12276 even try to upload our descriptor if we're a relay.
12277 . Do not honor .exit requests to an excluded node.
12278 - When the set of permitted nodes changes, we now remove any mappings
12279 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
12281 - We never cannibalize a circuit that had excluded nodes on it, even
12282 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
12283 - Improve log messages related to excluded nodes.
12285 o Major features (misc):
12286 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
12287 to help Tor build correctly for Android phones.
12288 - The options SocksPort, ControlPort, and so on now all accept a
12289 value "auto" that opens a socket on an OS-selected port. A
12290 new ControlPortWriteToFile option tells Tor to write its
12291 actual control port or ports to a chosen file. If the option
12292 ControlPortFileGroupReadable is set, the file is created as
12293 group-readable. Now users can run two Tor clients on the same
12294 system without needing to manually mess with parameters. Resolves
12295 part of ticket 3076.
12296 - Tor now supports tunneling all of its outgoing connections over
12297 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12298 configuration options. Code by Christopher Davis.
12300 o Code security improvements:
12301 - Replace all potentially sensitive memory comparison operations
12302 with versions whose runtime does not depend on the data being
12303 compared. This will help resist a class of attacks where an
12304 adversary can use variations in timing information to learn
12305 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12306 implementation by Robert Ransom based partially on code by DJB.)
12307 - Enable Address Space Layout Randomization (ASLR) and Data Execution
12308 Prevention (DEP) by default on Windows to make it harder for
12309 attackers to exploit vulnerabilities. Patch from John Brooks.
12310 - New "--enable-gcc-hardening" ./configure flag (off by default)
12311 to turn on gcc compile time hardening options. It ensures
12312 that signed ints have defined behavior (-fwrapv), enables
12313 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
12314 with canaries (-fstack-protector-all), turns on ASLR protection if
12315 supported by the kernel (-fPIE, -pie), and adds additional security
12316 related warnings. Verified to work on Mac OS X and Debian Lenny.
12317 - New "--enable-linker-hardening" ./configure flag (off by default)
12318 to turn on ELF specific hardening features (relro, now). This does
12319 not work with Mac OS X or any other non-ELF binary format.
12320 - Always search the Windows system directory for system DLLs, and
12321 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
12322 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
12323 current and future memory pages via mlockall(). On supported
12324 platforms (modern Linux and probably BSD but not Windows or OS X),
12325 this should effectively disable any and all attempts to page out
12326 memory. This option requires that you start your Tor as root --
12327 if you use DisableAllSwap, please consider using the User option
12328 to properly reduce the privileges of your Tor.
12330 o Major bugfixes (crashes):
12331 - Fix crash bug on platforms where gmtime and localtime can return
12332 NULL. Windows 7 users were running into this one. Fixes part of bug
12333 2077. Bugfix on all versions of Tor. Found by boboper.
12334 - Introduce minimum/maximum values that clients will believe
12335 from the consensus. Now we'll have a better chance to avoid crashes
12336 or worse when a consensus param has a weird value.
12337 - Fix a rare crash bug that could occur when a client was configured
12338 with a large number of bridges. Fixes bug 2629; bugfix on
12339 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12340 - Do not crash when our configuration file becomes unreadable, for
12341 example due to a permissions change, between when we start up
12342 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12344 - If we're in the pathological case where there's no exit bandwidth
12345 but there is non-exit bandwidth, or no guard bandwidth but there
12346 is non-guard bandwidth, don't crash during path selection. Bugfix
12348 - Fix a crash bug when trying to initialize the evdns module in
12349 Libevent 2. Bugfix on 0.2.1.16-rc.
12351 o Major bugfixes (stability):
12352 - Fix an assert in parsing router descriptors containing IPv6
12353 addresses. This one took down the directory authorities when
12354 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12355 - Fix an uncommon assertion failure when running with DNSPort under
12356 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12357 - Treat an unset $HOME like an empty $HOME rather than triggering an
12358 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
12359 - More gracefully handle corrupt state files, removing asserts
12360 in favor of saving a backup and resetting state.
12361 - Instead of giving an assertion failure on an internal mismatch
12362 on estimated freelist size, just log a BUG warning and try later.
12363 Mitigates but does not fix bug 1125.
12364 - Fix an assert that got triggered when using the TestingTorNetwork
12365 configuration option and then issuing a GETINFO config-text control
12366 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
12367 - If the cached cert file is unparseable, warn but don't exit.
12369 o Privacy fixes (relays/bridges):
12370 - Don't list Windows capabilities in relay descriptors. We never made
12371 use of them, and maybe it's a bad idea to publish them. Bugfix
12373 - If the Nickname configuration option isn't given, Tor would pick a
12374 nickname based on the local hostname as the nickname for a relay.
12375 Because nicknames are not very important in today's Tor and the
12376 "Unnamed" nickname has been implemented, this is now problematic
12377 behavior: It leaks information about the hostname without being
12378 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
12379 introduced the Unnamed nickname. Reported by tagnaq.
12380 - Maintain separate TLS contexts and certificates for incoming and
12381 outgoing connections in bridge relays. Previously we would use the
12382 same TLS contexts and certs for incoming and outgoing connections.
12383 Bugfix on 0.2.0.3-alpha; addresses bug 988.
12384 - Maintain separate identity keys for incoming and outgoing TLS
12385 contexts in bridge relays. Previously we would use the same
12386 identity keys for incoming and outgoing TLS contexts. Bugfix on
12387 0.2.0.3-alpha; addresses the other half of bug 988.
12388 - Make the bridge directory authority refuse to answer directory
12389 requests for "all descriptors". It used to include bridge
12390 descriptors in its answer, which was a major information leak.
12391 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12393 o Privacy fixes (clients):
12394 - When receiving a hidden service descriptor, check that it is for
12395 the hidden service we wanted. Previously, Tor would store any
12396 hidden service descriptors that a directory gave it, whether it
12397 wanted them or not. This wouldn't have let an attacker impersonate
12398 a hidden service, but it did let directories pre-seed a client
12399 with descriptors that it didn't want. Bugfix on 0.0.6.
12400 - Start the process of disabling ".exit" address notation, since it
12401 can be used for a variety of esoteric application-level attacks
12402 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12404 - Reject attempts at the client side to open connections to private
12405 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
12406 a randomly chosen exit node. Attempts to do so are always
12407 ill-defined, generally prevented by exit policies, and usually
12408 in error. This will also help to detect loops in transparent
12409 proxy configurations. You can disable this feature by setting
12410 "ClientRejectInternalAddresses 0" in your torrc.
12411 - Log a notice when we get a new control connection. Now it's easier
12412 for security-conscious users to recognize when a local application
12413 is knocking on their controller door. Suggested by bug 1196.
12415 o Privacy fixes (newnym):
12416 - Avoid linkability based on cached hidden service descriptors: forget
12417 all hidden service descriptors cached as a client when processing a
12418 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12419 - On SIGHUP, do not clear out all TrackHostExits mappings, client
12420 DNS cache entries, and virtual address mappings: that's what
12421 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
12422 - Don't attach new streams to old rendezvous circuits after SIGNAL
12423 NEWNYM. Previously, we would keep using an existing rendezvous
12424 circuit if it remained open (i.e. if it were kept open by a
12425 long-lived stream, or if a new stream were attached to it before
12426 Tor could notice that it was old and no longer in use). Bugfix on
12427 0.1.1.15-rc; fixes bug 3375.
12429 o Major bugfixes (relay bandwidth accounting):
12430 - Fix a bug that could break accounting on 64-bit systems with large
12431 time_t values, making them hibernate for impossibly long intervals.
12432 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
12433 - Fix a bug in bandwidth accounting that could make us use twice
12434 the intended bandwidth when our interval start changes due to
12435 daylight saving time. Now we tolerate skew in stored vs computed
12436 interval starts: if the start of the period changes by no more than
12437 50% of the period's duration, we remember bytes that we transferred
12438 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
12440 o Major bugfixes (bridges):
12441 - Bridges now use "reject *:*" as their default exit policy. Bugfix
12442 on 0.2.0.3-alpha. Fixes bug 1113.
12443 - If you configure your bridge with a known identity fingerprint,
12444 and the bridge authority is unreachable (as it is in at least
12445 one country now), fall back to directly requesting the descriptor
12446 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
12448 - Fix a bug where bridge users who configure the non-canonical
12449 address of a bridge automatically switch to its canonical
12450 address. If a bridge listens at more than one address, it
12451 should be able to advertise those addresses independently and
12452 any non-blocked addresses should continue to work. Bugfix on Tor
12453 0.2.0.3-alpha. Fixes bug 2510.
12454 - If you configure Tor to use bridge A, and then quit and
12455 configure Tor to use bridge B instead (or if you change Tor
12456 to use bridge B via the controller), it would happily continue
12457 to use bridge A if it's still reachable. While this behavior is
12458 a feature if your goal is connectivity, in some scenarios it's a
12459 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
12460 - When the controller configures a new bridge, don't wait 10 to 60
12461 seconds before trying to fetch its descriptor. Bugfix on
12462 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
12464 o Major bugfixes (directory authorities):
12465 - Many relays have been falling out of the consensus lately because
12466 not enough authorities know about their descriptor for them to get
12467 a majority of votes. When we deprecated the v2 directory protocol,
12468 we got rid of the only way that v3 authorities can hear from each
12469 other about other descriptors. Now authorities examine every v3
12470 vote for new descriptors, and fetch them from that authority. Bugfix
12472 - Authorities could be tricked into giving out the Exit flag to relays
12473 that didn't allow exiting to any ports. This bug could screw
12474 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
12475 1238. Bug discovered by Martin Kowalczyk.
12476 - If all authorities restart at once right before a consensus vote,
12477 nobody will vote about "Running", and clients will get a consensus
12478 with no usable relays. Instead, authorities refuse to build a
12479 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
12481 o Major bugfixes (stream-level fairness):
12482 - When receiving a circuit-level SENDME for a blocked circuit, try
12483 to package cells fairly from all the streams that had previously
12484 been blocked on that circuit. Previously, we had started with the
12485 oldest stream, and allowed each stream to potentially exhaust
12486 the circuit's package window. This gave older streams on any
12487 given circuit priority over newer ones. Fixes bug 1937. Detected
12488 originally by Camilo Viecco. This bug was introduced before the
12489 first Tor release, in svn commit r152: it is the new winner of
12490 the longest-lived bug prize.
12491 - Fix a stream fairness bug that would cause newer streams on a given
12492 circuit to get preference when reading bytes from the origin or
12493 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
12494 introduced before the first Tor release, in svn revision r152.
12495 - When the exit relay got a circuit-level sendme cell, it started
12496 reading on the exit streams, even if had 500 cells queued in the
12497 circuit queue already, so the circuit queue just grew and grew in
12498 some cases. We fix this by not re-enabling reading on receipt of a
12499 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
12500 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
12502 - Newly created streams were allowed to read cells onto circuits,
12503 even if the circuit's cell queue was blocked and waiting to drain.
12504 This created potential unfairness, as older streams would be
12505 blocked, but newer streams would gladly fill the queue completely.
12506 We add code to detect this situation and prevent any stream from
12507 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
12510 o Major bugfixes (hidden services):
12511 - Apply circuit timeouts to opened hidden-service-related circuits
12512 based on the correct start time. Previously, we would apply the
12513 circuit build timeout based on time since the circuit's creation;
12514 it was supposed to be applied based on time since the circuit
12515 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
12516 - Improve hidden service robustness: When we find that we have
12517 extended a hidden service's introduction circuit to a relay not
12518 listed as an introduction point in the HS descriptor we currently
12519 have, retry with an introduction point from the current
12520 descriptor. Previously we would just give up. Fixes bugs 1024 and
12521 1930; bugfix on 0.2.0.10-alpha.
12522 - Directory authorities now use data collected from their own
12523 uptime observations when choosing whether to assign the HSDir flag
12524 to relays, instead of trusting the uptime value the relay reports in
12525 its descriptor. This change helps prevent an attack where a small
12526 set of nodes with frequently-changing identity keys can blackhole
12527 a hidden service. (Only authorities need upgrade; others will be
12528 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
12529 - Stop assigning the HSDir flag to relays that disable their
12530 DirPort (and thus will refuse to answer directory requests). This
12531 fix should dramatically improve the reachability of hidden services:
12532 hidden services and hidden service clients pick six HSDir relays
12533 to store and retrieve the hidden service descriptor, and currently
12534 about half of the HSDir relays will refuse to work. Bugfix on
12535 0.2.0.10-alpha; fixes part of bug 1693.
12537 o Major bugfixes (misc):
12538 - Clients now stop trying to use an exit node associated with a given
12539 destination by TrackHostExits if they fail to reach that exit node.
12540 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
12541 - Fix a regression that caused Tor to rebind its ports if it receives
12542 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
12543 - Remove an extra pair of quotation marks around the error
12544 message in control-port STATUS_GENERAL BUG events. Bugfix on
12545 0.1.2.6-alpha; fixes bug 3732.
12547 o Minor features (relays):
12548 - Ensure that no empty [dirreq-](read|write)-history lines are added
12549 to an extrainfo document. Implements ticket 2497.
12550 - When bandwidth accounting is enabled, be more generous with how
12551 much bandwidth we'll use up before entering "soft hibernation".
12552 Previously, we'd refuse new connections and circuits once we'd
12553 used up 95% of our allotment. Now, we use up 95% of our allotment,
12554 AND make sure that we have no more than 500MB (or 3 hours of
12555 expected traffic, whichever is lower) remaining before we enter
12557 - Relays now log the reason for publishing a new relay descriptor,
12558 so we have a better chance of hunting down instances of bug 1810.
12559 Resolves ticket 3252.
12560 - Log a little more clearly about the times at which we're no longer
12561 accepting new connections (e.g. due to hibernating). Resolves
12563 - When AllowSingleHopExits is set, print a warning to explain to the
12564 relay operator why most clients are avoiding her relay.
12565 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
12566 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
12567 clients are already deprecated because of security bugs.
12569 o Minor features (network statistics):
12570 - Directory mirrors that set "DirReqStatistics 1" write statistics
12571 about directory requests to disk every 24 hours. As compared to the
12572 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
12573 improvements: 1) stats are written to disk exactly every 24 hours;
12574 2) estimated shares of v2 and v3 requests are determined as mean
12575 values, not at the end of a measurement period; 3) unresolved
12576 requests are listed with country code '??'; 4) directories also
12577 measure download times.
12578 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
12579 number of exit streams and transferred bytes per port to disk every
12581 - Relays that set "CellStatistics 1" write statistics on how long
12582 cells spend in their circuit queues to disk every 24 hours.
12583 - Entry nodes that set "EntryStatistics 1" write statistics on the
12584 rough number and origins of connecting clients to disk every 24
12586 - Relays that write any of the above statistics to disk and set
12587 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
12588 their extra-info documents. Implements proposal 166.
12590 o Minor features (GeoIP and statistics):
12591 - Provide a log message stating which geoip file we're parsing
12592 instead of just stating that we're parsing the geoip file.
12593 Implements ticket 2432.
12594 - Make sure every relay writes a state file at least every 12 hours.
12595 Previously, a relay could go for weeks without writing its state
12596 file, and on a crash could lose its bandwidth history, capacity
12597 estimates, client country statistics, and so on. Addresses bug 3012.
12598 - Relays report the number of bytes spent on answering directory
12599 requests in extra-info descriptors similar to {read,write}-history.
12600 Implements enhancement 1790.
12601 - Report only the top 10 ports in exit-port stats in order not to
12602 exceed the maximum extra-info descriptor length of 50 KB. Implements
12604 - If writing the state file to disk fails, wait up to an hour before
12605 retrying again, rather than trying again each second. Fixes bug
12606 2346; bugfix on Tor 0.1.1.3-alpha.
12607 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
12608 when we switch from being a public relay to a bridge. Otherwise
12609 there will still be clients that see the relay in their consensus,
12610 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
12612 - Update to the August 2 2011 Maxmind GeoLite Country database.
12614 o Minor features (clients):
12615 - When expiring circuits, use microsecond timers rather than
12616 one-second timers. This can avoid an unpleasant situation where a
12617 circuit is launched near the end of one second and expired right
12618 near the beginning of the next, and prevent fluctuations in circuit
12620 - If we've configured EntryNodes and our network goes away and/or all
12621 our entrynodes get marked down, optimistically retry them all when
12622 a new socks application request appears. Fixes bug 1882.
12623 - Always perform router selections using weighted relay bandwidth,
12624 even if we don't need a high capacity circuit at the time. Non-fast
12625 circuits now only differ from fast ones in that they can use relays
12626 not marked with the Fast flag. This "feature" could turn out to
12627 be a horrible bug; we should investigate more before it goes into
12629 - When we run out of directory information such that we can't build
12630 circuits, but then get enough that we can build circuits, log when
12631 we actually construct a circuit, so the user has a better chance of
12632 knowing what's going on. Fixes bug 1362.
12633 - Log SSL state transitions at debug level during handshake, and
12634 include SSL states in error messages. This may help debug future
12635 SSL handshake issues.
12637 o Minor features (directory authorities):
12638 - When a router changes IP address or port, authorities now launch
12639 a new reachability test for it. Implements ticket 1899.
12640 - Directory authorities now reject relays running any versions of
12641 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
12642 known bugs that keep RELAY_EARLY cells from working on rendezvous
12643 circuits. Followup to fix for bug 2081.
12644 - Directory authorities now reject relays running any version of Tor
12645 older than 0.2.0.26-rc. That version is the earliest that fetches
12646 current directory information correctly. Fixes bug 2156.
12647 - Directory authorities now do an immediate reachability check as soon
12648 as they hear about a new relay. This change should slightly reduce
12649 the time between setting up a relay and getting listed as running
12650 in the consensus. It should also improve the time between setting
12651 up a bridge and seeing use by bridge users.
12652 - Directory authorities no longer launch a TLS connection to every
12653 relay as they startup. Now that we have 2k+ descriptors cached,
12654 the resulting network hiccup is becoming a burden. Besides,
12655 authorities already avoid voting about Running for the first half
12656 hour of their uptime.
12657 - Directory authorities now log the source of a rejected POSTed v3
12658 networkstatus vote, so we can track failures better.
12659 - Backport code from 0.2.3.x that allows directory authorities to
12660 clean their microdescriptor caches. Needed to resolve bug 2230.
12662 o Minor features (hidden services):
12663 - Use computed circuit-build timeouts to decide when to launch
12664 parallel introduction circuits for hidden services. (Previously,
12665 we would retry after 15 seconds.)
12666 - Don't allow v0 hidden service authorities to act as clients.
12667 Required by fix for bug 3000.
12668 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
12669 by fix for bug 3000.
12670 - Make hidden services work better in private Tor networks by not
12671 requiring any uptime to join the hidden service descriptor
12672 DHT. Implements ticket 2088.
12673 - Log (at info level) when purging pieces of hidden-service-client
12674 state because of SIGNAL NEWNYM.
12676 o Minor features (controller interface):
12677 - New "GETINFO net/listeners/(type)" controller command to return
12678 a list of addresses and ports that are bound for listeners for a
12679 given connection type. This is useful when the user has configured
12680 "SocksPort auto" and the controller needs to know which port got
12681 chosen. Resolves another part of ticket 3076.
12682 - Have the controller interface give a more useful message than
12683 "Internal Error" in response to failed GETINFO requests.
12684 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
12685 event, to give information on the current rate of circuit timeouts
12686 over our stored history.
12687 - The 'EXTENDCIRCUIT' control port command can now be used with
12688 a circ id of 0 and no path. This feature will cause Tor to build
12689 a new 'fast' general purpose circuit using its own path selection
12691 - Added a BUILDTIMEOUT_SET controller event to describe changes
12692 to the circuit build timeout.
12693 - New controller command "getinfo config-text". It returns the
12694 contents that Tor would write if you send it a SAVECONF command,
12695 so the controller can write the file to disk itself.
12697 o Minor features (controller protocol):
12698 - Add a new ControlSocketsGroupWritable configuration option: when
12699 it is turned on, ControlSockets are group-writeable by the default
12700 group of the current user. Patch by Jérémy Bobbio; implements
12702 - Tor now refuses to create a ControlSocket in a directory that is
12703 world-readable (or group-readable if ControlSocketsGroupWritable
12704 is 0). This is necessary because some operating systems do not
12705 enforce permissions on an AF_UNIX sockets. Permissions on the
12706 directory holding the socket, however, seems to work everywhere.
12707 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
12708 not. This would lead to a cookie that is still not group readable.
12709 Closes bug 1843. Suggested by katmagic.
12710 - Future-proof the controller protocol a bit by ignoring keyword
12711 arguments we do not recognize.
12713 o Minor features (more useful logging):
12714 - Revise most log messages that refer to nodes by nickname to
12715 instead use the "$key=nickname at address" format. This should be
12716 more useful, especially since nicknames are less and less likely
12717 to be unique. Resolves ticket 3045.
12718 - When an HTTPS proxy reports "403 Forbidden", we now explain
12719 what it means rather than calling it an unexpected status code.
12720 Closes bug 2503. Patch from Michael Yakubovich.
12721 - Rate-limit a warning about failures to download v2 networkstatus
12722 documents. Resolves part of bug 1352.
12723 - Rate-limit the "your application is giving Tor only an IP address"
12724 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
12725 - Rate-limit "Failed to hand off onionskin" warnings.
12726 - When logging a rate-limited warning, we now mention how many messages
12727 got suppressed since the last warning.
12728 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
12729 2 no signature, 4 required" messages about consensus signatures
12730 easier to read, and make sure they get logged at the same severity
12731 as the messages explaining which keys are which. Fixes bug 1290.
12732 - Don't warn when we have a consensus that we can't verify because
12733 of missing certificates, unless those certificates are ones
12734 that we have been trying and failing to download. Fixes bug 1145.
12736 o Minor features (log domains):
12737 - Add documentation for configuring logging at different severities in
12738 different log domains. We've had this feature since 0.2.1.1-alpha,
12739 but for some reason it never made it into the manpage. Fixes
12741 - Make it simpler to specify "All log domains except for A and B".
12742 Previously you needed to say "[*,~A,~B]". Now you can just say
12744 - Add a "LogMessageDomains 1" option to include the domains of log
12745 messages along with the messages. Without this, there's no way
12746 to use log domains without reading the source or doing a lot
12748 - Add a new "Handshake" log domain for activities that happen
12749 during the TLS handshake.
12751 o Minor features (build process):
12752 - Make compilation with clang possible when using
12753 "--enable-gcc-warnings" by removing two warning options that clang
12754 hasn't implemented yet and by fixing a few warnings. Resolves
12756 - Detect platforms that brokenly use a signed size_t, and refuse to
12757 build there. Found and analyzed by doorss and rransom.
12758 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
12760 - Add support for statically linking zlib by specifying
12761 "--enable-static-zlib", to go with our support for statically
12762 linking openssl and libevent. Resolves bug 1358.
12763 - Instead of adding the svn revision to the Tor version string, report
12764 the git commit (when we're building from a git checkout).
12765 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
12767 - New --digests command-line switch to output the digests of the
12768 source files Tor was built with.
12769 - Generate our manpage and HTML documentation using Asciidoc. This
12770 change should make it easier to maintain the documentation, and
12771 produce nicer HTML. The build process fails if asciidoc cannot
12772 be found and building with asciidoc isn't disabled (via the
12773 "--disable-asciidoc" argument to ./configure. Skipping the manpage
12774 speeds up the build considerably.
12776 o Minor features (options / torrc):
12777 - Warn when the same option is provided more than once in a torrc
12778 file, on the command line, or in a single SETCONF statement, and
12779 the option is one that only accepts a single line. Closes bug 1384.
12780 - Warn when the user configures two HiddenServiceDir lines that point
12781 to the same directory. Bugfix on 0.0.6 (the version introducing
12782 HiddenServiceDir); fixes bug 3289.
12783 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
12784 do individual connection-level rate limiting of clients. The torrc
12785 config options with the same names trump the consensus params, if
12786 both are present. Replaces the old "bwconnrate" and "bwconnburst"
12787 consensus params which were broken from 0.2.2.7-alpha through
12788 0.2.2.14-alpha. Closes bug 1947.
12789 - New config option "WarnUnsafeSocks 0" disables the warning that
12790 occurs whenever Tor receives a socks handshake using a version of
12791 the socks protocol that can only provide an IP address (rather
12792 than a hostname). Setups that do DNS locally over Tor are fine,
12793 and we shouldn't spam the logs in that case.
12794 - New config option "CircuitStreamTimeout" to override our internal
12795 timeout schedule for how many seconds until we detach a stream from
12796 a circuit and try a new circuit. If your network is particularly
12797 slow, you might want to set this to a number like 60.
12798 - New options for SafeLogging to allow scrubbing only log messages
12799 generated while acting as a relay. Specify "SafeLogging relay" if
12800 you want to ensure that only messages known to originate from
12801 client use of the Tor process will be logged unsafely.
12802 - Time and memory units in the configuration file can now be set to
12803 fractional units. For example, "2.5 GB" is now a valid value for
12805 - Support line continuations in the torrc config file. If a line
12806 ends with a single backslash character, the newline is ignored, and
12807 the configuration value is treated as continuing on the next line.
12810 o Minor features (unit tests):
12811 - Revise our unit tests to use the "tinytest" framework, so we
12812 can run tests in their own processes, have smarter setup/teardown
12813 code, and so on. The unit test code has moved to its own
12814 subdirectory, and has been split into multiple modules.
12815 - Add a unit test for cross-platform directory-listing code.
12816 - Add some forgotten return value checks during unit tests. Found
12818 - Use GetTempDir to find the proper temporary directory location on
12819 Windows when generating temporary files for the unit tests. Patch
12822 o Minor features (misc):
12823 - The "torify" script now uses torsocks where available.
12824 - Make Libevent log messages get delivered to controllers later,
12825 and not from inside the Libevent log handler. This prevents unsafe
12826 reentrant Libevent calls while still letting the log messages
12828 - Certain Tor clients (such as those behind check.torproject.org) may
12829 want to fetch the consensus in an extra early manner. To enable this
12830 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12831 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12832 as only certain clients who must have this information sooner should
12834 - Expand homedirs passed to tor-checkkey. This should silence a
12835 coverity complaint about passing a user-supplied string into
12836 open() without checking it.
12837 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
12838 used on bridges, and it makes bridge scanning somewhat easier.
12839 - Create the /var/run/tor directory on startup on OpenSUSE if it is
12840 not already created. Patch from Andreas Stieger. Fixes bug 2573.
12842 o Minor bugfixes (relays):
12843 - When a relay decides that its DNS is too broken for it to serve
12844 as an exit server, it advertised itself as a non-exit, but
12845 continued to act as an exit. This could create accidental
12846 partitioning opportunities for users. Instead, if a relay is
12847 going to advertise reject *:* as its exit policy, it should
12848 really act with exit policy "reject *:*". Fixes bug 2366.
12849 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
12850 - Publish a router descriptor even if generating an extra-info
12851 descriptor fails. Previously we would not publish a router
12852 descriptor without an extra-info descriptor; this can cause fast
12853 exit relays collecting exit-port statistics to drop from the
12854 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
12855 - When we're trying to guess whether we know our IP address as
12856 a relay, we would log various ways that we failed to guess
12857 our address, but never log that we ended up guessing it
12858 successfully. Now add a log line to help confused and anxious
12859 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
12860 - For bandwidth accounting, calculate our expected bandwidth rate
12861 based on the time during which we were active and not in
12862 soft-hibernation during the last interval. Previously, we were
12863 also considering the time spent in soft-hibernation. If this
12864 was a long time, we would wind up underestimating our bandwidth
12865 by a lot, and skewing our wakeup time towards the start of the
12866 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
12867 - Demote a confusing TLS warning that relay operators might get when
12868 someone tries to talk to their ORPort. It is not the operator's
12869 fault, nor can they do anything about it. Fixes bug 1364; bugfix
12871 - Change "Application request when we're believed to be offline."
12872 notice to "Application request when we haven't used client
12873 functionality lately.", to clarify that it's not an error. Bugfix
12874 on 0.0.9.3; fixes bug 1222.
12876 o Minor bugfixes (bridges):
12877 - When a client starts or stops using bridges, never use a circuit
12878 that was built before the configuration change. This behavior could
12879 put at risk a user who uses bridges to ensure that her traffic
12880 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
12882 - Do not reset the bridge descriptor download status every time we
12883 re-parse our configuration or get a configuration change. Fixes
12884 bug 3019; bugfix on 0.2.0.3-alpha.
12885 - Users couldn't configure a regular relay to be their bridge. It
12886 didn't work because when Tor fetched the bridge descriptor, it found
12887 that it already had it, and didn't realize that the purpose of the
12888 descriptor had changed. Now we replace routers with a purpose other
12889 than bridge with bridge descriptors when fetching them. Bugfix on
12890 0.1.1.9-alpha. Fixes bug 1776.
12891 - In the special case where you configure a public exit relay as your
12892 bridge, Tor would be willing to use that exit relay as the last
12893 hop in your circuit as well. Now we fail that circuit instead.
12894 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
12896 o Minor bugfixes (clients):
12897 - We now ask the other side of a stream (the client or the exit)
12898 for more data on that stream when the amount of queued data on
12899 that stream dips low enough. Previously, we wouldn't ask the
12900 other side for more data until either it sent us more data (which
12901 it wasn't supposed to do if it had exhausted its window!) or we
12902 had completely flushed all our queued data. This flow control fix
12903 should improve throughput. Fixes bug 2756; bugfix on the earliest
12904 released versions of Tor (svn commit r152).
12905 - When a client finds that an origin circuit has run out of 16-bit
12906 stream IDs, we now mark it as unusable for new streams. Previously,
12907 we would try to close the entire circuit. Bugfix on 0.0.6.
12908 - Make it explicit that we don't cannibalize one-hop circuits. This
12909 happens in the wild, but doesn't turn out to be a problem because
12910 we fortunately don't use those circuits. Many thanks to outofwords
12911 for the initial analysis and to swissknife who confirmed that
12912 two-hop circuits are actually created.
12913 - Resolve an edge case in path weighting that could make us misweight
12914 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
12915 - Make the DNSPort option work with libevent 2.x. Don't alter the
12916 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
12918 o Minor bugfixes (directory authorities):
12919 - Make directory authorities more accurate at recording when
12920 relays that have failed several reachability tests became
12921 unreachable, so we can provide more accuracy at assigning Stable,
12922 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
12923 - Directory authorities are now more robust to hops back in time
12924 when calculating router stability. Previously, if a run of uptime
12925 or downtime appeared to be negative, the calculation could give
12926 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
12928 - Directory authorities will now attempt to download consensuses
12929 if their own efforts to make a live consensus have failed. This
12930 change means authorities that restart will fetch a valid
12931 consensus, and it means authorities that didn't agree with the
12932 current consensus will still fetch and serve it if it has enough
12933 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
12934 - Never vote for a server as "Running" if we have a descriptor for
12935 it claiming to be hibernating, and that descriptor was published
12936 more recently than our last contact with the server. Bugfix on
12937 0.2.0.3-alpha; fixes bug 911.
12938 - Directory authorities no longer change their opinion of, or vote on,
12939 whether a router is Running, unless they have themselves been
12940 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12943 o Minor bugfixes (hidden services):
12944 - Log malformed requests for rendezvous descriptors as protocol
12945 warnings, not warnings. Also, use a more informative log message
12946 in case someone sees it at log level warning without prior
12947 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
12948 - Accept hidden service descriptors if we think we might be a hidden
12949 service directory, regardless of what our consensus says. This
12950 helps robustness, since clients and hidden services can sometimes
12951 have a more up-to-date view of the network consensus than we do,
12952 and if they think that the directory authorities list us a HSDir,
12953 we might actually be one. Related to bug 2732; bugfix on
12955 - Correct the warning displayed when a rendezvous descriptor exceeds
12956 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12958 - Clients and hidden services now use HSDir-flagged relays for hidden
12959 service descriptor downloads and uploads even if the relays have no
12960 DirPort set and the client has disabled TunnelDirConns. This will
12961 eventually allow us to give the HSDir flag to relays with no
12962 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
12963 - Only limit the lengths of single HS descriptors, even when multiple
12964 HS descriptors are published to an HSDir relay in a single POST
12965 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
12967 o Minor bugfixes (controllers):
12968 - Allow GETINFO fingerprint to return a fingerprint even when
12969 we have not yet built a router descriptor. Fixes bug 3577;
12970 bugfix on 0.2.0.1-alpha.
12971 - Send a SUCCEEDED stream event to the controller when a reverse
12972 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
12973 discovered by katmagic.
12974 - Remove a trailing asterisk from "exit-policy/default" in the
12975 output of the control port command "GETINFO info/names". Bugfix
12977 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
12978 2917. Bugfix on 0.1.1.1-alpha.
12979 - When we restart our relay, we might get a successful connection
12980 from the outside before we've started our reachability tests,
12981 triggering a warning: "ORPort found reachable, but I have no
12982 routerinfo yet. Failing to inform controller of success." This
12983 bug was harmless unless Tor is running under a controller
12984 like Vidalia, in which case the controller would never get a
12985 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12987 - When a controller changes TrackHostExits, remove mappings for
12988 hosts that should no longer have their exits tracked. Bugfix on
12990 - When a controller changes VirtualAddrNetwork, remove any mappings
12991 for hosts that were automapped to the old network. Bugfix on
12993 - When a controller changes one of the AutomapHosts* options, remove
12994 any mappings for hosts that should no longer be automapped. Bugfix
12996 - Fix an off-by-one error in calculating some controller command
12997 argument lengths. Fortunately, this mistake is harmless since
12998 the controller code does redundant NUL termination too. Found by
12999 boboper. Bugfix on 0.1.1.1-alpha.
13000 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
13001 would return "551 Internal error" rather than "552 Unrecognized key
13002 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
13003 - Don't spam the controller with events when we have no file
13004 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
13005 for log messages was already solved from bug 748.)
13006 - Emit a GUARD DROPPED controller event for a case we missed.
13007 - Ensure DNS requests launched by "RESOLVE" commands from the
13008 controller respect the __LeaveStreamsUnattached setconf options. The
13009 same goes for requests launched via DNSPort or transparent
13010 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
13012 o Minor bugfixes (config options):
13013 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
13014 Change the limit to 512 characters by removing base64 newlines.
13015 Fixes bug 2752. Fix by Michael Yakubovich.
13016 - Complain if PublishServerDescriptor is given multiple arguments that
13017 include 0 or 1. This configuration will be rejected in the future.
13018 Bugfix on 0.2.0.1-alpha; closes bug 1107.
13019 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
13020 Bugfix on 0.2.0.13-alpha; closes bug 928.
13022 o Minor bugfixes (log subsystem fixes):
13023 - When unable to format an address as a string, report its value
13024 as "???" rather than reusing the last formatted address. Bugfix
13026 - Be more consistent in our treatment of file system paths. "~" should
13027 get expanded to the user's home directory in the Log config option.
13028 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
13029 feature for the -f and --DataDirectory options.
13031 o Minor bugfixes (memory management):
13032 - Don't stack-allocate the list of supplementary GIDs when we're
13033 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13034 could take up to 256K, which is way too much stack. Found by
13035 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13036 - Save a couple bytes in memory allocation every time we escape
13037 certain characters in a string. Patch from Florian Zumbiehl.
13039 o Minor bugfixes (protocol correctness):
13040 - When checking for 1024-bit keys, check for 1024 bits, not 128
13041 bytes. This allows Tor to correctly discard keys of length 1017
13042 through 1023. Bugfix on 0.0.9pre5.
13043 - Require that introduction point keys and onion handshake keys
13044 have a public exponent of 65537. Starts to fix bug 3207; bugfix
13046 - Handle SOCKS messages longer than 128 bytes long correctly, rather
13047 than waiting forever for them to finish. Fixes bug 2330; bugfix
13048 on 0.2.0.16-alpha. Found by doorss.
13049 - Never relay a cell for a circuit we have already destroyed.
13050 Between marking a circuit as closeable and finally closing it,
13051 it may have been possible for a few queued cells to get relayed,
13052 even though they would have been immediately dropped by the next
13053 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
13054 - Never queue a cell for a circuit that's already been marked
13056 - Fix a spec conformance issue: the network-status-version token
13057 must be the first token in a v3 consensus or vote. Discovered by
13058 "parakeep". Bugfix on 0.2.0.3-alpha.
13059 - A networkstatus vote must contain exactly one signature. Spec
13060 conformance issue. Bugfix on 0.2.0.3-alpha.
13061 - When asked about a DNS record type we don't support via a
13062 client DNSPort, reply with NOTIMPL rather than an empty
13063 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
13064 - Make more fields in the controller protocol case-insensitive, since
13065 control-spec.txt said they were.
13067 o Minor bugfixes (log messages):
13068 - Fix a log message that said "bits" while displaying a value in
13069 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
13071 - Downgrade "no current certificates known for authority" message from
13072 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
13073 - Correctly describe errors that occur when generating a TLS object.
13074 Previously we would attribute them to a failure while generating a
13075 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
13077 - Fix an instance where a Tor directory mirror might accidentally
13078 log the IP address of a misbehaving Tor client. Bugfix on
13080 - Stop logging at severity 'warn' when some other Tor client tries
13081 to establish a circuit with us using weak DH keys. It's a protocol
13082 violation, but that doesn't mean ordinary users need to hear about
13083 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
13084 - If your relay can't keep up with the number of incoming create
13085 cells, it would log one warning per failure into your logs. Limit
13086 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
13088 o Minor bugfixes (build fixes):
13089 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13090 - When warning about missing zlib development packages during compile,
13091 give the correct package names. Bugfix on 0.2.0.1-alpha.
13092 - Fix warnings that newer versions of autoconf produce during
13093 ./autogen.sh. These warnings appear to be harmless in our case,
13094 but they were extremely verbose. Fixes bug 2020.
13095 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
13098 o Minor bugfixes (portability):
13099 - Write several files in text mode, on OSes that distinguish text
13100 mode from binary mode (namely, Windows). These files are:
13101 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13102 that collect those statistics; 'client_keys' and 'hostname' for
13103 hidden services that use authentication; and (in the tor-gencert
13104 utility) newly generated identity and signing keys. Previously,
13105 we wouldn't specify text mode or binary mode, leading to an
13106 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13107 the DirRecordUsageByCountry option which would have triggered
13108 the assertion failure was added), although this assertion failure
13109 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13110 - Selectively disable deprecation warnings on OS X because Lion
13111 started deprecating the shipped copy of openssl. Fixes bug 3643.
13112 - Use a wide type to hold sockets when built for 64-bit Windows.
13114 - Fix an issue that prevented static linking of libevent on
13115 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
13116 where we introduced the "--with-static-libevent" configure option.
13117 - Fix a bug with our locking implementation on Windows that couldn't
13118 correctly detect when a file was already locked. Fixes bug 2504,
13119 bugfix on 0.2.1.6-alpha.
13120 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
13122 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
13123 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
13126 o Minor bugfixes (code correctness):
13127 - Always NUL-terminate the sun_path field of a sockaddr_un before
13128 passing it to the kernel. (Not a security issue: kernels are
13129 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13130 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13131 - Make connection_printf_to_buf()'s behavior sane. Its callers
13132 expect it to emit a CRLF iff the format string ends with CRLF;
13133 it actually emitted a CRLF iff (a) the format string ended with
13134 CRLF or (b) the resulting string was over 1023 characters long or
13135 (c) the format string did not end with CRLF *and* the resulting
13136 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
13137 fixes part of bug 3407.
13138 - Make send_control_event_impl()'s behavior sane. Its callers
13139 expect it to always emit a CRLF at the end of the string; it
13140 might have emitted extra control characters as well. Bugfix on
13141 0.1.1.9-alpha; fixes another part of bug 3407.
13142 - Make crypto_rand_int() check the value of its input correctly.
13143 Previously, it accepted values up to UINT_MAX, but could return a
13144 negative number if given a value above INT_MAX+1. Found by George
13145 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
13146 - Fix a potential null-pointer dereference while computing a
13147 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
13149 - If we fail to compute the identity digest of a v3 legacy keypair,
13150 warn, and don't use a buffer-full of junk instead. Bugfix on
13151 0.2.1.1-alpha; fixes bug 3106.
13152 - Resolve an untriggerable issue in smartlist_string_num_isin(),
13153 where if the function had ever in the future been used to check
13154 for the presence of a too-large number, it would have given an
13155 incorrect result. (Fortunately, we only used it for 16-bit
13156 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
13157 - Be more careful about reporting the correct error from a failed
13158 connect() system call. Under some circumstances, it was possible to
13159 look at an incorrect value for errno when sending the end reason.
13160 Bugfix on 0.1.0.1-rc.
13161 - Correctly handle an "impossible" overflow cases in connection byte
13162 counting, where we write or read more than 4GB on an edge connection
13163 in a single second. Bugfix on 0.1.2.8-beta.
13164 - Avoid a double mark-for-free warning when failing to attach a
13165 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
13167 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
13168 found by "cypherpunks". This bug was introduced before the first
13169 Tor release, in svn commit r110.
13170 - Fix a bug in bandwidth history state parsing that could have been
13171 triggered if a future version of Tor ever changed the timing
13172 granularity at which bandwidth history is measured. Bugfix on
13173 Tor 0.1.1.11-alpha.
13174 - Add assertions to check for overflow in arguments to
13175 base32_encode() and base32_decode(); fix a signed-unsigned
13176 comparison there too. These bugs are not actually reachable in Tor,
13177 but it's good to prevent future errors too. Found by doorss.
13178 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
13180 - Set target port in get_interface_address6() correctly. Bugfix
13181 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
13182 - Fix an impossible-to-actually-trigger buffer overflow in relay
13183 descriptor generation. Bugfix on 0.1.0.15.
13184 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
13186 o Minor bugfixes (code improvements):
13187 - After we free an internal connection structure, overwrite it
13188 with a different memory value than we use for overwriting a freed
13189 internal circuit structure. Should help with debugging. Suggested
13191 - If OpenSSL fails to make a duplicate of a private or public key, log
13192 an error message and try to exit cleanly. May help with debugging
13193 if bug 1209 ever remanifests.
13194 - Some options used different conventions for uppercasing of acronyms
13195 when comparing manpage and source. Fix those in favor of the
13196 manpage, as it makes sense to capitalize acronyms.
13197 - Take a first step towards making or.h smaller by splitting out
13198 function definitions for all source files in src/or/. Leave
13199 structures and defines in or.h for now.
13200 - Remove a few dead assignments during router parsing. Found by
13202 - Don't use 1-bit wide signed bit fields. Found by coverity.
13203 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
13204 None of the cases where we did this before were wrong, but by making
13205 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
13206 - The memarea code now uses a sentinel value at the end of each area
13207 to make sure nothing writes beyond the end of an area. This might
13208 help debug some conceivable causes of bug 930.
13209 - Always treat failure to allocate an RSA key as an unrecoverable
13211 - Add some more defensive programming for architectures that can't
13212 handle unaligned integer accesses. We don't know of any actual bugs
13213 right now, but that's the best time to fix them. Fixes bug 1943.
13215 o Minor bugfixes (misc):
13216 - Fix a rare bug in rend_fn unit tests: we would fail a test when
13217 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
13218 on 0.2.0.10-alpha; fixes bug 1808.
13219 - Where available, use Libevent 2.0's periodic timers so that our
13220 once-per-second cleanup code gets called even more closely to
13221 once per second than it would otherwise. Fixes bug 943.
13222 - Ignore OutboundBindAddress when connecting to localhost.
13223 Connections to localhost need to come _from_ localhost, or else
13224 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
13226 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
13228 - If any of the v3 certs we download are unparseable, we should
13229 actually notice the failure so we don't retry indefinitely. Bugfix
13230 on 0.2.0.x; reported by "rotator".
13231 - When Tor fails to parse a descriptor of any kind, dump it to disk.
13232 Might help diagnosing bug 1051.
13233 - Make our 'torify' script more portable; if we have only one of
13234 'torsocks' or 'tsocks' installed, don't complain to the user;
13235 and explain our warning about tsocks better.
13236 - Fix some urls in the exit notice file and make it XHTML1.1 strict
13237 compliant. Based on a patch from Christian Kujau.
13239 o Documentation changes:
13240 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
13241 - Resolve all doxygen warnings except those for missing documentation.
13243 - Add doxygen documentation for more functions, fields, and types.
13244 - Convert the HACKING file to asciidoc, and add a few new sections
13245 to it, explaining how we use Git, how we make changelogs, and
13246 what should go in a patch.
13247 - Document the default socks host and port (127.0.0.1:9050) for
13249 - Removed some unnecessary files from the source distribution. The
13250 AUTHORS file has now been merged into the people page on the
13251 website. The roadmaps and design doc can now be found in the
13252 projects directory in svn.
13254 o Deprecated and removed features (config):
13255 - Remove the torrc.complete file. It hasn't been kept up to date
13256 and users will have better luck checking out the manpage.
13257 - Remove the HSAuthorityRecordStats option that version 0 hidden
13258 service authorities could use to track statistics of overall v0
13259 hidden service usage.
13260 - Remove the obsolete "NoPublish" option; it has been flagged
13261 as obsolete and has produced a warning since 0.1.1.18-rc.
13262 - Caches no longer download and serve v2 networkstatus documents
13263 unless FetchV2Networkstatus flag is set: these documents haven't
13264 haven't been used by clients or relays since 0.2.0.x. Resolves
13267 o Deprecated and removed features (controller):
13268 - The controller no longer accepts the old obsolete "addr-mappings/"
13269 or "unregistered-servers-" GETINFO values.
13270 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
13271 always on; using them is necessary for correct forward-compatible
13274 o Deprecated and removed features (misc):
13275 - Hidden services no longer publish version 0 descriptors, and clients
13276 do not request or use version 0 descriptors. However, the old hidden
13277 service authorities still accept and serve version 0 descriptors
13278 when contacted by older hidden services/clients.
13279 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13280 anything since 0.2.1.16-rc.
13281 - Remove everything related to building the expert bundle for OS X.
13282 It has confused many users, doesn't work right on OS X 10.6,
13283 and is hard to get rid of once installed. Resolves bug 1274.
13284 - Remove support for .noconnect style addresses. Nobody was using
13285 them, and they provided another avenue for detecting Tor users
13286 via application-level web tricks.
13287 - When we fixed bug 1038 we had to put in a restriction not to send
13288 RELAY_EARLY cells on rend circuits. This was necessary as long
13289 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
13290 active. Now remove this obsolete check. Resolves bug 2081.
13291 - Remove workaround code to handle directory responses from servers
13292 that had bug 539 (they would send HTTP status 503 responses _and_
13293 send a body too). Since only server versions before
13294 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
13295 keep the workaround in place.
13296 - Remove the old 'fuzzy time' logic. It was supposed to be used for
13297 handling calculations where we have a known amount of clock skew and
13298 an allowed amount of unknown skew. But we only used it in three
13299 places, and we never adjusted the known/unknown skew values. This is
13300 still something we might want to do someday, but if we do, we'll
13301 want to do it differently.
13302 - Remove the "--enable-iphone" option to ./configure. According to
13303 reports from Marco Bonetti, Tor builds fine without any special
13304 tweaking on recent iPhone SDK versions.
13307 Changes in version 0.2.1.30 - 2011-02-23
13308 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
13309 change is a slight tweak to Tor's TLS handshake that makes relays
13310 and bridges that run this new version reachable from Iran again.
13311 We don't expect this tweak will win the arms race long-term, but it
13312 buys us time until we roll out a better solution.
13315 - Stop sending a CLOCK_SKEW controller status event whenever
13316 we fetch directory information from a relay that has a wrong clock.
13317 Instead, only inform the controller when it's a trusted authority
13318 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
13319 the rest of bug 1074.
13320 - Fix a bounds-checking error that could allow an attacker to
13321 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
13322 Found by "piebeer".
13323 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
13324 Tor would ignore their RelayBandwidthBurst setting,
13325 potentially using more bandwidth than expected. Bugfix on
13326 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
13327 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
13328 hidserv" in her torrc. The 'hidserv' argument never controlled
13329 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
13332 - Adjust our TLS Diffie-Hellman parameters to match those used by
13334 - Update to the February 1 2011 Maxmind GeoLite Country database.
13337 - Check for and reject overly long directory certificates and
13338 directory tokens before they have a chance to hit any assertions.
13339 Bugfix on 0.2.1.28. Found by "doorss".
13340 - Bring the logic that gathers routerinfos and assesses the
13341 acceptability of circuits into line. This prevents a Tor OP from
13342 getting locked in a cycle of choosing its local OR as an exit for a
13343 path (due to a .exit request) and then rejecting the circuit because
13344 its OR is not listed yet. It also prevents Tor clients from using an
13345 OR running in the same instance as an exit (due to a .exit request)
13346 if the OR does not meet the same requirements expected of an OR
13347 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
13349 o Packaging changes:
13350 - Stop shipping the Tor specs files and development proposal documents
13351 in the tarball. They are now in a separate git repository at
13352 git://git.torproject.org/torspec.git
13353 - Do not include Git version tags as though they are SVN tags when
13354 generating a tarball from inside a repository that has switched
13355 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
13358 Changes in version 0.2.1.29 - 2011-01-15
13359 Tor 0.2.1.29 continues our recent code security audit work. The main
13360 fix resolves a remote heap overflow vulnerability that can allow remote
13361 code execution. Other fixes address a variety of assert and crash bugs,
13362 most of which we think are hard to exploit remotely.
13364 o Major bugfixes (security):
13365 - Fix a heap overflow bug where an adversary could cause heap
13366 corruption. This bug probably allows remote code execution
13367 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
13369 - Prevent a denial-of-service attack by disallowing any
13370 zlib-compressed data whose compression factor is implausibly
13371 high. Fixes part of bug 2324; reported by "doorss".
13372 - Zero out a few more keys in memory before freeing them. Fixes
13373 bug 2384 and part of bug 2385. These key instances found by
13374 "cypherpunks", based on Andrew Case's report about being able
13375 to find sensitive data in Tor's memory space if you have enough
13376 permissions. Bugfix on 0.0.2pre9.
13378 o Major bugfixes (crashes):
13379 - Prevent calls to Libevent from inside Libevent log handlers.
13380 This had potential to cause a nasty set of crashes, especially
13381 if running Libevent with debug logging enabled, and running
13382 Tor with a controller watching for low-severity log messages.
13383 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
13384 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
13385 underflow errors there too. Fixes the other part of bug 2324.
13386 - Fix a bug where we would assert if we ever had a
13387 cached-descriptors.new file (or another file read directly into
13388 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
13389 on 0.2.1.25. Found by doorss.
13390 - Fix some potential asserts and parsing issues with grossly
13391 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
13394 o Minor bugfixes (other):
13395 - Fix a bug with handling misformed replies to reverse DNS lookup
13396 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
13397 bug reported by doorss.
13398 - Fix compilation on mingw when a pthreads compatibility library
13399 has been installed. (We don't want to use it, so we shouldn't
13400 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
13401 - Fix a bug where we would declare that we had run out of virtual
13402 addresses when the address space was only half-exhausted. Bugfix
13404 - Correctly handle the case where AutomapHostsOnResolve is set but
13405 no virtual addresses are available. Fixes bug 2328; bugfix on
13406 0.1.2.1-alpha. Bug found by doorss.
13407 - Correctly handle wrapping around when we run out of virtual
13408 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
13411 - Update to the January 1 2011 Maxmind GeoLite Country database.
13412 - Introduce output size checks on all of our decryption functions.
13415 - Tor does not build packages correctly with Automake 1.6 and earlier;
13416 added a check to Makefile.am to make sure that we're building with
13417 Automake 1.7 or later.
13418 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
13419 because we built it with a too-old version of automake. Thus that
13420 release broke ./configure --enable-openbsd-malloc, which is popular
13421 among really fast exit relays on Linux.
13424 Changes in version 0.2.1.28 - 2010-12-17
13425 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
13426 exploitable bugs. We also took this opportunity to change the IP address
13427 for one of our directory authorities, and to update the geoip database
13431 - Fix a remotely exploitable bug that could be used to crash instances
13432 of Tor remotely by overflowing on the heap. Remote-code execution
13433 hasn't been confirmed, but can't be ruled out. Everyone should
13434 upgrade. Bugfix on the 0.1.1 series and later.
13436 o Directory authority changes:
13437 - Change IP address and ports for gabelmoo (v3 directory authority).
13440 - Update to the December 1 2010 Maxmind GeoLite Country database.
13443 Changes in version 0.2.1.27 - 2010-11-23
13444 Yet another OpenSSL security patch broke its compatibility with Tor:
13445 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
13446 also took this opportunity to fix several crash bugs, integrate a new
13447 directory authority, and update the bundled GeoIP database.
13450 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
13451 No longer set the tlsext_host_name extension on server SSL objects;
13452 but continue to set it on client SSL objects. Our goal in setting
13453 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
13454 bugfix on 0.2.1.1-alpha.
13455 - Do not log messages to the controller while shrinking buffer
13456 freelists. Doing so would sometimes make the controller connection
13457 try to allocate a buffer chunk, which would mess up the internals
13458 of the freelist and cause an assertion failure. Fixes bug 1125;
13459 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
13460 - Learn our external IP address when we're a relay or bridge, even if
13461 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
13462 where we introduced bridge relays that don't need to publish to
13463 be useful. Fixes bug 2050.
13464 - Do even more to reject (and not just ignore) annotations on
13465 router descriptors received anywhere but from the cache. Previously
13466 we would ignore such annotations at first, but cache them to disk
13467 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
13468 - When you're using bridges and your network goes away and your
13469 bridges get marked as down, recover when you attempt a new socks
13470 connection (if the network is back), rather than waiting up to an
13471 hour to try fetching new descriptors for your bridges. Bugfix on
13472 0.2.0.3-alpha; fixes bug 1981.
13475 - Move to the November 2010 Maxmind GeoLite country db (rather
13476 than the June 2009 ip-to-country GeoIP db) for our statistics that
13477 count how many users relays are seeing from each country. Now we'll
13478 have more accurate data, especially for many African countries.
13480 o New directory authorities:
13481 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
13485 - Fix an assertion failure that could occur in directory caches or
13486 bridge users when using a very short voting interval on a testing
13487 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
13489 - Enforce multiplicity rules when parsing annotations. Bugfix on
13490 0.2.0.8-alpha. Found by piebeer.
13491 - Allow handshaking OR connections to take a full KeepalivePeriod
13492 seconds to handshake. Previously, we would close them after
13493 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
13494 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
13496 - When building with --enable-gcc-warnings on OpenBSD, disable
13497 warnings in system headers. This makes --enable-gcc-warnings
13498 pass on OpenBSD 4.8.
13501 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
13502 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
13503 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
13504 Servers can start sending this code when enough clients recognize
13505 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
13506 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
13507 Patch from mingw-san.
13510 - Remove the old debian/ directory from the main Tor distribution.
13511 The official Tor-for-debian git repository lives at the URL
13512 https://git.torproject.org/debian/tor.git
13513 - Stop shipping the old doc/website/ directory in the tarball. We
13514 changed the website format in late 2010, and what we shipped in
13515 0.2.1.26 really wasn't that useful anyway.
13518 Changes in version 0.2.1.26 - 2010-05-02
13519 Tor 0.2.1.26 addresses the recent connection and memory overload
13520 problems we've been seeing on relays, especially relays with their
13521 DirPort open. If your relay has been crashing, or you turned it off
13522 because it used too many resources, give this release a try.
13524 This release also fixes yet another instance of broken OpenSSL libraries
13525 that was causing some relays to drop out of the consensus.
13528 - Teach relays to defend themselves from connection overload. Relays
13529 now close idle circuits early if it looks like they were intended
13530 for directory fetches. Relays are also more aggressive about closing
13531 TLS connections that have no circuits on them. Such circuits are
13532 unlikely to be re-used, and tens of thousands of them were piling
13533 up at the fast relays, causing the relays to run out of sockets
13534 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
13535 their directory fetches over TLS).
13536 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
13537 that claim to be earlier than 0.9.8m, but which have in reality
13538 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
13539 behavior. Possible fix for some cases of bug 1346.
13540 - Directory mirrors were fetching relay descriptors only from v2
13541 directory authorities, rather than v3 authorities like they should.
13542 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
13543 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
13546 - Finally get rid of the deprecated and now harmful notion of "clique
13547 mode", where directory authorities maintain TLS connections to
13551 - In the util/threads test, no longer free the test_mutex before all
13552 worker threads have finished. Bugfix on 0.2.1.6-alpha.
13553 - The master thread could starve the worker threads quite badly on
13554 certain systems, causing them to run only partially in the allowed
13555 window. This resulted in test failures. Now the master thread sleeps
13556 occasionally for a few microseconds while the two worker-threads
13557 compete for the mutex. Bugfix on 0.2.0.1-alpha.
13560 Changes in version 0.2.1.25 - 2010-03-16
13561 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
13562 prevent relays from guessing their IP address correctly. It also fixes
13563 several minor potential security bugs.
13566 - Fix a regression from our patch for bug 1244 that caused relays
13567 to guess their IP address incorrectly if they didn't set Address
13568 in their torrc and/or their address fails to resolve. Bugfix on
13569 0.2.1.23; fixes bug 1269.
13570 - When freeing a session key, zero it out completely. We only zeroed
13571 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
13572 patched by ekir. Fixes bug 1254.
13575 - Fix a dereference-then-NULL-check sequence when publishing
13576 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
13578 - Fix another dereference-then-NULL-check sequence. Bugfix on
13579 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
13580 - Make sure we treat potentially not NUL-terminated strings correctly.
13581 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
13584 Changes in version 0.2.1.24 - 2010-02-21
13585 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
13589 - Work correctly out-of-the-box with even more vendor-patched versions
13590 of OpenSSL. In particular, make it so Debian and OS X don't need
13591 customized patches to run/build.
13594 Changes in version 0.2.1.23 - 2010-02-13
13595 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
13596 again on the latest OS X, and updates the location of a directory
13599 o Major bugfixes (performance):
13600 - We were selecting our guards uniformly at random, and then weighting
13601 which of our guards we'd use uniformly at random. This imbalance
13602 meant that Tor clients were severely limited on throughput (and
13603 probably latency too) by the first hop in their circuit. Now we
13604 select guards weighted by currently advertised bandwidth. We also
13605 automatically discard guards picked using the old algorithm. Fixes
13606 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
13609 - Make Tor work again on the latest OS X: when deciding whether to
13610 use strange flags to turn TLS renegotiation on, detect the OpenSSL
13611 version at run-time, not compile time. We need to do this because
13612 Apple doesn't update its dev-tools headers when it updates its
13613 libraries in a security patch.
13614 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
13615 that could happen on 32-bit platforms with 64-bit time_t. Also fix
13616 a memory leak when requesting a hidden service descriptor we've
13617 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
13621 - Refactor resolve_my_address() to not use gethostbyname() anymore.
13622 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
13625 - Avoid a mad rush at the beginning of each month when each client
13626 rotates half of its guards. Instead we spread the rotation out
13627 throughout the month, but we still avoid leaving a precise timestamp
13628 in the state file about when we first picked the guard. Improves
13629 over the behavior introduced in 0.1.2.17.
13632 Changes in version 0.2.1.22 - 2010-01-19
13633 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
13634 authorities -- it would tell you its whole history of bridge descriptors
13635 if you make the right directory request. This stable update also
13636 rotates two of the seven v3 directory authority keys and locations.
13638 o Directory authority changes:
13639 - Rotate keys (both v3 identity and relay identity) for moria1
13643 - Stop bridge directory authorities from answering dbg-stability.txt
13644 directory queries, which would let people fetch a list of all
13645 bridge identities they track. Bugfix on 0.2.1.6-alpha.
13648 Changes in version 0.2.1.21 - 2009-12-21
13649 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
13650 library. If you use Tor on Linux / Unix and you're getting SSL
13651 renegotiation errors, upgrading should help. We also recommend an
13652 upgrade if you're an exit relay.
13655 - Work around a security feature in OpenSSL 0.9.8l that prevents our
13656 handshake from working unless we explicitly tell OpenSSL that we
13657 are using SSL renegotiation safely. We are, of course, but OpenSSL
13658 0.9.8l won't work unless we say we are.
13659 - Avoid crashing if the client is trying to upload many bytes and the
13660 circuit gets torn down at the same time, or if the flip side
13661 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
13664 - Do not refuse to learn about authority certs and v2 networkstatus
13665 documents that are older than the latest consensus. This bug might
13666 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
13667 Spotted and fixed by xmux.
13668 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
13669 trigger platform-specific option misparsing case found by Coverity
13671 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
13672 trigger assert. Fixes bug 1173.
13675 Changes in version 0.2.1.20 - 2009-10-15
13676 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
13677 services at once, prepares for more performance improvements, and
13678 fixes a bunch of smaller bugs.
13680 The Windows and OS X bundles also include a more recent Vidalia,
13681 and switch from Privoxy to Polipo.
13683 The OS X installers are now drag and drop. It's best to un-install
13684 Tor/Vidalia and then install this new bundle, rather than upgrade. If
13685 you want to upgrade, you'll need to update the paths for Tor and Polipo
13686 in the Vidalia Settings window.
13689 - Send circuit or stream sendme cells when our window has decreased
13690 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
13691 by Karsten when testing the "reduce circuit window" performance
13692 patch. Bugfix on the 54th commit on Tor -- from July 2002,
13693 before the release of Tor 0.0.0. This is the new winner of the
13695 - Fix a remotely triggerable memory leak when a consensus document
13696 contains more than one signature from the same voter. Bugfix on
13698 - Avoid segfault in rare cases when finishing an introduction circuit
13699 as a client and finding out that we don't have an introduction key
13700 for it. Fixes bug 1073. Reported by Aaron Swartz.
13703 - Tor now reads the "circwindow" parameter out of the consensus,
13704 and uses that value for its circuit package window rather than the
13705 default of 1000 cells. Begins the implementation of proposal 168.
13707 o New directory authorities:
13708 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
13710 - Move moria1 and tonga to alternate IP addresses.
13713 - Fix a signed/unsigned compile warning in 0.2.1.19.
13714 - Fix possible segmentation fault on directory authorities. Bugfix on
13716 - Fix an extremely rare infinite recursion bug that could occur if
13717 we tried to log a message after shutting down the log subsystem.
13718 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
13719 - Fix an obscure bug where hidden services on 64-bit big-endian
13720 systems might mis-read the timestamp in v3 introduce cells, and
13721 refuse to connect back to the client. Discovered by "rotor".
13722 Bugfix on 0.2.1.6-alpha.
13723 - We were triggering a CLOCK_SKEW controller status event whenever
13724 we connect via the v2 connection protocol to any relay that has
13725 a wrong clock. Instead, we should only inform the controller when
13726 it's a trusted authority that claims our clock is wrong. Bugfix
13727 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
13728 - We were telling the controller about CHECKING_REACHABILITY and
13729 REACHABILITY_FAILED status events whenever we launch a testing
13730 circuit or notice that one has failed. Instead, only tell the
13731 controller when we want to inform the user of overall success or
13732 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
13734 - Don't warn when we're using a circuit that ends with a node
13735 excluded in ExcludeExitNodes, but the circuit is not used to access
13736 the outside world. This should help fix bug 1090. Bugfix on
13738 - Work around a small memory leak in some versions of OpenSSL that
13739 stopped the memory used by the hostname TLS extension from being
13743 - Add a "getinfo status/accepted-server-descriptor" controller
13744 command, which is the recommended way for controllers to learn
13745 whether our server descriptor has been successfully received by at
13746 least on directory authority. Un-recommend good-server-descriptor
13747 getinfo and status events until we have a better design for them.
13750 Changes in version 0.2.1.19 - 2009-07-28
13751 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
13755 - Make accessing hidden services on 0.2.1.x work right again.
13756 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
13757 part of patch provided by "optimist".
13760 - When a relay/bridge is writing out its identity key fingerprint to
13761 the "fingerprint" file and to its logs, write it without spaces. Now
13762 it will look like the fingerprints in our bridges documentation,
13763 and confuse fewer users.
13766 - Relays no longer publish a new server descriptor if they change
13767 their MaxAdvertisedBandwidth config option but it doesn't end up
13768 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
13769 fixes bug 1026. Patch from Sebastian.
13770 - Avoid leaking memory every time we get a create cell but we have
13771 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
13772 fixes bug 1034. Reported by BarkerJr.
13775 Changes in version 0.2.1.18 - 2009-07-24
13776 Tor 0.2.1.18 lays the foundations for performance improvements,
13777 adds status events to help users diagnose bootstrap problems, adds
13778 optional authentication/authorization for hidden services, fixes a
13779 variety of potential anonymity problems, and includes a huge pile of
13780 other features and bug fixes.
13782 o Major features (clients):
13783 - Start sending "bootstrap phase" status events to the controller,
13784 so it can keep the user informed of progress fetching directory
13785 information and establishing circuits. Also inform the controller
13786 if we think we're stuck at a particular bootstrap phase. Implements
13788 - Clients replace entry guards that were chosen more than a few months
13789 ago. This change should significantly improve client performance,
13790 especially once more people upgrade, since relays that have been
13791 a guard for a long time are currently overloaded.
13792 - Network status consensus documents and votes now contain bandwidth
13793 information for each relay. Clients use the bandwidth values
13794 in the consensus, rather than the bandwidth values in each
13795 relay descriptor. This approach opens the door to more accurate
13796 bandwidth estimates once the directory authorities start doing
13797 active measurements. Implements part of proposal 141.
13799 o Major features (relays):
13800 - Disable and refactor some debugging checks that forced a linear scan
13801 over the whole server-side DNS cache. These accounted for over 50%
13802 of CPU time on a relatively busy exit node's gprof profile. Also,
13803 disable some debugging checks that appeared in exit node profile
13804 data. Found by Jacob.
13805 - New DirPortFrontPage option that takes an html file and publishes
13806 it as "/" on the DirPort. Now relay operators can provide a
13807 disclaimer without needing to set up a separate webserver. There's
13808 a sample disclaimer in contrib/tor-exit-notice.html.
13810 o Major features (hidden services):
13811 - Make it possible to build hidden services that only certain clients
13812 are allowed to connect to. This is enforced at several points,
13813 so that unauthorized clients are unable to send INTRODUCE cells
13814 to the service, or even (depending on the type of authentication)
13815 to learn introduction points. This feature raises the bar for
13816 certain kinds of active attacks against hidden services. Design
13817 and code by Karsten Loesing. Implements proposal 121.
13818 - Relays now store and serve v2 hidden service descriptors by default,
13819 i.e., the new default value for HidServDirectoryV2 is 1. This is
13820 the last step in proposal 114, which aims to make hidden service
13821 lookups more reliable.
13823 o Major features (path selection):
13824 - ExitNodes and Exclude*Nodes config options now allow you to restrict
13825 by country code ("{US}") or IP address or address pattern
13826 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
13827 refinement to decide what config options should take priority if
13828 you ask to both use a particular node and exclude it.
13830 o Major features (misc):
13831 - When building a consensus, do not include routers that are down.
13832 This cuts down 30% to 40% on consensus size. Implements proposal
13834 - New TestingTorNetwork config option to allow adjustment of
13835 previously constant values that could slow bootstrapping. Implements
13836 proposal 135. Patch from Karsten.
13837 - Convert many internal address representations to optionally hold
13838 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
13839 elements. Make resolver code handle nameservers located at IPv6
13841 - More work on making our TLS handshake blend in: modify the list
13842 of ciphers advertised by OpenSSL in client mode to even more
13843 closely resemble a common web browser. We cheat a little so that
13844 we can advertise ciphers that the locally installed OpenSSL doesn't
13846 - Use the TLS1 hostname extension to more closely resemble browser
13849 o Security fixes (anonymity/entropy):
13850 - Never use a connection with a mismatched address to extend a
13851 circuit, unless that connection is canonical. A canonical
13852 connection is one whose address is authenticated by the router's
13853 identity key, either in a NETINFO cell or in a router descriptor.
13854 - Implement most of proposal 110: The first K cells to be sent
13855 along a circuit are marked as special "early" cells; only K "early"
13856 cells will be allowed. Once this code is universal, we can block
13857 certain kinds of denial-of-service attack by requiring that EXTEND
13858 commands must be sent using an "early" cell.
13859 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13860 cross-platform entropy collection again. We used to use it, then
13861 stopped using it because of a bug that could crash systems that
13862 called RAND_poll when they had a lot of fds open. It looks like the
13863 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13864 at startup, and to call RAND_poll() when we reseed later only if
13865 we have a non-buggy OpenSSL version.
13866 - When the client is choosing entry guards, now it selects at most
13867 one guard from a given relay family. Otherwise we could end up with
13868 all of our entry points into the network run by the same operator.
13869 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13870 - Do not use or believe expired v3 authority certificates. Patch
13871 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13872 - Drop begin cells to a hidden service if they come from the middle
13873 of a circuit. Patch from lark.
13874 - When we erroneously receive two EXTEND cells for the same circuit
13875 ID on the same connection, drop the second. Patch from lark.
13876 - Authorities now vote for the Stable flag for any router whose
13877 weighted MTBF is at least 5 days, regardless of the mean MTBF.
13878 - Clients now never report any stream end reason except 'MISC'.
13879 Implements proposal 148.
13881 o Major bugfixes (crashes):
13882 - Parse dates and IPv4 addresses in a locale- and libc-independent
13883 manner, to avoid platform-dependent behavior on malformed input.
13884 - Fix a crash that occurs on exit nodes when a nameserver request
13885 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
13886 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
13888 - Do not assume that a stack-allocated character array will be
13889 64-bit aligned on platforms that demand that uint64_t access is
13890 aligned. Possible fix for bug 604.
13891 - Resolve a very rare crash bug that could occur when the user forced
13892 a nameserver reconfiguration during the middle of a nameserver
13893 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
13894 - Avoid a "0 divided by 0" calculation when calculating router uptime
13895 at directory authorities. Bugfix on 0.2.0.8-alpha.
13896 - Fix an assertion bug in parsing policy-related options; possible fix
13898 - Rate-limit too-many-sockets messages: when they happen, they happen
13899 a lot and end up filling up the disk. Resolves bug 748.
13900 - Fix a race condition that could cause crashes or memory corruption
13901 when running as a server with a controller listening for log
13903 - Avoid crashing when we have a policy specified in a DirPolicy or
13904 SocksPolicy or ReachableAddresses option with ports set on it,
13905 and we re-load the policy. May fix bug 996.
13906 - Fix an assertion failure on 64-bit platforms when we allocated
13907 memory right up to the end of a memarea, then realigned the memory
13908 one step beyond the end. Fixes a possible cause of bug 930.
13909 - Protect the count of open sockets with a mutex, so we can't
13910 corrupt it when two threads are closing or opening sockets at once.
13911 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
13913 o Major bugfixes (clients):
13914 - Discard router descriptors as we load them if they are more than
13915 five days old. Otherwise if Tor is off for a long time and then
13916 starts with cached descriptors, it will try to use the onion keys
13917 in those obsolete descriptors when building circuits. Fixes bug 887.
13918 - When we choose to abandon a new entry guard because we think our
13919 older ones might be better, close any circuits pending on that
13920 new entry guard connection. This fix should make us recover much
13921 faster when our network is down and then comes back. Bugfix on
13922 0.1.2.8-beta; found by lodger.
13923 - When Tor clients restart after 1-5 days, they discard all their
13924 cached descriptors as too old, but they still use the cached
13925 consensus document. This approach is good for robustness, but
13926 bad for performance: since they don't know any bandwidths, they
13927 end up choosing at random rather than weighting their choice by
13928 speed. Fixed by the above feature of putting bandwidths in the
13931 o Major bugfixes (relays):
13932 - Relays were falling out of the networkstatus consensus for
13933 part of a day if they changed their local config but the
13934 authorities discarded their new descriptor as "not sufficiently
13935 different". Now directory authorities accept a descriptor as changed
13936 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
13937 patch by Sebastian.
13938 - Ensure that two circuits can never exist on the same connection
13939 with the same circuit ID, even if one is marked for close. This
13940 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13941 - Directory authorities were neglecting to mark relays down in their
13942 internal histories if the relays fall off the routerlist without
13943 ever being found unreachable. So there were relays in the histories
13944 that haven't been seen for eight months, and are listed as being
13945 up for eight months. This wreaked havoc on the "median wfu" and
13946 "median mtbf" calculations, in turn making Guard and Stable flags
13947 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
13950 o Major bugfixes (hidden services):
13951 - When establishing a hidden service, introduction points that
13952 originate from cannibalized circuits were completely ignored
13953 and not included in rendezvous service descriptors. This might
13954 have been another reason for delay in making a hidden service
13955 available. Bugfix from long ago (0.0.9.x?)
13957 o Major bugfixes (memory and resource management):
13958 - Fixed some memory leaks -- some quite frequent, some almost
13959 impossible to trigger -- based on results from Coverity.
13960 - Speed up parsing and cut down on memory fragmentation by using
13961 stack-style allocations for parsing directory objects. Previously,
13962 this accounted for over 40% of allocations from within Tor's code
13963 on a typical directory cache.
13964 - Use a Bloom filter rather than a digest-based set to track which
13965 descriptors we need to keep around when we're cleaning out old
13966 router descriptors. This speeds up the computation significantly,
13967 and may reduce fragmentation.
13969 o New/changed config options:
13970 - Now NodeFamily and MyFamily config options allow spaces in
13971 identity fingerprints, so it's easier to paste them in.
13972 Suggested by Lucky Green.
13973 - Allow ports 465 and 587 in the default exit policy again. We had
13974 rejected them in 0.1.0.15, because back in 2005 they were commonly
13975 misconfigured and ended up as spam targets. We hear they are better
13976 locked down these days.
13977 - Make TrackHostExit mappings expire a while after their last use, not
13978 after their creation. Patch from Robert Hogan.
13979 - Add an ExcludeExitNodes option so users can list a set of nodes
13980 that should be be excluded from the exit node position, but
13981 allowed elsewhere. Implements proposal 151.
13982 - New --hush command-line option similar to --quiet. While --quiet
13983 disables all logging to the console on startup, --hush limits the
13984 output to messages of warning and error severity.
13985 - New configure/torrc options (--enable-geoip-stats,
13986 DirRecordUsageByCountry) to record how many IPs we've served
13987 directory info to in each country code, how many status documents
13988 total we've sent to each country code, and what share of the total
13989 directory requests we should expect to see.
13990 - Make outbound DNS packets respect the OutboundBindAddress setting.
13991 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
13992 - Allow separate log levels to be configured for different logging
13993 domains. For example, this allows one to log all notices, warnings,
13994 or errors, plus all memory management messages of level debug or
13995 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13996 - Update to the "June 3 2009" ip-to-country file.
13998 o Minor features (relays):
13999 - Raise the minimum rate limiting to be a relay from 20000 bytes
14000 to 20480 bytes (aka 20KB/s), to match our documentation. Also
14001 update directory authorities so they always assign the Fast flag
14002 to relays with 20KB/s of capacity. Now people running relays won't
14003 suddenly find themselves not seeing any use, if the network gets
14005 - If we're a relay and we change our IP address, be more verbose
14006 about the reason that made us change. Should help track down
14007 further bugs for relays on dynamic IP addresses.
14008 - Exit servers can now answer resolve requests for ip6.arpa addresses.
14009 - Implement most of Proposal 152: allow specialized servers to permit
14010 single-hop circuits, and clients to use those servers to build
14011 single-hop circuits when using a specialized controller. Patch
14012 from Josh Albrecht. Resolves feature request 768.
14013 - When relays do their initial bandwidth measurement, don't limit
14014 to just our entry guards for the test circuits. Otherwise we tend
14015 to have multiple test circuits going through a single entry guard,
14016 which makes our bandwidth test less accurate. Fixes part of bug 654;
14017 patch contributed by Josh Albrecht.
14019 o Minor features (directory authorities):
14020 - Try not to open more than one descriptor-downloading connection
14021 to an authority at once. This should reduce load on directory
14022 authorities. Fixes bug 366.
14023 - Add cross-certification to newly generated certificates, so that
14024 a signing key is enough information to look up a certificate. Start
14025 serving certificates by <identity digest, signing key digest>
14026 pairs. Implements proposal 157.
14027 - When a directory authority downloads a descriptor that it then
14028 immediately rejects, do not retry downloading it right away. Should
14029 save some bandwidth on authorities. Fix for bug 888. Patch by
14031 - Directory authorities now serve a /tor/dbg-stability.txt URL to
14032 help debug WFU and MTBF calculations.
14033 - In directory authorities' approved-routers files, allow
14034 fingerprints with or without space.
14036 o Minor features (directory mirrors):
14037 - When a download gets us zero good descriptors, do not notify
14038 Tor that new directory information has arrived.
14039 - Servers support a new URL scheme for consensus downloads that
14040 allows the client to specify which authorities are trusted.
14041 The server then only sends the consensus if the client will trust
14042 it. Otherwise a 404 error is sent back. Clients use this
14043 new scheme when the server supports it (meaning it's running
14044 0.2.1.1-alpha or later). Implements proposal 134.
14046 o Minor features (bridges):
14047 - If the bridge config line doesn't specify a port, assume 443.
14048 This makes bridge lines a bit smaller and easier for users to
14050 - If we're using bridges and our network goes away, be more willing
14051 to forgive our bridges and try again when we get an application
14054 o Minor features (hidden services):
14055 - When the client launches an introduction circuit, retry with a
14056 new circuit after 30 seconds rather than 60 seconds.
14057 - Launch a second client-side introduction circuit in parallel
14058 after a delay of 15 seconds (based on work by Christian Wilms).
14059 - Hidden services start out building five intro circuits rather
14060 than three, and when the first three finish they publish a service
14061 descriptor using those. Now we publish our service descriptor much
14062 faster after restart.
14063 - Drop the requirement to have an open dir port for storing and
14064 serving v2 hidden service descriptors.
14066 o Minor features (build and packaging):
14067 - On Linux, use the prctl call to re-enable core dumps when the User
14069 - Try to make sure that the version of Libevent we're running with
14070 is binary-compatible with the one we built with. May address bug
14072 - Add a new --enable-local-appdata configuration switch to change
14073 the default location of the datadir on win32 from APPDATA to
14074 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
14075 entirely. Patch from coderman.
14076 - Build correctly against versions of OpenSSL 0.9.8 or later that
14077 are built without support for deprecated functions.
14078 - On platforms with a maximum syslog string length, truncate syslog
14079 messages to that length ourselves, rather than relying on the
14080 system to do it for us.
14081 - Automatically detect MacOSX versions earlier than 10.4.0, and
14082 disable kqueue from inside Tor when running with these versions.
14083 We previously did this from the startup script, but that was no
14084 help to people who didn't use the startup script. Resolves bug 863.
14085 - Build correctly when configured to build outside the main source
14086 path. Patch from Michael Gold.
14087 - Disable GCC's strict alias optimization by default, to avoid the
14088 likelihood of its introducing subtle bugs whenever our code violates
14089 the letter of C99's alias rules.
14090 - Change the contrib/tor.logrotate script so it makes the new
14091 logs as "_tor:_tor" rather than the default, which is generally
14092 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
14093 - Change our header file guard macros to be less likely to conflict
14094 with system headers. Adam Langley noticed that we were conflicting
14095 with log.h on Android.
14096 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
14097 and stop using a warning that had become unfixably verbose under
14099 - Use a lockfile to make sure that two Tor processes are not
14100 simultaneously running with the same datadir.
14101 - Allow OpenSSL to use dynamic locks if it wants.
14102 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
14104 o Minor features (controllers):
14105 - When generating circuit events with verbose nicknames for
14106 controllers, try harder to look up nicknames for routers on a
14107 circuit. (Previously, we would look in the router descriptors we had
14108 for nicknames, but not in the consensus.) Partial fix for bug 941.
14109 - New controller event NEWCONSENSUS that lists the networkstatus
14110 lines for every recommended relay. Now controllers like Torflow
14111 can keep up-to-date on which relays they should be using.
14112 - New controller event "clients_seen" to report a geoip-based summary
14113 of which countries we've seen clients from recently. Now controllers
14114 like Vidalia can show bridge operators that they're actually making
14116 - Add a 'getinfo status/clients-seen' controller command, in case
14117 controllers want to hear clients_seen events but connect late.
14118 - New CONSENSUS_ARRIVED event to note when a new consensus has
14119 been fetched and validated.
14120 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
14121 controllers to prevent SIGHUP from reloading the configuration.
14123 - Return circuit purposes in response to GETINFO circuit-status.
14125 - Serve the latest v3 networkstatus consensus via the control
14126 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
14127 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
14128 controller can query our current bootstrap state in case it attaches
14129 partway through and wants to catch up.
14130 - Provide circuit purposes along with circuit events to the controller.
14132 o Minor features (tools):
14133 - Do not have tor-resolve automatically refuse all .onion addresses;
14134 if AutomapHostsOnResolve is set in your torrc, this will work fine.
14135 - Add a -p option to tor-resolve for specifying the SOCKS port: some
14136 people find host:port too confusing.
14137 - Print the SOCKS5 error message string as well as the error code
14138 when a tor-resolve request fails. Patch from Jacob.
14140 o Minor bugfixes (memory and resource management):
14141 - Clients no longer cache certificates for authorities they do not
14142 recognize. Bugfix on 0.2.0.9-alpha.
14143 - Do not use C's stdio library for writing to log files. This will
14144 improve logging performance by a minute amount, and will stop
14145 leaking fds when our disk is full. Fixes bug 861.
14146 - Stop erroneous use of O_APPEND in cases where we did not in fact
14147 want to re-seek to the end of a file before every last write().
14148 - Fix a small alignment and memory-wasting bug on buffer chunks.
14150 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
14151 to avoid unused RAM in buffer chunks and memory pools.
14152 - Reduce the default smartlist size from 32 to 16; it turns out that
14153 most smartlists hold around 8-12 elements tops.
14154 - Make dumpstats() log the fullness and size of openssl-internal
14156 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
14157 patch to their OpenSSL, turn it on to save memory on servers. This
14158 patch will (with any luck) get included in a mainline distribution
14160 - Fix a memory leak when v3 directory authorities load their keys
14161 and cert from disk. Bugfix on 0.2.0.1-alpha.
14162 - Stop using malloc_usable_size() to use more area than we had
14163 actually allocated: it was safe, but made valgrind really unhappy.
14164 - Make the assert_circuit_ok() function work correctly on circuits that
14165 have already been marked for close.
14166 - Fix uninitialized size field for memory area allocation: may improve
14167 memory performance during directory parsing.
14169 o Minor bugfixes (clients):
14170 - Stop reloading the router list from disk for no reason when we
14171 run out of reachable directory mirrors. Once upon a time reloading
14172 it would set the 'is_running' flag back to 1 for them. It hasn't
14173 done that for a long time.
14174 - When we had picked an exit node for a connection, but marked it as
14175 "optional", and it turned out we had no onion key for the exit,
14176 stop wanting that exit and try again. This situation may not
14177 be possible now, but will probably become feasible with proposal
14178 158. Spotted by rovv. Fixes another case of bug 752.
14179 - Fix a bug in address parsing that was preventing bridges or hidden
14180 service targets from being at IPv6 addresses.
14181 - Do not remove routers as too old if we do not have any consensus
14182 document. Bugfix on 0.2.0.7-alpha.
14183 - When an exit relay resolves a stream address to a local IP address,
14184 do not just keep retrying that same exit relay over and
14185 over. Instead, just close the stream. Addresses bug 872. Bugfix
14186 on 0.2.0.32. Patch from rovv.
14187 - Made Tor a little less aggressive about deleting expired
14188 certificates. Partial fix for bug 854.
14189 - Treat duplicate certificate fetches as failures, so that we do
14190 not try to re-fetch an expired certificate over and over and over.
14191 - Do not say we're fetching a certificate when we'll in fact skip it
14192 because of a pending download.
14193 - If we have correct permissions on $datadir, we complain to stdout
14194 and fail to start. But dangerous permissions on
14195 $datadir/cached-status/ would cause us to open a log and complain
14196 there. Now complain to stdout and fail to start in both cases. Fixes
14197 bug 820, reported by seeess.
14199 o Minor bugfixes (bridges):
14200 - When we made bridge authorities stop serving bridge descriptors over
14201 unencrypted links, we also broke DirPort reachability testing for
14202 bridges. So bridges with a non-zero DirPort were printing spurious
14203 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
14204 - Don't allow a bridge to publish its router descriptor to a
14205 non-bridge directory authority. Fixes part of bug 932.
14206 - When we change to or from being a bridge, reset our counts of
14207 client usage by country. Fixes bug 932.
14209 o Minor bugfixes (relays):
14210 - Log correct error messages for DNS-related network errors on
14212 - Actually return -1 in the error case for read_bandwidth_usage().
14213 Harmless bug, since we currently don't care about the return value
14214 anywhere. Bugfix on 0.2.0.9-alpha.
14215 - Provide a more useful log message if bug 977 (related to buffer
14216 freelists) ever reappears, and do not crash right away.
14217 - We were already rejecting relay begin cells with destination port
14218 of 0. Now also reject extend cells with destination port or address
14219 of 0. Suggested by lark.
14220 - When we can't transmit a DNS request due to a network error, retry
14221 it after a while, and eventually transmit a failing response to
14222 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
14223 - Solve a bug that kept hardware crypto acceleration from getting
14224 enabled when accounting was turned on. Fixes bug 907. Bugfix on
14226 - When a canonical connection appears later in our internal list
14227 than a noncanonical one for a given OR ID, always use the
14228 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
14230 - Avoid some nasty corner cases in the logic for marking connections
14231 as too old or obsolete or noncanonical for circuits. Partial
14233 - Fix another interesting corner-case of bug 891 spotted by rovv:
14234 Previously, if two hosts had different amounts of clock drift, and
14235 one of them created a new connection with just the wrong timing,
14236 the other might decide to deprecate the new connection erroneously.
14237 Bugfix on 0.1.1.13-alpha.
14238 - If one win32 nameserver fails to get added, continue adding the
14239 rest, and don't automatically fail.
14240 - Fix a bug where an unreachable relay would establish enough
14241 reachability testing circuits to do a bandwidth test -- if
14242 we already have a connection to the middle hop of the testing
14243 circuit, then it could establish the last hop by using the existing
14244 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
14245 circuits no longer use entry guards in 0.2.1.3-alpha.
14247 o Minor bugfixes (directory authorities):
14248 - Limit uploaded directory documents to be 16M rather than 500K.
14249 The directory authorities were refusing v3 consensus votes from
14250 other authorities, since the votes are now 504K. Fixes bug 959;
14251 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
14252 - Directory authorities should never send a 503 "busy" response to
14253 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
14255 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
14256 headers. Bugfix on 0.2.0.10-alpha.
14258 o Minor bugfixes (hidden services):
14259 - When we can't find an intro key for a v2 hidden service descriptor,
14260 fall back to the v0 hidden service descriptor and log a bug message.
14261 Workaround for bug 1024.
14262 - In very rare situations new hidden service descriptors were
14263 published earlier than 30 seconds after the last change to the
14264 service. (We currently think that a hidden service descriptor
14265 that's been stable for 30 seconds is worth publishing.)
14266 - If a hidden service sends us an END cell, do not consider
14267 retrying the connection; just close it. Patch from rovv.
14268 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
14269 service directories if they have no advertised dir port. Bugfix
14272 o Minor bugfixes (tools):
14273 - In the torify(1) manpage, mention that tsocks will leak your
14276 o Minor bugfixes (controllers):
14277 - If the controller claimed responsibility for a stream, but that
14278 stream never finished making its connection, it would live
14279 forever in circuit_wait state. Now we close it after SocksTimeout
14280 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
14281 - Make DNS resolved controller events into "CLOSED", not
14282 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
14284 - The control port would close the connection before flushing long
14285 replies, such as the network consensus, if a QUIT command was issued
14286 before the reply had completed. Now, the control port flushes all
14287 pending replies before closing the connection. Also fix a spurious
14288 warning when a QUIT command is issued after a malformed or rejected
14289 AUTHENTICATE command, but before the connection was closed. Patch
14290 by Marcus Griep. Fixes bugs 1015 and 1016.
14291 - Fix a bug that made stream bandwidth get misreported to the
14294 o Deprecated and removed features:
14295 - The old "tor --version --version" command, which would print out
14296 the subversion "Id" of most of the source files, is now removed. It
14297 turned out to be less useful than we'd expected, and harder to
14299 - RedirectExits has been removed. It was deprecated since
14301 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
14302 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
14303 - Cell pools are now always enabled; --disable-cell-pools is ignored.
14304 - Directory mirrors no longer fetch the v1 directory or
14305 running-routers files. They are obsolete, and nobody asks for them
14306 anymore. This is the first step to making v1 authorities obsolete.
14307 - Take out the TestVia config option, since it was a workaround for
14308 a bug that was fixed in Tor 0.1.1.21.
14309 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
14310 HiddenServiceExcludeNodes as obsolete: they never worked properly,
14311 and nobody seems to be using them. Fixes bug 754. Bugfix on
14312 0.1.0.1-rc. Patch from Christian Wilms.
14313 - Remove all backward-compatibility code for relays running
14314 versions of Tor so old that they no longer work at all on the
14317 o Code simplifications and refactoring:
14318 - Tool-assisted documentation cleanup. Nearly every function or
14319 static variable in Tor should have its own documentation now.
14320 - Rename the confusing or_is_obsolete field to the more appropriate
14321 is_bad_for_new_circs, and move it to or_connection_t where it
14323 - Move edge-only flags from connection_t to edge_connection_t: not
14324 only is this better coding, but on machines of plausible alignment,
14325 it should save 4-8 bytes per connection_t. "Every little bit helps."
14326 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
14327 for consistency; keep old option working for backward compatibility.
14328 - Simplify the code for finding connections to use for a circuit.
14329 - Revise the connection_new functions so that a more typesafe variant
14330 exists. This will work better with Coverity, and let us find any
14331 actual mistakes we're making here.
14332 - Refactor unit testing logic so that dmalloc can be used sensibly
14333 with unit tests to check for memory leaks.
14334 - Move all hidden-service related fields from connection and circuit
14335 structure to substructures: this way they won't eat so much memory.
14336 - Squeeze 2-5% out of client performance (according to oprofile) by
14337 improving the implementation of some policy-manipulation functions.
14338 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
14339 be more efficient. Formerly it was quadratic in the number of
14340 servers; now it should be linear. Fixes bug 509.
14341 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
14342 and n_conn_id_digest fields into a separate structure that's
14343 only needed when the circuit has not yet attached to an n_conn.
14344 - Optimize out calls to time(NULL) that occur for every IO operation,
14345 or for every cell. On systems like Windows where time() is a
14346 slow syscall, this fix will be slightly helpful.
14349 Changes in version 0.2.0.35 - 2009-06-24
14351 - Avoid crashing in the presence of certain malformed descriptors.
14352 Found by lark, and by automated fuzzing.
14353 - Fix an edge case where a malicious exit relay could convince a
14354 controller that the client's DNS question resolves to an internal IP
14355 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
14358 - Finally fix the bug where dynamic-IP relays disappear when their
14359 IP address changes: directory mirrors were mistakenly telling
14360 them their old address if they asked via begin_dir, so they
14361 never got an accurate answer about their new address, so they
14362 just vanished after a day. For belt-and-suspenders, relays that
14363 don't set Address in their config now avoid using begin_dir for
14364 all direct connections. Should fix bugs 827, 883, and 900.
14365 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
14366 that would occur on some exit nodes when DNS failures and timeouts
14367 occurred in certain patterns. Fix for bug 957.
14370 - When starting with a cache over a few days old, do not leak
14371 memory for the obsolete router descriptors in it. Bugfix on
14372 0.2.0.33; fixes bug 672.
14373 - Hidden service clients didn't use a cached service descriptor that
14374 was older than 15 minutes, but wouldn't fetch a new one either,
14375 because there was already one in the cache. Now, fetch a v2
14376 descriptor unless the same descriptor was added to the cache within
14377 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
14380 Changes in version 0.2.0.34 - 2009-02-08
14381 Tor 0.2.0.34 features several more security-related fixes. You should
14382 upgrade, especially if you run an exit relay (remote crash) or a
14383 directory authority (remote infinite loop), or you're on an older
14384 (pre-XP) or not-recently-patched Windows (remote exploit).
14386 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
14387 have many known flaws, and nobody should be using them. You should
14388 upgrade. If you're using a Linux or BSD and its packages are obsolete,
14389 stop using those packages and upgrade anyway.
14392 - Fix an infinite-loop bug on handling corrupt votes under certain
14393 circumstances. Bugfix on 0.2.0.8-alpha.
14394 - Fix a temporary DoS vulnerability that could be performed by
14395 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
14396 - Avoid a potential crash on exit nodes when processing malformed
14397 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
14398 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
14399 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
14402 - Fix compilation on systems where time_t is a 64-bit integer.
14403 Patch from Matthias Drochner.
14404 - Don't consider expiring already-closed client connections. Fixes
14405 bug 893. Bugfix on 0.0.2pre20.
14408 Changes in version 0.2.0.33 - 2009-01-21
14409 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
14410 useful to users. It also finally fixes a bug where a relay or client
14411 that's been off for many days would take a long time to bootstrap.
14413 This update also fixes an important security-related bug reported by
14414 Ilja van Sprundel. You should upgrade. (We'll send out more details
14415 about the bug once people have had some time to upgrade.)
14418 - Fix a heap-corruption bug that may be remotely triggerable on
14419 some platforms. Reported by Ilja van Sprundel.
14422 - When a stream at an exit relay is in state "resolving" or
14423 "connecting" and it receives an "end" relay cell, the exit relay
14424 would silently ignore the end cell and not close the stream. If
14425 the client never closes the circuit, then the exit relay never
14426 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
14427 reported by "wood".
14428 - When sending CREATED cells back for a given circuit, use a 64-bit
14429 connection ID to find the right connection, rather than an addr:port
14430 combination. Now that we can have multiple OR connections between
14431 the same ORs, it is no longer possible to use addr:port to uniquely
14432 identify a connection.
14433 - Bridge relays that had DirPort set to 0 would stop fetching
14434 descriptors shortly after startup, and then briefly resume
14435 after a new bandwidth test and/or after publishing a new bridge
14436 descriptor. Bridge users that try to bootstrap from them would
14437 get a recent networkstatus but would get descriptors from up to
14438 18 hours earlier, meaning most of the descriptors were obsolete
14439 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
14440 - Prevent bridge relays from serving their 'extrainfo' document
14441 to anybody who asks, now that extrainfo docs include potentially
14442 sensitive aggregated client geoip summaries. Bugfix on
14444 - If the cached networkstatus consensus is more than five days old,
14445 discard it rather than trying to use it. In theory it could be
14446 useful because it lists alternate directory mirrors, but in practice
14447 it just means we spend many minutes trying directory mirrors that
14448 are long gone from the network. Also discard router descriptors as
14449 we load them if they are more than five days old, since the onion
14450 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
14453 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
14454 could make gcc generate non-functional binary search code. Bugfix
14456 - Build correctly on platforms without socklen_t.
14457 - Compile without warnings on solaris.
14458 - Avoid potential crash on internal error during signature collection.
14459 Fixes bug 864. Patch from rovv.
14460 - Correct handling of possible malformed authority signing key
14461 certificates with internal signature types. Fixes bug 880.
14462 Bugfix on 0.2.0.3-alpha.
14463 - Fix a hard-to-trigger resource leak when logging credential status.
14465 - When we can't initialize DNS because the network is down, do not
14466 automatically stop Tor from starting. Instead, we retry failed
14467 dns_init() every 10 minutes, and change the exit policy to reject
14468 *:* until one succeeds. Fixes bug 691.
14469 - Use 64 bits instead of 32 bits for connection identifiers used with
14470 the controller protocol, to greatly reduce risk of identifier reuse.
14471 - When we're choosing an exit node for a circuit, and we have
14472 no pending streams, choose a good general exit rather than one that
14473 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
14474 - Fix another case of assuming, when a specific exit is requested,
14475 that we know more than the user about what hosts it allows.
14476 Fixes one case of bug 752. Patch from rovv.
14477 - Clip the MaxCircuitDirtiness config option to a minimum of 10
14478 seconds. Warn the user if lower values are given in the
14479 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
14480 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
14481 user if lower values are given in the configuration. Bugfix on
14482 0.1.1.17-rc. Patch by Sebastian.
14483 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
14484 the cache because we already had a v0 descriptor with the same ID.
14485 Bugfix on 0.2.0.18-alpha.
14486 - Fix a race condition when freeing keys shared between main thread
14487 and CPU workers that could result in a memory leak. Bugfix on
14488 0.1.0.1-rc. Fixes bug 889.
14489 - Send a valid END cell back when a client tries to connect to a
14490 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
14491 840. Patch from rovv.
14492 - Check which hops rendezvous stream cells are associated with to
14493 prevent possible guess-the-streamid injection attacks from
14494 intermediate hops. Fixes another case of bug 446. Based on patch
14496 - If a broken client asks a non-exit router to connect somewhere,
14497 do not even do the DNS lookup before rejecting the connection.
14498 Fixes another case of bug 619. Patch from rovv.
14499 - When a relay gets a create cell it can't decrypt (e.g. because it's
14500 using the wrong onion key), we were dropping it and letting the
14501 client time out. Now actually answer with a destroy cell. Fixes
14502 bug 904. Bugfix on 0.0.2pre8.
14504 o Minor bugfixes (hidden services):
14505 - Do not throw away existing introduction points on SIGHUP. Bugfix on
14506 0.0.6pre1. Patch by Karsten. Fixes bug 874.
14509 - Report the case where all signatures in a detached set are rejected
14510 differently than the case where there is an error handling the
14512 - When we realize that another process has modified our cached
14513 descriptors, print out a more useful error message rather than
14514 triggering an assertion. Fixes bug 885. Patch from Karsten.
14515 - Implement the 0x20 hack to better resist DNS poisoning: set the
14516 case on outgoing DNS requests randomly, and reject responses that do
14517 not match the case correctly. This logic can be disabled with the
14518 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
14519 of servers that do not reliably preserve case in replies. See
14520 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
14522 - Check DNS replies for more matching fields to better resist DNS
14524 - Never use OpenSSL compression: it wastes RAM and CPU trying to
14525 compress cells, which are basically all encrypted, compressed, or
14529 Changes in version 0.2.0.32 - 2008-11-20
14530 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
14531 packages (and maybe other packages) noticed by Theo de Raadt, fixes
14532 a smaller security flaw that might allow an attacker to access local
14533 services, further improves hidden service performance, and fixes a
14534 variety of other issues.
14537 - The "User" and "Group" config options did not clear the
14538 supplementary group entries for the Tor process. The "User" option
14539 is now more robust, and we now set the groups to the specified
14540 user's primary group. The "Group" option is now ignored. For more
14541 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
14542 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
14543 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
14544 - The "ClientDNSRejectInternalAddresses" config option wasn't being
14545 consistently obeyed: if an exit relay refuses a stream because its
14546 exit policy doesn't allow it, we would remember what IP address
14547 the relay said the destination address resolves to, even if it's
14548 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
14551 - Fix a DOS opportunity during the voting signature collection process
14552 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
14554 o Major bugfixes (hidden services):
14555 - When fetching v0 and v2 rendezvous service descriptors in parallel,
14556 we were failing the whole hidden service request when the v0
14557 descriptor fetch fails, even if the v2 fetch is still pending and
14558 might succeed. Similarly, if the last v2 fetch fails, we were
14559 failing the whole hidden service request even if a v0 fetch is
14560 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
14561 - When extending a circuit to a hidden service directory to upload a
14562 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
14563 requests failed, because the router descriptor has not been
14564 downloaded yet. In these cases, do not attempt to upload the
14565 rendezvous descriptor, but wait until the router descriptor is
14566 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
14567 descriptor from a hidden service directory for which the router
14568 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
14572 - Fix several infrequent memory leaks spotted by Coverity.
14573 - When testing for libevent functions, set the LDFLAGS variable
14574 correctly. Found by Riastradh.
14575 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
14576 bootstrapping with tunneled directory connections. Bugfix on
14577 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
14578 - When asked to connect to A.B.exit:80, if we don't know the IP for A
14579 and we know that server B rejects most-but-not all connections to
14580 port 80, we would previously reject the connection. Now, we assume
14581 the user knows what they were asking for. Fixes bug 752. Bugfix
14582 on 0.0.9rc5. Diagnosed by BarkerJr.
14583 - If we overrun our per-second write limits a little, count this as
14584 having used up our write allocation for the second, and choke
14585 outgoing directory writes. Previously, we had only counted this when
14586 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
14587 Bugfix on 0.2.0.x (??).
14588 - Remove the old v2 directory authority 'lefkada' from the default
14589 list. It has been gone for many months.
14590 - Stop doing unaligned memory access that generated bus errors on
14591 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
14592 - Make USR2 log-level switch take effect immediately. Bugfix on
14595 o Minor bugfixes (controller):
14596 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
14597 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
14600 Changes in version 0.2.0.31 - 2008-09-03
14601 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
14602 a big bug we're seeing where in rare cases traffic from one Tor stream
14603 gets mixed into another stream, and fixes a variety of smaller issues.
14606 - Make sure that two circuits can never exist on the same connection
14607 with the same circuit ID, even if one is marked for close. This
14608 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
14609 - Relays now reject risky extend cells: if the extend cell includes
14610 a digest of all zeroes, or asks to extend back to the relay that
14611 sent the extend cell, tear down the circuit. Ideas suggested
14613 - If not enough of our entry guards are available so we add a new
14614 one, we might use the new one even if it overlapped with the
14615 current circuit's exit relay (or its family). Anonymity bugfix
14616 pointed out by rovv.
14619 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
14620 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
14621 - Correctly detect the presence of the linux/netfilter_ipv4.h header
14622 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
14623 - Pick size of default geoip filename string correctly on windows.
14624 Fixes bug 806. Bugfix on 0.2.0.30.
14625 - Make the autoconf script accept the obsolete --with-ssl-dir
14626 option as an alias for the actually-working --with-openssl-dir
14627 option. Fix the help documentation to recommend --with-openssl-dir.
14628 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
14629 - When using the TransPort option on OpenBSD, and using the User
14630 option to change UID and drop privileges, make sure to open
14631 /dev/pf before dropping privileges. Fixes bug 782. Patch from
14632 Christopher Davis. Bugfix on 0.1.2.1-alpha.
14633 - Try to attach connections immediately upon receiving a RENDEZVOUS2
14634 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
14635 on the client side when connecting to a hidden service. Bugfix
14636 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
14637 - When closing an application-side connection because its circuit is
14638 getting torn down, generate the stream event correctly. Bugfix on
14639 0.1.2.x. Anonymous patch.
14642 Changes in version 0.2.0.30 - 2008-07-15
14643 This new stable release switches to a more efficient directory
14644 distribution design, adds features to make connections to the Tor
14645 network harder to block, allows Tor to act as a DNS proxy, adds separate
14646 rate limiting for relayed traffic to make it easier for clients to
14647 become relays, fixes a variety of potential anonymity problems, and
14648 includes the usual huge pile of other features and bug fixes.
14650 o New v3 directory design:
14651 - Tor now uses a new way to learn about and distribute information
14652 about the network: the directory authorities vote on a common
14653 network status document rather than each publishing their own
14654 opinion. Now clients and caches download only one networkstatus
14655 document to bootstrap, rather than downloading one for each
14656 authority. Clients only download router descriptors listed in
14657 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
14659 - Set up moria1, tor26, and dizum as v3 directory authorities
14660 in addition to being v2 authorities. Also add three new ones:
14661 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
14662 dannenberg (run by CCC).
14663 - Switch to multi-level keys for directory authorities: now their
14664 long-term identity key can be kept offline, and they periodically
14665 generate a new signing key. Clients fetch the "key certificates"
14666 to keep up to date on the right keys. Add a standalone tool
14667 "tor-gencert" to generate key certificates. Implements proposal 103.
14668 - Add a new V3AuthUseLegacyKey config option to make it easier for
14669 v3 authorities to change their identity keys if another bug like
14670 Debian's OpenSSL RNG flaw appears.
14671 - Authorities and caches fetch the v2 networkstatus documents
14672 less often, now that v3 is recommended.
14674 o Make Tor connections stand out less on the wire:
14675 - Use an improved TLS handshake designed by Steven Murdoch in proposal
14676 124, as revised in proposal 130. The new handshake is meant to
14677 be harder for censors to fingerprint, and it adds the ability
14678 to detect certain kinds of man-in-the-middle traffic analysis
14679 attacks. The new handshake format includes version negotiation for
14680 OR connections as described in proposal 105, which will allow us
14681 to improve Tor's link protocol more safely in the future.
14682 - Enable encrypted directory connections by default for non-relays,
14683 so censor tools that block Tor directory connections based on their
14684 plaintext patterns will no longer work. This means Tor works in
14685 certain censored countries by default again.
14686 - Stop including recognizeable strings in the commonname part of
14687 Tor's x509 certificates.
14689 o Implement bridge relays:
14690 - Bridge relays (or "bridges" for short) are Tor relays that aren't
14691 listed in the main Tor directory. Since there is no complete public
14692 list of them, even an ISP that is filtering connections to all the
14693 known Tor relays probably won't be able to block all the bridges.
14694 See doc/design-paper/blocking.pdf and proposal 125 for details.
14695 - New config option BridgeRelay that specifies you want to be a
14696 bridge relay rather than a normal relay. When BridgeRelay is set
14697 to 1, then a) you cache dir info even if your DirPort ins't on,
14698 and b) the default for PublishServerDescriptor is now "bridge"
14699 rather than "v2,v3".
14700 - New config option "UseBridges 1" for clients that want to use bridge
14701 relays instead of ordinary entry guards. Clients then specify
14702 bridge relays by adding "Bridge" lines to their config file. Users
14703 can learn about a bridge relay either manually through word of
14704 mouth, or by one of our rate-limited mechanisms for giving out
14705 bridge addresses without letting an attacker easily enumerate them
14706 all. See https://www.torproject.org/bridges for details.
14707 - Bridge relays behave like clients with respect to time intervals
14708 for downloading new v3 consensus documents -- otherwise they
14709 stand out. Bridge users now wait until the end of the interval,
14710 so their bridge relay will be sure to have a new consensus document.
14712 o Implement bridge directory authorities:
14713 - Bridge authorities are like normal directory authorities, except
14714 they don't serve a list of known bridges. Therefore users that know
14715 a bridge's fingerprint can fetch a relay descriptor for that bridge,
14716 including fetching updates e.g. if the bridge changes IP address,
14717 yet an attacker can't just fetch a list of all the bridges.
14718 - Set up Tonga as the default bridge directory authority.
14719 - Bridge authorities refuse to serve bridge descriptors or other
14720 bridge information over unencrypted connections (that is, when
14721 responding to direct DirPort requests rather than begin_dir cells.)
14722 - Bridge directory authorities do reachability testing on the
14723 bridges they know. They provide router status summaries to the
14724 controller via "getinfo ns/purpose/bridge", and also dump summaries
14725 to a file periodically, so we can keep internal stats about which
14726 bridges are functioning.
14727 - If bridge users set the UpdateBridgesFromAuthority config option,
14728 but the digest they ask for is a 404 on the bridge authority,
14729 they fall back to contacting the bridge directly.
14730 - Bridges always use begin_dir to publish their server descriptor to
14731 the bridge authority using an anonymous encrypted tunnel.
14732 - Early work on a "bridge community" design: if bridge authorities set
14733 the BridgePassword config option, they will serve a snapshot of
14734 known bridge routerstatuses from their DirPort to anybody who
14735 knows that password. Unset by default.
14736 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
14737 report sanitized aggregated summaries in their extra-info documents
14738 privately to the bridge authority, listing which countries are
14739 able to reach them. We hope this mechanism will let us learn when
14740 certain countries start trying to block bridges.
14741 - Bridge authorities write bridge descriptors to disk, so they can
14742 reload them after a reboot. They can also export the descriptors
14743 to other programs, so we can distribute them to blocked users via
14744 the BridgeDB interface, e.g. via https://bridges.torproject.org/
14745 and bridges@torproject.org.
14747 o Tor can be a DNS proxy:
14748 - The new client-side DNS proxy feature replaces the need for
14749 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
14750 for DNS requests on port 9999, use the Tor network to resolve them
14751 anonymously, and send the reply back like a regular DNS server.
14752 The code still only implements a subset of DNS.
14753 - Add a new AutomapHostsOnResolve option: when it is enabled, any
14754 resolve request for hosts matching a given pattern causes Tor to
14755 generate an internal virtual address mapping for that host. This
14756 allows DNSPort to work sensibly with hidden service users. By
14757 default, .exit and .onion addresses are remapped; the list of
14758 patterns can be reconfigured with AutomapHostsSuffixes.
14759 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14760 address. Thanks to the AutomapHostsOnResolve option, this is no
14761 longer a completely silly thing to do.
14763 o Major features (relay usability):
14764 - New config options RelayBandwidthRate and RelayBandwidthBurst:
14765 a separate set of token buckets for relayed traffic. Right now
14766 relayed traffic is defined as answers to directory requests, and
14767 OR connections that don't have any local circuits on them. See
14768 proposal 111 for details.
14769 - Create listener connections before we setuid to the configured
14770 User and Group. Now non-Windows users can choose port values
14771 under 1024, start Tor as root, and have Tor bind those ports
14772 before it changes to another UID. (Windows users could already
14774 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14775 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14776 on "vserver" accounts. Patch from coderman.
14778 o Major features (directory authorities):
14779 - Directory authorities track weighted fractional uptime and weighted
14780 mean-time-between failures for relays. WFU is suitable for deciding
14781 whether a node is "usually up", while MTBF is suitable for deciding
14782 whether a node is "likely to stay up." We need both, because
14783 "usually up" is a good requirement for guards, while "likely to
14784 stay up" is a good requirement for long-lived connections.
14785 - Directory authorities use a new formula for selecting which relays
14786 to advertise as Guards: they must be in the top 7/8 in terms of
14787 how long we have known about them, and above the median of those
14788 nodes in terms of weighted fractional uptime.
14789 - Directory authorities use a new formula for selecting which relays
14790 to advertise as Stable: when we have 4 or more days of data, use
14791 median measured MTBF rather than median declared uptime. Implements
14793 - Directory authorities accept and serve "extra info" documents for
14794 routers. Routers now publish their bandwidth-history lines in the
14795 extra-info docs rather than the main descriptor. This step saves
14796 60% (!) on compressed router descriptor downloads. Servers upload
14797 extra-info docs to any authority that accepts them; directory
14798 authorities now allow multiple router descriptors and/or extra
14799 info documents to be uploaded in a single go. Authorities, and
14800 caches that have been configured to download extra-info documents,
14801 download them as needed. Implements proposal 104.
14802 - Authorities now list relays who have the same nickname as
14803 a different named relay, but list them with a new flag:
14804 "Unnamed". Now we can make use of relays that happen to pick the
14805 same nickname as a server that registered two years ago and then
14806 disappeared. Implements proposal 122.
14807 - Store routers in a file called cached-descriptors instead of in
14808 cached-routers. Initialize cached-descriptors from cached-routers
14809 if the old format is around. The new format allows us to store
14810 annotations along with descriptors, to record the time we received
14811 each descriptor, its source, and its purpose: currently one of
14812 general, controller, or bridge.
14814 o Major features (other):
14815 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14816 Tor can warn and/or refuse connections to ports commonly used with
14817 vulnerable-plaintext protocols. Currently we warn on ports 23,
14818 109, 110, and 143, but we don't reject any. Based on proposal 129
14819 by Kevin Bauer and Damon McCoy.
14820 - Integrate Karsten Loesing's Google Summer of Code project to publish
14821 hidden service descriptors on a set of redundant relays that are a
14822 function of the hidden service address. Now we don't have to rely
14823 on three central hidden service authorities for publishing and
14824 fetching every hidden service descriptor. Implements proposal 114.
14825 - Allow tunnelled directory connections to ask for an encrypted
14826 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14827 connection independently. Now we can make anonymized begin_dir
14828 connections for (e.g.) more secure hidden service posting and
14831 o Major bugfixes (crashes and assert failures):
14832 - Stop imposing an arbitrary maximum on the number of file descriptors
14833 used for busy servers. Bug reported by Olaf Selke; patch from
14835 - Avoid possible failures when generating a directory with routers
14836 with over-long versions strings, or too many flags set.
14837 - Fix a rare assert error when we're closing one of our threads:
14838 use a mutex to protect the list of logs, so we never write to the
14839 list as it's being freed. Fixes the very rare bug 575, which is
14840 kind of the revenge of bug 222.
14841 - Avoid segfault in the case where a badly behaved v2 versioning
14842 directory sends a signed networkstatus with missing client-versions.
14843 - When we hit an EOF on a log (probably because we're shutting down),
14844 don't try to remove the log from the list: just mark it as
14845 unusable. (Bulletproofs against bug 222.)
14847 o Major bugfixes (code security fixes):
14848 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14850 - Rewrite directory tokenization code to never run off the end of
14851 a string. Fixes bug 455. Patch from croup.
14852 - Be more paranoid about overwriting sensitive memory on free(),
14853 as a defensive programming tactic to ensure forward secrecy.
14855 o Major bugfixes (anonymity fixes):
14856 - Reject requests for reverse-dns lookup of names that are in
14857 a private address space. Patch from lodger.
14858 - Never report that we've used more bandwidth than we're willing to
14859 relay: it leaks how much non-relay traffic we're using. Resolves
14861 - As a client, do not believe any server that tells us that an
14862 address maps to an internal address space.
14863 - Warn about unsafe ControlPort configurations.
14864 - Directory authorities now call routers Fast if their bandwidth is
14865 at least 100KB/s, and consider their bandwidth adequate to be a
14866 Guard if it is at least 250KB/s, no matter the medians. This fix
14867 complements proposal 107.
14868 - Directory authorities now never mark more than 2 servers per IP as
14869 Valid and Running (or 5 on addresses shared by authorities).
14870 Implements proposal 109, by Kevin Bauer and Damon McCoy.
14871 - If we're a relay, avoid picking ourselves as an introduction point,
14872 a rendezvous point, or as the final hop for internal circuits. Bug
14873 reported by taranis and lodger.
14874 - Exit relays that are used as a client can now reach themselves
14875 using the .exit notation, rather than just launching an infinite
14876 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
14877 - Fix a bug where, when we were choosing the 'end stream reason' to
14878 put in our relay end cell that we send to the exit relay, Tor
14879 clients on Windows were sometimes sending the wrong 'reason'. The
14880 anonymity problem is that exit relays may be able to guess whether
14881 the client is running Windows, thus helping partition the anonymity
14882 set. Down the road we should stop sending reasons to exit relays,
14883 or otherwise prevent future versions of this bug.
14884 - Only update guard status (usable / not usable) once we have
14885 enough directory information. This was causing us to discard all our
14886 guards on startup if we hadn't been running for a few weeks. Fixes
14888 - When our directory information has been expired for a while, stop
14889 being willing to build circuits using it. Fixes bug 401.
14891 o Major bugfixes (peace of mind for relay operators)
14892 - Non-exit relays no longer answer "resolve" relay cells, so they
14893 can't be induced to do arbitrary DNS requests. (Tor clients already
14894 avoid using non-exit relays for resolve cells, but now servers
14895 enforce this too.) Fixes bug 619. Patch from lodger.
14896 - When we setconf ClientOnly to 1, close any current OR and Dir
14897 listeners. Reported by mwenge.
14899 o Major bugfixes (other):
14900 - If we only ever used Tor for hidden service lookups or posts, we
14901 would stop building circuits and start refusing connections after
14902 24 hours, since we falsely believed that Tor was dormant. Reported
14904 - Add a new __HashedControlSessionPassword option for controllers
14905 to use for one-off session password hashes that shouldn't get
14906 saved to disk by SAVECONF --- Vidalia users were accumulating a
14907 pile of HashedControlPassword lines in their torrc files, one for
14908 each time they had restarted Tor and then clicked Save. Make Tor
14909 automatically convert "HashedControlPassword" to this new option but
14910 only when it's given on the command line. Partial fix for bug 586.
14911 - Patch from "Andrew S. Lists" to catch when we contact a directory
14912 mirror at IP address X and he says we look like we're coming from
14913 IP address X. Otherwise this would screw up our address detection.
14914 - Reject uploaded descriptors and extrainfo documents if they're
14915 huge. Otherwise we'll cache them all over the network and it'll
14916 clog everything up. Suggested by Aljosha Judmayer.
14917 - When a hidden service was trying to establish an introduction point,
14918 and Tor *did* manage to reuse one of the preemptively built
14919 circuits, it didn't correctly remember which one it used,
14920 so it asked for another one soon after, until there were no
14921 more preemptive circuits, at which point it launched one from
14922 scratch. Bugfix on 0.0.9.x.
14924 o Rate limiting and load balancing improvements:
14925 - When we add data to a write buffer in response to the data on that
14926 write buffer getting low because of a flush, do not consider the
14927 newly added data as a candidate for immediate flushing, but rather
14928 make it wait until the next round of writing. Otherwise, we flush
14929 and refill recursively, and a single greedy TLS connection can
14930 eat all of our bandwidth.
14931 - When counting the number of bytes written on a TLS connection,
14932 look at the BIO actually used for writing to the network, not
14933 at the BIO used (sometimes) to buffer data for the network.
14934 Looking at different BIOs could result in write counts on the
14935 order of ULONG_MAX. Fixes bug 614.
14936 - If we change our MaxAdvertisedBandwidth and then reload torrc,
14937 Tor won't realize it should publish a new relay descriptor. Fixes
14938 bug 688, reported by mfr.
14939 - Avoid using too little bandwidth when our clock skips a few seconds.
14940 - Choose which bridge to use proportional to its advertised bandwidth,
14941 rather than uniformly at random. This should speed up Tor for
14942 bridge users. Also do this for people who set StrictEntryNodes.
14944 o Bootstrapping faster and building circuits more intelligently:
14945 - Fix bug 660 that was preventing us from knowing that we should
14946 preemptively build circuits to handle expected directory requests.
14947 - When we're checking if we have enough dir info for each relay
14948 to begin establishing circuits, make sure that we actually have
14949 the descriptor listed in the consensus, not just any descriptor.
14950 - Correctly notify one-hop connections when a circuit build has
14951 failed. Possible fix for bug 669. Found by lodger.
14952 - Clients now hold circuitless TLS connections open for 1.5 times
14953 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14954 rebuild a new circuit over them within that timeframe. Previously,
14955 they held them open only for KeepalivePeriod (5 minutes).
14957 o Performance improvements (memory):
14958 - Add OpenBSD malloc code from "phk" as an optional malloc
14959 replacement on Linux: some glibc libraries do very poorly with
14960 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
14961 ./configure to get the replacement malloc code.
14962 - Switch our old ring buffer implementation for one more like that
14963 used by free Unix kernels. The wasted space in a buffer with 1mb
14964 of data will now be more like 8k than 1mb. The new implementation
14965 also avoids realloc();realloc(); patterns that can contribute to
14966 memory fragmentation.
14967 - Change the way that Tor buffers data that it is waiting to write.
14968 Instead of queueing data cells in an enormous ring buffer for each
14969 client->OR or OR->OR connection, we now queue cells on a separate
14970 queue for each circuit. This lets us use less slack memory, and
14971 will eventually let us be smarter about prioritizing different kinds
14973 - Reference-count and share copies of address policy entries; only 5%
14974 of them were actually distinct.
14975 - Tune parameters for cell pool allocation to minimize amount of
14977 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14978 for every single inactive connection_t. Free items from the
14979 4k/16k-buffer free lists when they haven't been used for a while.
14980 - Make memory debugging information describe more about history
14981 of cell allocation, so we can help reduce our memory use.
14982 - Be even more aggressive about releasing RAM from small
14983 empty buffers. Thanks to our free-list code, this shouldn't be too
14984 performance-intensive.
14985 - Log malloc statistics from mallinfo() on platforms where it exists.
14986 - Use memory pools to allocate cells with better speed and memory
14987 efficiency, especially on platforms where malloc() is inefficient.
14988 - Add a --with-tcmalloc option to the configure script to link
14989 against tcmalloc (if present). Does not yet search for non-system
14992 o Performance improvements (socket management):
14993 - Count the number of open sockets separately from the number of
14994 active connection_t objects. This will let us avoid underusing
14995 our allocated connection limit.
14996 - We no longer use socket pairs to link an edge connection to an
14997 anonymous directory connection or a DirPort test connection.
14998 Instead, we track the link internally and transfer the data
14999 in-process. This saves two sockets per "linked" connection (at the
15000 client and at the server), and avoids the nasty Windows socketpair()
15002 - We were leaking a file descriptor if Tor started with a zero-length
15003 cached-descriptors file. Patch by "freddy77".
15005 o Performance improvements (CPU use):
15006 - Never walk through the list of logs if we know that no log target
15007 is interested in a given message.
15008 - Call routerlist_remove_old_routers() much less often. This should
15009 speed startup, especially on directory caches.
15010 - Base64 decoding was actually showing up on our profile when parsing
15011 the initial descriptor file; switch to an in-process all-at-once
15012 implementation that's about 3.5x times faster than calling out to
15014 - Use a slightly simpler string hashing algorithm (copying Python's
15015 instead of Java's) and optimize our digest hashing algorithm to take
15016 advantage of 64-bit platforms and to remove some possibly-costly
15018 - When implementing AES counter mode, update only the portions of the
15019 counter buffer that need to change, and don't keep separate
15020 network-order and host-order counters on big-endian hosts (where
15021 they are the same).
15022 - Add an in-place version of aes_crypt() so that we can avoid doing a
15023 needless memcpy() call on each cell payload.
15024 - Use Critical Sections rather than Mutexes for synchronizing threads
15025 on win32; Mutexes are heavier-weight, and designed for synchronizing
15028 o Performance improvements (bandwidth use):
15029 - Don't try to launch new descriptor downloads quite so often when we
15030 already have enough directory information to build circuits.
15031 - Version 1 directories are no longer generated in full. Instead,
15032 authorities generate and serve "stub" v1 directories that list
15033 no servers. This will stop Tor versions 0.1.0.x and earlier from
15034 working, but (for security reasons) nobody should be running those
15036 - Avoid going directly to the directory authorities even if you're a
15037 relay, if you haven't found yourself reachable yet or if you've
15038 decided not to advertise your dirport yet. Addresses bug 556.
15039 - If we've gone 12 hours since our last bandwidth check, and we
15040 estimate we have less than 50KB bandwidth capacity but we could
15041 handle more, do another bandwidth test.
15042 - Support "If-Modified-Since" when answering HTTP requests for
15043 directories, running-routers documents, and v2 and v3 networkstatus
15044 documents. (There's no need to support it for router descriptors,
15045 since those are downloaded by descriptor digest.)
15046 - Stop fetching directory info so aggressively if your DirPort is
15047 on but your ORPort is off; stop fetching v2 dir info entirely.
15048 You can override these choices with the new FetchDirInfoEarly
15051 o Changed config option behavior (features):
15052 - Configuration files now accept C-style strings as values. This
15053 helps encode characters not allowed in the current configuration
15054 file format, such as newline or #. Addresses bug 557.
15055 - Add hidden services and DNSPorts to the list of things that make
15056 Tor accept that it has running ports. Change starting Tor with no
15057 ports from a fatal error to a warning; we might change it back if
15058 this turns out to confuse anybody. Fixes bug 579.
15059 - Make PublishServerDescriptor default to 1, so the default doesn't
15060 have to change as we invent new directory protocol versions.
15061 - Allow people to say PreferTunnelledDirConns rather than
15062 PreferTunneledDirConns, for those alternate-spellers out there.
15063 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
15064 accommodate the growing number of servers that use the default
15065 and are reaching it.
15066 - Make it possible to enable HashedControlPassword and
15067 CookieAuthentication at the same time.
15068 - When a TrackHostExits-chosen exit fails too many times in a row,
15069 stop using it. Fixes bug 437.
15071 o Changed config option behavior (bugfixes):
15072 - Do not read the configuration file when we've only been told to
15073 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
15074 based on patch from Sebastian Hahn.
15075 - Actually validate the options passed to AuthDirReject,
15076 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
15077 - Make "ClientOnly 1" config option disable directory ports too.
15078 - Don't stop fetching descriptors when FetchUselessDescriptors is
15079 set, even if we stop asking for circuits. Bug reported by tup
15081 - Servers used to decline to publish their DirPort if their
15082 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
15083 they look only at BandwidthRate and RelayBandwidthRate.
15084 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15085 minus 1 byte: the actual maximum declared bandwidth.
15086 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
15087 - Make the NodeFamilies config option work. (Reported by
15088 lodger -- it has never actually worked, even though we added it
15090 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15091 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15093 o New config options:
15094 - New configuration options AuthDirMaxServersPerAddr and
15095 AuthDirMaxServersperAuthAddr to override default maximum number
15096 of servers allowed on a single IP address. This is important for
15097 running a test network on a single host.
15098 - Three new config options (AlternateDirAuthority,
15099 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
15100 user selectively replace the default directory authorities by type,
15101 rather than the all-or-nothing replacement that DirServer offers.
15102 - New config options AuthDirBadDir and AuthDirListBadDirs for
15103 authorities to mark certain relays as "bad directories" in the
15104 networkstatus documents. Also supports the "!baddir" directive in
15105 the approved-routers file.
15106 - New config option V2AuthoritativeDirectory that all v2 directory
15107 authorities must set. This lets v3 authorities choose not to serve
15108 v2 directory information.
15110 o Minor features (other):
15111 - When we're not serving v2 directory information, there is no reason
15112 to actually keep any around. Remove the obsolete files and directory
15113 on startup if they are very old and we aren't going to serve them.
15114 - When we negotiate a v2 link-layer connection (not yet implemented),
15115 accept RELAY_EARLY cells and turn them into RELAY cells if we've
15116 negotiated a v1 connection for their next step. Initial steps for
15118 - When we have no consensus, check FallbackNetworkstatusFile (defaults
15119 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
15120 we can start out knowing some directory caches. We don't ship with
15121 a fallback consensus by default though, because it was making
15122 bootstrapping take too long while we tried many down relays.
15123 - Authorities send back an X-Descriptor-Not-New header in response to
15124 an accepted-but-discarded descriptor upload. Partially implements
15126 - If we find a cached-routers file that's been sitting around for more
15127 than 28 days unmodified, then most likely it's a leftover from
15128 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15130 - When we (as a cache) download a descriptor because it was listed
15131 in a consensus, remember when the consensus was supposed to expire,
15132 and don't expire the descriptor until then.
15133 - Optionally (if built with -DEXPORTMALLINFO) export the output
15134 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15136 - Tag every guard node in our state file with the version that
15137 we believe added it, or with our own version if we add it. This way,
15138 if a user temporarily runs an old version of Tor and then switches
15139 back to a new one, she doesn't automatically lose her guards.
15140 - When somebody requests a list of statuses or servers, and we have
15141 none of those, return a 404 rather than an empty 200.
15142 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15144 - Add an HSAuthorityRecordStats option that hidden service authorities
15145 can use to track statistics of overall hidden service usage without
15146 logging information that would be as useful to an attacker.
15147 - Allow multiple HiddenServicePort directives with the same virtual
15148 port; when they occur, the user is sent round-robin to one
15149 of the target ports chosen at random. Partially fixes bug 393 by
15150 adding limited ad-hoc round-robining.
15151 - Revamp file-writing logic so we don't need to have the entire
15152 contents of a file in memory at once before we write to disk. Tor,
15155 o Minor bugfixes (other):
15156 - Alter the code that tries to recover from unhandled write
15157 errors, to not try to flush onto a socket that's given us
15159 - Directory mirrors no longer include a guess at the client's IP
15160 address if the connection appears to be coming from the same /24
15161 network; it was producing too many wrong guesses.
15162 - If we're trying to flush the last bytes on a connection (for
15163 example, when answering a directory request), reset the
15164 time-to-give-up timeout every time we manage to write something
15166 - Reject router descriptors with out-of-range bandwidthcapacity or
15167 bandwidthburst values.
15168 - If we can't expand our list of entry guards (e.g. because we're
15169 using bridges or we have StrictEntryNodes set), don't mark relays
15170 down when they fail a directory request. Otherwise we're too quick
15171 to mark all our entry points down.
15172 - Authorities no longer send back "400 you're unreachable please fix
15173 it" errors to Tor servers that aren't online all the time. We're
15174 supposed to tolerate these servers now.
15175 - Let directory authorities startup even when they can't generate
15176 a descriptor immediately, e.g. because they don't know their
15178 - Correctly enforce that elements of directory objects do not appear
15179 more often than they are allowed to appear.
15180 - Stop allowing hibernating servers to be "stable" or "fast".
15181 - On Windows, we were preventing other processes from reading
15182 cached-routers while Tor was running. (Reported by janbar)
15183 - Check return values from pthread_mutex functions.
15184 - When opening /dev/null in finish_daemonize(), do not pass the
15185 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
15186 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
15188 o Controller features:
15189 - The GETCONF command now escapes and quotes configuration values
15190 that don't otherwise fit into the torrc file.
15191 - The SETCONF command now handles quoted values correctly.
15192 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
15193 ask about source, timestamp of arrival, purpose, etc. We need
15194 something like this to help Vidalia not do GeoIP lookups on bridge
15196 - Allow multiple HashedControlPassword config lines, to support
15197 multiple controller passwords.
15198 - Accept LF instead of CRLF on controller, since some software has a
15199 hard time generating real Internet newlines.
15200 - Add GETINFO values for the server status events
15201 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15203 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15204 GETINFO for Torstat to use until it can switch to using extrainfos.
15205 - New config option CookieAuthFile to choose a new location for the
15206 cookie authentication file, and config option
15207 CookieAuthFileGroupReadable to make it group-readable.
15208 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15209 match requests to applications. Patch from Robert Hogan.
15210 - Add a RESOLVE command to launch hostname lookups. Original patch
15212 - Add GETINFO status/enough-dir-info to let controllers tell whether
15213 Tor has downloaded sufficient directory information. Patch from Tup.
15214 - You can now use the ControlSocket option to tell Tor to listen for
15215 controller connections on Unix domain sockets on systems that
15216 support them. Patch from Peter Palfrader.
15217 - New "GETINFO address-mappings/*" command to get address mappings
15218 with expiry information. "addr-mappings/*" is now deprecated.
15220 - Add a new config option __DisablePredictedCircuits designed for
15221 use by the controller, when we don't want Tor to build any circuits
15223 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15224 so we can exit from the middle of the circuit.
15225 - Implement "getinfo status/circuit-established".
15226 - Implement "getinfo status/version/..." so a controller can tell
15227 whether the current version is recommended, and whether any versions
15228 are good, and how many authorities agree. Patch from "shibz".
15229 - Controllers should now specify cache=no or cache=yes when using
15230 the +POSTDESCRIPTOR command.
15231 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
15232 Robert Hogan. Fixes the first part of bug 681.
15233 - When reporting clock skew, and we know that the clock is _at least
15234 as skewed_ as some value, but we don't know the actual value,
15235 report the value as a "minimum skew."
15237 o Controller bugfixes:
15238 - Generate "STATUS_SERVER" events rather than misspelled
15239 "STATUS_SEVER" events. Caught by mwenge.
15240 - Reject controller commands over 1MB in length, so rogue
15241 processes can't run us out of memory.
15242 - Change the behavior of "getinfo status/good-server-descriptor"
15243 so it doesn't return failure when any authority disappears.
15244 - Send NAMESERVER_STATUS messages for a single failed nameserver
15246 - When the DANGEROUS_VERSION controller status event told us we're
15247 running an obsolete version, it used the string "OLD" to describe
15248 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
15249 "OBSOLETE" in both cases.
15250 - Respond to INT and TERM SIGNAL commands before we execute the
15251 signal, in case the signal shuts us down. We had a patch in
15252 0.1.2.1-alpha that tried to do this by queueing the response on
15253 the connection's buffer before shutting down, but that really
15254 isn't the same thing at all. Bug located by Matt Edman.
15255 - Provide DNS expiry times in GMT, not in local time. For backward
15256 compatibility, ADDRMAP events only provide GMT expiry in an extended
15257 field. "GETINFO address-mappings" always does the right thing.
15258 - Use CRLF line endings properly in NS events.
15259 - Make 'getinfo fingerprint' return a 551 error if we're not a
15260 server, so we match what the control spec claims we do. Reported
15262 - Fix a typo in an error message when extendcircuit fails that
15263 caused us to not follow the \r\n-based delimiter protocol. Reported
15265 - When tunneling an encrypted directory connection, and its first
15266 circuit fails, do not leave it unattached and ask the controller
15267 to deal. Fixes the second part of bug 681.
15268 - Treat some 403 responses from directory servers as INFO rather than
15269 WARN-severity events.
15271 o Portability / building / compiling:
15272 - When building with --enable-gcc-warnings, check for whether Apple's
15273 warning "-Wshorten-64-to-32" is available.
15274 - Support compilation to target iPhone; patch from cjacker huang.
15275 To build for iPhone, pass the --enable-iphone option to configure.
15276 - Port Tor to build and run correctly on Windows CE systems, using
15277 the wcecompat library. Contributed by Valerio Lupi.
15278 - Detect non-ASCII platforms (if any still exist) and refuse to
15279 build there: some of our code assumes that 'A' is 65 and so on.
15280 - Clear up some MIPSPro compiler warnings.
15281 - Make autoconf search for libevent, openssl, and zlib consistently.
15282 - Update deprecated macros in configure.in.
15283 - When warning about missing headers, tell the user to let us
15284 know if the compile succeeds anyway, so we can downgrade the
15286 - Include the current subversion revision as part of the version
15287 string: either fetch it directly if we're in an SVN checkout, do
15288 some magic to guess it if we're in an SVK checkout, or use
15289 the last-detected version if we're building from a .tar.gz.
15290 Use this version consistently in log messages.
15291 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15292 - Read resolv.conf files correctly on platforms where read() returns
15293 partial results on small file reads.
15294 - Build without verbose warnings even on gcc 4.2 and 4.3.
15295 - On Windows, correctly detect errors when listing the contents of
15296 a directory. Fix from lodger.
15297 - Run 'make test' as part of 'make dist', so we stop releasing so
15298 many development snapshots that fail their unit tests.
15299 - Add support to detect Libevent versions in the 1.4.x series
15301 - Add command-line arguments to unit-test executable so that we can
15302 invoke any chosen test from the command line rather than having
15303 to run the whole test suite at once; and so that we can turn on
15304 logging for the unit tests.
15305 - Do not automatically run configure from autogen.sh. This
15306 non-standard behavior tended to annoy people who have built other
15308 - Fix a macro/CPP interaction that was confusing some compilers:
15309 some GCCs don't like #if/#endif pairs inside macro arguments.
15311 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
15312 Fixes bug 704; fix from Steven Murdoch.
15313 - Correctly detect transparent proxy support on Linux hosts that
15314 require in.h to be included before netfilter_ipv4.h. Patch
15317 o Logging improvements:
15318 - When we haven't had any application requests lately, don't bother
15319 logging that we have expired a bunch of descriptors.
15320 - When attempting to open a logfile fails, tell us why.
15321 - Only log guard node status when guard node status has changed.
15322 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
15323 make "INFO" 75% less verbose.
15324 - When SafeLogging is disabled, log addresses along with all TLS
15326 - Report TLS "zero return" case as a "clean close" and "IO error"
15327 as a "close". Stop calling closes "unexpected closes": existing
15328 Tors don't use SSL_close(), so having a connection close without
15329 the TLS shutdown handshake is hardly unexpected.
15330 - When we receive a consensus from the future, warn about skew.
15331 - Make "not enough dir info yet" warnings describe *why* Tor feels
15332 it doesn't have enough directory info yet.
15333 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
15334 consumers. (We already do this on HUP.)
15335 - Give more descriptive well-formedness errors for out-of-range
15336 hidden service descriptor/protocol versions.
15337 - Stop recommending that every server operator send mail to tor-ops.
15338 Resolves bug 597. Bugfix on 0.1.2.x.
15339 - Improve skew reporting: try to give the user a better log message
15340 about how skewed they are, and how much this matters.
15341 - New --quiet command-line option to suppress the default console log.
15342 Good in combination with --hash-password.
15343 - Don't complain that "your server has not managed to confirm that its
15344 ports are reachable" if we haven't been able to build any circuits
15346 - Detect the reason for failing to mmap a descriptor file we just
15347 wrote, and give a more useful log message. Fixes bug 533.
15348 - Always prepend "Bug: " to any log message about a bug.
15349 - When dumping memory usage, list bytes used in buffer memory
15351 - When running with dmalloc, dump more stats on hup and on exit.
15352 - Put a platform string (e.g. "Linux i686") in the startup log
15353 message, so when people paste just their logs, we know if it's
15354 OpenBSD or Windows or what.
15355 - When logging memory usage, break down memory used in buffers by
15357 - When we are reporting the DirServer line we just parsed, we were
15358 logging the second stanza of the key fingerprint, not the first.
15359 - Even though Windows is equally happy with / and \ as path separators,
15360 try to use \ consistently on Windows and / consistently on Unix: it
15361 makes the log messages nicer.
15362 - On OSX, stop warning the user that kqueue support in libevent is
15363 "experimental", since it seems to have worked fine for ages.
15365 o Contributed scripts and tools:
15366 - Update linux-tor-prio.sh script to allow QoS based on the uid of
15367 the Tor process. Patch from Marco Bonetti with tweaks from Mike
15369 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15370 Unix users an easy way to script their Tor process (e.g. by
15371 adjusting bandwidth based on the time of the day).
15372 - In the exitlist script, only consider the most recently published
15373 server descriptor for each server. Also, when the user requests
15374 a list of servers that _reject_ connections to a given address,
15375 explicitly exclude the IPs that also have servers that accept
15376 connections to that address. Resolves bug 405.
15377 - Include a new contrib/tor-exit-notice.html file that exit relay
15378 operators can put on their website to help reduce abuse queries.
15380 o Newly deprecated features:
15381 - The status/version/num-versioning and status/version/num-concurring
15382 GETINFO controller options are no longer useful in the v3 directory
15383 protocol: treat them as deprecated, and warn when they're used.
15384 - The RedirectExits config option is now deprecated.
15386 o Removed features:
15387 - Drop the old code to choke directory connections when the
15388 corresponding OR connections got full: thanks to the cell queue
15389 feature, OR conns don't get full any more.
15390 - Remove the old "dns worker" server DNS code: it hasn't been default
15391 since 0.1.2.2-alpha, and all the servers are using the new
15393 - Remove the code to generate the oldest (v1) directory format.
15394 - Remove support for the old bw_accounting file: we've been storing
15395 bandwidth accounting information in the state file since
15396 0.1.2.5-alpha. This may result in bandwidth accounting errors
15397 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15398 downgrade to 0.1.1.x or earlier.
15399 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
15400 it, it had no AES, and it hasn't seen any security patches since
15402 - Stop overloading the circuit_t.onionskin field for both "onionskin
15403 from a CREATE cell that we are waiting for a cpuworker to be
15404 assigned" and "onionskin from an EXTEND cell that we are going to
15405 send to an OR as soon as we are connected". Might help with bug 600.
15406 - Remove the tor_strpartition() function: its logic was confused,
15407 and it was only used for one thing that could be implemented far
15409 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15410 and TorControl.py, as they use the old v0 controller protocol,
15411 and are obsoleted by TorFlow anyway.
15412 - Drop support for v1 rendezvous descriptors, since we never used
15413 them anyway, and the code has probably rotted by now. Based on
15414 patch from Karsten Loesing.
15415 - Stop allowing address masks that do not correspond to bit prefixes.
15416 We have warned about these for a really long time; now it's time
15417 to reject them. (Patch from croup.)
15418 - Remove an optimization in the AES counter-mode code that assumed
15419 that the counter never exceeded 2^68. When the counter can be set
15420 arbitrarily as an IV (as it is by Karsten's new hidden services
15421 code), this assumption no longer holds.
15422 - Disable the SETROUTERPURPOSE controller command: it is now
15426 Changes in version 0.1.2.19 - 2008-01-17
15427 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
15428 exit policy a little bit more conservative so it's safer to run an
15429 exit relay on a home system, and fixes a variety of smaller issues.
15432 - Exit policies now reject connections that are addressed to a
15433 relay's public (external) IP address too, unless
15434 ExitPolicyRejectPrivate is turned off. We do this because too
15435 many relays are running nearby to services that trust them based
15436 on network address.
15439 - When the clock jumps forward a lot, do not allow the bandwidth
15440 buckets to become negative. Fixes bug 544.
15441 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
15442 on every successful resolve. Reported by Mike Perry.
15443 - Purge old entries from the "rephist" database and the hidden
15444 service descriptor database even when DirPort is zero.
15445 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
15446 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
15447 crashing or mis-answering these requests.
15448 - When we decide to send a 503 response to a request for servers, do
15449 not then also send the server descriptors: this defeats the whole
15450 purpose. Fixes bug 539.
15453 - Changing the ExitPolicyRejectPrivate setting should cause us to
15454 rebuild our server descriptor.
15455 - Fix handling of hex nicknames when answering controller requests for
15456 networkstatus by name, or when deciding whether to warn about
15457 unknown routers in a config option. (Patch from mwenge.)
15458 - Fix a couple of hard-to-trigger autoconf problems that could result
15459 in really weird results on platforms whose sys/types.h files define
15460 nonstandard integer types.
15461 - Don't try to create the datadir when running --verify-config or
15462 --hash-password. Resolves bug 540.
15463 - If we were having problems getting a particular descriptor from the
15464 directory caches, and then we learned about a new descriptor for
15465 that router, we weren't resetting our failure count. Reported
15467 - Although we fixed bug 539 (where servers would send HTTP status 503
15468 responses _and_ send a body too), there are still servers out there
15469 that haven't upgraded. Therefore, make clients parse such bodies
15470 when they receive them.
15471 - Run correctly on systems where rlim_t is larger than unsigned long.
15472 This includes some 64-bit systems.
15473 - Run correctly on platforms (like some versions of OS X 10.5) where
15474 the real limit for number of open files is OPEN_FILES, not rlim_max
15475 from getrlimit(RLIMIT_NOFILES).
15476 - Avoid a spurious free on base64 failure.
15477 - Avoid segfaults on certain complex invocations of
15478 router_get_by_hexdigest().
15479 - Fix rare bug on REDIRECTSTREAM control command when called with no
15480 port set: it could erroneously report an error when none had
15484 Changes in version 0.1.2.18 - 2007-10-28
15485 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
15486 hidden service introduction that were causing huge delays, and a big
15487 bug that was causing some servers to disappear from the network status
15488 lists for a few hours each day.
15490 o Major bugfixes (crashes):
15491 - If a connection is shut down abruptly because of something that
15492 happened inside connection_flushed_some(), do not call
15493 connection_finished_flushing(). Should fix bug 451:
15494 "connection_stop_writing: Assertion conn->write_event failed"
15495 Bugfix on 0.1.2.7-alpha.
15496 - Fix possible segfaults in functions called from
15497 rend_process_relay_cell().
15499 o Major bugfixes (hidden services):
15500 - Hidden services were choosing introduction points uniquely by
15501 hexdigest, but when constructing the hidden service descriptor
15502 they merely wrote the (potentially ambiguous) nickname.
15503 - Clients now use the v2 intro format for hidden service
15504 connections: they specify their chosen rendezvous point by identity
15505 digest rather than by (potentially ambiguous) nickname. These
15506 changes could speed up hidden service connections dramatically.
15508 o Major bugfixes (other):
15509 - Stop publishing a new server descriptor just because we get a
15510 HUP signal. This led (in a roundabout way) to some servers getting
15511 dropped from the networkstatus lists for a few hours each day.
15512 - When looking for a circuit to cannibalize, consider family as well
15513 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15514 circuit cannibalization).
15515 - When a router wasn't listed in a new networkstatus, we were leaving
15516 the flags for that router alone -- meaning it remained Named,
15517 Running, etc -- even though absence from the networkstatus means
15518 that it shouldn't be considered to exist at all anymore. Now we
15519 clear all the flags for routers that fall out of the networkstatus
15520 consensus. Fixes bug 529.
15523 - Don't try to access (or alter) the state file when running
15524 --list-fingerprint or --verify-config or --hash-password. Resolves
15526 - When generating information telling us how to extend to a given
15527 router, do not try to include the nickname if it is
15528 absent. Resolves bug 467.
15529 - Fix a user-triggerable segfault in expand_filename(). (There isn't
15530 a way to trigger this remotely.)
15531 - When sending a status event to the controller telling it that an
15532 OR address is reachable, set the port correctly. (Previously we
15533 were reporting the dir port.)
15534 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15535 command. Bugfix on 0.1.2.17.
15536 - When loading bandwidth history, do not believe any information in
15537 the future. Fixes bug 434.
15538 - When loading entry guard information, do not believe any information
15540 - When we have our clock set far in the future and generate an
15541 onion key, then re-set our clock to be correct, we should not stop
15542 the onion key from getting rotated.
15543 - On some platforms, accept() can return a broken address. Detect
15544 this more quietly, and deal accordingly. Fixes bug 483.
15545 - It's not actually an error to find a non-pending entry in the DNS
15546 cache when canceling a pending resolve. Don't log unless stuff
15547 is fishy. Resolves bug 463.
15548 - Don't reset trusted dir server list when we set a configuration
15549 option. Patch from Robert Hogan.
15552 Changes in version 0.1.2.17 - 2007-08-30
15553 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
15554 X bundles. Vidalia 0.0.14 makes authentication required for the
15555 ControlPort in the default configuration, which addresses important
15556 security risks. Everybody who uses Vidalia (or another controller)
15559 In addition, this Tor update fixes major load balancing problems with
15560 path selection, which should speed things up a lot once many people
15563 o Major bugfixes (security):
15564 - We removed support for the old (v0) control protocol. It has been
15565 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
15566 become more of a headache than it's worth.
15568 o Major bugfixes (load balancing):
15569 - When choosing nodes for non-guard positions, weight guards
15570 proportionally less, since they already have enough load. Patch
15572 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15573 will allow fast Tor servers to get more attention.
15574 - When we're upgrading from an old Tor version, forget our current
15575 guards and pick new ones according to the new weightings. These
15576 three load balancing patches could raise effective network capacity
15577 by a factor of four. Thanks to Mike Perry for measurements.
15579 o Major bugfixes (stream expiration):
15580 - Expire not-yet-successful application streams in all cases if
15581 they've been around longer than SocksTimeout. Right now there are
15582 some cases where the stream will live forever, demanding a new
15583 circuit every 15 seconds. Fixes bug 454; reported by lodger.
15585 o Minor features (controller):
15586 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15587 is valid before any authentication has been received. It tells
15588 a controller what kind of authentication is expected, and what
15589 protocol is spoken. Implements proposal 119.
15591 o Minor bugfixes (performance):
15592 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
15593 greatly speeding up loading cached-routers from disk on startup.
15594 - Disable sentinel-based debugging for buffer code: we squashed all
15595 the bugs that this was supposed to detect a long time ago, and now
15596 its only effect is to change our buffer sizes from nice powers of
15597 two (which platform mallocs tend to like) to values slightly over
15598 powers of two (which make some platform mallocs sad).
15600 o Minor bugfixes (misc):
15601 - If exit bandwidth ever exceeds one third of total bandwidth, then
15602 use the correct formula to weight exit nodes when choosing paths.
15603 Based on patch from Mike Perry.
15604 - Choose perfectly fairly among routers when choosing by bandwidth and
15605 weighting by fraction of bandwidth provided by exits. Previously, we
15606 would choose with only approximate fairness, and correct ourselves
15607 if we ran off the end of the list.
15608 - If we require CookieAuthentication but we fail to write the
15609 cookie file, we would warn but not exit, and end up in a state
15610 where no controller could authenticate. Now we exit.
15611 - If we require CookieAuthentication, stop generating a new cookie
15612 every time we change any piece of our config.
15613 - Refuse to start with certain directory authority keys, and
15614 encourage people using them to stop.
15615 - Terminate multi-line control events properly. Original patch
15617 - Fix a minor memory leak when we fail to find enough suitable
15618 servers to choose a circuit.
15619 - Stop leaking part of the descriptor when we run into a particularly
15620 unparseable piece of it.
15623 Changes in version 0.1.2.16 - 2007-08-01
15624 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
15625 remote attacker in certain situations to rewrite the user's torrc
15626 configuration file. This can completely compromise anonymity of users
15627 in most configurations, including those running the Vidalia bundles,
15628 TorK, etc. Or worse.
15630 o Major security fixes:
15631 - Close immediately after missing authentication on control port;
15632 do not allow multiple authentication attempts.
15635 Changes in version 0.1.2.15 - 2007-07-17
15636 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
15637 problems, fixes compilation on BSD, and fixes a variety of other
15638 bugs. Everybody should upgrade.
15640 o Major bugfixes (compilation):
15641 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
15643 o Major bugfixes (crashes):
15644 - Try even harder not to dereference the first character after
15645 an mmap(). Reported by lodger.
15646 - Fix a crash bug in directory authorities when we re-number the
15647 routerlist while inserting a new router.
15648 - When the cached-routers file is an even multiple of the page size,
15649 don't run off the end and crash. (Fixes bug 455; based on idea
15651 - Fix eventdns.c behavior on Solaris: It is critical to include
15652 orconfig.h _before_ sys/types.h, so that we can get the expected
15653 definition of _FILE_OFFSET_BITS.
15655 o Major bugfixes (security):
15656 - Fix a possible buffer overrun when using BSD natd support. Bug
15658 - When sending destroy cells from a circuit's origin, don't include
15659 the reason for tearing down the circuit. The spec says we didn't,
15660 and now we actually don't. Reported by lodger.
15661 - Keep streamids from different exits on a circuit separate. This
15662 bug may have allowed other routers on a given circuit to inject
15663 cells into streams. Reported by lodger; fixes bug 446.
15664 - If there's a never-before-connected-to guard node in our list,
15665 never choose any guards past it. This way we don't expand our
15666 guard list unless we need to.
15668 o Minor bugfixes (guard nodes):
15669 - Weight guard selection by bandwidth, so that low-bandwidth nodes
15670 don't get overused as guards.
15672 o Minor bugfixes (directory):
15673 - Correctly count the number of authorities that recommend each
15674 version. Previously, we were under-counting by 1.
15675 - Fix a potential crash bug when we load many server descriptors at
15676 once and some of them make others of them obsolete. Fixes bug 458.
15678 o Minor bugfixes (hidden services):
15679 - Stop tearing down the whole circuit when the user asks for a
15680 connection to a port that the hidden service didn't configure.
15683 o Minor bugfixes (misc):
15684 - On Windows, we were preventing other processes from reading
15685 cached-routers while Tor was running. Reported by janbar.
15686 - Fix a possible (but very unlikely) bug in picking routers by
15687 bandwidth. Add a log message to confirm that it is in fact
15688 unlikely. Patch from lodger.
15689 - Backport a couple of memory leak fixes.
15690 - Backport miscellaneous cosmetic bugfixes.
15693 Changes in version 0.1.2.14 - 2007-05-25
15694 Tor 0.1.2.14 changes the addresses of two directory authorities (this
15695 change especially affects those who serve or use hidden services),
15696 and fixes several other crash- and security-related bugs.
15698 o Directory authority changes:
15699 - Two directory authorities (moria1 and moria2) just moved to new
15700 IP addresses. This change will particularly affect those who serve
15701 or use hidden services.
15703 o Major bugfixes (crashes):
15704 - If a directory server runs out of space in the connection table
15705 as it's processing a begin_dir request, it will free the exit stream
15706 but leave it attached to the circuit, leading to unpredictable
15707 behavior. (Reported by seeess, fixes bug 425.)
15708 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15709 to corrupt memory under some really unlikely scenarios.
15710 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15711 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15714 o Major bugfixes (security):
15715 - When choosing an entry guard for a circuit, avoid using guards
15716 that are in the same family as the chosen exit -- not just guards
15717 that are exactly the chosen exit. (Reported by lodger.)
15719 o Major bugfixes (resource management):
15720 - If a directory authority is down, skip it when deciding where to get
15721 networkstatus objects or descriptors. Otherwise we keep asking
15722 every 10 seconds forever. Fixes bug 384.
15723 - Count it as a failure if we fetch a valid network-status but we
15724 don't want to keep it. Otherwise we'll keep fetching it and keep
15725 not wanting to keep it. Fixes part of bug 422.
15726 - If all of our dirservers have given us bad or no networkstatuses
15727 lately, then stop hammering them once per minute even when we
15728 think they're failed. Fixes another part of bug 422.
15731 - Actually set the purpose correctly for descriptors inserted with
15732 purpose=controller.
15733 - When we have k non-v2 authorities in our DirServer config,
15734 we ignored the last k authorities in the list when updating our
15736 - Correctly back-off from requesting router descriptors that we are
15737 having a hard time downloading.
15738 - Read resolv.conf files correctly on platforms where read() returns
15739 partial results on small file reads.
15740 - Don't rebuild the entire router store every time we get 32K of
15741 routers: rebuild it when the journal gets very large, or when
15742 the gaps in the store get very large.
15745 - When routers publish SVN revisions in their router descriptors,
15746 authorities now include those versions correctly in networkstatus
15748 - Warn when using a version of libevent before 1.3b to run a server on
15749 OSX or BSD: these versions interact badly with userspace threads.
15752 Changes in version 0.1.2.13 - 2007-04-24
15753 This release features some major anonymity fixes, such as safer path
15754 selection; better client performance; faster bootstrapping, better
15755 address detection, and better DNS support for servers; write limiting as
15756 well as read limiting to make servers easier to run; and a huge pile of
15757 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15759 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15760 of the Freenode IRC network, remembering his patience and vision for
15761 free speech on the Internet.
15763 o Major features, client performance:
15764 - Weight directory requests by advertised bandwidth. Now we can
15765 let servers enable write limiting but still allow most clients to
15766 succeed at their directory requests. (We still ignore weights when
15767 choosing a directory authority; I hope this is a feature.)
15768 - Stop overloading exit nodes -- avoid choosing them for entry or
15769 middle hops when the total bandwidth available from non-exit nodes
15770 is much higher than the total bandwidth available from exit nodes.
15771 - Rather than waiting a fixed amount of time between retrying
15772 application connections, we wait only 10 seconds for the first,
15773 10 seconds for the second, and 15 seconds for each retry after
15774 that. Hopefully this will improve the expected user experience.
15775 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15776 to open a stream fails; now we do in more cases. This should
15777 make clients able to find a good exit faster in some cases, since
15778 unhandleable requests will now get an error rather than timing out.
15780 o Major features, client functionality:
15781 - Implement BEGIN_DIR cells, so we can connect to a directory
15782 server via TLS to do encrypted directory requests rather than
15783 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15784 config options if you like. For now, this feature only works if
15785 you already have a descriptor for the destination dirserver.
15786 - Add support for transparent application connections: this basically
15787 bundles the functionality of trans-proxy-tor into the Tor
15788 mainline. Now hosts with compliant pf/netfilter implementations
15789 can redirect TCP connections straight to Tor without diverting
15790 through SOCKS. (Based on patch from tup.)
15791 - Add support for using natd; this allows FreeBSDs earlier than
15792 5.1.2 to have ipfw send connections through Tor without using
15793 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15795 o Major features, servers:
15796 - Setting up a dyndns name for your server is now optional: servers
15797 with no hostname or IP address will learn their IP address by
15798 asking the directory authorities. This code only kicks in when you
15799 would normally have exited with a "no address" error. Nothing's
15800 authenticated, so use with care.
15801 - Directory servers now spool server descriptors, v1 directories,
15802 and v2 networkstatus objects to buffers as needed rather than en
15803 masse. They also mmap the cached-routers files. These steps save
15805 - Stop requiring clients to have well-formed certificates, and stop
15806 checking nicknames in certificates. (Clients have certificates so
15807 that they can look like Tor servers, but in the future we might want
15808 to allow them to look like regular TLS clients instead. Nicknames
15809 in certificates serve no purpose other than making our protocol
15810 easier to recognize on the wire.) Implements proposal 106.
15812 o Improvements on DNS support:
15813 - Add "eventdns" asynchronous dns library originally based on code
15814 from Adam Langley. Now we can discard the old rickety dnsworker
15815 concept, and support a wider variety of DNS functions. Allows
15816 multithreaded builds on NetBSD and OpenBSD again.
15817 - Add server-side support for "reverse" DNS lookups (using PTR
15818 records so clients can determine the canonical hostname for a given
15819 IPv4 address). Only supported by servers using eventdns; servers
15820 now announce in their descriptors if they don't support eventdns.
15821 - Workaround for name servers (like Earthlink's) that hijack failing
15822 DNS requests and replace the no-such-server answer with a "helpful"
15823 redirect to an advertising-driven search portal. Also work around
15824 DNS hijackers who "helpfully" decline to hijack known-invalid
15825 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15826 lets you turn it off.
15827 - Servers now check for the case when common DNS requests are going to
15828 wildcarded addresses (i.e. all getting the same answer), and change
15829 their exit policy to reject *:* if it's happening.
15830 - When asked to resolve a hostname, don't use non-exit servers unless
15831 requested to do so. This allows servers with broken DNS to be
15832 useful to the network.
15833 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15834 useless IPv6 DNS resolves.
15835 - Specify and implement client-side SOCKS5 interface for reverse DNS
15836 lookups (see doc/socks-extensions.txt). Also cache them.
15837 - When we change nameservers or IP addresses, reset and re-launch
15838 our tests for DNS hijacking.
15840 o Improvements on reachability testing:
15841 - Servers send out a burst of long-range padding cells once they've
15842 established that they're reachable. Spread them over 4 circuits,
15843 so hopefully a few will be fast. This exercises bandwidth and
15844 bootstraps them into the directory more quickly.
15845 - When we find our DirPort to be reachable, publish a new descriptor
15846 so we'll tell the world (reported by pnx).
15847 - Directory authorities now only decide that routers are reachable
15848 if their identity keys are as expected.
15849 - Do DirPort reachability tests less often, since a single test
15850 chews through many circuits before giving up.
15851 - Avoid some false positives during reachability testing: don't try
15852 to test via a server that's on the same /24 network as us.
15853 - Start publishing one minute or so after we find our ORPort
15854 to be reachable. This will help reduce the number of descriptors
15855 we have for ourselves floating around, since it's quite likely
15856 other things (e.g. DirPort) will change during that minute too.
15857 - Routers no longer try to rebuild long-term connections to directory
15858 authorities, and directory authorities no longer try to rebuild
15859 long-term connections to all servers. We still don't hang up
15860 connections in these two cases though -- we need to look at it
15861 more carefully to avoid flapping, and we likely need to wait til
15862 0.1.1.x is obsolete.
15864 o Improvements on rate limiting:
15865 - Enable write limiting as well as read limiting. Now we sacrifice
15866 capacity if we're pushing out lots of directory traffic, rather
15867 than overrunning the user's intended bandwidth limits.
15868 - Include TLS overhead when counting bandwidth usage; previously, we
15869 would count only the bytes sent over TLS, but not the bytes used
15871 - Servers decline directory requests much more aggressively when
15872 they're low on bandwidth. Otherwise they end up queueing more and
15873 more directory responses, which can't be good for latency.
15874 - But never refuse directory requests from local addresses.
15875 - Be willing to read or write on local connections (e.g. controller
15876 connections) even when the global rate limiting buckets are empty.
15877 - Flush local controller connection buffers periodically as we're
15878 writing to them, so we avoid queueing 4+ megabytes of data before
15880 - Revise and clean up the torrc.sample that we ship with; add
15881 a section for BandwidthRate and BandwidthBurst.
15883 o Major features, NT services:
15884 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15885 command-line flag so that admins can override the default by saying
15886 "tor --service install --user "SomeUser"". This will not affect
15887 existing installed services. Also, warn the user that the service
15888 will look for its configuration file in the service user's
15889 %appdata% directory. (We can't do the "hardwire the user's appdata
15890 directory" trick any more, since we may not have read access to that
15892 - Support running the Tor service with a torrc not in the same
15893 directory as tor.exe and default to using the torrc located in
15894 the %appdata%\Tor\ of the user who installed the service. Patch
15896 - Add an --ignore-missing-torrc command-line option so that we can
15897 get the "use sensible defaults if the configuration file doesn't
15898 exist" behavior even when specifying a torrc location on the
15900 - When stopping an NT service, wait up to 10 sec for it to actually
15901 stop. (Patch from Matt Edman; resolves bug 295.)
15903 o Directory authority improvements:
15904 - Stop letting hibernating or obsolete servers affect uptime and
15906 - Stop listing hibernating servers in the v1 directory.
15907 - Authorities no longer recommend exits as guards if this would shift
15908 too much load to the exit nodes.
15909 - Authorities now specify server versions in networkstatus. This adds
15910 about 2% to the size of compressed networkstatus docs, and allows
15911 clients to tell which servers support BEGIN_DIR and which don't.
15912 The implementation is forward-compatible with a proposed future
15913 protocol version scheme not tied to Tor versions.
15914 - DirServer configuration lines now have an orport= option so
15915 clients can open encrypted tunnels to the authorities without
15916 having downloaded their descriptors yet. Enabled for moria1,
15917 moria2, tor26, and lefkada now in the default configuration.
15918 - Add a BadDirectory flag to network status docs so that authorities
15919 can (eventually) tell clients about caches they believe to be
15920 broken. Not used yet.
15921 - Allow authorities to list nodes as bad exits in their
15922 approved-routers file by fingerprint or by address. If most
15923 authorities set a BadExit flag for a server, clients don't think
15924 of it as a general-purpose exit. Clients only consider authorities
15925 that advertise themselves as listing bad exits.
15926 - Patch from Steve Hildrey: Generate network status correctly on
15927 non-versioning dirservers.
15928 - Have directory authorities allow larger amounts of drift in uptime
15929 without replacing the server descriptor: previously, a server that
15930 restarted every 30 minutes could have 48 "interesting" descriptors
15932 - Reserve the nickname "Unnamed" for routers that can't pick
15933 a hostname: any router can call itself Unnamed; directory
15934 authorities will never allocate Unnamed to any particular router;
15935 clients won't believe that any router is the canonical Unnamed.
15937 o Directory mirrors and clients:
15938 - Discard any v1 directory info that's over 1 month old (for
15939 directories) or over 1 week old (for running-routers lists).
15940 - Clients track responses with status 503 from dirservers. After a
15941 dirserver has given us a 503, we try not to use it until an hour has
15942 gone by, or until we have no dirservers that haven't given us a 503.
15943 - When we get a 503 from a directory, and we're not a server, we no
15944 longer count the failure against the total number of failures
15945 allowed for the object we're trying to download.
15946 - Prepare for servers to publish descriptors less often: never
15947 discard a descriptor simply for being too old until either it is
15948 recommended by no authorities, or until we get a better one for
15949 the same router. Make caches consider retaining old recommended
15950 routers for even longer.
15951 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15952 headers for content, so that we can work better in the presence of
15953 caching HTTP proxies.
15954 - Stop fetching descriptors if you're not a dir mirror and you
15955 haven't tried to establish any circuits lately. (This currently
15956 causes some dangerous behavior, because when you start up again
15957 you'll use your ancient server descriptors.)
15959 o Major fixes, crashes:
15960 - Stop crashing when the controller asks us to resetconf more than
15961 one config option at once. (Vidalia 0.0.11 does this.)
15962 - Fix a longstanding obscure crash bug that could occur when we run
15963 out of DNS worker processes, if we're not using eventdns. (Resolves
15965 - Fix an assert that could trigger if a controller quickly set then
15966 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
15967 - Avoid crash when telling controller about stream-status and a
15968 stream is detached.
15969 - Avoid sending junk to controllers or segfaulting when a controller
15970 uses EVENT_NEW_DESC with verbose nicknames.
15971 - Stop triggering asserts if the controller tries to extend hidden
15972 service circuits (reported by mwenge).
15973 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15974 and hup, stop triggering an assert based on an empty onion_key.
15975 - Mask out all signals in sub-threads; only the libevent signal
15976 handler should be processing them. This should prevent some crashes
15977 on some machines using pthreads. (Patch from coderman.)
15978 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15980 o Major fixes, anonymity/security:
15981 - Automatically avoid picking more than one node from the same
15982 /16 network when constructing a circuit. Add an
15983 "EnforceDistinctSubnets" option to let people disable it if they
15984 want to operate private test networks on a single subnet.
15985 - When generating bandwidth history, round down to the nearest
15986 1k. When storing accounting data, round up to the nearest 1k.
15987 - When we're running as a server, remember when we last rotated onion
15988 keys, so that we will rotate keys once they're a week old even if
15989 we never stay up for a week ourselves.
15990 - If a client asked for a server by name, and there's a named server
15991 in our network-status but we don't have its descriptor yet, we
15992 could return an unnamed server instead.
15993 - Reject (most) attempts to use Tor circuits with length one. (If
15994 many people start using Tor as a one-hop proxy, exit nodes become
15995 a more attractive target for compromise.)
15996 - Just because your DirPort is open doesn't mean people should be
15997 able to remotely teach you about hidden service descriptors. Now
15998 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15999 - Fix a potential race condition in the rpm installer. Found by
16001 - Do not log IPs with TLS failures for incoming TLS
16002 connections. (Fixes bug 382.)
16004 o Major fixes, other:
16005 - If our system clock jumps back in time, don't publish a negative
16006 uptime in the descriptor.
16007 - When we start during an accounting interval before it's time to wake
16008 up, remember to wake up at the correct time. (May fix bug 342.)
16009 - Previously, we would cache up to 16 old networkstatus documents
16010 indefinitely, if they came from nontrusted authorities. Now we
16011 discard them if they are more than 10 days old.
16012 - When we have a state file we cannot parse, tell the user and
16013 move it aside. Now we avoid situations where the user starts
16014 Tor in 1904, Tor writes a state file with that timestamp in it,
16015 the user fixes her clock, and Tor refuses to start.
16016 - Publish a new descriptor after we hup/reload. This is important
16017 if our config has changed such that we'll want to start advertising
16018 our DirPort now, etc.
16019 - If we are using an exit enclave and we can't connect, e.g. because
16020 its webserver is misconfigured to not listen on localhost, then
16021 back off and try connecting from somewhere else before we fail.
16023 o New config options or behaviors:
16024 - When EntryNodes are configured, rebuild the guard list to contain,
16025 in order: the EntryNodes that were guards before; the rest of the
16026 EntryNodes; the nodes that were guards before.
16027 - Do not warn when individual nodes in the configuration's EntryNodes,
16028 ExitNodes, etc are down: warn only when all possible nodes
16029 are down. (Fixes bug 348.)
16030 - Put a lower-bound on MaxAdvertisedBandwidth.
16031 - Start using the state file to store bandwidth accounting data:
16032 the bw_accounting file is now obsolete. We'll keep generating it
16033 for a while for people who are still using 0.1.2.4-alpha.
16034 - Try to batch changes to the state file so that we do as few
16035 disk writes as possible while still storing important things in
16037 - The state file and the bw_accounting file get saved less often when
16038 the AvoidDiskWrites config option is set.
16039 - Make PIDFile work on Windows.
16040 - Add internal descriptions for a bunch of configuration options:
16041 accessible via controller interface and in comments in saved
16043 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16044 NNTP by default, so this seems like a sensible addition.
16045 - Clients now reject hostnames with invalid characters. This should
16046 avoid some inadvertent info leaks. Add an option
16047 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16048 is running a private network with hosts called @, !, and #.
16049 - Check for addresses with invalid characters at the exit as well,
16050 and warn less verbosely when they fail. You can override this by
16051 setting ServerDNSAllowNonRFC953Addresses to 1.
16052 - Remove some options that have been deprecated since at least
16053 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16054 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16055 to set log options. Mark PathlenCoinWeight as obsolete.
16056 - Stop accepting certain malformed ports in configured exit policies.
16057 - When the user uses bad syntax in the Log config line, stop
16058 suggesting other bad syntax as a replacement.
16059 - Add new config option "ResolvConf" to let the server operator
16060 choose an alternate resolve.conf file when using eventdns.
16061 - If one of our entry guards is on the ExcludeNodes list, or the
16062 directory authorities don't think it's a good guard, treat it as
16063 if it were unlisted: stop using it as a guard, and throw it off
16064 the guards list if it stays that way for a long time.
16065 - Allow directory authorities to be marked separately as authorities
16066 for the v1 directory protocol, the v2 directory protocol, and
16067 as hidden service directories, to make it easier to retire old
16068 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16069 to continue being hidden service authorities too.
16070 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16071 - Make TrackExitHosts case-insensitive, and fix the behavior of
16072 ".suffix" TrackExitHosts items to avoid matching in the middle of
16074 - New DirPort behavior: if you have your dirport set, you download
16075 descriptors aggressively like a directory mirror, whether or not
16076 your ORPort is set.
16079 - Create a new file ReleaseNotes which was the old ChangeLog. The
16080 new ChangeLog file now includes the notes for all development
16082 - Add a new address-spec.txt document to describe our special-case
16083 addresses: .exit, .onion, and .noconnnect.
16084 - Fork the v1 directory protocol into its own spec document,
16085 and mark dir-spec.txt as the currently correct (v2) spec.
16087 o Packaging, porting, and contrib
16088 - "tor --verify-config" now exits with -1(255) or 0 depending on
16089 whether the config options are bad or good.
16090 - The Debian package now uses --verify-config when (re)starting,
16091 to distinguish configuration errors from other errors.
16092 - Adapt a patch from goodell to let the contrib/exitlist script
16093 take arguments rather than require direct editing.
16094 - Prevent the contrib/exitlist script from printing the same
16095 result more than once.
16096 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16097 - In the hidden service example in torrc.sample, stop recommending
16098 esoteric and discouraged hidden service options.
16099 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16100 values before failing, and always enables eventdns.
16101 - Try to detect Windows correctly when cross-compiling.
16102 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16103 Try to fix this in configure.in by checking for most functions
16104 before we check for libevent.
16105 - Update RPMs to require libevent 1.2.
16106 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16107 or later. Log when we are doing this, so we can diagnose it when
16108 it fails. (Also, recommend libevent 1.1b for kqueue and
16109 win32 methods; deprecate libevent 1.0b harder; make libevent
16110 recommendation system saner.)
16111 - Build with recent (1.3+) libevents on platforms that do not
16112 define the nonstandard types "u_int8_t" and friends.
16113 - Remove architecture from OS X builds. The official builds are
16114 now universal binaries.
16115 - Run correctly on OS X platforms with case-sensitive filesystems.
16116 - Correctly set maximum connection limit on Cygwin. (This time
16118 - Start compiling on MinGW on Windows (patches from Mike Chiussi
16120 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16121 - Finally fix the openssl warnings from newer gccs that believe that
16122 ignoring a return value is okay, but casting a return value and
16123 then ignoring it is a sign of madness.
16124 - On architectures where sizeof(int)>4, still clamp declarable
16125 bandwidth to INT32_MAX.
16127 o Minor features, controller:
16128 - Warn the user when an application uses the obsolete binary v0
16129 control protocol. We're planning to remove support for it during
16130 the next development series, so it's good to give people some
16132 - Add STREAM_BW events to report per-entry-stream bandwidth
16133 use. (Patch from Robert Hogan.)
16134 - Rate-limit SIGNEWNYM signals in response to controllers that
16135 impolitely generate them for every single stream. (Patch from
16136 mwenge; closes bug 394.)
16137 - Add a REMAP status to stream events to note that a stream's
16138 address has changed because of a cached address or a MapAddress
16140 - Make REMAP stream events have a SOURCE (cache or exit), and
16141 make them generated in every case where we get a successful
16142 connected or resolved cell.
16143 - Track reasons for OR connection failure; make these reasons
16144 available via the controller interface. (Patch from Mike Perry.)
16145 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16146 can learn when clients are sending malformed hostnames to Tor.
16147 - Specify and implement some of the controller status events.
16148 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16149 - Reimplement GETINFO so that info/names stays in sync with the
16151 - Implement "GETINFO fingerprint".
16152 - Implement "SETEVENTS GUARD" so controllers can get updates on
16153 entry guard status as it changes.
16154 - Make all connections to addresses of the form ".noconnect"
16155 immediately get closed. This lets application/controller combos
16156 successfully test whether they're talking to the same Tor by
16157 watching for STREAM events.
16158 - Add a REASON field to CIRC events; for backward compatibility, this
16159 field is sent only to controllers that have enabled the extended
16160 event format. Also, add additional reason codes to explain why
16161 a given circuit has been destroyed or truncated. (Patches from
16163 - Add a REMOTE_REASON field to extended CIRC events to tell the
16164 controller why a remote OR told us to close a circuit.
16165 - Stream events also now have REASON and REMOTE_REASON fields,
16166 working much like those for circuit events.
16167 - There's now a GETINFO ns/... field so that controllers can ask Tor
16168 about the current status of a router.
16169 - A new event type "NS" to inform a controller when our opinion of
16170 a router's status has changed.
16171 - Add a GETINFO events/names and GETINFO features/names so controllers
16172 can tell which events and features are supported.
16173 - A new CLEARDNSCACHE signal to allow controllers to clear the
16174 client-side DNS cache without expiring circuits.
16175 - Fix CIRC controller events so that controllers can learn the
16176 identity digests of non-Named servers used in circuit paths.
16177 - Let controllers ask for more useful identifiers for servers. Instead
16178 of learning identity digests for un-Named servers and nicknames
16179 for Named servers, the new identifiers include digest, nickname,
16180 and indication of Named status. Off by default; see control-spec.txt
16181 for more information.
16182 - Add a "getinfo address" controller command so it can display Tor's
16183 best guess to the user.
16184 - New controller event to alert the controller when our server
16185 descriptor has changed.
16186 - Give more meaningful errors on controller authentication failure.
16187 - Export the default exit policy via the control port, so controllers
16188 don't need to guess what it is / will be later.
16190 o Minor bugfixes, controller:
16191 - When creating a circuit via the controller, send a 'launched'
16192 event when we're done, so we follow the spec better.
16193 - Correct the control spec to match how the code actually responds
16194 to 'getinfo addr-mappings/*'. Reported by daejees.
16195 - The control spec described a GUARDS event, but the code
16196 implemented a GUARD event. Standardize on GUARD, but let people
16197 ask for GUARDS too. Reported by daejees.
16198 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16199 clear the corresponding on_circuit variable, and remember later
16200 that we don't need to send a redundant CLOSED event. (Resolves part
16202 - Report events where a resolve succeeded or where we got a socks
16203 protocol error correctly, rather than calling both of them
16205 - Change reported stream target addresses to IP consistently when
16206 we finally get the IP from an exit node.
16207 - Send log messages to the controller even if they happen to be very
16209 - Flush ERR-level controller status events just like we currently
16210 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16211 the controller from learning about current events.
16212 - Report the circuit number correctly in STREAM CLOSED events. Bug
16213 reported by Mike Perry.
16214 - Do not report bizarre values for results of accounting GETINFOs
16215 when the last second's write or read exceeds the allotted bandwidth.
16216 - Report "unrecognized key" rather than an empty string when the
16217 controller tries to fetch a networkstatus that doesn't exist.
16218 - When the controller does a "GETINFO network-status", tell it
16219 about even those routers whose descriptors are very old, and use
16220 long nicknames where appropriate.
16221 - Fix handling of verbose nicknames with ORCONN controller events:
16222 make them show up exactly when requested, rather than exactly when
16224 - Controller signals now work on non-Unix platforms that don't define
16225 SIGUSR1 and SIGUSR2 the way we expect.
16226 - Respond to SIGNAL command before we execute the signal, in case
16227 the signal shuts us down. Suggested by Karsten Loesing.
16228 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16230 o Minor features, code performance:
16231 - Major performance improvement on inserting descriptors: change
16232 algorithm from O(n^2) to O(n).
16233 - Do not rotate onion key immediately after setting it for the first
16235 - Call router_have_min_dir_info half as often. (This is showing up in
16236 some profiles, but not others.)
16237 - When using GCC, make log_debug never get called at all, and its
16238 arguments never get evaluated, when no debug logs are configured.
16239 (This is showing up in some profiles, but not others.)
16240 - Statistics dumped by -USR2 now include a breakdown of public key
16241 operations, for profiling.
16242 - Make the common memory allocation path faster on machines where
16243 malloc(0) returns a pointer.
16244 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16245 split connection_t into edge, or, dir, control, and base structs.
16246 These will save quite a bit of memory on busy servers, and they'll
16247 also help us track down bugs in the code and bugs in the spec.
16248 - Use OpenSSL's AES implementation on platforms where it's faster.
16249 This could save us as much as 10% CPU usage.
16251 o Minor features, descriptors and descriptor handling:
16252 - Avoid duplicate entries on MyFamily line in server descriptor.
16253 - When Tor receives a router descriptor that it asked for, but
16254 no longer wants (because it has received fresh networkstatuses
16255 in the meantime), do not warn the user. Cache the descriptor if
16256 we're a cache; drop it if we aren't.
16257 - Servers no longer ever list themselves in their "family" line,
16258 even if configured to do so. This makes it easier to configure
16259 family lists conveniently.
16261 o Minor fixes, confusing/misleading log messages:
16262 - Display correct results when reporting which versions are
16263 recommended, and how recommended they are. (Resolves bug 383.)
16264 - Inform the server operator when we decide not to advertise a
16265 DirPort due to AccountingMax enabled or a low BandwidthRate.
16266 - Only include function names in log messages for info/debug messages.
16267 For notice/warn/err, the content of the message should be clear on
16268 its own, and printing the function name only confuses users.
16269 - Remove even more protocol-related warnings from Tor server logs,
16270 such as bad TLS handshakes and malformed begin cells.
16271 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16272 when the IP address is mapped through MapAddress to a hostname.
16273 - Fix misleading log messages: an entry guard that is "unlisted",
16274 as well as not known to be "down" (because we've never heard
16275 of it), is not therefore "up".
16277 o Minor fixes, old/obsolete behavior:
16278 - Start assuming we can use a create_fast cell if we don't know
16279 what version a router is running.
16280 - We no longer look for identity and onion keys in "identity.key" and
16281 "onion.key" -- these were replaced by secret_id_key and
16282 secret_onion_key in 0.0.8pre1.
16283 - We no longer require unrecognized directory entries to be
16285 - Drop compatibility with obsolete Tors that permit create cells
16286 to have the wrong circ_id_type.
16287 - Remove code to special-case "-cvs" ending, since it has not
16288 actually mattered since 0.0.9.
16289 - Don't re-write the fingerprint file every restart, unless it has
16292 o Minor fixes, misc client-side behavior:
16293 - Always remove expired routers and networkstatus docs before checking
16294 whether we have enough information to build circuits. (Fixes
16296 - When computing clock skew from directory HTTP headers, consider what
16297 time it was when we finished asking for the directory, not what
16299 - Make our socks5 handling more robust to broken socks clients:
16300 throw out everything waiting on the buffer in between socks
16301 handshake phases, since they can't possibly (so the theory
16302 goes) have predicted what we plan to respond to them.
16303 - Expire socks connections if they spend too long waiting for the
16304 handshake to finish. Previously we would let them sit around for
16305 days, if the connecting application didn't close them either.
16306 - And if the socks handshake hasn't started, don't send a
16307 "DNS resolve socks failed" handshake reply; just close it.
16308 - If the user asks to use invalid exit nodes, be willing to use
16310 - Track unreachable entry guards correctly: don't conflate
16311 'unreachable by us right now' with 'listed as down by the directory
16312 authorities'. With the old code, if a guard was unreachable by us
16313 but listed as running, it would clog our guard list forever.
16314 - Behave correctly in case we ever have a network with more than
16315 2GB/s total advertised capacity.
16316 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16317 - Fix a memory leak when we ask for "all" networkstatuses and we
16318 get one we don't recognize.
16321 Changes in version 0.1.1.26 - 2006-12-14
16322 o Security bugfixes:
16323 - Stop sending the HttpProxyAuthenticator string to directory
16324 servers when directory connections are tunnelled through Tor.
16325 - Clients no longer store bandwidth history in the state file.
16326 - Do not log introduction points for hidden services if SafeLogging
16330 - Fix an assert failure when a directory authority sets
16331 AuthDirRejectUnlisted and then receives a descriptor from an
16332 unlisted router (reported by seeess).
16335 Changes in version 0.1.1.25 - 2006-11-04
16337 - When a client asks us to resolve (rather than connect to)
16338 an address, and we have a cached answer, give them the cached
16339 answer. Previously, we would give them no answer at all.
16340 - We were building exactly the wrong circuits when we predict
16341 hidden service requirements, meaning Tor would have to build all
16342 its circuits on demand.
16343 - If none of our live entry guards have a high uptime, but we
16344 require a guard with a high uptime, try adding a new guard before
16345 we give up on the requirement. This patch should make long-lived
16346 connections more stable on average.
16347 - When testing reachability of our DirPort, don't launch new
16348 tests when there's already one in progress -- unreachable
16349 servers were stacking up dozens of testing streams.
16351 o Security bugfixes:
16352 - When the user sends a NEWNYM signal, clear the client-side DNS
16353 cache too. Otherwise we continue to act on previous information.
16356 - Avoid a memory corruption bug when creating a hash table for
16358 - Avoid possibility of controller-triggered crash when misusing
16359 certain commands from a v0 controller on platforms that do not
16360 handle printf("%s",NULL) gracefully.
16361 - Avoid infinite loop on unexpected controller input.
16362 - Don't log spurious warnings when we see a circuit close reason we
16363 don't recognize; it's probably just from a newer version of Tor.
16364 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16365 Tor/Privoxy we also uninstall Vidalia.
16368 Changes in version 0.1.1.24 - 2006-09-29
16370 - Allow really slow clients to not hang up five minutes into their
16371 directory downloads (suggested by Adam J. Richter).
16372 - Fix major performance regression from 0.1.0.x: instead of checking
16373 whether we have enough directory information every time we want to
16374 do something, only check when the directory information has changed.
16375 This should improve client CPU usage by 25-50%.
16376 - Don't crash if, after a server has been running for a while,
16377 it can't resolve its hostname.
16378 - When a client asks us to resolve (not connect to) an address,
16379 and we have a cached answer, give them the cached answer.
16380 Previously, we would give them no answer at all.
16383 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16384 - Don't crash when the controller receives a third argument to an
16385 "extendcircuit" request.
16386 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16387 response; fix error code when "getinfo dir/status/" fails.
16388 - Fix configure.in to not produce broken configure files with
16389 more recent versions of autoconf. Thanks to Clint for his auto*
16391 - Fix security bug on NetBSD that could allow someone to force
16392 uninitialized RAM to be sent to a server's DNS resolver. This
16393 only affects NetBSD and other platforms that do not bounds-check
16395 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16396 methods: these are known to be buggy.
16397 - If we're a directory mirror and we ask for "all" network status
16398 documents, we would discard status documents from authorities
16399 we don't recognize.
16402 Changes in version 0.1.1.23 - 2006-07-30
16404 - Fast Tor servers, especially exit nodes, were triggering asserts
16405 due to a bug in handling the list of pending DNS resolves. Some
16406 bugs still remain here; we're hunting them.
16407 - Entry guards could crash clients by sending unexpected input.
16408 - More fixes on reachability testing: if you find yourself reachable,
16409 then don't ever make any client requests (so you stop predicting
16410 circuits), then hup or have your clock jump, then later your IP
16411 changes, you won't think circuits are working, so you won't try to
16412 test reachability, so you won't publish.
16415 - Avoid a crash if the controller does a resetconf firewallports
16416 and then a setconf fascistfirewall=1.
16417 - Avoid an integer underflow when the dir authority decides whether
16418 a router is stable: we might wrongly label it stable, and compute
16419 a slightly wrong median stability, when a descriptor is published
16421 - Fix a place where we might trigger an assert if we can't build our
16422 own server descriptor yet.
16425 Changes in version 0.1.1.22 - 2006-07-05
16427 - Fix a big bug that was causing servers to not find themselves
16428 reachable if they changed IP addresses. Since only 0.1.1.22+
16429 servers can do reachability testing correctly, now we automatically
16430 make sure to test via one of these.
16431 - Fix to allow clients and mirrors to learn directory info from
16432 descriptor downloads that get cut off partway through.
16433 - Directory authorities had a bug in deciding if a newly published
16434 descriptor was novel enough to make everybody want a copy -- a few
16435 servers seem to be publishing new descriptors many times a minute.
16437 - Fix a rare bug that was causing some servers to complain about
16438 "closing wedged cpuworkers" and skip some circuit create requests.
16439 - Make the Exit flag in directory status documents actually work.
16442 Changes in version 0.1.1.21 - 2006-06-10
16443 o Crash and assert fixes from 0.1.1.20:
16444 - Fix a rare crash on Tor servers that have enabled hibernation.
16445 - Fix a seg fault on startup for Tor networks that use only one
16446 directory authority.
16447 - Fix an assert from a race condition that occurs on Tor servers
16448 while exiting, where various threads are trying to log that they're
16449 exiting, and delete the logs, at the same time.
16450 - Make our unit tests pass again on certain obscure platforms.
16453 - Add support for building SUSE RPM packages.
16454 - Speed up initial bootstrapping for clients: if we are making our
16455 first ever connection to any entry guard, then don't mark it down
16457 - When only one Tor server in the network is labelled as a guard,
16458 and we've already picked him, we would cycle endlessly picking him
16459 again, being unhappy about it, etc. Now we specifically exclude
16460 current guards when picking a new guard.
16461 - Servers send create cells more reliably after the TLS connection
16462 is established: we were sometimes forgetting to send half of them
16463 when we had more than one pending.
16464 - If we get a create cell that asks us to extend somewhere, but the
16465 Tor server there doesn't match the expected digest, we now send
16466 a destroy cell back, rather than silently doing nothing.
16467 - Make options->RedirectExit work again.
16468 - Make cookie authentication for the controller work again.
16469 - Stop being picky about unusual characters in the arguments to
16470 mapaddress. It's none of our business.
16471 - Add a new config option "TestVia" that lets you specify preferred
16472 middle hops to use for test circuits. Perhaps this will let me
16473 debug the reachability problems better.
16475 o Log / documentation fixes:
16476 - If we're a server and some peer has a broken TLS certificate, don't
16477 log about it unless ProtocolWarnings is set, i.e., we want to hear
16478 about protocol violations by others.
16479 - Fix spelling of VirtualAddrNetwork in man page.
16480 - Add a better explanation at the top of the autogenerated torrc file
16481 about what happened to our old torrc.
16484 Changes in version 0.1.1.20 - 2006-05-23
16485 o Crash and assert fixes from 0.1.0.17:
16486 - Fix assert bug in close_logs() on exit: when we close and delete
16487 logs, remove them all from the global "logfiles" list.
16488 - Fix an assert error when we're out of space in the connection_list
16489 and we try to post a hidden service descriptor (reported by Peter
16491 - Fix a rare assert error when we've tried all intro points for
16492 a hidden service and we try fetching the service descriptor again:
16493 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
16494 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
16495 out and refuse the setconf if it would fail.
16496 - If you specify a relative torrc path and you set RunAsDaemon in
16497 your torrc, then it chdir()'s to the new directory. If you then
16498 HUP, it tries to load the new torrc location, fails, and exits.
16499 The fix: no longer allow a relative path to torrc when using -f.
16500 - Check for integer overflows in more places, when adding elements
16501 to smartlists. This could possibly prevent a buffer overflow
16502 on malicious huge inputs.
16504 o Security fixes, major:
16505 - When we're printing strings from the network, don't try to print
16506 non-printable characters. Now we're safer against shell escape
16507 sequence exploits, and also against attacks to fool users into
16508 misreading their logs.
16509 - Implement entry guards: automatically choose a handful of entry
16510 nodes and stick with them for all circuits. Only pick new guards
16511 when the ones you have are unsuitable, and if the old guards
16512 become suitable again, switch back. This will increase security
16513 dramatically against certain end-point attacks. The EntryNodes
16514 config option now provides some hints about which entry guards you
16515 want to use most; and StrictEntryNodes means to only use those.
16516 Fixes CVE-2006-0414.
16517 - Implement exit enclaves: if we know an IP address for the
16518 destination, and there's a running Tor server at that address
16519 which allows exit to the destination, then extend the circuit to
16520 that exit first. This provides end-to-end encryption and end-to-end
16521 authentication. Also, if the user wants a .exit address or enclave,
16522 use 4 hops rather than 3, and cannibalize a general circ for it
16524 - Obey our firewall options more faithfully:
16525 . If we can't get to a dirserver directly, try going via Tor.
16526 . Don't ever try to connect (as a client) to a place our
16527 firewall options forbid.
16528 . If we specify a proxy and also firewall options, obey the
16529 firewall options even when we're using the proxy: some proxies
16530 can only proxy to certain destinations.
16531 - Make clients regenerate their keys when their IP address changes.
16532 - For the OS X package's modified privoxy config file, comment
16533 out the "logfile" line so we don't log everything passed
16535 - Our TLS handshakes were generating a single public/private
16536 keypair for the TLS context, rather than making a new one for
16537 each new connection. Oops. (But we were still rotating them
16538 periodically, so it's not so bad.)
16539 - When we were cannibalizing a circuit with a particular exit
16540 node in mind, we weren't checking to see if that exit node was
16541 already present earlier in the circuit. Now we are.
16542 - Require server descriptors to list IPv4 addresses -- hostnames
16543 are no longer allowed. This also fixes potential vulnerabilities
16544 to servers providing hostnames as their address and then
16545 preferentially resolving them so they can partition users.
16546 - Our logic to decide if the OR we connected to was the right guy
16547 was brittle and maybe open to a mitm for invalid routers.
16549 o Security fixes, minor:
16550 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
16551 Ian Goldberg can prove things about our handshake protocol more
16553 - Make directory authorities generate a separate "guard" flag to
16554 mean "would make a good entry guard". Clients now honor the
16555 is_guard flag rather than looking at is_fast or is_stable.
16556 - Try to list MyFamily elements by key, not by nickname, and warn
16557 if we've not heard of a server.
16558 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16559 OpenSSL. Also, reseed our entropy every hour, not just at
16560 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
16561 - Refuse server descriptors where the fingerprint line doesn't match
16562 the included identity key. Tor doesn't care, but other apps (and
16563 humans) might actually be trusting the fingerprint line.
16564 - We used to kill the circuit when we receive a relay command we
16565 don't recognize. Now we just drop that cell.
16566 - Fix a bug found by Lasse Overlier: when we were making internal
16567 circuits (intended to be cannibalized later for rendezvous and
16568 introduction circuits), we were picking them so that they had
16569 useful exit nodes. There was no need for this, and it actually
16570 aids some statistical attacks.
16571 - Start treating internal circuits and exit circuits separately.
16572 It's important to keep them separate because internal circuits
16573 have their last hops picked like middle hops, rather than like
16574 exit hops. So exiting on them will break the user's expectations.
16575 - Fix a possible way to DoS dirservers.
16576 - When the client asked for a rendezvous port that the hidden
16577 service didn't want to provide, we were sending an IP address
16578 back along with the end cell. Fortunately, it was zero. But stop
16581 o Packaging improvements:
16582 - Implement --with-libevent-dir option to ./configure. Improve
16583 search techniques to find libevent, and use those for openssl too.
16584 - Fix a couple of bugs in OpenSSL detection. Deal better when
16585 there are multiple SSLs installed with different versions.
16586 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16587 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
16589 - Make unit tests (and other invocations that aren't the real Tor)
16590 run without launching listeners, creating subdirectories, and so on.
16591 - The OS X installer was adding a symlink for tor_resolve but
16592 the binary was called tor-resolve (reported by Thomas Hardly).
16593 - Now we can target arch and OS in rpm builds (contributed by
16594 Phobos). Also make the resulting dist-rpm filename match the
16596 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16597 if you log to syslog and want something other than LOG_DAEMON.
16598 - Fix the torify (tsocks) config file to not use Tor for localhost
16600 - Start shipping socks-extensions.txt, tor-doc-unix.html,
16601 tor-doc-server.html, and stylesheet.css in the tarball.
16602 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
16603 They are useless now.
16604 - Add Peter Palfrader's contributed check-tor script. It lets you
16605 easily check whether a given server (referenced by nickname)
16606 is reachable by you.
16607 - Add BSD-style contributed startup script "rc.subr" from Peter
16610 o Directory improvements -- new directory protocol:
16611 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
16612 - Authorities and caches publish individual descriptors (by
16613 digest, by fingerprint, by "all", and by "tell me yours").
16614 - Clients don't download or use the old directory anymore. Now they
16615 download network-statuses from the directory authorities, and
16616 fetch individual server descriptors as needed from mirrors.
16617 - Clients don't download descriptors of non-running servers.
16618 - Download descriptors by digest, not by fingerprint. Caches try to
16619 download all listed digests from authorities; clients try to
16620 download "best" digests from caches. This avoids partitioning
16621 and isolating attacks better.
16622 - Only upload a new server descriptor when options change, 18
16623 hours have passed, uptime is reset, or bandwidth changes a lot.
16624 - Directory authorities silently throw away new descriptors that
16625 haven't changed much if the timestamps are similar. We do this to
16626 tolerate older Tor servers that upload a new descriptor every 15
16627 minutes. (It seemed like a good idea at the time.)
16628 - Clients choose directory servers from the network status lists,
16629 not from their internal list of router descriptors. Now they can
16630 go to caches directly rather than needing to go to authorities
16631 to bootstrap the first set of descriptors.
16632 - When picking a random directory, prefer non-authorities if any
16634 - Add a new flag to network-status indicating whether the server
16635 can answer v2 directory requests too.
16636 - Directory mirrors now cache up to 16 unrecognized network-status
16637 docs, so new directory authorities will be cached too.
16638 - Stop parsing, storing, or using running-routers output (but
16639 mirrors still cache and serve it).
16640 - Clients consider a threshold of "versioning" directory authorities
16641 before deciding whether to warn the user that he's obsolete.
16642 - Authorities publish separate sorted lists of recommended versions
16643 for clients and for servers.
16644 - Change DirServers config line to note which dirs are v1 authorities.
16645 - Put nicknames on the DirServer line, so we can refer to them
16646 without requiring all our users to memorize their IP addresses.
16647 - Remove option when getting directory cache to see whether they
16648 support running-routers; they all do now. Replace it with one
16649 to see whether caches support v2 stuff.
16650 - Stop listing down or invalid nodes in the v1 directory. This
16651 reduces its bulk by about 1/3, and reduces load on mirrors.
16652 - Mirrors no longer cache the v1 directory as often.
16653 - If we as a directory mirror don't know of any v1 directory
16654 authorities, then don't try to cache any v1 directories.
16656 o Other directory improvements:
16657 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
16658 fifth authoritative directory servers.
16659 - Directory authorities no longer require an open connection from
16660 a server to consider him "reachable". We need this change because
16661 when we add new directory authorities, old servers won't know not
16662 to hang up on them.
16663 - Dir authorities now do their own external reachability testing
16664 of each server, and only list as running the ones they found to
16665 be reachable. We also send back warnings to the server's logs if
16666 it uploads a descriptor that we already believe is unreachable.
16667 - Spread the directory authorities' reachability testing over the
16668 entire testing interval, so we don't try to do 500 TLS's at once
16670 - Make the "stable" router flag in network-status be the median of
16671 the uptimes of running valid servers, and make clients pay
16672 attention to the network-status flags. Thus the cutoff adapts
16673 to the stability of the network as a whole, making IRC, IM, etc
16674 connections more reliable.
16675 - Make the v2 dir's "Fast" flag based on relative capacity, just
16676 like "Stable" is based on median uptime. Name everything in the
16677 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
16678 - Retry directory requests if we fail to get an answer we like
16679 from a given dirserver (we were retrying before, but only if
16680 we fail to connect).
16681 - Return a robots.txt on our dirport to discourage google indexing.
16683 o Controller protocol improvements:
16684 - Revised controller protocol (version 1) that uses ascii rather
16685 than binary: tor/doc/control-spec.txt. Add supporting libraries
16686 in python and java and c# so you can use the controller from your
16687 applications without caring how our protocol works.
16688 - Allow the DEBUG controller event to work again. Mark certain log
16689 entries as "don't tell this to controllers", so we avoid cycles.
16690 - New controller function "getinfo accounting", to ask how
16691 many bytes we've used in this time period.
16692 - Add a "resetconf" command so you can set config options like
16693 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16694 a config option in the torrc with no value, then it clears it
16695 entirely (rather than setting it to its default).
16696 - Add a "getinfo config-file" to tell us where torrc is. Also
16697 expose guard nodes, config options/names.
16698 - Add a "quit" command (when when using the controller manually).
16699 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
16700 stop using any currently-dirty circuits for new streams, so we
16701 don't link new actions to old actions. This also occurs on HUP
16702 or "signal reload".
16703 - If we would close a stream early (e.g. it asks for a .exit that
16704 we know would refuse it) but the LeaveStreamsUnattached config
16705 option is set by the controller, then don't close it.
16706 - Add a new controller event type "authdir_newdescs" that allows
16707 controllers to get all server descriptors that were uploaded to
16708 a router in its role as directory authority.
16709 - New controller option "getinfo desc/all-recent" to fetch the
16710 latest server descriptor for every router that Tor knows about.
16711 - Fix the controller's "attachstream 0" command to treat conn like
16712 it just connected, doing address remapping, handling .exit and
16713 .onion idioms, and so on. Now we're more uniform in making sure
16714 that the controller hears about new and closing connections.
16715 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
16716 the controller. Also, rotate dns and cpu workers if the controller
16717 changes options that will affect them; and initialize the dns
16718 worker cache tree whether or not we start out as a server.
16719 - Add a new circuit purpose 'controller' to let the controller ask
16720 for a circuit that Tor won't try to use. Extend the "extendcircuit"
16721 controller command to let you specify the purpose if you're starting
16722 a new circuit. Add a new "setcircuitpurpose" controller command to
16723 let you change a circuit's purpose after it's been created.
16724 - Let the controller ask for "getinfo dir/server/foo" so it can ask
16725 directly rather than connecting to the dir port. "getinfo
16726 dir/status/foo" also works, but currently only if your DirPort
16728 - Let the controller tell us about certain router descriptors
16729 that it doesn't want Tor to use in circuits. Implement
16730 "setrouterpurpose" and modify "+postdescriptor" to do this.
16731 - If the controller's *setconf commands fail, collect an error
16732 message in a string and hand it back to the controller -- don't
16733 just tell them to go read their logs.
16735 o Scalability, resource management, and performance:
16736 - Fix a major load balance bug: we were round-robin reading in 16 KB
16737 chunks, and servers with bandwidthrate of 20 KB, while downloading
16738 a 600 KB directory, would starve their other connections. Now we
16739 try to be a bit more fair.
16740 - Be more conservative about whether to advertise our DirPort.
16741 The main change is to not advertise if we're running at capacity
16742 and either a) we could hibernate ever or b) our capacity is low
16743 and we're using a default DirPort.
16744 - We weren't cannibalizing circuits correctly for
16745 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16746 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16747 build those from scratch. This should make hidden services faster.
16748 - Predict required circuits better, with an eye toward making hidden
16749 services faster on the service end.
16750 - Compress exit policies even more: look for duplicate lines and
16752 - Generate 18.0.0.0/8 address policy format in descs when we can;
16753 warn when the mask is not reducible to a bit-prefix.
16754 - There used to be two ways to specify your listening ports in a
16755 server descriptor: on the "router" line and with a separate "ports"
16756 line. Remove support for the "ports" line.
16757 - Reduce memory requirements in our structs by changing the order
16758 of fields. Replace balanced trees with hash tables. Inline
16759 bottleneck smartlist functions. Add a "Map from digest to void*"
16760 abstraction so we can do less hex encoding/decoding, and use it
16761 in router_get_by_digest(). Many other CPU and memory improvements.
16762 - Allow tor_gzip_uncompress to extract as much as possible from
16763 truncated compressed data. Try to extract as many
16764 descriptors as possible from truncated http responses (when
16765 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
16766 - Make circ->onionskin a pointer, not a static array. moria2 was using
16767 125000 circuit_t's after it had been up for a few weeks, which
16768 translates to 20+ megs of wasted space.
16769 - The private half of our EDH handshake keys are now chosen out
16770 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
16771 - Stop doing the complex voodoo overkill checking for insecure
16772 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16773 - Do round-robin writes for TLS of at most 16 kB per write. This
16774 might be more fair on loaded Tor servers.
16775 - Do not use unaligned memory access on alpha, mips, or mipsel.
16776 It *works*, but is very slow, so we treat them as if it doesn't.
16778 o Other bugfixes and improvements:
16779 - Start storing useful information to $DATADIR/state, so we can
16780 remember things across invocations of Tor. Retain unrecognized
16781 lines so we can be forward-compatible, and write a TorVersion line
16782 so we can be backward-compatible.
16783 - If ORPort is set, Address is not explicitly set, and our hostname
16784 resolves to a private IP address, try to use an interface address
16785 if it has a public address. Now Windows machines that think of
16786 themselves as localhost can guess their address.
16787 - Regenerate our local descriptor if it's dirty and we try to use
16788 it locally (e.g. if it changes during reachability detection).
16789 This was causing some Tor servers to keep publishing the same
16790 initial descriptor forever.
16791 - Tor servers with dynamic IP addresses were needing to wait 18
16792 hours before they could start doing reachability testing using
16793 the new IP address and ports. This is because they were using
16794 the internal descriptor to learn what to test, yet they were only
16795 rebuilding the descriptor once they decided they were reachable.
16796 - It turns out we couldn't bootstrap a network since we added
16797 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16798 has never gone down. Add an AssumeReachable config option to let
16799 servers and authorities bootstrap. When we're trying to build a
16800 high-uptime or high-bandwidth circuit but there aren't enough
16801 suitable servers, try being less picky rather than simply failing.
16802 - Newly bootstrapped Tor networks couldn't establish hidden service
16803 circuits until they had nodes with high uptime. Be more tolerant.
16804 - Really busy servers were keeping enough circuits open on stable
16805 connections that they were wrapping around the circuit_id
16806 space. (It's only two bytes.) This exposed a bug where we would
16807 feel free to reuse a circuit_id even if it still exists but has
16808 been marked for close. Try to fix this bug. Some bug remains.
16809 - When we fail to bind or listen on an incoming or outgoing
16810 socket, we now close it before refusing, rather than just
16811 leaking it. (Thanks to Peter Palfrader for finding.)
16812 - Fix a file descriptor leak in start_daemon().
16813 - On Windows, you can't always reopen a port right after you've
16814 closed it. So change retry_listeners() to only close and re-open
16815 ports that have changed.
16816 - Workaround a problem with some http proxies that refuse GET
16817 requests that specify "Content-Length: 0". Reported by Adrian.
16818 - Recover better from TCP connections to Tor servers that are
16819 broken but don't tell you (it happens!); and rotate TLS
16820 connections once a week.
16821 - Fix a scary-looking but apparently harmless bug where circuits
16822 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16823 servers, and never switch to state CIRCUIT_STATE_OPEN.
16824 - Check for even more Windows version flags when writing the platform
16825 string in server descriptors, and note any we don't recognize.
16826 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16827 get a better idea of why their circuits failed. Not used yet.
16828 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16829 We don't use them yet, but maybe one day our DNS resolver will be
16830 able to discover them.
16831 - Let people type "tor --install" as well as "tor -install" when they
16832 want to make it an NT service.
16833 - Looks like we were never delivering deflated (i.e. compressed)
16834 running-routers lists, even when asked. Oops.
16835 - We were leaking some memory every time the client changed IPs.
16836 - Clean up more of the OpenSSL memory when exiting, so we can detect
16837 memory leaks better.
16838 - Never call free() on tor_malloc()d memory. This will help us
16839 use dmalloc to detect memory leaks.
16840 - Some Tor servers process billions of cells per day. These
16841 statistics are now uint64_t's.
16842 - Check [X-]Forwarded-For headers in HTTP requests when generating
16843 log messages. This lets people run dirservers (and caches) behind
16844 Apache but still know which IP addresses are causing warnings.
16845 - Fix minor integer overflow in calculating when we expect to use up
16846 our bandwidth allocation before hibernating.
16847 - Lower the minimum required number of file descriptors to 1000,
16848 so we can have some overhead for Valgrind on Linux, where the
16849 default ulimit -n is 1024.
16850 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16851 and its existence is confusing some users.
16853 o Config option fixes:
16854 - Add a new config option ExitPolicyRejectPrivate which defaults
16855 to on. Now all exit policies will begin with rejecting private
16856 addresses, unless the server operator explicitly turns it off.
16857 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
16858 - Add new ReachableORAddresses and ReachableDirAddresses options
16859 that understand address policies. FascistFirewall is now a synonym
16860 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
16861 - Start calling it FooListenAddress rather than FooBindAddress,
16862 since few of our users know what it means to bind an address
16864 - If the user gave Tor an odd number of command-line arguments,
16865 we were silently ignoring the last one. Now we complain and fail.
16866 This wins the oldest-bug prize -- this bug has been present since
16867 November 2002, as released in Tor 0.0.0.
16868 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16869 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16870 it would silently ignore the 6668.
16871 - If we get a linelist or linelist_s config option from the torrc,
16872 e.g. ExitPolicy, and it has no value, warn and skip rather than
16873 silently resetting it to its default.
16874 - Setconf was appending items to linelists, not clearing them.
16875 - Add MyFamily to torrc.sample in the server section, so operators
16876 will be more likely to learn that it exists.
16877 - Make ContactInfo mandatory for authoritative directory servers.
16878 - MaxConn has been obsolete for a while now. Document the ConnLimit
16879 config option, which is a *minimum* number of file descriptors
16880 that must be available else Tor refuses to start.
16881 - Get rid of IgnoreVersion undocumented config option, and make us
16882 only warn, never exit, when we're running an obsolete version.
16883 - Make MonthlyAccountingStart config option truly obsolete now.
16884 - Correct the man page entry on TrackHostExitsExpire.
16885 - Let directory authorities start even if they don't specify an
16886 Address config option.
16887 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16888 reflect the updated flags in our v2 dir protocol.
16890 o Config option features:
16891 - Add a new config option FastFirstHopPK (on by default) so clients
16892 do a trivial crypto handshake for their first hop, since TLS has
16893 already taken care of confidentiality and authentication.
16894 - Let the user set ControlListenAddress in the torrc. This can be
16895 dangerous, but there are some cases (like a secured LAN) where it
16897 - New config options to help controllers: FetchServerDescriptors
16898 and FetchHidServDescriptors for whether to fetch server
16899 info and hidserv info or let the controller do it, and
16900 PublishServerDescriptor and PublishHidServDescriptors.
16901 - Also let the controller set the __AllDirActionsPrivate config
16902 option if you want all directory fetches/publishes to happen via
16903 Tor (it assumes your controller bootstraps your circuits).
16904 - Add "HardwareAccel" config option: support for crypto hardware
16905 accelerators via OpenSSL. Off by default, until we find somebody
16906 smart who can test it for us. (It appears to produce seg faults
16907 in at least some cases.)
16908 - New config option "AuthDirRejectUnlisted" for directory authorities
16909 as a panic button: if we get flooded with unusable servers we can
16910 revert to only listing servers in the approved-routers file.
16911 - Directory authorities can now reject/invalidate by key and IP,
16912 with the config options "AuthDirInvalid" and "AuthDirReject", or
16913 by marking a fingerprint as "!reject" or "!invalid" (as its
16914 nickname) in the approved-routers file. This is useful since
16915 currently we automatically list servers as running and usable
16916 even if we know they're jerks.
16917 - Add a new config option TestSocks so people can see whether their
16918 applications are using socks4, socks4a, socks5-with-ip, or
16919 socks5-with-fqdn. This way they don't have to keep mucking
16920 with tcpdump and wondering if something got cached somewhere.
16921 - Add "private:*" as an alias in configuration for policies. Now
16922 you can simplify your exit policy rather than needing to list
16923 every single internal or nonroutable network space.
16924 - Accept "private:*" in routerdesc exit policies; not generated yet
16925 because older Tors do not understand it.
16926 - Add configuration option "V1AuthoritativeDirectory 1" which
16927 moria1, moria2, and tor26 have set.
16928 - Implement an option, VirtualAddrMask, to set which addresses
16929 get handed out in response to mapaddress requests. This works
16930 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16931 - Add a new config option FetchUselessDescriptors, off by default,
16932 for when you plan to run "exitlist" on your client and you want
16933 to know about even the non-running descriptors.
16934 - SocksTimeout: How long do we let a socks connection wait
16935 unattached before we fail it?
16936 - CircuitBuildTimeout: Cull non-open circuits that were born
16937 at least this many seconds ago.
16938 - CircuitIdleTimeout: Cull open clean circuits that were born
16939 at least this many seconds ago.
16940 - New config option SafeSocks to reject all application connections
16941 using unsafe socks protocols. Defaults to off.
16943 o Improved and clearer log messages:
16944 - Reduce clutter in server logs. We're going to try to make
16945 them actually usable now. New config option ProtocolWarnings that
16946 lets you hear about how _other Tors_ are breaking the protocol. Off
16948 - Divide log messages into logging domains. Once we put some sort
16949 of interface on this, it will let people looking at more verbose
16950 log levels specify the topics they want to hear more about.
16951 - Log server fingerprint on startup, so new server operators don't
16952 have to go hunting around their filesystem for it.
16953 - Provide dire warnings to any users who set DirServer manually;
16954 move it out of torrc.sample and into torrc.complete.
16955 - Make the log message less scary when all the dirservers are
16956 temporarily unreachable.
16957 - When tor_socketpair() fails in Windows, give a reasonable
16958 Windows-style errno back.
16959 - Improve tor_gettimeofday() granularity on windows.
16960 - We were printing the number of idle dns workers incorrectly when
16962 - Handle duplicate lines in approved-routers files without warning.
16963 - We were whining about using socks4 or socks5-with-local-lookup
16964 even when it's an IP address in the "virtual" range we designed
16965 exactly for this case.
16966 - Check for named servers when looking them up by nickname;
16967 warn when we're calling a non-named server by its nickname;
16968 don't warn twice about the same name.
16969 - Downgrade the dirserver log messages when whining about
16971 - Correct "your server is reachable" log entries to indicate that
16972 it was self-testing that told us so.
16973 - If we're trying to be a Tor server and running Windows 95/98/ME
16974 as a server, explain that we'll likely crash.
16975 - Provide a more useful warn message when our onion queue gets full:
16976 the CPU is too slow or the exit policy is too liberal.
16977 - Don't warn when we receive a 503 from a dirserver/cache -- this
16978 will pave the way for them being able to refuse if they're busy.
16979 - When we fail to bind a listener, try to provide a more useful
16980 log message: e.g., "Is Tor already running?"
16981 - Only start testing reachability once we've established a
16982 circuit. This will make startup on dir authorities less noisy.
16983 - Don't try to upload hidden service descriptors until we have
16984 established a circuit.
16985 - Tor didn't warn when it failed to open a log file.
16986 - Warn when listening on a public address for socks. We suspect a
16987 lot of people are setting themselves up as open socks proxies,
16988 and they have no idea that jerks on the Internet are using them,
16989 since they simply proxy the traffic into the Tor network.
16990 - Give a useful message when people run Tor as the wrong user,
16991 rather than telling them to start chowning random directories.
16992 - Fix a harmless bug that was causing Tor servers to log
16993 "Got an end because of misc error, but we're not an AP. Closing."
16994 - Fix wrong log message when you add a "HiddenServiceNodes" config
16995 line without any HiddenServiceDir line (reported by Chris Thomas).
16996 - Directory authorities now stop whining so loudly about bad
16997 descriptors that they fetch from other dirservers. So when there's
16998 a log complaint, it's for sure from a freshly uploaded descriptor.
16999 - When logging via syslog, include the pid whenever we provide
17000 a log entry. Suggested by Todd Fries.
17001 - When we're shutting down and we do something like try to post a
17002 server descriptor or rendezvous descriptor, don't complain that
17003 we seem to be unreachable. Of course we are, we're shutting down.
17004 - Change log line for unreachability to explicitly suggest /etc/hosts
17005 as the culprit. Also make it clearer what IP address and ports we're
17006 testing for reachability.
17007 - Put quotes around user-supplied strings when logging so users are
17008 more likely to realize if they add bad characters (like quotes)
17010 - NT service patch from Matt Edman to improve error messages on Win32.
17013 Changes in version 0.1.0.17 - 2006-02-17
17014 o Crash bugfixes on 0.1.0.x:
17015 - When servers with a non-zero DirPort came out of hibernation,
17016 sometimes they would trigger an assert.
17018 o Other important bugfixes:
17019 - On platforms that don't have getrlimit (like Windows), we were
17020 artificially constraining ourselves to a max of 1024
17021 connections. Now just assume that we can handle as many as 15000
17022 connections. Hopefully this won't cause other problems.
17024 o Backported features:
17025 - When we're a server, a client asks for an old-style directory,
17026 and our write bucket is empty, don't give it to him. This way
17027 small servers can continue to serve the directory *sometimes*,
17028 without getting overloaded.
17029 - Whenever you get a 503 in response to a directory fetch, try
17030 once more. This will become important once servers start sending
17031 503's whenever they feel busy.
17032 - Fetch a new directory every 120 minutes, not every 40 minutes.
17033 Now that we have hundreds of thousands of users running the old
17034 directory algorithm, it's starting to hurt a lot.
17035 - Bump up the period for forcing a hidden service descriptor upload
17036 from 20 minutes to 1 hour.
17039 Changes in version 0.1.0.16 - 2006-01-02
17040 o Crash bugfixes on 0.1.0.x:
17041 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17042 corrupting the heap, losing FDs, or crashing when we need to resize
17043 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17044 - It turns out sparc64 platforms crash on unaligned memory access
17045 too -- so detect and avoid this.
17046 - Handle truncated compressed data correctly (by detecting it and
17048 - Fix possible-but-unlikely free(NULL) in control.c.
17049 - When we were closing connections, there was a rare case that
17050 stomped on memory, triggering seg faults and asserts.
17051 - Avoid potential infinite recursion when building a descriptor. (We
17052 don't know that it ever happened, but better to fix it anyway.)
17053 - We were neglecting to unlink marked circuits from soon-to-close OR
17054 connections, which caused some rare scribbling on freed memory.
17055 - Fix a memory stomping race bug when closing the joining point of two
17056 rendezvous circuits.
17057 - Fix an assert in time parsing found by Steven Murdoch.
17059 o Other bugfixes on 0.1.0.x:
17060 - When we're doing reachability testing, provide more useful log
17061 messages so the operator knows what to expect.
17062 - Do not check whether DirPort is reachable when we are suppressing
17063 advertising it because of hibernation.
17064 - When building with -static or on Solaris, we sometimes needed -ldl.
17065 - One of the dirservers (tor26) changed its IP address.
17066 - When we're deciding whether a stream has enough circuits around
17067 that can handle it, count the freshly dirty ones and not the ones
17068 that are so dirty they won't be able to handle it.
17069 - When we're expiring old circuits, we had a logic error that caused
17070 us to close new rendezvous circuits rather than old ones.
17071 - Give a more helpful log message when you try to change ORPort via
17072 the controller: you should upgrade Tor if you want that to work.
17073 - We were failing to parse Tor versions that start with "Tor ".
17074 - Tolerate faulty streams better: when a stream fails for reason
17075 exitpolicy, stop assuming that the router is lying about his exit
17076 policy. When a stream fails for reason misc, allow it to retry just
17077 as if it was resolvefailed. When a stream has failed three times,
17078 reset its failure count so we can try again and get all three tries.
17081 Changes in version 0.1.0.15 - 2005-09-23
17082 o Bugfixes on 0.1.0.x:
17083 - Reject ports 465 and 587 (spam targets) in default exit policy.
17084 - Don't crash when we don't have any spare file descriptors and we
17085 try to spawn a dns or cpu worker.
17086 - Get rid of IgnoreVersion undocumented config option, and make us
17087 only warn, never exit, when we're running an obsolete version.
17088 - Don't try to print a null string when your server finds itself to
17089 be unreachable and the Address config option is empty.
17090 - Make the numbers in read-history and write-history into uint64s,
17091 so they don't overflow and publish negatives in the descriptor.
17092 - Fix a minor memory leak in smartlist_string_remove().
17093 - We were only allowing ourselves to upload a server descriptor at
17094 most every 20 minutes, even if it changed earlier than that.
17095 - Clean up log entries that pointed to old URLs.
17098 Changes in version 0.1.0.14 - 2005-08-08
17099 o Bugfixes on 0.1.0.x:
17100 - Fix the other half of the bug with crypto handshakes
17102 - Fix an assert trigger if you send a 'signal term' via the
17103 controller when it's listening for 'event info' messages.
17106 Changes in version 0.1.0.13 - 2005-08-04
17107 o Bugfixes on 0.1.0.x:
17108 - Fix a critical bug in the security of our crypto handshakes.
17109 - Fix a size_t underflow in smartlist_join_strings2() that made
17110 it do bad things when you hand it an empty smartlist.
17111 - Fix Windows installer to ship Tor license (thanks to Aphex for
17112 pointing out this oversight) and put a link to the doc directory
17114 - Explicitly set no-unaligned-access for sparc: it turns out the
17115 new gcc's let you compile broken code, but that doesn't make it
17119 Changes in version 0.1.0.12 - 2005-07-18
17120 o New directory servers:
17121 - tor26 has changed IP address.
17123 o Bugfixes on 0.1.0.x:
17124 - Fix a possible double-free in tor_gzip_uncompress().
17125 - When --disable-threads is set, do not search for or link against
17126 pthreads libraries.
17127 - Don't trigger an assert if an authoritative directory server
17128 claims its dirport is 0.
17129 - Fix bug with removing Tor as an NT service: some people were
17130 getting "The service did not return an error." Thanks to Matt
17134 Changes in version 0.1.0.11 - 2005-06-30
17135 o Bugfixes on 0.1.0.x:
17136 - Fix major security bug: servers were disregarding their
17137 exit policies if clients behaved unexpectedly.
17138 - Make OS X init script check for missing argument, so we don't
17139 confuse users who invoke it incorrectly.
17140 - Fix a seg fault in "tor --hash-password foo".
17141 - The MAPADDRESS control command was broken.
17144 Changes in version 0.1.0.10 - 2005-06-14
17146 - Make NT services work and start on startup on Win32 (based on
17147 patch by Matt Edman). See the FAQ entry for details.
17148 - Make 'platform' string in descriptor more accurate for Win32
17149 servers, so it's not just "unknown platform".
17150 - REUSEADDR on normal platforms means you can rebind to the port
17151 right after somebody else has let it go. But REUSEADDR on Win32
17152 means you can bind to the port _even when somebody else already
17153 has it bound_! So, don't do that on Win32.
17154 - Clean up the log messages when starting on Win32 with no config
17156 - Allow seeding the RNG on Win32 even when you're not running as
17157 Administrator. If seeding the RNG on Win32 fails, quit.
17159 o Assert / crash bugs:
17160 - Refuse relay cells that claim to have a length larger than the
17161 maximum allowed. This prevents a potential attack that could read
17162 arbitrary memory (e.g. keys) from an exit server's process
17164 - If unofficial Tor clients connect and send weird TLS certs, our
17165 Tor server triggers an assert. Stop asserting, and start handling
17166 TLS errors better in other situations too.
17167 - Fix a race condition that can trigger an assert when we have a
17168 pending create cell and an OR connection attempt fails.
17171 - Use pthreads for worker processes rather than forking. This was
17172 forced because when we forked, we ended up wasting a lot of
17173 duplicate ram over time.
17174 - Also switch to foo_r versions of some library calls to allow
17175 reentry and threadsafeness.
17176 - Implement --disable-threads configure option. Disable threads on
17177 netbsd and openbsd by default, because they have no reentrant
17178 resolver functions (!), and on solaris since it has other
17180 - Fix possible bug on threading platforms (e.g. win32) which was
17181 leaking a file descriptor whenever a cpuworker or dnsworker died.
17182 - Fix a minor memory leak when somebody establishes an introduction
17183 point at your Tor server.
17184 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
17186 - Add ./configure --with-dmalloc option, to track memory leaks.
17187 - And try to free all memory on closing, so we can detect what
17190 o Protocol correctness:
17191 - When we've connected to an OR and handshaked but didn't like
17192 the result, we were closing the conn without sending destroy
17193 cells back for pending circuits. Now send those destroys.
17194 - Start sending 'truncated' cells back rather than destroy cells
17195 if the circuit closes in front of you. This means we won't have
17196 to abandon partially built circuits.
17197 - Handle changed router status correctly when dirserver reloads
17198 fingerprint file. We used to be dropping all unverified descriptors
17199 right then. The bug was hidden because we would immediately
17200 fetch a directory from another dirserver, which would include the
17201 descriptors we just dropped.
17202 - Revise tor-spec to add more/better stream end reasons.
17203 - Revise all calls to connection_edge_end to avoid sending 'misc',
17204 and to take errno into account where possible.
17205 - Client now retries when streams end early for 'hibernating' or
17206 'resource limit' reasons, rather than failing them.
17207 - Try to be more zealous about calling connection_edge_end when
17208 things go bad with edge conns in connection.c.
17210 o Robustness improvements:
17211 - Better handling for heterogeneous / unreliable nodes:
17212 - Annotate circuits with whether they aim to contain high uptime
17213 nodes and/or high capacity nodes. When building circuits, choose
17215 - This means that every single node in an intro rend circuit,
17216 not just the last one, will have a minimum uptime.
17217 - New config option LongLivedPorts to indicate application streams
17218 that will want high uptime circuits.
17219 - Servers reset uptime when a dir fetch entirely fails. This
17220 hopefully reflects stability of the server's network connectivity.
17221 - If somebody starts his tor server in Jan 2004 and then fixes his
17222 clock, don't make his published uptime be a year.
17223 - Reset published uptime when we wake up from hibernation.
17224 - Introduce a notion of 'internal' circs, which are chosen without
17225 regard to the exit policy of the last hop. Intro and rendezvous
17226 circs must be internal circs, to avoid leaking information. Resolve
17227 and connect streams can use internal circs if they want.
17228 - New circuit pooling algorithm: keep track of what destination ports
17229 we've used recently (start out assuming we'll want to use 80), and
17230 make sure to have enough circs around to satisfy these ports. Also
17231 make sure to have 2 internal circs around if we've required internal
17232 circs lately (and with high uptime if we've seen that lately too).
17233 - Turn addr_policy_compare from a tristate to a quadstate; this should
17234 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17235 for google.com" problem.
17236 - When a client asks us for a dir mirror and we don't have one,
17237 launch an attempt to get a fresh one.
17238 - First cut at support for "create-fast" cells. Clients can use
17239 these when extending to their first hop, since the TLS already
17240 provides forward secrecy and authentication. Not enabled on
17243 o Reachability testing.
17244 - Your Tor server will automatically try to see if its ORPort and
17245 DirPort are reachable from the outside, and it won't upload its
17246 descriptor until it decides at least ORPort is reachable (when
17247 DirPort is not yet found reachable, publish it as zero).
17248 - When building testing circs for ORPort testing, use only
17249 high-bandwidth nodes, so fewer circuits fail.
17250 - Notice when our IP changes, and reset stats/uptime/reachability.
17251 - Authdirservers don't do ORPort reachability detection, since
17252 they're in clique mode, so it will be rare to find a server not
17253 already connected to them.
17254 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
17258 - Now we allow two unverified servers with the same nickname
17259 but different keys. But if a nickname is verified, only that
17260 nickname+key are allowed.
17261 - If you're an authdirserver connecting to an address:port,
17262 and it's not the OR you were expecting, forget about that
17263 descriptor. If he *was* the one you were expecting, then forget
17264 about all other descriptors for that address:port.
17265 - Allow servers to publish descriptors from 12 hours in the future.
17266 Corollary: only whine about clock skew from the dirserver if
17267 he's a trusted dirserver (since now even verified servers could
17268 have quite wrong clocks).
17269 - Require servers that use the default dirservers to have public IP
17270 addresses. We have too many servers that are configured with private
17271 IPs and their admins never notice the log entries complaining that
17272 their descriptors are being rejected.
17274 o Efficiency improvements:
17275 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
17276 and /dev/poll), and hopefully work better on Windows too.
17277 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
17278 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
17279 - Find libevent even if it's hiding in /usr/local/ and your
17280 CFLAGS and LDFLAGS don't tell you to look there.
17281 - Be able to link with libevent as a shared library (the default
17282 after 1.0d), even if it's hiding in /usr/local/lib and even
17283 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17284 assuming you're running gcc. Otherwise fail and give a useful
17286 - Switch to a new buffer management algorithm, which tries to avoid
17287 reallocing and copying quite as much. In first tests it looks like
17288 it uses *more* memory on average, but less cpu.
17289 - Switch our internal buffers implementation to use a ring buffer,
17290 to hopefully improve performance for fast servers a lot.
17291 - Reenable the part of the code that tries to flush as soon as an
17292 OR outbuf has a full TLS record available. Perhaps this will make
17293 OR outbufs not grow as huge except in rare cases, thus saving lots
17294 of CPU time plus memory.
17295 - Improve performance for dirservers: stop re-parsing the whole
17296 directory every time you regenerate it.
17297 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17298 it much faster to look up a circuit for each relay cell.
17299 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17300 since they're eating our cpu on exit nodes.
17301 - Stop wasting time doing a case insensitive comparison for every
17302 dns name every time we do any lookup. Canonicalize the names to
17303 lowercase when you first see them.
17306 - Handle unavailable hidden services better. Handle slow or busy
17307 hidden services better.
17308 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17309 circ as necessary, if there are any completed ones lying around
17310 when we try to launch one.
17311 - Make hidden services try to establish a rendezvous for 30 seconds
17312 after fetching the descriptor, rather than for n (where n=3)
17313 attempts to build a circuit.
17314 - Adjust maximum skew and age for rendezvous descriptors: let skew
17315 be 48 hours rather than 90 minutes.
17316 - Reject malformed .onion addresses rather then passing them on as
17317 normal web requests.
17320 - More Tor controller support. See
17321 http://tor.eff.org/doc/control-spec.txt for all the new features,
17322 including signals to emulate unix signals from any platform;
17323 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17324 closestream; closecircuit; etc.
17325 - Encode hashed controller passwords in hex instead of base64,
17326 to make it easier to write controllers.
17327 - Revise control spec and implementation to allow all log messages to
17328 be sent to controller with their severities intact (suggested by
17329 Matt Edman). Disable debug-level logs while delivering a debug-level
17330 log to the controller, to prevent loop. Update TorControl to handle
17331 new log event types.
17333 o New config options/defaults:
17334 - Begin scrubbing sensitive strings from logs by default. Turn off
17335 the config option SafeLogging if you need to do debugging.
17336 - New exit policy: accept most low-numbered ports, rather than
17337 rejecting most low-numbered ports.
17338 - Put a note in the torrc about abuse potential with the default
17340 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17342 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
17343 based on patch from Adam Langley (basic auth only).
17344 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17345 the fast servers that have been joining lately. (Clients are now
17346 willing to load balance over up to 2 MB of advertised bandwidth
17348 - New config option MaxAdvertisedBandwidth which lets you advertise
17349 a low bandwidthrate (to not attract as many circuits) while still
17350 allowing a higher bandwidthrate in reality.
17351 - Require BandwidthRate to be at least 20kB/s for servers.
17352 - Add a NoPublish config option, so you can be a server (e.g. for
17353 testing running Tor servers in other Tor networks) without
17354 publishing your descriptor to the primary dirservers.
17355 - Add a new AddressMap config directive to rewrite incoming socks
17356 addresses. This lets you, for example, declare an implicit
17357 required exit node for certain sites.
17358 - Add a new TrackHostExits config directive to trigger addressmaps
17359 for certain incoming socks addresses -- for sites that break when
17360 your exit keeps changing (based on patch from Mike Perry).
17361 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17362 which describes how often we retry making new circuits if current
17363 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17364 how long we're willing to make use of an already-dirty circuit.
17365 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
17366 a config option "ShutdownWaitLength" (when using kill -INT on
17368 - Fix an edge case in parsing config options: if they say "--"
17369 on the commandline, it's not a config option (thanks weasel).
17370 - New config option DirAllowPrivateAddresses for authdirservers.
17371 Now by default they refuse router descriptors that have non-IP or
17372 private-IP addresses.
17373 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17374 smart" default value: low for servers and high for clients.
17375 - Some people were putting "Address " in their torrc, and they had
17376 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17377 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17378 LOCALSTATEDIR/tor instead.
17379 - Implement --verify-config command-line option to check if your torrc
17380 is valid without actually launching Tor.
17382 o Logging improvements:
17383 - When dirservers refuse a server descriptor, we now log its
17384 contactinfo, platform, and the poster's IP address.
17385 - Only warn once per nickname from add_nickname_list_to_smartlist()
17386 per failure, so an entrynode or exitnode choice that's down won't
17388 - When we're connecting to an OR and he's got a different nickname/key
17389 than we were expecting, only complain loudly if we're an OP or a
17390 dirserver. Complaining loudly to the OR admins just confuses them.
17391 - Whine at you if you're a server and you don't set your contactinfo.
17392 - Warn when exit policy implicitly allows local addresses.
17393 - Give a better warning when some other server advertises an
17394 ORPort that is actually an apache running ssl.
17395 - If we get an incredibly skewed timestamp from a dirserver mirror
17396 that isn't a verified OR, don't warn -- it's probably him that's
17398 - When a dirserver causes you to give a warn, mention which dirserver
17400 - Initialize libevent later in the startup process, so the logs are
17401 already established by the time we start logging libevent warns.
17402 - Use correct errno on win32 if libevent fails.
17403 - Check and warn about known-bad/slow libevent versions.
17404 - Stop warning about sigpipes in the logs. We're going to
17405 pretend that getting these occasionally is normal and fine.
17407 o New contrib scripts:
17408 - New experimental script tor/contrib/exitlist: a simple python
17409 script to parse directories and find Tor nodes that exit to listed
17411 - New experimental script tor/contrib/ExerciseServer.py (needs more
17412 work) that uses the controller interface to build circuits and
17413 fetch pages over them. This will help us bootstrap servers that
17414 have lots of capacity but haven't noticed it yet.
17415 - New experimental script tor/contrib/PathDemo.py (needs more work)
17416 that uses the controller interface to let you choose whole paths
17418 "<hostname>.<path,separated by dots>.<length of path>.path"
17419 - New contributed script "privoxy-tor-toggle" to toggle whether
17420 Privoxy uses Tor. Seems to be configured for Debian by default.
17421 - Have torctl.in/tor.sh.in check for location of su binary (needed
17425 - chdir() to your datadirectory at the *end* of the daemonize process,
17426 not the beginning. This was a problem because the first time you
17427 run tor, if your datadir isn't there, and you have runasdaemon set
17428 to 1, it will try to chdir to it before it tries to create it. Oops.
17429 - Fix several double-mark-for-close bugs, e.g. where we were finding
17430 a conn for a cell even if that conn is already marked for close.
17431 - Stop most cases of hanging up on a socks connection without sending
17433 - Fix a bug in the RPM package: set home directory for _tor to
17434 something more reasonable when first installing.
17435 - Stop putting nodename in the Platform string in server descriptors.
17436 It doesn't actually help, and it is confusing/upsetting some people.
17437 - When using preferred entry or exit nodes, ignore whether the
17438 circuit wants uptime or capacity. They asked for the nodes, they
17440 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17441 artificially capped at 500kB.
17442 - Cache local dns resolves correctly even when they're .exit
17444 - If we're hibernating and we get a SIGINT, exit immediately.
17445 - tor-resolve requests were ignoring .exit if there was a working circuit
17446 they could use instead.
17447 - Pay more attention to the ClientOnly config option.
17448 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
17449 installer screens; and don't put stuff into StartupItems unless
17450 the user asks you to.
17453 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
17454 rather than just rejecting it.
17455 - If our clock jumps forward by 100 seconds or more, assume something
17456 has gone wrong with our network and abandon all not-yet-used circs.
17457 - When an application is using socks5, give him the whole variety of
17458 potential socks5 responses (connect refused, host unreachable, etc),
17459 rather than just "success" or "failure".
17460 - A more sane version numbering system. See
17461 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17462 - Change version parsing logic: a version is "obsolete" if it is not
17463 recommended and (1) there is a newer recommended version in the
17464 same series, or (2) there are no recommended versions in the same
17465 series, but there are some recommended versions in a newer series.
17466 A version is "new" if it is newer than any recommended version in
17468 - Report HTTP reasons to client when getting a response from directory
17469 servers -- so you can actually know what went wrong.
17470 - Reject odd-looking addresses at the client (e.g. addresses that
17471 contain a colon), rather than having the server drop them because
17473 - Stop publishing socksport in the directory, since it's not
17474 actually meant to be public. For compatibility, publish a 0 there
17476 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17477 cookies to disk and doesn't log each web request to disk. (Thanks
17478 to Brett Carrington for pointing this out.)
17479 - Add OSX uninstall instructions. An actual uninstall script will
17481 - Add "opt hibernating 1" to server descriptor to make it clearer
17482 whether the server is hibernating.
17485 Changes in version 0.0.9.10 - 2005-06-16
17486 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17487 - Refuse relay cells that claim to have a length larger than the
17488 maximum allowed. This prevents a potential attack that could read
17489 arbitrary memory (e.g. keys) from an exit server's process
17493 Changes in version 0.0.9.9 - 2005-04-23
17494 o Bugfixes on 0.0.9.x:
17495 - If unofficial Tor clients connect and send weird TLS certs, our
17496 Tor server triggers an assert. This release contains a minimal
17497 backport from the broader fix that we put into 0.1.0.4-rc.
17500 Changes in version 0.0.9.8 - 2005-04-07
17501 o Bugfixes on 0.0.9.x:
17502 - We have a bug that I haven't found yet. Sometimes, very rarely,
17503 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17504 thinks of itself as idle. This meant that no new circuits ever got
17505 established. Here's a workaround to kill any cpuworker that's been
17506 busy for more than 100 seconds.
17509 Changes in version 0.0.9.7 - 2005-04-01
17510 o Bugfixes on 0.0.9.x:
17511 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17512 - Compare identity to identity, not to nickname, when extending to
17513 a router not already in the directory. This was preventing us from
17514 extending to unknown routers. Oops.
17515 - Make sure to create OS X Tor user in <500 range, so we aren't
17516 creating actual system users.
17517 - Note where connection-that-hasn't-sent-end was marked, and fix
17518 a few really loud instances of this harmless bug (it's fixed more
17522 Changes in version 0.0.9.6 - 2005-03-24
17523 o Bugfixes on 0.0.9.x (crashes and asserts):
17524 - Add new end stream reasons to maintenance branch. Fix bug where
17525 reason (8) could trigger an assert. Prevent bug from recurring.
17526 - Apparently win32 stat wants paths to not end with a slash.
17527 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17528 blowing away the circuit that conn->cpath_layer points to, then
17529 checking to see if the circ is well-formed. Backport check to make
17530 sure we dont use the cpath on a closed connection.
17531 - Prevent circuit_resume_edge_reading_helper() from trying to package
17532 inbufs for marked-for-close streams.
17533 - Don't crash on hup if your options->address has become unresolvable.
17534 - Some systems (like OS X) sometimes accept() a connection and tell
17535 you the remote host is 0.0.0.0:0. If this happens, due to some
17536 other mis-features, we get confused; so refuse the conn for now.
17538 o Bugfixes on 0.0.9.x (other):
17539 - Fix harmless but scary "Unrecognized content encoding" warn message.
17540 - Add new stream error reason: TORPROTOCOL reason means "you are not
17541 speaking a version of Tor I understand; say bye-bye to your stream."
17542 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17543 into the future, now that we are more tolerant of skew. This
17544 resolves a bug where a Tor server would refuse to cache a directory
17545 because all the directories it gets are too far in the future;
17546 yet the Tor server never logs any complaints about clock skew.
17547 - Mac packaging magic: make man pages useable, and do not overwrite
17548 existing torrc files.
17549 - Make OS X log happily to /var/log/tor/tor.log
17552 Changes in version 0.0.9.5 - 2005-02-22
17553 o Bugfixes on 0.0.9.x:
17554 - Fix an assert race at exit nodes when resolve requests fail.
17555 - Stop picking unverified dir mirrors--it only leads to misery.
17556 - Patch from Matt Edman to make NT services work better. Service
17557 support is still not compiled into the executable by default.
17558 - Patch from Dmitri Bely so the Tor service runs better under
17559 the win32 SYSTEM account.
17560 - Make tor-resolve actually work (?) on Win32.
17561 - Fix a sign bug when getrlimit claims to have 4+ billion
17562 file descriptors available.
17563 - Stop refusing to start when bandwidthburst == bandwidthrate.
17564 - When create cells have been on the onion queue more than five
17565 seconds, just send back a destroy and take them off the list.
17568 Changes in version 0.0.9.4 - 2005-02-03
17569 o Bugfixes on 0.0.9:
17570 - Fix an assert bug that took down most of our servers: when
17571 a server claims to have 1 GB of bandwidthburst, don't
17573 - Don't crash as badly if we have spawned the max allowed number
17574 of dnsworkers, or we're out of file descriptors.
17575 - Block more file-sharing ports in the default exit policy.
17576 - MaxConn is now automatically set to the hard limit of max
17577 file descriptors we're allowed (ulimit -n), minus a few for
17579 - Give a clearer message when servers need to raise their
17580 ulimit -n when they start running out of file descriptors.
17581 - SGI Compatibility patches from Jan Schaumann.
17582 - Tolerate a corrupt cached directory better.
17583 - When a dirserver hasn't approved your server, list which one.
17584 - Go into soft hibernation after 95% of the bandwidth is used,
17585 not 99%. This is especially important for daily hibernators who
17586 have a small accounting max. Hopefully it will result in fewer
17587 cut connections when the hard hibernation starts.
17588 - Load-balance better when using servers that claim more than
17589 800kB/s of capacity.
17590 - Make NT services work (experimental, only used if compiled in).
17593 Changes in version 0.0.9.3 - 2005-01-21
17594 o Bugfixes on 0.0.9:
17595 - Backport the cpu use fixes from main branch, so busy servers won't
17596 need as much processor time.
17597 - Work better when we go offline and then come back, or when we
17598 run Tor at boot before the network is up. We do this by
17599 optimistically trying to fetch a new directory whenever an
17600 application request comes in and we think we're offline -- the
17601 human is hopefully a good measure of when the network is back.
17602 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17603 long as you keep using them; actually publish hidserv descriptors
17604 shortly after they change, rather than waiting 20-40 minutes.
17605 - Enable Mac startup script by default.
17606 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17607 - When you update AllowUnverifiedNodes or FirewallPorts via the
17608 controller's setconf feature, we were always appending, never
17610 - When you update HiddenServiceDir via setconf, it was screwing up
17611 the order of reading the lines, making it fail.
17612 - Do not rewrite a cached directory back to the cache; otherwise we
17613 will think it is recent and not fetch a newer one on startup.
17614 - Workaround for webservers that lie about Content-Encoding: Tor
17615 now tries to autodetect compressed directories and compression
17616 itself. This lets us Proxypass dir fetches through apache.
17619 Changes in version 0.0.9.2 - 2005-01-04
17620 o Bugfixes on 0.0.9 (crashes and asserts):
17621 - Fix an assert on startup when the disk is full and you're logging
17623 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17624 style address, then we'd crash.
17625 - Fix an assert trigger when the running-routers string we get from
17626 a dirserver is broken.
17627 - Make worker threads start and run on win32. Now win32 servers
17629 - Bandaid (not actually fix, but now it doesn't crash) an assert
17630 where the dns worker dies mysteriously and the main Tor process
17631 doesn't remember anything about the address it was resolving.
17633 o Bugfixes on 0.0.9 (Win32):
17634 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17635 name out of the warning/assert messages.
17636 - Fix a superficial "unhandled error on read" bug on win32.
17637 - The win32 installer no longer requires a click-through for our
17638 license, since our Free Software license grants rights but does not
17640 - Win32: When connecting to a dirserver fails, try another one
17641 immediately. (This was already working for non-win32 Tors.)
17642 - Stop trying to parse $HOME on win32 when hunting for default
17644 - Make tor-resolve.c work on win32 by calling network_init().
17646 o Bugfixes on 0.0.9 (other):
17647 - Make 0.0.9.x build on Solaris again.
17648 - Due to a fencepost error, we were blowing away the \n when reporting
17649 confvalue items in the controller. So asking for multiple config
17650 values at once couldn't work.
17651 - When listing circuits that are pending on an opening OR connection,
17652 if we're an OR we were listing circuits that *end* at us as
17653 being pending on every listener, dns/cpu worker, etc. Stop that.
17654 - Dirservers were failing to create 'running-routers' or 'directory'
17655 strings if we had more than some threshold of routers. Fix them so
17656 they can handle any number of routers.
17657 - Fix a superficial "Duplicate mark for close" bug.
17658 - Stop checking for clock skew for OR connections, even for servers.
17659 - Fix a fencepost error that was chopping off the last letter of any
17660 nickname that is the maximum allowed nickname length.
17661 - Update URLs in log messages so they point to the new website.
17662 - Fix a potential problem in mangling server private keys while
17663 writing to disk (not triggered yet, as far as we know).
17664 - Include the licenses for other free software we include in Tor,
17665 now that we're shipping binary distributions more regularly.
17668 Changes in version 0.0.9.1 - 2004-12-15
17669 o Bugfixes on 0.0.9:
17670 - Make hibernation actually work.
17671 - Make HashedControlPassword config option work.
17672 - When we're reporting event circuit status to a controller,
17673 don't use the stream status code.
17676 Changes in version 0.0.9 - 2004-12-12
17677 o Bugfixes on 0.0.8.1 (Crashes and asserts):
17678 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17679 write() call will fail and we handle it there.
17680 - When we run out of disk space, or other log writing error, don't
17681 crash. Just stop logging to that log and continue.
17682 - Fix isspace() and friends so they still make Solaris happy
17683 but also so they don't trigger asserts on win32.
17684 - Fix assert failure on malformed socks4a requests.
17685 - Fix an assert bug where a hidden service provider would fail if
17686 the first hop of his rendezvous circuit was down.
17687 - Better handling of size_t vs int, so we're more robust on 64
17690 o Bugfixes on 0.0.8.1 (Win32):
17691 - Make windows sockets actually non-blocking (oops), and handle
17692 win32 socket errors better.
17693 - Fix parse_iso_time on platforms without strptime (eg win32).
17694 - win32: when being multithreaded, leave parent fdarray open.
17695 - Better handling of winsock includes on non-MSV win32 compilers.
17696 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17698 - Make unit tests work on win32.
17700 o Bugfixes on 0.0.8.1 (Path selection and streams):
17701 - Calculate timeout for waiting for a connected cell from the time
17702 we sent the begin cell, not from the time the stream started. If
17703 it took a long time to establish the circuit, we would time out
17704 right after sending the begin cell.
17705 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17706 of * as always matching, so we were picking reject *:* nodes as
17707 exit nodes too. Oops.
17708 - When read() failed on a stream, we would close it without sending
17709 back an end. So 'connection refused' would simply be ignored and
17710 the user would get no response.
17711 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17712 we shouldn't hold-open-until-flush if the eof arrived first.
17713 - Let resolve conns retry/expire also, rather than sticking around
17715 - Fix more dns related bugs: send back resolve_failed and end cells
17716 more reliably when the resolve fails, rather than closing the
17717 circuit and then trying to send the cell. Also attach dummy resolve
17718 connections to a circuit *before* calling dns_resolve(), to fix
17719 a bug where cached answers would never be sent in RESOLVED cells.
17721 o Bugfixes on 0.0.8.1 (Circuits):
17722 - Finally fix a bug that's been plaguing us for a year:
17723 With high load, circuit package window was reaching 0. Whenever
17724 we got a circuit-level sendme, we were reading a lot on each
17725 socket, but only writing out a bit. So we would eventually reach
17726 eof. This would be noticed and acted on even when there were still
17727 bytes sitting in the inbuf.
17728 - Use identity comparison, not nickname comparison, to choose which
17729 half of circuit-ID-space each side gets to use. This is needed
17730 because sometimes we think of a router as a nickname, and sometimes
17731 as a hex ID, and we can't predict what the other side will do.
17733 o Bugfixes on 0.0.8.1 (Other):
17734 - Fix a whole slew of memory leaks.
17735 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17736 - If we are using select, make sure we stay within FD_SETSIZE.
17737 - When poll() is interrupted, we shouldn't believe the revents values.
17738 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17739 and smartlist_len, which are two major profiling offenders.
17740 - If do_hup fails, actually notice.
17741 - Flush the log file descriptor after we print "Tor opening log file",
17742 so we don't see those messages days later.
17743 - Hidden service operators now correctly handle version 1 style
17744 INTRODUCE1 cells (nobody generates them still, so not a critical
17746 - Handle more errnos from accept() without closing the listener.
17747 Some OpenBSD machines were closing their listeners because
17748 they ran out of file descriptors.
17749 - Some people had wrapped their tor client/server in a script
17750 that would restart it whenever it died. This did not play well
17751 with our "shut down if your version is obsolete" code. Now people
17752 don't fetch a new directory if their local cached version is
17754 - Make our autogen.sh work on ksh as well as bash.
17755 - Better torrc example lines for dirbindaddress and orbindaddress.
17756 - Improved bounds checking on parsed ints (e.g. config options and
17757 the ones we find in directories.)
17758 - Stop using separate defaults for no-config-file and
17759 empty-config-file. Now you have to explicitly turn off SocksPort,
17760 if you don't want it open.
17761 - We were starting to daemonize before we opened our logs, so if
17762 there were any problems opening logs, we would complain to stderr,
17763 which wouldn't work, and then mysteriously exit.
17764 - If a verified OR connects to us before he's uploaded his descriptor,
17765 or we verify him and hup but he still has the original TLS
17766 connection, then conn->nickname is still set like he's unverified.
17768 o Code security improvements, inspired by Ilja:
17769 - tor_snprintf wrapper over snprintf with consistent (though not C99)
17771 - Replace sprintf with tor_snprintf. (I think they were all safe, but
17773 - Replace strcpy/strncpy with strlcpy in more places.
17774 - Avoid strcat; use tor_snprintf or strlcat instead.
17776 o Features (circuits and streams):
17777 - New circuit building strategy: keep a list of ports that we've
17778 used in the past 6 hours, and always try to have 2 circuits open
17779 or on the way that will handle each such port. Seed us with port
17780 80 so web users won't complain that Tor is "slow to start up".
17781 - Make kill -USR1 dump more useful stats about circuits.
17782 - When warning about retrying or giving up, print the address, so
17783 the user knows which one it's talking about.
17784 - If you haven't used a clean circuit in an hour, throw it away,
17785 just to be on the safe side. (This means after 6 hours a totally
17786 unused Tor client will have no circuits open.)
17787 - Support "foo.nickname.exit" addresses, to let Alice request the
17788 address "foo" as viewed by exit node "nickname". Based on a patch
17789 from Geoff Goodell.
17790 - If your requested entry or exit node has advertised bandwidth 0,
17792 - Be more greedy about filling up relay cells -- we try reading again
17793 once we've processed the stuff we read, in case enough has arrived
17794 to fill the last cell completely.
17795 - Refuse application socks connections to port 0.
17796 - Use only 0.0.9pre1 and later servers for resolve cells.
17798 o Features (bandwidth):
17799 - Hibernation: New config option "AccountingMax" lets you
17800 set how many bytes per month (in each direction) you want to
17801 allow your server to consume. Rather than spreading those
17802 bytes out evenly over the month, we instead hibernate for some
17803 of the month and pop up at a deterministic time, work until
17804 the bytes are consumed, then hibernate again. Config option
17805 "MonthlyAccountingStart" lets you specify which day of the month
17806 your billing cycle starts on.
17807 - Implement weekly/monthly/daily accounting: now you specify your
17808 hibernation properties by
17809 AccountingMax N bytes|KB|MB|GB|TB
17810 AccountingStart day|week|month [day] HH:MM
17811 Defaults to "month 1 0:00".
17812 - Let bandwidth and interval config options be specified as 5 bytes,
17813 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17815 o Features (directories):
17816 - New "router-status" line in directory, to better bind each verified
17817 nickname to its identity key.
17818 - Clients can ask dirservers for /dir.z to get a compressed version
17819 of the directory. Only works for servers running 0.0.9, of course.
17820 - Make clients cache directories and use them to seed their router
17821 lists at startup. This means clients have a datadir again.
17822 - Respond to content-encoding headers by trying to uncompress as
17824 - Clients and servers now fetch running-routers; cache
17825 running-routers; compress running-routers; serve compressed
17827 - Make moria2 advertise a dirport of 80, so people behind firewalls
17828 will be able to get a directory.
17829 - Http proxy support
17830 - Dirservers translate requests for http://%s:%d/x to /x
17831 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17832 be routed through this host.
17833 - Clients ask for /tor/x rather than /x for new enough dirservers.
17834 This way we can one day coexist peacefully with apache.
17835 - Clients specify a "Host: %s%d" http header, to be compatible
17836 with more proxies, and so running squid on an exit node can work.
17837 - Protect dirservers from overzealous descriptor uploading -- wait
17838 10 seconds after directory gets dirty, before regenerating.
17840 o Features (packages and install):
17841 - Add NSI installer contributed by J Doe.
17842 - Apply NT service patch from Osamu Fujino. Still needs more work.
17843 - Commit VC6 and VC7 workspace/project files.
17844 - Commit a tor.spec for making RPM files, with help from jbash.
17845 - Add contrib/torctl.in contributed by Glenn Fink.
17846 - Make expand_filename handle ~ and ~username.
17847 - Use autoconf to enable largefile support where necessary. Use
17848 ftello where available, since ftell can fail at 2GB.
17849 - Ship src/win32/ in the tarball, so people can use it to build.
17850 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17853 o Features (ui controller):
17854 - Control interface: a separate program can now talk to your
17855 client/server over a socket, and get/set config options, receive
17856 notifications of circuits and streams starting/finishing/dying,
17857 bandwidth used, etc. The next step is to get some GUIs working.
17858 Let us know if you want to help out. See doc/control-spec.txt .
17859 - Ship a contrib/tor-control.py as an example script to interact
17860 with the control port.
17861 - "tor --hash-password zzyxz" will output a salted password for
17862 use in authenticating to the control interface.
17863 - Implement the control-spec's SAVECONF command, to write your
17864 configuration to torrc.
17865 - Get cookie authentication for the controller closer to working.
17866 - When set_conf changes our server descriptor, upload a new copy.
17867 But don't upload it too often if there are frequent changes.
17869 o Features (config and command-line):
17870 - Deprecate unofficial config option abbreviations, and abbreviations
17871 not on the command line.
17872 - Configuration infrastructure support for warning on obsolete
17874 - Give a slightly more useful output for "tor -h".
17875 - Break DirFetchPostPeriod into:
17876 - DirFetchPeriod for fetching full directory,
17877 - StatusFetchPeriod for fetching running-routers,
17878 - DirPostPeriod for posting server descriptor,
17879 - RendPostPeriod for posting hidden service descriptors.
17880 - New log format in config:
17881 "Log minsev[-maxsev] stdout|stderr|syslog" or
17882 "Log minsev[-maxsev] file /var/foo"
17883 - DirPolicy config option, to let people reject incoming addresses
17884 from their dirserver.
17885 - "tor --list-fingerprint" will list your identity key fingerprint
17887 - Make tor --version --version dump the cvs Id of every file.
17888 - New 'MyFamily nick1,...' config option for a server to
17889 specify other servers that shouldn't be used in the same circuit
17890 with it. Only believed if nick1 also specifies us.
17891 - New 'NodeFamily nick1,nick2,...' config option for a client to
17892 specify nodes that it doesn't want to use in the same circuit.
17893 - New 'Redirectexit pattern address:port' config option for a
17894 server to redirect exit connections, e.g. to a local squid.
17895 - Add "pass" target for RedirectExit, to make it easier to break
17896 out of a sequence of RedirectExit rules.
17897 - Make the dirservers file obsolete.
17898 - Include a dir-signing-key token in directories to tell the
17899 parsing entity which key is being used to sign.
17900 - Remove the built-in bulky default dirservers string.
17901 - New config option "Dirserver %s:%d [fingerprint]", which can be
17902 repeated as many times as needed. If no dirservers specified,
17903 default to moria1,moria2,tor26.
17904 - Make 'Routerfile' config option obsolete.
17905 - Discourage people from setting their dirfetchpostperiod more often
17906 than once per minute.
17908 o Features (other):
17909 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17910 get back to normal.)
17911 - Accept *:706 (silc) in default exit policy.
17912 - Implement new versioning format for post 0.1.
17913 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17914 log more informatively.
17915 - Check clock skew for verified servers, but allow unverified
17916 servers and clients to have any clock skew.
17917 - Make sure the hidden service descriptors are at a random offset
17918 from each other, to hinder linkability.
17919 - Clients now generate a TLS cert too, in preparation for having
17920 them act more like real nodes.
17921 - Add a pure-C tor-resolve implementation.
17922 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17923 1024) file descriptors.
17924 - Raise the max dns workers from 50 to 100.
17927 Changes in version 0.0.8.1 - 2004-10-13
17929 - Fix a seg fault that can be triggered remotely for Tor
17930 clients/servers with an open dirport.
17931 - Fix a rare assert trigger, where routerinfos for entries in
17932 our cpath would expire while we're building the path.
17933 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17934 - Fix a rare seg fault for people running hidden services on
17935 intermittent connections.
17936 - Fix a bug in parsing opt keywords with objects.
17937 - Fix a stale pointer assert bug when a stream detaches and
17939 - Fix a string format vulnerability (probably not exploitable)
17940 in reporting stats locally.
17941 - Fix an assert trigger: sometimes launching circuits can fail
17942 immediately, e.g. because too many circuits have failed recently.
17943 - Fix a compile warning on 64 bit platforms.
17946 Changes in version 0.0.8 - 2004-08-25
17948 - Made our unit tests compile again on OpenBSD 3.5, and tor
17949 itself compile again on OpenBSD on a sparc64.
17950 - We were neglecting milliseconds when logging on win32, so
17951 everything appeared to happen at the beginning of each second.
17952 - Check directory signature _before_ you decide whether you're
17953 you're running an obsolete version and should exit.
17954 - Check directory signature _before_ you parse the running-routers
17955 list to decide who's running.
17956 - Check return value of fclose while writing to disk, so we don't
17957 end up with broken files when servers run out of disk space.
17958 - Port it to SunOS 5.9 / Athena
17959 - Fix two bugs in saving onion keys to disk when rotating, so
17960 hopefully we'll get fewer people using old onion keys.
17961 - Remove our mostly unused -- and broken -- hex_encode()
17962 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17963 for pointing out this bug.)
17964 - Only pick and establish intro points after we've gotten a
17966 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17967 don't put it into the client dns cache.
17968 - If a begin failed due to exit policy, but we believe the IP
17969 address should have been allowed, switch that router to exitpolicy
17970 reject *:* until we get our next directory.
17972 o Protocol changes:
17973 - 'Extend' relay cell payloads now include the digest of the
17974 intended next hop's identity key. Now we can verify that we're
17975 extending to the right router, and also extend to routers we
17976 hadn't heard of before.
17979 - Tor nodes can now act as relays (with an advertised ORPort)
17980 without being manually verified by the dirserver operators.
17981 - Uploaded descriptors of unverified routers are now accepted
17982 by the dirservers, and included in the directory.
17983 - Verified routers are listed by nickname in the running-routers
17984 list; unverified routers are listed as "$<fingerprint>".
17985 - We now use hash-of-identity-key in most places rather than
17986 nickname or addr:port, for improved security/flexibility.
17987 - AllowUnverifiedNodes config option to let circuits choose no-name
17988 routers in entry,middle,exit,introduction,rendezvous positions.
17989 Allow middle and rendezvous positions by default.
17990 - When picking unverified routers, skip those with low uptime and/or
17991 low bandwidth, depending on what properties you care about.
17992 - ClientOnly option for nodes that never want to become servers.
17993 - Directory caching.
17994 - "AuthoritativeDir 1" option for the official dirservers.
17995 - Now other nodes (clients and servers) will cache the latest
17996 directory they've pulled down.
17997 - They can enable their DirPort to serve it to others.
17998 - Clients will pull down a directory from any node with an open
17999 DirPort, and check the signature/timestamp correctly.
18000 - Authoritative dirservers now fetch directories from other
18001 authdirservers, to stay better synced.
18002 - Running-routers list tells who's down also, along with noting
18003 if they're verified (listed by nickname) or unverified (listed
18005 - Allow dirservers to serve running-router list separately.
18006 This isn't used yet.
18007 - You can now fetch $DIRURL/running-routers to get just the
18008 running-routers line, not the whole descriptor list. (But
18009 clients don't use this yet.)
18010 - Clients choose nodes proportional to advertised bandwidth.
18011 - Clients avoid using nodes with low uptime as introduction points.
18012 - Handle servers with dynamic IP addresses: don't just replace
18013 options->Address with the resolved one at startup, and
18014 detect our address right before we make a routerinfo each time.
18015 - 'FascistFirewall' option to pick dirservers and ORs on specific
18016 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18017 which ports are open. (Defaults to 80,443)
18018 - Try other dirservers immediately if the one you try is down. This
18019 should tolerate down dirservers better now.
18020 - ORs connect-on-demand to other ORs
18021 - If you get an extend cell to an OR you're not connected to,
18022 connect, handshake, and forward the create cell.
18023 - The authoritative dirservers stay connected to everybody,
18024 and everybody stays connected to 0.0.7 servers, but otherwise
18025 clients/servers expire unused connections after 5 minutes.
18026 - When servers get a sigint, they delay 30 seconds (refusing new
18027 connections) then exit. A second sigint causes immediate exit.
18028 - File and name management:
18029 - Look for .torrc if no CONFDIR "torrc" is found.
18030 - If no datadir is defined, then choose, make, and secure ~/.tor
18032 - If torrc not found, exitpolicy reject *:*.
18033 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18034 - If no nickname is defined, derive default from hostname.
18035 - Rename secret key files, e.g. identity.key -> secret_id_key,
18036 to discourage people from mailing their identity key to tor-ops.
18037 - Refuse to build a circuit before the directory has arrived --
18038 it won't work anyway, since you won't know the right onion keys
18040 - Parse tor version numbers so we can do an is-newer-than check
18041 rather than an is-in-the-list check.
18042 - New socks command 'resolve', to let us shim gethostbyname()
18044 - A 'tor_resolve' script to access the socks resolve functionality.
18045 - A new socks-extensions.txt doc file to describe our
18046 interpretation and extensions to the socks protocols.
18047 - Add a ContactInfo option, which gets published in descriptor.
18048 - Write tor version at the top of each log file
18049 - New docs in the tarball:
18051 - Document that you should proxy your SSL traffic too.
18052 - Log a warning if the user uses an unsafe socks variant, so people
18053 are more likely to learn about privoxy or socat.
18054 - Log a warning if you're running an unverified server, to let you
18055 know you might want to get it verified.
18056 - Change the default exit policy to reject the default edonkey,
18057 kazaa, gnutella ports.
18058 - Add replace_file() to util.[ch] to handle win32's rename().
18059 - Publish OR uptime in descriptor (and thus in directory) too.
18060 - Remember used bandwidth (both in and out), and publish 15-minute
18061 snapshots for the past day into our descriptor.
18062 - Be more aggressive about trying to make circuits when the network
18063 has changed (e.g. when you unsuspend your laptop).
18064 - Check for time skew on http headers; report date in response to
18066 - If the entrynode config line has only one node, don't pick it as
18068 - Add strict{entry|exit}nodes config options. If set to 1, then
18069 we refuse to build circuits that don't include the specified entry
18071 - OutboundBindAddress config option, to bind to a specific
18072 IP address for outgoing connect()s.
18073 - End truncated log entries (e.g. directories) with "[truncated]".
18076 Changes in version 0.0.7.3 - 2004-08-12
18077 o Stop dnsworkers from triggering an assert failure when you
18078 ask them to resolve the host "".
18081 Changes in version 0.0.7.2 - 2004-07-07
18082 o A better fix for the 0.0.0.0 problem, that will hopefully
18083 eliminate the remaining related assertion failures.
18086 Changes in version 0.0.7.1 - 2004-07-04
18087 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18088 since internally we use 0.0.0.0 to signify "not yet resolved".
18091 Changes in version 0.0.7 - 2004-06-07
18092 o Fixes for crashes and other obnoxious bugs:
18093 - Fix an epipe bug: sometimes when directory connections failed
18094 to connect, we would give them a chance to flush before closing
18096 - When we detached from a circuit because of resolvefailed, we
18097 would immediately try the same circuit twice more, and then
18098 give up on the resolve thinking we'd tried three different
18100 - Limit the number of intro circuits we'll attempt to build for a
18101 hidden service per 15-minute period.
18102 - Check recommended-software string *early*, before actually parsing
18103 the directory. Thus we can detect an obsolete version and exit,
18104 even if the new directory format doesn't parse.
18105 o Fixes for security bugs:
18106 - Remember which nodes are dirservers when you startup, and if a
18107 random OR enables his dirport, don't automatically assume he's
18108 a trusted dirserver.
18110 - Directory connections were asking the wrong poll socket to
18111 start writing, and not asking themselves to start writing.
18112 - When we detached from a circuit because we sent a begin but
18113 didn't get a connected, we would use it again the first time;
18114 but after that we would correctly switch to a different one.
18115 - Stop warning when the first onion decrypt attempt fails; they
18116 will sometimes legitimately fail now that we rotate keys.
18117 - Override unaligned-access-ok check when $host_cpu is ia64 or
18118 arm. Apparently they allow it but the kernel whines.
18119 - Dirservers try to reconnect periodically too, in case connections
18121 - Fix some memory leaks in directory servers.
18122 - Allow backslash in Win32 filenames.
18123 - Made Tor build complain-free on FreeBSD, hopefully without
18124 breaking other BSD builds. We'll see.
18125 - Check directory signatures based on name of signer, not on whom
18126 we got the directory from. This will let us cache directories more
18128 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18131 - Doxygen markup on all functions and global variables.
18132 - Make directory functions update routerlist, not replace it. So
18133 now directory disagreements are not so critical a problem.
18134 - Remove the upper limit on number of descriptors in a dirserver's
18135 directory (not that we were anywhere close).
18136 - Allow multiple logfiles at different severity ranges.
18137 - Allow *BindAddress to specify ":port" rather than setting *Port
18138 separately. Allow multiple instances of each BindAddress config
18139 option, so you can bind to multiple interfaces if you want.
18140 - Allow multiple exit policy lines, which are processed in order.
18141 Now we don't need that huge line with all the commas in it.
18142 - Enable accept/reject policies on SOCKS connections, so you can bind
18143 to 0.0.0.0 but still control who can use your OP.
18144 - Updated the man page to reflect these features.
18147 Changes in version 0.0.6.2 - 2004-05-16
18148 o Our integrity-checking digest was checking only the most recent cell,
18149 not the previous cells like we'd thought.
18150 Thanks to Stefan Mark for finding the flaw!
18153 Changes in version 0.0.6.1 - 2004-05-06
18154 o Fix two bugs in our AES counter-mode implementation (this affected
18155 onion-level stream encryption, but not TLS-level). It turns
18156 out we were doing something much more akin to a 16-character
18157 polyalphabetic cipher. Oops.
18158 Thanks to Stefan Mark for finding the flaw!
18159 o Retire moria3 as a directory server, and add tor26 as a directory
18163 Changes in version 0.0.6 - 2004-05-02
18165 - Hidden services and rendezvous points are implemented. Go to
18166 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18167 hidden services. (This only works via a socks4a proxy such as
18168 Privoxy, and currently it's quite slow.)
18169 - We now rotate link (tls context) keys and onion keys.
18170 - CREATE cells now include oaep padding, so you can tell
18171 if you decrypted them correctly.
18172 - Retry stream correctly when we fail to connect because of
18173 exit-policy-reject (should try another) or can't-resolve-address.
18174 - When we hup a dirserver and we've *removed* a server from the
18175 approved-routers list, now we remove that server from the
18176 in-memory directories too.
18177 - Add bandwidthburst to server descriptor.
18178 - Directories now say which dirserver signed them.
18179 - Use a tor_assert macro that logs failed assertions too.
18180 - Since we don't support truncateds much, don't bother sending them;
18181 just close the circ.
18182 - Fetch randomness from /dev/urandom better (not via fopen/fread)
18183 - Better debugging for tls errors
18184 - Set Content-Type on the directory and hidserv descriptor.
18185 - Remove IVs from cipher code, since AES-ctr has none.
18187 - Fix an assert trigger for exit nodes that's been plaguing us since
18188 the days of 0.0.2prexx (thanks weasel!)
18189 - Fix a bug where we were closing tls connections intermittently.
18190 It turns out openssl keeps its errors around -- so if an error
18191 happens, and you don't ask about it, and then another openssl
18192 operation happens and succeeds, and you ask if there was an error,
18193 it tells you about the first error.
18194 - Fix a bug that's been lurking since 27 may 03 (!)
18195 When passing back a destroy cell, we would use the wrong circ id.
18196 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
18197 - Some versions of openssl have an SSL_pending function that erroneously
18198 returns bytes when there is a non-application record pending.
18199 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18200 o We were using an array of length zero in a few places.
18201 o Win32's gethostbyname can't resolve an IP to an IP.
18202 o Win32's close can't close a socket.
18203 o Handle windows socket errors correctly.
18205 - check for <sys/limits.h> so we build on FreeBSD again, and
18206 <machine/limits.h> for NetBSD.
18209 Changes in version 0.0.5 - 2004-03-30
18210 o Install torrc as torrc.sample -- we no longer clobber your
18212 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18213 o Only build circuits after we've fetched the directory: clients were
18214 using only the directory servers before they'd fetched a directory.
18215 This also means longer startup time; so it goes.
18216 o Fix an assert trigger where an OP would fail to handshake, and we'd
18217 expect it to have a nickname.
18218 o Work around a tsocks bug: do a socks reject when AP connection dies
18219 early, else tsocks goes into an infinite loop.
18220 o Hold socks connection open until reply is flushed (if possible)
18221 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18222 the dns farm to do it.
18223 o Fix c99 aliasing warnings in rephist.c
18224 o Don't include server descriptors that are older than 24 hours in the
18226 o Give socks 'reject' replies their whole 15s to attempt to flush,
18227 rather than seeing the 60s timeout and assuming the flush had failed.
18228 o Clean automake droppings from the cvs repository
18229 o Add in a 'notice' log level for things the operator should hear
18230 but that aren't warnings
18233 Changes in version 0.0.4 - 2004-03-26
18234 o When connecting to a dirserver or OR and the network is down,
18238 Changes in version 0.0.3 - 2004-03-26
18239 o Warn and fail if server chose a nickname with illegal characters
18240 o Port to Solaris and Sparc:
18241 - include missing header fcntl.h
18242 - have autoconf find -lsocket -lnsl automatically
18243 - deal with hardware word alignment
18244 - make uname() work (solaris has a different return convention)
18245 - switch from using signal() to sigaction()
18246 o Preliminary work on reputation system:
18247 - Keep statistics on success/fail of connect attempts; they're published
18248 by kill -USR1 currently.
18249 - Add a RunTesting option to try to learn link state by creating test
18250 circuits, even when SocksPort is off.
18251 - Remove unused open circuits when there are too many.
18254 Changes in version 0.0.2 - 2004-03-19
18255 - Include strlcpy and strlcat for safer string ops
18256 - define INADDR_NONE so we compile (but still not run) on solaris
18259 Changes in version 0.0.2pre27 - 2004-03-14
18261 - Allow internal tor networks (we were rejecting internal IPs,
18262 now we allow them if they're set explicitly).
18263 - And fix a few endian issues.
18266 Changes in version 0.0.2pre26 - 2004-03-14
18268 - If a stream times out after 15s without a connected cell, don't
18269 try that circuit again: try a new one.
18270 - Retry streams at most 4 times. Then give up.
18271 - When a dirserver gets a descriptor from an unknown router, it
18272 logs its fingerprint (so the dirserver operator can choose to
18273 accept it even without mail from the server operator).
18274 - Inform unapproved servers when we reject their descriptors.
18275 - Make tor build on Windows again. It works as a client, who knows
18277 - Clearer instructions in the torrc for how to set up a server.
18278 - Be more efficient about reading fd's when our global token bucket
18279 (used for rate limiting) becomes empty.
18281 - Stop asserting that computers always go forward in time. It's
18283 - When we sent a cell (e.g. destroy) and then marked an OR connection
18284 expired, we might close it before finishing a flush if the other
18285 side isn't reading right then.
18286 - Don't allow dirservers to start if they haven't defined
18287 RecommendedVersions
18288 - We were caching transient dns failures. Oops.
18289 - Prevent servers from publishing an internal IP as their address.
18290 - Address a strcat vulnerability in circuit.c
18293 Changes in version 0.0.2pre25 - 2004-03-04
18295 - Put the OR's IP in its router descriptor, not its fqdn. That way
18296 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18299 - If the user typed in an address that didn't resolve, the server
18303 Changes in version 0.0.2pre24 - 2004-03-03
18305 - Fix an assertion failure in dns.c, where we were trying to dequeue
18306 a pending dns resolve even if it wasn't pending
18307 - Fix a spurious socks5 warning about still trying to write after the
18308 connection is finished.
18309 - Hold certain marked_for_close connections open until they're finished
18310 flushing, rather than losing bytes by closing them too early.
18311 - Correctly report the reason for ending a stream
18312 - Remove some duplicate calls to connection_mark_for_close
18313 - Put switch_id and start_daemon earlier in the boot sequence, so it
18314 will actually try to chdir() to options.DataDirectory
18315 - Make 'make test' exit(1) if a test fails; fix some unit tests
18316 - Make tor fail when you use a config option it doesn't know about,
18317 rather than warn and continue.
18318 - Make --version work
18319 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18322 Changes in version 0.0.2pre23 - 2004-02-29
18324 - Print a statement when the first circ is finished, so the user
18325 knows it's working.
18326 - If a relay cell is unrecognized at the end of the circuit,
18327 send back a destroy. (So attacks to mutate cells are more
18329 - New config option 'excludenodes' to avoid certain nodes for circuits.
18330 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18331 so you can collect coredumps there.
18333 - Fix a bug in tls flushing where sometimes data got wedged and
18334 didn't flush until more data got sent. Hopefully this bug was
18335 a big factor in the random delays we were seeing.
18336 - Make 'connected' cells include the resolved IP, so the client
18337 dns cache actually gets populated.
18338 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18339 - When we time-out on a stream and detach from the circuit, send an
18340 end cell down it first.
18341 - Only warn about an unknown router (in exitnodes, entrynodes,
18342 excludenodes) after we've fetched a directory.
18345 Changes in version 0.0.2pre22 - 2004-02-26
18347 - Servers publish less revealing uname information in descriptors.
18348 - More memory tracking and assertions, to crash more usefully when
18350 - If the default torrc isn't there, just use some default defaults.
18351 Plus provide an internal dirservers file if they don't have one.
18352 - When the user tries to use Tor as an http proxy, give them an http
18353 501 failure explaining that we're a socks proxy.
18354 - Dump a new router.desc on hup, to help confused people who change
18355 their exit policies and then wonder why router.desc doesn't reflect
18357 - Clean up the generic tor.sh init script that we ship with.
18359 - If the exit stream is pending on the resolve, and a destroy arrives,
18360 then the stream wasn't getting removed from the pending list. I
18361 think this was the one causing recent server crashes.
18362 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18363 - When it couldn't resolve any dirservers, it was useless from then on.
18364 Now it reloads the RouterFile (or default dirservers) if it has no
18366 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18367 many users don't even *have* a /usr/local/sbin/.
18370 Changes in version 0.0.2pre21 - 2004-02-18
18372 - There's a ChangeLog file that actually reflects the changelog.
18373 - There's a 'torify' wrapper script, with an accompanying
18374 tor-tsocks.conf, that simplifies the process of using tsocks for
18375 tor. It even has a man page.
18376 - The tor binary gets installed to sbin rather than bin now.
18377 - Retry streams where the connected cell hasn't arrived in 15 seconds
18378 - Clean up exit policy handling -- get the default out of the torrc,
18379 so we can update it without forcing each server operator to fix
18381 - Allow imaps and pop3s in default exit policy
18383 - Prevent picking middleman nodes as the last node in the circuit
18386 Changes in version 0.0.2pre20 - 2004-01-30
18388 - We now have a deb package, and it's in debian unstable. Go to
18389 it, apt-getters. :)
18390 - I've split the TotalBandwidth option into BandwidthRate (how many
18391 bytes per second you want to allow, long-term) and
18392 BandwidthBurst (how many bytes you will allow at once before the cap
18393 kicks in). This better token bucket approach lets you, say, set
18394 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18395 performance while not exceeding your monthly bandwidth quota.
18396 - Push out a tls record's worth of data once you've got it, rather
18397 than waiting until you've read everything waiting to be read. This
18398 may improve performance by pipelining better. We'll see.
18399 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18400 from failed circuits (if they haven't been connected yet) and attach
18402 - Expire old streams that haven't managed to connect. Some day we'll
18403 have them reattach to new circuits instead.
18406 - Fix several memory leaks that were causing servers to become bloated
18408 - Fix a few very rare assert triggers. A few more remain.
18409 - Setuid to User _before_ complaining about running as root.
18412 Changes in version 0.0.2pre19 - 2004-01-07
18414 - Fix deadlock condition in dns farm. We were telling a child to die by
18415 closing the parent's file descriptor to him. But newer children were
18416 inheriting the open file descriptor from the parent, and since they
18417 weren't closing it, the socket never closed, so the child never read
18418 eof, so he never knew to exit. Similarly, dns workers were holding
18419 open other sockets, leading to all sorts of chaos.
18420 - New cleaner daemon() code for forking and backgrounding.
18421 - If you log to a file, it now prints an entry at the top of the
18422 logfile so you know it's working.
18423 - The onionskin challenge length was 30 bytes longer than necessary.
18424 - Started to patch up the spec so it's not quite so out of date.
18427 Changes in version 0.0.2pre18 - 2004-01-02
18429 - Fix endian issues with the 'integrity' field in the relay header.
18430 - Fix a potential bug where connections in state
18431 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18434 Changes in version 0.0.2pre17 - 2003-12-30
18436 - Made --debuglogfile (or any second log file, actually) work.
18437 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18438 adversary could force us into an infinite loop.
18441 - Each onionskin handshake now includes a hash of the computed key,
18442 to prove the server's identity and help perfect forward secrecy.
18443 - Changed cell size from 256 to 512 bytes (working toward compatibility
18445 - Changed cell length to 2 bytes, and moved it to the relay header.
18446 - Implemented end-to-end integrity checking for the payloads of
18448 - Separated streamid from 'recognized' (otherwise circuits will get
18449 messed up when we try to have streams exit from the middle). We
18450 use the integrity-checking to confirm that a cell is addressed to
18452 - Randomize the initial circid and streamid values, so an adversary who
18453 breaks into a node can't learn how many circuits or streams have
18457 Changes in version 0.0.2pre16 - 2003-12-14
18459 - Fixed a bug that made HUP trigger an assert
18460 - Fixed a bug where a circuit that immediately failed wasn't being
18461 counted as a failed circuit in counting retries.
18464 - Now we close the circuit when we get a truncated cell: otherwise we're
18465 open to an anonymity attack where a bad node in the path truncates
18466 the circuit and then we open streams at him.
18467 - Add port ranges to exit policies
18468 - Add a conservative default exit policy
18469 - Warn if you're running tor as root
18470 - on HUP, retry OR connections and close/rebind listeners
18471 - options.EntryNodes: try these nodes first when picking the first node
18472 - options.ExitNodes: if your best choices happen to include any of
18473 your preferred exit nodes, you choose among just those preferred
18475 - options.ExcludedNodes: nodes that are never picked in path building
18478 Changes in version 0.0.2pre15 - 2003-12-03
18479 o Robustness and bugfixes:
18480 - Sometimes clients would cache incorrect DNS resolves, which would
18481 really screw things up.
18482 - An OP that goes offline would slowly leak all its sockets and stop
18484 - A wide variety of bugfixes in exit node selection, exit policy
18485 handling, and processing pending streams when a new circuit is
18487 - Pick nodes for a path only from those the directory says are up
18488 - Choose randomly from all running dirservers, not always the first one
18489 - Increase allowed http header size for directory fetch.
18490 - Stop writing to stderr (if we're daemonized it will be closed).
18491 - Enable -g always, so cores will be more useful to me.
18492 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18495 - Wrote a man page. It lists commonly used options.
18498 - Change default loglevel to warn.
18499 - Make PidFile default to null rather than littering in your CWD.
18500 - OnionRouter config option is now obsolete. Instead it just checks
18502 - Moved to a single unified torrc file for both clients and servers.
18505 Changes in version 0.0.2pre14 - 2003-11-29
18506 o Robustness and bugfixes:
18507 - Force the admin to make the DataDirectory himself
18508 - to get ownership/permissions right
18509 - so clients no longer make a DataDirectory and then never use it
18510 - fix bug where a client who was offline for 45 minutes would never
18511 pull down a directory again
18512 - fix (or at least hide really well) the dns assert bug that was
18513 causing server crashes
18514 - warnings and improved robustness wrt clockskew for certs
18515 - use the native daemon(3) to daemonize, when available
18516 - exit if bind() fails
18517 - exit if neither socksport nor orport is defined
18518 - include our own tor_timegm (Win32 doesn't have its own)
18519 - bugfix for win32 with lots of connections
18520 - fix minor bias in PRNG
18521 - make dirserver more robust to corrupt cached directory
18524 - Wrote the design document (woo)
18526 o Circuit building and exit policies:
18527 - Circuits no longer try to use nodes that the directory has told them
18529 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18530 bitcounts (18.0.0.0/8).
18531 - Make AP connections standby for a circuit if no suitable circuit
18532 exists, rather than failing
18533 - Circuits choose exit node based on addr/port, exit policies, and
18534 which AP connections are standing by
18535 - Bump min pathlen from 2 to 3
18536 - Relay end cells have a payload to describe why the stream ended.
18537 - If the stream failed because of exit policy, try again with a new
18539 - Clients have a dns cache to remember resolved addresses.
18540 - Notice more quickly when we have no working circuits
18543 - APPort is now called SocksPort
18544 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18546 - RecommendedVersions is now a config variable rather than
18547 hardcoded (for dirservers)
18548 - Reloads config on HUP
18549 - Usage info on -h or --help
18550 - If you set User and Group config vars, it'll setu/gid to them.
18552 Changes in version 0.0.2pre13 - 2003-10-19
18553 o General stability:
18554 - SSL_write no longer fails when it returns WANTWRITE and the number
18555 of bytes in the buf has changed by the next SSL_write call.
18556 - Fix segfault fetching directory when network is down
18557 - Fix a variety of minor memory leaks
18558 - Dirservers reload the fingerprints file on HUP, so I don't have
18559 to take down the network when I approve a new router
18560 - Default server config file has explicit Address line to specify fqdn
18563 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18564 - Make listener connections not ever alloc bufs
18566 o Autoconf improvements:
18567 - don't clobber an external CFLAGS in ./configure
18568 - Make install now works
18569 - create var/lib/tor on make install
18570 - autocreate a tor.sh initscript to help distribs
18571 - autocreate the torrc and sample-server-torrc with correct paths
18573 o Log files and Daemonizing now work:
18574 - If --DebugLogFile is specified, log to it at -l debug
18575 - If --LogFile is specified, use it instead of commandline
18576 - If --RunAsDaemon is set, tor forks and backgrounds on startup